# SIP Trunk EIS

[Web version](https://docs.eis.it/en/voip/trunk-sip)

A SIP Trunk connects the customer's phone platform to the EIS network using the SIP protocol. It can serve a corporate power station, a SBC, a UCaaS platform or an AI voice agent.

## Types available

In Hive, during the creation of a new trunk, you can choose from these types:

[![Hive screen with six types available for a new SIP Trunk](/docs/assets/screenshots/voip/trunk-sip/01-tipologie-trunk-sip.png)](/docs/assets/screenshots/voip/trunk-sip/01-tipologie-trunk-sip.png)

Selection of the typology during the creation of a new SIP Trunk in Hive

Select the image to open it to full size.

| Type | Characteristics | When to use it |
| --- | --- | --- |
| **SIP Trunk recording** | Username and password SIP Authentication | PBX behind NAT, static public IP locations and traditional configurations |
| **SIP Trunk recording with numbering** | SIP registration with numbering association in the activation flow | Activations that require trunks and numbering in the same process |
| **SIP Trunk IP to IP** | Authorization via public IP addresses | SBC or infrastructure with static IP and direct network control |
| **SIP Trunk Webex** | Link dedicated to Webex Calling | Organizations using EIS as Cloud Connected PSTN Provider |
| **SIP Trunk Elastic FQN** | Route to a public host name | Cloud and elastic services that publish endpoints through DNS |
| **Microsoft Teams** | Connection dedicated to the Microsoft platform | Organizations that integrate EIS telephony with Microsoft Teams |

### Registration

The device sends SIP requests `REGISTER` Using the credentials shown in Hive. It is the easiest mode when the PBX is behind NAT. For this mode you can configure an external backup number: if the trunk is not registered, the incoming calls are automatically diverted.

### IP to IP

EIS authorizes public IP addresses declared for the trunk. Periodic registration with username and password is not required; however, the remote system must use stable addresses and allow SIP signaling and RTP flows correctly.

### Elastic FQDN

Traffic is routed to a full domain name, useful when the remote service manages availability and address changes through DNS. FQDN must publicly resolve and represent a client-controlled SIP endpoint.

### Webex and Microsoft Teams

The dedicated types simplify the connection with the chosen platform. [Webex Calling](/en/voip/webex-calling) and [Microsoft Teams Direct Routing](/en/voip/microsoft-teams); parameters, availability and activation mode depend on the service purchased.

## Configuration in Hive

### Create the trunk

Select customer, type of trunk and number of contemporary calls required.

### Set up the endpoint

Enter the credentials, authorized IPs, FQDN or platform data according to the type of choice.

### Adds numbering

Connect to the trunk the active numbers that must receive or present traffic.

### Set security and continuity

Configure countries enabled, premium numbering, anti-fraud threshold and, if available, backup number.

### Run the tests

Check input, output, bidirectional audio, CLI and error management.

> Do not publish SIP credentials and do not authorize broader networks than necessary. An incorrect configuration can expose the fraudulent traffic trunk.

Before testing check ports, networks, NATs, codecs and bandwidth on the page [Technical requirements](/en/voip/requisiti-tecnici).

Updated content from the guide [EIS TrunkSIP on EIS Wiki](https://wiki.eis.it/it/VoIP/Eis-Trunksip).
