Admin Guide - VoIP software provider

*Tip: you don‟t need to enforce traffic sender rights by routing. The routing can be done as generic as possible for example by specifying onlyCalled Prefixes (Leave the other direction option blank or „*‟). Rights can be enforced by setting “Enabled Prefixes” for all Traffic SendersRouting ConfigurationsTry to set up all routing rules and prioritizations using this form.Try to avoid prioritizations by gateways, simpackets or channels (absolutepriority, priority, allowedpartners, prioritypartners, etc)Almost all kind of configuration can be set up by using only the “routing” formThe actual priority order of your route list (right side list) will be affected by numerous factor:-Failowering: when a device or a device/direction is in failowered state, then its priority is lowered-Load balancing: will prioritize the direction where the last routed date time is oldest (only if the routing entries are entered with the samepriority)-LCR: the route with the lowest price will be prioritized-BRS: the best quality/lower price route will be prioritizedThese settings can be controlled by the “brs_lcr” global config option:0=not used1=only lcr for not gsm2=lcr3=brs for not gsm4=BRS (default)5=BRS+LCR4.4.8. Routing workflowIntroductionThe routing in the Mizu softswitch means deciding on which active gateway, user or gsm channel should we route the incoming call from traffic senders andendusers.The routing is influenced mainly by the following:-device ownership and access rights (allowedpartner settings)-routing time, direction and the selected pattern (device/packet priority list)-various priority settings