Cisco BTS 10200 Softswitch, Troubleshooting Manual

Page: 841 / 874

B-33
Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x
OL-8723-19
Appendix B System Usage of MGW Keepalive Parameters, Release 5.0
Keepalive for Release 5.0 Maintenance Release 1.1 and Later
•
For RGWs with 16 or fewer endpoints—If a KA attempt is successful, and no stable calls exist: The
system implements the KA pattern shown in Scenario 2. (See
Scenario 2 (Special Case)—Reachable
RGW with 16 or Fewer Endpoints and No Stable Calls In Progress .)
Note
For TGWs and RGWs with more than 16 endpoints—If a KA attempt is successful, the
system implements
Scenario 1—MGW Reachable regardless of whether there are stable
calls or not.
•
If a KA attempt is unsuccessful: The system raises one or more alarms and continues this pattern of
KA attempts (
Scenario 3—MGW Unreachable ). For any stable calls on this MGW, the system takes
the action specified in the spare1-supp token in the mgw-profile table.
Typical alarms for this condition include:
–
SIGNALING (36) —Trunk locally blocked (applicable to CAS, ISDN, and SS7 trunks).
– SIGNALING (79) —Trunking Gateway unreachable.
–
SIGNALING (171) —Residential Gateway unreachable.
Typical informational events for this condition include:
–
SIGNALING (152) —Termination transient error received. This event is applicable when the
keepalive functionality is enabled.
– SIGNALING (76) —Timeout on remote instance. This event is applicable when the keepalive
functionality is disabled.
•
If all KA attempts are unsuccessful through mgcp-keepalive-retries , the system declares the MGW
unreachable.