![Cisco BTS 10200 Softswitch Troubleshooting Manual Download Page 180](http://html.mh-extra.com/html/cisco/bts-10200-softswitch/bts-10200-softswitch_troubleshooting-manual_67550180.webp)
4-30
Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x
OL-8723-19
Chapter 4 Call Processing Troubleshooting
Monitoring Call Processing Events
Interactive Voice Response Real Time Transport Protocol Session Fail—Call
Processing (40)
The Interactive Voice Response Real Time Transport Protocol Session Fail event functions as a warning
that the IVR Real Time Transport Protocol (RTP) session failed. The primary cause of the event is that
the IVR server is not ready, or the connection failed. To correct the primary cause of the event, check
IVR server. The related route guide ID and/or trunk group index are provided if known at the time the
event report is issued
INVITE Message From Unauthorized Call Agent—Call Processing (41)
The INVITE Message From Unauthorized Call Agent alarm (minor) indicates that a INVITE message
was received from an unauthorized CA. To troubleshoot and correct the cause of the INVITE Message
From Unauthorized Call Agent alarm, refer to the
“INVITE Message From Unauthorized Call
Agent—Call Processing (41)” section on page 4-36
Call Failed after Local Number Portability Query with Location Routing Number
of this BTS 10200 and the Directory Number—Call Processing (42)
The Call Failed after Local Number Portability Query with Location Routing Number of this BTS 10200
and the Directory Number event serves as an information alert that the provisioning of ported-in
subscriber has not been completed. To correct the primary cause of the event, verify whether the given
DN has been provisioned correctly in the reporting BTS 10200. If there is an error in the LNP database
(SCP) or other switch, then notify the appropriate administrators. Note that porting of the subscriber and
DN from the donor switch to the recipient switch, and associated updates of the Location Routing
Number (LRN) in all the SCP databases, may not all occur at exactly the same time. Therefore it must
be expected that some call failures may occur until the porting process has completed at all network
nodes. Once the porting process is expected to be completed, if mis-routing still occurs, then the above
actions should be taken to resolve the issue. The secondary cause of the event is that the LNP database
(SCP) has an incorrect LRN for the given DN.
Call Processing Session Initiation Protocol Trigger Provisioning Error—Call
Processing (43)
The Call Processing Session Initiation Protocol Trigger Provisioning Error event serves as warning that
a provisioning data discrepancy between the Application Server and the BTS 10200 has occurred. To
correct the cause of the event, modify the provisioning data either in the BTS 10200 or the Application
Server.