RTPProxy version / package

[Jerome Martin]

> > I doubt port starvation is the cause, rtpproxy gives a '0' port number
> > even with only 50 sessions, and the default port range is more like
> > 10/15k available ports (and I don't have any other apps using up my UDP
> > ports on that server). Thanks for trying anyway :-)
> >   
> In another doc, it is suggested that a PC can only handle 2,000 
> concurrent RTP streams - so 15,000 ports should be plenty.

Right.

> 
> There was another bug patched which related to use of file descriptors.  
> stdin, stdout and stderr were being closed when rtpproxy started, and so 
> FD 0, 1 and 2 would then be re-used by the OS.  The end result was that, 
> in some situations, some warnings/errors printed with fprintf(stderr, 
> ...) would end up on the socket used by the application.

Any idea when this got patched, so I could check it out in the sources I
use ?