Help understanding Outbound Call Routing

<< < (5/7) > >>

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}

Navigation

[0] Message Index

[#] Next page

[*] Previous page