persistence with rtsp

Ideally you would like the transport to be UDP based. The client advertises one or more ports to the server and the server selects its own port set. The RTSP control channel remains for the duration of the presentation, but the audio/video is streamed over UDP using the ports selected by the client and server. Port holes need to be opened in the BigIP for this to work. Depending on where you clients are you may encounter firewall issues with this configuration. The BigIP does not currently support this. Native support for RTSP was completed recently but has not been released yet.

 

 

The next best option is to have the audio/video sent over the RTSP control connection. This is similar to HTTP tunneling but with less overhead. The audio/video is sent in binary form, no base64 encode/decode step involved and there are no HTTP headers to deal with. You can force this in real player by selecting the TCP option (and un-selecting the other transports) in the manual RTSP settings under tools>preferences>network transport.

 

The TCP option works with a simple virtual such as the following.

 

 

virtual helix {

 

destination 10.1.30.2:rtsp

 

ip protocol tcp

 

profile fastL4

 

pool helix

 

}

 

 

Hope this helps.