Can't Change OutboundCallRoute when primary line is not PSTN
Northern.Bob:
Thanks for all the suggestions guys. After much mucking about I final got it!
Let me first say that the setup is for the rest of the family whom I don't want to accidentally dial long distance on the PSTN line. My own line is running a Linksys 3102 which i set up to do this routing easily. I thought the 3102's dial code was a bit difficult to master until I met the Obi. I had no idea!
I can't have the primary be the PSTN line. The routing code would be massive with having to type all the area codes that need be routed to Sp1.
With the primary set as Sp1 (Voip.ms), I tried QZappy's code "(<**8>514xxxxxxx|<**8>x.450xxxxxxx )" placed in the DigitMap of the Line Port. It was ignored and routed to Sp1. I tried placing a slight variation in the OutboundCallRoute of the Phone Port and got a message "There is no service available to complete your call".
Finally, I put "{(<#:>514xxxxxxx|<#:>x.450xxxxxxx):li}" in the OutboundCallRoute as the second entry and BINGO! Any 514 or 450 number is pre-pended with # which opens up the PSTN line before dialing the number. It won't work if I delete the colon after #. Whew!
Thanks again guys, and one last question (grin): How to speed up dialing? IF I dial # after the number it takes 5 seconds to dial, 15 without the # added. How can I automate the # digit for all phone numbers, or can I?
Bob M.
Northern.Bob:
OOPS. Wrong direction. I think the earlier code was being ignored and at some point after a reboot the primary line was switched to PSTN without my noticing.
75 reboots later I think I nailed it. In the OutboundCallRoute I put:
{(<#:>|911|<1514:514>xxxxxxx|<1450:450>xxxxxxx|310xxxx|411|611):li}
when the primary is Sp1 (and probably Sp2 also) the OBi automagically adds a 1 in front of the number dialed. I had to strip it out before things worked. Doesn't seem to be a problem with shorter numbers such as the 310's or [4-9]11 numbers.
This took so long and so many reboots that I swear I took a year off the OBi's life!
Bob M.
Northern.Bob:
Actually, can anyone explain why the OBi is auto-magically adding a 1 to dialed numbers in the above situation (Primary Line is Sp2 or Sp1) ? Below is what is seen in Call History after dialing a local 514 AC out on the PSTN line:
xray:
There is something to do with the phone port digimap located in the setup wizard which tells me this is a important setting value.
I modified the the outboundcallroute to
{(<#:>|911|3420000):li} and the rest after it. notice that 3420000 is the # should be dialed in landline.
however, I always end up having 15103420000 to my sp1 (GV). 510 is my local area code.
my sp1 digimap: (1xxxxxxxxxx|<1510>[2-9]xxxxxx|<1>[2-9]xxxxxxxxx)
here is the way I fixed it to use landline to dial 3420000
I changed the phoneport digimap.
Default value: ([1-9]|[1-9][0-9]|911|**0|***|#|(Mpli)|**1(Msp1)|**2(Msp2)|**8(Mli)|**9(Mpp))
modified : ([1-9]|[1-9][0-9]|911|3420000|**0|***|#|(Mpli)|**1(Msp1)|**2(Msp2)|**8(Mli)|**9(Mpp))
Why the default value have 911 in both in phone digimap and outboundcallroute. because this way it make sure "911" is a fixed #, other digimap should not change 911 (by adding or subtracting).
my conclusion on this issue why Obi add 1 or 1+area code to the dialed #
Because: Obi first follows the phoneport digimap, if it find matches then it send to outboundcallroute.
If it didn't find matches then it go into the (Mpli) digimap (my primary line, pli, is sp1 in my case) and modify the dialed # to match pli digimap, ie adding 1510. Now Obi find the matches after (Mpli), it send 1510342000 to outboundcallroute. and it ends up in sp1 not landline because it now has 1 in front.
Navigation
[0] Message Index
[*] Previous page