Is there a bug in GV Call Waiting calls, or is it a CC issue?
CoalMinerRetired:
Quote from: zapattack on February 22, 2013, 10:06:51 pm
Yes, the situation you describe is similar to what I have experience with the Obi 110.
If you call yourself, the caller-ID behaves as you described, no display even though there is an incoming call.
It appears that the Obi thinks the line is busy, but only partly, so GV keeps on ringing. If I hang up, the incoming call gives a brief ring before disconnecting indicating the call was in the Obi.
Note that on a PSTN line, call waiting tone will not be heard if you have just picked up the phone and there is dial tone, and during dialing or ringing.
At the same time, the caller will hear busy tone, which is what you wanted to avoid by subscribing to call-waiting!
Call-waiting on the PSTN works only during a conversation.
Keep i mind the PSTN is a single channel network, but VoIP is usually two or more call channels per 'line'.
ZapAttack, can you confirm a few other details?
- GV presents the Call Waiting call saying with prompts 'unknown caller'? Even though ID and CNAM are in the log.
- Do you get any immediate reboots of your 110?
- Does the Obi call log show any calls ending suspiciously with "Call Ended (403 Incorrect Authentication)"?
I did some more experimenting. Looks to me like there's an issue in GV with the secomd incoming call always being presented with both Audio Caller ID and as 'unknown caller' even when GV Settings is for all calls to Screening Off and the ID (and CNAM via CC) are present in the Obi call history log.
There are some fields for hook-flash unique to an Obi110. I was also to connect to the second incoming call waiting call with one hook flash, and jump back and forth between the two calls with hook flash. (Need to see if this matches what the manual says.) However, in two of five tests, I got a reboot upon ending one of the two incoming calls.
Unlike in my first, original post, I now do see the incoming Caller ID and CNAM. Also unlike in the first post the two calls were from two different numbers. Suspicion here is the OBI sends a blank Caller ID and CNAM when the second incoming call waiting call is from the same number at the already in progress call.
Will do some more experimenting and report back...
zapattack:
Sorry, I have not looked as deeply into the issue as you have and am not a serious GV user so never had the spontaneous reboots you mention or other issues with 'duplicate' calls.
But I would like to mention that Obi CW caller-ID is not 100% compatible with some older CID units that claim to be CW CID units, thus the click-beep with no display. My Linksys talked to a BellSouth unit that Obi could not signal.
I now have a unit that does CW CID properly, but blanks out for multi-digit international calls.
MRTT:
Quote from: RFord on February 23, 2013, 03:07:30 am
According to the OBihai Support, the issue with incoming caller id not showing up on your phone is that some phones do not show Caller id when you are already on a call. I find this hard to believe.
I work for a telco. We saw the same issue when we migrated to different access gear. The word is that the V-tech phones (and some others) are slightly out of spec for the way the CWCID is supposed to operate. The vtech phones also do not mute for .5 seconds when the CWCID FSK tones are being sent, at least they didn't in our case. It's annoying. And we're still waiting for said access gear manufacturer's firmware update.
Navigation
[0] Message Index
[*] Previous page