![Cisco BTS 10200 Softswitch Troubleshooting Manual Download Page 172](http://html.mh-extra.com/html/cisco/bts-10200-softswitch/bts-10200-softswitch_troubleshooting-manual_67550172.webp)
4-22
Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x
OL-8723-19
Chapter 4 Call Processing Troubleshooting
Call Processing Events and Alarms
CALLP (44)
To monitor and correct the cause of the event, refer to the
“Call Processing No Session Initiation Protocol
Trigger Context Found—Call Processing (44)” section on page 4-31
.
Note
Refer to the
“Obtaining Documentation and Submitting a Service Request” section on page lvi
for
detailed instructions on contacting Cisco TAC and opening a service request.
CALLP (45)
To monitor and correct the cause of the event, refer to the
“Context in call from Application Server not
Found—Call Processing (45)” section on page 4-31
.
DESCRIPTION
Call Processing No Session Initiation Protocol Trigger Context Found (CALLP No SIP Trig Context
Found)
SEVERITY
WARNING
THRESHOLD
100
THROTTLE
0
DATAWORDS
Calling Party Number–STRING [64]
Called Party Number–STRING [64]
Call ID- FOUR_BYTES
Inbound Context String–STRING [64]
PRIMARY
CAUSE
An invalid service_ref in the SIP INVITE message coming from the AS has occurred.
PRIMARY
ACTION
Report the BTS 10200 and the AS with the received service_ref string to Cisco TAC. (Contact Cisco
TAC.)
DESCRIPTION
Context in Call from Application Server not Found (Context in Call from App Server not Found)
SEVERITY
WARNING
THRESHOLD
100
THROTTLE
0
PRIMARY
CAUSE
The BTS 10200 has received an INVITE from an AS which contains a context ID in the route header
which is invalid. It may be that the AS has not properly returned the Route Header.
PRIMARY
ACTION
Get the AS to return the BTS 10200 route header correctly
SECONDARY
CAUSE
It is possible that the BTS 10200 cleared the call and removed the context before the AS returned an
INVITE to the BTS 10200.
SECONDARY
ACTION
Check timing for the calls returned to the BTS 10200 from the AS.