This must have been asked many times, but I can't find it.
I'd like my local calls to be via the line port on my OBi110. (It get's the right caller ID, among other things.) What is the best way to accomplish this?
Thanks. Kent
If you'd like all calls to go out the LINE Port by default, set:
Physical Interfaces -> PHONE Port -> PrimaryLine : PSTN Line
Then to use another trunk:
**1 + number -> SP1 Service
**2 + number -> SP2 Service
**8 + number -> LINE Port
**9 + number -> OBiTALK Service
If you'd like something more automatic, like international calls to SP1 and all others to the LINE Port, give me the specifics and I'll try to help you with a dial plan that will accomplish it.
Thanks for the help. Let me explain further.
What I was looking for is automatic selection of ports based on digit pattern. Basically, I want 7-digit calls thru the LINE port and 1+ and 011+ calls, etc, via google voice on SP1. Maybe I'll also put 611 to LINE & 411 to SP1, etc.
The actual problem is a bit more complicated since they're installing an overlay code here. But I used to program telephone switches for a living, so I think I can figure out the patterns if I can see how you route different patterns to different ports.
Thanks. Kent
Service Providers -> ITSP Profile A -> General -> DigitMap:
(<**8>[2-9]11|1xxxxxxxxxx|<1>[2-9]xxxxxxxxx|<**8>xxxxxxx|011xx.|(Mipd)|[^*]@@.'@'@@.)
Physical Interfaces -> LINE Port -> DigitMap : ([2-9]11|1xxxxxxxxxx|<1>[2-9]xxxxxxxxx|xxxxxxx|011xx.)
Physical Interfaces -> PHONE Port -> PrimaryLine : SP1 Service
[2-9]11 -> LINE Port
7 digits -> LINE Port
10/11 digits -> SP1 Service
011+ -> SP1 Service
Great. So the trick is service providers.
Just to check, my ITSP-A is set to GoogleVoice. Should I leave this alone & setup ITSP-B for "local port" routing?
(If so, how do I get the ITSP-B page to be editable?)
Thanks.
Sorry, my bad.
I see the patterns "<**8>" is magically inserted on match before the call is routed. Cool.
Just what I needed.
Kent
ITSPB would only be used if you set up another provider, such as one on VoIP or a second Google Voice account.
Thanks.
BTW, could the pattern be simplified to just use "<**8>[2-9]x." as the first phrase & let the
telco switch sort it out?
Placing a call is a two-stage process.
1. The dialed number is processed through the PHONE Port DigitMap, validating and possibly transforming the number.
2. The resulting number is processed through the PHONE Port OutboundCallRoute, routing the call according to the first rule that matches.
Quote from: kenth on August 24, 2011, 11:54:30 AM
BTW, could the pattern be simplified to just use "<**8>[2-9]x." as the first phrase & let the
telco switch sort it out?
I prefer validation over ambiguity. :)
Thanks a lot for your help.
Kent
New at Obi, in fact, first day.
I would like a similar setup but I want all my 1+area code+number to go through LINE (which is Vonage) and all my 011 to go through Google Voice?
Can anyone help?
Quote from: babaganoush on August 26, 2011, 08:55:20 AM
I would like a similar setup but I want all my 1+area code+number to go through LINE (which is Vonage) and all my 011 to go through Google Voice?
Physical Interfaces -> PHONE Port -> PrimaryLine : PSTN Line
Physical Interfaces -> LINE Port -> DigitMap:
([2-9]11|1xxxxxxxxxx|<1>[2-9]xxxxxxxxx|<1aaa>xxxxxxx|<**1>011xx.)
where aaa is your local area code
Service Providers -> ITSP Profile A -> General -> DigitMap:
(1xxxxxxxxxx|<1>[2-9]xxxxxxxxx|<1aaa>xxxxxxx|011xx.|(Mipd)|[^*]@@.'@'@@.)
where aaa is your local area code
[2-9]11 -> LINE Port
7/10/11 digits -> LINE Port
011+ -> SP1 Service
If you could post the setup for the (almost) opposite configuration, I would greatly appreciate it.
Specifically,
7 digit -> SP1
10/11 digit -> SP1
911, 011+, 12+ digit -> Line
**2 -> SP2
Thank you so much for your help!
Quote from: JTravers on September 05, 2011, 03:11:06 PM
7 digit -> SP1
10/11 digit -> SP1
911, 011+, 12+ digit -> Line
**2 -> SP2
Service Providers -> ITSP Profile A -> General -> DigitMap:
(1xxxxxxxxxx|<1>[2-9]xxxxxxxxx|<1aaa>xxxxxxx|<**8>xxxxxxxxxxxxx.|
<**8>[2-9]11|<**8>011xx.|(Mipd)|[^*]@@.'@'@@.)
where aaa is your local area code
Service Providers -> ITSP Profile B -> General -> DigitMap:
(1xxxxxxxxxx|<1>[2-9]xxxxxxxxx|<1aaa>xxxxxxx|011xx.|(Mipd)|[^*]@@.'@'@@.)
where aaa is your local area code
Physical Interfaces -> LINE Port -> DigitMap:
([2-9]11|011xx.|xxxxxxxxxxxxx.|1xxxxxxxxxx|<1>[2-9]xxxxxxxxx|<1aaa>xxxxxxx)
where aaa is your local area code
Physical Interfaces -> PHONE Port -> PrimaryLine : SP1 Service
Default:
7/10/11 digits -> SP1 Service
12+ digits -> PSTN Line
[2-9]11 -> PSTN Line
011+ -> PSTN Line
**2:
7/10/11 digits -> SP2 Service
011+ -> SP2 Service
**8:
7/10/11 digits -> PSTN Line
12+ digits -> PSTN Line
[2-9]11 -> PSTN Line
011+ -> PSTN Line
If 7-digit numbers through the LINE Port are not supposed to be extended to 11-digits, remove <1aaa> from the last rule in the LINE Port DigitMap.
Wow! Thank you so much for your help. It is greatly appreciated.
One question. What does @@.'@'@@. do vs @@. (that's what was originally in my DigitMap)?
Thanks again!
Quote from: RonR on September 05, 2011, 04:16:11 PM
Service Providers -> ITSP Profile A -> General -> DigitMap:
(1xxxxxxxxxx|<1>[2-9]xxxxxxxxx|<1aaa>xxxxxxx|<**8>xxxxxxxxxxxxx.|
<**8>[2-9]11|<**8>011xx.|(Mipd)|[^*]@@.'@'@@.)
where aaa is your local area code
Service Providers -> ITSP Profile B -> General -> DigitMap:
(1xxxxxxxxxx|<1>[2-9]xxxxxxxxx|<1aaa>xxxxxxx|011xx.|(Mipd)|[^*]@@.'@'@@.)
where aaa is your local area code
Physical Interfaces -> LINE Port -> DigitMap:
([2-9]11|011xx.|xxxxxxxxxxxxx.|1xxxxxxxxxx|<1>[2-9]xxxxxxxxx|<1aaa>xxxxxxx)
where aaa is your local area code
Physical Interfaces -> PHONE Port -> PrimaryLine : SP1 Service
Default:
7/10/11 digits -> SP1 Service
12+ digits -> PSTN Line
[2-9]11 -> PSTN Line
011+ -> PSTN Line
**2:
7/10/11 digits -> SP2 Service
011+ -> SP2 Service
**8:
7/10/11 digits -> PSTN Line
12+ digits -> PSTN Line
[2-9]11 -> PSTN Line
011+ -> PSTN Line
If 7-digit numbers through the LINE Port are not supposed to be extended to 11-digits, remove <1aaa> from the last rule in the LINE Port DigitMap.
Quote from: JTravers on September 05, 2011, 08:24:29 PM
One question. What does @@.'@'@@. do vs @@. (that's what was originally in my DigitMap)?
It's for matching SIP URI's (for example, 18005551212@tf.callwithus.com). @@. matches anything, which is too general and interferes with certain other patterns.
Quote from: kenth on August 24, 2011, 11:54:30 AM
BTW, could the pattern be simplified to just use "<**8>[2-9]x." as the first phrase & let the
telco switch sort it out?
RonR's suggestion has another benefit he didn't mention.
When a rule is completely matched the call is routed immediately. The x. at the end of a rule would mean that the Obi has to wait for a 10 second timeout to expire to determine that there are no more digits expected. Only when it has all the digits will it proceed with routing.
911 and no delay feels a lot better than 911 followed by 10 seconds before something happens.
... and called something like "Common Dial Plan Setups"