Dial Plan Information For Test Call Not Found—Call Processing (35) - Cisco BTS 10200 Troubleshooting Manual

Chapter 4 Call Processing Troubleshooting
Dial Plan Information for Test Call Not Found—Call Processing (35)
The Dial Plan Information for Test Call Not Found event functions as a warning that the test call could
not be completed. The primary cause for the event is that the test call could not be completed because
the number entered could not be located in the dial plan. To correct the primary cause of the event, check
and correct the BTS 10200 dial plan provisioning. Additionally, check the number tested.
Invalid or Unknown Nature of Address—Call Processing (36)
The Invalid or Unknown Nature of Address event functions as a warning that the NOA was invalid or
incorrect. The primary cause of the event is that the NOA was incorrect in the dial plan. To correct the
primary cause of the event, check and correct the BTS 10200 dial plan provisioning.
Call Failure—Call Processing (37)
The Call Failure event functions as a warning that the placed call failed. The primary cause of the event
is that the call failed for the reasons indicated in the data words. To correct the primary cause of the
event, check the data words type of call (four bytes), calling number (20), called number (20), and failure
indication (20). Once the data words are checked, contact Cisco TAC to resolve the failure indicated.
Refer to the
Note
detailed instructions on contacting Cisco TAC and opening a service request.
Prior to contacting Cisco TAC, collect a billing-record for the failed call using the following:
report billing-record orignumber=<string>
Release Cause 25 Exchange Routing Error Received—Call Processing (38)
The Release Cause 25 Exchange Routing Error Received alarm (minor) indicates that a release with
cause number 25 occurred because an exchange routing error was received. To troubleshoot and correct
the cause of the Release Cause 25 Exchange Routing Error Received alarm, refer to the
25 Exchange Routing Error Received—Call Processing (38)" section on page
Test Call Blocked Due to Congestion or Isolation—Call Processing (39)
The Test Call Blocked Due to Congestion or Isolation event functions as a warning that the test call was
blocked due to congestion or isolation. The primary cause of the event is that the IAM for test call was
blocked due to congestion/isolation. To correct the primary cause of the event, correct congestion or
isolation problem and place test call again from remote system
OL-8723-19
"Obtaining Documentation and Submitting a Service Request" section on page lvi
Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x
Monitoring Call Processing Events
for
"Release Cause
4-36.
4-29