Skip to Content
EIS
VoIP Services

SIP Trunk EIS

Solutions for PBX, SBC, Cloud, Webex, Microsoft Teams and AI Voice Agents

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
Selection of the typology during the creation of a new SIP Trunk in Hive

Select the image to open it to full size.

TypeCharacteristicsWhen to use it
SIP Trunk recordingUsername and password SIP AuthenticationPBX behind NAT, static public IP locations and traditional configurations
SIP Trunk recording with numberingSIP registration with numbering association in the activation flowActivations that require trunks and numbering in the same process
SIP Trunk IP to IPAuthorization via public IP addressesSBC or infrastructure with static IP and direct network control
SIP Trunk WebexLink dedicated to Webex CallingOrganizations using EIS as Cloud Connected PSTN Provider
SIP Trunk Elastic FQNRoute to a public host nameCloud and elastic services that publish endpoints through DNS
Microsoft TeamsConnection dedicated to the Microsoft platformOrganizations 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 and Microsoft Teams Direct Routing; 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.

Updated content from the guide EIS TrunkSIP on EIS Wiki.