RohitJPatil / sipdroid

Automatically exported from code.google.com/p/sipdroid
GNU General Public License v3.0
0 stars 1 forks source link

starting SIP URI intent doesn't always trigger an outbound call #92

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. look up number with enumdroid enabled
2. select a SIP URI

What is the expected output? What do you see instead?
- expected - sipdroid outgoing call
- instead - blank screen

logcat output:
V/ENUMList( 8824): starting intent sip:351@xxxxxxxx with action
android.intent.action.CALL
I/ActivityManager(   56): Starting activity: Intent {
action=android.intent.action.CALL data=sip:351@xxxxxxxxxx flags=0x10000000
comp={org.sipdroid.sipua/org.sipdroid.sipua.ui.SIPUri} }
W/InputManagerService(   56): Starting input on non-focused client
com.android.internal.view.IInputMethodClient$Stub$Proxy@4372c3b0 (uid=10023
pid=8824)
I/ActivityManager(   56): Displayed activity org.sipdroid.sipua/.ui.SIPUri:
14848 ms

The Log output from this activity ("SIPUri: sip uri: sip:351@xxxxx")
doesn't appear in this case.  Unfortunately the bug is intermittent.

Original issue reported on code.google.com by ray.bellis on 24 Jul 2009 at 11:12

GoogleCodeExporter commented 9 years ago

Original comment by pmerl...@googlemail.com on 26 Jul 2009 at 11:24

GoogleCodeExporter commented 9 years ago

Original comment by pmerl...@googlemail.com on 22 Aug 2009 at 1:06