How to use Auto Attendant (dial in SP1 and access SP2)
dpang:
I have just bought a OBILine as well. To my disbelief, when I dian my POTS line it event didn't ring my other phones attached on the device as well, even I enabled this in the OBI configuration. I am not too sure if I have a faulty unit which just can't bridge the call. I will check on the call status when it says it bridges.
dpang:
I gather the following info from the Call Status page when the bridge occur (which has no audio) does it mean anything at all?
Call 1 Terminal 1 Terminal 2
Audio Codec tx=G729; rx=G711U (bridged) tx=G711U; rx=G729 (bridged)
giqcass:
Quote from: dpang on March 22, 2014, 02:03:33 pm
I have just bought a OBILine as well. To my disbelief, when I dian my POTS line it event didn't ring my other phones attached on the device as well, even I enabled this in the OBI configuration. I am not too sure if I have a faulty unit which just can't bridge the call. I will check on the call status when it says it bridges.
First make sure your firmware supports the Obiline.
I installed an Obiline on a OBi202 and I had some issues. Here is where my issues came from. There were changes to the OutboundCallRoutes that needed to be made. There may also be other changes I am unaware of. The easiest way to be sure everything is working properly after installation might be to reset the Obi to factory defaults. If that isn't a good option for you then you can try making manual changes or just try setting the OutboundCallRoutes to defaults.
dpang:
I have the latest firmware 3.0.1 (Build 4330) which supports OBILine starting build 4041. And, where is the OutboundCallRoutes ?
Also, I am still having trouble in bridging calls. The only thing that works so far is the phones attached to the OBI Device. (**9 222 222 222, echo test would work as well aided by the AA)
It is very frustrated to get this piece of hardware to work the way they claimed to do.
Navigation
[0] Message Index
[*] Previous page