Navigate to the MBG server manager. In the left-hand menu, click MiVoice Border Gateway under the applications header.
Select SIP trunking to open the dropdown menu and then select SIP trunks - this will open the SIP trucks page. Click the + icon to begin adding a new SIP trunk.
This will open a manage SIP trunk page where you can configure your SIP trunk.

Profile
In the profile you should set the trunk to be enabled and add a name to identify the trunk, for example “TalkativeVAI” is a common name used.
Option | Value |
Enabled | Checked |
Name | TalkativeVAI |
Connection
Set the connection details, you will have been provided these by your Talkative account manager or obtained from within the Engage platform.
Option | Value |
Transport protocol | UDP - TLS if using encryption |
Remote trunk endpoint address | {uuid}.sip.twilio.com (this may be regionalised) |
Remote trunk endpoint port | 5060 (5061 if using enryption) |
The remote trunk endpoint by default will use the Twilio US1 region for signalling. If you want to choose a different default region, you may change the format to be {uuid}.sip.{region}.twilio.com - a list of the signalling IPs can be found here: https://www.twilio.com/docs/sip-trunking/ip-addresses - there are 4 per region and should all be added to the whitelist to allow for resiliency should any region be unavailable.
The default connection will be UDP - if you require encryption, please ask Twilio support to enable this on your account.
Authentication
This trunk does not require authentication here. The connection will be between the MBG and the Talkative VAI server.
Option | Value |
Authentication username | Leave blank |
Authentication password | Leave blank |
Confirm authentication password | Leave blank |
Require mediasec | Leave unchecked |
SIP Adaptation
There are no sip adaptations needed for this Trunk
Option | Value |
Receive pipeline | Leave unselected |
Send pipeline | Leave unselected |
Protocol
Options keepalives can be enabled, however we have observed inconsistent behaviour and failures associated with them, so opt to keep them disabled.
Option | Value |
PRACK support | Use master setting (default) |
Options keepalives | Never |
Options interval | 60 (default) |
Rewrite host in PAI | Leave checked (default) |
Idle timeout (s) | 3000 (default) |
Use source port in contact header | Leave unchecked (default) |
Media
The settings in this section remain unchanged from default.
Option | Value |
Local streaming between trunk calls | Leave unchecked (default) |
RTP address override | Leave unselected (default) |
Trunk-side RTP Security
The trunk side RTP security controls the protocols used for traffic between the MBG and our Twilio Trunk. If you with to have a secure connection these should be set to SRTP only, otherwise the default values are permissible.
Option | Value |
Inbound | SRTP or RTP (default) |
Outbound | RTP only (default) (SRTP only if secure) |
Preferred cipher | Default value |
Icp-side RTP Security
The ICP-side RDP security controls the protocols used between your MBG and the inner PBX (MiVB, MX-One, MV5000 etc) if you with to use a secure connection, these should be set to SRPT, otherwise the default values are permissible
Option | Value |
Inbound | RTP Only (default) |
Outbound | RTP Only (default) |
Preferred cipher | Default value |
Trunk Rules
You must add a SIP trunk rule to match incoming traffic directed to this SIP Trunk. To do this, save the Trunk configuration and click the “Quick add rule” button.
Option | Value |
Header match | Request URI |
Rule | * (match all) |
Primary ICP | Your configured ICP |
Secondary ICP | Leave blank unless required |
Description | Optionally add a description |
