Troubleshooting guide

10-17
Cisco Broadband Local Integrated Services Solution Troubleshooting Guide
OL-5169-01
Chapter 10 Troubleshooting the Cisco BTS 10200 Softswitch
Cisco BTS 10200 Failure
SIP-controlled Trunk Groups
When a SIP-controlled trunk group’s administrative state is set to out-of-service (OOS), the trunk group
cannot be used for outgoing calls and incoming calls on that trunk group are rejected.
SIP-controlled trunk groups do not have physical resources; therefore, no mechanism can be used to
indicate to the remote switch the non-availability of the trunk group. The operational state of of the trunk
group is set to “not used.”
When a SIP-controlled trunk group’s administrative state is set to in-service (INS), all trunks in the trunk
group are brought in-service and both incoming and outgoing calls are allowed.
H323-controlled Trunk Groups
When an H323-controlled trunk group’s administrative state is set to out-of-service (OOS), the trunk
group cannot be used for outgoing calls; however, incoming calls on that trunk group are still allowed.
H323-controlled trunk groups do not have physical resources; therefore, the media gateway’s
administrative state is not affected when the trunk group is set to OOS.
H323-controlled trunk groups contain media gateway ids. When a media gateway is set to OOS no
incoming or outgoing calls are allowed through that gateway id because H3A unregisters that gateway
id with the gatekeeper.
When an H323-controlled trunk group’s administrative state is set to in-service (INS), both incoming
and outgoing calls are allowed, if the media gateways corresponding to that trunk group are in-service.
Cisco BTS 10200 Failure
The Cisco BTS 10200 hosts run in active-standby mode. The call-processing application is active on
only one Cisco BTS 10200 platform at a time, and the application switches to the standby platform when
a critical alarm occurs. The result is that Cisco BTS 10200 failure and switchover events are invisible to
the signaling network.
Cisco BTS 10200 alarms are configured as minor, major, or critical. Critical alarms are generated
whenever any significant failure occurs. Any critical alarm causes a switchover to occur. For example,
if the call engine or EMS should fail, there is a disconnection from the process manager (procM) and a
switchover to the standby system.
Operating System Failure
An operating system (OS) or hardware failure in the active Cisco BTS 10200 can also cause a switchover
to the standby Cisco BTS10200. The standby Cisco BTS 10200 detects the failure of the active Cisco
BTS 10200 and instructs the system to initiate a switchover. The standby Cisco BTS 10200 then takes
over all call-processing functions. The switchover is transparent to all the gateways.