Signaling Gateway Traffic Mode Mismatch—Signaling (164) - Cisco BTS 10200 Troubleshooting Manual

Monitoring Signaling Events
Signaling Gateway Traffic Mode Mismatch—Signaling (164)
The Signaling Gateway Traffic Mode Mismatch alarm (major) indicates that the traffic mode does not
match on the BTS 10200 and the Signaling Gateway. To troubleshoot and correct the primary cause of
the Signaling Gateway Traffic Mode Mismatch alarm, refer to the
Mismatch—Signaling (164)" section on page
No Session Initiation Protocol P-DCS Billing Information Header
Received—Signaling (165)
The No Session Initiation Protocol P-DCS Billing Information Header Received event serves as a
warning that no SIP P-DCS billing information headers are being received. The primary cause of the
event is that the originating switch is not provisioned to add the P-DCS-Billing-Info header to outgoing
SIP requests and responses. To correct the primary cause of the event, provision the originating switch
to add P-DCS-Billing-Info header to outgoing messages. The secondary cause of the event it that the
header could have been stripped off by an intermediate proxy. To correct the secondary cause of the
event, determine if the header has been stripped off by an intermediate proxy and configure the system
for corrective action if so. The ternary cause of the event is that there was a SIP message encode error
at the sending switch. To correct the ternary cause of the event, determine if a SIP message encode error
occurred at the adjacent switch and if so, call the technical assistance center to determine a fix for the
problem.
No Routing Keys are Active—Signaling (166)
The No Routing Keys are Active event serves as a warning that no routing keys are active. The primary
cause of the event is that the routing keys are not controlled into ACTIVE state. To correct the primary
cause of the event, control the routing keys to the ACTIVE state. The secondary cause of the event is
that the ITP provisioning is incorrect. To correct the secondary cause of the event, check the ITP
provisioning.
No Signaling Gateways are Active—Signaling (167)
The No Signaling Gateways are Active event serves as a warning that no signaling gateways are active.
The primary cause of the event is that there is a communication problem between ITP and the BTS
10200. To correct the primary cause of the event, check the communication path between BTS 10200
and the ITP.
A Session Initiation Protocol Server Group has no Child Elements
Provisioned—Signaling (168)
The A Session Initiation Protocol Server Group has no Child Elements Provisioned event is issued as a
warning when a SIP Server Group administrative in-service is provisioned but has no child elements
provisioned. This Server Group will be considered as if it is administrative out of service. If that is
acceptable, then no action required. If the server group was expected to be workable, then place the
server group back out of service, resolve the provisioning problem, and place back into service.
Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x
10-124
Chapter 10
"Signaling Gateway Traffic Mode
10-158.
Signaling Troubleshooting
OL-8723-19