@bbnnvv aka Andrzej
the only way to "fully kill PJSIP library" is to do something similar to
System.unloadLibrary("pjsua2");
But since there is no such call, the closest thing you can do is make a
PendingIntent to restart your app; restarting the app will clear out it's
stack/memory and cause all libraries to be unloaded and loaded again when
the application starts.
However, I didn't notice that PJSIP requires such hacks until now / yet.
Only had such problems with Doubango.
On Fri, Oct 27, 2017 at 6:00 PM, pjsip-request@lists.pjsip.org wrote:
Send pjsip mailing list submissions to
pjsip@lists.pjsip.org
To subscribe or unsubscribe via the World Wide Web, visit
http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org
or, via email, send a message with subject or body 'help' to
pjsip-request@lists.pjsip.org
You can reach the person managing the list at
pjsip-owner@lists.pjsip.org
When replying, please edit your Subject line so it is more specific
than "Re: Contents of pjsip digest..."
Today's Topics:
1. Android issues while enabling video (Srikar Reddy Vundi)
2. [BUG] Crash calling pjsua_call_answer2() on UAC call. (b17 c0de)
3. Re: [BUG] Crash calling pjsua_call_answer2() on UAC call.
(b17 c0de)
4. Problems with restarting PJSIP library (bbnnvv)
Message: 1
Date: Fri, 27 Oct 2017 06:38:19 +0000
From: Srikar Reddy Vundi srikar.vundi@inedasystems.com
To: "pjsip@lists.pjsip.org" pjsip@lists.pjsip.org
Subject: [pjsip] Android issues while enabling video
Message-ID:
<PN1PR01MB0350D1DA0B8450BEE8399B5FFA5A0@PN1PR01MB0350.
INDPRD01.PROD.OUTLOOK.COM>
Content-Type: text/plain; charset="iso-8859-1"
Hi,
I successfully enabled video in Android by following the steps in given
link,
https://trac.pjsip.org/repos/wiki/Getting-Started/Android
But my application is not displaying the video layout, from my observation
i figured out that for media type video(index) i was getting
Call media status as PJSUA_CALL_MEDIA_NONE and
VideoIncomingWindowId == -1(Invalid)
App Logs
pjsua_media.c .....Call 1: updating media..
pjsua_media.c .......Media stream call01:0 is destroyed
icetp00 ......Stopping ICE, reason=Remote answer doesn't support ICE
icetp00 ......Destroying ICE session 0xb7c4739c
pjsua_aud.c ......Audio channel update..
strm0xb7c7839c .......VAD temporarily disabled
strm0xb7c7839c .......Encoder stream started
strm0xb7c7839c .......Decoder stream started
pjsua_media.c ......Audio updated, stream #0: speex (sendrecv)
pjsua_media.c .......Media stream call01:1 is destroyed
pjsua_media.c ......Video updated, stream #1: (inactive)
icetp01 .......Destroying ICE session 0xb7c55604
icetp01 ......ICE stream transport 0xb7bbf234 destroyed
ice_session.c ......ICE session 0xb7c55604 destroyed
pjsua_aud.c .....Conf connect: 0 --> 1
conference.c ......Port 0 (Android JNI) transmitting to port 1 (
sip:444@inetra.inedasystems.com)
pjsua_aud.c .....Conf connect: 1 --> 0
conference.c ......Port 1 (sip:id) transmitting to port 0 (Android JNI)
pjsua_core.c .....TX 372 bytes Request msg ACK/cseq=14492
(tdta0xb7b7c0e4) to UDP 192.168.43.112:5060:
ACK sip:444@192.168.43.112:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.43.56:6000;rport;
branch=z9hG4bKPj46fa210c-8ae7-43f4-a1a5-68e00820381a
10-27 11:46:55.671 19582-19788/org.pjsip.pjsua2.app I/System.out:
Max-Forwards: 70
Call-ID: 1ee51668-6013-4b64-8d0c-4f6af2ad5a26
CSeq: 14492 ACK
Content-Length: 0
--end msg--
strm0xb7c7839c !VAD re-enabled
Regards,
Srikar
This email and any files transmitted with it are confidential and intended
solely for the use of the individual or entity to whom they are addressed.
If you have received this email in error please notify the system manager.
This message contains confidential information and is intended only for the
individual named. If you are not the named addressee you should not
disseminate, distribute or copy this e-mail. Please notify the sender
immediately by e-mail if you have received this e-mail by mistake and
delete this e-mail from your system. If you are not the intended recipient
you are notified that disclosing, copying, distributing or taking any
action in reliance on the contents of this information is strictly
prohibited.
I did a few things.
One is i hacked the callback for disconnect and put a pjsua->destroy()
there. That worked but gave ugly errors when it quit.
I have since found a better way is to open the thing in a linux screen
and use perl's open3 to interact with it. It is a bit complex to have
perl run a screen and then interact with the ui, but it works.
On 2017-10-27 10:43 AM, Aleksandar Milenkovic wrote:
@bbnnvv aka Andrzej
the only way to "fully kill PJSIP library" is to do something similar
to System.unloadLibrary("pjsua2");
But since there is no such call, the closest thing you can do is make
a PendingIntent to restart your app; restarting the app will clear out
it's stack/memory and cause all libraries to be unloaded and loaded
again when the application starts.
However, I didn't notice that PJSIP requires such hacks until now /
yet. Only had such problems with Doubango.
On Fri, Oct 27, 2017 at 6:00 PM, <pjsip-request@lists.pjsip.org
mailto:pjsip-request@lists.pjsip.org> wrote:
Send pjsip mailing list submissions to
pjsip@lists.pjsip.org <mailto:pjsip@lists.pjsip.org>
To subscribe or unsubscribe via the World Wide Web, visit
http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org
<http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org>
or, via email, send a message with subject or body 'help' to
pjsip-request@lists.pjsip.org <mailto:pjsip-request@lists.pjsip.org>
You can reach the person managing the list at
pjsip-owner@lists.pjsip.org <mailto:pjsip-owner@lists.pjsip.org>
When replying, please edit your Subject line so it is more specific
than "Re: Contents of pjsip digest..."
Today's Topics:
1. Android issues while enabling video (Srikar Reddy Vundi)
2. [BUG] Crash calling pjsua_call_answer2() on UAC call. (b17 c0de)
3. Re: [BUG] Crash calling pjsua_call_answer2() on UAC call.
(b17 c0de)
4. Problems with restarting PJSIP library (bbnnvv)
----------------------------------------------------------------------
Message: 1
Date: Fri, 27 Oct 2017 06:38:19 +0000
From: Srikar Reddy Vundi <srikar.vundi@inedasystems.com
<mailto:srikar.vundi@inedasystems.com>>
To: "pjsip@lists.pjsip.org <mailto:pjsip@lists.pjsip.org>"
<pjsip@lists.pjsip.org <mailto:pjsip@lists.pjsip.org>>
Subject: [pjsip] Android issues while enabling video
Message-ID:
<PN1PR01MB0350D1DA0B8450BEE8399B5FFA5A0@PN1PR01MB0350.INDPRD01.PROD.OUTLOOK.COM
<mailto:PN1PR01MB0350D1DA0B8450BEE8399B5FFA5A0@PN1PR01MB0350.INDPRD01.PROD.OUTLOOK.COM>>
Content-Type: text/plain; charset="iso-8859-1"
Hi,
I successfully enabled video in Android by following the steps in
given link,
https://trac.pjsip.org/repos/wiki/Getting-Started/Android
<https://trac.pjsip.org/repos/wiki/Getting-Started/Android>
But my application is not displaying the video layout, from my
observation i figured out that for media type video(index) i was
getting
Call media status as PJSUA_CALL_MEDIA_NONE and
VideoIncomingWindowId == -1(Invalid)
App Logs
pjsua_media.c .....Call 1: updating media..
pjsua_media.c .......Media stream call01:0 is destroyed
icetp00 ......Stopping ICE, reason=Remote answer doesn't
support ICE
icetp00 ......Destroying ICE session 0xb7c4739c
pjsua_aud.c ......Audio channel update..
strm0xb7c7839c .......VAD temporarily disabled
strm0xb7c7839c .......Encoder stream started
strm0xb7c7839c .......Decoder stream started
pjsua_media.c ......Audio updated, stream #0: speex (sendrecv)
pjsua_media.c .......Media stream call01:1 is destroyed
pjsua_media.c ......Video updated, stream #1: (inactive)
icetp01 .......Destroying ICE session 0xb7c55604
icetp01 ......ICE stream transport 0xb7bbf234 destroyed
ice_session.c ......ICE session 0xb7c55604 destroyed
pjsua_aud.c .....Conf connect: 0 --> 1
conference.c ......Port 0 (Android JNI) transmitting to port 1
(sip:444@inetra.inedasystems.com
<mailto:sip%3A444@inetra.inedasystems.com>)
pjsua_aud.c .....Conf connect: 1 --> 0
conference.c ......Port 1 (sip:id) transmitting to port 0
(Android JNI)
pjsua_core.c .....TX 372 bytes Request msg ACK/cseq=14492
(tdta0xb7b7c0e4) to UDP 192.168.43.112:5060
<http://192.168.43.112:5060>:
ACK sip:444@192.168.43.112:5060
<http://sip:444@192.168.43.112:5060> SIP/2.0
Via: SIP/2.0/UDP
192.168.43.56:6000;rport;branch=z9hG4bKPj46fa210c-8ae7-43f4-a1a5-68e00820381a
10-27 11:46:55.671 19582-19788/org.pjsip.pjsua2.app I/System.out:
Max-Forwards: 70
Call-ID: 1ee51668-6013-4b64-8d0c-4f6af2ad5a26
CSeq: 14492 ACK
Content-Length: 0
--end msg--
strm0xb7c7839c !VAD re-enabled
Regards,
Srikar
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom
they are addressed. If you have received this email in error
please notify the system manager. This message contains
confidential information and is intended only for the individual
named. If you are not the named addressee you should not
disseminate, distribute or copy this e-mail. Please notify the
sender immediately by e-mail if you have received this e-mail by
mistake and delete this e-mail from your system. If you are not
the intended recipient you are notified that disclosing, copying,
distributing or taking any action in reliance on the contents of
this information is strictly prohibited.