Azure VXC Setup

Architecture

We will construct the following architecture.

Prerequisites

Create ExpressRoute Circuit

This step is performed on Azure.

Parameter	Value
Region	Choose the matching available region from the VXC coverage API
Port Type	Provider
Provider	Equinix
Peering location	matching available region from the VXC coverage API
Bandwidth	Choose the available bandwidth from the VXC coverage API
SKU	Standard

Choose the rest of the parameters at your own discretion.

At the end of this step, the “Provider status” should say “Not provisioned”.

Telnyx Network

This step is performed on Telnyx. If you don’t have a network created already, you may follow this guide to create one.

Procedure

Create a VXC resource

This step is performed on Telnyx.

request

POST /v2/network_agents_gateway/vxc HTTP/1.1
Host: api.telnyx.com
Content-Type: application/json
Authorization: Bearer ***

{
    "customer_name": "my-company",
    "network_id": "<your-telnyx-network-id>",
    "type": "single",
    "csp": "AZU",
    "primary_service_key": "<your-expressroute-service-key>",
    "region": "germanywestcentral",
    "location": "Frankfurt, DE",
    "speed": "50M",
    "bgp_asn": 12076,
    "bgp_key_primary": "<optional-md5-auth-key>"
}

Parameter	Value
`csp`	`AZU`
`primary_service_key`	Service key from the ExpressRoute circuit created previously
`secondary_service_key`	Secondary service key, redundant connections only
`region`	Choose the matching Azure region from the VXC coverage API
`location`	Telnyx PoP name from the coverage API, e.g. `Frankfurt, DE`
`speed`	Chosen from available bandwidth in the VXC coverage API response
`bgp_asn`	Your BGP ASN (0–65535). Azure’s default is 12076.
`bgp_key_primary`	Optional MD5 BGP authentication key. Omit for no authentication.
`bgp_key_secondary`	Optional, redundant connections only.

BGP auth key: If you supply bgp_key_primary, configure the same MD5 key on the Azure ExpressRoute private peering — both peers must use the same key.

Take note of the following info in the response; you will need it later.

id
primary_cloud_ip
primary_bgp_key

Enable Routing

This step is performed on Telnyx. Enable BGP routing to bring up the session and start advertising routes. You must make sure routing is enabled before proceeding to the Azure Private Peering step.

request

PATCH /v2/network_agents_gateway/vxc/{vxc_id} HTTP/1.1
Host: api.telnyx.com
Content-Type: application/json
Authorization: Bearer ***

{
    "bgp_enabled": true
}

Poll GET /v2/network_agents_gateway/vxc/{vxc_id} until bgp_enabled is true before proceeding to the next step.

Azure Private Peering

This step is performed on Azure. “Provider status” must show “Provisioned” before performing this step.

Parameter	Value
Peer ASN	Telnyx’s BGP ASN which is 63440
Subnets	IPv4
IPv4 Primary subnet	Choose the /30 block that includes `primary_cloud_ip`
IPv4 Secondary subnet	Choose the next /30 block
VLAN ID	Choose any number from a valid VLAN range
Shared key	primary bgp key
Public IP address	Create new
Public IP address SKU	Standard

After saving, you may need to wait for some time before performing the next step.

At this point, you should see Telnyx IPs advertised in the result after you click into “View route table.”

At this point, you are all set. Perform the following steps only if you are trying to test things out before putting it into your own production environment.

Virtual Network

Parameters	Value
Region	Match that of the virtual network created from the previous step

Next, add a Gateway subnet. Keep all parameters as default.

Virtual Network Gateways

Parameters	Value
Name	Something meaningful to you
Region	Match that of the virtual network created from the previous step
Gateway type	Express Route
SKU	Standard
Virtual network	Choose the one created from the previous step
Public IP address	Create new
Public IP address SKU	Standard

The gateway creation will take a while; upward of 20 minutes. In the meantime, you can proceed to the following step.

Virtual Machines

Parameters	Value
Region	Match that of the virtual network created from the previous step

Parameters	Value
Virtual network	Choose the one created from the previous step

You can keep the rest default or choose at your discretion.

Add Gateway Connection

This step is performed on Azure. The Virtual Gateway you created must be successfully deployed before this step is performed.

Parameters	Value
Connection type	Express Route

Parameters	Value
Virtual network gateway	Choose the one created from the previous step
ExpressRoute circuit	Choose the one created from the previous step
Routing weight	0

Validate Connection

This step is performed on Azure. Ensure all of the following are successfully deployed:

ExpressRoute
Virtual network
Virtual network gateway & connection
Virtual machine

SSH into the VM and perform a traceroute to sip.telnyx.com and sip.telnyx.eu. You can see the next hop is the next hop indicated on the Azure Private Peering under the express route.

Private Networks

Networking API

For AI Agents

Azure VXC Setup

Architecture

Prerequisites

Create ExpressRoute Circuit

Telnyx Network

Procedure

Create a VXC resource

Enable Routing

Azure Private Peering

Virtual Network

Virtual Network Gateways

Virtual Machines

Add Gateway Connection

Validate Connection

​Architecture

​Prerequisites

​Create ExpressRoute Circuit

​Telnyx Network

​Procedure

​Create a VXC resource

​Enable Routing

​Azure Private Peering

​Virtual Network

​Virtual Network Gateways

​Virtual Machines

​Add Gateway Connection

​Validate Connection

Architecture

Prerequisites

Create ExpressRoute Circuit

Telnyx Network

Procedure

Create a VXC resource

Enable Routing

Azure Private Peering

Virtual Network

Virtual Network Gateways

Virtual Machines

Add Gateway Connection

Validate Connection