Configuration Events and Alarms

This section provides a brief overview of the configuration events and alarms for the Cisco BTS 10200 Softswitch; the event and alarms are arranged in numerical order. Table 5-1 lists all of the configuration events and alarms by severity.

The Cisco BTS 10200 software is released with a file named FIMXMLRules.xml. This file is only read during system initialization. It defines how to handle certain features provided on an external application server. The file might be missing.

Cisco BTS 10200 Provisioning for External Applications is Not Complete

Severity

Warning

Threshold

100

Throttle

0

PrimaryCause

The Cisco BTS 10200 call agent is provisioned to send a trigger to the feature server for the offhook delay trigger (OHD) feature or the terminating attempt trigger (TAT) feature. The subscriber is not provisioned to define the sip-trigger-profile ID.

PrimaryAction

Provision the sip-trigger-profile ID for each subscriber that has OHD or TAT provisioned.

Monitoring Configuration Events

This section provides the information you need for monitoring and correcting configuration events. Table 5-10 lists all of the configuration events in numerical order and provides cross-references to each subsection.

The Signaling Media Gateway Adapter Wrongly Configured Domain Name event functions as an informational alert that the signaling media gateway adapter (MGA) is configured with the wrong domain name. The primary cause of the event is that the domain name is invalid. To correct the primary cause of the event, check DNS server and correct domain name. The secondary cause of the event is that at least half of the local machine address does not match the MGCP domain name. To correct secondary cause of the event, check the DNS server for the domain name to ensure that the IP address is correct.

FIMXML Parse Error—Configuration (6)

The FIMXML Parse Error event serves as warning that the FIMXMLRules.xml file is missing or has been incorrectly modified. The Cisco BTS 10200 software is released with a file named FIMXMLRules.xml. This file is only read during system initialization. It defines how to handle certain features provided on an external application server. The file might be missing, or it might have been incorrectly modified. To correct the primary cause of the FIMXML Parse Error event, install the FIMXMLRules.xml file in the appropriate directory. A secondary cause of the event is that an invalid FIMXMLRules.xml file is installed. To correct the secondary cause of the event, install a valid FIMXMLRules.xml file.

Application Server Provisioning Error—Configuration (7)

The Application Server Provisioning Error event serves as a warning that the external application server has returned a SIP response code that indicates a subscriber is not provisioned on the AS. To correct the cause of the Application Server Provisioning Error event, provision the application server to handle all subscribers who are provisioned on the Cisco BTS 10200 to use applications on that server.

The Cisco BTS 10200 Provisioning for External Applications Is Not Complete event serves as warning that the Cisco BTS 10200 call agent is provisioned to send a trigger to the Feature Server for OHD or TAT feature. The subscriber is not provisioned to define the sip-trigger-profile ID. To correct the cause of the Cisco BTS 10200 Provisioning for External Applications is not Complete event, provision the sip-trigger-profile ID for each subscriber who has OHD or TAT provisioned.

Troubleshooting Configuration Alarms

This section provides the information needed to monitor and correct configuration alarms. Table 5-11 lists all of the configuration alarms in numerical order and provides cross-references to each subsection.

Mate Configuration Error—Configuration (3)

The Mate Configuration Error alarm (major) indicates that the mate configuration is incorrect. The primary cause of the alarm is that the mate side and the local side are configured to be the same side. To correct the primary cause of the alarm, configure the side of the platform coming up to be the opposite of its mate. The secondary cause of the alarm is that the mate is configured with the wrong mate DNS name or the mate DNS name entries have been changed. To correct the secondary cause of the alarm, properly configure the mate DNS name.

Configuration Error—Configuration (4)

The Configuration Error alarm (critical) indicates that a critical configuration error has occurred. The primary cause of the alarm is that there is incorrect configuration information in the platform.cfg file. To correct the primary cause of the alarm, check and, if necessary, correct the configuration parameters in the platform.cfg file.

The Feature Server Database and Command Line Host Mismatch alarm (minor) indicates that a feature-server DB and host command line mismatch configuration error has occurred. The primary cause of the alarm is that the Feature Server Table is mis-configured. To correct the primary cause of the alarm, reconfigure the Feature Server table to match command line -host and -port.