draft-ietf-ipcdn-pktc-signaling-11.txt   draft-ietf-ipcdn-pktc-signaling-12.txt 
INTERNET-DRAFT Gordon Beacham INTERNET-DRAFT Gordon Beacham
Motorola, Inc. Motorola, Inc.
draft-ietf-ipcdn-pktc-signaling-11.txt Satish Kumar draft-ietf-ipcdn-pktc-signaling-12.txt Satish Kumar
Texas Instruments Texas Instruments
Sumanth Channabasappa Sumanth Channabasappa
CableLabs(R) CableLabs(R)
Network-Based Call Signaling (NCS) Signaling MIB for PacketCable and Expires: April 2007 October 2006
Network-Based Call Signaling (NCS) MIB for PacketCable and
IPCablecom Multimedia Terminal Adapters (MTAs) IPCablecom Multimedia Terminal Adapters (MTAs)
Status of this Memo Status of this Memo
By submitting this Internet-Draft, each author represents that any By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware applicable patent or other IPR claims of which he or she is aware
have been or will be disclosed, and any of which he or she becomes have been or will be disclosed, and any of which he or she becomes
aware will be disclosed, in accordance with Section 6 of BCP 79. aware will be disclosed, in accordance with Section 6 of BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
skipping to change at page 1, line 43 skipping to change at page 2, line 5
http://www.ietf.org/shadow.html http://www.ietf.org/shadow.html
Abstract Abstract
This memo defines a portion of the Management Information Base (MIB) This memo defines a portion of the Management Information Base (MIB)
for use with network management protocols in the Internet community. for use with network management protocols in the Internet community.
In particular, it provides a common data and format representation In particular, it provides a common data and format representation
for PacketCable and IPCablecom compliant Multimedia Terminal Adapter for PacketCable and IPCablecom compliant Multimedia Terminal Adapter
devices. devices.
This memo specifies a MIB module in a manner that is compliant to
the SNMP SMIv2. The set of objects are consistent with the SNMP
framework and existing SNMP standards.
Table of Contents Table of Contents
1. The Internet-Standard Management Framework....................2 1. The Internet-Standard Management Framework....................2
2. Introduction..................................................2 2. Introduction..................................................2
3. Terminology...................................................3 3. Terminology...................................................3
3.1 MTA.......................................................3 3.1 MTA.......................................................3
3.2 Endpoint..................................................3 3.2 Endpoint..................................................3
3.3 L Line Package............................................3 3.3 L Line Package............................................3
3.4 E Line Package............................................4 3.4 E Line Package............................................4
4. Overview......................................................4 4. Overview......................................................4
4.1 Structure of the MIB......................................4 4.1 Structure of the MIB......................................4
4.2 pktcSigDevConfigObjects...................................5 4.2 pktcSigDevConfigObjects...................................5
skipping to change at page 2, line 14 skipping to change at page 2, line 17
1. The Internet-Standard Management Framework....................2 1. The Internet-Standard Management Framework....................2
2. Introduction..................................................2 2. Introduction..................................................2
3. Terminology...................................................3 3. Terminology...................................................3
3.1 MTA.......................................................3 3.1 MTA.......................................................3
3.2 Endpoint..................................................3 3.2 Endpoint..................................................3
3.3 L Line Package............................................3 3.3 L Line Package............................................3
3.4 E Line Package............................................4 3.4 E Line Package............................................4
4. Overview......................................................4 4. Overview......................................................4
4.1 Structure of the MIB......................................4 4.1 Structure of the MIB......................................4
4.2 pktcSigDevConfigObjects...................................5 4.2 pktcSigDevConfigObjects...................................5
4.3 pktcSigNotification.......................................8 4.3 pktcSigConformance........................................8
4.4 pktcSigConformance........................................8 5. Definitions...................................................9
5. Definitions...................................................8 6. Examples.....................................................65
6. Examples.....................................................63 7. Acknowledgments..............................................67
7. Acknowledgments..............................................65 8. Security Considerations......................................68
8. Security Considerations......................................65 9. IANA Considerations..........................................70
9. IANA Considerations..........................................67 10. Normative References........................................70
10. Normative References........................................67 11. Informative References......................................71
11. Informative References......................................69 Authors' Addresses..............................................72
Authors' Addresses..............................................70 Disclaimer of validity..........................................73
Disclaimer of validity..........................................71 Full Copyright Statement........................................74
Full Copyright Statement........................................71
1. The Internet-Standard Management Framework 1. The Internet-Standard Management Framework
For a detailed overview of the documents that describe the current For a detailed overview of the documents that describe the current
Internet-Standard Management Framework, please refer to section 7 of Internet-Standard Management Framework, please refer to section 7 of
RFC 3410 [RFC3410]. RFC 3410 [RFC3410].
Managed objects are accessed via a virtual information store, termed Managed objects are accessed via a virtual information store, termed
the Management Information Base or MIB. MIB objects are generally the Management Information Base or MIB. MIB objects are generally
accessed through the Simple Network Management Protocol (SNMP). accessed through the Simple Network Management Protocol (SNMP).
skipping to change at page 4, line 33 skipping to change at page 4, line 33
- the PacketCable 1.0 Signaling MIB Specification - the PacketCable 1.0 Signaling MIB Specification
[PKT-SP-MIB-SIG-1.0], [PKT-SP-MIB-SIG-1.0],
- the PacketCable 1.5 Signaling MIB Specification - the PacketCable 1.5 Signaling MIB Specification
[PKT-SP-MIB-SIG-1.5], [PKT-SP-MIB-SIG-1.5],
- the ITU-T IPCablecom SIG MIB requirements [ITU-T-J169], - the ITU-T IPCablecom SIG MIB requirements [ITU-T-J169],
- the ETSI SIG MIB [ETSI-TS-101-909-9]. The ETSI SIG MIB - the ETSI SIG MIB [ETSI-TS-101-909-9]. The ETSI SIG MIB
requirements also refer to various signal characteristics requirements also refer to various signal characteristics
defined in [ETSI-EN-300-001], [ETSI-EN-300-659-1], and defined in [ETSI-EN-300-001], [ETSI-EN-300-659-1], and
[ETSI-TR-101-183]. [ETSI-TR-101-183].
Several normative and informative references are used to help define Several normative and informative references are used to help define
NCS Signaling MIB objects. As a convention, wherever PacketCable and NCS MIB objects. As a convention, wherever PacketCable and
IPCablecom requirements are equivalent, the PacketCable reference is IPCablecom requirements are equivalent, the PacketCable reference is
used in the object REFERENCE clause. IPCablecom compliant MTA used in the object REFERENCE clause. IPCablecom compliant MTA
devices MUST use the equivalent IPCablecom references. devices MUST use the equivalent IPCablecom references.
This MIB module describes the various Signaling MIB objects that are This MIB module describes the various Signaling MIB objects that are
directly related to the PacketCable MTA and the endpoints supported directly related to the PacketCable MTA and the endpoints supported
on the MTA, each of which provides services independently. The on the MTA, each of which provides services independently. The
recognition and distinction of the endpoints is made by utilizing recognition and distinction of the endpoints is made by utilizing
the ifTable (IF-MIB), where each index (ifIndex) refers to a unique the ifTable (IF-MIB), where each index (ifIndex) refers to a unique
endpoint. This MIB module also utilizes the syntax definition of the endpoint. This MIB module also utilizes the syntax definition of the
Differentiated Services Code Point (DSCP) from DIFFSERV-DSCP-TC Differentiated Services Code Point (DSCP) from DIFFSERV-DSCP-TC
[RFC3289] for signaling MIB objects to allow for differentiation [RFC3289] for defining MIB objects that allow for differentiation
between various types of traffic in the service provider network. between various types of traffic in the service provider network.
This MIB module also utilizes SNMP management MIB architecture from
SNMP-FRAMEWORK-MIB [RFC3411].
4.1 Structure of the MIB 4.1 Structure of the MIB
This MIB is structured in three groups: This MIB is structured in three groups:
- Signaling information that control device and endpoint - Signaling information that control device and endpoint
configuration objects (pktcSigMibObjects) configuration objects (pktcSigMibObjects)
- Signaling Notification object, that notifies the status - Signaling Notification object, that notifies the status
(pktcSigNotification) (pktcSigNotification)
- Signaling Conformance has mandatory signaling objects - Signaling Conformance has mandatory signaling objects
(pktcSigConformance) (pktcSigConformance)
skipping to change at page 8, line 16 skipping to change at page 8, line 16
defined by local requirements. defined by local requirements.
pktcNcsEndPntConfigTable - this table describes the PacketCable NCS pktcNcsEndPntConfigTable - this table describes the PacketCable NCS
endPoint configuration. The number of entries in this table endPoint configuration. The number of entries in this table
represents the number of provisioned endpoints. represents the number of provisioned endpoints.
pktcSigEndPntConfigTable - this table describes the PacketCable pktcSigEndPntConfigTable - this table describes the PacketCable
endPoint selected signaling type. The number of entries in this endPoint selected signaling type. The number of entries in this
table represents the number of provisioned endpoints. table represents the number of provisioned endpoints.
4.3 pktcSigNotification 4.3 pktcSigConformance
pktcSigNotification - this object is used for signaling notification
and reserved for future use.
4.4 pktcSigConformance
pktcSigCompliances - this table has one object that has compliance pktcSigCompliances - this table has one object that has compliance
statements for devices that implement Signaling on the MTA. statements for devices that implement Signaling on the MTA.
pktcSigGroups - this table contains group of objects for the common pktcSigGroups - this table contains group of objects for the common
portion of the PacketCable NCS and Signaling MIB. portion of the PacketCable NCS and Signaling MIB.
pktcInternationalGroup - this table extends this MIB Module by pktcInternationalGroup - this table extends this MIB Module by
establishing a set of objects designed to support operations over establishing a set of objects designed to support operations over
the widest possible range of markets. the widest possible range of markets.
skipping to change at page 9, line 13 skipping to change at page 9, line 35
MODULE-COMPLIANCE MODULE-COMPLIANCE
FROM SNMPv2-CONF -- [RFC2580] FROM SNMPv2-CONF -- [RFC2580]
SnmpAdminString SnmpAdminString
FROM SNMP-FRAMEWORK-MIB -- [RFC3411] FROM SNMP-FRAMEWORK-MIB -- [RFC3411]
ifIndex ifIndex
FROM IF-MIB -- [RFC2863] FROM IF-MIB -- [RFC2863]
Dscp Dscp
FROM DIFFSERV-DSCP-TC; -- [RFC3289] FROM DIFFSERV-DSCP-TC; -- [RFC3289]
pktcIetfSigMib MODULE-IDENTITY pktcIetfSigMib MODULE-IDENTITY
LAST-UPDATED "200606100000Z" -- June 10, 2006 LAST-UPDATED "200610220000Z" -- October 22, 2006
ORGANIZATION "IETF IPCDN Working Group" ORGANIZATION "IETF IPCDN Working Group"
CONTACT-INFO CONTACT-INFO
"Sumanth Channabasappa "Sumanth Channabasappa
Cable Television Laboratories, Inc. Cable Television Laboratories, Inc.
858 Coal Creek Circle, 858 Coal Creek Circle,
Louisville, CO 80027, USA Louisville, CO 80027, USA
Phone: +1 303-661-3307 Phone: +1 303-661-3307
Email: Sumanth@cablelabs.com Email: Sumanth@cablelabs.com
Gordon Beacham Gordon Beacham
skipping to change at page 10, line 8 skipping to change at page 10, line 30
object for the PacketCable and IPCablecom Signaling object for the PacketCable and IPCablecom Signaling
protocols. This version of the MIB includes protocols. This version of the MIB includes
common signaling and Network Call Signaling common signaling and Network Call Signaling
(NCS) related signaling objects. (NCS) related signaling objects.
Copyright (C) The Internet Society (2006). This version of Copyright (C) The Internet Society (2006). This version of
this MIB module is part of RFC yyyy; see the RFC itself for this MIB module is part of RFC yyyy; see the RFC itself for
full legal notices." full legal notices."
-- RFC Ed: replace yyyy with actual RFC number and remove this note -- RFC Ed: replace yyyy with actual RFC number and remove this note
REVISION "200606100000Z" REVISION "200610220000Z"
DESCRIPTION DESCRIPTION
"Initial version, published as RFC yyyy." "Initial version, published as RFC yyyy."
-- RFC Ed: replace yyyy with actual RFC number and remove this note -- RFC Ed: replace yyyy with actual RFC number and remove this note
::= { mib-2 XXX } ::= { mib-2 XXX }
-- RFC Ed: replace XXX with IANA-assigned number and remove this -- RFC Ed: replace XXX with IANA-assigned number and remove this
-- note -- note
-- Textual Conventions -- Textual Conventions
skipping to change at page 12, line 28 skipping to change at page 13, line 4
The third of the reserved octets indicates 'repeatability' The third of the reserved octets indicates 'repeatability'
and MUST be either 0x80 or 0x00 - the former value and MUST be either 0x80 or 0x00 - the former value
indicating 'non-repeatability' and the latter indicating indicating 'non-repeatability' and the latter indicating
'repeatability'. 'repeatability'.
The MTA MUST reject attempts to set a value that violates The MTA MUST reject attempts to set a value that violates
any of the above requirements" any of the above requirements"
SYNTAX OCTET STRING (SIZE(4..36)) SYNTAX OCTET STRING (SIZE(4..36))
PktcSigType ::= TEXTUAL-CONVENTION PktcSigType ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
" This object lists the various types of signaling that may " This object lists the various types of signaling that may
be supported: be supported:
other - set when signaling other than ncs is used other(1) - set when signaling other than NCS is used
reserved - for future use ncs(2) - Network call signaling is a derivation of MGCP
ncs - Network call signaling is a derivation of MGCP
(Media Gateway Control Protocol) defined for (Media Gateway Control Protocol) defined for
IPCablecom/PacketCable MTAs." IPCablecom/PacketCable MTAs."
SYNTAX INTEGER { SYNTAX INTEGER {
other(1), other(1),
reserved(2), ncs(2)
ncs(3)
} }
DtmfCode::=TEXTUAL-CONVENTION DtmfCode::=TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This textual convention represents the DTMF Character used "This textual convention represents the DTMF Character used
to indicate the start or end of the digit transition to indicate the start or end of the digit transition
sequence used for Caller ID or VMWI. sequence used for Caller ID or VMWI.
Note: The DTMF code '*' is indicated using 'dtmfcodeStar' Note: The DTMF code '*' is indicated using 'dtmfcodeStar'
and the DTMF code '#' is indicated using ' dtmfcodeHash'." and the DTMF code '#' is indicated using ' dtmfcodeHash'."
skipping to change at page 16, line 8 skipping to change at page 16, line 28
" This object specifies if the device is capable of echo " This object specifies if the device is capable of echo
cancellation." cancellation."
::= { pktcSigDevConfigObjects 2 } ::= { pktcSigDevConfigObjects 2 }
pktcSigDevSilenceSuppression OBJECT-TYPE pktcSigDevSilenceSuppression OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
" This object specifies if the device is capable of " This object specifies if the device is capable of
silence suppression (Voice Activity Detection)." silence suppression (as a result of Voice Activity
Detection)."
::= { pktcSigDevConfigObjects 3 } ::= { pktcSigDevConfigObjects 3 }
pktcSigDevCidSigProtocol OBJECT-TYPE pktcSigDevCidSigProtocol OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
fsk (1), fsk (1),
dtmf (2) dtmf (2)
} }
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object identifies the subscriber line protocol used "This object is used to configure the subscriber line
for signaling on-hook caller id information. Different protocol used for signaling on-hook caller id information.
countries define different caller id signaling protocols to Different countries define different caller id signaling
support caller identification. Frequency shift keying (FSK) protocols to support caller identification.
is most commonly used. Dual tone multi-frequency (DTMF)
is an alternative." Setting this object at a value fsk(1) sets the subscriber
line protocol to be Frequency Shift Keying (FSK).
Setting this object at a value dtmf(2) sets the subscriber
line protocol to be Dual tone multi-frequency (DTMF)."
REFERENCE REFERENCE
"ETSI-EN-300-659-1 Specification" "ETSI-EN-300-659-1 Specification"
DEFVAL { fsk } DEFVAL { fsk }
::= { pktcSigDevConfigObjects 4 } ::= { pktcSigDevConfigObjects 4 }
pktcSigDevR0Cadence OBJECT-TYPE pktcSigDevR0Cadence OBJECT-TYPE
SYNTAX PktcRingCadence SYNTAX PktcRingCadence
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
skipping to change at page 20, line 23 skipping to change at page 20, line 48
" Provides the version of the signaling type - reference " Provides the version of the signaling type - reference
pktcSignalingType. Examples would be 1.0 or 2.33 etc." pktcSignalingType. Examples would be 1.0 or 2.33 etc."
::= { pktcSigCapabilityEntry 3 } ::= { pktcSigCapabilityEntry 3 }
pktcSignalingVendorExtension OBJECT-TYPE pktcSignalingVendorExtension OBJECT-TYPE
SYNTAX SnmpAdminString SYNTAX SnmpAdminString
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
" The vendor extension allows vendors to provide a list of " The vendor extension allows vendors to provide a list of
additional capabilities, vendors can decide how to encode additional capabilities.
these extensions, although space separated text is
suggested." The syntax for this MIB Object in ABNF ([RFC4234]) is
specified to be zero or more occurrences of vendor
extensions, as follows:
pktcSignalingVendorExtension =
*['X' ('-'/'+') 1*6(ALPHA / DIGIT) ';']
"
::= { pktcSigCapabilityEntry 4 } ::= { pktcSigCapabilityEntry 4 }
pktcSigDefNcsReceiveUdpPort OBJECT-TYPE pktcSigDefNcsReceiveUdpPort OBJECT-TYPE
SYNTAX InetPortNumber (1025..65535) SYNTAX InetPortNumber (1025..65535)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
" This object contains the MTA User Datagram Protocol (UDP) " This object contains the MTA User Datagram Protocol (UDP)
receive port that is being used for NCS call signaling. receive port that is being used for NCS call signaling.
This object should only be changed by the configuration This object should only be changed by the configuration
file." file.
Unless changed via configuration this MIB Object MUST
reflect a value of '2427'.
"
REFERENCE REFERENCE
"PacketCable NCS Specification" "PacketCable NCS Specification"
DEFVAL { 2427 }
::= { pktcSigDevConfigObjects 18 } ::= { pktcSigDevConfigObjects 18 }
pktcSigPowerRingFrequency OBJECT-TYPE pktcSigPowerRingFrequency OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
f20Hz(1), f20Hz(1),
f25Hz(2), f25Hz(2),
f33Point33Hz(3), f33Point33Hz(3),
f50Hz(4), f50Hz(4),
f15Hz(5), f15Hz(5),
f16Hz(6), f16Hz(6),
skipping to change at page 21, line 27 skipping to change at page 22, line 10
of 20 Hertz. The f25Hz setting corresponds to a power ring of 20 Hertz. The f25Hz setting corresponds to a power ring
frequency of 25 Hertz. The f33Point33Hz setting frequency of 25 Hertz. The f33Point33Hz setting
corresponds to a power ring frequency of 33.33 Hertz. The corresponds to a power ring frequency of 33.33 Hertz. The
f50Hz setting corresponds to a power ring frequency of 50 f50Hz setting corresponds to a power ring frequency of 50
Hertz. The f15Hz setting corresponds to a power ring Hertz. The f15Hz setting corresponds to a power ring
frequency of 15 Hertz. The f16Hz setting corresponds to a frequency of 15 Hertz. The f16Hz setting corresponds to a
power ring frequency of 16 Hertz. The f22Hz setting power ring frequency of 16 Hertz. The f22Hz setting
corresponds to a power ring frequency of 22 Hertz. The corresponds to a power ring frequency of 22 Hertz. The
f23Hz setting corresponds to a power ring frequency of 23 f23Hz setting corresponds to a power ring frequency of 23
Hertz. The f45Hz setting corresponds to a power ring Hertz. The f45Hz setting corresponds to a power ring
frequency of 45 Hertz." frequency of 45 Hertz.
Unless changed via configuration this MIB Object MUST
reflect a value of '2427'."
REFERENCE REFERENCE
"ETSI-EN-300-001 contains a list of frequency ranges "ETSI-EN-300-001 contains a list of frequency ranges
that are defined for each country." that are defined for each country."
DEFVAL { f20Hz }
::= { pktcSigDevConfigObjects 19 } ::= { pktcSigDevConfigObjects 19 }
pktcSigPulseSignalTable OBJECT-TYPE pktcSigPulseSignalTable OBJECT-TYPE
SYNTAX SEQUENCE OF PktcSigPulseSignalEntry SYNTAX SEQUENCE OF PktcSigPulseSignalEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
" The Pulse signal table defines the pulse signal operation. " The Pulse signal table defines the pulse signal operation.
There are nine types of international pulse signals, There are nine types of international pulse signals,
with each signal having a set of provisionable parameters. with each signal having a set of provisionable parameters.
skipping to change at page 33, line 51 skipping to change at page 34, line 36
DESCRIPTION DESCRIPTION
"This is the Ring Cadence. This object is required for the "This is the Ring Cadence. This object is required for the
E line package." E line package."
::= { pktcSigDevRingCadenceEntry 2 } ::= { pktcSigDevRingCadenceEntry 2 }
pktcSigDevToneTable OBJECT-TYPE pktcSigDevToneTable OBJECT-TYPE
SYNTAX SEQUENCE OF PktcSigDevToneEntry SYNTAX SEQUENCE OF PktcSigDevToneEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
" The Tone Table defines the various tone operations. Any " The Tone Table defines the composition of tones and
definition of the tones callWaiting1-4 in this table various tone operations.
Any definition of the tones callWaiting1-4 in this table
should just contain the audible tone itself and NOT should just contain the audible tone itself and NOT
contain the delay between tones or the tone repeat count. contain the delay between tones or the tone repeat count.
The delay between tones or the repeat count is controlled The delay between tones or the repeat count is controlled
by the objects pktcNcsEndPntConfigCallWaitingDelay, and by the objects pktcNcsEndPntConfigCallWaitingDelay, and
pktcNcsEndPntConfigCallWaitingMaxRep. If the pktcNcsEndPntConfigCallWaitingMaxRep. If the
pktcSigDevToneType is set to either of the values pktcSigDevToneType is set to either of the values
callWaiting1, callWaiting2, callWaiting3 or callWaiting4, callWaiting1, callWaiting2, callWaiting3 or callWaiting4,
then the value of the pktcSigDevToneWholeToneRepeatCount then the value of the pktcSigDevToneWholeToneRepeatCount
object has no effect on the tone. The MTA MUST object indicates that the particular frequency group is
make sure that, after the provisioning cycle, the table is applicable, as a repeatable part of the tone, based on the
fully populated (i.e., for each possible index, an entry value of the MIB Object
MUST be defined) using reasonable defaults for each row 'pktcSigDevToneWholeToneRepeatCount'.
that was not defined by the provisioning information
delivered by the MTA Configuration File. 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 delivered via MTA
Configuration.
The frequency composition of each tone is defined by the The frequency composition of each tone is defined by the
pktcSigDevMultiFreqToneTable. For each ToneType defined pktcSigDevMultiFreqToneTable. For each ToneType defined
in pktcSigDevToneTable, the MTA MUST populate at least in pktcSigDevToneTable, the MTA MUST populate at least
one entry in the pktcSigDevMultiFreqToneTable. one entry in the pktcSigDevMultiFreqToneTable.
For each particular value of pktcSigDevToneType, the
pktcSigDevToneTable table can define non-repeating and
repeating groups of the frequencies defined by the
pktcSigDevMultiFreqToneTable, such that each group is
represented by the set of the consecutive rows
(frequency group) in the pktcSigDevMultiFreqToneTable.
Objects in this table do not persist across MTA reboots. Objects in this table do not persist across MTA reboots.
For tones with multiple frequencies refer to the MIB table For tones with multiple frequencies refer to the MIB table
pktcSigDevMultiFreqToneTable." pktcSigDevMultiFreqToneTable."
REFERENCE REFERENCE
"PacketCable NCS Specification, ETSI-TS-101-909-4 "PacketCable NCS Specification, ETSI-TS-101-909-4
Specification." Specification."
::= { pktcSigDevConfigObjects 32 } ::= { pktcSigDevConfigObjects 32 }
pktcSigDevToneEntry OBJECT-TYPE pktcSigDevToneEntry OBJECT-TYPE
SYNTAX PktcSigDevToneEntry SYNTAX PktcSigDevToneEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
" The different tone types that can be provisioned based on " The different tone types that can be provisioned based on
country specific needs. country specific needs.
Each entry contains the tone generation parameters for Each entry contains the tone generation parameters for
a specific Tone Type. The different parameters can be a specific frequency group of the specific Tone Type.
provisioned by the MTA configuration file based on The different parameters can be provisioned via MTA
country specific needs. An MTA MUST populate all entries configuration based on country specific needs.
of this table for each tone type." An MTA MUST populate all entries of this table for each
INDEX { pktcSigDevToneType } tone type."
INDEX { pktcSigDevToneType, pktcSigDevToneFreqGroup }
::= { pktcSigDevToneTable 1 } ::= { pktcSigDevToneTable 1 }
PktcSigDevToneEntry ::= SEQUENCE { PktcSigDevToneEntry ::= SEQUENCE {
pktcSigDevToneType INTEGER, pktcSigDevToneType INTEGER,
pktcSigDevToneFreqGroup Unsigned32,
pktcSigDevToneFreqCounter Unsigned32,
pktcSigDevToneWholeToneRepeatCount Unsigned32, pktcSigDevToneWholeToneRepeatCount Unsigned32,
pktcSigDevToneSteady TruthValue pktcSigDevToneSteady TruthValue
} }
pktcSigDevToneType OBJECT-TYPE pktcSigDevToneType OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
busy(1), busy(1),
confirmation(2), confirmation(2),
dial(3), dial(3),
messageWaiting(4), messageWaiting(4),
offHookWarning(5), offHookWarning(5),
ringBack(6), ringBack(6),
reOrder(7), reOrder(7),
stutterdial(8), stutterdial(8),
skipping to change at page 35, line 41 skipping to change at page 36, line 43
"Unique value that will correspond to the different "Unique value that will correspond to the different
tone types. These tones can be provisioned based on tone types. These tones can be provisioned based on
country specific needs. This object defines the type country specific needs. This object defines the type
of tone being accessed. of tone being accessed.
The alertingSignal, specialDial, specialInfo, release, The alertingSignal, specialDial, specialInfo, release,
congestion, userDefined1, userDefined2, userDefined3 congestion, userDefined1, userDefined2, userDefined3
and userDefined4 tone types are used in and userDefined4 tone types are used in
the E line package." the E line package."
::= { pktcSigDevToneEntry 1 } ::= { pktcSigDevToneEntry 1 }
pktcSigDevToneFreqGroup OBJECT-TYPE
SYNTAX Unsigned32(1..4)
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This MIB Object represents the Tone Sequence reference
of a multi-sequence tone."
::={ pktcSigDevToneEntry 2}
pktcSigDevToneFreqCounter OBJECT-TYPE
SYNTAX Unsigned32(1..8)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This MIB Object represents the number of consecutive
multi-frequency tones for the particular tone type in
the multi-frequency table (pktcSigDevMultiFreqToneTable).
Such a sequence of the consecutive multi-frequency tones
forms the tone group for the particular tone type in the
pktcSigDevToneTable."
::={ pktcSigDevToneEntry 3}
pktcSigDevToneWholeToneRepeatCount OBJECT-TYPE pktcSigDevToneWholeToneRepeatCount OBJECT-TYPE
SYNTAX Unsigned32 (0..5000) SYNTAX Unsigned32 (0..5000)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This is the repeat count, which signifies how many times "This is the repeat count, which signifies how many times
to repeat the entire on-off cadence sequence. Setting this to repeat the entire on-off cadence sequence. Setting this
object may result in a cadence duration longer or shorter object may result in a cadence duration longer or shorter
than the overall signal duration specified by the time out than the overall signal duration specified by the time out
(TO) object for a particular signal. If the repeat count (TO) object for a particular signal. If the repeat count
skipping to change at page 36, line 16 skipping to change at page 37, line 42
tone duration repeat count will not be fully exercised and tone duration repeat count will not be fully exercised and
the desired tone duration will be truncated per the TO the desired tone duration will be truncated per the TO
setting. If the repeat count results in a shorter tone setting. If the repeat count results in a shorter tone
duration than the signal duration specified by the TO, the duration than the signal duration specified by the TO, the
tone duration defined by the repeat count takes precedence tone duration defined by the repeat count takes precedence
over the TO and will end the signal event. In this case, over the TO and will end the signal event. In this case,
the TO represents a time not to be exceeded for the signal. the TO represents a time not to be exceeded for the signal.
It is recommended to ensure proper telephony signaling that It is recommended to ensure proper telephony signaling that
The TO duration setting should always be longer than the The TO duration setting should always be longer than the
desired repeat count time duration." desired repeat count time duration."
::={ pktcSigDevToneEntry 2 } ::={ pktcSigDevToneEntry 4 }
pktcSigDevToneSteady OBJECT-TYPE pktcSigDevToneSteady OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This is the steady tone. Device must play out the on-off "This is the steady tone. Device must play out the on-off
cadence sequence for pktcSigDevToneWholeRepeatCount times cadence sequence for pktcSigDevToneWholeRepeatCount times
and then apply the last tone forever. Setting this object and then apply the last tone forever. Setting this object
may result in a tone duration longer or shorter than the may result in a tone duration longer or shorter than the
skipping to change at page 36, line 43 skipping to change at page 38, line 21
tone duration repeat count will not be fully exercised and tone duration repeat count will not be fully exercised and
the desired tone duration will be truncated per the TO the desired tone duration will be truncated per the TO
setting. If the repeat count results in a shorter tone setting. If the repeat count results in a shorter tone
duration than the signal duration specified by the TO, the duration than the signal duration specified by the TO, the
tone duration defined by the repeat count takes precedence tone duration defined by the repeat count takes precedence
over the TO and will end the signal event. In this case, over the TO and will end the signal event. In this case,
the TO represents a time not to be exceeded for the signal. the TO represents a time not to be exceeded for the signal.
It is recommended to ensure proper telephony signaling that It is recommended to ensure proper telephony signaling that
The TO duration setting should always be longer than the The TO duration setting should always be longer than the
desired repeat count time duration plus the desired maximum desired repeat count time duration plus the desired maximum
steady tone period." steady tone period.
::={ pktcSigDevToneEntry 3 } If pktcSigDevToneTable contains multiple rows with this
Object set to 'true', the steady tone is applied to the
last repeating frequency group of the tone."
::={ pktcSigDevToneEntry 5 }
pktcSigDevMultiFreqToneTable OBJECT-TYPE pktcSigDevMultiFreqToneTable OBJECT-TYPE
SYNTAX SEQUENCE OF PktcSigDevMultiFreqToneEntry SYNTAX SEQUENCE OF PktcSigDevMultiFreqToneEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
" This MIB table defines the characteristics of tones " This MIB table defines the characteristics of tones
with multiple frequencies. The constraints imposed with multiple frequencies. The constraints imposed
on the tones by the MIB table pktcSigDevToneTable on the tones by the MIB table pktcSigDevToneTable
need to be considered for MIB objects in this table need to be considered for MIB objects in this table
as well. as well.
The MTA MUST populate the corresponding row(s) The MTA MUST populate the corresponding row(s)
of the pktcSigDevMultiFreqToneTable for each tone of the pktcSigDevMultiFreqToneTable for each tone
defined in the pktcSigDevToneTable. defined in the pktcSigDevToneTable.
The contents of the table may be provisioned using The contents of the table may be provisioned via
the MTA configuration file." MTA configuration."
REFERENCE REFERENCE
"PacketCable NCS Specification, ETSI-TS-101-909-4 "PacketCable NCS Specification, ETSI-TS-101-909-4
Specification." Specification."
::= { pktcSigDevConfigObjects 33 } ::= { pktcSigDevConfigObjects 33 }
pktcSigDevMultiFreqToneEntry OBJECT-TYPE pktcSigDevMultiFreqToneEntry OBJECT-TYPE
SYNTAX PktcSigDevMultiFreqToneEntry SYNTAX PktcSigDevMultiFreqToneEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
skipping to change at page 39, line 44 skipping to change at page 41, line 25
modulation applied to the second frequency modulation applied to the second frequency
when the MIB Object 'pktcSigDevToneFreqMode' is when the MIB Object 'pktcSigDevToneFreqMode' is
set to a value of 'firstModulatedBySecond (1)'. set to a value of 'firstModulatedBySecond (1)'.
If the MIB Object 'pktcSigDevToneFreqMode' is set to If the MIB Object 'pktcSigDevToneFreqMode' is set to
value of 'summation (2)' then this MIB Object MUST be value of 'summation (2)' then this MIB Object MUST be
ignored." ignored."
::={ pktcSigDevMultiFreqToneEntry 7} ::={ pktcSigDevMultiFreqToneEntry 7}
pktcSigDevToneDbLevel OBJECT-TYPE pktcSigDevToneDbLevel OBJECT-TYPE
SYNTAX TenthdBm (-250..-30) SYNTAX TenthdBm (-250..-110)
UNITS "dBm" UNITS "dBm"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This MIB Object contains the decibel level for each "This MIB Object contains the decibel level for each
analog signal (tone) that is locally generated analog signal (tone) that is locally generated
(versus in band supervisory tones) and sourced to (versus in band supervisory tones) and sourced to
the a-b terminals (TE connection point). Each tone the a-b terminals (TE connection point). Each tone
in itself may consist of multiple frequencies as in itself may consist of multiple frequencies as
defined by the MIB table 'pktcSigDevMultiFreqToneTable'. defined by the MIB table 'pktcSigDevMultiFreqToneTable'.
This MIB Object MUST reflect the desired level at This MIB Object reflects the desired level at
the Telco (POTS) a-b (T/R) terminals including the the Telco (POTS) a-b (T/R) terminals including the
affect of any MTA receiver gain (loss). This is required affect of any MTA receiver gain (loss). This is required
so that locally generated tones are consistent with so that locally generated tones are consistent with
remotely generated in band tones at the a-b terminals, remotely generated in band tones at the a-b terminals,
consistent with user expectations. consistent with user expectations.
This MIB Object must be set for each tone. This MIB Object must be set for each tone.
When tones are formed by combining multi-frequencies, When tones are formed by combining multi-frequencies,
the level of each frequency shall be set so as to result the level of each frequency shall be set so as to result
in the tone level specified in this object at the a-b in the tone level specified in this object at the a-b
(T/R) terminals. (T/R) terminals.
The wide range of levels for this Object is required The wide range of levels for this Object is required
to provide signal generator levels across the wide to provide signal generator levels across the wide
range of gains (loss) - but does not imply the entire range of gains (loss) - but does not imply the entire
range is to be achievable given the range of gains (loss) range is to be achievable given the range of gains (loss)
in the MTA." in the MTA."
DEFVAL { -40 } DEFVAL { -120 }
::={ pktcSigDevMultiFreqToneEntry 8} ::={ pktcSigDevMultiFreqToneEntry 8}
pktcSigDevToneFreqOnDuration OBJECT-TYPE pktcSigDevToneFreqOnDuration OBJECT-TYPE
SYNTAX Unsigned32(0..5000) SYNTAX Unsigned32(0..5000)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This MIB Object represents the duration for which the "This MIB Object represents the duration for which the
frequency reference corresponding to the tone type frequency reference corresponding to the tone type
is turned on." is turned on."
skipping to change at page 46, line 28 skipping to change at page 48, line 9
-- --
pktcNcsEndPntConfigTable OBJECT-TYPE pktcNcsEndPntConfigTable OBJECT-TYPE
SYNTAX SEQUENCE OF PktcNcsEndPntConfigEntry SYNTAX SEQUENCE OF PktcNcsEndPntConfigEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
" This table describes the information pertaining to each " This table describes the information pertaining to each
endpoint of the MTA. All entries in this table represent endpoint of the MTA. All entries in this table represent
the provisioned endpoints provisioned with the information the provisioned endpoints provisioned with the information
required by the MTA to maintain the NCS signaling protocol required by the MTA to maintain the NCS protocol
communication with the CMS. Each endpoint can be assigned communication with the CMS. Each endpoint can be assigned
to its own CMS. If the specific endpoint does not have to its own CMS. If the specific endpoint does not have
the corresponding CMS information in this table, the the corresponding CMS information in this table, the
endpoint is considered as not provisioned with voice endpoint is considered as not provisioned with voice
services. Objects in this table do not persist across services. Objects in this table do not persist across
MTA reboots." MTA reboots."
::= { pktcNcsEndPntConfigObjects 1 } ::= { pktcNcsEndPntConfigObjects 1 }
pktcNcsEndPntConfigEntry OBJECT-TYPE pktcNcsEndPntConfigEntry OBJECT-TYPE
SYNTAX PktcNcsEndPntConfigEntry SYNTAX PktcNcsEndPntConfigEntry
skipping to change at page 48, line 20 skipping to change at page 49, line 50
operation." operation."
::= { pktcNcsEndPntConfigEntry 1 } ::= { pktcNcsEndPntConfigEntry 1 }
pktcNcsEndPntConfigCallAgentUdpPort OBJECT-TYPE pktcNcsEndPntConfigCallAgentUdpPort OBJECT-TYPE
SYNTAX InetPortNumber (1025..65535) SYNTAX InetPortNumber (1025..65535)
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
" This object contains the current value of the User " This object contains the current value of the User
Datagram Protocol (UDP) receive port on which the Datagram Protocol (UDP) receive port on which the
call agent will receive NCS signaling from the endpoint. call agent will receive NCS from the endpoint.
For each particular endpoint, the MTA MUST use the current For each particular endpoint, the MTA MUST use the current
value of this object to communicate with the corresponding value of this object to communicate with the corresponding
CMS. The MTA MUST update this object with the value of the CMS. The MTA MUST update this object with the value of the
'Notified Entity' parameter of the NCS message. If the 'Notified Entity' parameter of the NCS message. If the
Notified Entity parameter does not contain a CallAgent Notified Entity parameter does not contain a CallAgent
port, the MTA MUST update this object with the default port, the MTA MUST update this object with the default
value of 2727. Because of the high importance of this value of 2727. Because of the high importance of this
object to the ability of the MTA to maintain reliable NCS object to the ability of the MTA to maintain reliable NCS
communication with the CMS, it is highly recommended not communication with the CMS, it is highly recommended not
to change this object's value using SNMP during normal to change this object's value using SNMP during normal
skipping to change at page 50, line 9 skipping to change at page 51, line 39
pktcNcsEndPntConfigMessageWaitingTO OBJECT-TYPE pktcNcsEndPntConfigMessageWaitingTO OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
UNITS "seconds" UNITS "seconds"
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
" This object contains the default timeout value for message " This object contains the default timeout value for message
waiting indicator. The MTA MUST NOT update this object waiting indicator. The MTA MUST NOT update this object
with the value provided in the NCS message (if with the value provided in the NCS message (if
present). If the value of the object is modified by the present). If the value of the object is modified by the
SNMP Management Station, the MTA MUST use the new value as SNMP Manager application, the MTA MUST use the new value
a default only for a new signal requested by the NCS as a default only for a new signal requested by the NCS
message." message."
REFERENCE REFERENCE
"PacketCable NCS Specification" "PacketCable NCS Specification"
DEFVAL { 16 } DEFVAL { 16 }
::= { pktcNcsEndPntConfigEntry 7 } ::= { pktcNcsEndPntConfigEntry 7 }
pktcNcsEndPntConfigOffHookWarnToneTO OBJECT-TYPE pktcNcsEndPntConfigOffHookWarnToneTO OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
UNITS "seconds" UNITS "seconds"
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
" This object contains the default timeout value for the off " This object contains the default timeout value for the off
hook Warning tone. The MTA MUST NOT update this object hook Warning tone. The MTA MUST NOT update this object
with the value provided in the NCS message (if with the value provided in the NCS message (if
present). If the value of the object is modified by the present). If the value of the object is modified by the
SNMP Management Station, the MTA MUST use the new value as SNMP Manager application, the MTA MUST use the new value
a default only for a new signal requested by the NCS as a default only for a new signal requested by the NCS
message." message."
REFERENCE REFERENCE
"PacketCable NCS Specification" "PacketCable NCS Specification"
DEFVAL { 0 } DEFVAL { 0 }
::= { pktcNcsEndPntConfigEntry 8 } ::= { pktcNcsEndPntConfigEntry 8 }
pktcNcsEndPntConfigRingingTO OBJECT-TYPE pktcNcsEndPntConfigRingingTO OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
UNITS "seconds" UNITS "seconds"
MAX-ACCESS read-create MAX-ACCESS read-create
skipping to change at page 56, line 31 skipping to change at page 58, line 13
pktcNcsEndPntConfigCallWaitingMaxRep OBJECT-TYPE pktcNcsEndPntConfigCallWaitingMaxRep OBJECT-TYPE
SYNTAX Unsigned32 (0..10) SYNTAX Unsigned32 (0..10)
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
" This object contains the default value of the maximum " This object contains the default value of the maximum
number of repetitions of the call waiting tone that the number of repetitions of the call waiting tone that the
MTA will play from a single CMS request. The MTA MUST NOT MTA will play from a single CMS request. The MTA MUST NOT
update this object with the information provided in the update this object with the information provided in the
NCS message (if present). If the value of the object is NCS message (if present). If the value of the object is
modified by the SNMP Management Station, the MTA MUST use modified by the SNMP Manager application, the MTA MUST use
the new value as a default only for a new signal the new value as a default only for a new signal
requested by the NCS message." requested by the NCS message."
DEFVAL { 1 } DEFVAL { 1 }
::= { pktcNcsEndPntConfigEntry 27 } ::= { pktcNcsEndPntConfigEntry 27 }
pktcNcsEndPntConfigCallWaitingDelay OBJECT-TYPE pktcNcsEndPntConfigCallWaitingDelay OBJECT-TYPE
SYNTAX Unsigned32 (1..100) SYNTAX Unsigned32 (1..100)
UNITS "seconds" UNITS "seconds"
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
skipping to change at page 58, line 16 skipping to change at page 59, line 47
UNITS "Milliseconds" UNITS "Milliseconds"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
" This is the minimum time a line needs to be on hook for a " This is the minimum time a line needs to be on hook for a
valid hook flash. The value of this object MUST be valid hook flash. The value of this object MUST be
greater than the value of greater than the value of
pktcNcsEndPntConfigPulseDialMaxBreakTime. The value of pktcNcsEndPntConfigPulseDialMaxBreakTime. The value of
pktcNcsEndPntConfigMinHookFlash MUST be less than pktcNcsEndPntConfigMinHookFlash MUST be less than
pktcNcsEndPntConfigMaxHookFlash. This object MUST only be pktcNcsEndPntConfigMaxHookFlash. This object MUST only be
set via the configuration file during the provisioning set via the MTA configuration during the provisioning
process. process.
Furthermore, given the possibility for the 'pulse dial' Furthermore, given the possibility for the 'pulse dial'
and 'hook flash' to overlap, the value of this object and 'hook flash' to overlap, the value of this object
MUST be greater than the value contained by the MIB MUST be greater than the value contained by the MIB
Object 'pktcNcsEndPntConfigPulseDialMaxMakeTime'." Object 'pktcNcsEndPntConfigPulseDialMaxMakeTime'."
DEFVAL { 300 } DEFVAL { 300 }
::= { pktcNcsEndPntConfigEntry 32 } ::= { pktcNcsEndPntConfigEntry 32 }
pktcNcsEndPntConfigMaxHookFlash OBJECT-TYPE pktcNcsEndPntConfigMaxHookFlash OBJECT-TYPE
SYNTAX Unsigned32 (20..1550) SYNTAX Unsigned32 (20..1550)
UNITS "Milliseconds" UNITS "Milliseconds"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
" This is the maximum time a line needs to be on hook for a " This is the maximum time a line needs to be on hook for a
valid hook flash. The value of valid hook flash. The value of
pktcNcsEndPntConfigMaxHookFlash MUST be greater than pktcNcsEndPntConfigMaxHookFlash MUST be greater than
pktcNcsEndPntConfigMinHookFlash. This object MUST only be pktcNcsEndPntConfigMinHookFlash. This object MUST only be
set via the configuration file during the provisioning set via the MTA configuration during the provisioning
process." process."
DEFVAL { 800 } DEFVAL { 800 }
::= { pktcNcsEndPntConfigEntry 33 } ::= { pktcNcsEndPntConfigEntry 33 }
pktcNcsEndPntConfigPulseDialInterdigitTime OBJECT-TYPE pktcNcsEndPntConfigPulseDialInterdigitTime OBJECT-TYPE
SYNTAX Unsigned32 (100..1500) SYNTAX Unsigned32 (100..1500)
UNITS "Milliseconds" UNITS "Milliseconds"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
" This is the pulse dial inter-digit timeout. This object " This is the pulse dial inter-digit timeout. This object
MUST only be set via the configuration file during the MUST only be set via the MTA configuration during the
provisioning process." provisioning process."
DEFVAL { 100 } DEFVAL { 100 }
::= { pktcNcsEndPntConfigEntry 34 } ::= { pktcNcsEndPntConfigEntry 34 }
pktcNcsEndPntConfigPulseDialMinMakeTime OBJECT-TYPE pktcNcsEndPntConfigPulseDialMinMakeTime OBJECT-TYPE
SYNTAX Unsigned32 (20..200) SYNTAX Unsigned32 (20..200)
UNITS "Milliseconds" UNITS "Milliseconds"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
" This is the minimum make pulse width for the dial pulse. " This is the minimum make pulse width for the dial pulse.
The value of pktcNcsEndPntConfigPulseDialMinMakeTime MUST The value of pktcNcsEndPntConfigPulseDialMinMakeTime MUST
be less than pktcNcsEndPntConfigPulseDialMaxMakeTime. This be less than pktcNcsEndPntConfigPulseDialMaxMakeTime. This
object MUST only be set via the configuration file during object MUST only be set via the MTA configuration during
the provisioning process." the provisioning process."
DEFVAL { 25 } DEFVAL { 25 }
::= { pktcNcsEndPntConfigEntry 35 } ::= { pktcNcsEndPntConfigEntry 35 }
pktcNcsEndPntConfigPulseDialMaxMakeTime OBJECT-TYPE pktcNcsEndPntConfigPulseDialMaxMakeTime OBJECT-TYPE
SYNTAX Unsigned32 (20..200) SYNTAX Unsigned32 (20..200)
UNITS "Milliseconds" UNITS "Milliseconds"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
skipping to change at page 62, line 30 skipping to change at page 64, line 11
pktcNcsEndPntConfigStatus, pktcNcsEndPntConfigStatus,
pktcNcsEndPntConfigCallWaitingMaxRep, pktcNcsEndPntConfigCallWaitingMaxRep,
pktcNcsEndPntConfigCallWaitingDelay, pktcNcsEndPntConfigCallWaitingDelay,
pktcNcsEndPntStatusCallIpAddressType, pktcNcsEndPntStatusCallIpAddressType,
pktcNcsEndPntStatusCallIpAddress, pktcNcsEndPntStatusCallIpAddress,
pktcNcsEndPntStatusError pktcNcsEndPntStatusError
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Group of objects for the NCS portion of the PacketCable "Group of objects for the NCS portion of the PacketCable
Signaling MIB. This is mandatory for NCS signaling." Signaling MIB. This is mandatory for NCS."
::= { pktcSigGroups 2 } ::= { pktcSigGroups 2 }
pktcInternationalGroup OBJECT-GROUP pktcInternationalGroup OBJECT-GROUP
OBJECTS { OBJECTS {
pktcNcsEndPntConfigMinHookFlash, pktcNcsEndPntConfigMinHookFlash,
pktcNcsEndPntConfigMaxHookFlash, pktcNcsEndPntConfigMaxHookFlash,
pktcNcsEndPntConfigPulseDialInterdigitTime, pktcNcsEndPntConfigPulseDialInterdigitTime,
pktcNcsEndPntConfigPulseDialMinMakeTime, pktcNcsEndPntConfigPulseDialMinMakeTime,
pktcNcsEndPntConfigPulseDialMaxMakeTime, pktcNcsEndPntConfigPulseDialMaxMakeTime,
pktcNcsEndPntConfigPulseDialMinBreakTime, pktcNcsEndPntConfigPulseDialMinBreakTime,
skipping to change at page 63, line 20 skipping to change at page 64, line 50
pktcSigDevVmwiAfterDTAS, pktcSigDevVmwiAfterDTAS,
pktcSigDevVmwiAfterRPAS, pktcSigDevVmwiAfterRPAS,
pktcSigDevVmwiDTASAfterLR, pktcSigDevVmwiDTASAfterLR,
pktcSigPowerRingFrequency, pktcSigPowerRingFrequency,
pktcSigPulseSignalFrequency, pktcSigPulseSignalFrequency,
pktcSigPulseSignalDbLevel, pktcSigPulseSignalDbLevel,
pktcSigPulseSignalDuration, pktcSigPulseSignalDuration,
pktcSigPulseSignalPulseInterval, pktcSigPulseSignalPulseInterval,
pktcSigPulseSignalRepeatCount, pktcSigPulseSignalRepeatCount,
pktcSigDevToneDbLevel, pktcSigDevToneDbLevel,
pktcSigDevToneFreqCounter,
pktcSigDevToneWholeToneRepeatCount, pktcSigDevToneWholeToneRepeatCount,
pktcSigDevToneSteady, pktcSigDevToneSteady,
pktcSigDevToneFirstFreqValue, pktcSigDevToneFirstFreqValue,
pktcSigDevToneSecondFreqValue, pktcSigDevToneSecondFreqValue,
pktcSigDevToneThirdFreqValue, pktcSigDevToneThirdFreqValue,
pktcSigDevToneFourthFreqValue, pktcSigDevToneFourthFreqValue,
pktcSigDevToneFreqMode, pktcSigDevToneFreqMode,
pktcSigDevToneFreqAmpModePrtg, pktcSigDevToneFreqAmpModePrtg,
pktcSigDevToneFreqOnDuration, pktcSigDevToneFreqOnDuration,
pktcSigDevToneFreqOffDuration, pktcSigDevToneFreqOffDuration,
skipping to change at page 64, line 13 skipping to change at page 65, line 44
3) 400 Hz not AM modulated, on for 50 ms at -4 dBm 3) 400 Hz not AM modulated, on for 50 ms at -4 dBm
4) 400 Hz not AM modulated, off for 450 ms 4) 400 Hz not AM modulated, off for 450 ms
5) 400 Hz not AM modulated, on for 50 ms at -4 dBm 5) 400 Hz not AM modulated, on for 50 ms at -4 dBm
6) 400 Hz not AM modulated, off for 3450 ms 6) 400 Hz not AM modulated, off for 3450 ms
7) 400 Hz not AM modulated, on for 50 ms at -4 dBm 7) 400 Hz not AM modulated, on for 50 ms at -4 dBm
8) 400 Hz not AM modulated, off for 450 ms 8) 400 Hz not AM modulated, off for 450 ms
9) 400 Hz not AM modulated, on for 50 ms at -4 dBm 9) 400 Hz not AM modulated, on for 50 ms at -4 dBm
10) 400 Hz not AM modulated, off for 3450 ms 10) 400 Hz not AM modulated, off for 3450 ms
11) not repeated, not continuous 11) not repeated, not continuous
Assume userDefined1(17) is assigned to this tone: Assume userDefined1(18) is assigned to this tone:
pktcSigDevMultiFreqToneTable: pktcSigDevMultiFreqToneTable:
ToneType|F-1|F-2|F-3|F-4|F-Mode|ModePrtg|DbL|OnDur|OffDur|Rep-Count ToneType|F-1|F-2|F-3|F-4|F-Mode|ModePrtg|DbL|OnDur|OffDur|Rep-Count
=================================================================== ===================================================================
17 400 16 0 0 1 90 -40 500 400 0 18 400 16 0 0 1 90 -40 500 400 0
17 400 0 0 0 2 0 -40 50 450 0 18 400 0 0 0 2 0 -40 50 450 0
17 400 0 0 0 2 0 -40 50 3450 0 18 400 0 0 0 2 0 -40 50 3450 0
17 400 0 0 0 2 0 -40 50 450 0 18 400 0 0 0 2 0 -40 50 450 0
17 400 0 0 0 2 0 -40 50 3450 0 18 400 0 0 0 2 0 -40 50 3450 0
pktcSigDevToneTable: pktcSigDevToneTable:
ToneType|ToneRep-Count|Steady ToneType|ToneFreqGroup|ToneFreqCounter|ToneRep-Count|Steady
============================= =============================================================
17 0 false(2) 18 1 5 0 false(2)
The single row of the pktcSigDevToneTable defines one multi-
frequency group of five rows (ToneFreqCounter) defined in the
pktcSigDevMultiFreqToneTable and instructs the MTA to play this
group only once (non-repeatable as ToneRep-Count equals 0).
Example B - Congestion Tone - congestion(17): Example B - Congestion Tone - congestion(17):
Note: This example of an embedded cadence is based on an operator Note: This example of an embedded cadence is based on an operator
variation. variation.
1) 400Hz on for 400ms -10 dBm 1) 400Hz on for 400ms -10 dBm
2) 400Hz off for 350ms 2) 400Hz off for 350ms
3) 400Hz on for 225ms -4 dBm 3) 400Hz on for 225ms -4 dBm
4) 400Hz off for 525ms 4) 400Hz off for 525ms
skipping to change at page 65, line 4 skipping to change at page 66, line 33
3) 400Hz on for 225ms -4 dBm 3) 400Hz on for 225ms -4 dBm
4) 400Hz off for 525ms 4) 400Hz off for 525ms
5) repeat (1) through (4) 5000 times or T0 timeout (which ever is 5) repeat (1) through (4) 5000 times or T0 timeout (which ever is
shortest period) shortest period)
pktcSigDevMultiFreqToneTable: pktcSigDevMultiFreqToneTable:
ToneType|F-1|F-2|F-3|F-4|F-Mode|ModePrtg|DbL|OnDur|OffDur|Rep-Count ToneType|F-1|F-2|F-3|F-4|F-Mode|ModePrtg|DbL|OnDur|OffDur|Rep-Count
=================================================================== ===================================================================
17 400 0 0 0 2 0 -100 400 350 0 17 400 0 0 0 2 0 -100 400 350 0
17 400 0 0 0 2 0 -40 225 525 0 17 400 0 0 0 2 0 -40 225 525 0
pktcSigDevToneTable: pktcSigDevToneTable:
ToneType|ToneRep-Count|Steady ToneType|ToneFreqGroup|ToneFreqCounter|ToneRep-Count|Steady
============================= =============================================================
17 5000 false(0) 17 1 2 5000 false(2)
Example C - Call Waiting Tone - callWaiting1(9):
1) 16 Hz is modulated to carry the 400 Hz signal, ModulationRate
within 85%, on for 500msec, at -25 dBm or more but less than -14 dBm
2) 16 Hz is modulated to carry the 400 Hz signal, off for 0 ~ 4 secs
3) 400 Hz not modulated, on for 50 ms at -25 dBm or more but less
than -14 dBm
4) 400 Hz not modulated, off for 450ms
5) 400 Hz not modulated, on for 50 ms at -25 dBm or more but less
than -14 dBm
6) 400 Hz not modulated, off for 3450ms ([4000 - (50+450+50)])
7) Steps 3 thru 6 are repeated.
pktcSigDevMultiFreqToneTable:
ToneType|F-1|F-2|F-3|F-4|F-Mode|ModePrtg|DbL|OnDur|OffDur|Rep-Count
===================================================================
9 1 400 16 0 0 1 85 -25 500 1000 0
9 2 400 0 0 0 2 0 -25 50 450 0
9 3 400 0 0 0 2 0 -25 50 3450 0
pktcSigDevToneTable:
ToneType|ToneFreqGroup|ToneFreqCounter|ToneRep-Count|Steady
=============================================================
9 1 1 0 false(2)
9 2 2 1 false(2)
The first row of the pktcSigDevToneTable table instructs the MTA to
play one row (ToneFreqCounter) of the pktcSigDevMultiFreqToneTable
table only once (non-repeatable as ToneRep-Count equals 0). The
second row of the pktcSigDevToneTable table instructs the MTA to
play next two rows (ToneFreqCounter) of the
pktcSigDevMultiFreqToneTable table and make this frequency group
repeatable (ToneRep-Count is not 0).
7. Acknowledgments 7. Acknowledgments
This document is a production of the CableLabs PacketCable Working The current editors would like to thank the members of the IETF
Group. IPCDN working group and the CableLabs PacketCable Provisioning focus
team for their contributions, comments and suggestions.
The editors wish to express gratitude to: Specifically, the following individuals are recognized:
Angela Lyda Arris Interactive Angela Lyda Arris Interactive
Romascanu, Dan Avaya
Chad Griffiths Broadcom Corp. Chad Griffiths Broadcom Corp.
Eugene Nechamkin Broadcom Corp. Eugene Nechamkin Broadcom Corp.
Jean-Francois Mule CableLabs(R) Jean-Francois Mule CableLabs(R)
Matt A. Osman CableLabs(R) Matt A. Osman CableLabs(R)
Klaus Hermanns Cisco Systems, Inc. Klaus Hermanns Cisco Systems, Inc.
Rich Woundy Comcast Corp. Rich Woundy Comcast Corp.
Bert Wijnen Lucent Technologies Bert Wijnen Lucent Technologies
Randy Presuhn Mindspring Randy Presuhn Mindspring
Phillip Freyman Motorola, Inc. Phillip Freyman Motorola, Inc.
Rick Vetter Motorola, Inc. Rick Vetter Motorola, Inc.
Sasha Medvinsky Motorola, Inc. Sasha Medvinsky Motorola, Inc.
Wim De Ketelaere tComLabs Wim De Ketelaere tComLabs
David De Reu tComLabs David De Reu tComLabs
Kristof Sercu tComLabs Kristof Sercu tComLabs
Roy Spitzer Telogy Networks, Inc. Roy Spitzer Telogy Networks, Inc.
Itay Sherman Texas Instruments, Inc. Itay Sherman Texas Instruments, Inc.
Mauricio Sanchez Texas Instruments, Inc. Mauricio Sanchez Texas Instruments, Inc.
Shivakumar Thangapandi Texas Instruments, Inc. Shivakumar Thangapandi Texas Instruments, Inc.
Mike Heard Consultant Mike Heard Consultant
skipping to change at page 65, line 39 skipping to change at page 68, line 18
David De Reu tComLabs David De Reu tComLabs
Kristof Sercu tComLabs Kristof Sercu tComLabs
Roy Spitzer Telogy Networks, Inc. Roy Spitzer Telogy Networks, Inc.
Itay Sherman Texas Instruments, Inc. Itay Sherman Texas Instruments, Inc.
Mauricio Sanchez Texas Instruments, Inc. Mauricio Sanchez Texas Instruments, Inc.
Shivakumar Thangapandi Texas Instruments, Inc. Shivakumar Thangapandi Texas Instruments, Inc.
Mike Heard Consultant Mike Heard Consultant
For the international objects, the authors are especially thankful For the international objects, the authors are especially thankful
to Phillip Freyman and Eugene Nechamkin for their recommendations to Phillip Freyman and Eugene Nechamkin for their recommendations
and contributions. and contributions. Special appreciation is also expressed to the
IPCDN co-chairs (Jean-Francois, Rich woundy) and Dan Romascanu for
the numerous reviews and valuable comments.
8. Security Considerations 8. Security Considerations
There are a number of management objects defined in this MIB that There are a number of management objects defined in this MIB that
have a MAX-ACCESS clause of read-write and/or read-create. Such have a MAX-ACCESS clause of read-write and/or read-create. Such
objects may be considered sensitive or vulnerable in some network objects may be considered sensitive or vulnerable in some network
environments. The support for SET operations in a non-secure environments. The support for SET operations in a non-secure
environment without proper protection can have a negative effect on environment without proper protection can have a negative effect on
network operations. network operations.
skipping to change at page 66, line 50 skipping to change at page 69, line 26
operation, or a failure to obtain telephony service from client operation, or a failure to obtain telephony service from client
(MTA) devices. (MTA) devices.
The objects in the pktcNcsEndPntConfigTable are used for endpoint The objects in the pktcNcsEndPntConfigTable are used for endpoint
signaling. The pktcNcsEndPntConfigCallAgentId object contains the signaling. The pktcNcsEndPntConfigCallAgentId object contains the
name of the call agent, which includes the call agent Fully name of the call agent, which includes the call agent Fully
Qualified Domain Name (FQDN). If this object is SET maliciously, the Qualified Domain Name (FQDN). If this object is SET maliciously, the
MTA will not be able to communicate with the call agent, resulting MTA will not be able to communicate with the call agent, resulting
in a disruption of telephony service. The in a disruption of telephony service. The
pktcNcsEndPntConfigCallAgentUdpPort object identifies the UDP port pktcNcsEndPntConfigCallAgentUdpPort object identifies the UDP port
for NCS signaling traffic. If this object is SET maliciously, the for NCS traffic. If this object is SET maliciously, the call agent
call agent will not receive NCS signaling traffic from the MTA, also will not receive NCS traffic from the MTA, also resulting in a
resulting in a disruption of telephony service. disruption of telephony service.
Some of the readable objects in this MIB module (i.e., objects with Some of the readable objects in this MIB module (i.e., objects with
a MAX-ACCESS other than not-accessible) may be considered sensitive a MAX-ACCESS other than not-accessible) may be considered sensitive
or vulnerable in some network environments. It is thus important to or vulnerable in some network environments. It is thus important to
control even GET and/or NOTIFY access to these objects and possibly control even GET and/or NOTIFY access to these objects and possibly
to even encrypt the values of these objects when sending them over to even encrypt the values of these objects when sending them over
the network via SNMP. The most sensitive is the network via SNMP. The most sensitive is
pktcNcsEndPntStatusCallIpAddress within pktcNcsEndPntConfigTable. pktcNcsEndPntStatusCallIpAddress within pktcNcsEndPntConfigTable.
This information itself may be valuable to would-be attackers. This information itself may be valuable to would-be attackers.
skipping to change at page 69, line 17 skipping to change at page 71, line 43
11. Informative References 11. Informative References
[RFC3410] Case, J., Mundy, R., Partain, D. and B. Stewart, [RFC3410] Case, J., Mundy, R., Partain, D. and B. Stewart,
"Introduction and Applicability Statements for Internet- "Introduction and Applicability Statements for Internet-
Standard Management Framework", RFC 3410, December 2002. Standard Management Framework", RFC 3410, December 2002.
[RFC3435] Andreasen, F., and B. Foster, "Media Gateway Control [RFC3435] Andreasen, F., and B. Foster, "Media Gateway Control
Protocol (MGCP)", RFC 3435, January 2003. Protocol (MGCP)", RFC 3435, January 2003.
[RFC4234] D. Crocker, Ed. and P. Overell, "Augmented BNF for Syntax
Specifications: ABNF", RFC4234, October 2005.
[RFCXYZ] Nechamkin, E., and Mule J., "Multimedia Terminal Adapter [RFCXYZ] Nechamkin, E., and Mule J., "Multimedia Terminal Adapter
(MTA) Management Information Base for PacketCable and (MTA) Management Information Base for PacketCable and
IPCablecom compliant devices", RFCXYZ, <Date>. IPCablecom compliant devices", RFCXYZ, <Date>.
Editor's Note (to be removed prior to publication): This is the Editor's Note (to be removed prior to publication): This is the
reference to 'draft-ietf-ipcdn-pktc-mtamib' which is expected to reference to 'draft-ietf-ipcdn-pktc-mtamib' which is expected to
accepted at the same time as this draft. When the draft is accepted, accepted at the same time as this draft. When the draft is accepted,
the RFC Editor is asked to replace XYZ (and in the reference the RFC Editor is asked to replace XYZ (and in the reference
earlier) with the assigned value and to remove this note. earlier) with the assigned value and to remove this note.
 End of changes. 59 change blocks. 
103 lines changed or deleted 198 lines changed or added

This html diff was produced by rfcdiff 1.33. The latest version is available from http://tools.ietf.org/tools/rfcdiff/