Flux RTP/RTCP Big-ip Edge client (AlwaysON)

Question

Hello guys,&nbsp;&nbsp;I have been deployed the Big-IP Edge client in AlwaysON mode on the computers. We use the softphone client Jabber for the phone communication.&nbsp;&nbsp;My probleme is that when an user from the VPN want to call someone else&nbsp;in the local network or in external, the communication SIP is established so the phone rinnging etc...but the client aren't&nbsp;recevie the RTP/RTCP flux.&nbsp;(preserve Source Port Strict is already Enabled on the Connectivity Network Access)&nbsp;I did an tcpdump on the F5 and I can see my RTP/RTCP flux send to the client&nbsp;Maybe this probleme is apparead after the upgrade in V15.1.3 or after the big-ip edge client released V7213.2021.527&nbsp;&nbsp;Do you know if the are some know issues about this problem ?&nbsp;&nbsp;&nbsp;How I can decrypt the traffic come from the tunnel SSL (big-ip edge client) on the client with wireshark ? I would like to see if my RTP/RTCP packet arrive correctly to my client&nbsp;Thanks you for your answers &nbsp;Regards,&nbsp;Miguel

boneyard · Answer

i can imagine this becomes complex routing wise depending on where the other clients are and if traffic from one client is allowed to another. with voip the call setup is sometimes via a central point and then the RTP traffic between the end points.&nbsp;you can just capture on the client device with wireshark what comes out of the tunnel. look for the Local Area Connection &lt;ID&gt; which has traffic going when connect and be sure to disable Promiscuous, else traffic will stop.&nbsp;&nbsp;

Forum Discussion

SSO Login Update Coming to DevCentral

Kevin - June 2026 Featured F5er

Tyler - May 2026 Featured Member

Recent Discussions

UCS file migration on differing OS versions

qkview: revealing pool members & pools

ASM attack signatures not syncing between active and standby F5

Query on source IP preservation for syslog traffic through F5 virtual server

Hardware BIG-IP appliance reach EOSS, but the software version running on it not yet?

Related Content

F5 BIG-IP Zero Trust Access

Automating Certificate Management on F5 BIG-IP

BIG-IP Geolocation Updates – Part 7

What's new in BIG-IP v21.0?

Automatic Certificate Management with ACMEv2 in F5 BIG-IP