Two OBI devices on the same GV number
bergman:
ianobi - Thanks for the clarification. I will try this out in a few days when the second OBI arrives.
bergman:
The Master/Slave configuration posted by ianobi works great. One caveat - this config assumes you have set up each OBI on a separate account. In my case, I set them up on one account for simpler management so some adjustments were required. I'll let ianobi document the required settings. My advice to anyone trying this is to set up both OBI devices in one location and conduct your testing before deploying to separate physical locations. This made my work much simpler and prevented any possible missed calls since I already had one device live.
ianobi:
As bergman points out, there is a potential problem with this setup if you put both OBi devices in the same account. This is because the OBiTALK Portal puts both OBi devices in each others' Circle of Trust. This inserts extra and unwanted rules in both devices OBiTALK InboundCallRoutes.
The solution is to delete the unwanted extra rules so the master OBi has the OBiTALK InboundCallRoute as described in Reply #2 and the slave OBi has an OBiTALK InboundCallROute of simply "ph".
dhartman0172:
Thanks for posting the config. I used it to setup a master (obi200) and slave (obi100). This seems to be working great.
Out of curiosity, what part of the config points to speeddial number three? Is it the slave outboundcalls Route?
Physical Interfaces > Phone Port > OutboundCallRoute
{***:aa2},{(<**9:>(Mpp)):pp},{(<3*>(@@.)):pp}
Currently, like bergman I have both devices in the same account and both device's SP1 pointing to my GV account. Prior to any modifications I make out bound call from each device independent of the other. With the master/slave config if the master (OBI200) needs to be connected to the network in order to use the slave.
Is there a way to modify the config so incoming calls would ring both devices, but out going calls would go through SP1? It would be nice to have the slave work for outgoing calls even if the master was not on the network.
Thanks.
David
ianobi:
Quote
Out of curiosity, what part of the config points to speeddial number three? Is it the slave outboundcalls Route?
Physical Interfaces > Phone Port > OutboundCallRoute
{***:aa2},{(<**9:>(Mpp)):pp},{(<3*>(@@.)):pp}
Yes. This rule {(<3*>(@@.)):pp} is saying match any alphanumeric characters, prepend with 3* and send out on trunk OBiTALK 1. The Obihai servers translate 3* as meaning speed dial number 3 and send the alphanumeric characters to the master OBi. In the master OBi the OBiTALK InboundCallRoute matches anything it receives and routes it the same as if you were dialling from the master OBi Phone Port.
To be absolutely correct for you, we should take this:
Voice Services -> OBiTALK Service -> InboundCallRoute:
{(Mcot)>(Msp1):sp1},{(Mcot)>(<**1:>(Msp1)):sp1},{(Mcot)>(<**2:>(Msp2)):sp2},{(Mcot)>(<**8:>(Mli)):li},{(Mcot)>(<**9:>(Mpp)):pp},{(Mcot)>**0:aa},{(Mcot):aa},{ph}
and modify it to suit an OBi200. The original is based on the Phone Port OutboundCallRoute of an OBi110. If you only use sp1 and sp2, then you probably won't notice any problems.
Quote
Is there a way to modify the config so incoming calls would ring both devices, but out going calls would go through SP1? It would be nice to have the slave work for outgoing calls even if the master was not on the network.
One of the original reasons for this config was that two OBi devices cannot be registered to one GV account at the same time. I don't use GV, but I'm assuming this is still true. You could have a separate GV account for the slave. In this case simply put all the slave OBi100 settings back to default and calls from the slave will go out on its sp1. Incoming calls to the master will still ring both OBi devices.
Navigation
[0] Message Index
[#] Next page
[*] Previous page