CISCO-XGCP-MIB: View SNMP OID List / Download MIB

This MIB is an enhancement for existing XGCP-MIB. xGCP is a set of protocols, for example SGCP (Simple Gateway Control Protocol) and MGCP (Media Gateway Control Protocol), which are designed as a control protocol within a distributed system that appears to the outside as a single VoIP/VoATM gateway. This system is composed of a call agent (or MGC, Media Gateway Controller) and of a set of 'media gateways' that perform the conversion of media signals between circuits and packets. In the xGCP model, the gateways focus on the audio signal translation function, while the call agent handles the signaling and call processing functions. Examples of Gateway Control Protocols are: * Simple Gateway Control Protocol (SGCP) * Media Gateway Control Protocol (MGCP) xGCP assumes a connection model where the basic constructs are: Endpoints : sources or sinks of data that could be physical or virtual. Connections : an association between two or more endpoints with the purpose of transmitting data between these endpoints. Once this association is established for both endpoints, data transfer between these endpoints can take place. Connections are grouped in calls. One or more connections can belong to one call. Connections and calls are set up at the initiative of one or several call agents. Terminologies used: AAL : ATM Adaptation Layer AUCX : Audit Connection Command used by the MGC to find out the status of a given gateway connection. AUEP : Audit Endpoint Command used by the MGC to find out the status of a given endpoint. CCAPI : Call Control Application Program Interface. CID : Channel Identifier CRCX : Connection Command from a MGC to request the gateway MG : Media Gateway MGC : Media Gateway Controller DLCX : Delete Command. This command can be initiated by either the MGC or gateway. GSM : Global System for Mobile Communications GW : Gateway. HP : Hairpin MDCX : Modify Connection Command from a MGC to request the gateway NSE : Negative Stuffing Event NTFY : A Notify Command sent from a gateway to a MGC in response to a RQNT command. PSTN : Public Switched Telephone Network RQNT : Request To Nofity Command from a MGC to request the gateway to provide a notification for configuration changes. RSIP : Restart in Progress Command. This command can be initiated by either the MGC or gateway. SPRT : Simple Packet Relay Transport SSE : Silicon Switching Engine TDM : Time Division Multiplexing TGW : Target Gateway TWC : Three Way Calling VCCI : Virtual Circuit Connection Identifier VMG : Virtual Media Gateway. It is a logical representation of a module (or a set of modules) that has MG functionality. There could be multiple VMGs in a device. VoAAL2 : Voice over AAL2

This is a table which is used to provision a MGC or MGC group for a MG. Each entry corresponds to a MGC or a MGC group for a single MG.

Each row corresponds to a MGC or a group of MGCs for a media gateway.

This object specifies which MGC Redundant Group will be used in XGCP. The value of this object refers to the object cMgcGrpIndex from MGC Redundant Group Table, cMgcGrpParamTable. There are two conditions to associate a MGC group: 1. At least one MGC is associated with the MGC group 2. At least one protocol is associated with the MGC group If the value of the object is non-zero, it means the media gateway has a MGC Redundant Group. In the call setup, the parameters of call agents within the MGC Redundant Group will be sequentially tried according to its preference. This object cXgcpMgcConfigMgcGrpNum and object cXgcpMgcConfigAddress are mutually exclusive. The object cXgcpMgcConfigAddress can be set only when the object cXgcpMgcConfigMgcGrpNum is equal to 0. If the value of the object is 0, which means there is no MGC Redundant Group associated with the media gateway. It has only one call agent (in media gateway level) to communicate with. This call agent is indicated by cXgcpMgcConfigAddress and will be used in call setup (if call set-up on media gateway level).

This object specifies the address type of the MGC (object cXgcpMgcConfigAddress), either ipv4 or ipv6.

This object specifies the address of the MGC the gateway used to communicate with in call setup. This object cXgcpMgcConfigAddress and object cXgcpMgcConfigMgcGrpNum are mutually exclusive. The object cXgcpMgcConfigAddress can be set only when the object cXgcpMgcConfigMgcGrpNum is equal to 0. Otherwise, the SET will be rejected with error.

This object specifies which protocol that the MG should use to communicate with the MGC when it try to set up the call. The value of this object is the same as the value of object cMediaGwProtocolIndex from protocol table (cMediaGwProtocolTable). If the value of cXgcpMgcConfigMgcGrpNum is non-zero, this object will be ignored because the protocol will be determined by the MGC group. The initial value is 1, means the system should have at least one default protocol between the gateway and the MGC created in the cMeidaGwProtocolTable when the system is initialized.

The UDP port of the MG which is used to communicate with call agent in MGCP.

This table is used to provision xGCP configuration in a MG.

Each entry represents the xGCP attributes for a media gateway. An entry is created when the system detects the XGCP stack at system start-up. Accordingly, the existing entry shall be deleted when the system can't locate the XGCP stack at system start-up.

The request timeout is the period that the XGCP protocol waits before retransmitting an unacknowledged message. It is the responsibility of the requesting entity to provide suitable timeouts for all outstanding commands, and to retry commands when timeouts exceeded.

This object specifies the number of retries for a request that exceeds timeout without acknowledge before it tries to connect to another MGC.

This object specifies command retry method.

This object specifies the maximum timeout for exponential command retry by the media gateway.

The maximum waiting delay (MWD) timeout value is used for the media gateway to send the first Restart In Progress to the MGC. When a gateway is powered on, it should initiate a restart timer to a random value, uniformly distributed between 0 and a maximum waiting delay (MWD). The gateway should send the first RSIP message when the timer expires. The initial value of this object is chosen in an implementation-dependent manner by the MGCP functionality based on the call volume of the system.

This object specifies the Restart Delay Timeout for the restart process for a gateway to send out RestartInProgress when it is powered on or been reset. The purpose of setting the Restart Delay timer before sending the RestartInProgress notification to the media gateway controller is to avoid the network congestion during the critical period of service restoration.

This object represents the default capability package supported in the gateway. packageDC ( 1) - Don't Care package packageG ( 2) - Generic package packageD ( 3) - DTMF package packageM ( 4) - MF package packageT ( 5) - Trunk package packageL ( 6) - Line package packageH ( 7) - Handset package packageR ( 8) - RTP package packageN ( 9) - NAS package packageA (l0) - Announcement Server package packageS (11) - Script package packageATM (12) - ATM package packageMS (13) - MF CAS package packageDT (14) - DTMF CAS package packageMO (15) - MO package packageRES (16) - RES package packageSASDI(17) - ASDI package (S) NCS packageIT (18) - IT package (S) TGCP packageMT (19) - MT package packageB (20) - B package packageSST (21) - SST package packageMDR (22) - MDR package packageFXR (23) - FAX package packageBA (24) - Bulk Audit package packageMD (25) - MD package packageNAS (26) - Network Access Server package packageMDSTE(27) - Modem relay Secure Telephone Equipment package packagePRE (28) - PRE package packageLCS (29) - MGCP Line Control Signaling package packageSRTP (30) - Secure RTP package packageFM (31) - Media Format Package Enumeration: 'packageSST': 21, 'packageLCS': 29, 'packageRES': 16, 'packageATM': 12, 'packageIT': 18, 'packageNAS': 26, 'packageSASDI': 17, 'packageMO': 15, 'packageSRTP': 30, 'packageMDSTE': 27, 'packagePRE': 28, 'packageMD': 25, 'packageMDR': 22, 'packageFXR': 23, 'packageMT': 19, 'packageMS': 13, 'packageH': 7, 'packageL': 6, 'packageM': 4, 'packageN': 9, 'packageA': 10, 'packageB': 20, 'packageD': 3, 'packageBA': 24, 'packageG': 2, 'packageDT': 14, 'packageFM': 31, 'packageDC': 1, 'packageR': 8, 'packageS': 11, 'packageT': 5.

This object represents the bit map of MGCP supported packages. Bit 0 - Not Found Bit 1 - Package DC (Don't care package) Bit 2 - Package G (Generic package) Bit 3 - Package D (DTMF package) Bit 4 - Package M (MF package) Bit 5 - Package T (Trunk package) Bit 6 - Package L (Line package) Bit 7 - Package H (Handset package) Bit 8 - Package R (RTP package) Bit 9 - Package N (NAS package) Bit 10 - Package A (Announcement Server package) Bit 11 - Package S (Script package) Bit 12 - Package ATM (ATM package) Bit 13 - Package MS (MF CAS package) Bit 14 - Package DT (DTMF CAS package) Bit 15 - Package MO (MO package) Bit 16 - Package RES (RES package) Bit 17 - Package S_ASDI (ASDI package (S) NCS) Bit 18 - Package IT (IT package (S) TGCP) Bit 19 - Package MT (MT package) Bit 20 - Package B (B package) Bit 21 - Package SST (SST package) Bit 22 - Package MDR (MDR package) Bit 23 - Package FXR (FAX package) Bit 24 - Package BA (Bulk Audit package) Bit 25 - Package MD (MD package) Bit 26 - Package NAS (Network Access Server package) Bit 27 - Package MDSTE (Modem relay Secure Telephone Equipment package) Bit 28 - Package PRE (PRE package) Bit 29 - Package LCS (MGCP Line Control Signaling package) Bit 33 - Package SRTP (Secure RTP package) Bit 31 - Package FM (Media Format Package) The value 0 means there is no supported packages. Bits: 'packageSST': 21, 'packageMO': 15, 'packageLCS': 29, 'packageRES': 16, 'packageN': 9, 'packageATM': 12, 'packageIT': 18, 'packageNAS': 26, 'packageSASDI': 17, 'notFound': 0, 'packageSRTP': 30, 'packageMDSTE': 27, 'packagePRE': 28, 'packageMD': 25, 'packageMDR': 22, 'packageFXR': 23, 'packageMT': 19, 'packageMS': 13, 'packageH': 7, 'packageL': 6, 'packageM': 4, 'packageDC': 1, 'packageA': 10, 'packageB': 20, 'packageD': 3, 'packageBA': 24, 'packageG': 2, 'packageDT': 14, 'packageFM': 31, 'packageR': 8, 'packageS': 11, 'packageT': 5.

This object is used to enable/disable building of s, t, o lines in SDP message. where o field indicates the owner/creator and session identifier s field indicates the session name t field indicates the duration while a session is valid. If this object is set to 'true'(enabled), SDP will NOT include the fields s, t, and o. If this object is set to 'false', then it indicates that the o, s, t lines be built before sending SDP (Session Description Protocol).

This object specifies the ACK SDP is enabled or not. If this object is set to 'true', then it sends ADP with ACK when CODEC or reportable NTE delta changed, or an attempt is made to change CODEC, VAD, Packet-period, echo cancellation during FAX/modem mode.

This object enables/disables the undotted notation for CODEC. This object is used to set CODEC notation to 'dotted' or 'undotted' in SDP between the gateway and the call agent. For example, 'G.726' is 'dotted', while 'G726' is 'undotted'. If it is set to 'true', then the 'undotted' notation for CODEC is enabled.

This object is used to determine how to handle persistent events. If this object is set to 'true', the quarantined events should be processed, otherwise the quarantined events is discarded.

This object controls the default quarantine mode. If this object is set to 'true', the default quarantine mode is 'loop', not 'step'. When this object is set to 'true', the gateway is expected to generate multiple notifications (loop), not at most one notification (step by step), in response to quarantined events. This object will be ignored if the object cXgcpMediaGwQuarantineProcess is set to 'false'.

This object specifies how the persist events will be handled in quarantine processing. If this object is set to 'true', the persistent events bypass quarantine buffer. This object will be ignored if the object cXgcpMediaGwQuarantineProcess is set to 'false'.

This object enables/disables the piggyback message generating. If the piggyback message generating is enabled, a call agent can send several MGCP messages in the same UDP packets to the gateway.

This object specifies the maximum allowed xGCP message size which is used for checking if the size will be supported by the call agent via (AuditEndPoint) response. A value of 0 means that there is no limit to the size of the XGCP message.

This object indicates the address type, either IPv4 or IPv6, of cxeCallCtrlLastFailMgcAddr.

This object indicates the address of last MGC which the media gateway had tried to communicate with but failed.

When this object is set to 'true', the digits will be sent as peer-to-peer packet in the bearer. When this object is set to 'false', the digits will be sent as regular voice packets in the bearer. For low complexity CODECS (such as G.711), the preferred value for this object could be 'false'. For high complexity CODECS (such as G.729A), the preferred value for this object should be 'true', otherwise the digits may not get recognized properly at the remote end.

CALEA, Communication Assistance for Law Enforcement Act, is a feature that allows for a lawful intercept of a call details and call contents originating or terminating on specific terminals. CALEA feature can be turned on or off. A value 'true' specifies CALEA enabled and a value 'false' specifies CALEA disabled.

This object represents the bit map of MGCP packages configured and supported in the gateway. Bit 0 - Not Found Bit 1 - Package DC (Don't care package) Bit 2 - Package G (Generic package) Bit 3 - Package D (DTMF package) Bit 4 - Package M (MF package) Bit 5 - Package T (Trunk package) Bit 6 - Package L (Line package) Bit 7 - Package H (Handset package) Bit 8 - Package R (RTP package) Bit 9 - Package N (NAS package) Bit 10 - Package A (Announcement Server package) Bit 11 - Package S (Script package) Bit 12 - Package ATM (ATM package) Bit 13 - Package MS (MF CAS package) Bit 14 - Package DT (DTMF CAS package) Bit 15 - Package MO (MO package) Bit 16 - Package RES (RES package) Bit 17 - Package S_ASDI (ASDI package (S) NCS) Bit 18 - Package IT (IT package (S) TGCP) Bit 19 - Package MT (MT package) Bit 20 - Package B (B package) Bit 21 - Package SST (SST package) Bit 22 - Package MDR (MDR package) Bit 23 - Package FXR (FAX package) Bit 24 - Package BA (Bulk Audit package) Bit 25 - Package MD (MD package) Bit 26 - Package NAS (Network Access Server package) Bit 27 - Package MDSTE (Modem relay Secure Telephone Equipment package) Bit 28 - Package PRE (PRE package) Bit 29 - Package LCS (MGCP Line Control Signaling package) Bit 33 - Package SRTP (Secure RTP package) Bit 31 - Package FM (Media Format Package) The value 0 means there is no supported packages. Bits: 'packageSST': 21, 'packageMO': 15, 'packageLCS': 29, 'packageRES': 16, 'packageN': 9, 'packageATM': 12, 'packageIT': 18, 'packageNAS': 26, 'packageSASDI': 17, 'notFound': 0, 'packageSRTP': 30, 'packageMDSTE': 27, 'packagePRE': 28, 'packageMD': 25, 'packageMDR': 22, 'packageFXR': 23, 'packageMT': 19, 'packageMS': 13, 'packageH': 7, 'packageL': 6, 'packageM': 4, 'packageDC': 1, 'packageA': 10, 'packageB': 20, 'packageD': 3, 'packageBA': 24, 'packageG': 2, 'packageDT': 14, 'packageFM': 31, 'packageR': 8, 'packageS': 11, 'packageT': 5.

This object specifies the RSIP behavior of the endpoints with active calls (in connections) when they are forced to out-of-service. The following values can be set for this object: sendDlcx - The media gateway sends RSIP-graceful and then individual DLCX command to delete the endpoints of each connection and its children before it sends out RSIP-forced command when an endpoint goes into alarm or placed out-of-service forcefully through the user command if the endpoint or its children has any calls (in connections). rsipOnly - The media gateway sends out RSIP-forced command, and delete the connections without any DLCX or RSIP-graceful command. This object is applicable only if the endpoint or its children have any calls. If there are no calls on the endpoint, the media gateway sends RSIP-forced command when the endpoint is forced to out-of-service. Enumeration: 'rsipOnly': 2, 'sendDlcx': 1.

This object specifies the long duration timer. It is used to define the long duration of a connection. Once the timer expires, a notification will be sent to the MGC to indicate that a connection has established for the defined long duration.

This object specifies the XGCP profile in the media gateway level. The value of 0 means the XGCP default profile is used in the media gateway level. If the value of ccasIfExtVoiceCfgCcntrlProfile is 0, then the endpoint uses the profile specified in this object.

This object specifies the format for parsing or generating G.723 or G.729 codec in SDP message for the media gateway. The value 'true' means using Annex A and B in fmtp line complying with RFC 3555. The value 'false' means using Annex A and B in SDP attribute codec string.

This table contains statistical information on the transmitted and received network messages between MG and MGC, since the MG reset. The entries in this table are uniquly identified by the VMG index and the MGC address. This table contains statistics of the most recently received 64 MGC addressess for every VMG present in the device. When a new address is received and the number of entries for this MGC exceeds 64, then a least recently received entry is deleted.

This entry contains the statistical information on the received and transmitted network messages with the associated MGC address.

A unique index to identify a specific MGC address for tracking xGCP statistics between MGC and MG.

This object indicates the address type of cXgcpMsgStatsMgcIPAddress.

This object indicates IP address of the MGC. The IP address should be unique on the table.

This object indicates the number of successful messages that communicate with the MGC on that IP address. Successful messages apply to both transmit and receive messages. Transmit: Positive ACK received from the MGC. Receive : Positive ACK sent to the MGC. This implies that the format of the message is correct and the request can be fulfilled.

This object indicates the number of failed messages that communicate with the MGC on that IP address. Failed messages apply to both transmit and receive messages. Transmit: Either NAK has been received from the MGC or message times out waiting for ACK. Receive: Format of the received message is bad or the request was NAK'ed.

This object indicates the number of transmit messages for which time out occurred while waiting for an ACK.

This table contains information on the received and transmitted network messages, based on each message type, for all the VMGs present in the device. The table will have one entry for every VMG present in the device. When a new MG is instantiated, the device creates an entry. The entry is destroyed if the associated VMG is terminated.

This entry contains the information on the associated VMG's received and transmitted network messages. The value of each statistical object is incremented when the MG receives or transmits an XGCP message corresponding to that object type. All these values are set to '0' upon restarting of the VMG.

Number of UDP packets received from all the MGCs.

Number of UDP packets sent to all the MGCs.

Number of unrecognized UDP packets received from all the MGCs.

Number of messages with parsing errors received from all the MGCs.

Number of duplicate response messages sent to the MGCs.

Number of invalid protocol version messages received from all the MGCs.

Number of unknown message packets received from all the MGCs.

Number of acknowledgment messages sent by the MG.

Number of negative acknowledgment messages sent by the MG.

Number of acknowledgment messages received by the MG.

Number of negative acknowledgment messages received by the MG.

Number of CRCX messages received by the MG.

Number of CRCX messages received, that were successful.

Number of CRCX messages received, that failed.

Number of DLCX messages received.

Number of DLCX messages received, that were successful.

Number of DLCX messages received, that failed.

Number of DLCX messages sent.

Number of DLCX messages sent, that were successful.

Number of DLCX messages sent, that failed.

Number of MDCX messages received.

Number of MDCX messages received, that were successful.

Number of MDCX messages received, that failed.

Number of RQNT messages received.

Number of RQNT messages received, that were successful.

Number of RQNT messages received, that failed.

Number of AUCX messages received.

Number of AUCX messages received, that were successful.

Number of AUCX messages received, that failed.

Number of AUEP messages received.

Number of AUEP messages received, that were successful.

Number of AUEP messages received, that failed.

Number of RSIP messages sent.

Number of RSIP messages sent, that were successful.

Number of RSIP messages sent, that failed.

Number of NTFY messages sent.

Number of NTFY messages sent, that were successful.

Number of NTFY messages sent, that failed.

This table contains information on the active connections of all the VMGs present in the device. A MG may have zero or more number of calls at any given time. Each call consists of one or more connection. The table will have one entry per VMG per connection present in the device. When a new connection is established, the device creates an entry. The entry is destroyed if the associated connection is torn down.

This entry contains the information about an active connection.

Connection ID generated by the gateway and sent in the ACK message.

The physical or virtual entity that acts as a source or sink of data in the MG is called an endpoint. Every end point in the MG is assigned a textual name by the MG.

Call ID associated with this connection. Call ID is a parameter that identifies the call to which this connection belongs to. A call ID is unique within a VMG instance.

The local UDP port used for the connection.

The remote UDP port used for the connection.

Represents possible MG connection modes. invalid - Invalid value for mode sendOnly - The GW should only send packets recvOnly - The GW should only receive packets sendRecv - The GW can send and receive packets inActive - The GW should neither send nor receive packets loopBack - The GW should place the circuit in loopback mode contTest - The GW should place the circuit in test mode data - The GW should use the circuit for network access for data netwLoop - The GW should place the connection in network loopback mode netwTest - The GW should place the connection in network continuity test mode conference - The GW should place the connection in conference mode. Enumeration: 'sendOnly': 1, 'conference': 10, 'recvOnly': 2, 'loopBack': 5, 'netwTest': 9, 'invalid': 0, 'inActive': 4, 'contTest': 6, 'netwLoop': 8, 'data': 7, 'sendRecv': 3.

VCCI used for the VoAAL2 call. The object should have a non-zero value only if the associated call is of VoAAL2 type. For all other calls the value should be '0'.

CID used for the VoAAL2 call. The object should have a non-zero value only if the associated call is of VoAAL2 type. For all other calls the value should be '0'.

Represents possible MG call states. idle - Idle setting - Incoming call from PSTN connecting - CRCX message received conferencing - Call connected, await conf active - Conference created confDestroying - Destroying conference disconnecting - Conf destroyed, disconnect call inactive - call in inactive mode voiceConnecting - Creating telephony call leg only voiceActive - Telephony call leg created confDissociating - Destroying conf callLegsDissociated - Conf destroyed hpConnecting - connecting TDM hair-pin call leg hpConnected - one HP call leg connected hpConferencing - Conferencing TDM Hairpin call leg hpActive - TDM hair-pinning active state voipConfDestroy - Conf destroyed, make HP call erroState - call in error state connectingInactive - creating inactive connection confDestroyingInactive - conf destroy inactive conn confTest - AAL2/IP continuity test setupWait - Waiting for setup information waitNseSent - Wait for NSE event to be sent twcActive - TWC call active waitState - App is waiting for call control handOver - App is grabbing back the control Enumeration: 'waitNseSent': 22, 'confDestroyingInactive': 19, 'active': 4, 'confTest': 20, 'inactive': 7, 'voipConfDestroy': 16, 'erroState': 17, 'voiceConnecting': 8, 'connectingInactive': 18, 'setting': 1, 'connecting': 2, 'hpActive': 15, 'voiceActive': 9, 'disconnecting': 6, 'hpConferencing': 14, 'handOver': 25, 'confDissociating': 10, 'hpConnected': 13, 'setupWait': 21, 'callLegsDissociated': 11, 'hpConnecting': 12, 'waitState': 24, 'twcActive': 23, 'confDestroying': 5, 'idle': 0, 'conferencing': 3.

Specifies the codec type to be used with the Call. The following codec types are defined: notApplicable - no Codec Type is defined g711ulaw - G.711 mu-law g711alaw - G.711 A-law g726k32 - G.726 32K g726k24 - G.726 24K g726k16 - G.726 16K g729 - G.729 g729a - G.729-A g729b - G.729-B g729bLowComp - G.729-B Low Complexity g728 - G.728 g723 - G.723 g7231HighRate - G.723.1 High Rate g7231aHighRate - G.723.1 Annex A High Rate g7231LowRate - G.723.1 Low Rate g7231aLowRate - G.723.1 Annex A Low Rate gsmFullRate - GSM full rate gsmHalfRate - GSM half rate gsmEnhancedFullRate - GSM enhanced full rate gsmEnhancedHalfRate - GSM enhanced half rate g729ab - G.729-A-B. clearChannel - Nx64 clear channel nse - For NSE xnse - For X-NSE nte - For telephone-event t38 - T-38 modemRelay - Modem Relay mdsteModemRelay - For X+mdste sse - For SSE codecUnknown - Unknown Codec Enumeration: 'xnse': 130, 'modemRelay': 133, 'gsmHalfRate': 17, 'g729b': 8, 'g729a': 7, 'g7231aHighRate': 13, 'notApplicable': 0, 'gsmFullRate': 16, 'g726k16': 5, 'g728': 10, 'g711ulaw': 1, 't38': 132, 'codecUnknown': 200, 'g7231LowRate': 14, 'nse': 129, 'g729ab': 20, 'g711alaw': 2, 'gsmEnhancedHalfRate': 19, 'g726k24': 4, 'sse': 135, 'gsmEnhancedFullRate': 18, 'nte': 131, 'g729bLowComp': 9, 'g729': 6, 'g7231HighRate': 12, 'g726k32': 3, 'clearChannel': 128, 'g723': 11, 'mdsteModemRelay': 134, 'g7231aLowRate': 15.

A call event is defined as something that happens to a call at a given time. This object contains the latest MG call event that was successful.

This object contains the latest MG internal call event that was successful.

This object contains the latest MG call event that was failed.

This object contains the latest requested MG call event.

Represents possible MG call event results. normalOk - Normal event processed OK invalidOk - Invalid event processed OK callRecordReleased - The call record is released invalidCallId - TGW find invalid call id invalidConnId - TGW find invalid connection id duplicatedMsg - TGW find duplicated sgcp msg ackFailure - TGW can't send sgcp ack msg deleteFailure - TGW can't send sgcp delete msg createAckFailure - TGW can't send create ack msg createAckMissing - TGW did't send sgcp ack msg deleteAckFailure - TGW can't send delete ack msg notifyFailure - TGW can't send sgcp notify msg invalidState - TGW find event in wrong state invalidProtocolVer - GW finds protocl ver. not supported tgwDown - TGW in graceful shutdown mode tgwNotReady - TGW not ready for the event callVdbFailure - TGW can't obtain the vdbptr prevRtpPortLocked - TGW find previous rtp port locked connRecordMissing - TGW can't find conn record endPointNotRdy - TGW not ready for the event memResourceError - TGW has transient mem alloc err callCacFailure - GW does not have the bandwidth confRsrcError - GW cannot get conf resource gwRsrcNotAvailable - GW does not have available resource reqEventFailure - TGW can't handle requested event invalidCcapiEvent - TGW can't handle the ccapi event ignoreCcapiEvent - TGW will ignore the ccapi event signalFailure - TGW can't handle the signal abnormalOnhook - TGW find abnormal onhook invalidOffhook - TGW find invalid offhook invalidCot - TGW find invalid cot cotFailure - TGW failed to do COT cotDisableFailure - TGW failed to disable COT callSetupReqFailure - TGW can't setup call request callSetupIndFailure - TGW can't handle call indication callContextFailure - TGW can't setup the context callPeerFailure - TGW can't setup the peer callVoxCallFailure - TGW can't setup the voip/voaal2 call callVoipCallFailure - TGW can't setup the voip call callDiscFailure - TGW can't disconnect the call callModifyFailure - TGW can't modify the call parm callAlertFailure - TGW can't alert the call callDeleteFailure - TGW can't delete the call callUnknownFeature - TGW can't handle unknow feature upSupportedCodec - TGW find unsupported codec noDigitMap - TGW can't find the digit map ignoreDigit - TGW can't process the digits digitsOverflow - TGW can't handle too many digits digitsNotifyFailure - TGW can't send the digits out codecNotMatched - TGW codec doesn't match rmt TGW invalidConnMode - TGW can't understand con mode glare - GW encountered a glare condition peerMissing - TGW find not find the peer peerNotReady - TGW find peer not ready peerInWrongState - TGW find the peer in wrong state peerDisconnectFailure - TGW can't disconnect the peer noConferenceId - TGW can't find the conference ID confCreateFailure - TGW can't create conference confDestroyFailure - TGW can't destroy conference unknownConnType - TGW can't handle the con type invalidEndpoint - TGW can't connect to endpoint invalidNseEvent - Invalid NSE event nseRcvdOnWrongLeg - The NSE events come to a wrong leg sendNseFailure - Cannot send an NSE event playToneFailure - Cannot play NSE-requested tone codecSpecInError - Codec list provided in error mediaSpecUpsupported - Media specified not supported mediaChangeFail - Media change failed invalidNsePayload - Invalid payload type in SDP nsePayloadNotAvail - Specified NSE payload not free embMdcxError - Emb modify connection error mdcxLeg1Error - Modify connection leg1 error mdcxLeg2Error - Modify connection leg2 error deferMsg - For deferring events transError - TGW endpoint in transition state discOnWrongLeg - Disconnection on wrong call leg invalidNteEvent - Invalid NTE event notEnabledNteEvent - The NTE event has not been enabled for use nteEventExecuteFail - NTE execution failed sendNteFailure - Cannot send an NTE event invalidSsePayload - Invalid SSE payload ssePayloadNotAvailable - SSE payload is not available invalidModemRelayParam - Invalid Modem Relay Param modemRelayNotSupported - Modem Relay not supported in endpt invalidXcapXcpar - Invalid X-Cap or X-Cpar in SDP invalidSprtPayload - Invalid SPRT payload sprtPayloadNotAvailable - SPRT payload is not available Enumeration: 'duplicatedMsg': 12, 'normalOk': 0, 'codecNotMatched': 76, 'invalidModemRelayParam': 142, 'callVoipCallFailure': 65, 'callVoxCallFailure': 64, 'playToneFailure': 103, 'confRsrcError': 38, 'callSetupReqFailure': 60, 'ignoreDigit': 73, 'sendNseFailure': 102, 'unknownConnType': 97, 'deleteFailure': 14, 'sprtPayloadNotAvailable': 146, 'invalidNteEvent': 130, 'mdcxLeg1Error': 110, 'gwRsrcNotAvailable': 39, 'invalidOffhook': 52, 'invalidEndpoint': 98, 'peerMissing': 90, 'deferMsg': 112, 'notEnabledNteEvent': 131, 'glare': 78, 'cotDisableFailure': 55, 'confDestroyFailure': 96, 'embMdcxError': 109, 'reqEventFailure': 40, 'discOnWrongLeg': 120, 'deleteAckFailure': 17, 'transError': 115, 'endPointNotRdy': 35, 'abnormalOnhook': 51, 'tgwDown': 30, 'createAckMissing': 16, 'peerNotReady': 91, 'connRecordMissing': 34, 'invalidNseEvent': 100, 'nteEventExecuteFail': 132, 'mediaChangeFail': 106, 'invalidCallId': 10, 'callContextFailure': 62, 'codecSpecInError': 104, 'callModifyFailure': 67, 'modemRelayNotSupported': 143, 'tgwNotReady': 31, 'invalidCcapiEvent': 41, 'callVdbFailure': 32, 'noDigitMap': 72, 'callCacFailure': 37, 'invalidProtocolVer': 20, 'mdcxLeg2Error': 111, 'peerInWrongState': 92, 'invalidConnId': 11, 'callUnknownFeature': 70, 'callDeleteFailure': 69, 'digitsOverflow': 74, 'digitsNotifyFailure': 75, 'invalidOk': 1, 'signalFailure': 50, 'invalidSsePayload': 140, 'nsePayloadNotAvail': 108, 'memResourceError': 36, 'ssePayloadNotAvailable': 141, 'callPeerFailure': 63, 'callRecordReleased': 2, 'cotFailure': 54, 'mediaSpecUpsupported': 105, 'ackFailure': 13, 'invalidSprtPayload': 145, 'invalidNsePayload': 107, 'createAckFailure': 15, 'invalidState': 19, 'upSupportedCodec': 71, 'nseRcvdOnWrongLeg': 101, 'invalidCot': 53, 'callAlertFailure': 68, 'noConferenceId': 94, 'ignoreCcapiEvent': 42, 'invalidXcapXcpar': 144, 'invalidConnMode': 77, 'callDiscFailure': 66, 'prevRtpPortLocked': 33, 'sendNteFailure': 133, 'notifyFailure': 18, 'confCreateFailure': 95, 'callSetupIndFailure': 61, 'peerDisconnectFailure': 93.

Specifies what type of encryption suite is used to encode the information sent through this connection. none - No Encryption suite is used aes128Cm - AES-128 countermode encryption suite is used. Enumeration: 'aes128Cm': 1, 'none': 0.

The compliance statement for the SNMPv2 entities which implement XGCP. This has been replaced by ciscoXgcpMIBComplianceRev1.

The compliance statement for the SNMPv2 entities which implement CISCO-XGCP-MIB.

The compliance statement for the SNMPv2 entities which implement CISCO-XGCP-MIB.

The compliance statement for the SNMPv2 entities which implement CISCO-XGCP-MIB.

This group contains the MGC objects for SGCP/MGCP that the MG connects to.

This group contains core objects for SGCP/MGCP on the MG.

This group contains statistics objects for SGCP/MGCP on the MGC and the MG.

This group contains supplimentary objects for XGCP extended provisioning in the MG.

This group contains supplimentary objects for XGCP extended provisioning in the MG.

This group contains the received and transmitted network messages for every virtual MG present in the managed system.

This group contains active connections information that are controlled by the Gateway Control Protocol.