Service guide
Caller prepaid service guide V1.2
MyVoipApp
support team
Table of contents
1.1 Definitions,
symbols and abbreviations
List of figures
Figure 1‑1: Basic
network topology
Figure 2‑1 System
information configuration window (Remote database Tab)
Figure 2‑2: local user configuration
Figure 2‑4: prepaid rate configuration
Figure 2‑5: subscriber configuration
Figure 2‑6: caller prepaid configuration

Figure 1‑1: Basic network topology
In some deployments, it is required the caller should
be controlled with balance. When caller makes out-going call, the service
should check whether he/she has enough balance to make this call. After the
call is established, the server should be able to monitor the balance and fee
in real-time and the server should release the call forcedly if the user hasn’t
enough balance to continue the call.
When the user is receiving incoming call, it is
unnecessary to calculate his/her fee.
In MSS system, we name this service as “caller
prepaid”. From the network topology, we can see
(1)
All prepaid configurations will be
configured in MSS and stored in MySQL.
(2)
MSS will be responsible for
checking balance and calculate fee. Of course, MSS will be responsible for
establish and release the calls.
DB MySQL
database.
MSS miniSipServer
UE User End
There are three kinds of configurations we shall prepare for “caller prepaid” service.
(1) Remote database configuration.
(2) User configuration.
(3) Prepaid configuration..
In current phase, MSS can only connect to MySQL database.
Please click menu “DataàSystem informationàRemote database” and configure the parameters according to your MySQL configurations.

Figure 2‑1 System information configuration window (Remote database Tab)
|
Item |
Value |
Description |
|
Database address |
domain name or IP address |
Remote MySQL address. Note, MSS and MySQL can be installed in the same computer. In this case, the “database address” should be “localhost”. |
|
Visit port |
Integer. |
Remote MySQL visit port. If you updated port in MySQL configuration, you need update this configuration in MSS too. The default value is 3306. Please refer to MySQL manual document. |
|
User name |
String |
The user name which is created in MySQL database. The user should have the right to create database, create tables, etc. |
|
Password |
String |
Password of the visit user. It depends on MySQL configuration. |
In default, it is unnecessary to support “caller prepaid’ for normal users. If the user is plan to support “caller prepaid”, it should be indicated clearly.
Please click menu “DataàLocal users” and select/add a user as following.

Figure 2‑2: local user
configuration
It is ok to just select “caller prepaid” option.
It includes following parts: (1) How to set fee rate? (2) How to set balance for the prepaid users. (3) How to calculate fee?

Figure 2‑3: prepaid
menu
Please click menu “ServicesàPrepaidàPrepaid rate” and prepare to add a new prepaid rate.

Figure 2‑4: prepaid
rate configuration
|
Item |
Value |
Description |
|
ID |
integer |
Indication of current record. |
|
Interval |
Integer. |
Interval for calculating fee. The unit is “second” |
|
Tariff |
Integer |
Fee for each “Interval”. |
For an example, “ID=1; Interval=60; Tariff=
Please click menu “ServicesàPrepaidàSubscriber balance” and prepare to add balance for the prepaid users.

Figure 2‑5: subscriber
configuration
|
Item |
Value |
Description |
|
Subscriber |
String |
Local user who is prepaid subscriber |
|
Balance |
Integer |
Balance of the current prepaid user. |
Please click menu “ServicesàPrepaidàCaller prepaid” and prepare to set how to calculate fee for the prepaid subscribers.

Figure 2‑6: caller
prepaid configuration
|
Item |
Value |
Description |
|
Subscriber |
String |
Local user who is prepaid subscriber. This field can be set with “*”. That means for all prepaid subscriber. |
|
Route number |
String |
The destination prefix which the call will be routed. This field can be set with “*”. That means for all destinations. |
|
Prepaid rate ID |
Integer |
Prepaid rate for calculating fee. This ID is configured in previous section “2.3.1Prepaid rate”. |
For examples:
We configure following records in the “caller prepaid” table.
|
Subscriber |
Route number |
Prepaid rate ID |
Description |
|
* |
* |
1 |
For all prepaid subscriber and all
destination, the rate “ |
|
* |
101 |
2 |
Any subscribers call destination with
prefix “ |
|
100 |
* |
3 |
Subscriber “ |
|
100 |
1 |
4 |
Subscriber “ |
Then, we can see which rate will be applied in following cases.
(1)
“
(2)
“
(3)
“
(4)
“