Call Waiting Dropping Call
pc44:
Quote from: jimates on June 21, 2011, 04:41:04 pm
The Obi (and google voice) is supposed to support 2 simultaneous sessions per account.
If you can, set up another google voice number on sp2 and test with an incoming call on sp2 while an active call on sp1, and see if the same thing happens.
I called Google Voicemail and kept the connection active on line 1. Then, I called the second Google Voice Number from a landline and did not lose my original connection.
So I am still not sure what the problem is. Only when calling the same number/line do I lose both calls immediately before the second ring.
LeftRight:
Are you running latest 2384 firmware?
It does not seem to happen on my GV calls. After I hear the beep and see the second CallerID on my phone, I simply press hook-flash button and talk to the second caller, and I hookflash again, I get back to the first caller immediately.
In your case, did you hookflash to switch to the second call? or both call were just terminated without doing anything?
pc44:
Hi LeftRight!
Thanks for your post. Yes, I wish my setup was working like yours. In my case, both calls are terminated without doing anything. This is not an intermittent problem and can be reproduced consistently.
Regarding the firmware, I am at 1.2.1 (Build: 2289). As far as I understand, this build does allow for auto-updating via the telephone console. However, when I pick up the line and press ***6, I get the following verbal message: "Software update not available."
Is build 2384 official already? If so, I wonder why it will not come down via ***6.
RonR:
2289 is the latest 'official' release and the only one that can be installed via ***6.
2384 is technically a pre-release, but it's very stable and fixes a number of significant bugs present in 2289.
2384 has to be downloaded from here:
http://www.obihai.com/firmware/OBi-1-2-1-2384.fw
and installed locally.
LeftRight:
I downgraded my unit to 2289, and it worked fine too.
2384 is still a test firmware at the moment, and you may download it first, then manually upgrade your unit through web-browser. *** 6 does not apply until it becomes a official release later on.
You may try 2384 first, and see if problem remains. If the unit still behaves the same on GV call waiting, you might try on other voice services ...
You can easily test call waiting feature on OBiTALK service, and here are the steps (with 2 OBi units) --
1) OBi100 (1) calls into **9 - 222 222 222 (echo test)
2) OBi100 (2) places a call to OBi100 (1)
3) OBi100 (1) will hear a beep, then, see the callerID on the phone (callerID is the OBi number of OBi100(2))
4) OBi100 (1) hits hookflash, and talks to OBi100 (2)
5) OBi100 (1) hits hookflash again, and gets back to echo test.
If this works, then, we narrow down the problem to GV. One way we can do is to factory reset your unit, and check over all GV settings, hopefully we don't need to go this far ...
Navigation
[0] Message Index
[#] Next page
[*] Previous page