Forum Discussion
Genesys sent me a very complex iRule that defined an action for all of these events you listed in your answer. I did not understand very well what they sent me. Additionally, I have made an alternate configuration in the F5 that I think it would solve the problem in our installation. Basically, we have created a different fastL4 protocol profile with "Idle timeout" parameter configured to immediate, and assign this profile to a forwarding virtual server specifically created for the traffic that flows from Genesys interface to the SBCs, and configure the SNAT in the specific option of this virtual server, without an iRule To sum up, the specific configuration we included is as follows:
Previous Forwarding Virtual Server, now without the irule
ltm virtual /Common/vsWildCardOutbound { destination /Common/0.0.0.0:0 ip-forward mask any profiles { /Common/fastL4 { } } translate-address disabled translate-port disabled vlans { /Common/internal } vlans-enabled }
Specific Forwarding Virtual server that matches SIP traffic to the SBC. Specific fast-l4 profile and SNAT configured
ltm virtual /Common/vsWildCardOutbound_SBC { destination /Common/172.20.90.48:5060 ip-forward ip-protocol udp mask 255.255.255.240 profiles { /Common/Conexion_SBC { } } snatpool /Common/snatPoolVipBi translate-address disabled translate-port disabled vlans { /Common/internal } vlans-enabled
New fastl4 profile
ltm profile fastl4 /Common/Conexion_SBC { app-service none defaults-from /Common/fastL4 idle-timeout immediate }
Can somebody come back to me, and verify that this configuration is sensible and that would not carry out any other problem to the platform?
Thanks a lot for your help