Cal not being accepted after an endpoint crashes

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

 



The log file show the message pjsua_call.c Timed-Out trying to acquire
dialog mutex (possibly system has deadlocked) in pjsua_call_hangup()...

please help me understand if we can fix this or not?
the version i use for pjsip is 1.1.

Ravi

On Wed, May 11, 2011 at 3:48 PM, Ravi Kanth <k.ravikanthreddy at gmail.com>wrote:

> Hi,
>
> I have scenario where i am not able to realize if its an issue with the
> pjsip or the sip server.
> From one of the application developed using pjsip i make a call to another
> endpoint and leave it like that for say 3 days.
>
> after that when i come and try to diconnect the call, there is a bye packet
> going out bu the call is still stale and when i try calling the same
> extension again the application crashes.
>
> Please help me understand the issue and the possible solutions for
> eliminating the same.
>
> Thanks,
> Ravi
>
>   On Fri, May 6, 2011 at 9:32 PM, Joel Dodson <jdodson at acm.org> wrote:
>
>> this is really about how to recover when a call/resource goes away and
>> you don't get any notification.
>>
>> I've seen many cases where devices have RTP timeouts.  If a device is
>> expecting RTP but not seeing any for a certain amount of time, it'll
>> assume the call is gone and reclaim any resources associated with the
>> call.
>>
>> Session timers is another way to know if a resource is gone.
>>
>> I've addressed the problem from a server/proxy/gateway perspective but
>> at least the RTP timeout should still apply to the endpoint.
>>
>> Regards,
>> Joel
>>
>>
>> On Fri, May 6, 2011 at 8:28 AM, Ravi Kanth <k.ravikanthreddy at gmail.com>
>> wrote:
>> > Hi,
>> >
>> > I am facing a wierd issue here. Please help me.
>> >
>> > I have 2 sip enpoinnts developed using pjsip. let them A and B.
>> > B auto answers all the calls.
>> >
>> > Now we have a clal from  A to B, and after sometime for some reason A
>> > crashes and there is no bye message sent to B.
>> > Now there is a stale call in endpoint B. If i restart A with the same
>> > previous extension, B is not auto answering and it continously shows
>> ringing
>> > anf terminates and this call can never happpen until i restart B.
>> >
>> > Please help me understand how this can be resolved without restarting B
>> and
>> > consider the situation that B cannot be intimated about the crash of A
>> at
>> > anypoint.
>> >
>> > Regards,
>> > Ravi
>> > _______________________________________________
>> > 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
>> >
>> >
>>
>> _______________________________________________
>> 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/20110516/043181e0/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