System information

ShortTelnumber: sip short telnumber (for example if several users has the same BelongsToCompany field)
DisplayName: how the user will be displayed. Can be null
Username: the most important field. Used for authentification and also as a DID number. This field is unique and cannot be empty.
Password: password applicable everywhere (sip, web, VPC, etc)
Ip: sipphone, sipproxy or gsmgateway ip address. The server will overwrite with the last known ip address
AuthIp: if we want to authenticate after ip, not after username/password
More than one auth ip or domain can be used for a traffic sender. For this the tb_users_authip table is used.
NeedAuth:
-If NeedAuth is 0, then the system is an open voip relay !!!!
-If NeedAuth is 1, then AuthIP must match (usually from SIP traffic senders)
-If NeedAuth is 2, then TechPrefix must match (usually from H323)
-If NeedAuth is 3, then TechPrefix and IP must match (usually from H323)
-If NeedAuth is 4, then user/pwd must match (usually from SIP end-users)
-If NeedAuth is 5, then username must match
-If NeedAuth is 6, then AuthIP and Port must match
-If NeedAuth is 7, then AuthIP and username must match
-If NeedAuth is 8, then AuthIP and username/password must match
-If NeedAuth is 9 then AuthIP Range must match
-If NeedAuth is 10, then AuthIP Range and username/password must match
AddDate: when the user has been inserted in the database
Rights: rights on user interfaces
0: no access
10: cannot login (disabled)
20: can login but no rights
30: a normal user
40: sales
50: admin
60: general admin
AddedBy: the user id who have added this user (sales, web registration, etc)
Commission: used for sales to define their comission percent from the enduser price
Reduction: sales user can give to enduser some percent (substracted from their comission)
LateFee: applicable when the user is late paying the invoice cost
PacketID: billing for users, traffic senders
BillingDay: usually 1 (the first day in every month)
Qualification: the importance for the user. From 0 to 10. for example if the user has big priority, then we route its calls to better routes