System information

(select id from tb_groups where name = 'testgroup'),
1,
id
from tb_users
where username like '%111%'
--select users from this group
select tb_users.id, tb_users.Username, tb_users.name
from tb_groupentries, tb_users
where
tb_groupentries.groupid = (select id from tb_groups where name = 'testgroup') and
tb_users.id = tb_groupentries.entryid
--delete group
delete from tb_groupentries where groupid = (select id from tb_groups where name = 'testgroup')
delete from tb_groups where name = 'testgroup'
5.98. Compatibility issues
In case if you have SIP signaling compatibility issues with old devices you might change these global config options:
addnewlineaftermsg = 2
rtpwritefirst = 0
allowheaders = 0
5.99. CLI settings / A and B numbers / Dial plan
There are multiple ways to apply your rules.
The server will “normalize” the numbers automatically based on rules from the global configuration (search for normalize). For example it can remove
strange digits, IEC codes like 00 or +, enforce length, etc.
Also there are built-in rules for several countries, so users can dial without CC/IEC/NEC.
For outgoing calls if you need to use a tech prefix, you just have to enter the corresponding digits as tech prefix for the sip proxy user.
TechPrefix:
The server can authorize and/or route the traffic after the incoming techprefix.
Sip users can have techprefixes too. this is usually common for reseller company users.
If no techprefix is specified, then it will be loaded from tb_pxrules if any.
Sim owners and vpc users can have a list of prefixes separated by comma.
If no techprefix is specified, 111 will be inserted for incoming called numbers.
If the techprefix is „-1”, then the original techprefix will be forwarded.