Cisco BTS 10200 Troubleshooting Manual page 818

Keepalive for Release 5.0 Prior to Maintenance Release 1.1
Basic Scenario
The basic scenario is shown in
attempt) and has stable calls, but no MGCP messages have been exchanged between the BTS 10200 and
the MGW for a time interval equal to the provisioned value of mgcp-keepalive-interval (default 60
seconds) in the mgw-profile table.
The legend in this drawing explains how successful and unsuccessful keepalive attempts are illustrated
Note
throughout this document.
Figure B-5 KA Attempts—MGW Reachable with Stable Calls
KA 1
Repeating time intervals with
no MGCP command activity:
mgcp-keepalive-interval
(default = 60 seconds)
Note For detailed examples of successful KA attempts, see
The system takes the following actions in the scenario shown in
•
•
•
Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x
B-10
KA 2 KA 3
If KA attempts are successful, and stable calls exist: The system continues this pattern of KA
attempts (Scenario 1—MGW
For RGWs with 16 or fewer endpoints—If KA attempts are 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
For TGWs and RGWs with more than 16 endpoints—If a KA attempt is successful, the
Note
system continues to implement Scenario 1 regardless of whether there are stable calls or not.
If a KA attempt is unsuccessful: The system implements the KA pattern shown in Scenario 3. (See
Scenario 3—MGW Unreachable.)
Appendix B System Usage of MGW Keepalive Parameters, Release 5.0
Figure B-5. The MGW is reachable (an ACK is received during each KA
KA 4
Legend
Successful KA
Unsuccessful KA
Figure B-1
Reachable).
KA 5 KA 6
ACK
mgcp-t-max 2*mgcp-t-hist
and Figure B-2.
Figure B-5:
Scenario 2 (Special Case)—Reachable
Progress.)
Time
OL-8723-19