Introduction

This document will provide instructions, technical details and guidelines for integrating an AWS VPC environment with the Telnyx network backbone.  The VXC will allow you to bypass the Internet and allow direct private access to the Telnyx telephony engine, thereby eliminating hops and reducing the risk of packet loss and jitter.  You’ll also benefit from the additional security of direct interconnection. That said, to protect against man in the middle attacks, we always recommend that you encrypt both signaling and media with TLS & Z/SRTP.

Network Implementation Overview

Follow the steps below to create a private connection between your AWS VPC and the Telnyx network.

Your checklist:

  1. Provide Telnyx with VXC Preferences
  2. Create a Virtual Private Gateway (VGW)
  3. Accept pending Direct Connect connections 
  4. Create 1 virtual interface per circuit
  5. Propagate routing to virtual private gateway

All setup is done in the AWS Direct Connect and AWS Virtual Private Cloud consoles.

Network Implementation Details

Step 1. Provide Telnyx with VXC Preferences

In the Networking section of the Mission Control Portal, click on Create a New VXC to input VXC preferences, including: 

  • the 12-digit AWS account number associated with your VPC
  • AWS region
  • Bandwidth speed
  • Network name

After receiving these preferences, Telnyx will create 1 or 2 Direct Connect connections for you to accept in your AWS console. This will take 1-3 days for Telnyx to complete.  Once you submit your preferences to Telnyx, you will not be able to change them without creating a new VXC.


Step 2 can be completed now, but
you won’t be able to move on to step 3 before Telnyx completes this initial setup.

Step 2. Create a Virtual Private Gateway (VGW)

A VGW is an intermediary between AWS Direct Connect connections and your AWS VPCs. You’ll need to create 1 VGW to complete this setup. 

To create a VGW:

  1. Open the Amazon VPC console at https://console.aws.amazon.com/vpc/.
  2. Choose Virtual Private Gateways, Create Virtual Private Gateway.
  3. Name the gateway. 
  4. Use the default ASN.
  5. Choose Create Virtual Private Gateway.

Next, associate the new VGW with your destination AWS VPC:

  1. Select the virtual private gateway that you created, and then choose Actions, Attach to VPC.
  2. Select your VPC from the list and choose Yes, Attach.

Once completed, you should see the following output:


You won’t be able to move on to step 3 before Telnyx completes the initial setup described in step 1. If there are no pending connections as described in step 3 after 1 business day, please contact network@telnyx.com.

Step 3. Accept Pending Direct Connect Connections

Now that the VGW is created, the Direct Connect connections need to be accepted.  If you requested a backup link, you’ll see 2 pending connections in this step. Otherwise, there will only be 1.

To accept Telnyx’s connections:

  1. Open the AWS Direct Connect console at https://console.aws.amazon.com/directconnect/.
  2. In the navigation pane, choose Connections.
  3. You should see 1 or 2 connections pending acceptance:

    4. Expand each connection, select I understand that Direct Connect port charges apply once I click Accept Connection, and then choose Accept Connection.

Once the connections are completed, your output should show each connection as available.

Step 4. Create One Virtual Interface Per Circuit

Virtual interfaces are where the Layer 3 addressing and BGP details will be completed.  

Some of the information required below will be provided by Telnyx via email. Those fields are indicated below. If you were able to complete step 3, but have not received this information yet, please reach out to Telnyx support. 

To create these virtual interfaces:

  1. Open the AWS Direct Connect console at https://console.aws.amazon.com/directconnect/.
  2. In the navigation pane, choose Connections, select the first newly accepted connection, and then choose Actions, Create Virtual Interface.
  3. Complete the following form:

Required Fields

  • Public or Private:  Use "Private"
  • Virtual Interface Name: Tip: use the connection ID for easy identification.
  • Your router peer IP: “Telnyx IP” -  Provided in Telnyx support email
  • Amazon router peer IP: “Customer IP” - Provided in Telnyx support email
  • BGP ASN:  Provided in Telnyx support email
  • BGP Authentication Key:  Provided in Telnyx support email


If you requested a redundant backup link and accepted 2 connections in step 3, repeat these steps for that second connection.

Step 5. Enable Route Propagation for VPC Route Tables

After the virtual interfaces have been created, BGP sessions will form with Telnyx, and routing will be in place over the connections.  The final step is to ensure route propagation is enabled for the VGW.

To enable route propagation:

  1. Open the Amazon VPC console at https://console.aws.amazon.com/vpc/.
  2. On the Route Propagation tab, choose Edit.
  3. Select the Propagate check box next to the virtual private gateway, and then choose Save.

At this point, the routing table should show Telnyx prefixes routing to the VGW.  

     4.  Navigate to the Routes tab, the output should be similar to the following:

When Telnyx routes are visible in the routing table, full integration is complete, and IP reachability can be tested.  

Did this answer your question?