14-28
Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x
OL-8723-19
Chapter 14 General Troubleshooting
Protocol Troubleshooting
This shows that the H.323 gateway is in service, but it is not registered with a gatekeeper. The following
are possible reasons for this: Incorrect provisioning for H323_GW2GK (incorrect gatekeeper (GK)
name, incorrect GK IP address, security violation) ---- this can be verified by trace logs as a gatekeeper
reject (GRJ) would be sent back by GK as follows:
[+ . H3A3 . . ] “value RasMessage ::= gatekeeperReject : “
[+ . H3A3 . . ] “ {“
[+ . H3A3 . . ] “ requestSeqNum 11"
[+ . H3A3 . . ] “ protocolIdentifier { 0 0 8 2250 0 3 }”
[+ . H3A3 . . ] “ rejectReason terminalExcluded : NULL”
[+ . H3A3 . . ] “ }”
Gatekeeper is down (no alternate GK or alternate is also down) --- this can be verified by trace logs as
a timeout would occur (waiting for gatekeeper confirmation (GCF) or GRJ) after the H.323 gatekeeper
request (GRQ) has been sent.
Stable Calls Are Dropped When Call Agent Switches Over
If Annex E functionality is provisioned on the BTS 10200, but stable calls are being dropped when the
H.323 process restarts or CA switches over, check to see whether configuration is correctly registered
with the GK:
Step 1
Log on to gatekeeper
Step 2
# show gatekeeper endpoints
Step 3
Examine the display of the GK, which should look similar to the example below:
Step 4
Verify that both the CA and H.323 Protocol (H323)-GW are registered with the GK with Flags=E as
shown in the above example.
No Matching Dial Plan Found on Incoming H.323 Trunk Group
[I2 14:45:24.288 BCM 01-1 Lib_RTM] “dial_plan(pcld=45145211, dp_idx=0): no match”
[rtm_dial_plan.c:492]
[***ERROR*** 14:45:24.288 BCM 01-1 BCM_Main] “No Dial Plan Entry for digits in dial plan
0" [bcm_obcsm_sa_proc.c:8916]
After
the SETUP message has been received at incoming H.323 gateway, Basic Call module (BCM) uses
the dial_plan_id in the incoming trunk group and the called number to find out how to route the call. If
no match is found, then this error will be issued.
Solution
Add an entry to dial_plan for called number and assign the identification (ID) to incoming trunk_grp.
CLI>
add dial_plan id=cdp1; digit_string=451452; dest_id=ipdest; min_digits=7;
max_digits=10;
CLI>
change trunk_grp id=8991; dial_plan_id=cdp1;
CallSignalAddr
Port
RASSignalAddr
Port
Zone Name
Type
Flags
aaa.bbb.ccc.ddd
1234 eee.fff.ggg.hhh
12345
City GK
VOIP-gateway (GW)
E
iii.jjj.kkk.lll
5678 ppp.qqq.rrr.sss
56789
City GK
VOIP-GW
E
