![Cisco BTS 10200 Softswitch Скачать руководство пользователя страница 603](http://html.mh-extra.com/html/cisco/bts-10200-softswitch/bts-10200-softswitch_troubleshooting-manual_67550603.webp)
14-29
Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x
OL-8723-19
Chapter 14 General Troubleshooting
Protocol Troubleshooting
Configuration at Softswitch or Gatekeeper Has Placed Routing Into a Loop
[I5 10:16:20.921 BCM 01-1 BCM_Main] “BCM:TPM:Incr Counter( 3 ):4199302144”
[bcm_tpm_proc.c:106]
[***ERROR*** 10:16:20.921 H3A3 01-1 Main] “alarm=99 reason=<Loop detected!!> call cleared
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 “
[+ . H3A3 . . ] “ {“
[+ . H3A3 . . ] “ dialedDigits : “9991231234””
[+ . H3A3 . . ] “ }”
There are multiple ways that a gatekeeper could determine the destCallSignalAddress to send back in a
admission confirmation (ACF):
–
A registered E.164 address (in this case, highly unlikely)
–
A static route configured (has been observed)
–
Default routing (highest frequency of problem)
Outgoing H.323 Calls Routed to Incorrect Endpoint When Using Registration, Admissions, and Status
[I3 14:25:17.215 H3A3 01-1 Main] “Rel message from STACK--->H3A for callid=8, cause
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:
–
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)