![Cisco BTS 10200 Softswitch Скачать руководство пользователя страница 579](http://html.mh-extra.com/html/cisco/bts-10200-softswitch/bts-10200-softswitch_troubleshooting-manual_67550579.webp)
14-5
Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x
OL-8723-19
Chapter 14 General Troubleshooting
Troubleshooting Alerting Notification Problems
Troubleshooting Alerting Notification Problems
This section explains how to troubleshoot the system when the 3PTYFS does not appear to be receiving
the alerting notification and call data.
Step 1
Verify that the ID, transport service access point (TSAP) ADDR, and TYPE are properly provisioned in
the FEATURE-SERVER table.
Step 2
Verify that the alerting notification feature (ALERT_NOTIFY) is provisioned properly.
Step 3
Verify one of the following two cases, as applicable:
•
Verify that the ALERT_NOTIFY feature is included in the SERVICE table applicable to the specific
subscriber.
•
Verify that Alerting Notification is included in the SERVICE table applicable to the specific POP
(the service ID identified by the office-service-id token in the POP table).
•
Verify that the ALERT_NOTIFY feature is included in the default office service ID (if the feature
is intended to be offered to all subscribers on the switch).
Note
In the procedures included in this document, the alerting notification feature is provisioned using the
feature identifier
FNAME=ALERT_NOTIFY
. The feature identifier can be any unique string of up to
16 ASCII characters chosen by the service provider. If you are not sure of the name used in your system
for this feature, use the
SHOW FEATURE
command and view the system response to find the name.
Example:
SHOW FEATURE-SERVER;
SHOW FEATURE FNAME=ALERT_NOTIFY;
SHOW CA-CONFIG TYPE=DEFAULT-OFFICE-SERVICE-ID;
SHOW SERVICE ID=<the value of the default-office-service-id>
SHOW SERVICE ID=6543;
SHOW SUBSCRIBER-SERVICE-PROFILE SERVICE-ID=6543;
Step 4
If a TSAP address is used for the 3PTYFS, verify that the domain name is correctly provisioned in the
DNS and resolves to the intended 3PTYFS.
Step 5
Enter the CLI command to check for Signaling alarm #12—Feature Server is not up or is not responding
to Call Agent. If this alarm is raised, there is a communications problem between the BTS 10200 and
the 3PTYFS.
Example:
show alarm type=signaling;
show alarm type=signaling; number=12;
The following details apply to SIGNALING alarm #12:
–
For a 3PTYFS that is more than one hop away from the BTS 10200, SIGNALING alarm #12 is
raised when communications between the BTS 10200 and the first-hop node go down.
However, the alarm is
not
raised if communications on the second (or more distant) hop go
down, or if the DNS value for the 3PTYFS does not resolve correctly.
–
The system can take up to two minutes to detect a communications failure in the first hop toward
the 3PTYFS.