Closed GoogleCodeExporter closed 9 years ago
Similar issue here with SipDroid 2.0.1 on Moto XT701 (Android 2.1).
It seems as if sipdroid answers the call without the "slide to answer box"
being touched. I hear the incoming audio of the call being played over the
speakers, and a nasty once per second bit of feedback is sent back into the
microphone. Once the real "ringing timeout is reached", the call is simply
hungup, instead of being set as rejected, missed, or whatever should have been
appropriate.
Tested with phone set to silent, vibrate only, ring+vib, sipdroid set to
default ringtone, a different ringtone, "silent" ringtone, all same results.
Temporary workaround is to not forward incoming GV calls to Google Talk, but
that is a major -1 in functionality for me.
Original comment by dhvm...@gmail.com
on 2 Dec 2010 at 3:20
Almost forgot, the same thing happens if the "back" key is pressed on the
phone, or the down volume button. Both of those used to silence the call
without rejecting in sipdroid 1.5ish. Now, no matter what buttons are pushed or
not, sipdroid answers the call and starts the audio...
Original comment by dhvm...@gmail.com
on 2 Dec 2010 at 3:23
Issue verified. Also you get no missed calls showing up on Google Voice
voicemail. BUT, and this is a big but, the call is picked up even if my phone
isn't connected to the pbxes server. Meaning that the problem is that pbxes is
picking up the call whether or not there is anyone to route it to. Can anybody
else verify this? put the phone in airplane mode and give it a call, see if it
shows up on GV. That would make this a pbxes problem, not a sipdroid problem.
Original comment by Jason.Ri...@gmail.com
on 10 Dec 2010 at 5:18
I have the same issues as the OP and dhvmail with SipDroid 2.0.1 on Samsung
Epic 4G (Android 2.2) And Nexus One (Android 2.2.1); registered w/ PBXes via
SipDroid.
When someone calls my GV number, I receive the incoming call but after a few
seconds of ringing I hear all kinds of noises and I can actually hear the audio
from the other person's line without even having answered it. My friend who
was testing my setup for me was walking in the mall at the time and I could
hear her entire conversation before I answered. I can confirm that this
happens every time. THAT I could live with and it's even kind of funny, BUT..
My calls NEVER go to my GV voicemail, which is the most important part of this
entire setup for me. If I'm on SipDroid and I miss a call, I'll never get a
voicemail, only a missed call notification. I can check my GV history and see
who called as well, but all callers state that they never reach my voicemail
and that "it just rings and rings and then just disconnects". Callers also
report weird "beeping" and "international calling sounds" when they try to call
me.
I have disabled PBXes Voicemail, tried extending the voicemail pickup time from
20 to 60 seconds and everything in between but nothing works. We need our GV
voicemail!
Original comment by jallen...@gmail.com
on 10 Dec 2010 at 6:02
Jallen521, I'm thinking that the reason that we're seeing this problem has very
little to duo with sipdroid proper but more likely with the way that pbxes is
handling the gtalk trunk. Can you do me a favor in the name of diagnostics? Set
your phone to airplane mode and have somebody call you. If the problem persists
(IE that your calls don't go to Google voice voicemail) then the problem can't
be sipdroid. If that's the case, our bugs are in the wrong spot.
Original comment by Jason.Ri...@gmail.com
on 10 Dec 2010 at 10:17
Jallen, you should also consider posting your false ring tone bug in a
different listing. It'sa legitimate bug with other users including myself
affected, but it we should separate out bugs so they get dealt with faster.
Original comment by Jason.Ri...@gmail.com
on 10 Dec 2010 at 10:21
Hi, I've been having the same issue. I put it in airplane mode and am still
having the same problems.
The call does not reach any of my other phones hooked up to Google Voice either.
Original comment by bernardl...@gmail.com
on 12 Dec 2010 at 8:59
Well then that pretty much settles it. The problem isn't one with sipdroid.
It's pbxes gtalk voice peering system that's causing the issue. I've been on
the pbxes forum, and (because I don't have a paid membership) can't post there.
But someone has raised a question about this problem here, on the last page of
the forum post about google voice peering:
http://www1.pbxes.com/community.php?display=forum&news=1
I'm sorry I can't provide a better link, but their php-will not let me easily
get a better one. I'm sure y'all can use your giant brains to make it. Hell, I
did.
In any case, I'm pretty well convinced that this is not a sipdroid issue. Thus
the place we should be mentioning this is at pbxes. They need to retool their
trunk system with gtalk so that it doesn't pick up until a phone picks up
within your switch setup. Right now what it's doing is picking up immediately
and then waiting for a phone in your switch to pick up. That's why it doesn't
go through to voice mail or show up on missed calls. Och, that's a silly way to
have done things. I'm sure it's less complicated in terms of traffic routing
and coding interface difficulty, but it causes a huge problem in terms of what
google voice is for (IE ringing multiple phones at once based on rules and
schedules)
Here's hoping this issue gets resolved soon!
Original comment by Jason.Ri...@gmail.com
on 13 Dec 2010 at 1:17
Same issue for me. I guess going back to sipphone + GV callback app is better
than having lost calls an no voicemail.
I was really happy with direct calling using this feature, and now have to use
GV callback again.
Original comment by ivanja...@gmail.com
on 17 Dec 2010 at 8:32
A workaround would be turning on PBXes' voicemail in extensions.
Original comment by pmerl...@googlemail.com
on 18 Dec 2010 at 12:28
I'm having this issue too. No calls going to voicemail after linking my GV
account
Original comment by srsolo...@gmail.com
on 19 Dec 2010 at 8:05
After setting up the Sipdroid; I tried calling my GV number several times but
every time it rings for default 30s and never reached my GV voice mail. I tried
deleting my pbxes account and tried, same problem.
Original comment by vjg...@gmail.com
on 20 Dec 2010 at 12:30
I deleted the trunk settings and now calls going back to Google voicemail. The
problem I have is that I use Google voicemail for my cell voicemail on 1 phone
that if not answered rings to my Android phone that's setup receive the
incoming Google voice calls. I would like those calls to ring both my Galaxy
Tab running Sipdroid and my Android phone with Google voice, and if the call
isn't answered still go to voicemail.
Original comment by srsolo...@gmail.com
on 20 Dec 2010 at 12:38
@pmerl, That's not a "workaround" technically speaking, as it doesn't achieve
the intended effect, which is Google Voicemail. It does get you a voicemail,
but it doesn't solve a few of the other problems associated with this bug.
Namely that the other phones that google voice is tree'd don't ring either.
Also, we lose out on voicemail transcription. @srsolomon, @vjgade, if I
understand what you two are saying properly then all I can say is that this is
the exact nature of the bug. In order to have sipdroid ring on your phone, you
have to have incoming calls set up from google voice, but if you do that, calls
will never ring to google voice mail or your other phones, because pbxes "picks
up" immediately. @vjgade this is the exact bug everybody is talking about, you
are not alone, we are all waiting for a fix. @srsolomon, I don't know what to
tell you for the scheme you currently want, except wait for a fix. Right now
what I do is just disable incoming from google voice to my pbxes setup, let
somebody call me, and then call them back if I want to talk. Sorry but there is
nothing else to do until there is a bug fix for this.
Original comment by Jason.Ri...@gmail.com
on 20 Dec 2010 at 3:40
Original comment by pmerl...@googlemail.com
on 20 Dec 2010 at 4:31
@pmerl, just tested, still non-functional. Running up to date version.
Original comment by Jason.Ri...@gmail.com
on 20 Dec 2010 at 8:36
And Now?
Original comment by pmerl...@googlemail.com
on 20 Dec 2010 at 9:04
Still no joy. What did you change?
Original comment by Jason.Ri...@gmail.com
on 20 Dec 2010 at 9:58
Can anyone clarify that this bug has indeed been fixed? I don't think that this
marking is accurate, as the problem still seems to remain, but if a couple
other people could show that this has indeed been fixed then I would attribute
this as a flaw in my own system. As far as I know the same bug still manifests.
Original comment by Jason.Ri...@gmail.com
on 4 Jan 2011 at 7:23
Okay, sorry about that, now verified fixed, also noted in the relevant thread
on the pbxes.org forums. THANKS ALL!!!!
Original comment by Jason.Ri...@gmail.com
on 4 Jan 2011 at 7:45
yay! Finally it has been fixed! Thanks.
Original comment by params...@gmail.com
on 7 Jan 2011 at 7:30
Original issue reported on code.google.com by
params...@gmail.com
on 19 Nov 2010 at 12:12