Subject: [ipcdn] Email from Sumanth C, editor of draft-ipcdn-pktc-signaling-08: final changes(?)

From: "Jean-Francois Mule" <[email-masked]>
Date: Mon, 5 Sep 2005 07:57:30 -0600

Folks,

   As you know, this ID is now expired and we have a good to complete the wg milestone by October.

   Below is an email from Sumanth sent at Wednesday, August 31, 2005 11:30 PM US Mountain Time summarizing the changes (per my email from 8/26). The original email included a preliminary version of draft09 (I removed it per IETF practice).

  Please review and provide any comments to Sumanth and the ipcdn list by Friday September 9, 9am ET. 

Thanks,

Jean-François 

IPCDN co-chair

  _____  

From: Sumanth Channabasappa 
Sent: Wednesday, August 31, 2005 11:30 PM
To: [email-masked]
Subject: draft-ipcdn-pktc-signaling-08, final changes(?)

Folks,

Find enclosed a compilation of all the changes since the last draft as well as the actual MIB as an attachment. For those interested only in the changes made, please check the table (I have also included snippets of the MIB towards the end).

Please let me know if I have missed anything.

regards

Sumanth

Change

Reason

Renamed 'pktcSigDevToneFrequencyNumber' as 'pktcSigDevToneNumber'

   As per discussion on July 6, 2005

Renamed 'pktcSigDevToneFreqSecCompMode' as 'pktcSigDevToneFreqMode'

As per discussion on July 6, 2005

Renamed 'pktcSigDevToneFreqSecCompPrtg' as 'pktcSigDevToneFreqAmpModePrtg'

As per discussion on July 6, 2005

Deleted 'pktcNcsEndPntConfigTxGain' and 'pktcNcsEndPntConfigRxGain'

As per discussion on July 6, 2005

Modified Description of 'pktcSigDevToneDbLevel'

As per discussion on July 6, 2005

(Phillip proposed new text for this MIB Object)

'pktcSigDevToneNumber' -> changed the cardinality from 5..16 to 1..8

As per discussion on July 6. 2005

Moved 'pktcSigDevToneType' to the Tone Table

   MIB doctor suggestion

Removed  'pktcSigDevToneNumFrequencies' 

   As per discussion on July 6, 2005

Recommendation: 'pktcSigDevToneNumber' was recommended to be made 'not-accessible'

Done

Entries in the 'MultiFreqTable' were recommended to be made 'read-only'

Done

For all frequencies in the 'MultiFreqTable', the recommendation was to add a clarification to indicate that a value of '0' implied 'absence of the frequency'.

Done

Moved    

"pktcSigDevToneDbLevel" from SigDevToneTable to MultiFreqTable

Phillip's email on 8/9 and corresponding call

Change to the range for the MIB Object' pktcNcsEndPntConfigMaxHookFlash' 

As per Eugene's email on 8/30

Snippets of the MIB:

<snip>

pktcSigDevToneTable    OBJECT-TYPE 

<..>

    ::= { pktcSigDevConfigObjects 32 } 

pktcSigDevToneEntry    OBJECT-TYPE 

    SYNTAX       PktcSigDevToneEntry 

    MAX-ACCESS   not-accessible 

    STATUS       current 

    DESCRIPTION 

        " The different tone types that can be provisioned based on

          country specific needs.

          Each entry contains the tone generation parameters for 

          a specific Tone Type. The different parameters can be 

          provisioned by the MTA configuration file based on 

          country specific needs. An MTA MUST populate all entries 

          of this table for each tone type."

    INDEX { pktcSigDevToneType } 

    ::= { pktcSigDevToneTable 1 } 

PktcSigDevToneEntry ::= SEQUENCE { 

    pktcSigDevToneType                      INTEGER,

    pktcSigDevToneWholeToneRepeatCount      Unsigned32, 

    pktcSigDevToneSteady                    TruthValue 

    } 

pktcSigDevToneType        OBJECT-TYPE  

<..>

    ::= { pktcSigDevToneEntry 1 }  

pktcSigDevToneWholeToneRepeatCount      OBJECT-TYPE 

<..>

    ::={ pktcSigDevToneEntry 2 } 

pktcSigDevToneSteady    OBJECT-TYPE 

<..>

    ::={ pktcSigDevToneEntry 3 } 

 

<snip>

 

pktcSigDevMultiFreqToneTable    OBJECT-TYPE  

<..>

REFERENCE  

     ::= { pktcSigDevConfigObjects 35 }  

pktcSigDevMultiFreqToneEntry    OBJECT-TYPE  

<..>

INDEX { pktcSigDevToneType, pktcSigDevToneNumber}  

       ::= { pktcSigDevMultiFreqToneTable 1 }  

PktcSigDevMultiFreqToneEntry ::= SEQUENCE {

         pktcSigDevToneNumber                    Unsigned32,

         pktcSigDevToneFirstFreqValue            Unsigned32,

         pktcSigDevToneSecondFreqValue           Unsigned32,

         pktcSigDevToneThirdFreqValue            Unsigned32,

         pktcSigDevToneFourthFreqValue           Unsigned32,

         pktcSigDevToneFreqMode                  INTEGER,

         pktcSigDevToneFreqAmpModePrtg           Integer32,

         pktcSigDevToneDbLevel                   TenthdBm,

         pktcSigDevToneFreqOnDuration            Unsigned32,

         pktcSigDevToneFreqOffDuration           Unsigned32,

         pktcSigDevToneFreqRepeatCount           Unsigned32

   }

   pktcSigDevToneNumber OBJECT-TYPE  

   <..>

   ::={ pktcSigDevMultiFreqToneEntry 1}  

   pktcSigDevToneFirstFreqValue    OBJECT-TYPE  

   <..>

   ::={ pktcSigDevMultiFreqToneEntry 2}  

   pktcSigDevToneSecondFreqValue    OBJECT-TYPE  

   <..>

   ::={ pktcSigDevMultiFreqToneEntry 3}  

   pktcSigDevToneThirdFreqValue    OBJECT-TYPE  

   <..>

   ::={ pktcSigDevMultiFreqToneEntry 4}  

   pktcSigDevToneFourthFreqValue    OBJECT-TYPE  

   <..>

   ::={ pktcSigDevMultiFreqToneEntry 5}  

   pktcSigDevToneFreqMode OBJECT-TYPE  

       SYNTAX       INTEGER {

                     firstModulatedBySecond (1),

                     summation (2)

                    }

       MAX-ACCESS   read-write  

       STATUS       current  

       DESCRIPTION  

       "This MIB Object describes the way in which the

        frequencies comprising a tone need to be applied.

        It is to be noted that while summation can

        be done without any constraint on the number

        of frequencies, the modulation (amplitude)

        holds good only on two frequencies

        (first and second).

        Thus:

          - If the mode is set to a value of  

            firstModulatedBySecond (1), the first frequency

            MUST be modulated by the second and the remaining

            frequencies (third and fourth) ignored. The 

            percentage of amplitude modulation to be applied

            is defined by the MIB Object 

            'pktcSigDevToneFreqAmpModePrtg'.

          - If the mode is set to a value of 

            summation (2), all the frequencies MUST be

            summed, without any modulation

       "

       ::={ pktcSigDevMultiFreqToneEntry 6}  

  pktcSigDevToneFreqAmpModePrtg OBJECT-TYPE  

       SYNTAX       Integer32(0..100)

       MAX-ACCESS   read-write  

       STATUS       current  

       DESCRIPTION  

          "This MIB Object represents the percentage of amplitude

           modulation applied to the second frequency 

           when the MIB Object 'pktcSigDevToneFreqMode' is

           set to a value of 'firstModulatedBySecond (2)'.

           If the MIB Object 'pktcSigDevToneFreqMode' is set to 

           value of 'summation (2)' then this MIB Object MUST be

           ignored."

       ::={ pktcSigDevMultiFreqToneEntry 7}  

   pktcSigDevToneDbLevel    OBJECT-TYPE

    SYNTAX       TenthdBm (-250..-30)

    UNITS        "dBm" 

    MAX-ACCESS   read-only 

    STATUS       current 

    DESCRIPTION 

             "This MIB Object contains the decibel level for each            

             analog signal (tone) that is locally generated  

             (versus in band supervisory tones) and sourced to  

             the a-b terminals (TE connection point). Each tone  

             in itself may consist of multiple frequencies as  

             defined by the MIB table 'pktcSigDevMultiFreqToneTable'.

             This MIB Object MUST reflect the desired level at  

             the Telco (POTS) a-b (T/R) terminals including the  

             affect of any MTA receiver gain (loss).  This is required 

             so that locally generated tones are consistent with 

             remotely generated in band tones at the a-b terminals, 

             consistent with user expectations.

             This MIB Object must  be set for each tone.  

             When tones are formed by combining multi-frequencies, 

             the level of each frequency shall be set so as to result 

             in the tone level specified in this object at the a-b 

             (T/R) terminals.

             The wide range of levels for this Object is required  

             to provide signal generator levels across the wide  

             range of gains (loss) - but does not imply the entire 

             range is to be achievable given the range of gains (loss) 

             in the MTA."

    DEFVAL { -40 } 

    ::={ pktcSigDevMultiFreqToneEntry 8}

   pktcSigDevToneFreqOnDuration                     OBJECT-TYPE  

       SYNTAX       Unsigned32(0..5000)

       MAX-ACCESS   read-only  

       STATUS       current  

       DESCRIPTION  

          "This MIB Object represents the duration for which the

           frequency reference corresponding to the tone type

           is turned on."  

       ::={ pktcSigDevMultiFreqToneEntry 9}  

   pktcSigDevToneFreqOffDuration                     OBJECT-TYPE  

       SYNTAX       Unsigned32(0..5000)

       MAX-ACCESS   read-only  

       STATUS       current  

       DESCRIPTION  

          "This MIB Object represents the duration for which the

           frequency reference corresponding to the tone type

           is turned off."  

       ::={ pktcSigDevMultiFreqToneEntry 10}  

   pktcSigDevToneFreqRepeatCount             OBJECT-TYPE  

       SYNTAX       Unsigned32(0..5000) 

       MAX-ACCESS   read-only  

       STATUS       current  

       DESCRIPTION  

       "This MIB Object indicates the number of times

       to repeat the cadence cycle represented by the 

       on/off durations (refer to the MIB Objects 

       pktcSigDevToneFreqOnDuration and 

       pktcSigDevToneFreqOffDuration). 

       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 the 

       corresponding tone type. If the value of this MIB

       Object indicates a longer duration than the 

       specified by the TO, the latter overrules the former

       and the desired tone duration will be truncated according

       to the TO.

       However, 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. A value of zero

       means the tone sequence is to be played once but not

       repeated."

       ::={ pktcSigDevMultiFreqToneEntry 11}  

<snip>

   pktcNcsEndPntConfigMaxHookFlash    OBJECT-TYPE  

       SYNTAX       Unsigned32 (20..1550)  

       UNITS        "Milliseconds"  

       MAX-ACCESS   read-only  

       STATUS       current  

       DESCRIPTION  

           " This is the maximum time a line needs to be on hook for a 

             valid hook flash. The value of 

             pktcNcsEndPntConfigMaxHookFlash MUST be greater than 

             pktcNcsEndPntConfigMinHookFlash. This object MUST only be 

             set via the configuration file during the provisioning 

             process." 

       DEFVAL { 800 }  

       ::= { pktcNcsEndPntConfigEntry 33 }   

_______________________________________________
IPCDN mailing list
[email-masked]
https://www1.ietf.org/mailman/listinfo/ipcdn