answers phone call immediately and fakes ringing

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Register with a Freeswitch server.
2. Setup Freeswitch so when it receives an incoming call multiple phones 
will ring, including sipdroid.
3. Place incoming call from another phone.
4. Don't answer the phone.

What is the expected output?

All phones should ring until Freeswitch times out and passes call to 
Voicemail.

sipdroid should not answer the call unless autoanswer is configured (it 
isn't) or user deliberately takes action to answer the phone.

What do you see instead?

All phones ring once, then sipdroid answers the phone and passes a faked 
ring tone to the caller (which also is the wrong ring tone for this 
country). The sipdroid phone continues ringing, the other phones become 
silent.

This is really bad because it means the caller has paid for the phone call 
even though nobody has answered the call, because as far as Freeswitch is 
concerned the call was answered.

It also means that it is not possible to answer other phones on the group.

Also as a further complication, something really is badly wrong with the 
audio quality of incoming calls (outgoing is fine), but I think this is 
something for another bug report (after more debugging).

What version of the product are you using? On what operating system?

Version 1.4 beta on the Nexus One running Android 2.1

Which SIP server are you using? What happens with PBXes?

Up to date Freeswitch from subversion.

Which type of network are you using?

wifi.

Please provide any additional information below.

Freeswitch logs clearly show that sipdroid is answering the phone while it 
should still be ringing:

2010-03-20 10:42:57.223379 [NOTICE] mod_openzap.c:1561 Channel 
[OpenZAP/3:1/0397551926] has been answered

Freeswitch then goes and cancels the other phones from ringing because it 
believes the call was answered.

Brian May

Original issue reported on code.google.com by penguin....@gmail.com on 20 Mar 2010 at 12:50

• Merged into: #122

[GoogleCodeExporter]

Original comment by pmerl...@googlemail.com on 20 Mar 2010 at 8:44

• Changed state: Invalid

[GoogleCodeExporter]

Errr... Was was this marked as invalid? Do you mean:

(a) You disagree with my diagnosis? That you think this doesn't happen?

(b) You agree this happens but think for some reason that this is correct 
behaviour?

(c) There is a config option I missed that controls this behaviour?

(d) You really prefer not to deal with bug reports and prefer I don't use this 
program?

(e) Something else?

Unfortunately when somebody marks a bug report as invalid without any comment I 
have 
no idea why and have to start guessing (like I just did).

Brian May

Original comment by penguin....@gmail.com on 20 Mar 2010 at 11:06

[GoogleCodeExporter]

(b) Sipdroid does not answer the phone call. There is no 200 OK message.

Original comment by pmerl...@googlemail.com on 21 Mar 2010 at 10:03

[GoogleCodeExporter]

I have already shown you the freeswitch logs that shows the phone call is being 
answered.

However it seems you are asking for a packet trace demonstrating the problem. 
Fair 
enough. I will see what I can do.

Original comment by penguin....@gmail.com on 22 Mar 2010 at 12:20

[GoogleCodeExporter]

Issue 410 has been merged into this issue.

Original comment by pmerl...@googlemail.com on 9 Apr 2010 at 7:24

[GoogleCodeExporter]

I have tested my multiple-regisration FreeSWITCH config with the earlier 
available 
Sipdroid compilations (1.2.4 and 1.3.12) and it and does not work now (and I 
remember 
that it worked well earlier - on earlier version of Freeswitch though) so it is 
not a 
regression problem, but surely it exists and I'm not sure if it's not the 
Sipdroid's 
bug because all other phones seems to work ok in this FS conf.

When I will be able to do this I will try to check it on the earlier 
compilation of 
FreeSWITCH too.

In meantime please see the two logs from FreeSWITCH attached. One is a trace of 
call 
from ext. 34 to 22 (From ST2030 -> ST2030 and NokiaE51 on one login) and the 
other is 
a call from ext. 22 to 34 (From ST2030 -> ST2030 and G1 with Sipdroid on one 
login). 
Both are almost the same up to line number 168. Then after 1/2 rings FreeSWITCH 
gets 
SDP from Sipdroid and drops the ST2030 with the LOSE_RACE cause.

It probably has something to do with latest changes in FreeSWITCH, but all my 
other 
phones in this multiple-client configuration on new svn Freeswitch works OK 
(tested 
on a few Nokia E51s, Linksys SPA-2102s and a G1 with Sipagent). So please do 
not mark 
this bug as invalid yet because it can be that it's not FreeSWITCH's fault.

Original comment by piotrek....@gmail.com on 12 Apr 2010 at 9:00

• Changed state: New

Attachments:

• thomson+nokia+freeswitch.log
• thomson+sipdroid+freeswitch.log

[GoogleCodeExporter]

Original comment by pmerl...@googlemail.com on 4 Jun 2010 at 3:38

• Changed state: Duplicate

[GoogleCodeExporter]

This is an issue for me as well, running FreeSWITCH and Sipdroid.  Also, full 2 
way audio can be heard while the sipdroid device is faking a ring.  It makes my 
sipdroid phone unusable, as it auto answers every call.   If traces are still 
needed, I can provide them using ngrep.

Original comment by nik.mar...@gmail.com on 16 Oct 2010 at 12:29

[GoogleCodeExporter]

Exact same issue here.  Very annoying. Also notice the same issue as nik.martin 
with two way audio when it fakes ring.

Original comment by michael....@gmail.com on 25 Oct 2010 at 12:09

[GoogleCodeExporter]

Exact same issue here.  Very annoying. Also notice the same issue as nik.martin 
with two way audio when it fakes ring.

Original comment by michael....@gmail.com on 25 Oct 2010 at 12:09

[GoogleCodeExporter]

Same issue 2.0.1 beta

Original comment by john...@gmail.com on 7 Jan 2011 at 3:13

[GoogleCodeExporter]

This started happening to me after I enabled the STUN Server feature using the 
Ekiga Stun server. I use Google voice, PBXes.org, HTC Incredible Android 2.2 
SipDroid 2.4 beta.

Original comment by j...@jphein.com on 7 Feb 2012 at 4:57