Nortel-MsCarrier-MscPassport-VnetMcdnSigMIB: View SNMP OID List / Download MIB

This entry controls the addition and deletion of mscSigChanMcdn components.

A single entry in the table represents a single mscSigChanMcdn component.

This variable is used as the basis for SNMP naming of mscSigChanMcdn components. These components can be added and deleted.

This variable provides the component's string name for use with the ASCII Console Interface

This variable represents the storage type value for the mscSigChanMcdn tables.

This variable represents the index for the mscSigChanMcdn tables.

This entry controls the addition and deletion of mscSigChanMcdnFramer components.

A single entry in the table represents a single mscSigChanMcdnFramer component.

This variable is used as the basis for SNMP naming of mscSigChanMcdnFramer components. These components cannot be added nor deleted.

This variable provides the component's string name for use with the ASCII Console Interface

This variable represents the storage type value for the mscSigChanMcdnFramer tables.

This variable represents the index for the mscSigChanMcdnFramer tables.

This group contains the base provisioning data for the Framer component. Application or hardware interface specific provisioning data is contained in other provisionable Framer groups.

An entry in the mscSigChanMcdnFramerProvTable.

This attribute contains a hardware component name. The attribute associates the application with a specific link. This defines the module processor on which Framer's parent component (as well as Framer itself) will run.

This group contains the three OSI State attributes. The descriptions generically indicate what each state attribute implies about the component. Note that not all the values and state combinations described here are supported by every component which uses this group. For component-specific information and the valid state combinations, refer to NTP 241-7001-150, Passport Operations and Maintenance Guide.

An entry in the mscSigChanMcdnFramerStateTable.

This attribute indicates the OSI Administrative State of the component. The value locked indicates that the component is administratively prohibited from providing services for its users. A Lock or Lock - force command has been previously issued for this component. When the value is locked, the value of usageState must be idle. The value shuttingDown indicates that the component is administratively permitted to provide service to its existing users only. A Lock command was issued against the component and it is in the process of shutting down. The value unlocked indicates that the component is administratively permitted to provide services for its users. To enter this state, issue an Unlock command to this component. Enumeration: 'locked': 0, 'shuttingDown': 2, 'unlocked': 1.

This attribute indicates the OSI Operational State of the component. The value enabled indicates that the component is available for operation. Note that if adminState is locked, it would still not be providing service. The value disabled indicates that the component is not available for operation. For example, something is wrong with the component itself, or with another component on which this one depends. If the value is disabled, the usageState must be idle. Enumeration: 'disabled': 0, 'enabled': 1.

This attribute indicates the OSI Usage State of the component. The value idle indicates that the component is not currently in use. The value active indicates that the component is in use and has spare capacity to provide for additional users. The value busy indicates that the component is in use and has no spare operating capacity for additional users at this time. Enumeration: 'active': 1, 'idle': 0, 'busy': 2.

This group contains the operational statistics data for a Framer component.

An entry in the mscSigChanMcdnFramerStatsTable.

This attribute counts the number of frames transmitted to the link interface by Framer. This count wraps to zero after reaching its maximum value.

This attribute counts the number of frames received from the link interface by Framer. This count wraps to zero after reaching its maximum value.

This attribute counts the number of bytes received from the link interface by Framer. This count wraps to zero when it exceeds its maximum value.

This attribute counts the total number of aborts received. This count wraps to zero after reaching its maximum value.

This attribute counts the total number of frames with CRC errors. This count wraps to zero after reaching its maximum value.

This attribute counts the total number of frames with LRC errors. This count wraps to zero after reaching its maximum value.

This attribute counts the total number of frames that were non octet aligned. This count wraps to zero after reaching its maximum value.

This attribute counts the total number of frames received from the link for which overruns occurred. This count wraps to zero after reaching its maximum value.

This attribute counts the total number of frames transmitted to the link for which underruns occurred. This count wraps to zero after reaching its maximum value.

This attribute counts the total number of frames received which were too large (longer than 500 bytes). This count wraps to zero after reaching its maximum value.

This group specifies the provisionable layer 2 attributes of the Q.931 ITU-T protocol.

An entry in the mscSigChanMcdnL2Table.

This attribute specifies the layer 2 enable request timer.

This attribute specifies the maximum time between a layer 2 frame and its acknowledgment.

This attribute specifies the maximum number of re-transmissions of a layer 2 frame.

This attribute specifies the maximum time for which layer 2 frames may be absent. Expiry triggers a check on whether the far end is alive.

This attribute specifies the maximum number of sequentially numbered I frames (that is, window size (k)) that may be unacknowledged at any given time for a SAP supporting primary rate (64kbit/sec) signalling.

This group represents the provisionable Layer 3 timer attributes of the MCDN signalling protocol.

An entry in the mscSigChanMcdnL3Table.

This attribute specifies the overlap receiving timer; in a UNI, this is network to user, but for Peer to Peer it is all incoming calls. This attribute is ignored if overlap signalling is disabled.

This attribute specifies the overlap sending timer; in a UNI, this is user to network, but for Peer to Peer it is all outgoing calls. This attribute is ignored if overlap signalling is disabled.

This attribute specifies the data link disconnect timer; used to ride out temporary failures.

This attribute specifies the call proceeding state timer.

This attribute specifies the restart request response timer. It must be set greater than t317.

This attribute specifies the restart operation timer, used when a RESTART was received.

This group defines the general options of the D-channel signalling link.

An entry in the mscSigChanMcdnProvTable.

This attribute specifies whether the interface provides layer 2 and 3 services equivalent to the ITU-T network or user side of the connection. If this attribute is set to network, then the interface is master during channel negotiation, and uses network side layer 2 command/response bits. If this attribute is set to user, then the interface is slave during channel negotiation, and uses user side layer 2 command/response bits. Note that although a peer to peer protocol has no true network or user side, for channel negotiation and layer 2 handling the peer to peer and UNI protocols have identical function. A true UNI may also have uni-directional messages and/or message elements; the peer to peer has all elements bidirectional. Enumeration: 'network': 1, 'user': 2.

This attribute specifies the maximum number of simultaneous active non-call transactions that are allowed.

This attribute specifies whether overlap sending to the PBX is enabled. Enumeration: 'disabled': 1, 'enabled': 0.

This attribute specifies whether overlap receiving from the PBX is enabled. Enumeration: 'disabled': 1, 'enabled': 0.

This attribute specifies handling of channel maintenance events such as locking and unlocking a channel or channel registration on start-up. The decision here is whether to send individual channel RESTART messages, SERVICE messages, or nothing. Note that channel registration only occurs after the global interface restart at startup. The attribute controls start-up handling absolutely, and channel lock and unlock conditionally. That is, setting this to enable SERVICE messages ensures SERVICE messages at start-up and whenever a channel goes into or out of service. However, if this is not set to enable SERVICE messaging, a RESTART is always sent on unlocking a channel. globalOnStartup provides the minimum required function at start- up, without any individual channel confirmation. Note that when this is set, channel RESTART is still used for channel unlock. globalOnStartup applies to SigChan start-up only. serviceMessage enables sending and receiving SERVICE messages. If enabled, SERVICE messages are always used for channel maintenance on channel lock, channel unlock and start-up. restartMessage provides individual channel RESTARTs when a SigChan starts up. If enabled, the RESTART is used at start-up and channel unlock. However, if both SERVICE and RESTART messages are disabled, the RESTART will still be used when a channel unlocks. Enumeration: 'serviceMessage': 1, 'restartMessage': 2, 'globalOnStartup': 0.

This group contains the three OSI State attributes. The descriptions generically indicate what each state attribute implies about the component. Note that not all the values and state combinations described here are supported by every component which uses this group. For component-specific information and the valid state combinations, refer to NTP 241-7001-150, Passport Operations and Maintenance Guide.

An entry in the mscSigChanMcdnStateTable.

This attribute indicates the OSI Administrative State of the component. The value locked indicates that the component is administratively prohibited from providing services for its users. A Lock or Lock - force command has been previously issued for this component. When the value is locked, the value of usageState must be idle. The value shuttingDown indicates that the component is administratively permitted to provide service to its existing users only. A Lock command was issued against the component and it is in the process of shutting down. The value unlocked indicates that the component is administratively permitted to provide services for its users. To enter this state, issue an Unlock command to this component. Enumeration: 'locked': 0, 'shuttingDown': 2, 'unlocked': 1.

This attribute indicates the OSI Operational State of the component. The value enabled indicates that the component is available for operation. Note that if adminState is locked, it would still not be providing service. The value disabled indicates that the component is not available for operation. For example, something is wrong with the component itself, or with another component on which this one depends. If the value is disabled, the usageState must be idle. Enumeration: 'disabled': 0, 'enabled': 1.

This attribute indicates the OSI Usage State of the component. The value idle indicates that the component is not currently in use. The value active indicates that the component is in use and has spare capacity to provide for additional users. The value busy indicates that the component is in use and has no spare operating capacity for additional users at this time. Enumeration: 'active': 1, 'idle': 0, 'busy': 2.

This group provides the operational components for the McdnSig component.

An entry in the mscSigChanMcdnStatsTable.

This attribute counts the total number of calls that have been made to the interface. The value wraps when it reaches its maximum.

This attribute counts the total number of calls from the interface. The value wraps when it reaches its maximum.

This attribute counts the total number of non-call associated sessions to the interface. The value wraps when it reaches its maximum.

This attribute counts the total number of non-call associated sessions from the interface. The value wraps when it reaches its maximum.

This group provides the operational attributes for the MCDN signalling.

An entry in the mscSigChanMcdnOperTable.

This attribute indicates the number of currently active channels. This includes data and voice channels.

This attribute indicates the number of channels that are currently carrying voice.

This attribute indicates the number of channels that are currently carrying data. This does not include modem data.

This attribute indicates the maximum number of channels that have been active on this signalling channel during the last polling period.

This attribute indicates the maximum number of voice channels that have been active on this signalling channel during the last polling period.

This attribute indicates the maximum number of data channels that have been active on this signalling channel during the last polling period.

This attribute indicates the state of the D-channel. outOfService means that there is no layer 2 or layer 3 connectivity to the PBX. establishing means that the signalling channel is attempting to stage the layer 2. established means that the layer 2 is enabled. If the signalling channel stays in the established state, then it is waiting for a restart from the PBX. enabling means that the resources for processing calls are being initialized. If the signalling channel stays in the enabling state then it is waiting for a restart acknowledgement from the PBX. inService means that the resources for processing calls are available. restarting means that the resources for call processing are being rei- initialized. Enumeration: 'outOfService': 0, 'established': 2, 'establishing': 1, 'enabling': 3, 'restarting': 5, 'inService': 4.

This contains a series of operational attributes which turn on and off several kinds of tracing.

An entry in the mscSigChanMcdnToolsTable.

This attribute defines which types of tracing are active for this signalling channel. The tracing messages are sent to the debug stream. To see the messages the agentQueue attribute in Col/debug must be greater than 0 and a Telnet NMIS session must list the debug stream in in its data streams (ex. set nmis telnet session/1 dataStreams debug). Different types of tracing can be enabled simultaneously. Note that tracing consumes additional CPU resources and will slow down call processing on a heavily loaded card. If there is message block exhaustion tracing will be suspended for a period and then automatically reenabled. An alarm is generated on tracing suspension and resumption. This mechanism protects the function processor against excessive numbers of tracing messages. Types of tracing include: protocolErrors - get details of any protocol errors which are occuring. Protocol errors are also reported in summary form as alarms. q931Summary - Summary of the Q.931 messages on the signalling link, including certain call details (calling number, called number, release codes). q931Hex - Q.931 messages displayed in hex format. Useful to determine protocol compliance in case of errors reported on local or remote ends. q931Symbolic - Q.931 messages parsed to give maximum detail. Useful for understanding content of messages flowing on the link. portHex - Messages in hex format being sent and received on the link. Description of bits: protocolErrors(0) q931Summary(1) q931Hex(2) q931Symbolic(3) portHex(4)

This attribute specifies the type of ISDN messages that are to be traced. Description of bits: alerting(0) callProceeding(1) connectionlessFacility(2) congestionControl(3) connect(4) connectAcknowledge(5) disconnect(6) facility(7) facilityAcknowledge(8) facilityReject(9) information(10) notify(11) progress(12) register(13) releaseComp(14) release(15) restart(16) restartAcknowledge(17) service(18) serviceAcknowledge(19) setup(20) setupAcknowledge(21) status(22) statusEnquiry(23) userInformation(24) all(25)

This attribute indicates whether the incoming (from PBX), outgoing (to PBX), or both incoming and outgoing messages are traced. Description of bits: incoming(0) outgoing(1)

This group enables and disables the support of the MCDN proprietary signalling for connectionless features on the local signalling channel.

An entry in the mscSigChanMcdnClsTable.

This attribute specifies the features to be supported by MCDN 'TCAP' connectionless messaging. Note that some features such as Network ACD combine connectionless and connection oriented. In the NACD case, the connectionless messaging enables the source and target PBXs to establish the networked relationship, and calls sent across the network (connection oriented) will contain basic information relating the call to the feature. Feature Definitions: networkAcd: transfer of a call from a pool of agents to a second pool of agents across the network. networkMessageService: message waiting capability (for example, lamps on sets). Also includes signalling for voice mail, but is not limited to voice mail. networkVoiceMail: a specific subset of Network Message Service, separated functionally as it always terminates on an interactive voice response mailbox application. networkRingAgain: ring again to remote sets. electronicLock: change of set capabilities by a remote user dialling the applicable code and password. remoteCallForward: call forwarding a phone via applicable code and password. callPickupNetworkWide (call pickup world wide): scan for a ringing call on another node, to enable the scanning set to pick up the call. networkPackage1: a collection of other features including but not limited to network clock synchronization. Note that on the Meridian 1, this is a general purpose group used for very small features not requiring a new ISDN Facility feature type. isdnApplicationInterface: network wide support of a number of Meridian 1 Application Module Link features. mobilityMultisiteNetworking: the capability to use a wireless phone in multiple sites, by having the phone register on arrival at the new site, and having the PBX at the new site negotiate the set 'relocation' with the base PBX. miscellaneous: Any feature that is not listed above. Description of bits: networkAcd(0) networkMessageService(1) networkRingAgain(2) networkVoiceMail(3) electronicLock(4) remoteCallForward(5) callPickupWorldWide(6) networkPackage1(7) isdnApplicationInterface(8) mobilityMultisiteNetworking(9) notused10(10) notused11(11) notused12(12) notused13(13) notused14(14) miscellaneous(15)

This group enables and disables the support of the MCDN proprietary signalling for the listed features on the local signalling channel.

An entry in the mscSigChanMcdnCoTable.

This attribute specifies if the Meridian 1 Drop Back Congestion Handling for trunks is enabled, and what type is being supported. Enumeration: 'noDropBackAllowed': 0, 'dropBackToPriorNode': 2, 'dropBackToOriginator': 1.

This attribute specifies what Name Display is supported. nd1 corresponds to the Meridian 1 RCAP (Remote CAPability) nd1. This translates as caller provides name info in SETUP, ringing party name in ALERTING, redirection name in NOTIFY, and answering party name in CONNECT (as applicable, and if the name changes). nd2 corresponds to the Meridian 1 RCAP (Remote CAPability) nd2. This translates as caller provides name info in SETUP, answering party provides name in NOTIFY on answer. nd3 corresponds to the Meridian 1 RCAP (Remote CAPability) nd3, which is nd1 plus name information in call clearing messages (busy user, etc.) where a specific user was found but either could not answer or cleared the call. This corresponds to the QSIG name display. Description of bits: nameDisplay1(0) nameDisplay2(1) nameDisplay3(2)

This attribute specifies whether to enable transport for the Meridian 1 Multisite Business Group IE. The Meridian 1 allows multiple 'Tenants' to exist on a single PBX. These Tenants have limited access to each other and to system resources. That is, users associated with 'Tenant group one' cannot use trunks, attendants, and features from another group, and so forth. The Multi-Site Business Group is a single Tenant existing on more than one PBX. As an example, 'tenant one' on a PBX may 'own' resources belonging to 'tenant one' on another PBX. The Multi-Site Business Group IE as used in the Meridian 1 Network Tenant Services feature enables linking the two tenants together. Enumeration: 'discard': 1, 'transport': 0.

This attribute indicates the features to be supported by MCDN 'ROSE' connection oriented messaging. Feature Definitions: networkAttendantService: network wide support of Attendant ('operator') services. classOfServiceTransport: this is not a ROSE feature. Class of Service transport takes place in the called party number when provisioned on the Meridian 1 to use an ESN signalling type. trunkRouteOptimization: dropping of redundant links in a call, when a set call forwards a call prior to answer. remoteVirtualQueuing: queuing at a remote node without requiring a B channel to be kept up. offHookQueuing: Queuing by maintaining the speech path to the queuing node. networkCallTrace: call progress tracing across a network (that is, call reached node a, node b, terminated at c,...). networkIntercom: network wide access to an intercom system onm a Meridian 1. callPickupNetworkWide: connection oriented messages associated with the TCAP call pickup scan operation. The messages that actually pick up the ringing call. radioPaging: access to a radio paging system network wide, allowing single radio paging facilities in a relatively dense local PBX network. networkAccess: information to enable access to PBX features from outside the network. Additional data is provided to identify access capabilities for a spoecific call. (Similar to transmittiong authorization code capabilities network wide.) antiTromboning: actually includes two capabilities - NAS (Network Attendant Setvice) and Trunk Anti-Tromboning. Calls that exit the subnet to a PBX and are transferred back to a network number via the same D channel can be optimized. If PBX A (Passport A) calls across the subnet to Passport B, D channel Z, to PBX B, and PBX B transfers across D channel Z to Passport B and therefore to PBX C/Passport C, this allows tha call to simplify to PBX/Passport A to PBX/Passport C. miscellaneous: Any feature that is not listed above. Description of bits: networkAttendantService(0) classOfServiceTransport(1) trunkRouteOptimization(2) remoteVirtualQueuing(3) networkCallId(4) offHookQueuing(5) networkCallTrace(6) networkIntercom(7) callPickupNetworkWide(8) radioPaging(9) networkAccess(10) antiTromboning(11) miscellaneous(12)