3-33
Cisco BTS 10200 Softswitch Troubleshooting Guide, Release 5.0.x
OL-8723-19
Chapter 3 Billing Troubleshooting
Monitoring Billing Events
Prepaid Subscriber Call Attempt Failed Because of Balance—Billing (57)
The Prepaid Subscriber Call Attempt Failed Because of Balance event functions as informational alert
that a prepaid subscriber call attempt has failed of the subscriber account balance. The primary cause of
the event is that the subscriber has an insufficient balance to place the attempted call. To correct the
primary cause of the event, ask the subscriber to deposit more money in their account. Additionally, there
may be a problem with the billing information on the prepaid server. To correct the secondary cause of
the event, verify the billing information on the prepaid server.
Signaling Prepaid Server Inaccessible—Billing (58)
The Signaling Prepaid Server Inaccessible alarm (major) indicates that the signaling prepaid server has
become inaccessible. To troubleshoot and correct the cause of the Signaling Prepaid Server Inaccessible
alarm, refer to the
“Signaling Prepaid Server Inaccessible—Billing (58)” section on page 3-43
Billing File Name Type Change in Command Line Interface is
Inconsistent—Billing (59)
The Billing File Name Type Change in Command Line Interface is Inconsistent event serves as an
informational alert that a user updated the billing filename type in the CLI. To correct the primary cause
of the event, execute a switchover or a platform restart so the change is propagated to the billing code.
