Admin Guide - Mizu Voip

4.4.6. Prefix rulesYou should instead use the “Rules” form mentioned above.You can rewrite prefixes before they arrive to the routing by entering your preferences here.The Mizu routing engine will accept only 3 digit length techprefixes or no thechprefix, so you must convert them here if your traffic sender will send thetraffic with techprefix that are not three digit length.Example 1:To 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. Number123499999 will be rewritten to 5699999.If the “RewriteFrom” is emtly, then the “RewriteTo” fill be inserted before the numberExample 2: To remove 011 before all dialed numbers:Protocol: 0Type: 1Value: emptyRewrite from: 011Rewrite to: emptyNumber to rewrite: Incoming Called (0)Example 3: To replace 06 with 446 for all SIP calls coming from 192.168.1.8:Protocol: 1Type: 2Value: 192.168.1.8Rewrite from: 06Rewrite to: 446Number to rewrite: Incoming Called (0)Example 4: to handle the hungarian roaming prefix: 08 + SK + BK + NSN +SN you have to set the following values:prefixrewritestr: 08X…prefixrewritefrom: 9prefixrewriteto: 364.4.7. Dial PlansYou should instead use the “Rules” form mentioned above.During the routing process you can modify the caller and called number with the dialplan stored procedure (v_dialplan)v_dialplan can be called several times during the routing depending on the checkdialplan1-4 global config option.For CLI and A number rewrite it is enough to set checkdialplan4 to true (after routing) and check/rewrite the numbers using the LIKE operator (wildcardsare enabled).