RTSP Proxy

You probably want to use the super-secret relate_server command. This will create a new session that is "related" to the control session and will then be cleaned up when the control connection goes away. The syntax would be something like this:

 

when SERVER_CONNECTED {
   relate_server {
      proto 17
      clientflow 4092 $snat_addr $snat_port $server_addr $server_port 
      serverflow 4093 $vip_addr $vip_port $client_addr $client_port
   }
}

 

This code assumes your external vlan is 4092, your internal vlan is 4093. It also assumes you have set the variables at some previous time or event. snat_addr/snat_port are the address and port the server is attempting to connect to and server_addr/server_port are the server's address and port that the connection is coming from. Vip_addr/vip_port are the address/port used going out to the client and client_addr/client_port are the destination client.

 

Hope this helps. As I've said before, the next release includes complete support for RTSP.