System information

Password: sip password used in authentification
CallerNumber: usually the same as username. If left as blank, then the server use the actual caller username.
Credit: account balance. When it reach 0, then we switch to the next account if any
DateEntered: record insertion date
LastUsed: the date-time when the server was routed some calls with this account
ProxyID: to which proxy the account belongs
Enabled: set to 0 to disable the usage of this account
SubsFails: the number of subsequent wrong calls with this account. If subsfails will reach a predefined value (3
0 as default), it means that there is some problem with th
account or the money/time limit have been expired, and the server will switch to the next account if any
4.3.3. Groups
Grouping of several items will ease the administrations tasks. The following type of items can be grouped:
SIM Packets
Users
Gateways
Traffic Senders
These groups then can be used to simplify your routing and billing.
4.3.4. Ownership
Useful when you have arranged your users in certain hierarchies. For example reseller chain relationship.
Resellers can have an unlimited child-parent relationship (limited by the ”maxresellers” global config options).
To define the relationships we use the tb_users id and parented fields.
4.3.5. User authorization
Registration and authentication
User authentification can be done multiple ways (AuthType field in the user table).
Registration and authorization answers are cached in the Mizu server, so for subsequent requests from the same ip:port doesn’t have to query the database
again. This means that if you change the password in the database it may take some time until it is considered.
Mizu server has built-in DOS attach protection. This means (among others) that after a few unsuccessful registration (wrong password) request from a UA
that will be banned for a time. This banned list can be cleared from the server console with the “delbanned” command. Even whole IP ranges can be