System information

Routing Configurations
Try 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” form
The 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 same priority)
-LCR: the route with the lowest price will be prioritized
-BRS: the best quality/lower price route will be prioritized
These settings can be controlled by the “brs_lcr” global config option:
0=not used
1=only lcr for not gsm
2=lcr
3=brs for not gsm
4=BRS (default)
5=BRS+LCR
4.4.11. Routing workflow
Introduction
The routing in the Mizu softswitch means deciding on which active gateway, user or gsm channel should we route the incoming call from traffic senders and endusers.
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
The routing is blocked if the following conditions are met:
General conditions
syntax error in incoming number (or not known)
max call/day, max speachlength reached (licensing option)
Caller user check
the traffic sender reached their maximum channels
caller gateway, simcard or simpacket is not enabled or temporarily disabled
failed authorization (wrong originating ip, bad username or password or wrong techprefix)