new OBI110, 1 google voice account, outgoing calls fine, NO incoming calls

<< < (3/6) > >>

RonR:
TimmyP,

Can you answer an incoming call even though the phone isn't ringing?

Try the following to test the OBi's ability to ring the phone attached to the PHONE Port:

1. Dial **0

2. When prompted, press 3 to enter a callback number

3. Dial 0#

4. When the Auto Attendant says Goodbye, hang up

The Auto Attendant should call the OBi PHONE Port.

TimmyP:
OK. Tried this on one of the lines on my account ( but not the one with the known problem ) and the call back worked 1 time. 5 other trials the procedure seemed to work, getting all the proper responses, but no ring back on the phone.

Tim

RonR:
Quote from: TimmyP on March 22, 2012, 12:24:02 pm

OK. Tried this on one of the lines on my account ( but not the one with the known problem ) and the call back worked 1 time. 5 other trials the procedure seemed to work, getting all the proper responses, but no ring back on the phone.


Sorry, but I can't decipher your response.

I assume you are having trouble with one particular OBi.  I don't understand the responses about accounts and lines.

TimmyP:
Sorry for the confusion. There are 3 OBi's on my account. 2 are remote from me right now and one of the remote boxes is not able to receive ( ring the handset ) even though the call shows in the device's log.

So just to play, I tried the **O call back using the device that is next to me. It rang the first time I tried and the next 5 attempts, my phone did not ring back and the 5 missing call backs did not show up in the OBi's log.  All 6 **O calls gave me the same voice prompts from OBi server and ended with a good by, thanks for using OBi technology.
So this malfunction on O# call back may be a different issue as the return call did not show in the call logs when it failed. The original "no ring" problem has the missing calls showing in the device's log as shown using the OBi website.

Reading some others posts, it seems that trusted caller MAY have been an issue for certain cases. I have a trusted caller  ( daughter's cell phone number ) set on this account and have removed and added this number. Also, adding or removing the trusted caller number has no effect on the OBi voice attendant during an inbound call from her cell phone.

Tim

RonR:
Quote from: TimmyP on March 22, 2012, 12:49:36 pm

So just to play, I tried the **O call back using the device that is next to me. It rang the first time I tried and the next 5 attempts, my phone did not ring back and the 5 missing call backs did not show up in the OBi's log.  All 6 **O calls gave me the same voice prompts from OBi server and ended with a good by, thanks for using OBi technology.
So this malfunction on O# call back may be a different issue as the return call did not show in the call logs when it failed. The original "no ring" problem has the missing calls showing in the device's log as shown using the OBi website.


The Auto Attendant callback feature will not work on subsequent attempts if you do not hang up from the Auto Attendant and dial **0 again to start the process over.  There is a bug in the Auto Attendent that causes callbacks to fail when issued from a callback.  Obihai has chosen to ignore several reports to them about this and has not fixed the problem.

Quote from: TimmyP on March 22, 2012, 12:49:36 pm

Reading some others posts, it seems that trusted caller MAY have been an issue for certain cases. I have a trusted caller  ( daughter's cell phone number ) set on this account and have removed and added this number. Also, adding or removing the trusted caller number has no effect on the OBi voice attendant during an inbound call from her cell phone.


I would suggest you temporarily set:

Voice Services -> SP1 Service -> X_InboundCallRoute : ph

to rule out any possibly that your inability to receive incoming calls via Google Voice is related to Circle-of-Trust issues.  Get incoming calls working reliably before attempting anything else.

Navigation

[0] Message Index

[#] Next page

[*] Previous page