Closed GoogleCodeExporter closed 9 years ago
Futher info required, logcat trace or description when this happens.
Original comment by pmerl...@googlemail.com
on 12 Feb 2010 at 6:42
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
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
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
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
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
[deleted comment]
Original comment by pmerl...@googlemail.com
on 13 Feb 2010 at 4:50
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
Original comment by pmerl...@googlemail.com
on 15 Feb 2010 at 10:16
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
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
Original comment by pmerl...@googlemail.com
on 17 Feb 2010 at 8:22
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
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
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
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
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
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
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
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
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:
I installed "SendLog" and here is the part of the log which I think is
relevant, in
particular:
03-01 21:37:09.043 E/AndroidRuntime(21575): java.lang.NullPointerException
03-01 21:37:09.043 E/AndroidRuntime(21575): at
org.sipdroid.media.RtpStreamSender.run(RtpStreamSender.java:269)
Probably p_type == null?
03-01 21:36:50.503 I/ActivityManager( 70): Starting activity: Intent {
act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER]
flg=0x10200000
cmp=org.sipdroid.sipua/.ui.Sipdroid bnds=[125,234][235,352] }
03-01 21:36:50.653 I/ActivityManager( 70): Start proc org.sipdroid.sipua for
activity org.sipdroid.sipua/.ui.Sipdroid: pid=21575 uid=10084 gids={3003, 1006,
1015}
03-01 21:36:50.683 I/dalvikvm(21575): Debugger thread not active, ignoring DDM
send
(t=0x41504e4d l=38)
03-01 21:36:50.703 I/dalvikvm(21575): Debugger thread not active, ignoring DDM
send
(t=0x41504e4d l=40)
03-01 21:36:50.703 V/RenderScript_jni(16866): surfaceDestroyed
03-01 21:36:50.703 V/RenderScript(16866): setSurface 0 0 0x0
03-01 21:36:50.753 D/ViewFlipper(16866): updateRunning() mVisible=false,
mStarted=true, mUserPresent=true, mRunning=false
03-01 21:36:51.373 D/dalvikvm(21575): GC freed 4974 objects / 313176 bytes in
72ms
03-01 21:36:51.453 W/InputMethodManager(21575): Ignoring onBind: cur seq=1528,
given
seq=1527
03-01 21:36:51.553 D/LocationManager(21575): Constructor: service =
android.location.ILocationManager$Stub$Proxy@44973a40
03-01 21:36:51.553 D/LocationManager(21575): removeUpdates: intent =
PendingIntent{449a5048: android.os.BinderProxy@4498cdb8}
03-01 21:36:52.833 I/FieldContext( 130): Bundle = Bundle[{imeOptions=268435460,
packageName=org.sipdroid.sipua, inputType=65569, hint=Called Party Address,
label=,
fieldName=, fieldId=2131230769, singleLine=true}]
03-01 21:36:55.153 I/ActivityManager( 70): Start proc com.android.settings for
broadcast com.android.settings/.widget.SettingsAppWidgetProvider: pid=21595
uid=1000
gids={3003, 3002, 3001}
03-01 21:36:55.173 I/ActivityManager( 70): Starting activity: Intent {
act=android.intent.action.MAIN cat=[android.intent.category.HOME] flg=0x10200000
cmp=com.android.launcher2/.Launcher }
03-01 21:36:55.193 W/InputManagerService( 70): Ignoring hideSoftInput of:
com.android.internal.view.IInputMethodClient$Stub$Proxy@44ab2f88
03-01 21:36:55.203 V/RenderScript_jni(16866): surfaceCreated
03-01 21:36:55.203 V/RenderScript_jni(16866): surfaceChanged
03-01 21:36:55.203 V/RenderScript(16866): setSurface 480 762 0x4e5690
03-01 21:36:55.213 D/ViewFlipper(16866): updateRunning() mVisible=true,
mStarted=true, mUserPresent=true, mRunning=true
03-01 21:36:55.663 I/ActivityManager( 70): Process com.android.vending (pid
18237)
has died.
03-01 21:36:55.663 I/WindowManager( 70): WIN DEATH: Window{44b72ba8
com.android.vending/com.android.vending.SearchAssetListActivity paused=false}
03-01 21:36:55.673 I/WindowManager( 70): WIN DEATH: Window{44ba13d8
com.android.vending/com.android.vending.MyDownloadsActivity paused=false}
03-01 21:36:55.673 I/WindowManager( 70): WIN DEATH: Window{44b07600
com.android.vending/com.android.vending.MyDownloadsActivity paused=false}
03-01 21:36:55.673 I/WindowManager( 70): WIN DEATH: Window{44df5dc8
com.android.vending/com.android.vending.AssetInfoActivity paused=false}
03-01 21:36:55.673 I/dalvikvm(21595): Debugger thread not active, ignoring DDM
send
(t=0x41504e4d l=38)
03-01 21:36:55.693 W/InputManagerService( 70): Starting input on non-focused
client
com.android.internal.view.IInputMethodClient$Stub$Proxy@44b3fa50 (uid=10084
pid=21575)
03-01 21:36:55.693 W/IInputConnectionWrapper(21575): showStatusIcon on inactive
InputConnection
03-01 21:36:55.713 I/dalvikvm(21595): Debugger thread not active, ignoring DDM
send
(t=0x41504e4d l=44)
03-01 21:36:55.813 I/FieldContext( 130): Bundle = Bundle[{imeOptions=0, hint=,
label=, fieldName=, fieldId=-1, packageName=com.android.launcher2, inputType=0}]
03-01 21:36:56.023 D/dalvikvm( 70): GC freed 15814 objects / 794808 bytes in
151ms
03-01 21:36:57.273 I/ActivityManager( 70): Starting activity: Intent {
act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER]
flg=0x10200000
cmp=com.android.contacts/.DialtactsContactsEntryActivity
bnds=[125,586][235,704] }
03-01 21:36:57.653 V/RenderScript_jni(16866): surfaceDestroyed
03-01 21:36:57.653 V/RenderScript(16866): setSurface 0 0 0x0
03-01 21:36:57.663 D/ViewFlipper(16866): updateRunning() mVisible=false,
mStarted=true, mUserPresent=true, mRunning=false
03-01 21:36:59.503 I/ActivityManager( 70): Starting activity: Intent {
act=android.intent.action.VIEW
dat=content://com.android.contacts/contacts/lookup/2866i1.2866i45d30abe8baacdbf/
274
cmp=com.android.contacts/.ViewContactActivity }
03-01 21:36:59.753 D/dalvikvm( 8371): GC freed 15947 objects / 931016 bytes in
73ms
03-01 21:36:59.773 W/Sources ( 8371): Unknown type=com.google,
mime=vnd.com.google.cursor.item/contact_misc
03-01 21:36:59.773 W/Sources ( 8371): Unknown type=com.google,
mime=vnd.com.google.cursor.item/contact_misc
03-01 21:37:00.023 I/ActivityManager( 70): Displayed activity
com.android.contacts/.ViewContactActivity: 431 ms (total 9396 ms)
03-01 21:37:00.033 D/dalvikvm( 8371): threadid=51 wakeup: interrupted
03-01 21:37:00.033 D/dalvikvm( 8371): threadid=49 wakeup: interrupted
03-01 21:37:00.033 D/dalvikvm( 8371): threadid=53 wakeup: interrupted
03-01 21:37:05.463 D/dalvikvm(16866): GC freed 5382 objects / 455024 bytes in
101ms
03-01 21:37:06.373 I/ActivityManager( 70): Starting activity: Intent {
act=android.intent.action.CALL_PRIVILEGED dat=tel:%2B41622962847
cmp=com.android.phone/.PrivilegedOutgoingCallBroadcaster }
03-01 21:37:06.403 D/PhoneUtils( 131): checkAndCopyPhoneProviderExtras: some
or all
extras are missing.
03-01 21:37:06.563 I/ActivityManager( 70): Starting activity: Intent {
flg=0x10000000 cmp=org.sipdroid.sipua/.ui.Activity2 }
03-01 21:37:06.593 D/LocationManager(21575): removeUpdates: intent =
PendingIntent{449a5048: android.os.BinderProxy@4498cdb8}
03-01 21:37:06.763 D/dalvikvm(21575): GC freed 10167 objects / 559592 bytes in
128ms
03-01 21:37:06.933 D/LocationManager(21575): removeUpdates: intent =
PendingIntent{449a5048: android.os.BinderProxy@4498cdb8}
03-01 21:37:06.983 I/ActivityManager( 70): Starting activity: Intent {
flg=0x10000000 cmp=org.sipdroid.sipua/.ui.InCallScreen }
03-01 21:37:07.193 D/dalvikvm(21575): GC freed 5225 objects / 274024 bytes in
67ms
03-01 21:37:07.494 I/ActivityManager( 70): Displayed activity
org.sipdroid.sipua/.ui.InCallScreen: 481 ms (total 1106 ms)
03-01 21:37:09.013 D/dalvikvm(21575): Trying to load lib
/data/data/org.sipdroid.sipua/lib/libOSNetworkSystem.so 0x44946858
03-01 21:37:09.023 D/dalvikvm(21575): Added shared lib
/data/data/org.sipdroid.sipua/lib/libOSNetworkSystem.so 0x44946858
03-01 21:37:09.023 D/dalvikvm(21575): No JNI_OnLoad found in
/data/data/org.sipdroid.sipua/lib/libOSNetworkSystem.so 0x44946858
03-01 21:37:09.023 D/dalvikvm(21575): +++ not scanning
'/system/lib/libwebcore.so'
for 'oneTimeInitializationImpl' (wrong CL)
03-01 21:37:09.023 D/dalvikvm(21575): +++ not scanning
'/system/lib/libmedia_jni.so'
for 'oneTimeInitializationImpl' (wrong CL)
03-01 21:37:09.023 D/dalvikvm(21575): +++ not scanning '/system/lib/libexif.so'
for
'oneTimeInitializationImpl' (wrong CL)
03-01 21:37:09.023 D/dalvikvm(21575): +++ not scanning
'/system/lib/libsrec_jni.so'
for 'oneTimeInitializationImpl' (wrong CL)
03-01 21:37:09.023 D/dalvikvm(21575): +++ not scanning
'/system/lib/libwebcore.so'
for 'createDatagramSocketImpl' (wrong CL)
03-01 21:37:09.023 D/dalvikvm(21575): +++ not scanning
'/system/lib/libmedia_jni.so'
for 'createDatagramSocketImpl' (wrong CL)
03-01 21:37:09.023 D/dalvikvm(21575): +++ not scanning '/system/lib/libexif.so'
for
'createDatagramSocketImpl' (wrong CL)
03-01 21:37:09.023 D/dalvikvm(21575): +++ not scanning
'/system/lib/libsrec_jni.so'
for 'createDatagramSocketImpl' (wrong CL)
03-01 21:37:09.033 D/dalvikvm(21575): +++ not scanning
'/system/lib/libwebcore.so'
for 'socketBindImpl2' (wrong CL)
03-01 21:37:09.033 D/dalvikvm(21575): +++ not scanning
'/system/lib/libmedia_jni.so'
for 'socketBindImpl2' (wrong CL)
03-01 21:37:09.033 D/dalvikvm(21575): +++ not scanning '/system/lib/libexif.so'
for
'socketBindImpl2' (wrong CL)
03-01 21:37:09.033 D/dalvikvm(21575): +++ not scanning
'/system/lib/libsrec_jni.so'
for 'socketBindImpl2' (wrong CL)
03-01 21:37:09.033 D/dalvikvm(21575): +++ not scanning
'/system/lib/libwebcore.so'
for 'getSocketFlagsImpl' (wrong CL)
03-01 21:37:09.033 D/dalvikvm(21575): +++ not scanning
'/system/lib/libmedia_jni.so'
for 'getSocketFlagsImpl' (wrong CL)
03-01 21:37:09.033 D/dalvikvm(21575): +++ not scanning '/system/lib/libexif.so'
for
'getSocketFlagsImpl' (wrong CL)
03-01 21:37:09.033 D/dalvikvm(21575): +++ not scanning
'/system/lib/libsrec_jni.so'
for 'getSocketFlagsImpl' (wrong CL)
03-01 21:37:09.033 D/dalvikvm(21575): +++ not scanning
'/system/lib/libwebcore.so'
for 'setSocketOptionImpl' (wrong CL)
03-01 21:37:09.033 D/dalvikvm(21575): +++ not scanning
'/system/lib/libmedia_jni.so'
for 'setSocketOptionImpl' (wrong CL)
03-01 21:37:09.033 D/dalvikvm(21575): +++ not scanning '/system/lib/libexif.so'
for
'setSocketOptionImpl' (wrong CL)
03-01 21:37:09.033 D/dalvikvm(21575): +++ not scanning
'/system/lib/libsrec_jni.so'
for 'setSocketOptionImpl' (wrong CL)
03-01 21:37:09.033 W/dalvikvm(21575): threadid=17: thread exiting with uncaught
exception (group=0x4001b180)
03-01 21:37:09.033 E/AndroidRuntime(21575): Uncaught handler: thread Thread-43
exiting due to uncaught exception
03-01 21:37:09.043 E/AndroidRuntime(21575): java.lang.NullPointerException
03-01 21:37:09.043 E/AndroidRuntime(21575): at
org.sipdroid.media.RtpStreamSender.run(RtpStreamSender.java:269)
03-01 21:37:09.053 I/Process ( 70): Sending signal. PID: 21575 SIG: 3
03-01 21:37:09.053 I/dalvikvm(21575): threadid=7: reacting to signal 3
03-01 21:37:09.144 I/dalvikvm(21575): Wrote stack trace to
'/data/anr/traces.txt'
03-01 21:37:11.314 I/Process (21575): Sending signal. PID: 21575 SIG: 9
03-01 21:37:11.343 I/ActivityManager( 70): Process org.sipdroid.sipua (pid
21575)
has died.
03-01 21:37:11.343 W/ActivityManager( 70): Scheduling restart of crashed
service
org.sipdroid.sipua/.ui.RegisterService in 5000ms
03-01 21:37:11.363 I/WindowManager( 70): WIN DEATH: Window{44c4a170
org.sipdroid.sipua/org.sipdroid.sipua.ui.Sipdroid paused=false}
03-01 21:37:11.363 I/WindowManager( 70): WIN DEATH: Window{44ba13d8
org.sipdroid.sipua/org.sipdroid.sipua.ui.InCallScreen paused=false}
03-01 21:37:11.383 I/UsageStats( 70): Unexpected resume of
com.android.contacts
while already resumed in org.sipdroid.sipua
03-01 21:37:11.433 W/Sources ( 8371): Unknown type=com.google,
mime=vnd.com.google.cursor.item/contact_misc
03-01 21:37:11.443 W/Sources ( 8371): Unknown type=com.google,
mime=vnd.com.google.cursor.item/contact_misc
03-01 21:37:11.453 W/InputManagerService( 70): Got RemoteException sending
setActive(false) notification to pid 21575 uid 10084
03-01 21:37:16.353 I/ActivityManager( 70): Start proc org.sipdroid.sipua for
service org.sipdroid.sipua/.ui.RegisterService: pid=21630 uid=10084 gids={3003,
1006,
1015}
Original comment by sylvain....@gmail.com
on 1 Mar 2010 at 9:16
After a reboot and fresh run of sipdroid, I get the same crash:
03-01 22:31:04.860 E/AndroidRuntime( 373): java.lang.NullPointerException
03-01 22:31:04.860 E/AndroidRuntime( 373): at
org.sipdroid.media.RtpStreamSender.run(RtpStreamSender.java:269)
It is 100% reproducable so far (tried ~7 times).
Original comment by sylvain....@gmail.com
on 1 Mar 2010 at 9:35
I have an experience with similar kind of bug. I'm trying to call from Sipdroid
(account1) to Ekiga (account2) using the same SIP provider. When I answer the
call in
Ekiga, the Sipdroid crashes:
W/System.err( 3001): java.lang.NullPointerException
W/System.err( 3001): at
org.sipdroid.media.RtpStreamReceiver.<init>(RtpStreamReceiver.java:86)
W/System.err( 3001): at
org.sipdroid.media.JAudioLauncher.<init>(JAudioLauncher.java:95)
W/System.err( 3001): at
org.sipdroid.sipua.UserAgent.launchMediaApplication(UserAgent.java:452)
W/System.err( 3001): at
org.sipdroid.sipua.UserAgent.onCallAccepted(UserAgent.java:620)
W/System.err( 3001): at
org.zoolu.sip.call.Call.onDlgInviteSuccessResponse(Call.java:312)
W/System.err( 3001): at
org.zoolu.sip.dialog.InviteDialog.onTransSuccessResponse(InviteDialog.java:789)
W/System.err( 3001): at
org.zoolu.sip.dialog.ExtendedInviteDialog.onTransSuccessResponse(ExtendedInviteD
ialog.java:314)
W/System.err( 3001): at
org.zoolu.sip.transaction.TransactionClient.onReceivedMessage(TransactionClient.
java:126)
W/System.err( 3001): at
org.zoolu.sip.provider.SipProvider.processReceivedMessage(SipProvider.java:1065)
W/System.err( 3001): at
org.zoolu.sip.provider.SipProvider.onReceivedMessage(SipProvider.java:1195)
W/System.err( 3001): at
org.zoolu.sip.provider.UdpTransport.onReceivedPacket(UdpTransport.java:117)
W/System.err( 3001): at org.zoolu.net.UdpProvider.run(UdpProvider.java:189)
I/System.out( 3001): AudioLauncher: starting java audio..
W/dalvikvm( 3001): threadid=57: thread exiting with uncaught exception
(group=0x4001e180)
I/System.out( 3001): SipProvider: received new SIP message null SIP/2.0 200 OK
E/AndroidRuntime( 3001): Uncaught handler: thread Thread-537 exiting due to
uncaught
exception
E/AndroidRuntime( 3001): java.lang.NullPointerException
E/AndroidRuntime( 3001): at
org.sipdroid.media.RtpStreamSender.run(RtpStreamSender.java:269)
Original comment by jiri....@gmail.com
on 4 Mar 2010 at 3:37
I just would like to add the information that the same happens even in the
opposite
direction (calling from Ekiga to Sipdroid). The logcat is in both directions
the
same.
Original comment by jiri....@gmail.com
on 7 Mar 2010 at 7:32
In upcoming version 1.4 instead of the force close a "no codec" error message
should
appear. To further debug the cause a SIP trace needs to be done.
Original comment by pmerl...@googlemail.com
on 9 Mar 2010 at 9:07
Issue 345 has been merged into this issue.
Original comment by pmerl...@googlemail.com
on 9 Mar 2010 at 9:07
I am having the same bug with 1.4. Sipdroid crashes when placing a call. At
first it
didnt happen but after some time this problem appeared and wont work anymore
until
reinstall, but after some time it happens again
Original comment by marcusde...@gmail.com
on 10 Mar 2010 at 3:34
@ comment 27:
What exactly do you mean with SIP trace? Wireshark trace on the air interface or
something which traces direct on the device? For the first I've at the moment
unfortunately no sparse WLAN access point with ethernet interface to do so - my
current configuration is WLAN AP integrated in DSL modem. If case two is
possible
(trace straight on the device) pls tell me how to proceed.
Thanks
Original comment by bloatm...@googlemail.com
on 10 Mar 2010 at 6:07
Original comment by pmerl...@googlemail.com
on 3 Apr 2010 at 3:26
Original comment by pmerl...@googlemail.com
on 5 Apr 2010 at 8:32
Same problem ("The application Sipdroid((process org.sipdroid.sipua) has stopped
unexpectedly. Please try again")
HTC HERO
Rom: MODACO 3.2
Radio: 63.18.55.06EU
Original comment by lucio.ma...@gmail.com
on 21 Apr 2010 at 1:32
Why does this say closed & fixed?
Same problem, htc evo, sipdroid app, worked fine but now does not ring on
outgoing call, user on other end
picks up to silence and call continues to stay connected in background.
Original comment by tye.atw...@gmail.com
on 28 May 2010 at 5:02
Same problem, how can i fix this?????
Original comment by bvian...@gmail.com
on 29 Sep 2010 at 12:34
I installed it on my Honeycomb Acer A500.
When I make an outgoing call to Indonesia, it works fine.
When I call Germany, it crashed the kernel (Reboot!)
Original comment by hansfba...@gmail.com
on 19 May 2011 at 12:52
I'm in US. Is calling Indonesia or other countries free?
Original comment by juzbha...@gmail.com
on 28 Jul 2011 at 8:13
not if it is due to open another issue, but I have the same problem with
Sipdroid 3.6 beta and Samgsung galaxy S3.
I am having the same bug. Sipdroid crashes when placing a call. At first it
didnt happen but after some time this problem appeared and wont work anymore
until
reinstall, but after some time it happens again.
# What steps will reproduce the problem?
The problem occurs when making an outgoing call using the native codec gsm,
speedx.
# What is the expected output? Instead What do you see?
The logcat says:
org.sipdroid.sipua dalvikvm JNI ERROR: env -> self != theread-self (....
vs .....);
org.sipdroid.sipua libc Fatal signal 11 (SIGSEGV) at ......
code=1.....
# What version of the product are you using? On what device / operating system?
Sipdroid 3.6 beta and Samgsung Galaxy S3 (GT-I9300) with android 4.3.
# Which SIP server are you using? What happens With PBXes?
I'm using a sip account generated through PBXes 8did.com
# Which type of network are you using?
the problem occurs in networks 3g, h+, wlan.
Original comment by ibarrien...@m-lat.net
on 9 Feb 2015 at 7:19
additionally, to reproduce the error becomes necessary to close completely
Sipdroid using the exit option and then running it again.
Original comment by ibarrien...@m-lat.net
on 10 Feb 2015 at 6:23
Same problem with Sipdroid 3.6 beta, Android 5.0 (cyanogen mod 12).
Original comment by Sonny.Ra...@gmail.com
on 22 May 2015 at 1:48
Original issue reported on code.google.com by
mail.jan...@gmail.com
on 12 Feb 2010 at 6:11