10-75
Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x
OL-8723-19
Chapter 10 Signaling Troubleshooting
Signaling Events and Alarms
SIGNALING (141)
To monitor and correct the cause of the event, refer to the
“Address not Resolved by Domain Name
System Server—Signaling (141)” section on page 10-119
.
SIGNALING (142)
To troubleshoot and correct the cause of the alarm, refer to the
“Session Initiation Protocol Trunk
Operationally Out-of-Service—Signaling (142)” section on page 10-155
.
DESCRIPTION
Address not Resolved by Domain Name System Server (Address not Resolved by DNS Server)
SEVERITY
WARNING
THRESHOLD
100
THROTTLE
0
DATAWORDS
TSAP_Address/Hostname–STRING [256]
Reason–STRING [64]
PRIMARY
CAUSE
The transport service access point (TSAP) address or hostname is not defined in the DNS.
PRIMARY
ACTION
Add an entry for the TSAP address to the DNS server, or fix the BTS 10200 provisioning.
DESCRIPTION
Session Initiation Protocol Trunk Operationally Out-of-Service (SIP Trunk Operationally out of
Service)
SEVERITY
CRITICAL
THRESHOLD
100
THROTTLE
0
DATAWORDS
Trunk Group Description –STRING [21]
Trunk SIP Element ID–STRING [65]
Trunk Server Group ID–STRING [65]
PRIMARY
CAUSE
Issued when the BTS 10200 is unable to communicate with a remote SIP party (Call-Agent or Proxy)
over a SIP or a SIP-T trunk.
PRIMARY
ACTION
Verify that the DNS resolution exists, if TSAP address of the remote entity is a domain name. Verify
that the remote entity is reachable by Internet Control Message Protocol (ICMP) ping, using the Trunk
TSAP address from the Event Report. If the same alarm is reported on all the softswitch trunk groups,
verify that the network connection is operational.
SECONDARY
CAUSE
The remote SIP party is not operational.
SECONDARY
ACTION
If the ping is not successful, then diagnose the issue that prevents the TSAP address from being
reached. Verify that the SIP application is running on the remote host and is listening on the port
specified in the TSAP address.