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

[Daniel Pocock]

> 1. I would like the make it possible to enable/disable "disconnect 
> notification" feature on the per-call basis. Basically, the idea is that 
> the client code will pass the address that it wants rtpproxy to send the 
> disconnect notification to with the "create session" request. This would 
> allow several "disconnect-aware" clients to share one proxy.
>
>   
The socket information is now encapsulated in a struct, and each 
rtpp_session keeps a pointer to the struct.

Currently, all pointers are initialised to point to a single struct in 
the config struct, the command for controlling this on a per-call basis 
can be added later.

> The important issue here is the security - allowing rtpproxy opening 
> arbitrary local socket could be dangerous, my suggestion is that on 
> startup the proxy should be supplied with the list of allowed 
> "disconnect sockets" and only allow client requesting notification to 
> any of those.
>   
Maybe we can use my `-n' command line parameter, with a colon-separated 
list of permitted sockets?  Currently, it only accepts a single socket.  
If no socket is specified, then there will be no notifications (the old 
behaviour).

Incidently, for the purposes of using multiple products with the proxy, 
I prefer to start different instances of the proxy.  Each instance is 
bound to a specific IP address rather than 0.0.0.0.  Each B2BUA or SER 
is on the same IP as the associated RTPproxy, and all of them can use 
port 5060, even on the same machine.

Regards,

Daniel



-- 


-----------------------------------------------------------------------
Ready Technology Limited
http://www.readytechnology.co.uk
Incorporated in England and Wales, 4940731
Registered office: Devonshire House, 60 Goswell Rd, London, EC1M 7AD
-----------------------------------------------------------------------