Unexpected hangup when use pjsua2 on Android.

X
xiaofeng
Wed, Nov 8, 2017 2:12 AM

Hi,

I use the pjsua2 module to build an app on Android, when call state change
to PJSIP_INV_STATE_DISCONNECTED, I un-reference the Call(without calling
delete).

After several calls(max calls out of use), my new call got hangup
unexpectedly. After looking at the logs and code, it seems caused by a
hangup in the finalizer called by Java GC.

By looking at the demo, I can manually delete the call in the onCallState
callback. But doesn't the Call should also check whether the call_id is
owned by it or not before hanging it up?

--
xiaofeng

--
gpg key fingerprint:
2048R/5E63005B
C84F 671F 70B7 7330 4726  5EC8 02BC CBA2 5E63 005B

trans-zh_cn mailing list
trans-zh_cn@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/trans-zh_cn

Hi, I use the pjsua2 module to build an app on Android, when call state change to PJSIP_INV_STATE_DISCONNECTED, I un-reference the Call(without calling delete). After several calls(max calls out of use), my new call got hangup unexpectedly. After looking at the logs and code, it seems caused by a hangup in the finalizer called by Java GC. By looking at the demo, I can manually delete the call in the onCallState callback. But doesn't the Call should also check whether the call_id is owned by it or not before hanging it up? -- xiaofeng -- gpg key fingerprint: 2048R/5E63005B C84F 671F 70B7 7330 4726 5EC8 02BC CBA2 5E63 005B -- trans-zh_cn mailing list trans-zh_cn@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/trans-zh_cn