Setting up Obi200 - DigitMap
dima:
hello,
I've followed the config from this thread: https://www.obitalk.com/forum/index.php?topic=9107.msg64244#msg64244
setting up SP1 = FPL, SP2 = GV. I want to dial either US or Canadian number with or without '1'. International numbers will go to SP1.
my current settings are as follow:
Physical interfaces - PHONE 1
DigitMap:
([1-9]S9|[1-9][0-9]S9|*98|211|311|911|1xxxxxxxxxx|[2-9]xxxxxxxxx|011xx.S3|00xx.S3|**0|***|222222222|**[1-3]xx.S3)
OutboundCallRoute:
{**0:aa},{***:aa2},{222222222:pp},{(Msp1):sp1},{(Msp2):sp2}
Service Provider -> ITSP Profile A -> DigitMap:
(<1:>(236|250|778|403|587|780|825|306|639|204|431|416|437|647|807|249|705|226|519|548|289
|365|905|343|613|418|581|450|579|438|514|819|873|709|506|782|902|867)xxxxxxx|(236|250|778|403|587|780|825|306|639|204|431|416|437|647|807|249|705|226|519|548|289
|365|905|343|613|418|581|450|579|438|514|819|873|709|506|782|902|867)xxxxxxx|<**1:>xx.|18(00|88|77|66|55|44)xxxxxxx|*98|911|933)
Service Provider -> ITSP Profile B -> DigitMap:
(1xxxxxxxxxx|[2-9]xxxxxxxxx|<**2:>xx.)
Seems Canadian numbers work but when dialing US number, the message says "there is no call route available".
Wasn't ITSP Profile B Digit map suppose to catch non-listed in profile A area codes and route the call using GV ?
thank you.
azrobert:
First, I think there is a problem with your "A" digit map not related to your problem. You have 2 sets of rules for 10 digit Canadian numbers. I think the 2nd set needs a one prefix like "1(236|250.....)" to route 11 digit numbers. If you don't want to check for 11 digit numbers, delete the 2nd set of 10 digit rules. Also, rule "<1:>" can be coded as "<1>". The colon is optional when only adding characters.
I don't see anything wrong with your code that would cause your error. I think it's caused by corrupted firmware or configuration. I helped someone with a similar problem by ignoring the provider digit map and used a user defined digit map.
User Settings -> User Defined Digit Maps -> User Defined DM2
Label: ud1
DigitMap: (1xxxxxxxxxx|[2-9]xxxxxxxxx|<**2:>xx.)
OutboundCallRoute:
{**0:aa},{***:aa2},{222222222:pp},{(Msp1):sp1},{(Mud1):sp2}
I also had a similar problem and actually fixed the OBi by doing a factory reset and manually re-configured. I first tried to restore the configuration from a backup after the reset, but it didn't work.
dima:
Thanks you azrobert! Very much appreciate you looking into this. If I don't care about dialing with or without '1', I think I do need to check for 11-digit number, so I'll correct the 'A'-map like this:
(<1>(236|250|778|.....omitting for brevity...|902|867)xxxxxxx|(236|250|778|.....omitting for brevity......782|902|867)xxxxxxx|<**1:>xx.|18(00|88|77|66|55|44)xxxxxxx|*98|911|933)
I'll add user-defined map like you suggest and try it out.
this is brand new unit, I got it up and running in less than 5 min for both FPL and GV, so I'm puzzled what could go wrong with firmware. here is what I have:
HardwareVersion 1.4
SoftwareVersion 3.1.0 (Build: 5264)
is this okay version?
I did once used "restore from file" so maybe THAT corrupted it ?
thanks again.
dm.
dima:
Hi azrobert,
Here is my update after trying different things on outbound call route
I had enabled this , thinking that having those **2: **3:, **4: wouldn't hurt if I ever enable other services:
{(<##:>):li},{(<**70:>(Mli)):li},{(<**82:>(Mbt2)):bt2},{(<**81:>(Mbt)):bt},{(<**8:>(Mbt)):bt},{**0:aa},{***:aa2},{(<**1:>(Msp1)):sp1},{(<**2:>(Msp2)):sp2},{(<**3:>(Msp3)):sp3},{(<**4:>(Msp4)):sp4},{(<**9:>(Mpp)):pp},{(Mpli):pli}
then, I coded your suggestion:
{**0:aa},{***:aa2},{222222222:pp},{(Msp1):sp1},{(Mud1):sp2}
it worked! I could make US bound calls with or without '1' and I did NOT do factory reset.
thank you very much for helping.
dima:
Any idea why my local Canadian calls using GV provider ?
Navigation
[0] Message Index
[#] Next page