CISCO-VISM-XGCP-EXT

OBJECT-IDENTITY

OBJECT-IDENTITY

OBJECT-TYPE

This object specifies the maximum timeout value. This timer value is used along with xgcpRequestTimeout and xgcpRequestRetries (in xgcpGrp.my) to determine the exponential retry interval for retransmitting unacknowledged xgcp messages. The value of this timer has to be greater than or equal to xgcpRequestTimeout. The default value of this object is 500 milliseconds. When the value of this object changes vismXgcpCoreObjects changed trap will be sent.

OBJECT-TYPE

This object is used to configure the local UDP port on VISM used by the SGCP and MGCP protocols to communicate with the call agent. The UDP port is used together with vismIpAddress to identify the local end of a SGCP/MGCP connection. The default value of this object is 2427. In VISM 1.5 this object always defaults to 2427 and is read-only.

OBJECT-TYPE

This table is used to provision peer-specific XGCP configuration information. Each table entry corresponds to an XGCP peer name / peer XGCP variant combination.

OBJECT-TYPE

Each row is identified by XGCP peer name and peer XGCP protocol number combination. This means, if an MGC uses more than one variant of XGCP (i.e MGCP, SGCP 1.0, SGCP 1.1 etc), an entry will be maintained for each of the protocols. mgcNumber and mgcProtocolNumber from MGMIB are used as foreign index to this table. Entries in this table are implicitly created by the agent. An entry shall be created when an entry is created in the mgcProtocolTable and when mgcProtocolNumber refers to an XGCP variant (i.e MGCP, SGCP 1.0, SGCP 1.1 etc) as supported protocol. An entry shall be deleted if the corresponding entry in the mgcProtocolTable is deleted. As both mgcProtocolTable and vismXgcpPeerTable have mgcNumber and mgcProtocolNumber as index, referential integrity between the two tables is automatically ensured.

OBJECT-TYPE

The value of this object is the same as mgcNumber from MGMIB.

OBJECT-TYPE

The value of this object is the same as mgcProtocolNumber from MGMIB.

OBJECT-TYPE

This object is used to configure the local UDP port on VISM used by the SGCP and MGCP protocols to communicate with the call agent. The UDP port is used together with vismIpAddress to identify the local end of a SGCP/MGCP connection. If the protocol configured for the call agent is MGCP 1.0, the default port is 2727. In all other cases, the default value of this object is 2427. In VISM 1.5 this object always defaults to 2427 and is read-only.

OBJECT-TYPE

This table is an extension to the xgcpMsgStatTable contained in the XGCP MIB. This table provides per-message type based detailed statistics information.

OBJECT-TYPE

The row of the vismXgcpMsgStatTable contains additional information about XGCP message statistics beyond that provided by the XGCP MIB.

OBJECT-TYPE

This object specifies the IP address of the Media Gateway Controller. The value of this object is the same as xgcpIpAddress of XGCP-MIB.

OBJECT-TYPE

This refers to the count of CRCX (Create Connection) messages received from the call agent since reset.

OBJECT-TYPE

This refers to the count of CRCX (Create Connection) messages received from the call agent that were responded to with a failure return code.

OBJECT-TYPE

This refers to the count of MDCX (Modify Connection) messages received from the call agent since reset.

OBJECT-TYPE

This refers to the count of MDCX (Modify Connection) messages received from the call agent that were responded to with a failure return code.

OBJECT-TYPE

This refers to the count of DLCX (Delete Connection) messages received from the call agent since reset.

OBJECT-TYPE

This refers to the count of DLCX (Delete Connection) messages received from the call agent that were responded to with a failure return code.

OBJECT-TYPE

This refers to the count of DLCX (Delete Connection) messages sent to the call agent since reset.

OBJECT-TYPE

This refers to the count of DLCX (Delete Connection) messages sent to the call agent for which a response with failure return code was received or which timed out waiting for an acknowledgement.

OBJECT-TYPE

This refers to the count of RQNT (Request Notify) messages received from the call agent since reset.

OBJECT-TYPE

This refers to the count of RQNT (Request Notify) messages received from the call agent that were responded to with a failure return code.

OBJECT-TYPE

This refers to the count of NTFY (Notify) messages sent to the call agent since reset.

OBJECT-TYPE

This refers to the count of NTFY (Notify) messages sent to the call agent for which a response with failure return code was received or which timed out waiting for a response.

OBJECT-TYPE

This refers to the count of AUEP (Audit Endpoint) messages received from the call agent since reset.

OBJECT-TYPE

This refers to the count of AUEP (Audit Endpoint) messages received from the call agent that were responded to with a failure return code.

OBJECT-TYPE

This refers to the count of AUCX (Audit Connection) messages received from the call agent since reset.

OBJECT-TYPE

This refers to the count of AUCX (Audit Connection) messages received from the call agent that were responded to with a failure return code.

OBJECT-TYPE

This refers to the count of RSIP (Restart In Progress) messages sent to the call agent since reset.

OBJECT-TYPE

This refers to the count of RSIP (Restart In Progress) messages sent to the call agent for which a response with failure return code was received or which timed out waiting for a response.

OBJECT-IDENTITY

OBJECT-TYPE

The endpoint becomes disconnected when it tries to communicate with the call agent and the retransmission procedure times out after retrying. The endpoint in disconnected state starts the disconnected timer initialised to the random value and uniformly distributed between 1 and initial waiting delay (Tdinit) in seconds. The gateway waits for either the end of this timer, or the reception of call agent command or the detection of local user activity for the endpoint. When the disconnected timer elapses, or when a command is received from the call agent or when there is a local user activity, the Media Gateway sends the Restart In Progress command with the restart method as RM:disconnected to the Media Gateway Controller. The initial waiting delay (Tdinit) timeout value is defined by this MIB object. The recommended value of this object is 15 seconds.

OBJECT-TYPE

The endpoint becomes disconnected when it tries to communicate with the call agent and the retransmission procedure times out after retrying. The endpoint in disconnected state starts the disconnected timer initialised to the random value and uniformly distributed between 1 and initial waiting delay (Tdinit) in seconds. The gateway waits for either the end of this timer, or the reception of call agent command or the detection of local user activity for the endpoint. When the disconnected timer elapses, or when a command is received from the call agent or when there is a local user activity, the Media Gateway sends the Restart In Progress command with the restart method as RM:disconnected to the Media Gateway Controller. In case of local user activity, a provisionable disconnected minimum waiting delay (Tdmin) must have been elapsed since the gateway became disconnected. The minimum waiting delay (Tdmin) timeout value used by the Media Gateway to send the Restart In Progress with the restart method as RM:disconnected to the Media Gateway Controller if there is any local user activity is defined by this object. Media Gateway initiated delete connection (DLCX) or restart in progress (RSIP) commands are not considered as local user activity. The events observed on the TDM interface or on the network constitute the local user activity. The recommended value of this object is 15 seconds.

OBJECT-TYPE

The maximum waiting delay (Tdmax) timeout value used by the Media Gateway to send the Restart In Progress with the restart method as RM:disconnected to the Media Gateway Controller when the endpoint has become disconnected is defined by this object. The endpoint becomes disconnected when it tries to communicate with the call agent and the retransmission procedure times out after retrying. The endpoint in disconnected state starts the disconnected timer initialised to the random value and uniformly distributed between 1 and initial waiting delay (Tdinit) in seconds. The gateway waits for either the end of this timer, or the reception of call agent command or the detection of local user activity for the endpoint. When the disconnected timer elapses, or when a command is received from the call agent or when there is a local user activity, the Media Gateway sends the Restart In Progress command with the restart method as RM:disconnected to the Media Gateway Controller. If the disconnected procedure still left the endpoint disconnected, the disconnected timer is doubled subject to a provisionable disconnected maximum waiting delay (Tdmax) in seconds and the gateway starts the new disconnected procedure again. Once the maximum value is reached, the subsequent disconnected Restart In Progress commands use the maximum waiting delay (Tdmax). The recommended value of this object is 600 seconds.

OBJECT-IDENTITY

OBJECT-IDENTITY

OBJECT-IDENTITY