[RTPproxy Users] patch - per-channel timeouts, notification on timeout

[Daniel Pocock]

> Daniel Pocock wrote:
>>
>>
>> I've been using patched version of rtpproxy with the following features:
>>
>> - the TTL is maintained for each direction independently, so if just one
>> side stops sending for max_ttl seconds, the connection can be dropped
>>
>> - whenever a connection is dropped, a notification is logged to a socket
>> (the socket is configured with the new parameter, -n )
>>
>> Does anyone have any comments on this patch and it's suitability for the
>> main rtpproxy CVS?  I'm going to post the patch and some other work on
>> this list shortly.
>
> Daniel,
>
> Both make sense to me. Please post them, but make sure they are for the
> CVS trunk before posting, though. There were many changes, particularly
> in the TTL tracking code.
>

The patches were originally developed on 0.2

I have modified them for the CVS trunk and attached a diff.

Another change that is included:  the command x or X will cause all
sessions to be dropped.  I invoke this command when my B2BUA starts, to
ensure there are no lingering sessions from a previous B2BUA that crashed.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: rtpproxy.diff
Type: text/x-diff
Size: 6215 bytes
Desc: not available
Url : http://lists.rtpproxy.org/pipermail/users/attachments/20080507/58379786/attachment.bin