Absence of Busy Line Detection/Answer Supervision
KevKan:
Recently, I found I had failed to receive a busy signal on what was actually a busy line; it just continued to ring until I terminated the call. I discovered this deficiency when I called a family member’s PTSN at a scheduled time and it was not answered by them or their answering machine. Since I knew the called party had to be at home, I tried calling on my cell phone and immediately received a busy signal.
Is this a known deficiency or am I just becoming aware of it? Is this an ObiHai issue?
KevKan:
After checking further, I believe this is a Google Voice issue. From the, following, it appears XMPP might not support Busy Line Detection,
I made a call to this PTSN line, again in a known busy state, this time using PhonePower as the Service Provider in place of Google Voice. When I did, I immediately received the busy signal, just as I did when using my cell phone. However, when I used PhonePower to call a different number, also in a known busy state, I was surprised when I failed to receive the expected busy signal. The phone just continued to ring, the same as if the call was on GV, until it was terminated. Subsequently it was determined the second number had “Call Waiting” which must suppress a busy signal from being returned.
Anyone else experienced this? Any comments?
Taoman:
Quote from: KevKan on January 11, 2015, 07:42:50 pm
Any comments?
Google Voice does not support "early media." I seriously doubt it has anything to do with XMPP, your OBi device, or Busy Line Detection. Any "media" that is transmitted before the connection is actually made is not supported by Google Voice. This is why you can't use ringback tones or IVR (Interactive Voice Response) with Google Voice.
For instance, try calling the following number with your cell phone and you will get a busy signal. Call the same number thru Google Voice and you will get one ring and then a fast busy signal indicating the call could not be completed.
518-571-0000
Or if you're nostalgic, try calling the following number with your cell phone and listen to the message. Then try calling the same number via Google Voice. All you will hear is ringing. Why? GV doesn't support early media. Google doesn't want to pay for it.
631-265-0000
From freeswitch wiki:
Quote
Another good example is what happens on a busy signal. Using the same parties from the previous example:
Party A picks up her phone, hears dial-tone, and enters a phone number
After a few moments, she hears a busy signal. (This is "early" media - no call has been established)
Party A hangs up
The busy signal is an audible signal - a form of audio media if you will - that lets the calling party know that the call has not gone through. It is an unconnected call, but it still had sound. In a case of per-call billing, this call would not be billed (usually) because it was never connected. The same holds true for calls that are ring/no answer. It even holds true for calls to disconnected numbers where you hear the Special Information Tones (SIT) and a recorded message.
KevKan:
Thank you Taoman for solving the mystery! I guess the old adage. “You get what you pay for” obviously applies here!
I am sure there are other GV users who would like to know their unanswered calls are not always due to no one being available or the absence of an answering device. Are GV deficiencies like this documented anywhere? If so, where might I look?
I stumbled on to this problem while making twice daily scheduled welfare check calls to a 90 year old widow who lives alone. Seconds after concluding one of these calls I had to call her back to ask a question. When I did, the phone just continued to ring. I immediately thought something had occurred that rendered her unconscious. For some reason, I decided to try calling one more time, using my cell phone, before calling her neighbor. Obviously I was relieved when I received the busy signal. Another concern is a possible off-hook situation resulting from not turning off a cordless phone when done. This would also lead you to believe no one was home.
Taoman:
Quote from: KevKan on January 12, 2015, 02:40:02 pm
Are GV deficiencies like this documented anywhere? If so, where might I look?
I am not aware of any Google documentation listing GV's shortcomings. There was a recent post on DSLreports that listed a few although I'm sure you are aware of most of them. Look for the post by Stewart (who is also a member of this forum):
http://www.dslreports.com/forum/r29754149-Other-Google-Voice
An issue Stewart did not mention is the latency added to the call path when forwarding your GV number to another DID (cell phone, work phone, etc). This has the potential to add sufficient lag to cause people to talk over each other. Certainly isn't experienced (or noticed) by most people but enough people complain about it to make it an issue. I had to go through a few SIP/DID providers before I could find one that worked acceptably with Google Voice.
As you said, you get what you pay for.
Navigation
[0] Message Index
[#] Next page