Calling Local & Remote Extensions

[azrobert]

This is a continuation of a previous topic here:
http://www.obitalk.com/forum/index.php?topic=5086.0

I thought of a scheme for calling extensions.
Each extension would be assigned a unique 2 digit number, first digit being the OBi#. If there are 2 OBi's and an ATA on the same LAN you can assign either OBi# as the first digit of the ATA extension number. The Speed Dial# corresponds to the extension number.
Assume the following with extension numbers in parenthesis.

OBi#1 on Lan#1
OBi110  (10)  OBi-ID = 200100001
ATA (11)

OBi#2 on Lan#2
OBi202 (22,23)  OBi-ID = 200100002
ATA (24)

Common config for both OBi's:

SpeedDial91 = PP(ob200100001)
SpeedDial92 = PP(ob200100002)

User Defined DigitMap ud2:
(<1:91*>xx|<2:92*>xx)

SP2 X_InboundCallRoute:
{(userid)>(10):ph},},{(user)>(<91*>11):pp},{(userid)>(22):ph},{(userid)>(23):ph2},{(user)>(<92*>24):pp},.............

Note: For extensions "11" and "24" the "91*" and "92*" point to speed dial numbers.

OBiTalk InboundCallRoute:
{(2xxxxxxxx)>(10):ph},{(2xxxxxxxx)>(11):sp2(user@192.168.1.100:5062)},{(2xxxxxxxx)>(22):ph},{(2xxxxxxxx)>(23):ph2},{(2xxxxxxxx)>(24):sp2(user@192.168.1.110:5064)}

All Phone DigitMaps = ((Mud2)|............)

OBi110 Config:
SpeedDial10 = 10
SpeedDial11 = sp2(user@192.168.1.100:5062)
SpeedDial22 = 222
SpeedDial23 = 223
SpeedDial24 = 224

OBi202 config:
SpeedDial10 = 110
SpeedDial11 = 111
SpeedDial22 = 22
SpeedDial23 = 23
SpeedDial24 = sp2(user@192.168.1.110:5064)

OBi202 Phone#1 OutboundCallRoute = {(23):ph2},.........
OBi202 Phone#2 OutboundCallRoute = {(22):ph},...........


** end of config  **


OBi#1 DigitMap will translate Speed Dial23 from "223" to "92*23".
It would then route "23" to OBi#2.
OBi#2 OBiTalk InboundCallRoute would ring ph2.
All other distant extensions would work in a similar manner.

I included all rules in both OBi's.
The rules that don't apply for an OBi would never be used.
I did this to keep the configs as close to the same as possible.

I only have one OBi110, so I can't completely test this.

Edit:
With the help of ianobi I believe the above configuration has been completely tested.

[azrobert]

It looks like I'm late to the game again.  ianobi in his topic "Using any OBi as a home PBX" has a setup to call extensions.

I only have 1 LAN with an OBi110 and an ATA to test with, but I think I solved all my problems.  I have a free PBXes.org account and defined an extension.  I forwarded the extension to the second phone port on my ATA.  Using a phone on port one on my ATA I called the second port via the OBi's SP2 InboundCallRoute and PBXes.org.  This should work calling an ATA extension on another LAN.

This is a different approach than ianobi's, so at least I'm giving you a second option.

I would appreciate if someone would try my config using 2 OBi's.

[ianobi]

Another interesting post! As you say, we have come up with different approaches to a similar aim. Mine was more a local "PBX" based on one OBi; yours could be a worldwide "PBX" based on many OBis.

I have not tested every detail in your setup (I have not got a PBXes account), but it all looks good to me. You might want to consider adding in the auto attendant. Users, who you do not wish to give direct dialling access, could then call an extension using Option 2.

These OBi devices are capable of so much. Now if only they could make a nice cup of tea ... 

[Ostracus]

These OBi devices are capable of so much. Now if only they could make a nice cup of tea ... 

Earl Gray, hot. Make it so, number one.

[azrobert]

ianobi,

Thank you for the reply.  I was beginning to think everybody put me on ignore.

I have another question.
On a match would rule {(user)>(24):PP(200100002)}  send "24" to the remote OBi?

I tried this rule on my OBi110 with its own OBi# thinking the call would go out the OBiTalk network and then come right back, but I received a "Not Found" error.

If this would work then I could eliminate PBXes.org

[ianobi]

On a match would rule {(user)>(24):PP(200100002)}  send "24" to the remote OBi?

This one got me thinking / testing. I could not set up the exact same rules as you suggest, but I did get the equivalent of this to work in my Phone Port OutboundCallRoute dialling 24:

{(<ob200100002*>24):pp}

You could try either of these formats for your rule:

{(user)>(ob200100002*24):pp}

Or, using the speed dial:

{(user)>(92*24):pp}

I tried this rule on my OBi110 with its own OBi# thinking the call would go out the OBiTalk network and then come right back, but I received a "Not Found" error.

Although there is enough capacity to make and receive OBiTALK calls at the same time, I think the problem here is that you cannot call your own OBi from itself.

[azrobert]

ianobi,

Both your suggested formats seemed to work with a minor alteration.  The "<  >" were missing. You forced me to think.  I tested by routing a call to my OBION App.  This didn't confirm the extension number was sent, but I'm confident it was.

Thanks for the help.

Bob

[ianobi]

Hmmm, I missed the <> - too many punctuation marks going around in my brain 

Just to confirm the rule in your setup would be:
{(user)>(<92*>24):pp}

I have just tested this the other way around. Dialling 24 in from OBiAPP (user = 290xxxxxx). It does show 92*24 going out on OBiTALK1. So all looks good.