Data Center & Cloud Infrastructure VMUG Community

Expand all | Collapse all

Anyone using VMC for hosting VoIP workloads?

  • 1.  Anyone using VMC for hosting VoIP workloads?

    Posted 01-30-2020 09:17 PM
    I have a customer that wants to use VMC to host their VM's. Several of their VM's handle some type of VoIP workload traffic. The VoIP VM's are public facing VM's without a NAT, currently on vCD w/NSX-V (not sure which exact version). I'm not a VoiP expert by any means but from my understanding, NAT'ing doesn't pass VoIP or SIP type traffic. In VMC/NSX-T, a public IP is required to be routed through the CGW using NAT. My question is if anyone is using VMC for VoIP traffic, how are they handling the NAT configuration?

    ------------------------------
    Edwin Arcilla
    VMware Solutions Architect
    Rackspace
    San Diego CA
    ------------------------------


  • 2.  RE: Anyone using VMC for hosting VoIP workloads?

    Posted 01-31-2020 12:20 PM
    Edwin,

    That's probably not the whole picture - a public IP is not required to be routed through the CGW, the CGW is where you land a tunneled interface from your premises. Internal addresses will flow through the tunnel, which means that the VoIP traffic in question shouldn't need to NAT, as long as it knows how to get to VMC on AWS.

    Are you landing the CGW on a NSX-V ESG, or on their perimeter device?
    If so, is the NSX-V ESG configured to use a route-based VPN or policy based?
    Is the NSX-V ESG advertising the VMC networks to the greater network?

    Another side note - you may want to run jitter/latency testing before putting a VoIP workload on AWS - if the customer is not well placed for that, they may want to consider a public VIF direct connect to ensure that it doesn't fall out of tolerance.

    ------------------------------
    Nicholas Schmidt
    Engineer
    AK
    ------------------------------



  • 3.  RE: Anyone using VMC for hosting VoIP workloads?

    Posted 02-03-2020 12:10 PM
    Ah - so you're trying to migrate the public-facing service -> VMC.

    For the most part, the "no-NAT" rule with SIP isn't really true, and if it's on a public IP, odds are they may be NATing it already.

    Here's a guide on how - https://cloud.vmware.com/community/2019/07/24/vmware-cloud-aws-internet-access-design-deep-dive/

    This uses AWS EIP - which is NAT, but not NAT overload, which is usually what breaks telephony services - no privacy, but easy access.

    Another option would be to create a public segment and use it internally, but that would introduce a dependency on the CGW tunnel for all sites - which depending on scale, may be problematic.

    Perhaps we're asking the wrong question here as well - what telephony platform are they using? Most SIP-based platforms handle NAT just fine, but require application-specific tweaks.

    ------------------------------
    Nicholas Schmidt
    Engineer
    AK
    ------------------------------