Can't run pjsua_app.py

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi David,

I'm not familiar with pjsua_app.py, but it appears that you have a bad 
transport configuration which causes the assertion, and then no SIP 
worker threads are created, and the app just quits. Check your transport 
configuration.

Regards,

Bill

On 10/25/2015 6:21 AM, David Villasmil Govea wrote:
> Hello,
>
> I have installed all necessary libs, etc. I can run a py and register 
> properly, etc.
>
> But when I try to run pjsua_app.py i get:
>
> /usr/bin/python /Users/David/Documents/scripts/test.py
> 11:18:10.340 os_core_unix.c !pjlib 2.3 for POSIX initialized
> 11:18:10.344 sip_endpoint.c  .Creating endpoint instance...
> 11:18:10.346          pjlib  .select() I/O Queue created (0x7fc9910622d8)
> 11:18:10.346 sip_endpoint.c  .Module "mod-msg-print" registered
> 11:18:10.346 sip_transport.  .Transport manager created.
> 11:18:10.346   pjsua_core.c  .PJSUA state changed: NULL --> CREATED
> 11:18:10.346 sip_endpoint.c  .Module "mod-pjsua-log" registered
> 11:18:10.346 sip_endpoint.c  .Module "mod-tsx-layer" registered
> 11:18:10.346 sip_endpoint.c  .Module "mod-stateful-util" registered
> 11:18:10.347 sip_endpoint.c  .Module "mod-ua" registered
> 11:18:10.347 sip_endpoint.c  .Module "mod-100rel" registered
> 11:18:10.347 sip_endpoint.c  .Module "mod-pjsua" registered
> 11:18:10.349 sip_endpoint.c  .Module "mod-invite" registered
> 11:18:10.402       pa_dev.c  ..PortAudio sound library initialized, 
> status=0
> 11:18:10.403       pa_dev.c  ..PortAudio host api count=1
> 11:18:10.403       pa_dev.c  ..Sound device count=4
> 11:18:10.403          pjlib  ..select() I/O Queue created (0x7fc99202d828)
> Assertion failed: (type<=PJ_QOS_TYPE_CONTROL && p_param), function 
> pj_qos_get_params, file ../src/pj/sock_qos_common.c, line 45.
> 11:18:10.412 sip_endpoint.c  .Module "mod-evsub" registered
> 11:18:10.412 sip_endpoint.c  .Module "mod-presence" registered
> 11:18:10.412 sip_endpoint.c  .Module "mod-mwi" registered
> 11:18:10.413 sip_endpoint.c  .Module "mod-refer" registered
> 11:18:10.413 sip_endpoint.c  .Module "mod-pjsua-pres" registered
> 11:18:10.413 sip_endpoint.c  .Module "mod-pjsua-im" registered
> 11:18:10.413 sip_endpoint.c  .Module "mod-pjsua-options" registered
> 11:18:10.413   pjsua_core.c  .No SIP worker threads created
> 11:18:10.413   pjsua_core.c  .pjsua version 2.3 for Darwin-15.0/x86_64 
> initialized
> 11:18:10.413   pjsua_core.c  .PJSUA state changed: CREATED --> INIT
>
> Process finished with exit code 134
>
>
> Anyone knows why this is?
>
> Thanks
>
> David
>
> -- 
> DVG
>
> -- 
> Imagination is more important than knowledge
> Albert Einstein
>
>
> _______________________________________________
> Visit our blog: http://blog.pjsip.org
>
> pjsip mailing list
> pjsip at lists.pjsip.org
> http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.pjsip.org/pipermail/pjsip_lists.pjsip.org/attachments/20151025/4d848148/attachment.html>


[Index of Archives]     [Asterisk Users]     [Asterisk App Development]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Security]     [Bugtraq]     [Linux]     [Linux OMAP]     [Linux MIPS]     [Linux API]
  Powered by Linux