12.07.2015 Views

Admin Guide - Mizu Voip

Admin Guide - Mizu Voip

Admin Guide - Mizu Voip

SHOW MORE
SHOW LESS
  • No tags were found...

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

If the techprefix is „-2”, then the original techprefix will be inserted in cdr record (but not forwarded).If the techprefix is empty, then only the normalized callednumber will be forwarded.The following techprefixes are reserved for the server: 111,222,999.Only 3 digit techprefix is allowed. If your traffic sender needs another techprefix length, you must rewrite the incoming number in the “Prefix Rules” form.Example: protocol: sip, Type: ip, value: your traffic sender ip, rewritefrom: oldtechprefix, rewriteto: newtechprefix.If you need more complex rules then you can use the prefix rules form in the mmanage application. Here you can add/remove any prefix for A and Bnumbers before and after the routing.You can rewrite prefixes before they arrive to the routing by entering your preferences here.The <strong>Mizu</strong> routing engine will accept only 3 digit length techprefixes or no thechprefix, so you must convert them here if your traffic sender will send the traffic with techprefix that are not three digit length.For example you can set up a rule which defines that every incoming number from ip 111.111.111.111 on H323 if begins with 1234 must be rewritten to begin with 56. Number 123499999 will be rewritten to5699999.If the “RewriteFrom” is emtly, then the “RewriteTo” fill be inserted before the numberTo rewrite prefixes on router number normalization, you have to set the following global config values:prefixrewritestr: the original prefixprefixrewritefrom: keep fromprefixrewriteto: inserted stringfor example to handle the hungarian roaming prefix: 08 + SK + BK + NSN +SN you have to set the following values:prefixrewritestr: 08X…prefixrewritefrom: 9prefixrewriteto: 36If you need more flexibility, you can edit the v_check_pxrules stored procedure manually using any SQL expression.For CLI control you can set the “cli” field for any user:CLI: CLIR and CLIP settings0: forward always (forward asserted as normal number always!). Will not hide, even if caller was set so.1: normal handling (forward asserted as normal number) -default2: forward as asserted identity always (identityrewrite asserted)3: forward as asserted identity only to trusted domains (identityrewrite asserted)4: normal hide (no idenityrewrite forwarding)5: force hide (no asserted identity too!). Always hidden.To completely rewrite the A number you can use the “rewriteanumber” field.To cut some prefixes from the A number use the “cutanumber” field.To allow some A numbers and rewrite other numbers you can use the identityrewrite and identityforward fields.This can be useful when not all your user have real PSTN numbers.Addtechprefix: we insert this number before the callednumber if the caller doesn’t send its calls with tech prefix.identityforward: we can toward these kinds of usernames and the other we rewrite to „identityrewrite”.identityrewrite: if the caller username don’t match the identityforward prefix, then we rewrite it.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!