As part of our ongoing efforts to deliver reliable and high-quality voice communications, Flowroute is pleased to announce the launch of our new Points of Presence (PoPs) located in New Jersey, Virginia, Oregon, Washington, New Jersey, and Virginia. These additional PoPs have been architected to leverage on modern cloud infrastructure.
This configuration guide is designed to provide you with the necessary information for connecting to the new PoPs and accessing our inbound and outbound voice services. It focuses on the technical specifications. For Manage-related configurations, see Related Articles section below.
Flowroute currently operates two Legacy PoPs in the US - in Nevada (Primary) and California (Secondary). As part of our ongoing expansion, we are deploying additional PoPs in Oregon, Washington, New Jersey, and Virginia!
The new PoPs are deployed on popular state-of-the-art public clouds and run on infrastructure several times more powerful and resilient than Flowroute's current Production PoPs.
You can utilize any of the four mechanisms below ordered from most preferred to the least preferred, from a service resiliency point of view.
- IP Address
If your outbound gateway supports NAPTR, you can access the New PoPs using one of the following NAPTRs based on your geographical and infrastructure preferences:
Provided your outbound gateway supports NAPTR, you will be able to send traffic to your preferred PoP and fail over as geographically close as possible upon setting your preferred PoP via Manage.
Allow SIP over UDP and TCP
Make sure to whitelist all of the IP addresses associated with our PoPs to allow SIP over UDP and TCP. See Dialing via an IP Address for the list.
If your outbound gateway is capable of supporting SRV, you can access the New PoPs using one of the following based on your geographical and infrastructure preference:
|PoP||SRV (High Availability)|
|US-West-WA|| UDP: _sip._udp.us-west-wa.sip.flowroute.com
UDP and TCP Portions of SRV Records
Most PBX configurations only need the us-west-wa.sip.flowroute.com portion of the SRV record set. PBXs will typically add the _sip._udp portion automatically.
Flowroute's production SRV, sip.flowroute.com, is always included for failover as part of the SRV record set. To read an old but good tutorial on SRV and NAPTR connections, see SIP using NAPTR and SRV DNS Records.
|PoP||Primary A-Record (Potentially Lower Availability)|
If your outbound gateway is NOT capable of supporting NAPTR OR SRV OR A-records, the last resort will be to use IP addresses to access the New PoPs. In this case, you must directly use the IP address returned by your preferred A-record.
To check quickly, run the following from a command shell window. In the following request, we are using US East 1 as an example:
dig us-east-nj.sip.flowroute.com +short
For customers that use SIP registration, calls will only ever originate from PoPs that you register with. You will need to configure your gateways to register with one or more of the following to utilize the new PoPs for inbound calling:
For inbound routes with Phone Number as route type (Call Forwarding), the origination call is sent out as an outbound call back to the Public Switched Telephone Network (PSTN). Thus, there is no change in the associated Inbound Route configuration.
With the new PoPs, you can now configure your preferred inbound PoP and enable an edge strategy on a per route level for routes set to either SIP URI or Hostname. Additionally, you can configure your preferred PoP for your account which will be selected by default as your Edge set strategy with new inbound routes that you add to your account. See the following resources for the associated steps:
- Set Up Your Preferred PoP
- Edit an Inbound Route with Your Preferred PoP
- Create an Inbound Route with Your Preferred PoP
As an existing Flowroute customer, you have probably already set firewall policies. We have updated Set Firewall Policies for Flowroute’s SIP Signaling and RTP Media with the list of IP ranges that you will have to add to your whitelist. Make sure to whitelist all of them.