Extending an anlogue pbx extension using Obi's
PaulS:
Hi, that is the exact setup I am looking to achieve with 2 X OBI110 to extend an analogue PBX extension by bridging over a LAN.
Can't seem to quite find the correct procedure yet. Any advice would be appreciated.
Also is it possible to make the process invisible, ie as soon as the remote handset is picked up that OBI will connect to the 2nd OBI and the user will hear tone from PBX. Same in reverse, when PBX extension calls OBI 2 it will ring OBI 1 phone. Ideally without users dialing extra digits?
Thanks again, if anyone has any pointers would be a great help.
ianobi:
PaulS – welcome to the forum.
This should work, but note my comments at the end.
Remote OBi 200654321:
Physical Interfaces > Phone Port > DigitMap:
(<:ob200123456>)
Physical Interfaces > Phone Port > OutboundCallRoute
{ob200123456:pp}
PBX OBi 200123456:
Voice Services -> OBiTALK Service -> InboundCallRoute:
{(200654321):li},{ph}
Physical Interfaces -> LINE Port -> InboundCallRoute
{pp(ob200654321)}
If you would like the PBX OBi’s phone to ring as well as the Remote OBi’s phone use:
{ph,pp(ob200654321)}
This will do what you wish, but has a few drawbacks, which may or not matter.
There is no access to local auto attendant 2 at Remote OBi, so some configuration changes are not possible after this is set up.
Remote OBi is really a “dumb phone”. It can only access the PBX line and none of its own or the PBX OBi’s other services.
You might want to consider this Master/Slave setup which gives the Remote OBi a lot more services:
http://www.obitalk.com/forum/index.php?topic=5076.msg32750#msg32750
azrobert:
You can look at my solution here:
http://www.obitalk.com/forum/index.php?topic=5086.0
This topic shows how I configure an OBi.
The first reply is how to modify it to access a resource on a remote OBi.
I use a prefix to direct the call to a resource on the remote OBi.
Using my example you would dial "29" to get dial tone on a distant PSTN line. You can also dial "294805551212" to make a call on the distant PSTN line. Dial "214805551212" to make a call on the distant SP1.
PaulS:
Thanks for your suggestions, will be trying soon, only I don't have PBX system with me so will have to test on site sadly :( in next day or 3
Sure will be back with questions!
The limitations you mentioned are fine, really my goal is simply to add a wired PBX extension in an area where it is not possible or practical to cable to, but there is a LAN covering entire site. As I said ideally the OBI devices will be invisible as far as user actions go - extra digits to be dialed, message prompts etc.
This is my first look at the hardware, I have 2 devices but can see the setup options are immense and its a bit of a minefield for me!
I think after reading some more I need to go back to basics with this technology to understand the terminology and meanings as I would rather not just copy/paste and not understand what I am doing, even if it works!
I prefer to understand what I have done wherever possible! Please bear with me!
Thanks
ianobi:
PaulS – as you seem interested in the “nuts and bolts” here are some explanations:
Remote OBi 200654321:
Physical Interfaces > Phone Port > DigitMap:
(<:ob200123456>)
<aaa:xxx> means replace aaa with xxx. In this case aaa is nothing so as soon as the phone is picked up the nothing is replaced by ob200123456, which is the format needed to send an OBi number over the OBiTALK network.
Physical Interfaces > Phone Port > OutboundCallRoute
{ob200123456:pp}
This means send ob200123456 out on trunk pp1. This is the OBiTALK trunk.
PBX OBi 200123456:
Voice Services -> OBiTALK Service -> InboundCallRoute:
{(200654321):li},{ph}
First rule means send incoming calls with CallerID 200654321 to line. In this case there are no digits so the connection gives PBX dial tone. Second rule means send all other incoming calls to the local Obi Phone Port.
Physical Interfaces -> LINE Port -> InboundCallRoute
{pp(ob200654321)}
Any calls coming in to the Line Port should be forwarded to Obi number 200654321 using trunk pp1.
The workings are invisible to the extension user and the PBX. The extension can be anywhere in the world. Maybe a slight down side is that the call is being set up via the OBiTALK server, although the speech path should resolve itself locally within the local LAN.
As both Obi110s are in the same LAN, it is possible to set up a similar setup using direct SIP calling between the two Obi110s, which would be independent of the OBiTALK network. I guess that can wait for another post ;)
Navigation
[0] Message Index
[#] Next page
[*] Previous page