Sipdroid crashes (outgoing call)

[GoogleCodeExporter]

When I try to call someone with SIPdroid it crashes with this error message:

"The application Sipdroid((process org.sipdroid.sipua) has stopped
unexpectedly. Please try again"

Sipdroid version: 1.3.11
Handset: Motorola Milestone (Android 2.0.1)

Original issue reported on code.google.com by mail.jan...@gmail.com on 12 Feb 2010 at 6:11

[GoogleCodeExporter]

Futher info required, logcat trace or description when this happens.

Original comment by pmerl...@googlemail.com on 12 Feb 2010 at 6:42

[GoogleCodeExporter]

It happens when I am dialling any number which should be routed via Sipdroid. 
For a
few seconds nothing happens (no ringtone) and then the application crashes. 

I asked someone I tried to call and he said his phone is ringing and when he 
picks up
there is silence. I can still see the green "ongoing call" symbol in the top 
left
corner of the Android homescreen after Sipdroid crashed. The only way to end 
this
"frozen" call ist to restart the handset.

I tried to change the configuration of Sipdroid from "directly connected to
sipgate.de" to "connected to sipgate.de through pbxes.org" but both 
configurations
produce the same error.

Now I reinstalled an older version of Sipdroid and everything works fine again. 

Original comment by mail.jan...@gmail.com on 12 Feb 2010 at 6:54

[GoogleCodeExporter]

One more thing: If I tried to call Sipgate internal numbers (e.g. 10002 for a 
test
call), the application didn't crash and I could hear the automated message.

Original comment by mail.jan...@gmail.com on 12 Feb 2010 at 6:58

[GoogleCodeExporter]

Are you sure of the crash? In issue 317 you mention good voice quality after 
call 
establishment. A logcat trace would be great.

Original comment by pmerl...@googlemail.com on 12 Feb 2010 at 8:02

[GoogleCodeExporter]

In 317 I just checked the 10002 of sipgate.de. After I wrote 317 I tried to call
other numbers and the crash appeared. If you explain to me what logcat is, I 
can try
to do it later.

Original comment by mail.jan...@gmail.com on 12 Feb 2010 at 8:06

[GoogleCodeExporter]

Ok I re-installed 1.3.11 now and now it is not crashing but there is now no 
ringback
tone if I am calling another number which is using connected to VoiP. If I am 
calling
a Pots number, I am getting a ringback tone. With older versions of sipdroid I 
had no
ringback tone if directly connected to sipgate.de but always a ringback tone if
connected through pbxes.org. Now there is no ringback tone for both if I am 
calling
VoiP numbers. So maybe you can merge Issue 317 and 319 because it seeems to be 
related.

Original comment by mail.jan...@gmail.com on 12 Feb 2010 at 8:25

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

Original comment by pmerl...@googlemail.com on 13 Feb 2010 at 4:50

• Changed state: FutureRelease

[GoogleCodeExporter]

Can you please fix this bug soon... it makes Sipdroid unusable for me :-(

Original comment by mail.jan...@gmail.com on 14 Feb 2010 at 2:56

[GoogleCodeExporter]

Original comment by pmerl...@googlemail.com on 15 Feb 2010 at 10:16

• Changed state: Fixed

[GoogleCodeExporter]

This issue is not fixed, unless its in a version not available in the app 
market as
of 12:04 AM EST.

I get this exact problem listed above:

It happens when I am dialling any number which should be routed via Sipdroid. 
For a
few seconds nothing happens (no ringtone) and then the application crashes. 

I asked someone I tried to call and he said his phone is ringing and when he 
picks up
there is silence. I can still see the green "ongoing call" symbol in the top 
left
corner of the Android homescreen after Sipdroid crashed. The only way to end 
this
"frozen" call ist to restart the handset.

Original comment by linuxgr...@gmail.com on 16 Feb 2010 at 5:05

[GoogleCodeExporter]

It should have been fixed in version 1.3.13 (see info box to check your 
version).

Have you tried reinstalling as comment #6 suggests?

Does this only happen to you if you hangup the call while it is still ringing? 
Please 
describe in more detail which steps have to be performed to reproduce this 
issue. 
Also tell us which phone you are using, SIP server etc. Maybe the best would be 
to 
open a new issue report and fill out all questions asked.

Original comment by pmerl...@googlemail.com on 16 Feb 2010 at 8:51

[GoogleCodeExporter]

Original comment by pmerl...@googlemail.com on 17 Feb 2010 at 8:22

• Changed state: New

[GoogleCodeExporter]

This was a fresh install on the night of February 15th, and I had recently 
wiped my
phone (for other reasons) so there were no old configuration settings to 
interfere.

If I dial a call, nothing happens for a few seconds, then, the application 
crashes.
It crashes BEFORE the other phone rings. After the crash message, the other 
phone
starts to ring. When the other person picks it up, they hear silence.

I have a teal "connected" Sipdroid icon in my status bar, after the crash 
message
clears. The only way to get rid of it is to power off the phone or kill the 
Sipdroid
process.

I'm using a Milestone, with 2.0.1, the german version (if that matters), on the 
USA
Tmobile network. I try using Sipdroid over Wifi or Edge. I was trying to test 
the new
Speex codec on Edge, but, it also occurred on Wifi.

Steps to reproduce:

1) Dial an outgoing phone number in Sipdroid, relaying through my Google Voice
account. I am not using pbxes.org

2) Wait for the phone to start ringing. The android phone will show a crash 
message:
"The application Sipdroid (process org.sipdroid.sipua) has stopped unexpectedly.
Please try again". The called phone will then ring.

3) After the app crashes, the teal "active call" icon appears in the top status 
bar. 

4) If the person picks up the called phone they hear silence. The called phone 
will
continue to ring if they don't pick it up. The crashed call can go to voicemail.

At this point, the status bar will show an active call, and if you pull down the
updates screen, the call time will increment (ie: show how long you've been on 
the
silent call). 

The only way to stop the call is to kill the process or turn off the phone.

Original comment by linuxgr...@gmail.com on 18 Feb 2010 at 11:11

[GoogleCodeExporter]

This also happened under the Milestone stock 2.0 (ie: this happened before and 
after
I upgraded to 2.0.1).

I've uninstalled and reinstalled Sipdroid earlier tonight (2/18). It still 
happens. I
don't know how to see what version it is, it says "Version 57" when I go into my
Menu/Application Settings/Manage Applications/Application Info.

This is why I told you when I downloaded it from the market.

Original comment by linuxgr...@gmail.com on 18 Feb 2010 at 11:15

[GoogleCodeExporter]

I also get "The application Sipdroid (process org.sipdroid.sipua) has stopped 
unexpectedly. Please try again." when dialing out. 

Sipdroid 1.3.14.
Nexus One Android 2.1-update1. 

PS. I didn't seen any other Nexus One users so that is why I'm adding this 
comment 
and not just starring this issue. I apologize in advance if knowing that it is 
broke 
on Nexus One is not helpful. Thanks for all your work. 

Original comment by patrick....@gmail.com on 19 Feb 2010 at 8:33

[GoogleCodeExporter]

Is there still a request for logcat output? I've just logged the crash.

http://www.pastebin.com/m6838010
On line 97 is the mentioned process crash.

Further conditions/information:

-Device: Motorola Milestone @ Android 2.0.1 (DACH Firmware)
-Sipdroid: 1.3.14 beta
-SIP-Provider: sipgate.de (using STUN-Server @ stun.sipgate.net:10000)
-Using natted network over AVM FritzBox router
-Incoming calls work just fine
-Outgoing calls are crashing like mentioned above (comment 14)
-SIP-test-calls to 10005@sipgate.de and 10000@sipgate.de do not crash, but 
apparently
I have only onesided communication/voice (don't hear speaking myself in 
echo-test
10005@sipgate.de)

I haven't tried to call over pbxes.org yet (if this is necessary for further
revision, let me know). But with a glance over the debbuging-log I think this 
is a
fundamental audio-initialization cause!?

If you need additional information or more logs under different circumstances 
(e.g.
logs of working incoming call), then please give me some instructions.

Thanks for your great efforts!

bloatmode

Original comment by bloatm...@googlemail.com on 22 Feb 2010 at 10:55

[GoogleCodeExporter]

I have the same problem on the 
nexus one since the update. It was 
working perfectly before. Could 
you make the older version 
available for download so that we 
can use the app until it is fixed?

Original comment by sylvain....@gmail.com on 28 Feb 2010 at 10:03

[GoogleCodeExporter]

Please give us some more useful information. Go on the Android Market and 
install 
the "SendLog" application from there. Then invoke the Sipdroid to crash and 
publish 
here the logfile (via "Attach a file" under your replay).

Original comment by jiri....@gmail.com on 28 Feb 2010 at 10:15

[GoogleCodeExporter]

Sipdroid latest version on G1 without sound. Loged in to iptel.org succesfully, 
but 
when i dial some sip number, it get connected but no dialing sound, no response 
voice.
Yesterday with same settings it was function fine, until it crashed!

Original comment by mzajd...@gmail.com on 28 Feb 2010 at 10:41

[GoogleCodeExporter]

In replay to mzajdlik:

Try to reboot your phone. Sometimes when the Siproid (or an other application 
using 
sound device) crashes, the sound device get blocked and there is no other way 
to fix 
it than reboot the phone.

Original comment by jiri....@gmail.com on 28 Feb 2010 at 10:47

[GoogleCodeExporter]

Now I invoked a crash and got the log with SendLog method -> attachment.

Circumstances:
- Started outgoing sipdroid call direct after fresh reboot
- Getting the log immediately with SendLog after sipdroid error

Original comment by bloatm...@googlemail.com on 1 Mar 2010 at 8:50

Attachments:

• sendlog