Menace Voice Managed SIP

What you get, and what you bring#

When managed provisioning is available and completes successfully, your organization receives a telephony configuration named Menace Voice Cloudonix SIP. It provides a SIP domain connected to the Menace Voice pipeline without requiring your own Cloudonix account. Check that this configuration exists and its setup checklist is complete before relying on managed SIP.

What it does not include is phone service. Menace Voice does not sell or resell phone numbers, and no calls flow until you connect a carrier:

If you would rather bring your own Cloudonix account instead of using the provisioned domain, follow Cloudonix Integration and add a separate configuration. Self-hosted deployments can also connect their own Asterisk via Asterisk ARI.

Prerequisites#

• A SIP trunk from a carrier (or a PBX such as Asterisk or FreeSWITCH) that can accept calls from a fixed IP address and send calls to a hostname
• At least one phone number (DID) on that trunk
• Permission to change the trunk's IP allowlist and routing on the carrier side

Step 1: Read your SIP endpoints from Menace Voice#

1. Go to Telephony configurations and open Menace Voice Cloudonix SIP
2. Expand SIP connectivity
3. Choose the region closest to your carrier — Global, India, or UAE. Every value on the panel is region-specific, so set this first
4. Note the two values you will need on the carrier side:
   • Inbound hostname and ports — where your carrier sends calls to Menace Voice
   • Outbound origin IP address — the address Menace Voice's calls arrive from

Step 2: Point your carrier at Menace Voice (inbound)#

On your carrier or PBX, route your DIDs to the inbound hostname and port shown in SIP connectivity. UDP and TCP share one port; TLS uses a separate one.

This is the direction that makes your agent answer calls.

Step 3: Create the outbound trunk (outbound)#

Menace Voice needs to know where to send calls when your agent dials out.

1. On your carrier, allow the origin IP address from Step 1 to send SIP traffic to your trunk. Calls from Menace Voice are unauthenticated and identified by source IP, so this step is required
2. Back in Menace Voice, under Outbound trunks, choose Add trunk and fill in:
   • Name — any name you choose. Letters, digits and hyphens only
   • SIP domain — the hostname of your carrier or PBX, for example sip.example.com. Menace Voice puts this in both the SIP To header and the Request-URI
   • Region — the edge Menace Voice dials your carrier from. The dialog shows the origin IP that region uses, which is the one to allowlist above
3. Leave Enabled on and choose Save trunk

You can add more than one trunk — a second carrier, or a failover. Each keeps its own region, and each lists the numbers that dial out over it.

Step 4: Add your phone numbers#

Cloudonix requires a caller ID on every outbound call and rejects the call without one, so this step is required even if you only care about inbound.

1. Choose Add number on the trunk whose carrier gave you the number — the trunk is then filled in for you. (Add phone number further down works too; there you pick the Outbound trunk yourself, or leave it unset for a number that belongs to no trunk.)
2. Enter a number your carrier delivers to you, in E.164 format — +, country code, then the number, with no spaces or dashes, for example +14155550123
3. Mark the number you want outbound calls to present as the default caller ID

Add every DID you intend to use. A number your carrier does not own will be rejected by the carrier even though Menace Voice accepts it — which is why the trunk assignment matters as soon as you have more than one carrier. With a single trunk, Menace Voice uses it for every number and the field can be left alone.

Step 5: Route inbound calls to an agent#

Only needed if you want to receive calls.

1. In the Phone numbers section, edit the number that should be answered
2. Set its Inbound workflow to the agent that should pick up
3. Save

Menace Voice pushes the inbound webhook URL to the Voice Application on the provisioned domain automatically. You still need the DID bound to that application — see Step 2 of the Cloudonix inbound setup.

Step 6: Place a test call#

1. Open an agent, and make sure it is saved with no validation errors
2. Choose Phone Call
3. Select Menace Voice Cloudonix SIP, pick your caller ID, enter a destination number, and start the call

Troubleshooting#