Chapter 14
General Troubleshooting
Configuration at Softswitch or Gatekeeper Has Placed Routing Into a Loop
[I5 10:16:20.921 BCM
[bcm_tpm_proc.c:106]
[***ERROR*** 10:16:20.921 H3A3 01-1 Main]
for callid=1
39 " [h3a_alarms.c:281]
Solution
The routing problem could be in either the gatekeeper or the BTS 10200. Check the gatekeeper against
the dialedDigits pattern in the admission request (ARQ), example:
destinationInfo "
[+
[+
[+
There are multiple ways that a gatekeeper could determine the destCallSignalAddress to send back in a
admission confirmation (ACF):
Outgoing H.323 Calls Routed to Incorrect Endpoint When Using Registration, Admissions, and Status
[I3 14:25:17.215 H3A3 01-1 Main]
code=3" [h3a_sig_sai.c:1549]
After the SETUP message has been sent out, a RELEASE COMPLETE is received from the remote
endpoint. In this case, the remote endpoint does not service the destination address (cause code=3).
Solution
Login to gatekeeper that outgoing H.323 gateway is registered with and determine the routing for called
number. Gatekeeper could be configured to route based on several configurations:
OL-8723-19
01-1 BCM_Main]
.
H3A3 .
.
H3A3 .
.
H3A3 .
A registered E.164 address (in this case, highly unlikely)
–
A static route configured (has been observed)
–
Default routing (highest frequency of problem)
–
Called number is matched against static routing
–
No routing defined for called number, uses default routing
–
Routing is based on tech prefix (will be pre-pended to called number in ARQ)
–
"BCM:TPM:Incr Counter( 3 ):4199302144"
"alarm=99 reason=<Loop detected!!> call cleared
.
]
"
{"
.
]
"
.
]
"
}"
"Rel message from STACK--->H3A for callid=8, cause
Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x
Protocol Troubleshooting
dialedDigits : "9991231234""
14-29