Prerequisites – Network Configuration & MBG WAN Mode

Before configuring any SIP trunk on the MiVoice Border Gateway (MBG), it is essential that the MBG is correctly deployed as a true border device with both LAN and WAN interfaces configured, running in gateway mode. This is a fundamental networking requirement and is not specific to Talkative — it applies to any external SIP trunk requiring connectivity across a network boundary.

The MBG must have a WAN interface configured with a publicly routable IP address. Without this, the MBG has no basis on which to rewrite SIP Contact headers for outbound traffic, meaning internal RFC 1918 private IP addresses will be presented to external parties such as Twilio. These addresses are unreachable from the public internet, which will cause SIP signalling to fail — including ACKs, in-dialog requests such as REFER, and media streams.

LAN mode and custom mode without a configured WAN interface are not supported configurations for external SIP trunking. If the MBG status page does not show a populated WAN interface with a public IP address, do not proceed with SIP trunk configuration until this is resolved.

To validate the MBG is correctly configured, navigate to the MBG status page and confirm the network profile shows gateway mode with both LAN and WAN interfaces populated before proceeding.

Trunk Setup

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)

RTP Security Configuration

RTP security configuration configures how the MBG will handle media streams between the various legs of the call - it describes what connections it will accept, negotiate and if it can upgrade or downgrade them.

⚠️

The PBX administrator should map out the expected media flow for each call scenario, identifying which trunks operate as SRTP and which as RTP. Each trunk's security settings should then be configured to give the MBG the flexibility to perform the necessary protocol conversion — for instance, using SRTP or RTP rather than a strict single-protocol setting where conversion may be required.

If your environment has multiple trunks with differing security requirements — for example, a carrier trunk configured as SRTP-only, and the Talkative Voice AI trunk configured as RTP-only — the MBG must be able to upgrade or downgrade the media protocol as calls traverse it. Setting all trunks to a single rigid protocol when the actual traffic mix is more varied will result in audio issues or failed calls.

Trunk-side RTP Security

The trunk-side RTP security controls the protocols used for traffic between the MBG and the Talkative/Twilio trunk. These settings must be considered in the context of your full media path — not in isolation.

If you wish to have a fully encrypted connection end-to-end and all trunks in the path support SRTP, these may be set to SRTP only. Otherwise, the default values below are a safe starting point — review them against your specific environment.

⚠️

Important — consider your entire trunk configuration before setting these values.

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 RTP security controls the protocols used between the MBG and the inner PBX (MiVB, MX-One, MV5000 etc). As with the trunk-side settings above, these must be configured with the full call flow in mind.

If a call arrives from a carrier trunk as SRTP and needs to be passed to an internal extension or onward to the Voice AI trunk as RTP (or vice versa), the MBG handles that conversion — but only if the ICP-side settings permit it. Restricting this interface to a single protocol when the internal PBX or other connected trunks use a different one will break audio. In testing, RTP Only or AVP+crypto works correctly for insecure trunks originating calls externally, but the administrator should confirm this matches the security posture of the internal PBX.

⚠️