Google VXC Setup

Architecture

We will construct the following architecture on Google Cloud.

Prerequisites

VLAN Attachment

This step is performed on Google.

Parameters:

“Partner Interconnect Connection”
“Set up unencrypted Interconnect”

“Network”: Choose the one you are connecting from
“Region”: Choose the one that there is a Telnyx PoP in proximity
“MTU”: 8896

Create a router or choose an existing one.

After creating the attachment, Google will display a pairing key — a string in the format <uuid>/<region>/<number> (e.g. 718639df-e02e-49ba-856b-0d86b17e77f4/us-central1/1). Copy this — you will need it in the next step. For redundant connections, create two VLAN attachments and collect both pairing keys.

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. Note the network_id — it is required when creating a VXC.

Procedure

Create a VXC resource

This step is performed on Telnyx. For a single connection:

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": "GCP",
    "region": "us-central1",
    "location": "Chicago IL, US",
    "speed": "50M",
    "primary_pairing_key": "<uuid>/<region>/1",
    "bgp_key_primary": "<optional-md5-auth-key>"
}

For a redundant connection:

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": "redundant",
    "csp": "GCP",
    "region": "us-central1",
    "location": "Chicago IL, US",
    "speed": "50M",
    "primary_pairing_key": "<uuid>/<region>/1",
    "secondary_pairing_key": "<uuid>/<region>/2",
    "bgp_key_primary": "<optional-md5-auth-key>",
    "bgp_key_secondary": "<optional-md5-auth-key>"
}

Key notes for GCP:

csp_account is not required for GCP (unlike AWS).
cross_connect P2P CIDRs are optional on create — GCP assigns the BGP peering IPs from the CSP side. You can supply /29 CIDRs if you want to pre-configure them; otherwise set them via PATCH after the connection is up.
primary_pairing_key and secondary_pairing_key are the VLAN attachment pairing keys obtained from Google Cloud Console.
If you supply bgp_key_primary, configure the same MD5 key on the Google Cloud Router BGP session — both peers must use the same key.

Poll GET /v2/network_agents_gateway/vxc/{vxc_id} to track provisioning status. The agent reports pending while work is in progress, then created on success or failed on error.

Activate Connection

This step is performed on Google.

“Peer ASN”: 63440 (Telnyx)

Set Cross-Connect CIDRs (if not supplied on create)

This step is performed on Telnyx. After activation, Google assigns BGP peering IP addresses to the VLAN attachment. Use these to configure the P2P /29 subnets on the VXC:

request

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

{
    "cross_connect": {
        "primary": "169.254.2.0/29",
        "secondary": "169.254.2.8/29"
    }
}

Note: GCP Dedicated Interconnect uses /29 subnets (not /30). The first usable IP in the block is assigned to the GCP router; the second to Telnyx.

Enable Routing

This step is performed on Telnyx. Enable BGP routing to bring up the session:

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
}

At this point, on Google, the “Status” will show as “Up”.

Validate Connection

This step is performed on Google.

Under VPC networks, you should see the routes advertised over the cloud router created.
You can also SSH into one of your instances in the same network and perform a traceroute.

xxx@instance-20240503-154050:~$ traceroute sip.telnyx.com
traceroute to sip.telnyx.com (192.76.120.10), 30 hops max, 60 byte packets
* * *
100.65.72.1 (100.65.72.1)  4.393 ms  4.367 ms  4.349 ms
64.16.254.51 (64.16.254.51)  114.732 ms  114.715 ms  114.698 ms
64.16.247.105 (64.16.247.105)  114.903 ms  114.877 ms  114.878 ms
192.76.120.160 (192.76.120.160)  114.843 ms  114.825 ms  114.825 ms
sip.telnyx.com (192.76.120.10)  114.857 ms  114.064 ms  114.038 ms

Private Networks

Networking API

For AI Agents

Google VXC Setup

Architecture

Prerequisites

VLAN Attachment

Telnyx Network

Procedure

Create a VXC resource

Activate Connection

Set Cross-Connect CIDRs (if not supplied on create)

Enable Routing

Validate Connection

​Architecture

​Prerequisites

​VLAN Attachment

​Telnyx Network

​Procedure

​Create a VXC resource

​Activate Connection

​Set Cross-Connect CIDRs (if not supplied on create)

​Enable Routing

​Validate Connection

Architecture

Prerequisites

VLAN Attachment

Telnyx Network

Procedure

Create a VXC resource

Activate Connection

Set Cross-Connect CIDRs (if not supplied on create)

Enable Routing

Validate Connection