May 16, 2021, 09:31:12 am *
Welcome, Guest. Please login or register.
News:
 
   Forum Home   Search Login Register OBiTALK  
Pages: [1]
  Print  
Author Topic: Detailed Guide to Configure Obi2162 to dial out using PSTN line on OBi212  (Read 383 times)
jccpa
Jr. Member
**
Posts: 60


« on: April 27, 2021, 01:09:56 pm »

Credit to drgeoff, azrobert, ianobi, and all those who help each other selflessly

**Adapted from "A Tutorial on Digit Maps and Call Routing for OBi Devices"


Devices DO NOT need to be in same ObiTalk group

Definitions:
218211111 = Obi2182, Remote Obi to be routed over 212 PSTN line
212222222 = Obi212, Obi with PSTN directly connectd
aaa = first 4 digits of area code
aaabbbcccc = 10-digit phone number to call
7*aaabbbcccc = Dialing format when typing numbers into 2162 to call
7 = Dialing format to call 212 attached phone
/ = comment. ignore it everywhere and whatever is immediately after

Note: Designed to route by area code. If ALL numbers to be routed
   out the 212 PSTN, replace both instances of [aaa] with xxx
   Remember to remove brackets as well

//
ObiTalk(.)com speed dial 7 for the Obi2182 group.
   **9212222222     /MAKE SURE YOU SET THIS, choose your number

//
Obi 212 / Voice Services / OBiTALK Service / InboundCallRoute
   copy default route that includes all your ObiTalk-registered devices,
      then clear both checkboxes and add to beginning:

   {218211111>(Mli):li},                / don't forget the comma
   {218211111>(<+:>xx.|xx.):li},   /alternative option, strips + from incoming number

//
Obi 212 / Voice Services / OBiTALK Service / DigitMap
   unchanged, nothing to do here

   (<ob>xxxxxxxxx|obxxxxxxxxx)

//
Obi 212 / Physical Interfaces / PHONE Port / DigitMap
   unchanged, nothing to do here. All one line, no spaces

   ([1-9]x?*(Mpli)|[1-9]S9|[1-9][0-9]S9|911|**0|***|#|##|**70(Mli)|**8(Mbt)
   |**81(Mbt)|**82(Mbt2)|**1(Msp1)|**2(Msp2)|**3(Msp3)|**4(Msp4)|**9(Mpp)|(Mpli))  

//
Obi 212 / Physical Interfaces / PHONE 1 / OutboundCallRoute
   unchanged, nothing to do here. All one line, no spaces

   {([1-9]x?*(Mpli)):pp},{(<##:>):li},{(<**70:>(Mli)):li},{(<**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}

//
Obi 212 / Physical Interfaces / Line / DigitMap
   unchanged, nothing to do here

   (xxxxxxxS4|1xxxxxxxxxx|xx.)

//
Obi 212 / Physical Interfaces / Line / InboundCallRoute
   unchanged, nothing to do here

   ph

//
Obi 2182 / Voice Services / ObiTALK Service / DigitMap

   [aaa] xxx xxxx|    /add this after first (

//
Obi 2182 / Voice Services / ObiTALK Service / InboundCallRoute
   unchanged, nothing to do here. Should be all your Obitalk(.)com registered
   devices in 9-digit rrrrrrrrr format, separated by pipe |

   {(rrrrrrrrr|sssssssss)>(xx.):LI},{(rrrrrrrrr|sssssssss):aa},{ph}

//
Obi 2182 / Voice Services / Gateways &TrunkGrps / Voice Gateway1 / Name
   make up a name
  
   vg1

//
Obi 2182 / Voice Services / Gateways &TrunkGrps / Voice Gateway1 / AccessNumber

   PP(ob212222222)      / Obi212 number

//
Obi 2182 / Voice Services / Gateways &TrunkGrps / Voice Gateway1 / DigitMap
   unchanged, nothing to do here.

   (xx.)

//
Obi 2182 / IP Phone / PHONE Settings / OutboundCallRoute
   copy default route that includes all your ObiTalk-registered devices,
      then clear both checkboxes and add to beginning:  

   {([aaa]xxx xxxx):vg1},   / don't forget the comma

//


Want to see all the challenges without these steps? Look here:
http://www.obitalk.com/forum/index.php?topic=18103.60
« Last Edit: May 04, 2021, 08:33:15 am by jccpa » Logged
jccpa
Jr. Member
**
Posts: 60


« Reply #1 on: April 27, 2021, 01:14:36 pm »

Please test and let me know of any changes or additions? Thanks.
Logged
drgeoff
Hero Member & Beta Tester
*****
Posts: 5321


« Reply #2 on: April 27, 2021, 04:39:44 pm »

That is basically what I have had running for years.  My differences:

1.  OBi110 instead of OBi212.  OBi100 instead of OBi2182.

2.  I don't have a speed dial explicitly configured. Not clear why you need that.

3.  The OBi110 with PSTN line is in the UK.  Gateway calls coming in to that OBi are not sent directly to the LINE port but instead to SP1.  SP1 is registered to a FreePBX server which has time of day and day of week outbound routeing rules.  Those decide whether the call is to proceed over a SIP trunk on the PBX or be sent back to the OBi (SP2) to be DTMF dialled out on the PSTN line.

4.  The originating OBi100 (in Japan) has a User Defined Digit Map which caters for the vagaries of the numbers of the permitted call destinations.  That map is then used in its Phone port digit map and OutboundCallRoute.
Logged
jccpa
Jr. Member
**
Posts: 60


« Reply #3 on: April 27, 2021, 06:14:07 pm »

That is basically what I have had running for years.  My differences:

1.  OBi110 instead of OBi212.  OBi100 instead of OBi2182.

2.  I don't have a speed dial explicitly configured. Not clear why you need that.

3.  The OBi110 with PSTN line is in the UK.  Gateway calls coming in to that OBi are not sent directly to the LINE port but instead to SP1.  SP1 is registered to a FreePBX server which has time of day and day of week outbound routeing rules.  Those decide whether the call is to proceed over a SIP trunk on the PBX or be sent back to the OBi (SP2) to be DTMF dialled out on the PSTN line.

4.  The originating OBi100 (in Japan) has a User Defined Digit Map which caters for the vagaries of the numbers of the permitted call destinations.  That map is then used in its Phone port digit map and OutboundCallRoute.

Yeah, I didn't create anything new here. I took the parts you guys all helped me with and applied them to fresh hardware and took note of the locations and specific changes, including syntax. Syntax messed me up and frustrated us all. Maybe this can help the next guys avoid that.

I believe in following or even cutting a path and laying asphalt behind me. If we've spent the effort to work out the details, let's make it clear and easier for those who follow. Pay it forward Wink

I appreciate all the help and the patience. I've been the guy on the other end. Thanks for sticking with me on this project. I learned a lot about Obi syntax and workings.

Sounds like an interesting setup you have. I've seen some topics mention FreePBX but haven't messed with it yet. I do have a 110 floating around somewhere, as mentioned in my older topics.

But I was relying on GV to "do it all" back then. Now we're using other VoIP and some GV as a provider, not a complete solution.

BTW, order Obi212 from NEWEGG(.)com I ordered 212's 3 times in the past month from Amazon (direct and fulfilled by Amazon) and they were all 202's. Amazon blocked my review mentioning that problem, so people will keep ordering and getting the wrong product.

Let me know how I can help. Any time.

Logged
myobinameisinuse9987
Jr. Member
**
Posts: 38


« Reply #4 on: April 28, 2021, 05:15:06 pm »

SLIMEBALL SON-OF-A-GUN!!!

Stopped working.

As soon as I configured GV on the phone SPx

Call History 2182 when it worked 4/27 15:14:25  :

To PP1(7*1aaabbbcccc)

Call History 212 when it worked 4/27 15:14:29 :

To LI1(1aaabbbcccc)


But NOW...

Call History 2182 when it doesn't work 4/28 19:54:19 :

To PP1(7*+1aaabbbcccc)


See the LEADING +  Huh

azrobert posted this in the other thread:
Quote
I also don’t understand why the “+” prefix.

Use this OBi212 OBiTalk inbound route to remove the “+”:
OBi212 OBiTalk inbound route:
{111111111>(<+:>xx.|xx.):li}

(snip)It does matter, GV prepends a “+”.

So apparently once GV is added to the phone as SP, the magical and destructive + appears and pollutes the packets  Cry

Helps explain why the fresh phones worked and the already config'd phones didn't and now they don't, either. Grrr.

Okay, so now to address this "+" part and keep trying.


Logged
jccpa
Jr. Member
**
Posts: 60


« Reply #5 on: May 04, 2021, 08:32:56 am »

SOLVED:

using azrobert suggestion:

Obi 212 / Voice Services / OBiTALK Service / InboundCallRoute

   {218211111>(<+:>xx.|xx.):li}   /alternative option, strips + from incoming number


If you have trouble with GV or something else adding + to the number, use the alternative. I've updated the original post to show both options.

Thanks again to all for the suggestions and help.
Logged
Pages: [1]
  Print  
 
Jump to:  

Powered by SMF 1.1.11 | SMF © 2006-2009, Simple Machines LLC

Advertisement
Advertisement