SIP Trunk Setup for Voyced – Cisco IP PBX (CUCM & CME)

Connect your Cisco telephone system to Voyced to make and receive calls using your business telephone number.

This guide covers two Cisco platforms:

• Cisco Unified Communications Manager (CUCM), using a compatible Cisco voice gateway or Cisco Unified Border Element (CUBE).

• Cisco Unified Communications Manager Express (CME), using a Cisco IOS or IOS XE voice router.

The configuration differs between these systems. Follow the instructions for your platform.

What You'll Need

Before starting, make sure you have:

• Administrator access to your Cisco telephone system.

• At least one working telephone extension.

• An active Voyced telephone number.

• Your Voyced SIP username and Service Password.

• A working internet connection.

• A Cisco voice gateway or CUBE capable of the required SIP registration, if you use CUCM.

• The required Cisco voice features and licences for your installation.

Voyced SIP details

Replace the example credentials with your own Voyced details.

You can find your DID under Cloud PBX / IP Centrex > Phone Lines in your Voyced Hosted IPPBX. Select the wrench icon beside your number.

Your Service Password is available under My Profile > Settings.

The Service Password is different from your Voyced website login password.

Requirements Before You Begin

1. Identify your Cisco system

Cisco offers several telephone platforms.

This guide covers the first three.

2. Understand SIP registration

Voyced's standard SIP connection uses an account username and Service Password.

The connected system must be able to authenticate and register that account.

Cisco CUCM supports SIP trunks, but a normal CUCM SIP trunk does not register with a provider in the same way as a SIP telephone.

For the standard Voyced registration-based connection, use a compatible Cisco gateway or CUBE between CUCM and Voyced.

The call path is:

Cisco IP Phones → CUCM → Cisco Gateway/CUBE → Voyced

For Cisco CME, a supported IOS voice router can handle SIP registration directly.

3. Check your network

Make sure:

1. Your provider-facing Cisco device can resolve sip.voyced.eu.

2. The device can communicate with Voyced using UDP port 5060.

3. Your firewall permits the SIP and RTP traffic required by your system.

4. Your Cisco gateway uses the correct public address and network settings.

5. Your internal extensions can make calls within the Cisco telephone system.

The RTP port range depends on your Cisco gateway and its configuration.

Use the actual range configured on your device.

4. Check the required Cisco features

For CUCM:

• Confirm an appropriate Cisco gateway or CUBE is available.

• Check that the gateway supports SIP registration to an external provider.

• Confirm CUCM can communicate with the gateway.

For CME:

• Check that your router supports the SIP user-agent commands.

• Confirm the required VoIP features are enabled.

• Check the existing extension and dial-peer configuration.

Cisco IOS commands and available features vary by router model and software release.

SIP Trunk Setup

Part A: Cisco Unified Communications Manager (CUCM)

These instructions cover the CUCM side of the connection.

The Cisco gateway or CUBE must separately be configured to register with Voyced using the credentials supplied for your account.

Step 1: Create a SIP trunk security profile

1. Log in to Cisco Unified CM Administration.

2. Open System > Security > SIP Trunk Security Profile.

On some releases, the menu is under:

System > Security Profile > SIP Trunk Security Profile

3. Click Add New.

Configure:

Use the SIP listening port configured for the CUCM-facing side of your Cisco gateway.

Click Save.

CUCM does not need your Voyced Service Password in this security profile.

The provider authentication belongs on the gateway that registers with Voyced.

Step 2: Add the SIP trunk

1. Open Device > Trunk.

2. Click Add New.

3. Select SIP Trunk as the trunk type.

4. Select None (Default) as the service type.

5. Click Next.

Enter:

Use the device pool appropriate to your Cisco network.

Step 3: Configure the trunk destination

Under SIP Information, enter:

The Destination Address here is your Cisco gateway, not sip.voyced.eu.

The gateway handles the connection to Voyced.

Click Save.

Apply the configuration to the trunk when prompted.

Step 4: Configure the Cisco gateway

The Cisco gateway or CUBE provides the connection between CUCM and Voyced.

On its provider-facing side, configure:

The gateway must be configured for registration-based service, not merely a static destination pointing to Voyced.

Its configuration must also route:

• Outgoing CUCM calls to Voyced.

• Incoming Voyced calls to CUCM.

• The correct called number and Caller ID on each call.

On supported Cisco IOS XE versions, CUBE offers SIP registration settings through voice-class tenants. Other gateway versions use SIP user-agent configuration.

Use the method supported by your gateway and its installed software.

Step 5: Create an outbound route pattern

In CUCM:

1. Open Call Routing > Route/Hunt > Route Pattern.

2. Click Add New.

For an organisation using 9 as the outside-line access digit, configure:

This example allows users to dial 9 before an international number.

The PreDot setting removes the initial 9 but preserves the international 00.

For example:

Make sure any called-party transformation settings on your route groups or route lists also preserve the required number format.

If your existing CUCM dial plan does not use an outside-line prefix, create a suitable route pattern that sends numbers beginning with 00 unchanged.

Add separate national and local routes where required.

Keep your existing emergency call routing appropriately configured.

Step 6: Configure incoming call routing

Incoming calls arrive through the Cisco gateway and the CUCM SIP trunk.

To route the calls:

1. Confirm the gateway passes the called DID to CUCM.

2. Check that CUCM recognises the incoming number.

3. Use the existing directory numbers, translation patterns or other suitable call routing rules to direct the call to its destination.

For example:

The number received from the Cisco gateway must match the destination or translation pattern used by CUCM.

If incoming calls do not reach the correct destination, check the called number in the incoming SIP message before changing your route patterns.

Part B: Cisco Unified Communications Manager Express (CME)

CME runs on supported Cisco IOS voice routers.

The following example uses Cisco IOS SIP user-agent and dial-peer configuration.

The exact commands available depend on your router and IOS or IOS XE release.

Step 1: Access the Cisco router

Connect to the Cisco router using SSH or your normal management method.

Enter privileged EXEC mode:

enable

Enter configuration mode:

configure terminal

Step 2: Enable SIP-to-SIP calling

If your CME system uses SIP endpoints, enable SIP-to-SIP connections:

voice service voip
 allow-connections sip to sip
 exit

Keep your existing voice-service configuration.

Do not replace unrelated working settings.

Step 3: Configure the audio codecs

Create a codec preference list:

voice class codec 1
 codec preference 1 g711alaw
 codec preference 2 g711ulaw
 exit

This provides G.711 A-law and μ-law for normal Voyced telephone calls.

Other codecs may be used where your router and the complete call path support them.

Step 4: Configure SIP authentication and registration

Enter SIP user-agent configuration:

sip-ua
 credentials number YOUR-DID username YOUR-DID password 0 YOUR-SERVICE-PASSWORD realm sip.voyced.eu
 authentication username YOUR-DID password 0 YOUR-SERVICE-PASSWORD realm sip.voyced.eu
 registrar dns:sip.voyced.eu expires 3600
 sip-server dns:sip.voyced.eu
 exit

Replace:

• YOUR-DID with your Voyced SIP username.

• YOUR-SERVICE-PASSWORD with your Voyced Service Password.

The registration and credential syntax may differ between Cisco IOS releases.

Some routers require a registered number to be associated with an eligible dial peer or SIP trunk registration configuration. On newer IOS XE systems, the equivalent settings may be configured under a voice-class tenant.

The authentication realm must match the realm used by the SIP server. If registration fails because of a realm mismatch, check the realm returned in the SIP authentication challenge.

Confirm that your router actually sends a SIP REGISTER request and receives a successful response before continuing.

Step 5: Configure the outgoing dial-peer

Create an outgoing dial-peer for international calls:

dial-peer voice 1000 voip
 description Outbound via Voyced
 destination-pattern 00T
 session protocol sipv2
 session target dns:sip.voyced.eu
 session transport udp
 voice-class codec 1
 dtmf-relay rtp-nte
 no vad
 exit

The destination pattern 00T matches international numbers beginning with 00.

Make sure your existing CME dial plan passes the full international number to this dial-peer.

Do not strip the first two digits.

If your users dial an additional outside-line access digit, configure your existing dial plan to remove only that access digit before sending the number to Voyced.

Step 6: Configure voicemail access

To route Voyced voicemail calls, add a dial-peer:

dial-peer voice 1001 voip
 description Voyced Voicemail
 destination-pattern 1233
 session protocol sipv2
 session target dns:sip.voyced.eu
 session transport udp
 voice-class codec 1
 dtmf-relay rtp-nte
 no vad
 exit

This routes calls to 1233 towards Voyced.

Check that your existing CME dial plan does not intercept this number as a local feature code.

Step 7: Configure incoming call routing

Create an incoming dial-peer that recognises calls to your Voyced DID:

dial-peer voice 2000 voip
 description Incoming from Voyced
 incoming called-number YOUR-DID
 session protocol sipv2
 voice-class codec 1
 dtmf-relay rtp-nte
 no vad
 exit

Replace YOUR-DID with your actual telephone number.

This dial-peer identifies incoming SIP calls. It does not, by itself, select the final internal extension.

Use your existing CME directory-number and dial-plan configuration, with the appropriate number translation or destination matching, to route the received DID to the correct extension or group.

For a system with several Voyced DIDs, create appropriate matching and routing rules for each number.

Step 8: Save and check registration

Finish the configuration:

end
write memory

Check SIP registration:

show sip-ua register status

A successfully registered number should show:

yes

You can also check:

show sip-ua status
show dial-peer voice summary

If the registration command shows no entries, check whether the router has an eligible number or SIP registration configuration for the trunk.

A configured registrar address alone does not prove that the router has registered your Voyced account.

Test Your Connection

Once the Cisco gateway or CME router has registered successfully, complete these tests.

Test 1: Outgoing calls

1. Use a Cisco telephone extension.

2. Dial a permitted external number.

3. Confirm the call reaches Voyced.

4. Check audio in both directions.

5. Verify that the recipient sees your authorised Caller ID.

Test 2: Incoming calls

1. Call your Voyced number from another telephone.

2. Confirm your Cisco system receives the call.

3. Check that the DID reaches the correct extension or group.

4. Answer and test audio.

Test 3: International calls

Voyced requires all international calls to use:

00 + Country Code + Telephone Number

For example:

00442035000202

If your Cisco dial plan uses 9 for an outside line, the user may dial:

900442035000202

The Cisco system must remove the access digit and send:

00442035000202

to Voyced.

Test 4: Voicemail

Dial:

1233

If your Cisco system uses an outside-line prefix, follow the configured dial plan.

Confirm that the call reaches Voyced voicemail.

Cisco telephone systems may also provide their own voicemail service. You can continue using that instead.

Test 5: Simultaneous calls

If your Voyced account supports several simultaneous calls, test the expected call capacity.

The available number of calls depends on your Voyced service and the Cisco system's licensed capacity and configuration.

Troubleshooting

The gateway does not register with Voyced

Check:

Do not use your Voyced website login password.

For CME or IOS gateways, check:

show sip-ua register status

If no registration is shown, verify the supported registration method for your IOS release.

CUCM trunk exists but Voyced does not register

A CUCM SIP trunk is not the same as a SIP registration account.

Check the provider-facing Cisco gateway or CUBE.

The gateway must perform the required Voyced registration.

Creating a Digest User in CUCM does not replace this step.

Incoming calls do not work

• Confirm the provider-facing device has registered.

• Check the incoming SIP dial-peer or CUBE call routing.

• Check that the correct DID reaches CUCM or CME.

• Confirm the internal destination exists.

• Review the gateway and PBX call routing rules.

For CUCM, make sure the inbound number matches an appropriate directory number, translation pattern or other configured destination.

For CME, make sure the incoming DID is mapped through the local dial plan.

Outgoing calls do not work

• Check SIP registration on the gateway.

• Confirm the correct outgoing dial-peer or CUCM route pattern is selected.

• Check that the destination number is formatted correctly.

• Verify your Voyced account has sufficient call credit.

• Confirm the destination is permitted.

International calls fail

Check that the number sent to Voyced begins with 00.

For CUCM, check the route pattern and Discard Digits settings.

For CME, check the dial-peer and any number translation rules.

Do not let the Cisco system remove the international prefix.

No audio or one-way audio

Check:

• The Cisco gateway's network and NAT configuration.

• The configured RTP ports and firewall rules.

• The selected codecs.

• The audio settings of connected extensions.

• Any media translation or termination settings between CUCM and the gateway.

Start with G.711 A-law and μ-law.

Incorrect Caller ID

Your Cisco system may set outgoing identity information through SIP headers, calling-party transformations and dial-peer settings.

Only use telephone numbers authorised on your Voyced account.

If you want another outbound Caller ID:

1. Log in to your Voyced client area.

2. Open a sales support ticket.

3. Use the subject Outbound Caller ID adjustment.

4. Provide your Voyced DID.

5. Provide the number you want displayed.

Numbers outside your Voyced account require proof of ownership and additional verification.

Voyced Internal DIDs and extension numbers must not be used as public Caller ID numbers.

Check Cisco SIP diagnostics

For CME and Cisco IOS voice gateways, useful commands include:

show sip-ua status
show sip-ua register status
show dial-peer voice summary
show call active voice brief

For SIP message tracing:

debug ccsip messages

Disable debugging after the test:

undebug all

On CUCM, use Cisco Real-Time Monitoring Tool (RTMT) and the available call-processing traces.

If you contact Voyced Support, provide the date, time, destination number and result of the failed call.

Do not share your Service Password.

Final Tips

• Use sip.voyced.eu as your primary SIP server.

• Use UDP port 5060 for the standard connection.

• Use G.711 A-law and μ-law for broad audio compatibility.

• Make sure the provider-facing Cisco device supports and performs SIP registration.

• For CUCM, configure the provider connection on a compatible gateway or CUBE.

• For CME, verify actual SIP registration, not just the presence of registrar settings.

• Keep incoming and outgoing routing correctly configured.

• Preserve the leading 00 for every international call.

• If your Cisco dial plan uses an outside-line access digit, remove only that digit.

• Use only authorised Caller ID numbers.

• Check your Cisco licences and Voyced call capacity.

• Test incoming and outgoing calls after changing SIP or routing settings.

Once registration, call routing and audio have been tested successfully, your Cisco telephone system is ready to use with Voyced.

Last updated: 27/10/2026

© Voyced
All information provided is copyrighted and purely informative in nature. It is maintained by Voyced with the greatest of care using reliable sources only.
Given the fast evolution of the telecom sector, Voyced does not offer any guarantee about the accuracy and completeness of the information offered. 
We explicitly do not give anyone permission to use this information in any other way than to inform themselves about what (legal) requirements there may be and they need to comply with when registering Services and/or DIDs with Voyced.