Call fail, log says deadlock

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

 



Hi Faba,

This seems to just get fixed by https://trac.pjsip.org/repos/ticket/1578.

BR,
nanang


On Thu, Sep 6, 2012 at 10:20 PM, Faba Aa <aafaba at gmail.com> wrote:
> After many tests, I am sure this case depend on network condition, I guess
> it is due to slow stun server response.
>
> "acquire_call("med_tp_timer_cb", call_med->call->index, &call, &dlg);" code
> line catch this case....
>
> How can I avoid this problem?
>
> Any suggestion?
>
> Thanks in advance
>
>
>
> On Wed, Sep 5, 2012 at 8:05 PM, Faba Aa <aafaba at gmail.com> wrote:
>>
>> Hi pjsips,
>>
>>     I got a call fail case. It seems has more chance to reproduce  when
>> stun server response slowly. But can not reproduce this every time under
>> same network conditon.
>>
>>
>> 09:20:26.232   pjsua_call.c  .Incoming (null)
>> 09:20:26.234  pjsua_media.c  ..Call 0: initializing media..
>> 09:20:26.235        icetp00  ...Creating ICE stream transport with 2
>> component(s)
>> 09:20:26.235        icetp00  ....Comp 1: srflx candidate starts Binding
>> discovery
>> 09:20:26.494 stuntp0x44026a !.STUN mapped address found/changed:
>> 145.114.190.185:59907
>> 09:20:33.216        icetp00 !....Comp 1: host candidate 192.168.0.4:47293
>> added
>> 09:20:33.217        icetp00  ....Comp 2: srflx candidate starts Binding
>> discovery
>> 09:20:33.228        icetp00  ....Comp 2: host candidate 192.168.0.4:56630
>> added
>> 09:20:33.230        icetp00  ....ICE stream transport created
>> 09:20:33.230        icetp01  ...Creating ICE stream transport with 2
>> component(s)
>> 09:20:33.231        icetp01  ....Comp 1: srflx candidate starts Binding
>> discovery
>> 09:20:33.234        icetp00 !.Comp 1: Binding discovery complete, srflx
>> address is 145.114.190.185:59907
>> 09:20:33.475 stuntp0x440293  .STUN mapped address found/changed:
>> 145.114.190.185:62147
>> 09:20:33.480        icetp00  .Comp 2: Binding discovery complete, srflx
>> address is 145.114.190.185:62147
>> 09:20:35.581   pjsua_call.c  Timed-out trying to acquire PJSUA mutex
>> (possibly system has deadlocked) in med_tp_timer_cb
>> 09:20:35.582        icetp00  .ICE stream transport destroyed
>> 09:20:38.247        icetp01 !....Comp 1: host candidate 192.168.0.4:36844
>> added
>> 09:20:38.247        icetp01  ....Comp 2: srflx candidate starts Binding
>> discovery
>> 09:20:38.259        icetp01  ....Comp 2: host candidate 192.168.0.4:54071
>> added
>> 09:20:38.260        icetp01  ....ICE stream transport created
>> 09:20:38.260  pjsua_media.c  ...Media index 0 selected for audio call 0
>> 09:20:38.261         test.c  ..Incoming call from <sip:192.168.1.100>!!
>> 09:20:38.261   pjsua_call.c  ..Answering call 0: code=200
>> 09:20:38.261   pjsua_call.c  ...Pending answering call 0 upon completion
>> of media transport
>> 09:20:38.262   pjsua_call.c  Error initializing media channel: Pending
>> operation (PJ_EPENDING) [status=70002]
>> 09:20:38.263      faba_ua.c  ......Call 0 state=DISCONNCTD
>> 09:20:38.263  pjsua_media.c  ......Call 0: deinitializing media..
>> 09:20:38.263  pjsua_media.c  Call 0: deinitializing media..
>> 09:20:38.264 stuntp0x4402c2  .STUN mapped address found/changed:
>> 145.114.190.185:62443
>>
>>
>>
>>
>
>
> _______________________________________________
> 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
>



[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