Call Processing No Session Initiation Protocol Trigger Context Found—Call Processing (44) - Cisco BTS 10200 Troubleshooting Manual

Chapter 4 Call Processing Troubleshooting
Call Processing No Session Initiation Protocol Trigger Context Found—Call
Processing (44)
The Call Processing No Session Initiation Protocol Trigger Context Found event serves as a warning that
an invalid "service_ref" in the SIP INVITE message coming from the Application Server has occurred.
To correct the cause of the event, report the BTS 10200 and the Application Server with the received
"service_ref" string to Cisco TAC.
Note Refer to the
detailed instructions on contacting Cisco TAC and opening a service request.
Context in call from Application Server not Found—Call Processing (45)
The Context in call from Application Server not Found event serves as a warning that an BTS 10200 has
received an INVITE from an application server which contains a context ID in the route header which
is invalid. It may be that the Application Server has not properly returned the route header. Additionally,
it is possible that the BTS 10200 has cleared the call and removed the context before the application
server returned an INVITE message to the BTS 10200. To correct the cause of the event, get the
application server to correctly return the BTS 10200 route header back to the BTS 10200 and check
timing for the calls returned to the BTS 10200 from the application server.
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
4-31