![Cisco BTS 10200 Softswitch Troubleshooting Manual Download Page 171](http://html.mh-extra.com/html/cisco/bts-10200-softswitch/bts-10200-softswitch_troubleshooting-manual_67550171.webp)
4-21
Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x
OL-8723-19
Chapter 4 Call Processing Troubleshooting
Call Processing Events and Alarms
CALLP (42)
For additional information, refer to
“Call Failed after Local Number Portability Query with Location
Routing Number of this BTS 10200 and the Directory Number—Call Processing (42)” section on
page 4-30
.
CALLP (43)
To monitor and correct the cause of the event, refer to the
“Call Processing Session Initiation Protocol
Trigger Provisioning Error—Call Processing (43)” section on page 4-30
DESCRIPTION
Call Failed after Local Number Portability Query with Location Routing Number of this BTS 10200
and the Directory Number (Call Failed after LNP Query with LRN of this switch and the DN)
SEVERITY
INFO
THRESHOLD
100
THROTTLE
0
DATAWORDS
Calling Number–STRING [20]
Called Number (GAP)–STRING [20]
Location Routing Number (LRN)–STRING [20]
Jurisdiction Information Parameter–STRING [20]
PRIMARY
CAUSE
The provisioning of the ported-in subscriber has not been completed.
PRIMARY
ACTION
Verify whether the given DN has been provisioned correctly in the reporting BTS. 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 the 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 completed, if mis-routing still occurs,
then the listed actions should be taken to resolve the issue.
SECONDARY
CAUSE
The LNP database (SCP) has an incorrect location routing number (LRN) for the given directory
number (DN).
DESCRIPTION
Call Processing Session Initiation Protocol Trigger Provisioning Error (CALLP SIP Trigger
Provisioning Error)
SEVERITY
WARNING
THRESHOLD
100
THROTTLE
0
DATAWORDS
Calling Party Number–STRING [64]
Called Party Number–STRING [64]
Call ID- FOUR_BYTES
OBCSM/TBCSM SIP Trigger–STRING [8]
PRIMARY
CAUSE
A provisioning data discrepancy between the Application Server (AS) and the BTS 10200 has
occurred.
PRIMARY
ACTION
Modify the provisioning data either in the BTS 10200 or the AS.