logo
logo
Sign in

Cloud Managed SD-WAN Services - Uplevel Systems (Tigard, Oregon, USA)

avatar
uplevelsystems
Cloud Managed SD-WAN Services - Uplevel Systems (Tigard, Oregon, USA)

Uplevel Systems is a leading cloud management SD-WAN provider with a passion to help our customers build a more efficient, performant and secure enterprise network. Uplevel Systems provides expertly managed, cloud-based SD-WAN services with both hybrid and cloud options.


The need for the fixed IP is driven by fact that some VoIP providers use the source public IP and port of the voice RTP streams that originate from the customer site to associate the RTP streams with specific calls. This is fine when there is only a single WAN connection to the customer site, with a static IP assigned by the ISP. In that case, the source public IP will never change, and the VoIP provider can use it as part of call connection tracking.


However, what happens when there are two ISP links to the customer site, with failover from the primary link to the secondary link? When failover occurs, the source public IP of the RTP streams will change. (Obviously you can’t have outbound packets maintain their source IP address if you’ve just switched over from one ISP link to another!) If the VoIP provideris tracking connection state using the source public IP, then this looks like the connection was interrupted; there are no more packets from the old – failed – ISP public IP, and there are all these unknown packets arriving from the new – secondary – ISP public IP. This will cause the voice call to drop.


The traditional solution by an SD-WAN vendor involves backhauling (i.e., tunneling) all the traffic from the customer site to a dedicated Point of Presence (PoP) somewhere, preferably very close to the customer. At the PoP, the traffic is removed from the tunnel and allowed to exit to the Internet through a router with a fixed public IP on its peer interface.


NAT is used to make the VoIP traffic look like it is originating from this public IP, rather than from the customer’s actual ISP-assigned IP address. Now, when the primary link fails to the secondary link, the VoIP provider doesn’t see anything changing; this is all hidden by the managed SD-WAN vendor between the customer site and their router. Of course, this gets rather expensive quite fast – VoIP QoS is heavily dependent on loss and delay, and to minimize the delay you need a PoP as close to the customer’s physical site as possible.

collect
0
avatar
uplevelsystems
guide
Zupyak is the world’s largest content marketing community, with over 400 000 members and 3 million articles. Explore and get your content discovered.
Read more