Event and action using a iRule

The deployment I´m referring to was done with another vendors SGC and it really took us a couple of days to get everything done and tested. And in this case I was already using a tested set of iRules.

 

With SIP you will very likely need to touch a couple of SIP headers to rewrite IP addresses bi-directional and in some cases the SIP URI needs to be modified. Some heades will show up multiple times in the same message and each of it has to be rewritten.

 

In all cases we used the SIP profile with our virtual servers allowing us to access the header and URI information.

 

Perhaps your SIP environment is robust enough and can deal with the address translation by the load balancer, but especially for outgoing messages it will be required to use specific persistency to map responses to a client if an immediate timeout was applied.

 

I would recommend to work closely with an experienced F5 systems engineer.

 

Trying to use DevCentral to get it done will make this one a very long thread, imho.