[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[ipcdn] pktcSigDevToneWholeToneRepeatCount description in draft-07 of the Signaling MIB



The draft-07 of the Signaling MIB contains the following wording on the
requirement for pktcSigDevToneWholeToneRepeatCount object:

             If the pktcSigDevToneType is callWaiting1-4, the 
             pktcSigDevToneWholeToneRepeatCount does not apply and MUST 
             be ignored on SNMP get/set operations.

I have two issues here:

1. The MUST requirement above should be located in the description of
the object which it refers to, i.e. it should be moved to the
DESCRIPTION clause of the pktcSigDevToneWholeToneRepeatCount object.

2. The requirement above is not speific on what particulary it means
"MUST be ignored on SNMP get/set operations". Does this mean that all
SNMP GET/SET must be dropped as ifi they did not exist ? Does this mean
that MTA must return "success" of the SNMP operation without actually
doing anything ? 

To address these concerns the following is proposed:

1. Change the DESCRIPTION of the pktcSigDevToneTable:

           " The Tone Table defines the various tone operations. Any 
             definition of the tones callWaiting1-4 in this table 
             should just contain the audible tone itself and NOT 
             contain the delay between tones or the tone repeat count. 
             The delay between tones or the repeat count is controlled 
             by the objects pktcNcsEndPntConfigCallWaitingDelay, and 
             pktcNcsEndPntConfigCallWaitingMaxRep. The MTA MUST 
             make sure that, after the provisioning cycle, the table is 
             fully populated (i.e., for each possible index, an entry 
             MUST be defined) using reasonable defaults for each row 
             that was not defined by the provisioning information. 
             Objects in this table do not persist across MTA reboots."  

2. Change the DESCRIPTION of the pktcSigDevToneWholeToneRepeatCount:

           "This is the repeat count, which signifies how many times 
            to repeat the entire on-off sequence. Setting this object 
            may result in a tone duration longer or shorter than the 
            overall signal duration specified by the time out (TO) 
            object for a particular signal. If the repeat count results 
            in a longer tone duration than the signal duration 
            specified by the TO, the tone duration defined 
            by the TO object for a particular signal always represents 
            the overall signal duration for a tone. In this case, the 
            tone duration repeat count will not be fully exercised and 
            the desired tone duration will be truncated per the TO 
            setting. If the repeat count results in a shorter tone 
            duration than the signal duration specified by the TO, the 
            tone duration defined by the repeat count takes precedence 
            over the TO and will end the signal event. In this case, 
            the TO represents a time not to be exceeded for the signal. 
            It is recommended to ensure proper telephony signaling that 
            The TO duration setting should always be longer than the 
            desired repeat count time duration.
            
            If the pktcSigDevToneType is set to either of the values 
            callWaiting1, .. callWaiting4, the 
            the MTA MUST return "noSuchInstance" for all SNMP SET/GET 
            operations on pktcSigDevToneWholeToneRepeatCount object."  


Eugene.


_______________________________________________
IPCDN mailing list
IPCDN at ietf.org
https://www1.ietf.org/mailman/listinfo/ipcdn