Admin Guide - Mizu Voip

-strong but slower encryption mode (when usequickencryption is false)Encryption can be enabled/disabled with the “useencryption” global configuration value:0=disabled,1=only when rec encrypted (default)2=use3=alwaysThe encryption method is stored in the “candisablesim” field in tb_users (refreshed automatically by the server on client connect)Also, there is a possibility to define a list of ip addresses with the “encryptedpeerlist”. All communications with these peers will be done encrypted.If the mvoiptunnel client service is used with some always running device, then you should set a fix “encryptionkey”, otherwise it is changed every nightwhich might cause communication issues for long running clients.Standard SSL/TLS signaling encryptions are negotiated runtime as well as SRTP media encryption.The recommended encryption type between mizu devices is the embedded fast or bowlish+compression. These types of encryption require much less CPUpower and are done with no additional network overhead.Running Mizu Server in proxy mode(the server doesn’t handle registration and authentication, just forward it)Fwdregistrations=2 // //0=no,1=only from alternate port, 2=alwaysfwdregistrations_domain=registrar sip domainfwdregistrations_ip=registrar ip or FQDNSfwdregistrations_port=registrar portautocreatereguser=1 //0=no,1=when fwd authenticated ok register, 2=always (when we receive the register)Forwardauthentifications=1 //will forward invite (regarding routing setup)Sendrandompackets=trueudptunnelsamesock=1Ftpname=-Allowdiscmessage=falseMaxreroute=1 //only if 1 upper server is usedSslogport=0Setup routing to point to the upper serverOptionaly you may increase these tresholds:Maxmsgcountlimitmultiplier=2Maxnocdrmin=3000Maxroutereqpermin=5000