System information

Set the “haslinkedaccounts” global config option to “true” for this to work.
5.107. Server clustering
You can setup multiple servers with one (clustered) database backend.
For this you will have to edit the .ini file near the server and set the node value. Each server must have its unique node id (1,2,3…)
[database]
node=1
For any global configuration option specific to a node, a #NODENUMBER have to be appended for the key.
For example bindip#1.
(usually only the IP and ports are different for nodes)
You can set one main node with the “mainnode” global config option which must be equal with a node id. If not set, then node 1 will be the main.
Certain tasks (maintenance, reporting, etc) are handled only by the mainnode. If the mainnode app server fails, then another mainnode must be assigned
manually.
For database clustering please consult your db admin.
check:
webportal, web interface
check all db table, stored procedure, cpp file and server documentation
check cdr and billing, asyncDecreaseCredit, check user credit
select from tb_users order by instance
implementation:
db.h NODE, instanceclause, config.ismainnode
tb_users.srvinstance, tb_currcals.srvinstance, tb_cdrs.srvinstance
mizu clients will send \r\n for all servers to keep alive the nat, other calls have to be routed between server instances (tb_user.instance)
voicehere will work only on it's own server
5.108. Quality statistics (whithout extended cdrinfo)
--simple stats by call type
SELECT
b.marker, count(b.id) as 'CDRC (count)',
sum(b.realduration)/60 as 'SL (min)',
sum(SIGN(b.realduration))*100/count(b.id) as 'ASR (%)',