System information

4.4.8. Blacklisting
List the blacklisted numbers on the selected time interval and direction.
This query will generate high server load. Use it only in off-peak time if possible
4.4.9. Access Lists
You can define the “Blacklist” and the “Whitelist” here. The listing will be appreciated in the routing depending of the actual packet “filtering” setting. Check
section 4
for details regarding filtering.
Blacklist fields:
-telnumber: country code + operator + telnum
-sure: levels
tb_blacklist.sure:
0 –probably good numbers (reput)
1 - not sure (holes)
2 - probably wrong number (monthly autodisabled)
3 - very sure (roaming numbers)
6 – always block (not only to gsm)
filtering: determines how we check the blacklist and the known numbers
0 -no filtering
1 - filter if very sure blacklisted (tb_blacklist.sure >=3)
2 - filter if probably blacklisted (tb_blacklist.sure > =2)
3 –filter if suspicious (tb_blacklist.sure > =1)
4 - filter if present in blacklist (any tb_blacklist.sure)
5 - filter if not a known number
6 - filter out if no sure known number
4.4.10. Routing
For every time period and direction a “Routing Pattern” needs to be defined. Every Routing pattern has a list of routing directories which may be Mizu
GSM Gateteways, other H323 gateways or gatekeepers, ISDN gateways or SIP proxies in priority order. Set up as much directories with the same priority
order as possible so the routing engine can prioritize itself after other settings (device priority, LCR, quality,BRS)
Generic rules can be defined by setting the pattern priority lower. For example for every call that doesn’t have a specific route can be routed to a specific
direction (otherwise is dropped)
There is a list of typical time definition. If none of them match your needs, the “Start-End Time” entry can be selected to specify proprietary intervals.