pjsip_transport_destroy return E_BUSY

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

 



On Fri, Sep 12, 2008 at 7:40 PM, yeffri z <yeffri at gmail.com> wrote:

> Dear Sir,
>
> When I call pjsip_transport_destroy() the function return busy as if
> there's still reference for this transport.
> Should I wait and call this function again?


No, definitely not.


> Or Is there function to
> really force the transport to destroy
>
>
No. You should just call transport_shutdown() (or something like that) and
let the transport be destroyed by the stack when it's safe to do so. I think
this has been discussed a while back on this list.

 -benny



>
> Warm Regards
>
> Yeffri
>
> _______________________________________________
> 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/20080915/c023f0b1/attachment-0001.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