Hi, Regarding media transport recv() error messages because of sudden remote termination, it has been discussed here http://lists.pjsip.org/pipermail/pjsip_lists.pjsip.org/2008-August/004345.html Regards, nanang On Fri, Sep 5, 2008 at 8:44 AM, Mark Webster <mark.webster+pjsip at gmail.com<mark.webster%2Bpjsip at gmail.com> > wrote: > Hi PJSIP team > > Firstly, you guys are heroes for putting so much time into this. Many > thanks for your efforts :) > > I have a related query, also regarding the disappearance of the remote > party (for example, in the event of network failure or the sudden > termination of the client). > > I'm currently compiling for win32, and I'm using media streams directly > (ie, not media sessions). Killing the remote client results in a > never-ending stream of "RTP recv() error" messages. Is there a clever way to > detect when this is ocurring? > > Currently I am aware of 2 ways of doing this. > > 1) Install my own (very thin) wrapper around on_rx_rtp to detect > bytes_read<0 and use that as my callback, > > 2) Modify on_rx_rtp and struct pjmedia_stream to keep a count of > consecutive bad socket reads and add an accessor for this new field. > > Any thoughts? > > > On Wed, Sep 3, 2008 at 11:45 AM, Gang Liu <gangban.lau at gmail.com> wrote: > >> Hi, benny >> >> any updates? >> >> regards, >> Gang >> > > > _______________________________________________ > 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/20080905/5e3b9cc1/attachment.html
