draft-ietf-ipcdn-pktc-signaling-03.txt   draft-ietf-ipcdn-pktc-signaling-04.txt 
IPCDN IPCDN
Internet Draft Gordon Beacham Internet Draft Gordon Beacham
Document: draft-ietf-ipcdn-pktc-signaling- Motorola, Inc Document: draft-ietf-ipcdn-pktc-signaling- Motorola, Inc
03.txt 04.txt
Satish Kumar Satish Kumar
Texas Instruments Texas Instruments
Sumanth Sumanth
Channabasappa Channabasappa
Alopa Networks Alopa Networks
Inc Inc
Expires: July 2004 February 2004 Expires: December 2004 July 2004
Network-Based Call Signaling (NCS) Signaling MIB for PacketCable and Network-Based Call Signaling (NCS) Signaling 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, I certify that any applicable
patent or other IPR claims of which I am aware have been disclosed,
or will be disclosed, and any of which I become aware will be
disclosed, in accordance with RFC 3668.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet- other groups may also distribute working documents as Internet-
Drafts. Drafts.
Internet-Drafts are draft documents valid for a maximum of six Internet-Drafts are draft documents valid for a maximum of six
months and may be updated, replaced, or obsoleted by other documents months and may be updated, replaced, or obsoleted by other documents
at any time. It is inappropriate to use Internet-Drafts as at any time. It is inappropriate to use Internet-Drafts as
reference material or to cite them other than as "work in progress." reference material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt http://www.ietf.org/ietf/1id-abstracts.html
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2004). All Rights Reserved. Copyright (C) The Internet Society (2004). All Rights Reserved.
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
PacketCable/IPCablecom NCS Signaling MIB February 2004
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 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 the SNMP SMIv2. The set of objects are consistent with the SNMP
framework and existing SNMP standards. framework and existing SNMP standards.
PacketCable/IPCablecom NCS Signaling MIB February 2004
Table of Contents Table of Contents
1. The Internet-Standard Management Framework....................2 1. The Internet-Standard Management Framework....................2
2. Terminology...................................................2 2. Terminology...................................................2
2.1 MTA.......................................................3 2.1 MTA.......................................................3
2.2 Endpoint..................................................3 2.2 Endpoint..................................................3
2.3 L Line Package............................................3 2.3 L Line Package............................................3
2.4 E Line Package............................................3 2.4 E Line Package............................................3
3. Overview......................................................3 3. Overview......................................................3
3.1 Structure of the MIB......................................4 3.1 Structure of the MIB......................................4
3.2 pktcSigDevConfigObjects...................................4 3.2 pktcSigDevConfigObjects...................................4
3.3 pktcSigNotification.......................................6 3.3 pktcSigNotification.......................................6
3.4 pktcSigConformance........................................6 3.4 pktcSigConformance........................................6
4. Definitions...................................................7 4. Definitions...................................................6
5. Acknowledgments..............................................54 5. Acknowledgments..............................................48
6. Normative References.........................................55 6. Normative References.........................................48
7. Informative References.......................................55 7. Informative References.......................................49
8. Security Considerations......................................57 8. Security Considerations......................................50
9. Intellectual Property........................................58 9. IANA Considerations..........................................52
10. Authors' Addresses..........................................59 10. Intellectual Property.......................................52
11. Full Copyright Statement....................................59 11. Authors' Addresses..........................................53
12. Full Copyright Statement....................................53
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).
Objects in the MIB are defined using the mechanisms defined in the Objects in the MIB are defined using the mechanisms defined in the
Structure of Management Information (SMI). This memo specifies a MIB Structure of Management Information (SMI). This memo specifies a MIB
module that is compliant to the SMIv2, which is described in STD 58, module that is compliant to the SMIv2, which is described in STD 58,
RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580
[RFC2580]. [RFC2580].
2. Terminology 2.
Terminology
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
PacketCable/IPCablecom NCS Signaling MIB February 2004
"OPTIONAL", when used in the guidelines in this memo, are to be "OPTIONAL", when used in the guidelines in this memo, are to be
interpreted as described in RFC 2119 [RFC2119]. interpreted as described in RFC 2119 [RFC2119].
The terms "MIB module" and "information module" are used The terms "MIB module" and "information module" are used
interchangeably in this memo. As used here, both terms refer to any interchangeably in this memo. As used here, both terms refer to any
of the three types of information modules defined in Section 3 of of the three types of information modules defined in Section 3 of
RFC 2578 [RFC2578]. RFC 2578 [RFC2578].
PacketCable/IPCablecom NCS Signaling MIB February 2004 2.1
MTA
2.1 MTA
A Multimedia Terminal Adapter is a PacketCable or IPCablecom A Multimedia Terminal Adapter is a PacketCable or IPCablecom
compliant device providing telephony services over a cable or hybrid compliant device providing telephony services over a cable or hybrid
system used to deliver video signals to a community. It contains an system used to deliver video signals to a community. It contains an
interface to endpoints, a network interface, CODECs, and all interface to endpoints, a network interface, CODECs, and all
signaling and encapsulation functions required for Voice over IP signaling and encapsulation functions required for Voice over IP
transport, call signaling, and Quality of Service signaling. A MTA transport, call signaling, and Quality of Service signaling. A MTA
can be an embedded or a standalone device. An Embedded MTA (E-MTA) can be an embedded or a standalone device. An Embedded MTA (E-MTA)
is a MTA device containing an embedded DOCSIS Cable Modem. A is a MTA device containing an embedded DOCSIS Cable Modem. A
Standalone MTA (S-MTA) is a MTA device separated from the DOCSIS Standalone MTA (S-MTA) is a MTA device separated from the DOCSIS
Cable Modem by non-DOCSIS MAC interface (e.g., Ethernet, USB). Cable Modem by non-DOCSIS MAC interface (e.g., Ethernet, USB).
2.2 Endpoint 2.2
Endpoint
An endpoint or MTA endpoint is a standard RJ-11 telephony physical An endpoint or MTA endpoint is a standard RJ-11 telephony physical
port located on the MTA and used for attaching the telephone device port located on the MTA and used for attaching the telephone device
to the MTA. to the MTA.
2.3 L Line Package 2.3
L Line Package
The L line package refers to the core signaling functionality as The L line package refers to the core signaling functionality as
defined by PacketCable and IPCablecom. An MTA provides all L package defined by PacketCable and IPCablecom. An MTA provides all L package
elements, however the operator determines their application. elements, however the operator determines their application.
2.4 E Line Package 2.4
E Line Package
The E line package refers to extensions, over and above the core L The E line package refers to extensions, over and above the core L
package, defined in support of international requirements. E line package, defined in support of international requirements. E line
package elements are optional, vary from country to country, and are package elements are optional, vary from country to country, and are
set by operator or regulatory requirements. set by operator or regulatory requirements.
3. Overview 3.
Overview
This MIB provides a set of objects required for Signaling This MIB provides a set of objects required for Signaling
PacketCable and IPCablecom compliant Multimedia Terminal Adapter PacketCable and IPCablecom compliant Multimedia Terminal Adapter
(MTA) devices. MTA devices include one or more endpoints (e.g., (MTA) devices. MTA devices include one or more endpoints (e.g.,
telephone ports) which receive signaling information to establish telephone ports) which receive signaling information to establish
ring cadence, and codecs used for providing telephony service. ring cadence, and codecs used for providing telephony service.
PacketCable/IPCablecom NCS Signaling MIB February 2004
Telephone systems are typically very complex and often have a wide Telephone systems are typically very complex and often have a wide
distribution. It is therefore important for management systems to distribution. It is therefore important for management systems to
support MTAs from multiple vendors at the same time, including those support MTAs from multiple vendors at the same time, including those
from multiple countries. This MIB module provides objects suitable from multiple countries. This MIB module provides objects suitable
for managing signaling for MTA devices in the widest possible for managing signaling for MTA devices in the widest possible
variety of marketplaces. variety of marketplaces.
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, in the object REFERENCE NCS Signaling MIB objects. As a convention, in the object REFERENCE
PacketCable/IPCablecom NCS Signaling MIB February 2004
clauses, we use the PacketCable reference. IPCablecom compliant MTA clauses, we use the PacketCable reference. IPCablecom compliant MTA
devices MUST use the equivalent IPCablecom references. devices MUST use the equivalent IPCablecom references.
3.1 Structure of the MIB 3.1
Structure of the MIB
This MIB is identified by pktcSigMib and is structured in three This MIB is identified by pktcSigMib and is structured in three
groups: 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)
Each group of objects is explained in detail. Each group of objects is explained in detail.
3.2 pktcSigDevConfigObjects 3.2
pktcSigDevConfigObjects
pktcSigDevEchoCancellation - This object identifies the capability pktcSigDevEchoCancellation - This object identifies the capability
of echo cancellation on the device. of echo cancellation on the device.
pktcSigDevSilenceSuppression - This object specifies if the device pktcSigDevSilenceSuppression - This object specifies if the device
is capable of silence suppression (Voice Activity Detection). is capable of silence suppression (Voice Activity Detection).
pktcSigDevR0Cadence - this object specifies ring cadence 0. pktcSigDevR0Cadence - this object specifies ring cadence 0.
pktcSigDevR1Cadence - this object specifies ring cadence 1.
pktcSigDevR2Cadence - this object specifies ring cadence 2.
pktcSigDevR3Cadence - this object specifies ring cadence 3.
pktcSigDevR4Cadence - this object specifies ring cadence 4.
pktcSigDevR5Cadence - this object specifies ring cadence 5.
pktcSigDevR6Cadence - this object specifies ring cadence 6. pktcSigDevR6Cadence - this object specifies ring cadence 6.
PacketCable/IPCablecom NCS Signaling MIB February 2004
pktcSigDevR7Cadence - this object specifies ring cadence 7. pktcSigDevR7Cadence - this object specifies ring cadence 7.
pktcSigDevRgCadence - this object specifies ring cadence rg.
pktcSigDevRsCadence - this object specifies ring cadence rs.
pktcSigDefCallSigDscp - this object specifies the default value used pktcSigDefCallSigDscp - this object specifies the default value used
in the IP header for setting the Differentiated Services Code Point in the IP header for setting the Differentiated Services Code Point
(DSCP) value for call signaling. (DSCP) value for call signaling.
pktcSigDefMediaStreamDscp - this object specifies the default value pktcSigDefMediaStreamDscp - this object specifies the default value
used in the IP header for setting the Differentiated Services Code used in the IP header for setting the Differentiated Services Code
Point (DSCP) value for media stream packets. Point (DSCP) value for media stream packets.
pktcSigCapabilityTable - this table specifies list of supported pktcSigCapabilityTable - this table specifies list of supported
signaling types, versions and vendor extensions for MTA. signaling types, versions and vendor extensions for MTA.
pktcSigDefNcsReceiveUdpPort - this object contains the MTA User pktcSigDefNcsReceiveUdpPort - this object contains the MTA User
Datagram Protocol (UDP) receive port that is being used for NCS call Datagram Protocol (UDP) receive port that is being used for NCS call
signaling. signaling.
PacketCable/IPCablecom NCS Signaling MIB February 2004
pktcSigServiceClassNameUS - this object contains a string indicating
the Service Class Name to create an Upstream Service Flow for NCS.
pktcSigServiceClassNameDS - this object contains a string indicating
the Service Class Name to create an Downstream Service Flow for NCS.
pktcSigServiceClassNameMask - this object contains a value for the
Call Signaling Network Mask.
pktcSigNcsServiceFlowState - this object contains a status value of
the Call Signaling Service Flow.
pktcSigDevR1Cadence - this object specifies ring cadence 1.
pktcSigDevR2Cadence - this object specifies ring cadence 2.
pktcSigDevR3Cadence - this object specifies ring cadence 3.
pktcSigDevR4Cadence - this object specifies ring cadence 4.
pktcSigDevR5Cadence - this object specifies ring cadence 5.
pktcSigDevRgCadence - this object specifies ring cadence rg.
pktcSigDevRsCadence - this object specifies ring cadence rs.
pktcSigDevCIDMode - this international object selects various modes pktcSigDevCIDMode - this international object selects various modes
of caller id in common use. of caller id in common use.
pktcSigDevCIDFskAfterRing - this international object sets the delay pktcSigDevCIDFskAfterRing - this international object sets the delay
between the end of first ringing and the transmission of caller id between the end of first ringing and the transmission of caller id
information. information.
pktcSigDevCIDFskAfterDTAS - this international object sets the delay pktcSigDevCIDFskAfterDTAS - this international object sets the delay
between the dual-tone alert signal and the transmission of caller id between the dual-tone alert signal and the transmission of caller id
information. information.
skipping to change at page 6, line 5 skipping to change at page 5, line 50
between the ring pulse alert signal and the transmission of caller between the ring pulse alert signal and the transmission of caller
id information. id information.
pktcSigDevCIDRingAfterFSK - this international object sets the delay pktcSigDevCIDRingAfterFSK - this international object sets the delay
between the transmission of caller id information and the first between the transmission of caller id information and the first
ringing pattern. ringing pattern.
pktcSigDevCIDDTASAfterLR - this international object sets the delay pktcSigDevCIDDTASAfterLR - this international object sets the delay
between the end of a line reversal and the dual-tone alert signal. between the end of a line reversal and the dual-tone alert signal.
PacketCable/IPCablecom NCS Signaling MIB February 2004
pktcSigDevVmwiMode - this object selects various modes of visual pktcSigDevVmwiMode - this object selects various modes of visual
message waiting indicator service in common use. message waiting indicator service in common use.
PacketCable/IPCablecom NCS Signaling MIB February 2004
pktcSigDevVmwiFskAfterDTAS - this international object sets the pktcSigDevVmwiFskAfterDTAS - this international object sets the
delay between the dual-tone alert signal and the transmission of delay between the dual-tone alert signal and the transmission of
visual message waiting information. visual message waiting information.
pktcSigDevVwmiFskAfterRPAS - this international object sets the pktcSigDevVwmiFskAfterRPAS - this international object sets the
delay between the ring pulse alert signal and the transmission of delay between the ring pulse alert signal and the transmission of
visual message waiting information. visual message waiting information.
pktcSigDevVwmiDTASAfterLR - this international object sets the delay pktcSigDevVwmiDTASAfterLR - this international object sets the delay
between the end of a line reversal and the dual-tone alert signal between the end of a line reversal and the dual-tone alert signal
for visual message waiting information. for visual message waiting information.
pktcSigDevRingCadenceTable - this international object provides a pktcSigDevRingCadenceTable - this international object provides a
flexible structure within which to specify a variety of ring flexible structure within which to specify a variety of ring
cadences. cadences.
pktcSigDevStandardRingCadence - this international object specifies
the standard ring assumed by the MTA.
pktcSigDevRingSplashCadence - this international object specifies
the standard splash ring assumed by the MTA.
pktcSigDevToneTable - this international object specifies a flexible pktcSigDevToneTable - this international object specifies a flexible
structure within which to specify all of the tones used in the MTA. structure within which to specify all of the tones used in the MTA.
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.
3.3 pktcSigNotification 3.3
pktcSigNotification
pktcSigNotification - this object is used for signaling notification pktcSigNotification - this object is used for signaling notification
and reserved for future use. and reserved for future use.
3.4 pktcSigConformance 3.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.
PacketCable/IPCablecom NCS Signaling MIB February 2004
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 range of marketplaces as is possible. the widest range of marketplaces as is possible.
4. Definitions 4.
Definitions
PKTC-IETF-SIG-MIB DEFINITIONS ::= BEGIN PKTC-IETF-SIG-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
PacketCable/IPCablecom NCS Signaling MIB February 2004
MODULE-IDENTITY, MODULE-IDENTITY,
OBJECT-TYPE, OBJECT-TYPE,
Integer32, Integer32,
Unsigned32, Unsigned32,
mib-2 mib-2
FROM SNMPv2-SMI FROM SNMPv2-SMI
InetAddressType, InetAddressType,
InetAddress, InetAddress,
InetPortNumber InetPortNumber
FROM INET-ADDRESS-MIB FROM INET-ADDRESS-MIB
skipping to change at page 7, line 41 skipping to change at page 7, line 32
MODULE-COMPLIANCE MODULE-COMPLIANCE
FROM SNMPv2-CONF FROM SNMPv2-CONF
SnmpAdminString SnmpAdminString
FROM SNMP-FRAMEWORK-MIB FROM SNMP-FRAMEWORK-MIB
ifIndex ifIndex
FROM IF-MIB FROM IF-MIB
Dscp Dscp
FROM DIFFSERV-DSCP-TC; FROM DIFFSERV-DSCP-TC;
pktcSigMib MODULE-IDENTITY pktcSigMib MODULE-IDENTITY
LAST-UPDATED "200402180000Z" -- February 18, 2004 LAST-UPDATED "200407010000Z" -- July 1, 2004
ORGANIZATION "IETF IPCDN Working Group" ORGANIZATION "IETF IPCDN Working Group"
CONTACT-INFO CONTACT-INFO
"Satish Kumar Mudugere Eswaraiah "Satish Kumar Mudugere Eswaraiah
Texas Instruments India (P) Ltd., Texas Instruments India (P) Ltd.,
Golf view, Wind Tunnel Road Golf view, Wind Tunnel Road
Murugesh Palya Murugesh Palya
Bangalore - 560 017, INDIA Bangalore - 560 017, INDIA
Phone: +91 80 5269451 Phone: +91 80 5269451
Email: satish.kumar@ti.com Email: satish.kumar@ti.com
Sumanth Channabasappa Sumanth Channabasappa
Alopa Networks Inc Alopa Networks Inc
248, McCaslin Bvld #101, 248, McCaslin Bvld #101,
Louisville, Colorado - 80027 Louisville, Colorado - 80027
PacketCable/IPCablecom NCS Signaling MIB February 2004
U.S.A. U.S.A.
Phone: +1 303 604 6595 Phone: +1 303 604 6595
Email: Sumanth@alopa.com Email: Sumanth@alopa.com
Gordon Beacham Gordon Beacham
Motorola BCS/DCG Motorola BCS/DCG
6450 Sequence Drive, Bldg. 1 6450 Sequence Drive, Bldg. 1
San Diego, CA 92121, USA San Diego, CA 92121, USA
Phone: +1 858-404-2335 Phone: +1 858-404-2335
PacketCable/IPCablecom NCS Signaling MIB February 2004
E-Mail: gordon.beacham@motorola.com E-Mail: gordon.beacham@motorola.com
IETF IPCDN Working Group IETF IPCDN Working Group
General Discussion: ipcdn@ietf.org General Discussion: ipcdn@ietf.org
Subscribe: http://www.ietf.org/mailman/listinfo/ipcdn Subscribe: http://www.ietf.org/mailman/listinfo/ipcdn
Archive: ftp://ftp.ietf.org/ietf-mail-archive/ipcdn Archive: ftp://ftp.ietf.org/ietf-mail-archive/ipcdn
Co-Chair: Jean-Francois Mule, jf.mule@cablelabs.com Co-Chair: Jean-Francois Mule, jf.mule@cablelabs.com
Co-Chair: Richard Woundy, Richard_Woundy@cable.comcast.com" Co-Chair: Richard Woundy, Richard_Woundy@cable.comcast.com"
DESCRIPTION DESCRIPTION
skipping to change at page 8, line 37 skipping to change at page 8, line 28
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 (2004). This version of Copyright (C) The Internet Society (2004). 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 "200402180000Z" REVISION "200407010000Z"
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
TenthdBm ::= TEXTUAL-CONVENTION TenthdBm ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d-1" DISPLAY-HINT "d-1"
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This data type represents power levels that are normally "This data type represents power levels that are normally
expressed in dBm. Units are in tenths of a dBm; expressed in dBm. Units are in tenths of a dBm;
for example, -13.5 dBm will be represented as -135." for example, -13.5 dBm will be represented as -135."
PacketCable/IPCablecom NCS Signaling MIB February 2004
SYNTAX Integer32 SYNTAX Integer32
PktcCodecType ::= TEXTUAL-CONVENTION PktcCodecType ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
" Textual Convention defines various types of CODECs that " Textual Convention defines various types of CODECs that
MAY be supported. The list of CODECs MUST be consistent MAY be supported. The list of CODECs MUST be consistent
with the Codec RTP MAP Parameters Table in the PacketCable with the Codec RTP MAP Parameters Table in the PacketCable
CODEC specification. In-line embedded comments below CODEC specification. In-line embedded comments below
PacketCable/IPCablecom NCS Signaling MIB February 2004
contain the Literal Codec Name for each CODEC. The Literal contain the Literal Codec Name for each CODEC. The Literal
Codec Name is the second column of the table with CODEC Codec Name is the second column of the table with CODEC
RTP Map Parameters. Literal Codec Name Column contains the RTP Map Parameters. Literal Codec Name Column contains the
CODEC name used in LCD of the NCS messages CRCX/MDCX and CODEC name used in LCD of the NCS messages CRCX/MDCX and
is also used to identify the CODEC in the CMS is also used to identify the CODEC in the CMS
Provisioning Specification. RTP Map Parameter Column of Provisioning Specification. RTP Map Parameter Column of
the Table contains the string used in the media attribute the Table contains the string used in the media attribute
line (a=) of the SDP parameters in NCS messages." line (a=) of the SDP parameters in NCS messages."
SYNTAX INTEGER { SYNTAX INTEGER {
other (1), other (1),
skipping to change at page 9, line 42 skipping to change at page 9, line 33
g728 (8), -- G728 g728 (8), -- G728
pcma (9), -- PCMA pcma (9), -- PCMA
g726at16 (10), -- G726-16 g726at16 (10), -- G726-16
g726at24 (11), -- G726-24 g726at24 (11), -- G726-24
g726at40 (12) -- G726-40 g726at40 (12) -- G726-40
} }
PktcRingCadence ::= TEXTUAL-CONVENTION PktcRingCadence ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
" This object represents a ring cadence and repeatable "
characteristics in bit string format. The ring cadence This object represents a ring cadence and repeatable
representation starts with the first 1 in the pattern (the Characteristics in a bit string format. The first two
leading 0s in the MSB are padding and are to be ignored). octets of the bit string represent the length in bits of
Each bit represents 100ms of tone; 1 is tone, 0 is no the duration of the cadence (i.e., the number of bits that
tone. 64 bits MUST be used for cadence representation. The follow the third octet). The third octet is used to
LSB 4 bits of this object are used for representing represent repeatable characteristics. 00000000 means
repeatable characteristics. 0000 means repeatable, and repeatable, and 10000000 means non repeatable. Each bit
1000 means non repeatable. During SNMP SET operations, 64 after the third octet represents 50 ms and 1 represents
bits MUST be used, otherwise the MTA MUST reject the ring and 0 represents silent. The first bit of the fourth
value. As an example, the hex representation of a ring octet is the first bit of the ring cadence. All bits are
cadence of 0.5 secs on; 4 secs off; repeatable would be: counted in network order such that the octet with only the
0x0001F00000000000." first bit set will look like 10000000 bit sequence. A
SYNTAX BITS { total of 264 bits can be set to represent 13200 ms of
total cadence cycle. There will be at most 3 on/off
PacketCable/IPCablecom NCS Signaling MIB February 2004 transitions per cadence period."
SYNTAX OCTET STRING (SIZE(4..36))
interval1 (0),
interval2 (1),
interval3 (2),
interval4 (3),
interval5 (4),
interval6 (5),
interval7 (6),
interval8 (7),
interval9 (8),
interval10 (9),
interval11 (10),
interval12 (11),
interval13 (12),
interval14 (13),
interval15 (14),
interval16 (15),
interval17 (16),
interval18 (17),
interval19 (18),
interval20 (19),
interval21 (20),
interval22 (21),
interval23 (22),
interval24 (23),
interval25 (24),
interval26 (25),
interval27 (26),
interval28 (27),
interval29 (28),
interval30 (29),
interval31 (30),
interval32 (31),
interval33 (32),
interval34 (33),
interval35 (34),
interval36 (35),
interval37 (36),
interval38 (37),
interval39 (38),
interval40 (39),
interval41 (40),
interval42 (41),
interval43 (42),
interval44 (43),
interval45 (44),
interval46 (45),
interval47 (46),
interval48 (47),
interval49 (48),
PacketCable/IPCablecom NCS Signaling MIB February 2004
interval50 (49),
interval51 (50),
interval52 (51),
interval53 (52),
interval54 (53),
interval55 (54),
interval56 (55),
interval57 (56),
interval58 (57),
interval59 (58),
interval60 (59),
repeat1 (60),
repeat2 (61),
repeat3 (62),
repeat4 (63)
}
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.
PacketCable/IPCablecom NCS Signaling MIB February 2004
ncs - 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), -- reserved for future use reserved(2), -- reserved for future use
ncs(3) ncs(3)
} }
pktcSigMibObjects OBJECT IDENTIFIER ::= { pktcSigMib 1 } pktcSigMibObjects OBJECT IDENTIFIER ::= { pktcSigMib 1 }
pktcSigDevConfigObjects OBJECT IDENTIFIER ::= pktcSigDevConfigObjects OBJECT IDENTIFIER ::=
{ pktcSigMibObjects 1 } { pktcSigMibObjects 1 }
pktcNcsEndPntConfigObjects OBJECT IDENTIFIER ::= pktcNcsEndPntConfigObjects OBJECT IDENTIFIER ::=
{ pktcSigMibObjects 2 } { pktcSigMibObjects 2 }
pktcSigEndPntConfigObjects OBJECT IDENTIFIER ::=
{ pktcSigMibObjects 3 }
-- --
-- The codec table (pktcSigDevCodecTable) defines all combinations -- The codec table (pktcSigDevCodecTable) defines all combinations
-- of codecs supported by the Multimedia Terminal Adapter (MTA). -- of codecs supported by the Multimedia Terminal Adapter (MTA).
-- --
pktcSigDevCodecTable OBJECT-TYPE pktcSigDevCodecTable OBJECT-TYPE
SYNTAX SEQUENCE OF PktcSigDevCodecEntry SYNTAX SEQUENCE OF PktcSigDevCodecEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
" This table describes the MTA supported codec types. An MTA " This table describes the MTA supported codec types. An MTA
MUST populate this table with all possible combinations of MUST populate this table with all possible combinations of
PacketCable/IPCablecom NCS Signaling MIB February 2004
codecs it supports for simultaneous operation. For codecs it supports for simultaneous operation. For
example, an MTA with two endpoints may be designed with a example, an MTA with two endpoints may be designed with a
particular DSP and memory architecture that allows it to particular DSP and memory architecture that allows it to
support the following fixed combinations of codecs for support the following fixed combinations of codecs for
simultaneous operation: simultaneous operation:
Codec Type Maximum Number of Simultaneous Codecs Codec Type Maximum Number of Simultaneous Codecs
PCMA 3 PCMA 3
PCMA 2 PCMA 2
skipping to change at page 12, line 29 skipping to change at page 11, line 5
PCMA 1 PCMA 1
PCMU 2 PCMU 2
PCMU 3 PCMU 3
PCMA 1 PCMA 1
G729 1 G729 1
G729 2 G729 2
PacketCable/IPCablecom NCS Signaling MIB February 2004
PCMU 1 PCMU 1
G729 1 G729 1
Based on this example, the entries in the codec table Based on this example, the entries in the codec table
would be: would be:
CodecComboIndex pktcSigDevCodecType pktcSigDevCodecMax CodecComboIndex pktcSigDevCodecType pktcSigDevCodecMax
1 pcma 3 1 pcma 3
2 pcma 2 2 pcma 2
2 pcmu 1 2 pcmu 1
3 pcma 1 3 pcma 1
3 pcmu 2 3 pcmu 2
4 pcmu 3 4 pcmu 3
5 pcma 1 5 pcma 1
5 g729 1 5 g729 1
6 g729 2 6 g729 2
7 pcmu 1 7 pcmu 1
7 g729 1 7 g729 1
An operator querying this table is able to determine all An operator querying this table is able to determine all
Possible codec combinations the MTA is capable of possible codec combinations the MTA is capable of
simultaneously supporting." simultaneously supporting."
::= { pktcSigDevConfigObjects 1 } ::= { pktcSigDevConfigObjects 1 }
PacketCable/IPCablecom NCS Signaling MIB February 2004
pktcSigDevCodecEntry OBJECT-TYPE pktcSigDevCodecEntry OBJECT-TYPE
SYNTAX PktcSigDevCodecEntry SYNTAX PktcSigDevCodecEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Each entry represents the maximum number of active "Each entry represents the maximum number of active
connections with a particular codec the MTA is capable of connections with a particular codec the MTA is capable of
supporting. Each row is indexed by a composite key supporting. Each row is indexed by a composite key
consisting of a number enumerating the particular codec consisting of a number enumerating the particular codec
combination and the codec type." combination and the codec type."
skipping to change at page 13, line 29 skipping to change at page 12, line 4
PktcSigDevCodecEntry ::= SEQUENCE { PktcSigDevCodecEntry ::= SEQUENCE {
pktcSigDevCodecComboIndex Unsigned32, pktcSigDevCodecComboIndex Unsigned32,
pktcSigDevCodecType PktcCodecType, pktcSigDevCodecType PktcCodecType,
pktcSigDevCodecMax Unsigned32 pktcSigDevCodecMax Unsigned32
} }
pktcSigDevCodecComboIndex OBJECT-TYPE pktcSigDevCodecComboIndex OBJECT-TYPE
SYNTAX Unsigned32 (1..255) SYNTAX Unsigned32 (1..255)
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
PacketCable/IPCablecom NCS Signaling MIB February 2004
STATUS current STATUS current
DESCRIPTION DESCRIPTION
" The index value which enumerates a particular codec " The index value which enumerates a particular codec
combination in the pktcSigDevCodecTable." combination in the pktcSigDevCodecTable."
::= { pktcSigDevCodecEntry 1 } ::= { pktcSigDevCodecEntry 1 }
pktcSigDevCodecType OBJECT-TYPE pktcSigDevCodecType OBJECT-TYPE
SYNTAX PktcCodecType SYNTAX PktcCodecType
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
skipping to change at page 14, line 4 skipping to change at page 12, line 32
SYNTAX Unsigned32(1..255) SYNTAX Unsigned32(1..255)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
" The maximum number of simultaneous sessions of a " The maximum number of simultaneous sessions of a
particular codec that the MTA can support." particular codec that the MTA can support."
::= { pktcSigDevCodecEntry 3 } ::= { pktcSigDevCodecEntry 3 }
-- --
-- These are the common signaling related definitions that affect -- These are the common signaling related definitions that affect
PacketCable/IPCablecom NCS Signaling MIB February 2004
-- the entire MTA device. -- the entire MTA device.
-- --
pktcSigDevEchoCancellation OBJECT-TYPE pktcSigDevEchoCancellation 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 echo " This object specifies if the device is capable of echo
cancellation." cancellation."
skipping to change at page 14, line 30 skipping to change at page 13, line 4
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 (Voice Activity Detection)."
::= { pktcSigDevConfigObjects 3 } ::= { pktcSigDevConfigObjects 3 }
pktcSigDevCallerIdSigProtocol OBJECT-TYPE pktcSigDevCallerIdSigProtocol OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
PacketCable/IPCablecom NCS Signaling MIB February 2004
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 identifies the subscriber line protocol used
for signaling on-hook caller id information." for signaling on-hook caller id information."
REFERENCE REFERENCE
"EN 300 659-1 Specification" "EN 300 659-1 Specification"
DEFVAL { fsk } DEFVAL { fsk }
::= { pktcSigDevConfigObjects 4 } ::= { pktcSigDevConfigObjects 4 }
--
-- In the United States Ring Cadences 0, 6, and 7 are custom ring
-- cadences definable by the system administrator. The following
-- three objects are used for these definitions.
--
pktcSigDevR0Cadence OBJECT-TYPE pktcSigDevR0Cadence OBJECT-TYPE
SYNTAX PktcRingCadence SYNTAX PktcRingCadence
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
" This object specifies ring cadence 0 (a user defined " This object specifies ring cadence 0 (a user defined
field) where each bit represents a duration of 100 field). This object is required for the L line package."
::= { pktcSigDevConfigObjects 5 }
pktcSigDevR1Cadence OBJECT-TYPE
SYNTAX PktcRingCadence
MAX-ACCESS read-write
STATUS current
DESCRIPTION
" This object specifies ring cadence 1 (a user defined
field). This object is required for the L line package."
::= { pktcSigDevConfigObjects 6 }
pktcSigDevR2Cadence OBJECT-TYPE
SYNTAX PktcRingCadence
MAX-ACCESS read-write
STATUS current
DESCRIPTION
" This object specifies ring cadence 2 (a user defined
field). This object is required for the L line package."
::= { pktcSigDevConfigObjects 7 }
pktcSigDevR3Cadence OBJECT-TYPE
SYNTAX PktcRingCadence
MAX-ACCESS read-write
STATUS current
DESCRIPTION
" This object specifies ring cadence 3 (a user defined
field). This object is required for the L line package."
::= { pktcSigDevConfigObjects 8 }
PacketCable/IPCablecom NCS Signaling MIB February 2004 PacketCable/IPCablecom NCS Signaling MIB February 2004
milliseconds (6 seconds total), except the LSB 4 bits pktcSigDevR4Cadence OBJECT-TYPE
which are used to represent repeatable characteristics." SYNTAX PktcRingCadence
DEFVAL {{ interval1, interval2, interval3, interval4, interval5, MAX-ACCESS read-write
interval6, interval7, interval8, interval9, STATUS current
interval10, interval11, interval12, interval13, DESCRIPTION
interval14, interval15, interval16, interval17, " This object specifies ring cadence 4 (a user defined
interval18, interval19, interval20 }} field). This object is required for the L line package."
-- 11111111111111111111000000000000000000000000000000000000000 ::= { pktcSigDevConfigObjects 9 }
-- 00000
::= { pktcSigDevConfigObjects 5 } pktcSigDevR5Cadence OBJECT-TYPE
SYNTAX PktcRingCadence
MAX-ACCESS read-write
STATUS current
DESCRIPTION
" This object specifies ring cadence 5 (a user defined
field). This object is required for the L line package."
::= { pktcSigDevConfigObjects 10 }
pktcSigDevR6Cadence OBJECT-TYPE pktcSigDevR6Cadence OBJECT-TYPE
SYNTAX PktcRingCadence SYNTAX PktcRingCadence
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
" This object specifies ring cadence 6 (a user defined " This object specifies ring cadence 6 (a user defined
field) where each bit represents a duration of 100 field). This object is required for the L line package."
milliseconds (6 seconds total), except the LSB 4 bits ::= { pktcSigDevConfigObjects 11 }
which are used to represent repeatable characteristics."
DEFVAL {{ interval1, interval2, interval3, interval4, interval5,
interval6, interval7, interval8, interval9,
interval10, interval11, interval12, interval13,
interval14, interval15, interval16, interval17,
interval18, interval19, interval20 }}
-- 11111111111111111111000000000000000000000000000000000000000
-- 00000
::= { pktcSigDevConfigObjects 6 }
pktcSigDevR7Cadence OBJECT-TYPE pktcSigDevR7Cadence OBJECT-TYPE
SYNTAX PktcRingCadence SYNTAX PktcRingCadence
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
" This object specifies ring cadence 7 (a user defined " This object specifies ring cadence 7 (a user defined
field) where each bit represents a duration of 100 field). This object is required for the L line package."
milliseconds (6 seconds total), except the LSB 4 bits ::= { pktcSigDevConfigObjects 12 }
which are used to represent repeatable characteristics."
DEFVAL {{ interval1, interval2, interval3, interval4, interval5,
interval6, interval7, interval8, interval9,
interval10, interval11, interval12, interval13,
interval14, interval15, interval16, interval17,
interval18, interval19, interval20 }}
-- 11111111111111111111000000000000000000000000000000000000000
-- 00000
::= { pktcSigDevConfigObjects 7 }
pktcSigDefCallSigDscp OBJECT-TYPE pktcSigDevRgCadence OBJECT-TYPE
SYNTAX Dscp -- RFC 3289: DIFFSERV-DSCP-TC SYNTAX PktcRingCadence
MAX-ACCESS read-write
STATUS current
DESCRIPTION
" This object specifies ring cadence rg (a user defined
field). This object is required for the L line package."
::= { pktcSigDevConfigObjects 13 }
pktcSigDevRsCadence OBJECT-TYPE
SYNTAX PktcRingCadence
MAX-ACCESS read-write
STATUS current
PacketCable/IPCablecom NCS Signaling MIB February 2004 PacketCable/IPCablecom NCS Signaling MIB February 2004
DESCRIPTION
" This object specifies ring cadence rs (a user defined
field) The MTA MUST reject any attempt to make this object
repeatable. This object is required for the L line
package."
::= { pktcSigDevConfigObjects 14 }
pktcSigDefCallSigDscp OBJECT-TYPE
SYNTAX Dscp -- RFC 3289: DIFFSERV-DSCP-TC
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
" The default value used in the IP header for setting the " The default value used in the IP header for setting the
Differentiated Services Code Point (DSCP) value for call Differentiated Services Code Point (DSCP) value for call
signaling." signaling."
DEFVAL { 0 } DEFVAL { 0 }
::= { pktcSigDevConfigObjects 8 } ::= { pktcSigDevConfigObjects 15 }
pktcSigDefMediaStreamDscp OBJECT-TYPE pktcSigDefMediaStreamDscp OBJECT-TYPE
SYNTAX Dscp -- RFC 3289: DIFFSERV-DSCP-TC SYNTAX Dscp -- RFC 3289: DIFFSERV-DSCP-TC
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
" The default value used in the IP header for setting " The default value used in the IP header for setting
the Differentiated Services Code Point (DSCP) value for the Differentiated Services Code Point (DSCP) value for
media stream packets." media stream packets."
DEFVAL { 0 } DEFVAL { 0 }
::= { pktcSigDevConfigObjects 9 } ::= { pktcSigDevConfigObjects 16 }
-- --
-- pktcSigCapabilityTable - This table defines the valid signaling -- pktcSigCapabilityTable - This table defines the valid signaling
-- types supported by this MTA. -- types supported by this MTA.
-- --
pktcSigCapabilityTable OBJECT-TYPE pktcSigCapabilityTable OBJECT-TYPE
SYNTAX SEQUENCE OF PktcSigCapabilityEntry SYNTAX SEQUENCE OF PktcSigCapabilityEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
" This table describes the signaling types supported by this " This table describes the signaling types supported by this
MTA." MTA."
::= { pktcSigDevConfigObjects 10 } ::= { pktcSigDevConfigObjects 17 }
pktcSigCapabilityEntry OBJECT-TYPE pktcSigCapabilityEntry OBJECT-TYPE
SYNTAX PktcSigCapabilityEntry SYNTAX PktcSigCapabilityEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
" Entries in pktcMtaDevSigCapabilityTable - List of " Entries in pktcMtaDevSigCapabilityTable - List of
PacketCable/IPCablecom NCS Signaling MIB February 2004
supported signaling types, versions and vendor extensions supported signaling types, versions and vendor extensions
for this MTA. Each entry in the list provides for one for this MTA. Each entry in the list provides for one
signaling type and version combination. If the device signaling type and version combination. If the device
supports multiple versions of the same signaling type it supports multiple versions of the same signaling type it
will require multiple entries." will require multiple entries."
INDEX { pktcSignalingIndex } INDEX { pktcSignalingIndex }
::= { pktcSigCapabilityTable 1 } ::= { pktcSigCapabilityTable 1 }
PktcSigCapabilityEntry ::= SEQUENCE { PktcSigCapabilityEntry ::= SEQUENCE {
PacketCable/IPCablecom NCS Signaling MIB February 2004
pktcSignalingIndex Unsigned32, pktcSignalingIndex Unsigned32,
pktcSignalingType PktcSigType, pktcSignalingType PktcSigType,
pktcSignalingVersion SnmpAdminString, pktcSignalingVersion SnmpAdminString,
pktcSignalingVendorExtension SnmpAdminString pktcSignalingVendorExtension SnmpAdminString
} }
pktcSignalingIndex OBJECT-TYPE pktcSignalingIndex OBJECT-TYPE
SYNTAX Unsigned32 (1..255) SYNTAX Unsigned32 (1..255)
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
skipping to change at page 17, line 47 skipping to change at page 17, line 4
" 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
PacketCable/IPCablecom NCS Signaling MIB February 2004
additional capabilities, vendors can decide how to encode additional capabilities, vendors can decide how to encode
these extensions, although space separated text is these extensions, although space separated text is
suggested." suggested."
::= { 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
PacketCable/IPCablecom NCS Signaling MIB February 2004
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."
REFERENCE REFERENCE
"PacketCable NCS Specification" "PacketCable NCS Specification"
DEFVAL { 2427 } DEFVAL { 2427 }
::= { pktcSigDevConfigObjects 11 }
pktcSigServiceClassNameUS OBJECT-TYPE
SYNTAX SnmpAdminString (SIZE (0..15))
MAX-ACCESS read-write
STATUS current
DESCRIPTION
" This object contains a string indicating the Service
Class Name to create an Upstream Service Flow for NCS.
If the object has an empty string value then the NCS SF
is not created and the best effort primary SF is used for
NCS data. If this object is set to a non-empty (non-zero
length) string, the MTA MUST create the NCS SF if it does
not currently exist and the pktcSigServiceClassNameMask
object has a non-zero value. If this object is
subsequently set to an empty (zero-length) string, the
MTA MUST delete the NCS SF if it exists. Setting this
object to a different value does not cause the US SF to
be re-created. The string MUST contain printable ASCII
characters. The length of the string does not include a
terminating zero. The MTA MUST append a terminating zero
when the MTA creates the service flow."
DEFVAL { "" }
::= { pktcSigDevConfigObjects 12 }
pktcSigServiceClassNameDS OBJECT-TYPE
SYNTAX SnmpAdminString (SIZE (0..15))
MAX-ACCESS read-write
STATUS current
DESCRIPTION
" This object contains a string indicating the Service
Class Name to create a Downstream Service Flow for NCS.
If the object has an empty string value then the NCS SF
is not created and the best effort primary SF is used for
NCS data. If this object is set to a non-empty (non-zero
length) string, the MTA MUST create the NCS SF if it does
not currently exist and the pktcSigServiceClassNameMask
object has a non-zero value. If this object is
subsequently set to an empty (zero-length) string, the
MTA MUST delete the NCS SF if it exists. Setting this
object to a different value does not cause the DS SF to
PacketCable/IPCablecom NCS Signaling MIB February 2004
be re-created. The string MUST contain printable ASCII
characters. The length of the string does not include a
terminating zero. The MTA MUST append a terminating zero
when the MTA creates the service flow."
DEFVAL { "" }
::= { pktcSigDevConfigObjects 13 }
pktcSigServiceClassNameMask OBJECT-TYPE
SYNTAX Integer32
MAX-ACCESS read-write
STATUS current
DESCRIPTION
" This object contains a value used for the NCS Call
Signaling classifier mask. If this object is set to a
zero value, the MTA MUST delete both NCS SFs. When
this object is set to a non-zero value, the MTA MUST
create the NCS SF for which the corresponding MIB object
(pktcSigServiceClassNameUS or pktcSigServiceClassNameDS)
has a non-empty value, if the NCS SF does not already
exist."
DEFVAL { 0 }
::= { pktcSigDevConfigObjects 14 }
pktcSigNcsServiceFlowState OBJECT-TYPE
SYNTAX INTEGER {
notactive (1),
active (2),
error (3)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object contains a status value of the Call Signaling
Service Flow.
- notactive indicates that the NCS SF is not being used,
and has not tried to be created,
- active indicates that the NCS SF is in use,
- error indicates that the NCS SF creation resulted in
an error and the best effort channel is used for NCS
Signaling."
::= { pktcSigDevConfigObjects 15 }
pktcSigDevR1Cadence OBJECT-TYPE
SYNTAX PktcRingCadence
MAX-ACCESS read-write
STATUS current
DESCRIPTION
" This object specifies ring cadence 1 (a user defined
field) where each bit represents a duration of 100
PacketCable/IPCablecom NCS Signaling MIB February 2004
milliseconds (6 seconds total), except the LSB 4 bits
which are used to represent repeatable characteristics."
DEFVAL {{ interval1, interval2, interval3, interval4, interval5,
interval6, interval7, interval8, interval9,
interval10, interval11, interval12, interval13,
interval14, interval15, interval16, interval17,
interval18, interval19, interval20 }}
-- 11111111111111111111000000000000000000000000000000000000000
-- 00000
::= { pktcSigDevConfigObjects 16 }
pktcSigDevR2Cadence OBJECT-TYPE
SYNTAX PktcRingCadence
MAX-ACCESS read-write
STATUS current
DESCRIPTION
" This object specifies ring cadence 2 (a user defined
field) where each bit represents a duration of 100
milliseconds (6 seconds total), except the LSB 4 bits
which are used to represent repeatable characteristics."
DEFVAL {{ interval1, interval2, interval3, interval4, interval5,
interval6, interval7, interval8, interval13,
interval14, interval15, interval16, interval17,
interval18, interval19, interval20 }}
-- 11111111000011111111000000000000000000000000000000000000000
-- 00000
::= { pktcSigDevConfigObjects 17 }
pktcSigDevR3Cadence OBJECT-TYPE
SYNTAX PktcRingCadence
MAX-ACCESS read-write
STATUS current
DESCRIPTION
" This object specifies ring cadence 3 (a user defined
field) where each bit represents a duration of 100
milliseconds (6 seconds total), except the LSB 4 bits
which are used to represent repeatable characteristics."
DEFVAL {{ interval1, interval2, interval3, interval4, interval7,
interval8, interval9, interval10, interval13,
interval14, interval15, interval16, interval17,
interval18, interval19, interval20 }}
-- 11110011110011111111000000000000000000000000000000000000000
-- 00000
::= { pktcSigDevConfigObjects 18 } ::= { pktcSigDevConfigObjects 18 }
pktcSigDevR4Cadence OBJECT-TYPE
SYNTAX PktcRingCadence
MAX-ACCESS read-write
STATUS current
PacketCable/IPCablecom NCS Signaling MIB February 2004
DESCRIPTION
" This object specifies ring cadence 4 (a user defined
field) where each bit represents a duration of 100
milliseconds (6 seconds total), except the LSB 4 bits
which are used to represent repeatable characteristics."
DEFVAL {{ interval1, interval2, interval3, interval6, interval7,
interval8, interval9, interval10, interval11,
interval12, interval13, interval14, interval15,
interval18, interval19, interval20 }}
-- 11100111111111100111000000000000000000000000000000000000000
-- 00000
::= { pktcSigDevConfigObjects 19 }
pktcSigDevR5Cadence OBJECT-TYPE
SYNTAX PktcRingCadence
MAX-ACCESS read-write
STATUS current
DESCRIPTION
" This object specifies ring cadence 5 (a user defined
field) where each bit represents a duration of 100
milliseconds, except the LSB 4 bits which are used to
represent repeatable characteristics."
DEFVAL {{ interval1, interval2, interval3, interval4, interval5,
repeat1 }}
-- 11111000000000000000000000000000000000000000000000000000000
-- 01000
::= { pktcSigDevConfigObjects 20 }
pktcSigDevRgCadence OBJECT-TYPE
SYNTAX PktcRingCadence
MAX-ACCESS read-write
STATUS current
DESCRIPTION
" This object specifies ring cadence rg (a user defined
field) where each bit represents a duration of 100
milliseconds (6 seconds total), except the LSB 4 bits
which are used to represent repeatable characteristics.
This object is required for the L line package."
DEFVAL {{ interval1, interval2, interval3, interval4, interval5,
interval6, interval7, interval8, interval9,
interval10, interval11, interval12, interval13,
interval14, interval15, interval16, interval17,
interval18, interval19, interval20 } }
-- 11111111111111111111000000000000000000000000000000000000000
-- 00000
::= { pktcSigDevConfigObjects 21 }
pktcSigDevRsCadence OBJECT-TYPE
SYNTAX PktcRingCadence
PacketCable/IPCablecom NCS Signaling MIB February 2004
MAX-ACCESS read-write
STATUS current
DESCRIPTION
" This object specifies ring cadence rs (a user defined
field) where each bit represents a duration of 100
milliseconds (6 seconds total), except the LSB 4 bits
which are used to represent repeatable characteristics.
The MTA MUST reject any attempt to make this object
repeatable. This object is required for the L line
package."
DEFVAL {{ interval1, interval2, interval3, interval4, interval5,
repeat1 }}
-- 11111000000000000000000000000000000000000000000000000000000
-- 01000
::= { pktcSigDevConfigObjects 22 }
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),
f22Hz(7), f22Hz(7),
f23Hz(8), f23Hz(8),
skipping to change at page 22, line 49 skipping to change at page 17, line 52
" This object must only be set via the configuration file " This object must only be set via the configuration file
during the provisioning process. The power ring frequency during the provisioning process. The power ring frequency
is the frequency at which the sinusoidal voltage must is the frequency at which the sinusoidal voltage must
travel down the twisted pair to make terminal equipment travel down the twisted pair to make terminal equipment
ring. Different countries define different electrical ring. Different countries define different electrical
characteristics to make terminal equipment ring." characteristics to make terminal equipment ring."
REFERENCE REFERENCE
"EN 300 001 contains a list of frequency ranges that "EN 300 001 contains a list of frequency ranges that
are defined for each country." are defined for each country."
DEFVAL { f20Hz } DEFVAL { f20Hz }
::= { pktcSigDevConfigObjects 23 } ::= { pktcSigDevConfigObjects 19 }
pktcSigPulseSignalTable OBJECT-TYPE pktcSigPulseSignalTable OBJECT-TYPE
SYNTAX SEQUENCE OF PktcSigPulseSignalEntry SYNTAX SEQUENCE OF PktcSigPulseSignalEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
PacketCable/IPCablecom NCS Signaling MIB February 2004 PacketCable/IPCablecom NCS Signaling MIB February 2004
MAX-ACCESS not-accessible
STATUS current
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.
The values of the MIB objects in this table take effect The values of the MIB objects in this table take effect
only if these parameters are not defined via signaling, in only if these parameters are not defined via signaling, in
which case the latter determines the values of the which case the latter determines the values of the
parameters. This object is required for the E line parameters. This object is required for the E line
package. Signals defined in this table are triggered using package. Signals defined in this table are triggered using
the E line package. the E line package.
Objects in this table do not persist across MTA reboots." Objects in this table do not persist across MTA reboots."
REFERENCE REFERENCE
"TS 101 909-4 Specification" "TS 101 909-4 Specification"
::= { pktcSigDevConfigObjects 24 } ::= { pktcSigDevConfigObjects 20 }
pktcSigPulseSignalEntry OBJECT-TYPE pktcSigPulseSignalEntry OBJECT-TYPE
SYNTAX PktcSigPulseSignalEntry SYNTAX PktcSigPulseSignalEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
" This object defines the set of parameters associated with " This object defines the set of parameters associated with
each particular value of pktcSigPulseSignalType. Each each particular value of pktcSigPulseSignalType. Each
entry in the pktcSigPulseSignalTable is indexed by the entry in the pktcSigPulseSignalTable is indexed by the
pktcSigPulseSignalType object." pktcSigPulseSignalType object."
skipping to change at page 23, line 53 skipping to change at page 19, line 4
SYNTAX INTEGER SYNTAX INTEGER
{ {
initialRing(1), initialRing(1),
pulseLoopClose(2), pulseLoopClose(2),
pulseLoopOpen(3), pulseLoopOpen(3),
enableMeterPulse(4), enableMeterPulse(4),
meterPulseBurst(5), meterPulseBurst(5),
pulseNoBattery(6), pulseNoBattery(6),
pulseNormalPolarity(7), pulseNormalPolarity(7),
pulseReducedBattery(8), pulseReducedBattery(8),
pulseReversePolarity(9)
}
MAX-ACCESS not-accessible
PacketCable/IPCablecom NCS Signaling MIB February 2004 PacketCable/IPCablecom NCS Signaling MIB February 2004
pulseReversePolarity(9)
}
MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
" There are nine types of international pulse signals." " There are nine types of international pulse signals."
REFERENCE REFERENCE
"EN 300 324-1 Specification" "EN 300 324-1 Specification"
::= { pktcSigPulseSignalEntry 1 } ::= { pktcSigPulseSignalEntry 1 }
pktcSigPulseSignalFrequency OBJECT-TYPE pktcSigPulseSignalFrequency OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
skipping to change at page 24, line 53 skipping to change at page 20, line 4
SYNTAX TenthdBm (-250..152) SYNTAX TenthdBm (-250..152)
UNITS "dbm" UNITS "dbm"
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
" This object is only applicable to the enableMeterPulse and " This object is only applicable to the enableMeterPulse and
meterPulseBurst signal types. This is the decibel level meterPulseBurst signal types. This is the decibel level
for each frequency at which tones could be generated at for each frequency at which tones could be generated at
the a and b terminals (TE connection point)." the a and b terminals (TE connection point)."
REFERENCE REFERENCE
PacketCable/IPCablecom NCS Signaling MIB February 2004
"EN 300 001 Specification" "EN 300 001 Specification"
DEFVAL { -135 } DEFVAL { -135 }
::={pktcSigPulseSignalEntry 3 } ::={pktcSigPulseSignalEntry 3 }
PacketCable/IPCablecom NCS Signaling MIB February 2004
pktcSigPulseSignalDuration OBJECT-TYPE pktcSigPulseSignalDuration OBJECT-TYPE
SYNTAX Unsigned32 (0..5000) SYNTAX Unsigned32 (0..5000)
UNITS "Milliseconds" UNITS "Milliseconds"
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
" This object specifies the pulse duration for each " This object specifies the pulse duration for each
signal type. In addition, the MTA must accept the values signal type. In addition, the MTA must accept the values
in the incremental steps specific for each signal type. in the incremental steps specific for each signal type.
The following table defines the default values and the The following table defines the default values and the
skipping to change at page 25, line 52 skipping to change at page 21, line 4
signal type. The following table defines the default signal type. The following table defines the default
values and the incremental steps for this object depending values and the incremental steps for this object depending
on the signal type. on the signal type.
pktcSigPulseSignaltype Default (ms) Increment (ms) pktcSigPulseSignaltype Default (ms) Increment (ms)
initialRing 200 50 initialRing 200 50
pulseLoopClose 1000 10 pulseLoopClose 1000 10
pulseLoopOpen 1000 10 pulseLoopOpen 1000 10
enableMeterPulse 1000 10 enableMeterPulse 1000 10
meterPulseBurst 1000 10 meterPulseBurst 1000 10
pulseNoBattery 1000 10 pulseNoBattery 1000 10
pulseNormalPolarity 1000 10
pulseReducedBattery 1000 10
pulseReversePolarity 1000 10"
PacketCable/IPCablecom NCS Signaling MIB February 2004 PacketCable/IPCablecom NCS Signaling MIB February 2004
pulseNormalPolarity 1000 10
pulseReducedBattery 1000 10
pulseReversePolarity 1000 10"
REFERENCE REFERENCE
"EN 300 324-1 Specification" "EN 300 324-1 Specification"
::= { pktcSigPulseSignalEntry 5} ::= { pktcSigPulseSignalEntry 5}
pktcSigPulseSignalRepeatCount OBJECT-TYPE pktcSigPulseSignalRepeatCount OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
" This object specifies how many times to repeat a pulse. " This object specifies how many times to repeat a pulse.
skipping to change at page 26, line 53 skipping to change at page 22, line 4
" This object is used for international systems only. " This object is used for international systems only.
For on-hook Caller ID, pktcSigDevCIDMode selects the For on-hook Caller ID, pktcSigDevCIDMode selects the
method of Caller ID. For the duringRingingETS method, the method of Caller ID. For the duringRingingETS method, the
FSK containing the Caller ID information is sent between FSK containing the Caller ID information is sent between
the first and second ring pattern. For the dtAsETS, the first and second ring pattern. For the dtAsETS,
rpAsETS, and lrAsETS methods, the FSK containing the rpAsETS, and lrAsETS methods, the FSK containing the
Caller ID information is sent before the first ring Caller ID information is sent before the first ring
pattern. For the dtAsETS method, the FSK is sent after the pattern. For the dtAsETS method, the FSK is sent after the
Dual Tone Alert Signal. Dual Tone Alert Signal.
For the rpAsETS method, the FSK is sent after a Ring For the rpAsETS method, the FSK is sent after a Ring
Pulse. For the lrAsETS method, the Line Reversal occurs
first, then the Dual Tone Alert Signal, and finally the
FSK is sent."
PacketCable/IPCablecom NCS Signaling MIB February 2004 PacketCable/IPCablecom NCS Signaling MIB February 2004
Pulse. For the lrAsETS method, the Line Reversal occurs
first, then the Dual Tone Alert Signal, and finally the
FSK is sent."
DEFVAL { dtAsETS } DEFVAL { dtAsETS }
::= {pktcSigDevConfigObjects 25 } ::= {pktcSigDevConfigObjects 21 }
pktcSigDevCIDFskAfterRing OBJECT-TYPE pktcSigDevCIDFskAfterRing OBJECT-TYPE
SYNTAX Unsigned32 (50..2000) SYNTAX Unsigned32 (50..2000)
UNITS "Milliseconds" UNITS "Milliseconds"
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
" This object is used for international systems only. This " This object is used for international systems only. This
object specifies the delay between the end of first object specifies the delay between the end of first
ringing pattern and the start of the transmission of the ringing pattern and the start of the transmission of the
FSK containing the Caller ID information. It is only used FSK containing the Caller ID information. It is only used
when pktcSigDevCIDMode is duringRingingETS. when pktcSigDevCIDMode is duringRingingETS.
pktcSigDevCIDMode pktcSigDevCIDFskAfterRing pktcSigDevCIDMode pktcSigDevCIDFskAfterRing
duringringingETS 550 ms duringringingETS 550 ms
dtAsETS not used dtAsETS not used
rpAsETS not used rpAsETS not used
lrAsETS not used" lrAsETS not used"
REFERENCE REFERENCE
"EN 300 659-1 Specification" "EN 300 659-1 Specification"
DEFVAL { 550 } DEFVAL { 550 }
::= {pktcSigDevConfigObjects 26 } ::= {pktcSigDevConfigObjects 22 }
pktcSigDevCIDFskAfterDTAS OBJECT-TYPE pktcSigDevCIDFskAfterDTAS OBJECT-TYPE
SYNTAX Unsigned32 (45..500) SYNTAX Unsigned32 (45..500)
UNITS "Milliseconds" UNITS "Milliseconds"
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
" This object is used for international systems only. This " This object is used for international systems only. This
object specifies the delay between the end of the Dual object specifies the delay between the end of the Dual
Tone Alert Signal (DT-AS) and the start of the Tone Alert Signal (DT-AS) and the start of the
skipping to change at page 27, line 51 skipping to change at page 22, line 54
information. This object is only used when information. This object is only used when
pktcSigDevCIDMode is dtAsETS or lrAsETS. pktcSigDevCIDMode is dtAsETS or lrAsETS.
pktcSigDevCIDMode pktcSigDevCIDFskAfterDTAS pktcSigDevCIDMode pktcSigDevCIDFskAfterDTAS
duringringingETS not used duringringingETS not used
dtAsETS 50 ms dtAsETS 50 ms
rpAsETS not used rpAsETS not used
lrAsETS 50 ms" lrAsETS 50 ms"
REFERENCE REFERENCE
"EN 300 659-1 Specification" "EN 300 659-1 Specification"
DEFVAL { 50 } DEFVAL { 50 }
::= {pktcSigDevConfigObjects 27 } ::= {pktcSigDevConfigObjects 23 }
PacketCable/IPCablecom NCS Signaling MIB February 2004
pktcSigDevCIDFskAfterRPAS OBJECT-TYPE pktcSigDevCIDFskAfterRPAS OBJECT-TYPE
SYNTAX Unsigned32 (500..800) SYNTAX Unsigned32 (500..800)
UNITS "Milliseconds" UNITS "Milliseconds"
PacketCable/IPCablecom NCS Signaling MIB February 2004
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
" This object is used for international systems only. This " This object is used for international systems only. This
object specifies the delay between the end of the Ring object specifies the delay between the end of the Ring
Pulse Alert Signal (RP-AS) and the start of the Pulse Alert Signal (RP-AS) and the start of the
transmission of the FSK containing the Caller ID transmission of the FSK containing the Caller ID
information. This object is only used when information. This object is only used when
pktcSigDevCIDMode is rpAsETS. pktcSigDevCIDMode is rpAsETS.
pktcSigDevCIDMode pktcSigDevCIDFskAfterRPAS pktcSigDevCIDMode pktcSigDevCIDFskAfterRPAS
duringringingETS not used duringringingETS not used
dtAsETS not used dtAsETS not used
rpAsETS 650 ms rpAsETS 650 ms
lrAsETS not used" lrAsETS not used"
REFERENCE REFERENCE
"EN 300 659-1 Specification" "EN 300 659-1 Specification"
DEFVAL { 650 } DEFVAL { 650 }
::= {pktcSigDevConfigObjects 28 } ::= {pktcSigDevConfigObjects 24 }
pktcSigDevCIDRingAfterFSK OBJECT-TYPE pktcSigDevCIDRingAfterFSK OBJECT-TYPE
SYNTAX Unsigned32 (50..500) SYNTAX Unsigned32 (50..500)
UNITS "Milliseconds" UNITS "Milliseconds"
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
" This object is used for international systems only. This " This object is used for international systems only. This
object specifies the delay between the end of the complete object specifies the delay between the end of the complete
transmission of the FSK containing the Caller ID transmission of the FSK containing the Caller ID
skipping to change at page 28, line 46 skipping to change at page 23, line 49
only used when pktcSigDevCIDMode is dtAsETS, rpAsETS or only used when pktcSigDevCIDMode is dtAsETS, rpAsETS or
lrAsETS. lrAsETS.
pktcSigDevCIDMode pktcSigDevCIDFskAfterFSK pktcSigDevCIDMode pktcSigDevCIDFskAfterFSK
duringringingETS not used duringringingETS not used
dtAsETS 250 ms dtAsETS 250 ms
rpAsETS 250 ms rpAsETS 250 ms
lrAsETS 250 ms" lrAsETS 250 ms"
REFERENCE REFERENCE
"EN 300 659-1 Specification" "EN 300 659-1 Specification"
DEFVAL { 250 } DEFVAL { 250 }
::= {pktcSigDevConfigObjects 29 } ::= {pktcSigDevConfigObjects 25 }
pktcSigDevCIDDTASAfterLR OBJECT-TYPE pktcSigDevCIDDTASAfterLR OBJECT-TYPE
SYNTAX Unsigned32 (50..655) SYNTAX Unsigned32 (50..655)
UNITS "Milliseconds" UNITS "Milliseconds"
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION
" This object is used for international systems only. This
object specifies the delay between the end of the Line
PacketCable/IPCablecom NCS Signaling MIB February 2004 PacketCable/IPCablecom NCS Signaling MIB February 2004
DESCRIPTION
" This object is used for international systems only. This
object specifies the delay between the end of the Line
Reversal and the start of the Dual Tone Alert Signal Reversal and the start of the Dual Tone Alert Signal
(DT-AS). This object is only used when pktcSigDevCIDMode (DT-AS). This object is only used when pktcSigDevCIDMode
is lrAsETS. is lrAsETS.
pktcSigDevCIDMode pktcSigDevCIDFskAfterLR pktcSigDevCIDMode pktcSigDevCIDFskAfterLR
duringringingETS not used duringringingETS not used
dtAsETS not used dtAsETS not used
rpAsETS not used rpAsETS not used
lrAsETS 250 ms" lrAsETS 250 ms"
REFERENCE REFERENCE
"EN 300 659-1 Specification" "EN 300 659-1 Specification"
DEFVAL { 250 } DEFVAL { 250 }
::= {pktcSigDevConfigObjects 31 } ::= {pktcSigDevConfigObjects 26 }
pktcSigDevVmwiMode OBJECT-TYPE pktcSigDevVmwiMode OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
dtAsETS(1), dtAsETS(1),
rpAsETS(2), rpAsETS(2),
lrAsETS(3), lrAsETS(3),
osi(4) osi(4)
} }
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
skipping to change at page 29, line 43 skipping to change at page 24, line 46
the dtAsETS, rpAsETS, lrAsETS, and OSI methods, the dtAsETS, rpAsETS, lrAsETS, and OSI methods,
the FSK containing the VMWI information is sent after an the FSK containing the VMWI information is sent after an
alerting signal. For the dtAsETS method, the FSK is sent alerting signal. For the dtAsETS method, the FSK is sent
after the Dual Tone Alert Signal. For the rpAsETS method, after the Dual Tone Alert Signal. For the rpAsETS method,
the FSK is sent after a Ring Pulse. For the lrAsETS the FSK is sent after a Ring Pulse. For the lrAsETS
method, the Line Reversal occurs first, then the Dual Tone method, the Line Reversal occurs first, then the Dual Tone
Alert Signal, and finally the FSK is sent. For the OSI Alert Signal, and finally the FSK is sent. For the OSI
method, the FSK is sent after the Open Switching method, the FSK is sent after the Open Switching
Interval." Interval."
DEFVAL { dtAsETS } DEFVAL { dtAsETS }
::= {pktcSigDevConfigObjects 32 } ::= {pktcSigDevConfigObjects 27 }
pktcSigDevVmwiFskAfterDTAS OBJECT-TYPE pktcSigDevVmwiFskAfterDTAS OBJECT-TYPE
SYNTAX Unsigned32 (45..500) SYNTAX Unsigned32 (45..500)
UNITS "Milliseconds" UNITS "Milliseconds"
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
" This object is used for international systems only. This " This object is used for international systems only. This
object specifies the delay between the end of the Dual object specifies the delay between the end of the Dual
Tone Alert Signal (DT-AS) and the start of the
transmission of the FSK containing the VMWI information.
This object is only used when pktcSigDevVmwiMode is
PacketCable/IPCablecom NCS Signaling MIB February 2004 PacketCable/IPCablecom NCS Signaling MIB February 2004
Tone Alert Signal (DT-AS) and the start of the
transmission of the FSK containing the VMWI information.
This object is only used when pktcSigDevVmwiMode is
dtAsETS or lrAsETS. dtAsETS or lrAsETS.
pktcSigDevVmwiMode pktcSigDevVmwiFskAfterDTAS pktcSigDevVmwiMode pktcSigDevVmwiFskAfterDTAS
dtAsETS 50 ms dtAsETS 50 ms
rpAsETS not used rpAsETS not used
lrAsETS 50 ms" lrAsETS 50 ms"
REFERENCE REFERENCE
"EN 300 659-1 Specification" "EN 300 659-1 Specification"
DEFVAL { 50 } DEFVAL { 50 }
::= {pktcSigDevConfigObjects 33 } ::= {pktcSigDevConfigObjects 28 }
pktcSigDevVmwiFskAfterRPAS OBJECT-TYPE pktcSigDevVmwiFskAfterRPAS OBJECT-TYPE
SYNTAX Unsigned32 (500..800) SYNTAX Unsigned32 (500..800)
UNITS "Milliseconds" UNITS "Milliseconds"
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
" This object is used for international systems only. This " This object is used for international systems only. This
object specifies the delay between the end of the Ring object specifies the delay between the end of the Ring
Pulse Alert Signal (RP-AS) and the start of the Pulse Alert Signal (RP-AS) and the start of the
transmission of the FSK containing the VMWI information. transmission of the FSK containing the VMWI information.
This object is only used when pktcSigDevVmwiMode is This object is only used when pktcSigDevVmwiMode is
rpAsETS. rpAsETS.
pktcSigDevVmwiMode pktcSigDevVmwiFskAfterRPAS pktcSigDevVmwiMode pktcSigDevVmwiFskAfterRPAS
dtAsETS not used dtAsETS not used
rpAsETS 650 ms rpAsETS 650 ms
lrAsETS not used " lrAsETS not used "
REFERENCE REFERENCE
"EN 300 659-1 Specification" "EN 300 659-1 Specification"
DEFVAL { 650 } DEFVAL { 650 }
::= {pktcSigDevConfigObjects 34 } ::= {pktcSigDevConfigObjects 29 }
pktcSigDevVmwiDTASAfterLR OBJECT-TYPE pktcSigDevVmwiDTASAfterLR OBJECT-TYPE
SYNTAX Unsigned32 (50..655) SYNTAX Unsigned32 (50..655)
UNITS "Milliseconds" UNITS "Milliseconds"
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
" This object is used for international systems only. This " This object is used for international systems only. This
object specifies the delay between the end of the Line object specifies the delay between the end of the Line
Reversal and the start of the Dual Tone Alert Signal Reversal and the start of the Dual Tone Alert Signal
(DT-AS) for VMWI information. This object is only used (DT-AS) for VMWI information. This object is only used
when pktcSigDevVmwiMode is lrAsETS. when pktcSigDevVmwiMode is lrAsETS.
pktcSigDevVmwiMode pktcSigDevVmwiDTASAfterLR pktcSigDevVmwiMode pktcSigDevVmwiDTASAfterLR
dtAsETS not used dtAsETS not used
rpAsETS not used rpAsETS not used
lrAsETS 250 ms "
REFERENCE
"EN 300 659-1 Specification"
PacketCable/IPCablecom NCS Signaling MIB February 2004 PacketCable/IPCablecom NCS Signaling MIB February 2004
lrAsETS 250 ms "
REFERENCE
"EN 300 659-1 Specification"
DEFVAL { 250 } DEFVAL { 250 }
::= {pktcSigDevConfigObjects 35 } ::= {pktcSigDevConfigObjects 30 }
pktcSigDevRingCadenceTable OBJECT-TYPE pktcSigDevRingCadenceTable OBJECT-TYPE
SYNTAX SEQUENCE OF PktcSigDevRingCadenceEntry SYNTAX SEQUENCE OF PktcSigDevRingCadenceEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
" In V5.2, Cadence rings are defined by the telco governing " In V5.2, Cadence rings are defined by the telco governing
body for each country. The MTA must be able to support body for each country. The MTA must be able to support
various ranges of cadence patterns and cadence periods. various ranges of cadence patterns and cadence periods.
The MTA will be able to support country specific The MTA will be able to support country specific
provisioning of the cadence and idle period. There will be provisioning of the cadence and idle period. Each
at most 3 on/off transitions per cadence period. Each
cadence pattern will be assigned a unique value ranging cadence pattern will be assigned a unique value ranging
from 1-128 (inclusive) corresponding to the value of x from 1-128 (inclusive) corresponding to the value of x
plus one, where x is the value sent in the cr(x) signal plus one, where x is the value sent in the cr(x) signal
requested per the appropriate NCS message, and defined in requested per the appropriate NCS message, and defined in
the E package. The MTA will derive the cadence periods the E package. The MTA will derive the cadence periods
from the ring Cadence table entry as provisioned by the from the ring Cadence table entry as provisioned by the
customer. The MTA is allowed to provide appropriate customer. The MTA is allowed to provide appropriate
default values for each of the ring cadences. This table default values for each of the ring cadences. This table
only needs to be supported when the MTA implements the NCS only needs to be supported when the MTA implements the NCS
E package. Objects in this table do not persist across MTA E package. Objects in this table do not persist across MTA
reboots." reboots."
REFERENCE REFERENCE
"TS 101 909-4 Specification" "TS 101 909-4 Specification"
::= { pktcSigDevConfigObjects 36 } ::= { pktcSigDevConfigObjects 31 }
pktcSigDevRingCadenceEntry OBJECT-TYPE pktcSigDevRingCadenceEntry OBJECT-TYPE
SYNTAX PktcSigDevRingCadenceEntry SYNTAX PktcSigDevRingCadenceEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
" Unique value ranging from 1 to 128 that corresponds to the " Unique value ranging from 1 to 128 that corresponds to the
value sent by the LE (plus one) based on country specific value sent by the LE (plus one) based on country specific
cadences, one row per cadence cycle. In any given system cadences, one row per cadence cycle. In any given system
implementation for a particular country, it is anticipated implementation for a particular country, it is anticipated
that a small number of ring cadences will be in use. Thus, that a small number of ring cadences will be in use. Thus,
this table most likely will not be populated to its full this table most likely will not be populated to its full
128-row size." 128-row size."
INDEX { pktcSigDevRingCadenceIndex } INDEX { pktcSigDevRingCadenceIndex }
::= { pktcSigDevRingCadenceTable 1 } ::= { pktcSigDevRingCadenceTable 1 }
PktcSigDevRingCadenceEntry ::= SEQUENCE { PktcSigDevRingCadenceEntry ::= SEQUENCE {
pktcSigDevRingCadenceIndex Unsigned32, pktcSigDevRingCadenceIndex Unsigned32,
pktcSigDevRingCadence OCTET STRING pktcSigDevRingCadence OCTET STRING
}
PacketCable/IPCablecom NCS Signaling MIB February 2004 PacketCable/IPCablecom NCS Signaling MIB February 2004
}
pktcSigDevRingCadenceIndex OBJECT-TYPE pktcSigDevRingCadenceIndex OBJECT-TYPE
SYNTAX Unsigned32 (1..128) SYNTAX Unsigned32 (1..128)
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
" The table index equivalent to the country specific cadence " The table index equivalent to the country specific cadence
(1 - 128)." (1 - 128)."
::= { pktcSigDevRingCadenceEntry 1 } ::= { pktcSigDevRingCadenceEntry 1 }
pktcSigDevRingCadence OBJECT-TYPE pktcSigDevRingCadence OBJECT-TYPE
SYNTAX OCTET STRING (SIZE(4..36)) SYNTAX PktcRingCadence
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
" This is the Ring Cadence Octet String. The first two " This is the Ring Cadence Octet String. This object is
octets of the bit string represent the length in bits of required for the E line package."
the duration of the cadence. The third octet is used to
represent repeatable charcteristics. 00000000 means
repeatable, and 10000000 means non repeatable. Each Bit
after the third octet represents 50 ms and 1 represents
ring and 0 represents silent. The first bit of the fourth
octet is the first bit of the ring cadence. A total of 264
Bits can be set to represent 13200 ms of total cadence
cycle. This object is required for the E line package."
::= { pktcSigDevRingCadenceEntry 2 } ::= { pktcSigDevRingCadenceEntry 2 }
pktcSigDevStandardRingCadence OBJECT-TYPE
SYNTAX OCTET STRING (SIZE(4..36))
MAX-ACCESS read-write
STATUS current
DESCRIPTION
" This is the Ring Cadence Octet String for the standard
ring. The first two octets of the bit string represent
the length in bits of the duration of the cadence. The
third octet is used to represent repeatable
characteristics. 00000000 means repeatable, and 10000000
means non repeatable. Each Bit after the third octet
represents 50 ms and 1 represents ring and 0 represents
silent. The first bit of the fourth octet is the first bit
of the ring cadence. A total of 264 Bits can be set to
represent 13200 ms of cadence cycle. The MTA MUST provide
a default value for this object in accordance with
published specifications for the country of operation.
This object is required for the E line package."
REFERENCE
"TR 101 183 Specification"
::= { pktcSigDevConfigObjects 37 }
pktcSigDevRingSplashCadence OBJECT-TYPE
PacketCable/IPCablecom NCS Signaling MIB February 2004
SYNTAX OCTET STRING (SIZE(4..36))
MAX-ACCESS read-write
STATUS current
DESCRIPTION
" This is the Ring Cadence Octet String for splash ring. The
first two octets of the bit string represent the length in
bits of the duration of the cadence. The third octet is
used to represent repeatable characteristics. 00000000
means repeatable, and 10000000 means non repeatable. Each
Bit after the third octet represents 50 ms and 1
represents ring and 0 represents silent. The first bit of
the fourth octet is the first bit of the ring cadence. A
total of 264 Bits can be set to represent 13200 ms of
cadence cycle. The MTA MUST provide a default value for
this object in accordance with published specifications
for the country of operation. This object is required for
the E line package."
REFERENCE
"TR 101 183 Specification"
::= { pktcSigDevConfigObjects 38 }
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 various tone operations. Any
definition of the tones callWaiting1-4 in this table 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 MIB objects pktcNcsEndPntConfigCallWaitingDelay, by the MIB objects pktcNcsEndPntConfigCallWaitingDelay,
and pktcNcsEndPntConfigCallWaitingMaxRep. The MTA MUST and pktcNcsEndPntConfigCallWaitingMaxRep. The MTA MUST
make sure that, after the provisioning cycle, the table is make sure that, after the provisioning cycle, the table is
fully populated (i.e., for each possible index, an entry fully populated (i.e., for each possible index, an entry
MUST be defined) using reasonable defaults for each row MUST be defined) using reasonable defaults for each row
that was not defined by the provisioning information. that was not defined by the provisioning information.
Objects in this table do not persist across MTA reboots." Objects in this table do not persist across MTA reboots."
REFERENCE REFERENCE
"NCS Specification, TS 101 909-4 Specification" "NCS Specification, TS 101 909-4 Specification"
::= { pktcSigDevConfigObjects 39 } ::= { 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
" Unique value ranging from 1 to 21 that will correspond to " Unique value ranging from 1 to 21 that will correspond to
the different tone types that are being supported by the the different tone types that are being supported by the
PacketCable/IPCablecom NCS Signaling MIB February 2004 PacketCable/IPCablecom NCS Signaling MIB February 2004
skipping to change at page 35, line 19 skipping to change at page 29, line 19
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
" This object defines the type of tone being accessed. The " This object defines the type of tone being accessed. The
alertingSignal, specialDial, specialInfo, release, alertingSignal, specialDial, specialInfo, release,
congestion and userDefined1-4 tone types are triggered congestion and userDefined1-4 tone types are triggered
using the E line package." using the E line package."
::={pktcSigDevToneEntry 1 } ::={pktcSigDevToneEntry 1 }
pktcSigDevToneDbLevel OBJECT-TYPE pktcSigDevToneDbLevel OBJECT-TYPE
SYNTAX TenthdBm (-600..40) SYNTAX TenthdBm (-250..-30)
UNITS "dbm" UNITS "dbm"
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
" This is the decibel level for each frequency at which " This is the decibel level for each frequency at which
tones could be generated at the a and b terminals (TE tones could be generated at the a and b terminals (TE
connection point)." connection point)."
DEFVAL { -40 } DEFVAL { -40 }
::={pktcSigDevToneEntry 2 } ::={pktcSigDevToneEntry 2 }
skipping to change at page 40, line 11 skipping to change at page 34, line 11
::= { pktcNcsEndPntConfigObjects 1 } ::= { pktcNcsEndPntConfigObjects 1 }
pktcNcsEndPntConfigEntry OBJECT-TYPE pktcNcsEndPntConfigEntry OBJECT-TYPE
PacketCable/IPCablecom NCS Signaling MIB February 2004 PacketCable/IPCablecom NCS Signaling MIB February 2004
SYNTAX PktcNcsEndPntConfigEntry SYNTAX PktcNcsEndPntConfigEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
" Entries in pktcNcsEndPntConfigTable û Each entry " Entries in pktcNcsEndPntConfigTable ¡ Each entry
represents the required signaling parameters for the represents the required signaling parameters for the
specific endpoint provisioned with voice services." specific endpoint provisioned with voice services."
INDEX { ifIndex } INDEX { ifIndex }
::= { pktcNcsEndPntConfigTable 1 } ::= { pktcNcsEndPntConfigTable 1 }
PktcNcsEndPntConfigEntry ::= SEQUENCE { PktcNcsEndPntConfigEntry ::= SEQUENCE {
pktcNcsEndPntConfigCallAgentId SnmpAdminString, pktcNcsEndPntConfigCallAgentId SnmpAdminString,
pktcNcsEndPntConfigCallAgentUdpPort InetPortNumber, pktcNcsEndPntConfigCallAgentUdpPort InetPortNumber,
pktcNcsEndPntConfigPartialDialTO Unsigned32, pktcNcsEndPntConfigPartialDialTO Unsigned32,
pktcNcsEndPntConfigCriticalDialTO Unsigned32, pktcNcsEndPntConfigCriticalDialTO Unsigned32,
skipping to change at page 51, line 11 skipping to change at page 45, line 11
during the provisioning process." during the provisioning process."
DEFVAL { 75 } DEFVAL { 75 }
::= { pktcNcsEndPntConfigEntry 38 } ::= { pktcNcsEndPntConfigEntry 38 }
PacketCable/IPCablecom NCS Signaling MIB February 2004 PacketCable/IPCablecom NCS Signaling MIB February 2004
-- --
-- notification group is for future extension. -- notification group is for future extension.
-- --
pktcSigNotification OBJECT IDENTIFIER ::= { pktcSigMib 0 } pktcSigNotification OBJECT IDENTIFIER ::= { pktcSigMib 0 }
pktcSigConformance OBJECT IDENTIFIER ::= { pktcSigMib 3 } pktcSigConformance OBJECT IDENTIFIER ::= { pktcSigMib 2 }
pktcSigCompliances OBJECT IDENTIFIER ::= { pktcSigConformance 1 } pktcSigCompliances OBJECT IDENTIFIER ::= { pktcSigConformance 1 }
pktcSigGroups OBJECT IDENTIFIER ::= { pktcSigConformance 2 } pktcSigGroups OBJECT IDENTIFIER ::= { pktcSigConformance 2 }
-- --
-- compliance statements -- compliance statements
-- --
pktcSigBasicCompliance MODULE-COMPLIANCE pktcSigBasicCompliance MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION DESCRIPTION
skipping to change at page 52, line 10 skipping to change at page 46, line 10
pktcSigGroup OBJECT-GROUP pktcSigGroup OBJECT-GROUP
OBJECTS { OBJECTS {
pktcSigDevCodecType, pktcSigDevCodecType,
pktcSigDevCodecMax, pktcSigDevCodecMax,
PacketCable/IPCablecom NCS Signaling MIB February 2004 PacketCable/IPCablecom NCS Signaling MIB February 2004
pktcSigDevEchoCancellation, pktcSigDevEchoCancellation,
pktcSigDevSilenceSuppression, pktcSigDevSilenceSuppression,
pktcSigDevR0Cadence, pktcSigDevR0Cadence,
pktcSigDevR1Cadence,
pktcSigDevR2Cadence,
pktcSigDevR3Cadence,
pktcSigDevR4Cadence,
pktcSigDevR5Cadence,
pktcSigDevR6Cadence, pktcSigDevR6Cadence,
pktcSigDevR7Cadence, pktcSigDevR7Cadence,
pktcSigDevRgCadence,
pktcSigDevRsCadence,
pktcSigDefCallSigDscp, pktcSigDefCallSigDscp,
pktcSigDefMediaStreamDscp, pktcSigDefMediaStreamDscp,
pktcSigDevVmwiMode, pktcSigDevVmwiMode,
pktcSignalingType, pktcSignalingType,
pktcSignalingVersion, pktcSignalingVersion,
pktcSignalingVendorExtension, pktcSignalingVendorExtension,
pktcSigDefNcsReceiveUdpPort, pktcSigDefNcsReceiveUdpPort
pktcSigServiceClassNameUS,
pktcSigServiceClassNameDS,
pktcSigServiceClassNameMask,
pktcSigNcsServiceFlowState,
pktcSigDevR1Cadence,
pktcSigDevR2Cadence,
pktcSigDevR3Cadence,
pktcSigDevR4Cadence,
pktcSigDevR5Cadence,
pktcSigDevRgCadence,
pktcSigDevRsCadence
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Group of objects for the common portion of the "Group of objects for the common portion of the
PacketCable Signaling MIB." PacketCable Signaling MIB."
::= { pktcSigGroups 1 } ::= { pktcSigGroups 1 }
pktcNcsGroup OBJECT-GROUP pktcNcsGroup OBJECT-GROUP
OBJECTS { OBJECTS {
pktcNcsEndPntConfigCallAgentId, pktcNcsEndPntConfigCallAgentId,
skipping to change at page 53, line 4 skipping to change at page 46, line 51
pktcNcsEndPntConfigMessageWaitingTO, pktcNcsEndPntConfigMessageWaitingTO,
pktcNcsEndPntConfigOffHookWarnToneTO, pktcNcsEndPntConfigOffHookWarnToneTO,
pktcNcsEndPntConfigRingingTO, pktcNcsEndPntConfigRingingTO,
pktcNcsEndPntConfigRingBackTO, pktcNcsEndPntConfigRingBackTO,
pktcNcsEndPntConfigReorderToneTO, pktcNcsEndPntConfigReorderToneTO,
pktcNcsEndPntConfigStutterDialToneTO, pktcNcsEndPntConfigStutterDialToneTO,
pktcNcsEndPntConfigTSMax, pktcNcsEndPntConfigTSMax,
pktcNcsEndPntConfigMax1, pktcNcsEndPntConfigMax1,
pktcNcsEndPntConfigMax2, pktcNcsEndPntConfigMax2,
pktcNcsEndPntConfigMax1QEnable, pktcNcsEndPntConfigMax1QEnable,
PacketCable/IPCablecom NCS Signaling MIB February 2004
pktcNcsEndPntConfigMax2QEnable, pktcNcsEndPntConfigMax2QEnable,
pktcNcsEndPntConfigMWD, pktcNcsEndPntConfigMWD,
pktcNcsEndPntConfigTdinit, pktcNcsEndPntConfigTdinit,
pktcNcsEndPntConfigTdmin, pktcNcsEndPntConfigTdmin,
pktcNcsEndPntConfigTdmax, pktcNcsEndPntConfigTdmax,
PacketCable/IPCablecom NCS Signaling MIB February 2004
pktcNcsEndPntConfigRtoMax, pktcNcsEndPntConfigRtoMax,
pktcNcsEndPntConfigRtoInit, pktcNcsEndPntConfigRtoInit,
pktcNcsEndPntConfigLongDurationKeepAlive, pktcNcsEndPntConfigLongDurationKeepAlive,
pktcNcsEndPntConfigThist, pktcNcsEndPntConfigThist,
pktcNcsEndPntConfigStatus, pktcNcsEndPntConfigStatus,
pktcNcsEndPntConfigCallWaitingMaxRep, pktcNcsEndPntConfigCallWaitingMaxRep,
pktcNcsEndPntConfigCallWaitingDelay, pktcNcsEndPntConfigCallWaitingDelay,
pktcNcsEndPntStatusCallIpAddressType, pktcNcsEndPntStatusCallIpAddressType,
pktcNcsEndPntStatusCallIpAddress, pktcNcsEndPntStatusCallIpAddress,
pktcNcsEndPntStatusError pktcNcsEndPntStatusError
skipping to change at page 53, line 39 skipping to change at page 47, line 34
pktcInternationalGroup OBJECT-GROUP pktcInternationalGroup OBJECT-GROUP
OBJECTS { OBJECTS {
pktcNcsEndPntConfigMinHookFlash, pktcNcsEndPntConfigMinHookFlash,
pktcNcsEndPntConfigMaxHookFlash, pktcNcsEndPntConfigMaxHookFlash,
pktcNcsEndPntConfigPulseDialInterdigitTime, pktcNcsEndPntConfigPulseDialInterdigitTime,
pktcNcsEndPntConfigPulseDialMinMakeTime, pktcNcsEndPntConfigPulseDialMinMakeTime,
pktcNcsEndPntConfigPulseDialMaxMakeTime, pktcNcsEndPntConfigPulseDialMaxMakeTime,
pktcNcsEndPntConfigPulseDialMinBreakTime, pktcNcsEndPntConfigPulseDialMinBreakTime,
pktcNcsEndPntConfigPulseDialMaxBreakTime, pktcNcsEndPntConfigPulseDialMaxBreakTime,
pktcSigDevRingCadence, pktcSigDevRingCadence,
pktcSigDevStandardRingCadence,
pktcSigDevRingSplashCadence,
pktcSigDevCallerIdSigProtocol, pktcSigDevCallerIdSigProtocol,
pktcSigDevCIDMode, pktcSigDevCIDMode,
pktcSigDevCIDFskAfterRing, pktcSigDevCIDFskAfterRing,
pktcSigDevCIDFskAfterDTAS, pktcSigDevCIDFskAfterDTAS,
pktcSigDevCIDFskAfterRPAS, pktcSigDevCIDFskAfterRPAS,
pktcSigDevCIDRingAfterFSK, pktcSigDevCIDRingAfterFSK,
pktcSigDevCIDDTASAfterLR, pktcSigDevCIDDTASAfterLR,
pktcSigDevVmwiFskAfterDTAS, pktcSigDevVmwiFskAfterDTAS,
pktcSigDevVmwiFskAfterRPAS, pktcSigDevVmwiFskAfterRPAS,
pktcSigDevVmwiDTASAfterLR, pktcSigDevVmwiDTASAfterLR,
pktcSigPowerRingFrequency, pktcSigPowerRingFrequency,
pktcSigPulseSignalType, pktcSigPulseSignalType,
pktcSigPulseSignalFrequency, pktcSigPulseSignalFrequency,
pktcSigPulseSignalDbLevel, pktcSigPulseSignalDbLevel,
pktcSigPulseSignalDuration, pktcSigPulseSignalDuration,
PacketCable/IPCablecom NCS Signaling MIB February 2004
pktcPulseSignalPulseInterval, pktcPulseSignalPulseInterval,
pktcSigPulseSignalRepeatCount, pktcSigPulseSignalRepeatCount,
pktcSigDevToneDbLevel, pktcSigDevToneDbLevel,
pktcSigDevToneFreqType, pktcSigDevToneFreqType,
pktcSigDevToneNumFrequencies, pktcSigDevToneNumFrequencies,
pktcSigDevToneFirstFrequency, pktcSigDevToneFirstFrequency,
pktcSigDevToneSecondFrequency, pktcSigDevToneSecondFrequency,
PacketCable/IPCablecom NCS Signaling MIB February 2004
pktcSigDevToneThirdFrequency, pktcSigDevToneThirdFrequency,
pktcSigDevToneFourthFrequency, pktcSigDevToneFourthFrequency,
pktcSigDevToneNumOnOffTimes, pktcSigDevToneNumOnOffTimes,
pktcSigDevToneFirstToneOn, pktcSigDevToneFirstToneOn,
pktcSigDevToneFirstToneOff, pktcSigDevToneFirstToneOff,
pktcSigDevToneSecondToneOn, pktcSigDevToneSecondToneOn,
pktcSigDevToneSecondToneOff, pktcSigDevToneSecondToneOff,
pktcSigDevToneThirdToneOn, pktcSigDevToneThirdToneOn,
pktcSigDevToneThirdToneOff, pktcSigDevToneThirdToneOff,
pktcSigDevToneFourthToneOn, pktcSigDevToneFourthToneOn,
skipping to change at page 54, line 39 skipping to change at page 48, line 32
DESCRIPTION DESCRIPTION
" Group of objects that extend the behavior of existing " Group of objects that extend the behavior of existing
objects to support operations in the widest possible set objects to support operations in the widest possible set
of international marketplaces. Note that many of these of international marketplaces. Note that many of these
objects represent a superset of behaviors described in objects represent a superset of behaviors described in
other objects within this MIB Module." other objects within this MIB Module."
::= { pktcSigGroups 3 } ::= { pktcSigGroups 3 }
END END
5. Acknowledgments 5.
Acknowledgments
This document is a production of the PacketCable Working Group. This document is a production of the PacketCable Working Group.
The current editors wish to express gratitude to: The current editors wish to express gratitude to:
Angela Lyda Arris Interactive Angela Lyda Arris Interactive
Sasha Medvinsky Motorola Sasha Medvinsky Motorola
Roy Spitzer Telogy Networks, Inc. Roy Spitzer Telogy Networks, Inc.
Rick Vetter Motorola Rick Vetter Motorola
Itay Sherman Texas Instruments Itay Sherman Texas Instruments
Klaus Hermanns Cisco Systems Klaus Hermanns Cisco Systems
Eugene Nechamkin Broadcom Corp Eugene Nechamkin Broadcom Corp
Matt A. Osman CableLabs Matt A. Osman CableLabs
Jean-Francois Mule CableLabs Jean-Francois Mule CableLabs
Rich Woundy Comcast Rich Woundy Comcast
Bert Wijnen Lucent Bert Wijnen Lucent
PacketCable/IPCablecom NCS Signaling MIB February 2004
Mike Heard Consultant Mike Heard Consultant
6. Normative References 6.
Normative References
[RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
Rose, M. and S. Waldbusser, "Structure of Management Rose, M. and S. Waldbusser, "Structure of Management
Information Version 2 (SMIv2)", STD 58, RFC 2578, April Information Version 2 (SMIv2)", STD 58, RFC 2578, April
PacketCable/IPCablecom NCS Signaling MIB February 2004
1999. 1999.
[RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
Rose, M. and S. Waldbusser, "Textual Conventions for Rose, M. and S. Waldbusser, "Textual Conventions for
SMIv2", STD 58, RFC 2579, April 1999. SMIv2", STD 58, RFC 2579, April 1999.
[RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
Rose, M. and S. Waldbusser, "Conformance Statements for Rose, M. and S. Waldbusser, "Conformance Statements for
SMIv2", STD 58, RFC 2580, April 1999. SMIv2", STD 58, RFC 2580, April 1999.
skipping to change at page 55, line 53 skipping to change at page 49, line 46
[PKT-SP-MGCP-IO9-040113] Packetcable Network-Based Call Signaling [PKT-SP-MGCP-IO9-040113] Packetcable Network-Based Call Signaling
Protocol Specification PKT-SP-EC-MGCP- Protocol Specification PKT-SP-EC-MGCP-
IO9-040113. IO9-040113.
[PKT-SP-PROV-IO8-040113] Packetcable MTA Device Provisioning [PKT-SP-PROV-IO8-040113] Packetcable MTA Device Provisioning
Specification PKT-SP-PROV-IO8-040113. Specification PKT-SP-PROV-IO8-040113.
[PKT-SP-CODEC-IO5-040113] Packetcable Audio/Video Codecs [PKT-SP-CODEC-IO5-040113] Packetcable Audio/Video Codecs
Specification PKT-SP-CODEC-IO5-040113. Specification PKT-SP-CODEC-IO5-040113.
7. Informative References 7.
Informative References
[RFC3261] Rosenberg, J., Schulzrinne H., Camarillo, G., Johnston, [RFC3261] Rosenberg, J., Schulzrinne H., Camarillo, G., Johnston,
PacketCable/IPCablecom NCS Signaling MIB February 2004
A., Peterson, J., Sparks, R., Handley, M., and Schooler, A., Peterson, J., Sparks, R., Handley, M., and Schooler,
E. "SIP: Session Initiation Protocol", RFC 3261, June E. "SIP: Session Initiation Protocol", RFC 3261, June
2002. 2002.
[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.
PacketCable/IPCablecom NCS Signaling MIB February 2004
[RFC3435] Andreasen, F., Foster, B., "Media Gateway Control Protocol [RFC3435] Andreasen, F., Foster, B., "Media Gateway Control Protocol
(MGCP)", RFC 3435, January 2003. (MGCP)", RFC 3435, January 2003.
[PKT-SP-MIB-MTA-I08-040113] Packetcable MTA MIB Specification PKT- [PKT-SP-MIB-MTA-I08-040113] Packetcable MTA MIB Specification PKT-
SP-MIB-MTA-I08-040113. SP-MIB-MTA-I08-040113.
[ETSI TS 101 909-4] ETSI TS 101 909-4:"Access and Terminals (AT); [ETSI TS 101 909-4] ETSI TS 101 909-4:"Access and Terminals (AT);
Digital Broadband Cable Access to the Public Digital Broadband Cable Access to the Public
Telecommunications Network; IP Multimedia Time Telecommunications Network; IP Multimedia Time
Critical Services; Part 4: Network Call Critical Services; Part 4: Network Call
skipping to change at page 57, line 5 skipping to change at page 50, line 49
(PSTN); Subscriber line protocol over the local loop (PSTN); Subscriber line protocol over the local loop
for display (and related) services; Part 1: On hook for display (and related) services; Part 1: On hook
data transmission". data transmission".
[ITU-T E.180] ITU-T: "Various Tones Used in National Networks, [ITU-T E.180] ITU-T: "Various Tones Used in National Networks,
Supplement 2 to Recommendation E.180". Supplement 2 to Recommendation E.180".
[TR 101 183] TR 101 183: "Public Switched Telephone Network (PSTN) [TR 101 183] TR 101 183: "Public Switched Telephone Network (PSTN)
Analogue Ringing Signals". Analogue Ringing Signals".
PacketCable/IPCablecom NCS Signaling MIB February 2004 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
PacketCable/IPCablecom NCS Signaling MIB February 2004
environment without proper protection can have a negative effect on environment without proper protection can have a negative effect on
network operations. network operations.
The following Differentiated Services Code Point (DSCP) and mask The following Differentiated Services Code Point (DSCP) and mask
objects are used to differentiate between various types of traffic objects are used to differentiate between various types of traffic
in the service provider network: in the service provider network:
pktcSigDefCallSigDscp pktcSigDefCallSigDscp
pktcSigDefMediaStreamDscp pktcSigDefMediaStreamDscp
pktcSigServiceClassNameMask
These objects may contain information that may be sensitive from a These objects may contain information that may be sensitive from a
business perspective. For example, they may represent a customer's business perspective. For example, they may represent a customer's
service contract that a service provider chooses to apply to a service contract that a service provider chooses to apply to a
customer's ingress or egress traffic. If these objects are SET customer's ingress or egress traffic. If these objects are SET
maliciously, it may permit unmarked or inappropriately marked maliciously, it may permit unmarked or inappropriately marked
signaling and media traffic to enter the service provider network, signaling and media traffic to enter the service provider network,
resulting in unauthorized levels of service for customers. resulting in unauthorized levels of service for customers.
The following objects determine ring cadence, repeatable The following objects determine ring cadence, repeatable
skipping to change at page 58, line 5 skipping to change at page 51, line 47
pktcSigDevRgCadence pktcSigDevRgCadence
pktcSigDevRsCadence pktcSigDevRsCadence
pktcSigDevCallerIdSigProtocol pktcSigDevCallerIdSigProtocol
pktcSigPulseSignalDuration pktcSigPulseSignalDuration
pktcSigPulseSignalPauseDuration pktcSigPulseSignalPauseDuration
If these objects are SET maliciously, it may result in unwanted If these objects are SET maliciously, it may result in unwanted
operation, or a failure to obtain telephony service from client operation, or a failure to obtain telephony service from client
(MTA) devices. (MTA) devices.
PacketCable/IPCablecom NCS Signaling MIB February 2004
The objects in the pktcNcsEndPntConfigTable are used for end point The objects in the pktcNcsEndPntConfigTable are used for end point
signaling. The pktcNcsEndPntConfigCallAgentId object contains the signaling. The pktcNcsEndPntConfigCallAgentId object contains the
name of the call agent, which includes the call agent FQDN. If this name of the call agent, which includes the call agent FQDN. If this
object is SET maliciously, the MTA will not be able to communicate object is SET maliciously, the MTA will not be able to communicate
with the call agent, resulting in a disruption of telephony service. with the call agent, resulting in a disruption of telephony service.
The pktcNcsEndPntConfigCallAgentUdpPort object identifies the UDP The pktcNcsEndPntConfigCallAgentUdpPort object identifies the UDP
port for NCS signaling traffic. If this object is SET maliciously, port for NCS signaling traffic. If this object is SET maliciously,
the call agent will not receive NCS signaling traffic from the MTA, the call agent will not receive NCS signaling traffic from the MTA,
also resulting in a disruption of telephony service. also resulting in a disruption of telephony service.
PacketCable/IPCablecom NCS Signaling MIB February 2004
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.
SNMP versions prior to SNMPv3 did not include adequate security. SNMP versions prior to SNMPv3 did not include adequate security.
skipping to change at page 58, line 45 skipping to change at page 52, line 35
authentication and privacy). authentication and privacy).
Further, deployment of SNMP versions prior to SNMPv3 is NOT Further, deployment of SNMP versions prior to SNMPv3 is NOT
RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to
enable cryptographic security. It is then a customer/operator enable cryptographic security. It is then a customer/operator
responsibility to ensure that the SNMP entity giving access to an responsibility to ensure that the SNMP entity giving access to an
instance of this MIB module is properly configured to give access to instance of this MIB module is properly configured to give access to
the objects only to those principals (users) that have legitimate the objects only to those principals (users) that have legitimate
rights to indeed GET or SET (change/create/delete) them. rights to indeed GET or SET (change/create/delete) them.
9. Intellectual Property 9.
IANA Considerations
No IANA actions are required by this document.
10.
Intellectual Property
The IETF takes no position regarding the validity or scope of any The IETF takes no position regarding the validity or scope of any
intellectual property or other rights that might be claimed to Intellectual Property Rights or other rights that might be claimed
pertain to the implementation or use of the technology described in to pertain to the implementation or use of the technology described
this document or the extent to which any license under such rights in this document or the extent to which any license under such
might or might not be available; neither does it represent that it rights might or might not be available; nor does it represent that
has made any effort to identify any such rights. Information on the it has made any independent effort to identify any such rights.
IETF's procedures with respect to rights in standards-track and Information on the procedures with respect to rights in RFC
standards-related documentation can be found in BCP-11. Copies of documents can be found in BCP 78 and BCP 79.
claims of rights made available for publication and any assurances
Copies of IPR disclosures made to the IETF Secretariat and any
assurances of licenses to be made available, or the result of an
attempt made to obtain a general license or permission for the use
of such proprietary rights by implementers or users of this
PacketCable/IPCablecom NCS Signaling MIB February 2004 PacketCable/IPCablecom NCS Signaling MIB February 2004
of licenses to be made available, or the result of an attempt made specification can be obtained from the IETF on-line IPR repository
to obtain a general license or permission for the use of such at http://www.ietf.org/ipr.
proprietary rights by implementers or users of this specification
can be obtained from the IETF Secretariat.
The IETF invites any interested party to bring to its attention any The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary copyrights, patents or patent applications, or other proprietary
rights which may cover technology that may be required to practice rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF Executive this standard. Please address the information to the IETF at
Director. ipr@ietf.org.
10. Authors' Addresses 11.
Authors' Addresses
Gordon Beacham Gordon Beacham
Motorola BCS/DCG Motorola BCS/DCG
6450 Sequence Drive, Bldg. 1 6450 Sequence Drive, Bldg. 1
San Diego, CA 92121, USA San Diego, CA 92121, USA
+1 858-404-2335 +1 858-404-2335
gordon.beacham@motorola.com gordon.beacham@motorola.com
Satish Kumar Mudugere Eswaraiah Satish Kumar Mudugere Eswaraiah
Texas Instruments India (P) Ltd., Texas Instruments India (P) Ltd.,
skipping to change at page 59, line 43 skipping to change at page 53, line 42
satish.kumar@ti.com satish.kumar@ti.com
Sumanth Channabasappa Sumanth Channabasappa
Alopa Networks Inc Alopa Networks Inc
248, McCaslin Bvld #101, 248, McCaslin Bvld #101,
Louisville, Colorado - 80027 Louisville, Colorado - 80027
U.S.A. U.S.A.
+1 303 604 6595 +1 303 604 6595
Sumanth@alopa.com Sumanth@alopa.com
11. Full Copyright Statement 12.
Full Copyright Statement
The IETF takes no position regarding the validity or scope of any
intellectual property or other rights that might be claimed to
pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights
might or might not be available; neither does it represent that it
has made any effort to identify any such rights. Information on the
IETF's procedures with respect to rights in standards-track and
standards-related documentation can be found in BCP-11. Copies of
claims of rights made available for publication and any assurances
of licenses to be made available, or the result of an attempt made
to obtain a general license or permission for the use of such
PacketCable/IPCablecom NCS Signaling MIB February 2004
proprietary rights by implementers or users of this specification
can be obtained from the IETF Secretariat.
The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary
rights which may cover technology that may be required to practice
this standard. Please address the information to the IETF Executive
Director.
Copyright (C) The Internet Society (2004). All Rights Reserved.
This document and translations of it may be copied and furnished to
others, and derivative works that comment on or otherwise explain it
or assist in its implmentation may be prepared, copied, published
and distributed, in whole or in part, without restriction of any
kind, provided that the above copyright notice and this paragraph
are included on all such copies and derivative works. However, this
document itself may not be modified in any way, such as by removing
the copyright notice or references to the Internet Society or other
Internet organizations, except as needed for the purpose of
developing Internet standards in which case the procedures for
copyrights defined in the Internet Standards process must be
followed, or as required to translate it into languages other than
English.
The limited permissions granted above are perpetual and will not be Copyright (C) The Internet Society (2004). This document is subject
revoked by the Internet Society or its successors or assigns. to the rights, licenses and restrictions contained in BCP 78, and
except as set forth therein, the authors retain all their rights.
This document and the information contained herein is provided on an This document and the information contained herein are provided on
"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE
TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE
BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR
HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
 End of changes. 

This html diff was produced by rfcdiff 1.23, available from http://www.levkowetz.com/ietf/tools/rfcdiff/