RTSP Proxy

I have been wrestling with a couple of approaches to the RTSP proxy problem. Basically, I have client requests arriving at a virtual server on the external VLAN (192.168.3.50) and I'm trying to load balance a couple of 3GPP streaming servers (10.1.1.11, 10.1.1.21) on an internal VLAN.

 

 

I've seen a number of posts promising "full RTSP support" in future releases, but I'm not sure how far that ever got or what was meant by "full". As in the previous post, I need to provide a means for outbound UDP traffic to reach the client,as well as inbound UDP traffic (RTCP reports) to reach the appropriate server. I did some things with global arrays that successfully mapped the incoming RTCP reports to the correct streaming server for the session, but things started looking pretty kludgy.

 

 

I'm just starting to investigate the relate_server command and would like to know if it might provide a correct (supported) solution. (It was referred to as "ultra-secret" in one post.) In my current implementation, I'm collecting the payload, then in the SERVER_DATA event, based on the current "state" I'm in(DESCRIBE/SETUP/etc.), I update the SDP response to the DESCRIBE (update o= with the VS address) or extract the client_port and server_port attributes from the response to the SETUP request(Transport header) . I'm still getting my head around the relate_server command, so I guess I'm looking for a vote of confidence that this is the right approach. Should I follow that path, or has something "newer and wonderfuller" come along?

 

 

Thanks,

 

Mark