SIP Trunk Setup for Wazo Platform

Use Voyced as an external SIP provider

This guide explains how to connect your Voyced telephone number and SIP trunk to Wazo Platform, allowing your business to make and receive telephone calls through Voyced.

Wazo Platform supports third-party SIP providers using standard SIP registration with a username, password and SIP server.

This manual covers modern Wazo Platform installations using PJSIP, including Wazo Platform 26.x.

The instructions use Wazo's web administration interface, Wazo UI.

What You'll Need

Before you begin, make sure you have:

• Administrator access to Wazo Platform

• Access to Wazo UI

• A working Wazo Platform installation

• At least one configured user and SIP telephone

• Permission to manage SIP trunks and call routing

• An active Voyced telephone number

Your Voyced SIP details:

Replace the example username and password with your actual Voyced service details.

Requirements Before You Begin

Your Wazo installation must have:

• A working internet connection

• Correct DNS settings

• A configured SIP transport

• At least one internal calling context

• An incoming-call context

• An outgoing-call context

• A working SIP extension for testing

Recommended audio codecs:

• PCMA / G.711 A-law

• PCMU / G.711 μ-law

Your firewall must allow the required SIP signalling and RTP audio traffic.

Use full international telephone numbers without a leading + when sending calls to Voyced.

Example:

442012345678

Permitted Calling Traffic

Voyced provides retail-quality telephone services for normal business conversations.

Wazo can support contact centre applications, but Voyced does not permit predictive dialling, automated bulk calling or short-burst traffic.

Agent-initiated calls, incoming customer calls and ordinary business conversations are supported.

SIP Trunk Setup Steps

1. Log in to Wazo Platform

1. Open your Wazo UI administration interface.

2. Log in using your administrator credentials.

3. Select the tenant or organisation that will use Voyced.

4. Navigate to Call Management → Trunks.

5. Click Add or Create.

6. Select SIP as the trunk type.

Modern Wazo Platform uses PJSIP to manage SIP trunks.

The configuration is divided into several tabs:

• Trunk

• AOR

• Authentication

• Endpoint

• Identify

• Registration

• Registration Outbound Auth

• Outbound Auth

Each tab handles a different part of the SIP connection.

2. Create the Voyced SIP Trunk

Open the Trunk tab.

Enter:

The Context determines which dialplan processes incoming calls.

For a normal single-tenant installation, select the existing incoming-call context.

Depending on your configuration, this may be called:

from-extern

Modern multi-tenant Wazo installations typically use a generated context name similar to:

ctx-company-incall-xxxxxxxx

Select the actual incoming-call context belonging to your tenant.

Do not select the internal context for incoming public calls.

SIP Transport

Use the existing UDP transport.

On many installations, this is named:

transport-udp

Wazo normally listens on UDP port 5060.

This is the local SIP listening port. Voyced also uses destination port 5060 for the standard connection.

Outgoing Caller ID Format

Where available, select:

E164

This is the digits-only international caller ID format.

Wazo also offers +E164 on supported versions.

The E164 setting is appropriate for caller IDs selected dynamically through Wazo applications.

The called telephone number is controlled separately by the outbound dialplan, which we will configure later.

Save the initial trunk settings if your interface requires it.

3. Configure the SIP Server Address

Open the AOR tab.

AOR means Address of Record.

This section tells Wazo where to send SIP requests for the trunk.

Add the following AOR option:

Enter:

sip:sip.voyced.eu:5060

This is the SIP destination used for outgoing calls.

The sip: prefix is required here because this field expects a SIP URI.

Optional Connection Monitoring

You can also configure:

This tells Asterisk to check the SIP destination periodically using SIP OPTIONS requests.

For the initial configuration, you may use the existing default.

If the server does not respond to OPTIONS requests but registration and calls work, do not treat an OPTIONS failure alone as proof that the SIP account is unavailable.

Save the AOR settings.

4. Configure the SIP Endpoint

Open the Endpoint tab.

This section controls how Wazo sends and receives SIP calls through the trunk.

Add the following PJSIP options:

Replace Your-Voyced-DID with your Voyced SIP username.

From User

Enter:

Your-Voyced-DID

This identifies the account in outgoing SIP messages.

From Domain

Enter:

sip.voyced.eu

Audio Codecs

The combination:

disallow=all
allow=alaw,ulaw

restricts the trunk to the two recommended G.711 codecs.

If your version uses a single codec list, configure:

alaw,ulaw

DTMF

Set:

rfc4733

This supports keypad input during calls, including IVR menus.

Direct Media

Set:

no

This keeps RTP audio routed through Wazo rather than attempting to connect the telephone and external provider directly.

Save the endpoint settings.

5. Configure Registration

Open the Registration tab.

This is where Wazo registers its SIP account with Voyced.

Add the following options:

Server URI

Enter:

sip:sip.voyced.eu:5060

This is the registrar address.

Client URI

Enter:

sip:Your-Voyced-DID@sip.voyced.eu

For example, if your SIP username is 442012345678:

sip:442012345678@sip.voyced.eu

Contact User

Enter your Voyced SIP username:

Your-Voyced-DID

This controls the username in the SIP Contact header.

Registration Expiry

Set:

3600

This requests a registration lifetime of 3600 seconds.

If the registrar accepts another interval, Wazo will follow the negotiated registration settings.

Retry Interval

Set:

60

This controls how soon Wazo retries a temporary registration failure.

Line Parameter

Set:

yes

This adds a unique registration identifier to the SIP Contact address.

If the provider returns that identifier in incoming calls, Asterisk can associate those calls with the correct SIP endpoint.

Where your Wazo version exposes an endpoint option in the registration settings, associate it with the Voyced trunk endpoint.

The registration identifier is useful for inbound call identification, but its effectiveness depends on the information present in incoming SIP requests.

Save the registration settings.

6. Configure Registration Authentication

Open:

Registration Outbound Auth

This section contains the credentials used when Voyced challenges a SIP REGISTER request.

Enter:

Replace the placeholders with your actual credentials.

For example:

Username: 442012345678
Password: YourServicePassword

The password must be the SIP service password associated with the telephone number.

Save the authentication settings.

7. Configure Outbound Call Authentication

Open the Outbound Auth tab.

This section controls authentication for outgoing SIP calls.

Enter:

These credentials are normally the same as those used for SIP registration.

This allows Wazo to respond if an outgoing SIP INVITE receives an authentication challenge.

Both authentication sections are important:

Save the settings.

8. Configure Incoming SIP Identification

Open the Identify tab.

This section determines how Wazo recognises incoming calls belonging to the Voyced trunk.

For the initial configuration, use the registration-based endpoint identification configured earlier.

If the incoming SIP request preserves the registration's line identifier, Asterisk can match the call to the appropriate endpoint.

If the provider does not return this identifier, an additional incoming identification method may be required.

Wazo supports identification using:

• SIP source address

• SIP headers

• SIP authentication information

For source-address identification, use the actual signalling addresses verified for incoming calls.

Do not enter an arbitrary or guessed IP address.

For the initial configuration, avoid adding an identification rule until you know whether registration-based matching works.

Incoming Authentication

The separate Authentication tab controls authentication of SIP requests arriving at Wazo.

It is not where you enter your Voyced registration password.

Leave this section unconfigured for the initial provider connection unless the incoming SIP service specifically requires authenticated INVITE requests.

Incoming calls must still match the correct SIP endpoint.

Save the trunk configuration.

9. Verify SIP Registration

After saving the trunk, allow Wazo to apply the configuration.

Open a terminal on your Wazo server.

Run:

asterisk -rx "pjsip show registrations"

Look for the registration associated with Voyced.

Expected status:

Registered

You can also inspect the available SIP endpoints:

asterisk -rx "pjsip show endpoints"

And the configured contacts:

asterisk -rx "pjsip show contacts"

The registration should point to:

sip.voyced.eu

If the registration is rejected, check the registration and authentication settings before continuing.

A successful SIP registration confirms that Wazo has authenticated with Voyced.

Incoming and outgoing call routing must still be configured.

10. Check Your Calling Contexts

Wazo uses contexts to control which telephone numbers are reachable.

A standard installation has three types:

In Wazo UI, open:

Settings → Dialplan → Contexts

Select your tenant's contexts.

Check that:

1. An internal context exists.

2. An incoming-call context exists.

3. An outgoing-call context exists.

4. The internal context includes the appropriate outgoing-call context.

The incoming-call context should not be included in the internal context simply to make external calling work.

Incoming Number Range

Select your incoming-call context.

Open the Incall section.

Make sure it permits your Voyced telephone number.

For example:

The example number contains 12 digits.

If your Voyced number has another length, enter the correct value.

For several telephone numbers, add the necessary number ranges.

Save the context.

11. Create an Incoming Call Route

To receive calls through Voyced:

1. Navigate to Call Management → Incalls.

2. Click Create.

3. Enter the incoming-call details.

Example:

Replace Your-Voyced-DID with your full telephone number.

For example:

442012345678

The extension must match the telephone number received in the incoming SIP INVITE.

Example: Reception

Click Save.

Incoming calls to this number will now follow the selected route.

12. Configure an Incoming Call Group

If several employees should receive calls to the same Voyced number, create a ring group.

1. Navigate to Call Management → Groups.

2. Create a new group.

3. Enter a group name.

4. Add the relevant users.

5. Select the ringing method.

6. Save.

Example:

Return to:

Call Management → Incalls

Edit your Voyced incoming route.

Change:

Save the changes.

You can also route incoming calls to a queue, IVR or voicemail destination already configured in Wazo.

13. Create the Outgoing Call Route

Navigate to:

Call Management → Outcalls

Click Create.

Open the Outcall tab.

Enter:

Next, open the Trunks tab.

Select:

Voyced SIP Trunk

This associates the outgoing route with your Voyced connection.

Save the initial route settings.

14. Configure the Outbound Dial Pattern

Open the route's Extensions section.

Add a dial pattern.

For this example, users dial 9 before an international telephone number.

Configure:

Some Wazo UI versions handle the leading underscore automatically when creating an Asterisk extension pattern.

If the interface expects the pattern without that prefix, enter:

9X.

The resulting Asterisk dialplan should contain the equivalent pattern:

_9X.

How the Prefix Works

A user dials:

9442012345678

Wazo removes the leading 9.

The outgoing SIP request contains:

442012345678

This is the number format required for Voyced.

The Strip Digits setting is:

1

because the example uses one internal access digit.

If your business already has a different dialling prefix, adjust the routing rule to match that prefix.

The example pattern is broad. For production use, apply your existing destination restrictions and retain separate emergency and special-service routes.

Save the route.

15. Configure Outbound Caller ID

Wazo supports outbound caller ID settings at user and outgoing-route level.

For a simple setup, use your authorised Voyced telephone number.

In:

Call Management → Outcalls

Open Voyced Outbound.

In the Extensions section, set the Caller ID to:

Your-Voyced-DID

For example:

"Reception" <442012345678>

The number must be authorised for presentation through your Voyced account.

Individual User Caller IDs

Wazo also supports individual outbound caller IDs.

Open the relevant user under the user management section.

Locate Outgoing Caller ID.

Choose either:

• Default

• An authorised outgoing number

When a user selects Default, Wazo can use the caller ID configured on the outgoing route.

If a specific authorised number is selected, Wazo may use that number instead.

Recent Wazo Platform releases also allow users to select a default outgoing caller ID for telephones that cannot select the number during each call.

Save the settings.

16. Configure Multiple Voyced Telephone Numbers

If multiple telephone numbers are delivered through the same Voyced SIP account, you can route them through the existing trunk.

For each additional telephone number:

1. Open your incoming-call context.

2. Add the required DID range.

3. Navigate to Call Management → Incalls.

4. Create a new incoming route.

5. Enter the additional telephone number.

6. Select its destination.

7. Save.

Example:

Each number must match the format received from the SIP provider.

A separate SIP registration is not needed for every number delivered through the same account.

If your telephone numbers belong to different SIP accounts, configure separate registrations using the credentials assigned to those accounts.

17. Configure Simultaneous Calls

Your Wazo system may have several active telephone extensions and external routes.

Make sure the number of simultaneous calls matches the capacity available on your Voyced service.

For example:

These values are examples only.

Use the actual simultaneous calling capacity of your Voyced service.

Where needed, apply suitable call limits in your Wazo configuration to avoid exceeding the available capacity.

18. Configure Firewall and NAT

Your Wazo server must communicate with:

sip.voyced.eu

Recommended settings:

If Wazo Is Behind NAT

Wazo supports NAT settings through its PJSIP transport and endpoint configuration.

Open the SIP transport settings.

Depending on your version, these may be available under the advanced SIP or transport administration section.

Review:

Example internal network:

192.168.1.0/24

Use your actual network details.

For endpoints behind NAT, the following options may also be needed:

These settings help Asterisk handle SIP and RTP traffic behind NAT.

Changes to PJSIP transport settings may require an Asterisk restart.

If your Wazo server already uses a working NAT configuration, retain it.

Testing Your Setup

Registration Test

Open a terminal on your Wazo server.

Run:

asterisk -rx "pjsip show registrations"

The expected result is:

Registered

If the registration fails, check the SIP server and authentication settings.

Inbound Test

1. Call your Voyced telephone number from an external mobile telephone.

2. Confirm Wazo receives the SIP call.

3. Check the correct incoming-call route matches.

4. Verify the configured user, group or IVR receives the call.

5. Answer the call.

6. Check two-way audio.

If you have several Voyced numbers, test each number separately.

Outbound Test

1. Pick up a telephone registered to Wazo.

2. Dial 9 followed by the full international number.

3. Confirm Wazo selects the Voyced trunk.

4. Verify the destination rings.

5. Check audio in both directions.

6. Confirm the correct caller ID appears.

Example:

9442012345678

Wazo should send:

442012345678

to Voyced.

Troubleshooting

SIP Registration Fails

Check:

• SIP server is sip.voyced.eu

• server_uri is correct

• client_uri contains your Voyced username

• Registration Outbound Auth contains the correct credentials

• UDP transport is selected

• Destination port is 5060

• DNS resolution works

Run:

asterisk -rx "pjsip show registrations"

Check the registration state.

401 or 407 Error

These SIP responses indicate authentication is required.

An initial challenge is normal.

If registration or outgoing calls continue to fail, check:

• SIP username

• Service password

• Registration Outbound Auth

• Outbound Auth

• Authentication realm

• Subsequent authenticated SIP requests

Remember that Wazo has separate authentication settings for registration and outgoing calls.

403 Error

Check:

• SIP authentication

• Account status

• Outbound calling permissions

• Caller ID authorisation

• Any account restrictions

404 Error

Check:

• Destination telephone number

• Outbound route

• Dial pattern

• Strip Digits setting

• SIP Request-URI

• Incoming DID matching

• Which system returned the response

For example:

Incorrect number sent to Voyced:

9442012345678

Correct number:

442012345678

Incoming Calls Do Not Ring

Check:

• SIP registration

• Incoming endpoint identification

• Registration line setting

• Incoming-call context

• DID range

• Incoming-call route

• Destination user or group

If Wazo receives the SIP INVITE but does not identify the correct trunk, inspect the endpoint matching information.

If Wazo identifies the trunk but no destination rings, check the incoming DID and routing context.

Incoming Calls Receive 401 Unauthorized

This may happen when the incoming SIP request is matched to an endpoint that requires authentication.

Check:

• The trunk's Authentication tab

• The Identify settings

• Registration-based endpoint matching

• The incoming SIP source

• The SIP endpoint handling the INVITE

Do not confuse authentication of Wazo's outgoing REGISTER with authentication of incoming INVITE requests.

Outbound Calls Fail

Check:

• SIP registration

• Outbound trunk authentication

• Outgoing route

• Dial pattern

• Outgoing-call context

• Trunk assignment

• Caller ID

• Account credit

• Simultaneous call capacity

Outgoing Calls Do Not Match the Route

Check that the outgoing-call context is included in the user's internal context.

Also confirm the dialled number matches the configured extension pattern.

For example:

_9X.

If the outbound context is not available to the user, Wazo will not select the outgoing route.

Caller ID Is Incorrect

Check:

• The Caller ID configured on the outgoing route

• The user's Outgoing Caller ID

• Dynamic caller ID selection

• The trunk's outgoing caller ID format

• SIP From and identity headers

For the initial setup, use your registered Voyced telephone number.

One-Way Audio

Check:

• RTP port configuration

• Firewall rules

• NAT settings

• Public IP address

• Codec negotiation

• SDP media addresses

• SIP ALG

A successful SIP registration does not guarantee that RTP audio is working.

Calls Disconnect After Approximately 30 Seconds

Check:

• SIP acknowledgement delivery

• NAT handling

• Firewall timeouts

• SIP signalling addresses

• Session timers

Trunk Appears Unavailable

Check the registration separately from endpoint reachability.

Run:

asterisk -rx "pjsip show registrations"

Then:

asterisk -rx "pjsip show endpoints"

A provider may accept registration while not responding to SIP OPTIONS checks.

Confirm the problem with an actual inbound or outbound call test.

Reviewing SIP Logs

Wazo uses Asterisk for SIP signalling.

For detailed troubleshooting, open the Asterisk CLI:

asterisk -rvvv

Enable the SIP message logger:

pjsip set logger on

Repeat the failed registration or telephone call.

Look for:

• REGISTER

• INVITE

• Request-URI

• From

• To

• SIP response code

• SDP media information

Disable detailed SIP logging afterwards:

pjsip set logger off

Avoid sharing SIP traces containing authentication information without removing sensitive values.

Final Tips

• Keep the SIP server set to sip.voyced.eu.

• Use your Voyced telephone number as the SIP authentication username.

• Use your Voyced service password for registration and outbound authentication.

• Use PJSIP for modern Wazo installations.

• Configure the AOR to point to the Voyced SIP server.

• Enable SIP registration.

• Configure both Registration Outbound Auth and Outbound Auth.

• Use PCMA and PCMU for audio compatibility.

• Use the correct incoming-call context.

• Create an incoming route for each telephone number.

• Create an outgoing route linked to the Voyced trunk.

• Remove any internal access prefix before sending outbound calls.

• Use full international telephone numbers without a leading +.

• Present an authorised outbound caller ID.

• Test registration, incoming calls and outgoing calls separately.

Wazo Platform supports external SIP trunks through PJSIP registration and authentication.

With the correct SIP trunk, incoming routes, outgoing routes and telephone number settings, your Wazo installation can use Voyced for normal inbound and outbound business telephone calls.

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.