For more information regarding the security incident at F5, the actions we are taking to address it, and our ongoing efforts to protect our customers, click here.

Forum Discussion

liang_14081's avatar
liang_14081
Icon for Nimbostratus rankNimbostratus
Mar 05, 2009

RTSP Load Balancing with RTP&RTCP Persistency

I have a video server load balancing case in our Carrier, and the application protocol is RTSP, the detailed scenario as below:   Most clients are behind proxy servers, when the client initiat...
application delivery
dev
devops
iRules
Nat_Thirasuttakorn's avatar
Nat_Thirasuttakorn
Icon for Employee rankEmployee
Mar 08, 2009
BIG-IP checks transport header. let say it is like this

 

Transport: RTP/AVP;unicast;client_port=6970-6971;server_port=6972-6973;ssrc=000017F8;source=172.16.59.31

 

then BIG-IP will create entries for communication between client and server in connection table as a combination of

 

client_port=6970-6971;

 

and

 

server_port=6972-6973

 

if you run command 'bigpipe conn', you should be able to see them listed.

 

v9 does not honor the source attribute which indicate server address(in this example: source=172.16.59.31) but it is normally same as RTSP anyway.

 

v10 honor "source" attribute, it also creates entries in connection table but between client and address specified by source attribute (if source attribute does not exist, it will do the same as v9)