Shortcut to city calls
azrobert:
You are changing the wrong DigitMap. Change the DigitMap under Physical Interfaces/Phone2.
You also didn't place the rules after the beginning parenthesis.
It should look like this:
(0xxxxxxxxx|0xxxxxxxxxxx|[1-9]|[1-9][0-9]|911|**0|***|#|(Mpli).....................
If I didn't screw up mobile calls will work.
Edit:
If your Primary Line for Phone2 is SP2 (Physical Interfaces/Phone2/Primary Line = SP2) you can keep the rules where you put them, but it should look like this:
(0xxxxxxxxx|0xxxxxxxxxxx|1xxxxxxxxxx|<1>[2-9]xxxxxxxxx|011xx.|xx.|(Mipd)|[^*#]@@.)
Either place will work.
janitorjoe:
Cool, it's working (both local and mobile phones are ringing).
BTW, for the next guy who gets stuck, when you change these settings, you may need to change them thru ObiTalk.com (in Expert Settings) and not directly over LAN to your OBi device....
I had big issues with this (settings sometimes would and other times wouldn't get saved!). See http://www.obitalk.com/forum/index.php?topic=1503.0 for another guy's story.
Summary of actions (note, my default phone and SP phone are "Phone 2" and "SP2" (provider "B"), respectively, and that is visible in your device's Obitalk.com settings.
1. Modified my SP2 phone's DigitMap
In obitalk.com go to Expert Settings for your device, find Service Providers > ITSP Profile B > General Settings (uncheck both checkmarks, then paste this line and save:
(0xxxxxxxxx|0xxxxxxxxxxx|1xxxxxxxxxx|<1>[2-9]xxxxxxxxx|011xx.|xx.|(Mipd)|[^*#]@@.)
It appears the first two make it possible to call city and mobile phones (0x 5555 5555 and 0xxx 5555 5555) in my area.
At first I pasted the additional part outside of the left parenthesis - I took the advice to paste the addition at the beginning too literally!
2. Modified my Phone2's OutboundCallRoute
I had one failure where I incorrectly modified DigiMap as I was trying to figure this out based on http://www.obitalk.com/forum/index.php?topic=1792.0 and also Felix mention "digit map" so I simply strayed away.
In obitalk.com go to your device, go to Expert Config > Physical Interfaces > Phone 2 > Outbound Call Route (uncheck the both checkmarks, then overwrite the default and save). In my case the first two 886's are my country code.
{(<0:00886>xxxxxxxxx):sp2},{(<00886>0xxxxxxxxxxx):sp2},{([1-9]x?*(Mpli)):pp},{(<#:>):ph1},{(<**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}
3. It seems each save action will make obitalk.com push the new settings to your device and reboot it. To be on the safe side I waited 5 minutes between the changes as I didn't want to have any unexpected situations with settings not taking effect.
Thank you for your help and hope this helps others in a similar situation!
janitorjoe:
Quote from: janitorjoe on February 24, 2013, 09:38:47 am
Cool, it's working (both local and mobile phones are ringing).
Today I discovered what's not working: in-country toll free numbers in the following format:
0080-123-4567 (0080-xxx-xxxx)
I get "we could not complete your call, please try again" (I don't know if that's from my OBi or from the toll free number operator).
Does anyone has idea how to modify the rules to make this work?
zapattack:
Dial the failing number and immediately check Status/Call Status before hanging up.
It should show what digits were sent and where.
If the call actually went to the Service Provider, then Call History will show 'Call Connected'.
janitorjoe:
Good idea. But "expect the unexpected": the call did connect, but it didn't connect:
02:36:32 From PH1 To GT2(00801231234)
02:36:33 Call Connected
02:36:37 Call Ended
The "We could not complete your call - Please try again." thing makes the call "connected".
I didn't know whether the message comes from OBi or the 0080 provider, but I just googled it and:
https://productforums.google.com/forum/?fromgroups=#!topic/voice/zZCtLu1Em30
As one of the comments say, there are known issues of GV integration with 3rd party systems. This 0080 isn't a Sprint number, but obviously integration between this 0080 provider and GV doesn't work and the message is from Google Voice.
At least now I know the rule is correct and it's a Google Voice problem.
Thanks!
Navigation
[0] Message Index
[#] Next page
[*] Previous page