# Connecting your network to ours

An operator hands subscriber traffic to Netavo in one of two ways: over IPSec, or through a direct interconnect between the two networks. This page sets out the choice, and what is agreed between our engineers and yours before traffic moves.

## Two ways to interconnect

| Method | How it works | Suited to |
| --- | --- | --- |
| IPSec | Encrypted tunnels between your mobile core and our breakout points, carried over the internet | Starting quickly, reaching many regions, and volumes that do not justify dedicated capacity |
| Direct on-net NNI | A network-to-network interconnect between your network and ours, with no internet in between | Higher volumes, and operators already present in the same datacentres |

## Which to choose

IPSec needs nothing but internet connectivity at each end, so it can be established to any breakout point without either party being physically present there. Most deployments begin with it.

A direct interconnect removes the internet from the path between the two networks. It suits an operator with substantial traffic in a region, or one whose own network already reaches the datacentres where ours is present. The two can be combined: direct where the volume is, IPSec elsewhere.

- **IPSec**: No physical presence needed
- **Direct NNI**: No internet between the networks
- **Together**: Direct in some regions, IPSec in others

## What we agree in the design

| Subject | What is settled |
| --- | --- |
| Regions | Where your subscribers are, and which breakout points will serve them |
| Capacity | The traffic expected at each breakout point, and how it will grow |
| Interconnection | IPSec, a direct NNI, or both, for each region |
| Addressing | Local public addressing in each country, and how subscriber addresses are translated |
| IPv6 | Whether subscribers are given native IPv6 as well as IPv4 |
| DNS | Local resolution at each breakout point |
| Resilience | How traffic is handled if a tunnel, an interconnect or a breakout point is unavailable |

## From design to live traffic

### 01 Design

Our engineers and yours agree the regions, the capacity, the interconnection and the addressing.

### 02 Build

Interconnection is established to each breakout point, by IPSec or direct NNI.

### 03 Test

Test subscribers are routed through each breakout point, and the address, DNS and performance they receive are checked.

### 04 Migrate

Live traffic is moved region by region, with the existing route kept until each is proven.

## Who is responsible for what

The operator keeps its subscribers, its tariffs and its mobile core. Netavo provides the breakout points, the secure termination of the traffic handed to them, and the operation of both. Engineering questions are dealt with between engineers.

[About our network](https://netavo.com/network)

- **Operator**: Subscribers, tariffs and mobile core
- **Netavo**: Breakout points, termination and operation
- **Support**: Direct access to the engineering team

## Discuss interconnection

Tell us how your core hands off traffic today and where your network is present. An engineer will respond with the options for connecting to ours.

[Work with us](https://netavo.com/work-with-us)

Source: https://netavo.com/sectors/mobile-operators-and-mvnos/interconnection