Issue with simulatenous SIP and GSM calls

```
a) Before posting your issue you MUST answer to the questions otherwise it
will be rejected (invalid status) by us
b) Please check the issue tacker to avoid duplication
c) Please provide network capture (wireshark) or Android log (DDMS output)
if you want quick response

What steps will reproduce the problem?
1. Make a videocall by setting H264 + GSM call
2. Close videocall
3. Close GSM Call and app crash

What is the expected output? What do you see instead?
I expected app does not crash after GSM call stop

What version of the product are you using? On what operating system?
latest version by using the following links to download the source files:
svn checkout http://imsdroid.googlecode.com/svn/trunk/imsdroid-read-only
version 2.0 revision 836

Please provide any additional information below.
We have an app, and we want to have simultaenous calls GSM (or 3G) and SIP (to
different destinations obviosly). We want to use the GSM voice as a payment
(we call to a premium number).

We can have both calls without problems, but if we hangup the SIP call and we
try to hangup the GSM call

mAVSession.hangUpCall()

this methods calls to :

org.doubango.ngn.sip

public boolean hangUpCall(){

if (super.isConnected()){

return mSession.hangup();

}

else{

return mSession.reject();

}

}

and in the call to mSession.rejected() , we receives this message:

02-11 10:52:30.466: A/libc(10282): Fatal signal 11 (SIGSEGV) at 0x00000004
(code=1), thread 10282

And the app crashes.

TRACES:

02-12 10:25:15.640: I/GLThread(3331): noticed surfaceView surface lost tid=80
02-12 10:25:15.640: W/EglHelper(3331): destroySurface() tid=80
02-12 10:25:15.691: W/EglHelper(3331): finish() tid=80
02-12 10:25:15.710: D/com.prn.android.cuatroG.Screens.ScreenAV(3331): onStop()
02-12 10:25:15.710: V/Phone(3331): hangUpCall 1
02-12 10:25:15.710: E/tinyWRAP(3331): ***ERROR: function:
"tsip_ssession_handle()"
02-12 10:25:15.710: E/tinyWRAP(3331): file: "src/tsip_ssession.c"
02-12 10:25:15.710: E/tinyWRAP(3331): line: "607"
02-12 10:25:15.710: E/tinyWRAP(3331): MSG: Failed to find dialog with this opid
[3]
02-12 10:25:15.710: E/tinyWRAP(3331): ***ERROR: function:
"tsip_api_common_reject()"
02-12 10:25:15.710: E/tinyWRAP(3331): file: "src/api/tsip_api_common.c"
02-12 10:25:15.710: E/tinyWRAP(3331): line: "84"
02-12 10:25:15.710: E/tinyWRAP(3331): MSG: Reject() failed.
02-12 10:25:15.710: D/com.prn.android.cuatroG.Screens.ScreenAV(3331):
onDestroy()
02-12 10:25:15.714: D/org.doubango.ngn.media.NgnProxyAudioProducer(3331):
stopCallback
02-12 10:25:15.714: D/org.doubango.ngn.media.NgnProxyAudioConsumer(3331):
stopCallback
02-12 10:25:15.714: D/org.doubango.ngn.media.NgnProxyPluginMgr(3331):
OnPluginDestroyed(5,twrap_proxy_plugin_audio_consumer)
02-12 10:25:15.714: D/org.doubango.ngn.media.NgnProxyAudioProducer(3331):
stopCallback
02-12 10:25:15.714: D/org.doubango.ngn.media.NgnProxyPluginMgr(3331):
OnPluginDestroyed(6,twrap_proxy_plugin_audio_producer)
02-12 10:25:15.714: D/org.doubango.ngn.media.NgnProxyVideoProducer(3331):
stopCallback
02-12 10:25:15.714: D/org.doubango.ngn.media.NgnProxyVideoConsumerGL(3331):
stopCallback
02-12 10:25:15.714: D/org.doubango.ngn.media.NgnProxyPluginMgr(3331):
OnPluginDestroyed(7,twrap_proxy_plugin_video_consumer)
02-12 10:25:15.757: D/dalvikvm(3331): GC_EXPLICIT freed 1228K, 52% free
4926K/10119K, external 7763K/8363K, paused 32ms
02-12 10:25:15.761: D/org.doubango.ngn.media.NgnProxyPluginMgr(3331):
OnPluginDestroyed(8,twrap_proxy_plugin_video_producer)
02-12 10:25:15.788: D/dalvikvm(3331): GC_EXPLICIT freed 546K, 57% free
4380K/10119K, external 7763K/8363K, paused 31ms
02-12 10:25:15.792: D/org.doubango.ngn.sip.NgnSipSession(3331): mRefCount=0
02-12 10:25:17.124: I/dalvikvm(3331): Jit: resizing JitTable from 4096 to 8192
02-12 10:25:19.019: V/Phone(3331): Broadcast receive
02-12 10:25:19.019: V/Phone(3331): State idle
02-12 10:25:19.019: V/Phone(3331): hangUpCall 1
02-12 10:25:21.550: I/dalvikvm(3331): threadid=4: reacting to signal 3
02-12 10:25:21.558: I/dalvikvm(3331): Wrote stack traces to
'/data/anr/traces.txt'

```

Original issue reported on code.google.com by `csan...@imagine800.es` on 12 Feb 2014 at 9:33

Reproduce the H264/GSM videocall sequence and capture the Android log. Start with mAVSession.hangUpCall(), then inspect tsip_ssession.c at tsip_ssession_handle() and tsip_api_common.c at tsip_api_common_reject(), which the trace identifies. Done means ending the SIP call and then the GSM call no longer crashes the app.

Written by the indexing model from the issue text.