Obi-100 (or 202!) and Sipsorcery
ianobi:
# bridges the phone port to the line port because of this rule in Phone Port OutboundCallRoute ...,{(<#:>|911):li},...
The default Phone Port OutboundCallRoute is:
{([1-9]x?*(Mpli)):pp},{(<#:>|911):li},{**0:aa},{***:aa2},{(<**1:>(Msp1)):sp1},{(<**2:>(Msp2)):sp2},{(<**8:>(Mli)):li},{(<**9:>(Mpp)):pp},{(Mpli):pli}
You could make changes such that #1, #2 etc replace **1, **2 etc, then maybe use ** to replace # in the default rule. The OBi is very flexible in this respect - they are rules not laws :)
It is worth reading the admin guide to make sure that any rule changes do not give you unexpected results. E.g. single * is used for "Star Codes", so best not use it for other uses.
azrobert:
I did it this way:
Any valid 7 or 10 digit number or 10 digits with a "1" prefix routed to SP1/GV.
Any valid 7 or 10 digit number with a prefix "2" thru "9" routed to SP2/SipSorcery.
SP1 DigitMap:
(1?[2-9]xx[2-9]xxxxxx|<480>[2-9]xxxxxx)
SP2 DigitMap:
(x[2-9]xx[2-9]xxxxxx|x[2-9]xxxxxx)
Add to Phone Port DigitMap:
(Msp1)|(Msp2)|
Add to Phone Port OutCallRoute:
{(Msp1):sp1},{(Msp2):sp2},
If you want to use #2 Thru #9 use SP2 DigitMap:
(#x[2-9]xx[2-9]xxxxxx|#x[2-9]xxxxxx)
Nothing else has to change as long as you place SP2 CallRoute entry before the LI entry.
user17600:
Thanks ian and robert. Been away and just getting back to checking in on this.
Robert, this looks great, but a question for you: does your SS dialplan have multiple accounts, where you use an asterisk (*) to denote the outgoing line (trunk)?
I ask because I'm trying to envisage daily use: if I use SP2 to dial out on my SS trunk 2 (a GV number on SS), then I would need to dial #2*2(555)444-3333. I'm trying to determine if the *2 is being sent properly in your experience.
Thanks, just trying to gather some real-world experiences.
Cheers
azrobert:
I use the prefix (2-9) to determine the outbound trunk in SipSorcery.
You would dial 25554443333.
Below is a sample SipSorcery Dialplan.
Hope I didn't make any mistakes.
outnum="#{req.URI.User}" # Save outbound number
outnum.insert(1,"480") if outnum.match /^[2-9]\d{7}$/ # Insert local area code w/7 digits
if outnum.match /^2(\d{10}$)/ # Prefix 2 = Trunk1
sys.Dial("#{$1}@Trunk1")
elsif outnum.match /^3(\d{10}$)/ # Prefix 3 = Trunk2
sys.Dial("1#{$1}@Trunk2") # Insert "1" before out number
elsif outnum.match /^4(\d{10}$)/ # Prefix 4 = Trunk3
sys.Dial("#{$1}@Trunk3")
end
user17600:
My new OBI-202 arrived last night ;D, but so far I have been completely thwarted in setting up SP3 in the manner I described previously. Sorry to say, I must just not get the settings logic to enable what I would like to do.
So, is there anyone who has a -100 (or a -202) that is using multiple SIP/GV accounts in Sipsorcery, but forces selection of the outbound trunk in SS? As I noted above, with my old ATA, I would dial *1(XXX)xxx-xxxx to force a call on SS trunk 1 (GV in this case), or *2(XXX)xxx-xxxx to force the call on SS trunk 2 (a VOSP), etc, all the way through *9.
Even with the changes suggested by others, I can't seem to get the -202 to pass the *1 on through to SS. Maybe there is no way to do this (in which case I'll need to keep my old ATA), but I have to believe that I'm just missing a particular phrase in the digitmap or call routes.
After I sort this out, I intent to add another SIP provider to SP4, but I want to sort out this SS on SP3 issue first.
Thanks for your assistance and patience.
Navigation
[0] Message Index
[#] Next page
[*] Previous page