Event and action using a iRule

In SIP deployments I always used an immediate timeout. That´s why I never struggeled with a problem like this.

 

This approach makes the iRule a bit more complex as you need to provide bi-directional processing for requests and responses (because the client and the gateway can send both types of messages).

 

The following events were required:

 

RULE_INIT, CLIENT_ACCEPTED, SIP_REQUEST, SIP_REQUEST_SEND, SIP_RESPONSE

 

As well it was necessary to keep additional persistence records for mapping outgoing messages to the peer.

 

The whole set of iRules is appr. 300 lines and requires some explanation (and sanitization).