Table Of Contents
ICMP Message Blocking
Release 4.4 introduces a feature that provides the ability to block ICMP message from Call Agent to MGCP Gateway from the Call Agent (CA) to the MGCP gateway (MGW). Previously, you could perform both an AuditEndpoint (AUEP) ping and ICMP ping together; there was no method to perform one without the other. Release 4.4 provides the ability to run an AUEP ping alone, and to disable the transmission of an ICMP ping.
Blocking ICMP Messages
This new feature allows users to enable or disable ICMP ping to MGCP gateways.
Prior to this release, if AUEP ping was enabled for a media gateway and was unsuccessful, Cisco BTS 10200 sent an ICMP ping message to the MGCP media gateway to detect IP network connectivity between the Call Agent and media gateway. However, ICMP ping was always enabled when AUEP ping was enabled, so there was no method to perform just an AUEP ping without also performing an ICMP ping.
Cisco BTS 10200 Softswitch uses the AuditEndpoint (AUEP) ping or "keep alive" method to determine the CA's connectivity status to In Service media gateways, including trunking, residential and access gateways. The Cisco BTS 10200 sends an AUEP message to a representative endpoint on the gateway; this endpoint is the first Termination provisioned in the MGW table for the media gateway.
You can disable AUEP ping at the global level by configuring MGW-MONITORING-ENABLED=N in the CALL-AGENT table (by default, it is enabled).
If `AUEP ping' is disabled (either at the CA or MGW level), ICMP ping is also disabled. If `AUEP ping' is enabled for any media gateway, you can configure ICMP ping by using the newly-defined field KEEPALIVE-METHOD in the MGW-PROFILE table (by configuring the AUEP value).
In the scenario, when ICMP ping is enabled, Cisco BTS 10200 also stores the ICMP ping result in the MGW table in the Call Agent (as a dynamic field). If the AUEP ping fails, the alarm is generated only after the ICMP ping completes, and the alarm `SIGNALING 68' contains the message "ICMP ping <success/fail/in progress/not performed>".
Additionally, if the status command is issued for the MGW table, the result contains the ICMP ping status "<success/fail/in progress/not performed>." If the ICMP ping is disabled, or if the ICMP ping status is not performed, both the Alarm and Status commands show the ICMP ping status as "Not performed."
The ICMP message blocking feature does not add any new alarms to Cisco BTS 10200. However, the existing alarm SIGNALING 68 has an additional data-word, such as "ICMP ping status: <success/failed/in progress/not performed>."
The following example shows this:SIGNALING(68)DESCRIPTION: Media gateway/termination downSEVERITY: MAJORTHRESHOLD: 100THROTTLE: 0END-CUSTOMER PERCEPTION: Complete loss of customer capabilitiesDATAWORDSFully qualified name - STRING Type of mgw - STRING Failure Cause - STRING Subscriber Info - STRING ICMP ping status - STRING  = "ICMP ping status: <success/failed/in progress/not performed>"
New or Changed Tables
Table 1 CALL-AGENT Table Syntax Description
Token PK/FK Type Values Mandatory/ Optional
Media gateway monitoring enabled/disabled indicator.
Table 2 MGW-PROFILE Table Syntax Description