News:

On Tuesday September 6th the forum will be down for maintenance from 9:30 PM to 11:59 PM PDT

Main Menu

Help understanding Outbound Call Routing

Started by xpr722946ghd, May 06, 2017, 09:20:27 PM

Previous topic - Next topic

xpr722946ghd

0808 UK freephone also routing via SP2 instead of SP3.

azrobert

It appears there is something wrong with (Msp2) and it matches any number. I don't see the problem. I don't have the time right now to test it on my OBi, maybe in a couple hours.

Could you try a shorter version of (Msp2) like this:
(911|933|1(403|587|780)xxxxxxx)

Change one of the area codes to match the number you are calling.

azrobert

I have an OBi200, but I don't want to mess with the configuration. I tested the digit map on an OBi110. It's setup differently than yours, using trunks groups. When I tested with SP1 defined with the digit map, the box hung up. Re-booting didn't free it. I had to power cycle the box. There is a max length for a digit map. I don't remember the number, but I don't think the digit map exceeds the limit. Anyway, I tried breaking up the digit map using a user defined map and it worked. Try the following:

ITSP B DigitMap:
(911|933|1(Mcan)xxxxxxx)

User Settings -> User defined Digit Maps -> User Defined Digit Map2
Label: can
DigitMap:
(403|587|780|825|236|250|604|778|204|431|506|709|879|867|782|902|867|226|249|289|343|365|416|437|519|548|613|647|705|807|905|782|902|367|418|438|450|514|579|581|819|873|306|639|867|600|622)

xpr722946ghd

Quote from: azrobert on May 09, 2017, 08:54:40 PM
Try the following:

ITSP B DigitMap:
(911|933|1(Mcan)xxxxxxx)

User Settings -> User defined Digit Maps -> User Defined Digit Map2
Label: can
DigitMap:
(403|587|780|825|236|250|604|778|204|431|506|709|879|867|782|902|867|226|249|289|343|365|416|437|519|548|613|647|705|807|905|782|902|367|418|438|450|514|579|581|819|873|306|639|867|600|622)


Thanks for working on this.  I set the User map, and it is fine.
However, when I enter the ITSP B Digit Map, experiencing the same issues.

So, I logged into the local interface for the Obi.  Guess what.  Although ObiTalk is showing the custom ITSP B Digit Map above, the Obi local interface is prepending Anveo's map, resulting in

(933|*xx|*123|1xxxxxxxxxx|<1>[2-9]xxxxxxxxx|011xx.|xx.|911|933|1(Mcan)xxxxxxx)

I'm assuming this is where the problem is to be found.  Obi & Anveo must have some kind of deal going on!

I attempted disabling auto provisioning using the local interface.  I did this for both LUA Script and ITSP, but to no avail.  The box would reboot in order to make the change.  Then several seconds after loading up, it would reboot a second time and return to the Anveo preppended Digit Map above.

I wonder if your solution over at https://www.obitalk.com/forum/index.php?topic=11376.0 can be used to bypass the Anveo modified Digit Map?

azrobert

User Settings -> User defined Digit Maps -> User Defined Digit Map2
Label: can1
DigitMap:
(911|933|1(Mcan2)xxxxxxx)

User Settings -> User defined Digit Maps -> User Defined Digit Map3
Label: can2
DigitMap:
(403|587|780|825|236|250|604|778|204|431|506|709|879|867|782|902|867|226|249|289|343|365|416|437|519|548|613|647|705|807|905|782|902|367|418|438|450|514|579|581|819|873|306|639|867|600|622)

Phone DigitMap
Change (Msp2) to (Mcan1)

Outbound Route:
Change {(Msp2):sp2} to {(Mcan1):sp2}

azrobert

Quote from: xpr722946ghd on May 09, 2017, 10:19:51 PM
I attempted disabling auto provisioning using the local interface.  I did this for both LUA Script and ITSP, but to no avail.  The box would reboot in order to make the change.  Then several seconds after loading up, it would reboot a second time and return to the Anveo preppended Digit Map above.

Use OBi Expert to disable ITSP Provisioning.

xpr722946ghd

Quote from: azrobert on May 09, 2017, 11:12:25 PM
User Settings -> User defined Digit Maps -> User Defined Digit Map2
Label: can1
DigitMap:
(911|933|1(Mcan2)xxxxxxx)

User Settings -> User defined Digit Maps -> User Defined Digit Map3
Label: can2
DigitMap:
(403|587|780|825|236|250|604|778|204|431|506|709|879|867|782|902|867|226|249|289|343|365|416|437|519|548|613|647|705|807|905|782|902|367|418|438|450|514|579|581|819|873|306|639|867|600|622)

Phone DigitMap
Change (Msp2) to (Mcan1)

Outbound Route:
Change {(Msp2):sp2} to {(Mcan1):sp2}


This might be it.  I'm just heading out to work now but quickly made these changes and performed 3 test calls.

UK call routed correctly to SP1.
Canadian call routed correctly to SP2.
US call routed correctly to SP4.

I've yet to test toll-free North America (assuming it will work since it was working before) an UK toll free which wasn't working before.  They'll have to wait until I'm home later.

Thanks - this turned out to be much more complicated than I had anticipated!

azrobert

If everything works, please try using OBi Expert to disable ITSP Provisioning then test again using my original configuration in Reply#13 or use mod in Reply#22.

xpr722946ghd

Quote from: azrobert on May 10, 2017, 01:51:12 PM
If everything works, please try using OBi Expert to disable ITSP Provisioning then test again using my original configuration in Reply#13 or use mod in Reply#22.

Bizarrely I seem unable to completely disable ITSP Provisioning.  I tried doing so in the Obi Expert settings, along with LUA script, but still when I make changes to the Anveo account (I was trying to force connection to the US server instead of the Canadian one) I get the same thing happening.

The Obi reboots.  Then several seconds later, reboots a second time, resetting to Anveo defaults.  This is with Auto Provisioning disabled in Obi Expert.

I didn't try disabling ObiTalk provisioning.  Do I need to do that too?

azrobert

I don't understand why it doesn't work. If you disabled OBiTalk Provisioning, you wouldn't be able to use OBiTalk to update your OBi. I think you screwed with this enough and I recommend just using the User Defined DigitMaps.

xpr722946ghd

Sorry to resurrect this thread from a few weeks ago.  I've just encountered a challenge today.  SP2 provider not routing outbound calls (account funds issue which I'm waiting for Anveo to sort out).

So I wanted to route a Canadian call to go via SP1 by prefixing with **1, but just got a busy signal.  The call does not appear on the Call History Log.

However applying **4 enabled me to route the Canadian call through GV with no problem.

I looked over the digit maps, and don't see why **1 is not allowing the call to proceed via SP1.
As per azrobert's suggestion, I had left the config as it was since I seem not to be able to disable auto provisioning.

Any further ideas?

azrobert

When you dial "**1 14805551212" rule **1(Msp1) in the DigitMap and {(**1(Msp1)):sp1} in the outbound route come into play.  The dialed "**1" matches the "**1" in the DigitMap rule. The "14805551212" must match a rule in (Msp1). It doesn't, so the call fails. Add rule "1xxxxxxxxxx" to (Msp1) to fix the problem. SP1 is the Primary Line and is routed last, so this rule won't affect routing of numbers without a prefix.

xpr722946ghd

Quote from: azrobert on May 25, 2017, 09:31:30 AM
Add rule "1xxxxxxxxxx" to (Msp1) to fix the problem. SP1 is the Primary Line and is routed last, so this rule won't affect routing of numbers without a prefix.

Bang on. That took care of it.  Thanks azrobert for all your help!