Routing according the timenframe

<< < (2/3) > >>

azrobert:
Routing an outbound call is a 2 step process.
The Phone Port DigitMap validates the dialed number.
Rule (Mpli) will include the rules in primary line's default DigitMap.
If the dialed number doesn't match a rule, you will receive a fast busy.
You can modify the dialed number in the Phone DigitMap

If the dialed number matches a rule in the DigitMap the phone port outbound call route will route the call to the primary line using rule {(Mpli):pli}
(Mpli) above is also a DigitMap and can modify the dialed number.
When the 1st rule is enclosed in parentheses, it's a DigitMap.
When it's not, it's a literal.
{(xx):li} is comparing for 2 digits.
{xx:li} is comparing for 2 alpha xx's.

* All number starting with 0 should be redirected toward LINE
* All number starting with 00 should be redirected toward SP1

Physical Interfaces -> line Port -> DigitMap: (0xx.S3)

This DigitMap will match any number starting with "0" or "00"
The Primary Line for a OBi110 is the Line Port, so (Mpli) in the Phone Port DigitMap will include the Line DigitMap and will validate all numbers beginning with "0" or "00".
You can't remove the prefix here because when the outbound route gets control it won't see the prefix.

Physical Interfaces -> Phone Port
Add the following to the beginning of the OutboundCallRoute:
{(<00:>xx.):sp1},{(<0:>xx.):li},

The above will remove the prefix and route the call to the correct trunk.

The rule 0xx.S3 will have a 3 second delay before call is routed because of the "x.".
If I had xx. there would be a 10 second delay.
If you were more specific about the format of the dialed numbers, I could make the DigitMaps more efficient.

JOMA:
Brilliant! Thank-you so much, it's very clear.
As I'd like to learn, I'll try to make the DigitMap myself then I'll post it and explain the rule so you can may correct me?

Have a nice day :)

JOMA:
Hello,

Here was I think:

The first short numbers are emergency numbers. Then I have placed the most common number format of the country and finally xx.S3 for all numbers for international or short special numbers.
DigitMap : (112|100|101|107|103|116000|070245245|0xxxxxxxx|0xxxxxxxx|04xxxxxxxx|xx.S3)

In the call route, I want only the international call to go through SP1. The international call will start with 00 and as I need E.164 format, I'll remove them. For national call, I ll use the li connection and I don't need the E.164 format, so I won't remove anything. I've keept the xx.S3 for li because of all special format number. International numbers can correspond to xx.S3 but has the rule comes second it will be catched before and send toward sp1

OutboundCallRoute : {(<00:>xx.):sp1},{(112|100|101|107|103|116000|070245245|0xxxxxxxx|0xxxxxxxx|04xxxxxxxx|xx.S3):li},

Am I right?

Thx!

drgeoff:
You have 0xxxxxxxx present twice.

And 0xxxxxxxx includes the unique 07.... number you have in there, so having the 07... is of no benefit. Incidentally it is not a good idea to show complete real numbers on any web page so you may wish to edit your post.

Probably you have already done so but if not check that your ITSP is really expecting only a country code at the start of international calls.

azrobert:
Looks good!

If the unique 07.. is a frequently dialed number, you could use an S0 suffix for no delay. You could also add the S0 suffix to the emergency numbers.

My description of the routing delay wasn't very clear. This delay only occurs when the Phone DigitMap has control. The "S3" suffix in the outbound route won't hurt, but is not needed.

The following is not a suggestion, just FYI. When the DigitMap contains a "xx.", the OBi110 will wait 2 seconds for the other rules. It is waiting for additional digits to be entered.  If you didn't have the "xx." and dialed 012345678 or any other number, you wouldn't need the s0 suffix for zero delay. This is because additional digits will not match another rule.

Navigation

[0] Message Index

[#] Next page

[*] Previous page