Troubleshooting guide

1-31
Cisco Broadband Local Integrated Services Solution Troubleshooting Guide
OL-5169-01
Chapter 1 Solution Overview
Solution Features
Trunk Testing
Trunk testing is used to determine the transmission quality of the shared trunks that interconnect
switching systems. Trunk testing is extremely important in monitoring system health, because it is the
only practical way to objectively determine the performance of individual trunks.
Near End Test Origination Test Calls
The Cisco BTS 10200 Softswitch supports calls used to test individual trunks that connect a local
gateway with a gateway or PSTN switch at a remote office. The Cisco BTS 10200 Softswitch supports
OTL and TTL capability. User-provided test equipment and, optionally, test controllers may be
connected to the test lines. Proper selection of test equipment and test functions helps to ensure
interoperability between different carriers.
1XX Test Line
When the Cisco BTS 10200 Softswitch is the near end switch, the remote switch recognizes the trunk
test prefix (9581 or 9591) on the incoming signal, and the test type is used to route the test to the
appropriate test line. The appropriate tests are performed on the test set and additional test processes may
occur, depending on the specific test configuration.
When the Cisco BTS 10200 Softswitch is supporting the TTL capability (test call originated at another
switch), it receives the 958 or 959 call, recognizes the 958 or 959 type, and routes the test to the
appropriate test line.
Default Office Service ID
One service ID (the default office service ID, typically ID=999) is reserved for provisioning of
switch-based features. These switch-based features can include certain network features and certain
usage-sensitive features. The service provider must provision this service ID in the service table, and
define these features in the feature table.
Route Selection
As shown in Figure 1-7, when a request for routing is received by the routing subsystem, the subsystem
first searches through the termination table to determine whether the called number is a subscriber.
If the called number is a subscriber, the dial plan table processes the call through the dn2subscriber and
subscriber tables. If the called number is not a subscriber, the call is either routed to the appropriate
trunk using one of the following:
• Policy-Based Routing, page 1-32
• Carrier-Based Routing, page 1-34
• Trunk Group Selection Policies, page 1-34