Signaling System 7 Trunk Was Found To Be In Erroneous State—Signaling (139) (Ss7) - Cisco BTS 10200 Troubleshooting Manual

Chapter 10 Signaling Troubleshooting
Number of Open Session Initiation Protocol Connections is Reaching
Engineered Limit—Signaling (138)
The Number of Open Session Initiation Protocol Connections is Reaching Engineered Limit event
functions as an informational alert that the number of open SIP connections is reaching the engineered
limit. The primary cause of the event is that the call failed or a feature is not available. To correct the
primary cause of the event, is to increase the engineered limit to allow for more open connections.
System configuration and traffic load have caused the number of open connections to approach the
engineered limit. Contact Cisco TAC for assistance in increasing in the limit.
Refer to the
Note
detailed instructions on contacting Cisco TAC and opening a service request.
Signaling System 7 Trunk was Found to be in Erroneous State—Signaling (139)
(SS7)
The Signaling System 7 Trunk was Found to be in Erroneous State event functions as an informational
alert that a SS7 trunk was found to be in an erroneous state. The primary cause of the event is that a
discrepancy exists between the local and the remote trunk states. The corrective action is automatically
enforced when using ANSI ISUP.
Unanswered Information Message—Signaling (140)
The Unanswered Information Message event functions as an informational alert that an INF message has
not been answered. The primary cause of the event is that the far-end switch is not responding to INF
message with an INR message. To correct the primary cause of the event, verify that the far-end switch
can correctly respond to an INF message.
Address not Resolved by Domain Name System Server—Signaling (141)
The Address not Resolved by Domain Name System Server event serves as a warning that an address
was not resolved by the DNS server. The primary cause of the event is that the TSAP address/hostname
is not defined in the DNS. To correct the primary cause of the event, add an entry for TSAP address to
the DNS server or fix the BTS 10200 provisioning.
Following tips may help troubleshoot NLP/DNS related issues.
•
•
OL-8723-19
"Obtaining Documentation and Submitting a Service Request" section on page lvi
Grep for GET_HOST_BY_NAME keyword in the traces at INFO3 trace level.
Grep for warning/error keyword in the traces at INFO3 trace level.
Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x
Monitoring Signaling Events
for
10-119