Obi110 Setup Help
nichmj01:
Thanks everyone! I'll look at and play with the suggested configurations when I have a chance, probably won't be until tomorrow.
nichmj01:
Just wanted to give an update. Again, thanks everyone for all the help. I mostly followed 202Owner's suggestion. I liked that International calls would automatically route through GV. My original requirements didn't ask for this but it greatly simplifies it for my family and the suggestions helped me understand what I needed to do. I like that they can just pick up the phone and make the call like it's the local line and then have it go through GV for the savings.
Anyway here is my current configuration. Please let me know if you see any problems. I tested a bunch of different numbers and looked at the Call History to see how they were being routed so I'm feeling good that it's set up at least close to correctly.
SP1 Google Voice (Msp1) = (1 [2-9]xx xxx xxxx|011 xx.) ;US long distance (must use US prefix = 1), US International (US IDD prefix = 011).
SP1 Service::X_NoRegNoCall = checked
PP1 OBiTALK (Mpp1) = (<ob>xxxxxxxxx|obxxxxxxxxx) ; default
LI1 LINE (Mli1) = (911 | 999 | 990 | 811 | 555 | [2-9]xx xxxx | 1 [2-9]xx xxx xxxx | 011 xx. | xx.) ; T&T Emergency Numbers (911 - Emergency, 999 - Police, 990 - Fire, 811 - Ambulance, 555 - Anti-Crime Hotline) , local (T&T), US Calls (T&T US prefix = 1), T&T Other International (T&T IDD prefix = 011), all unmatched numbers fall through to Line.
PH PHONE Port digit map = (**1(Msp1)|**2(Msp2)|**8(Mli1)|**9(Mpp1)|**0|***|#|[1-9]S9|[1-9][0-9]S9|(Mpp1)|(Mpli))
PH PHONE Port outbound call route = {(<**1:>(Msp1)):sp1},{(<**2:>(Msp2)):sp2},{(<**8:>(Mli1)):li1},{((<**9:>|ob)(Mpp1)):pp1},{**0:aa1},{***:aa2},{(<#:>):li1},{(Mpli):pli}
PH PHONE Port PLI Primary Line = TG1 Trunk Group 1 = sp1,li1
PH PHONE Port (Mpli) = TG1 (Mtg1) = ((Msp1)|(Mli1))
One interesting thing is that I can't just dial an Obi 9 digit number and have it work. I have to use the **9 prefix. When I look at the call history, I see the ob prefix is added twice? (See attached). Am I missing something here? I'm not worried about this since they are probably never gonna make Obi2Obi calls but I thought it was strange.
azrobert:
When you dial 123456789 it is changed to ob123456789 in the Phone port DigitMap
ob123456789 will match rule {((<**9:>|ob)(Mpp1)):pp1} and <ob>xxxxxxxxx in Mpp will add another ob prefix.
The dialed number doesn't use the trunk group because the above rule is to the left of {(Mpli):pli}
The "ob" is optional.
To fix the problem:
PP1 OBiTALK (Mpp) = (xxxxxxxxx)
Change {((<**9:>|ob)(Mpp1)):pp1} to {(<**9:>(Mpp)):pp}
PH PHONE Port PLI Primary Line = TG1 Trunk Group 1 = sp1,li,pp
Now you don't need the **9 prefix and the dialed number will use the trunk group.
Edit:
You don't have to change the Mpp DigitMap
You can remove (Mpp1) from the phone port DigitMap
202Owner:
Quote from: nichmj01 on January 28, 2015, 07:26:32 am
Just wanted to give an update. Again, thanks everyone for all the help. I mostly followed 202Owner's suggestion.
One interesting thing is that I can't just dial an Obi 9 digit number and have it work. I have to use the **9 prefix. When I look at the call history, I see the ob prefix is added twice? (See attached). Am I missing something here? I'm not worried about this since they are probably never gonna make Obi2Obi calls but I thought it was strange.
Cool! You certainly have it under control now. My work here is done. :-)
Note that digit maps are NOT evaluated left-to-right. They are parsed and evaluated en mass, best match wins. So, you can organize them logically to keep them tidy... 911 can go anywhere. I prefer a general left-to-right/specific-to-general/local-to-global digit map organization:
features, extensions, services (911), local/long-distance, toll-free, International, iNum, SIP peering, SIP URI addressing.
Note that call routes ARE evaluated left-to-right, first match wins. I prefer the order I used, OBi routing, my routing.
The 9-digit OBiTALK dialing and auto-routing was a last minute idea that I did not vet (not using OBiTALK). I will revise it and test thoroughly for my own dial plan, but I'm sure you can fix it or set it back to the default manual routing only. I'll post back if I get to it sooner than later.
202Owner:
Quote from: azrobert on January 28, 2015, 08:14:01 am
Change {((<**9:>|ob)(Mpp1)):pp1} to {(<**9:>(Mpp)):pp}
PH PHONE Port PLI Primary Line = TG1 Trunk Group 1 = sp1,li,pp
Now you don't need the **9 prefix and the dialed number will use the trunk group.
Edit:
You don't have to change the Mpp DigitMap
You can remove (Mpp1) from the phone port DigitMap
I'm not in dial plan mode right now, but I'm liking this revision... it leverages the trunk group magic and simplifies everything else... Elegant!
Edit: <dial plan mode ON>
(Mpp1) = OBiTALK = (<ob>xxx xxx xxx|obxxx xxx xxx) ;OBiTALK server account (default setting).
Trunk Group 1 = sp1,li1,pp1
(Mpli) = (Mtg1) = ((Msp1)|(Mli1)|(Mpp1))
Remove |(Mpp1) from the PH PHONE port digit map.
Change {((<**9:>|ob)(Mpp1)):pp1} back to default {(<**9:>(Mpp1)):pp1} in the PH PHONE port outbound call route.
Note that digit maps are limited to 511 characters including spaces... pretty generous but you never know. I prefer to only use spaces to break up x'es as in ([2-9]xx xxx xxxx) to discourage a miscount.
Telephony means test, test, test!
Navigation
[0] Message Index
[#] Next page
[*] Previous page