|
The Billing® application has two components:
· First is a Billing Server, which controls the Dialogic boards, handles the incoming calls, gets the user information (PIN, ANI, etc.), makes the outbound phone call on behalf of the user, and keeps billing the user during the conversation.
The Billing Server doesn't have routing capabilities for now, this means that the other equipment must route the outbound call depending on the destination.
· The second component is a database administration component, called Billing Admin. This application handles all the database related issues, for example it manages the destinations, each having a time unit, a value per time unit, a prefix, etc. It also manages the available users, which could be of 2 types, prepaid and postpaid, it generates any number of new PINs, and also allows changing the specific properties for a certain client.
|
The basic system functionality is:
receive call->verify client->make outbound call->start billing the client when connected
Before making the outbound call, a Postpaid client might ask to hear the current value of his PIN, and a Prepaid client might hear the current value and availability of the card, and might even refill the card with another Prepaid card. The actual billing starts only when the outbound call is connected at the destination. |
|
