![Cisco BTS 10200 Softswitch Troubleshooting Manual Download Page 174](http://html.mh-extra.com/html/cisco/bts-10200-softswitch/bts-10200-softswitch_troubleshooting-manual_67550174.webp)
4-24
Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x
OL-8723-19
Chapter 4 Call Processing Troubleshooting
Monitoring Call Processing Events
Test Report—Call Processing (1)
The Test Report event is used for testing the call processing event category. The event is informational
and no further action is required.
No Route Available for Called Number—Call Processing (8)
The No Route Available for Called Number event functions as a warning that there is no route available
for the number called. The primary cause for the event is that the call originates from a subscriber or
trunk for a called party number that has no route available. The Orig Type (one byte), Orig Sub or trunk
group (TG) ID (eight bytes), calling party number (20), and called party number (20) data words in the
event report indicate what parameters that need to be corrected. Refer to office records for the
subscriber. The secondary cause for the event is that parameters in the subscriber and/or dial-plan table
are missing or incorrect for the number dialed. To correct any parameter error, determine whether the
routing parameters (such as digit-string) were entered incorrectly in the subscriber and dial-plan tables.
If the called party is a subscriber, verify that the subscriber-type is listed as a subscriber in the dial-plan
table. If the call is long distance using a PIC, check that the PIC for this subscriber is properly
provisioned in the dial-plan table. If necessary, edit these files using the
change dial-plan
or
change
subscriber
commands.
No Route Available for Carrier Dialed—Call Processing (9)
The No Route Available for Carrier Dialed event functions as a warning that is no route available for the
dialed carrier. The primary cause for the event is that no route is available for the IXC dialed. The Orig
Type (one byte), Orig Sub or TG ID (eight bytes), calling party number (20), called party number (20),
and carrier code dialed (20) data words in the event report indicate the parameters that need to be
corrected. Refer to office records for the carrier. The secondary cause for the event is that parameters in
the carrier and/or route-grp table are missing or incorrect for the carrier. Determine whether the routing
parameters were entered correctly in the carrier and/or route-grp tables. If the Carrier-ID or
Route-Grp-ID are not specified, or are incorrect, in the dial-plan table, enter the correct values. Use the
change carrier
or
change route-grp
command.
CALLP(39)
Test Call Blocked Due to Congestion or Isolation—Call Processing (39)
WARNING
CALLP(40)
Interactive Voice Response Real Time Transport Protocol Session Fail—Call
Processing (40)
WARNING
CALLP(41)
INVITE Message From Unauthorized Call Agent—Call Processing (41)
MINOR
CALLP(42)
INFO
CALLP(43)
Call Processing Session Initiation Protocol Trigger Provisioning Error—Call
Processing (43)
WARNING
CALLP(44)
Call Processing No Session Initiation Protocol Trigger Context Found—Call
Processing (44)
WARNING
CALLP(45)
Context in call from Application Server not Found—Call Processing (45)
WARNING
Table 4-2
BTS 10200 Call Processing Events (continued)
Event Type
Event Name
Event Severity