![Cisco BTS 10200 Softswitch Troubleshooting Manual Download Page 176](http://html.mh-extra.com/html/cisco/bts-10200-softswitch/bts-10200-softswitch_troubleshooting-manual_67550176.webp)
4-26
Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x
OL-8723-19
Chapter 4 Call Processing Troubleshooting
Monitoring Call Processing Events
Unable to Play Announcement—Call Processing (18)
The Unable to Play Announcement event functions as a warning that an announcement was not played.
The primary cause of the event is that the announcement was not provisioned correctly. To correct the
primary cause of the event, check the provisioning of the announcement and verify that the
announcement is provisioned correctly.
Call Routed to Unprovisioned Subscriber—Call Processing (19)
The Call Routed to Unprovisioned Subscriber event functions as a warning that a call was routed to an
unprovisioned subscriber. The primary cause of the event is that the subscriber account was not properly
provisioned. The correct the primary cause of the event, provision the subscriber.
No Route or Trunk Group Available to Route Call—Call Processing (20)
The No Route or Trunk Group Available to Route Call event functions as a warning that there was no
route or trunk group available to route a call. The primary cause of the event is that the trunk group in
the route was not provisioned correctly. To correct the primary cause of the event, verify the route and
trunk group provisioning.
Call Released Due to Maximum Hop Counts Exceeded—Call Processing (21)
The Call Released Due to Maximum Hop Counts Exceeded event functions as a warning that the call
was released due to the maximum hop counts being exceeded. The primary cause of the event is that the
number of hops between the destinations is excessive. To correct the primary cause of the event, reduce
the number of hops between the destinations.
Trunk Group Index Read Failure—Call Processing (22)
The Trunk Group Index Read Failure event functions as a warning that a trunk group index read failed.
The primary cause of the event is that the trunk group index could not be retrieved from the call data.
To correct the primary cause of the event, check and correct the BTS 10200 trunk group and call data
provisioning.
Routing Error: Termination is Not a Subscriber—Call Processing (23)
The Routing Error: Termination is Not a Subscriber event functions as a warning that the destination
termination is not a subscriber. The primary cause of the event is that the destination termination is not
provisioned as a subscriber. To correct the primary cause of the event, check and correct the BTS 10200
subscriber termination provisioning.