F5 is upgrading its customer support chat feature on My.F5.com. Chat support will be unavailable from 6am-10am PST on 1/20/26. Refer to K000159584 for details.

Forum Discussion

LK_85527's avatar
LK_85527
Icon for Nimbostratus rankNimbostratus
May 20, 2015

Video Conference through LTM

Hi,we have BigIP-5000 ver 11.5.1 LTM box.Would like to explore the possibility of routing VC traffic through F5. VC is conducted LAN-->WAN and WAN-->Public(public).There are some 16 VC hardwares in the WAN side.Probably, a VS with pool of VCs behind the VS would be required. what should be the configuration in F5?

 

LK

 

3 Replies

  • BinaryCanary_19's avatar
    BinaryCanary_19
    Historic F5 Account

    No special configuration is required. Assuming you know enough about how the BigIP works to configure it to load-balance (or persist sessions) to your VC servers, then all you need is an appropriate virtual server with the appropriate profiles and the appropriate pool.

     

    Unless of course you have a specific concern in mind, then you should lay it out so that a more specific response can be provided.

     

    • LK_85527's avatar
      LK_85527
      Icon for Nimbostratus rankNimbostratus
      Fine I'll elaborate... The requirement is as follows... A third party from internet wants to dial branch office .The Br.Off has no Internet gateway.It’s internet g/w is HO which is in the WAN side. Now, this 3rd party should reach br.off VC (Polycom device) via HO. A VS will be created in F5 which is in HO LAN (DMZ).VS IP will be natted to a public IP thru a F/w which is again in HO. Behind the VS is a pool member (VC) of Br.Off.The idea is this 3rd party will dial the VS which in turn will send the traffic to the pool member. If the above is viable, then how to route the return traffic from Br.Off VC to the 3rd party. Any route is required in the routers of Br & HO?
    • BinaryCanary_19's avatar
      BinaryCanary_19
      Historic F5 Account
      What you describe is viable and pretty common too. You can ensure that VC traffic that originates from the F5 goes back through the F5 by applying SNAT (Automap or Snat Pool) on the F5 Virtual. Strictly speaking, this is not necessary, it is only needed if you want to avoid configuring your routing on the Servers so that they route back the relevant traffic through the F5. The F5 knows when it sends a connection (even for UDP) to the VC that the return traffic on that connection was received on a virtual, and it will intelligently route it appropriately back to the original client. This is all told, pretty easy to do, but it seems like you're new to F5. It may be a good idea to hire someone to do this for you (or get yourself trained) to avoid the headaches and frustrations.