Cisco BTS 10200 Troubleshooting Manual page 841

Hide thumbs Also See for BTS 10200:

Table of Contents

System Usage of MGW Keepalive Parameters, Release 5.0

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

RGW with 16 or Fewer Endpoints and No Stable Calls In

If a KA attempt is unsuccessful: The system raises one or more alarms and continues this pattern of

the action specified in the spare1-supp token in the mgw-profile table.

Typical alarms for this condition include:

Typical informational events for this condition include:

If all KA attempts are unsuccessful through mgcp-keepalive-retries, the system declares the MGW

unreachable.

For TGWs and RGWs with more than 16 endpoints—If a KA attempt is successful, the

system implements

Scenario 1—MGW Reachable

calls or not.

(Scenario 3—MGW

(36)—Trunk locally blocked (applicable to CAS, ISDN, and SS7 trunks).

(79)—Trunking Gateway unreachable.

(171)—Residential Gateway unreachable.

(152)—Termination transient error received. This event is applicable when the

keepalive functionality is enabled.

(76)—Timeout on remote instance. This event is applicable when the keepalive

functionality is disabled.

Keepalive for Release 5.0 Maintenance Release 1.1 and Later

regardless of whether there are stable

Unreachable). For any stable calls on this MGW, the system takes

Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x

Scenario 2 (Special Case)—Reachable

Chapters

Table of Contents