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?