Help with complex digit map
xpr722946ghd:
Quote from: drgeoff on May 05, 2017, 11:08:03 am
Ditch the local web interface, and do everything through the ObiTalk web interface EXPERT MODE.
You can still use the local mode to LOOK at settings, but not modify them.
BINGO ;D
Using the Expert Settings part of the web interface has done the trick. The following digit map is working perfectly!
(*xxxx|1xx|<:1780>[2-9]xxxxxx|<:1>[2-9]xx[2-9]xxxxxx|1[2-9]xx[2-9]xxxxxx|<07:011447>xxxxxxxxx|<0:04444>[1-2]xxxxxxxxx|<44:04444>[1-2]xxxxxxxxx|011[2-9]x.|310xxxxS0|(Mipd)|[^*]@@.)
Thank you so much to all contributors for helping me get this sorted.
Now that has been accomplished, we move on to phase 2 ;) Directing calls to different providers automatically.
The goal :
UK calls (07, 01, 02) numbers get routed to SP1
Canadian calls (all area codes) routed to SP2
US calls (all non-Canadian or non-toll-free North American area codes) routed to SP4 (My GV account)
UK toll free calls (0800, 0808, 0500) routed via SP3
CAN & US toll free calls routed to SP1
International calls (outside of UK & North America) routed via SP1
Initially 911 calls need to route via SP1 until I have E911 services configured on SP2.
Having this fully automated would be very cool.
According to the tutorial I can handle this via Outbound Call Routes in the phone port section.
When writing the Outbound Call Route digit map, do I represent the number as dialled (e.g. 02xxx xxxxxx for a UK number) or what the service provider sees after transformation according to the digit map above (e.g. 044442xxx xxxxxx)?
I realize this might take a bit of scripting to come up with, but if anyone has any examples of separating Canadian / US calls for example, that would be most helpful.
I am wondering if I can create a list of Canadian area codes which get routed to SP2, and all other codes beginning with a 1 (with the exception of toll free) can be sent to SP4.
Any advice / suggestions / ways of doing this I haven't thought of?
Rob
drgeoff:
I suggest that you use the digit map under each ITSP to determine what dialled numbers that ITSP will handle. You then refer to that digit map in the Phone Port's OutboundCallRoute.
I'm in the UK and don't need to differentiate between US and Canadian numbers so I don't know if there is an easy way to do that other than by listing all the Canadian area codes. (https://www.allareacodes.com/canadian_area_codes.htm) OutboundCallRoutes are processed left to right and the first successful match wins, so if you have the Canadian map early in the rules it will catch all the Canadian ones before the general rule for the whole NANP gets the remaining (USA) ones.
You may need to refer to the Admin Guide http://www.obihai.com/docs/OBiDeviceAdminGuide.pdf, page 195.
Yes, the OutBoundCallRoute sees the mangled version of whatever a phone port digit map does to the number dialled on the phone.
A tip: When dealing with long digit maps or call routes, do all the editing in a text editor on your computer. Then copy and paste into the small field in the web browser page.
xpr722946ghd:
Quote from: drgeoff on May 05, 2017, 01:52:25 pm
I suggest that you use the digit map under each ITSP to determine what dialled numbers that ITSP will handle. You then refer to that digit map in the Phone Port's OutboundCallRoute.
I'm in the UK and don't need to differentiate between US and Canadian numbers so I don't know if there is an easy way to do that other than by listing all the Canadian area codes. (https://www.allareacodes.com/canadian_area_codes.htm) OutboundCallRoutes are processed left to right and the first successful match wins, so if you have the Canadian map early in the rules it will catch all the Canadian ones before the general rule for the whole NANP gets the remaining (USA) ones.
You may need to refer to the Admin Guide http://www.obihai.com/docs/OBiDeviceAdminGuide.pdf, page 195.
Yes, the OutBoundCallRoute sees the mangled version of whatever a phone port digit map does to the number dialled on the phone.
A tip: When dealing with long digit maps or call routes, do all the editing in a text editor on your computer. Then copy and paste into the small field in the web browser page.
Thanks for pointing out the larger admin guide. Just read through the pages now.
I think I'll set up the user digit maps for Canadian numbers. That will help the Outbound Call Route dialog be more readable.
As for your tip, I do just that. I keep several generations of amended digit maps in Evernote, so should I need to revert after breaking something, it is a simple copy / paste operation :)
SteveInWA:
Quote
The goal :
UK calls (07, 01, 02) numbers get routed to SP1
Canadian calls (all area codes) routed to SP2
US calls (all non-Canadian or non-toll-free North American area codes) routed to SP4 (My GV account)
UK toll free calls (0800, 0808, 0500) routed via SP3
CAN & US toll free calls routed to SP1
International calls (outside of UK & North America) routed via SP1
Rather than spend a lot more time, adding this additional layer of complexity to your digit maps, why don't you re-think the need for 4 different service providers, with logic to select between them? I don't think you've told us which providers are provisioned on each SPx, so I will simply point out that all calls to Canada are free via Google Voice, as are all US toll-free calls. Google Voice also has supposedly competitive rates to the UK:
https://support.google.com/hangouts/answer/3187125
https://www.google.com/voice/b/0/rates?p=hangout#U
xpr722946ghd:
Quote from: SteveInWA on May 06, 2017, 10:58:12 pm
Rather than spend a lot more time, adding this additional layer of complexity to your digit maps, why don't you re-think the need for 4 different service providers, with logic to select between them? I don't think you've told us which providers are provisioned on each SPx, so I will simply point out that all calls to Canada are free via Google Voice, as are all US toll-free calls. Google Voice also has supposedly competitive rates to the UK:
The quickest answer to your question is, "I'm a sucker for punishment!" I also know it is possible to do this and am a bit of a geek so would like to see it up and running!
Voip.ms is on SP1. Been with them for years, and love their service. Their calls to the UK are lower than Google Voice on a premium routing which is of excellent quality. Their IVR stuff is great, and I can have multiple sub accounts and extensions which I use. I can send any Caller ID I like - which enables my family in 3 different Countries to see my local DID to them. Their infrastructure is amazing - offering geographic POP in several areas of Canada. The lowest latency (22ms) to me is Vancouver which allows me to make use of 311 and 310-xxxx services in my area.
Anveo is on SP2. I've just signed up to evaluate their service and quality compared to Voip.ms. Some of their services are more competitively priced. Specifically incoming DIDs here in Canada. Through the ObiTalk deal I've been able to move E911 to them, and so am paying less for my DID than with Voip.ms. I'll probably port over my main mumber from Voip.ms if I find the service good. International calls are a little more expensive than Voip.ms but Canadian calls are bundled in the price. That is why I want the Obi to be able to select the correct provider on outbound calls. I can also present the correct Caller ID with Anveo after verification. I set that up yesterday and it is working well.
Sipgate is on SP3. They provide an incoming DID from the UK. This is a backup DID to safeguard against failure of the other 3 DIDs that route to my IVR at Voip.ms. The provider of the UK DIDs experienced an outage last week which was most inconvenient when my Mum tried to let me know my father had gone into hospital. I won't use SP3 for outbound calls except for freephone UK numbers very occasionally.
Google Voice on SP4. US calls only. Why? Because they are free. Why not use them for Canadian calls? Because I am unable to manipulate the Caller ID. That's the biggest drawback. I also can't point my UK DIDs to a GV account because they are not SIP based. My brother in the US calls my GV number which is local to him.
Once my complex maps are set up, the user at home can dial any UK number without needing international codes. They can also dial US / Canadian numbers which will route at the least cost, presenting the correct caller ID for which ever Country the call is arriving in. That will be a pretty slick system. Since the Obi202 supports 4 Service Providers, I thought I would give it a go! Previously I have been unable to use GV reliably (they stopped validating Canadian numbers, so I more or less stopped using them for the last several years).
The digit map side of things is running well now. If I was only using line 1, it would be fine. It handles the number transformation nicely allowing me to dial UK 01, 02 & 07 numbers, as well as 10 & 11 digit North American numbers.
Now comes the task of splitting those calls to the different providers. I've started another thread abut that part of the operation because I'm really not clear on the Outbound Call Routing at all.
Navigation
[0] Message Index
[#] Next page
[*] Previous page