SIP Trunk Setup for MagnusBilling

Use Voyced as an external SIP provider

This guide explains how to connect your Voyced telephone number and SIP trunk to MagnusBilling.

MagnusBilling is a VoIP billing and telephone management platform built on Asterisk. It supports external SIP providers, telephone extensions, incoming numbers, outbound routing and call billing.

With the correct configuration, MagnusBilling can make and receive business telephone calls through Voyced using SIP registration.

This manual covers:

• MagnusBilling 8 using Asterisk 20 and PJSIP

• MagnusBilling 7 using Asterisk 13 and chan_sip

MagnusBilling 8 is the current development version. MagnusBilling 7 remains available in maintenance mode.

The administration menus are similar, but the underlying SIP configurations are different.

What You'll Need

Before you begin, make sure you have:

• Administrator access to MagnusBilling

• A working MagnusBilling installation

• A working internet connection

• Access to the Routes and Rates menus

• At least one customer and SIP telephone for testing

• Permission to manage trunks, providers and DIDs

• 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 MagnusBilling system must have:

• A working Asterisk service

• DNS resolution for sip.voyced.eu

• Internet access for SIP signalling

• Available RTP connectivity for telephone audio

• Sufficient calling capacity

• At least one functioning SIP account

• Correct firewall and NAT settings

Recommended audio codecs:

• G.711 A-law / alaw

• G.711 μ-law / ulaw

Voyced expects outgoing numbers in full international format without a leading +.

Example:

442012345678

Permitted Calling Traffic

Voyced provides telephone services for normal business conversations.

MagnusBilling includes automated calling features, but Voyced does not permit predictive dialling, automated bulk calling or short-burst traffic.

Use the Voyced connection for incoming calls and individually initiated business conversations.

SIP Trunk Setup Steps

1. Check Your MagnusBilling Version

Log in to MagnusBilling.

Check your installed software version under the administration or system information area.

This difference is important.

MagnusBilling 8 generates PJSIP trunk configurations. MagnusBilling 7 uses traditional SIP configuration.

Do not copy legacy chan_sip settings directly into a MagnusBilling 8 installation.

Both versions provide a web interface for configuring SIP trunks.

2. Log in to MagnusBilling

1. Open your MagnusBilling administration interface.

2. Log in with your administrator account.

3. Open the main dashboard.

4. Locate the Routes menu.

5. Check whether another SIP provider is already configured.

If you have existing working providers, leave their settings unchanged.

For Voyced, create a new provider and trunk.

3. Create the Voyced Provider

Navigate to:

Routes → Providers

Click New.

Enter:

The Provider record identifies Voyced inside MagnusBilling.

It is used for carrier management and reporting.

The Provider record does not handle SIP registration. That is configured through the Trunk.

Click Save.

4. Create the Voyced SIP Trunk

Navigate to:

Routes → Trunks

Click New.

Under the General tab, enter:

Trunk Name

Enter:

voyced

This identifies the connection inside MagnusBilling.

Username

Enter your Voyced SIP username.

For example:

442012345678

Password

Enter your Voyced SIP service password.

Host

Enter:

sip.voyced.eu

Do not use a fixed SIP server IP address.

Register Trunk

Select:

Yes

This is required for the normal Voyced connection.

MagnusBilling will configure SIP registration using the trunk details.

5. Configure the SIP Destination Port

In the trunk configuration, open:

Supplementary Info

Locate:

Port

Enter:

5060

This is Voyced's SIP destination port.

It is separate from the local SIP port used by your Asterisk server.

For example, your MagnusBilling server may listen on its configured local SIP transport while connecting to Voyced on UDP port 5060.

You do not need to change the local listening port simply because Voyced uses 5060.

6. Configure Registration and Authentication

Return to the trunk's General tab.

Confirm:

These settings identify the SIP account that MagnusBilling registers with Voyced.

MagnusBilling 8

MagnusBilling 8 creates the PJSIP registration and authentication objects.

The generated connection includes:

• Endpoint

• Authentication

• Address of Record

• Outbound registration

• SIP transport

• Incoming endpoint identification

The registration must use the Voyced credentials.

Its SIP server and registrar must point to:

sip.voyced.eu

MagnusBilling 7

Older installations use a traditional Asterisk SIP registration string.

The expected format is:

username:password@registrar/contact

For Voyced, this corresponds to:

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

The final telephone number identifies the registration contact extension.

MagnusBilling's trunk form normally generates the registration details from the saved fields.

The Register String field may not be visible because MagnusBilling manages it automatically.

Use the registration format above when checking the generated configuration or troubleshooting registration.

7. Configure the Audio Codecs

In the trunk's General tab, find:

Codec

Select:

Keep only alaw and ulaw selected for the initial configuration.

These correspond to G.711 A-law and G.711 μ-law.

They are suitable for normal business telephone conversations.

8. Configure SIP Identity Settings

Open:

Supplementary Info

Review:

Fromuser

Leave this field empty for the initial configuration.

MagnusBilling can use the caller ID associated with the SIP customer account when generating the From header.

Entering a fixed Fromuser may override the caller ID you want to present.

If SIP authentication or testing shows that the provider requires the registered account username in the From header, enter your Voyced SIP username and test again.

Fromdomain

Enter:

sip.voyced.eu

Context

Keep the existing MagnusBilling billing context.

On standard installations, this is:

billing

The context tells Asterisk where incoming calls should enter the billing and routing system.

Do not change it to another context without confirming that the destination has the appropriate MagnusBilling call handling.

DTMF

Use RFC2833.

This supports telephone keypad input for IVR menus, voicemail and similar services.

Direct Media

Set:

no

This keeps audio routed through Asterisk.

Qualify

Set:

yes

Asterisk can use SIP OPTIONS to check whether the provider is reachable.

Registration and OPTIONS responses should be checked separately during troubleshooting.

9. Configure the Simultaneous Call Limit

Still under Supplementary Info, locate:

Max use

This limits simultaneous use of the trunk.

For example:

Enter the number of concurrent calls supported by your Voyced service.

The value -1 is used for an unrestricted limit in MagnusBilling.

For a normal business connection, configure a limit that reflects your actual service capacity.

If several customer accounts share the trunk, their combined use must remain within that capacity.

Save the trunk.

10. Check the Trunk's Active Status

Navigate to:

Routes → Trunks

Find:

voyced

Check that its Status is Active.

If it is inactive:

1. Open the trunk.

2. Change Status to Active.

3. Save.

An Active status confirms that MagnusBilling can select the trunk for routing.

It does not prove that SIP registration has succeeded.

The registration status must be checked separately.

11. Verify SIP Registration

MagnusBilling 8

For a self-managed installation, open a terminal on your MagnusBilling server.

Run:

asterisk -rx "pjsip show registrations"

Look for the Voyced connection.

Expected registration state:

Registered

You can also inspect the configured endpoints:

asterisk -rx "pjsip show endpoints"

And the available contacts:

asterisk -rx "pjsip show contacts"

MagnusBilling 7

On older installations using chan_sip, run:

asterisk -rx "sip show registry"

Expected state:

Registered

If registration fails, check the username, password, registrar hostname and SIP transport settings before continuing.

12. Create the Voyced Trunk Group

MagnusBilling uses Trunk Groups to decide which carrier handles outgoing calls.

Navigate to:

Routes → Trunk Groups

Click New.

Enter:

The Type field supports several routing methods.

For a single Voyced trunk, select:

Order

Then add the Voyced trunk to the group.

If your system uses several providers, you may configure a suitable backup arrangement.

Save the Trunk Group.

13. Create a Calling Plan

MagnusBilling associates customer tariffs with a Plan.

Navigate to:

Rates → Plans

Click New.

Enter:

Save.

The Plan will be assigned to the customer account that uses Voyced.

If the customer already has a working Plan, you can add the Voyced tariffs to that Plan instead.

Do not replace an existing Plan if it contains working rates for other providers.

14. Configure Destination Prefixes

MagnusBilling uses destination prefixes to identify which telephone numbers match a tariff.

Navigate to:

Rates → Prefixes

Click New.

Enter the destination information.

For example:

This matches telephone numbers beginning with the UK country code.

Example:

442012345678

The prefix is used for rate matching.

It does not necessarily mean all UK destinations have the same price.

Landline, mobile and special-service destinations may have different rates.

Create the destination prefixes required by your actual Voyced tariff.

Save each prefix.

15. Configure the Customer Tariff

Navigate to:

Rates → Tariffs

Click New.

Select:

The tariff links three important elements:

1. The customer's calling Plan

2. The destination number prefix

3. The Trunk Group used for the call

For example:

Use the actual rates and billing increments you want to apply.

Do not enter an invented call price simply to complete the form.

If you are using MagnusBilling only for internal company calls, you can configure the pricing structure required by your internal accounting system.

Save the Tariff.

Repeat for the destinations the customer is permitted to call.

16. Configure Provider Rates

MagnusBilling also supports Provider Rates.

Navigate to:

Routes → Provider Rates

Use this section to record the costs associated with the Voyced provider.

For example:

These records support provider cost reporting and routing decisions where used.

Customer selling prices and provider buying prices are different values.

If you need accurate margin reporting, configure both correctly.

Save the Provider Rates.

17. Configure Number Prefix Handling

Voyced expects full international telephone numbers without a leading +.

For example:

442012345678

MagnusBilling can modify numbers using the trunk's:

• Add Prefix

• Remove Prefix

These fields appear under:

Routes → Trunks → voyced → General

Direct International Dialling

If your customers already dial:

442012345678

configure:

No modification is needed.

Dialling with International Access Prefix 00

If users dial:

00442012345678

the number must be converted before reaching Voyced.

The result must be:

442012345678

Use the applicable MagnusBilling number normalisation or prefix-removal rule to remove the leading 00.

The Remove Prefix field and any customer-level number handling must be checked together.

Do not remove the same prefix twice.

Dialling with a Leading +

If the dialled number is:

+442012345678

the final number sent through the trunk must be:

442012345678

Check the number actually passed to Asterisk's Dial operation.

The important result is the SIP Request-URI sent to Voyced.

18. Create or Select a Customer Account

Navigate to:

Customers → Users

On older MagnusBilling installations, this appears under:

Clients → Users

Click New, or select an existing test customer.

Enter the required customer information.

Example:

Assign the Plan configured earlier.

Save.

MagnusBilling normally creates a SIP account when a new customer is created.

This SIP account is used by the customer's telephone.

It is separate from the Voyced trunk registration.

19. Configure the Customer SIP Account

Navigate to:

Customers → SIP Users

On older versions:

Clients → SIP Users

Locate the SIP account belonging to your test customer.

Record:

• SIP username

• SIP password

• SIP server address

• SIP listening port

Configure a telephone or softphone with these details.

The telephone registers to MagnusBilling.

The connection is:

Telephone
    |
    v
MagnusBilling / Asterisk
    |
    v
Voyced SIP Trunk
    |
    v
External Telephone Network

The customer's telephone should not register directly with Voyced when you want MagnusBilling to manage its billing and routing.

Version 8

MagnusBilling 8 uses PJSIP for customer SIP accounts.

The standard local SIP port is UDP 5060, unless your administrator has changed it.

Version 7

Older installations use chan_sip.

Use the SIP port configured on your installation.

Confirm that the telephone registers successfully before continuing.

20. Configure Outbound Caller ID

The number presented on outgoing calls must be authorised for your Voyced service.

MagnusBilling supports caller ID settings for customer accounts and SIP users.

For the first test, use:

Your-Voyced-DID

For example:

442012345678

Navigate to the relevant SIP User or CallerID configuration.

Assign the authorised number.

If your installation allows several outgoing caller IDs, make sure users can only present numbers authorised for their account.

Trunk Fromuser

Remember that the trunk's Fromuser setting can override the outgoing SIP identity.

For the initial test, keep Fromuser empty and configure the caller ID through the customer account.

If the provider requires the registration username in the From header, enter that value only after confirming the requirement.

21. Add Test Credit

MagnusBilling can use prepaid or postpaid billing.

For a prepaid account, the customer needs sufficient balance to place a call.

Navigate to:

Billing → Refills

Click New.

Select your test customer.

Enter a suitable test credit amount.

Save.

The customer balance should now reflect the refill.

For postpaid accounts, confirm the customer's credit limit permits the test call.

A successful SIP registration does not bypass MagnusBilling's billing and credit controls.

22. Check Outbound Routing Before Calling

MagnusBilling 8 includes an administrator call diagnostic.

Navigate to:

Customers → SIP Users

1. Select exactly one SIP account.

2. Click Check User.

3. Enter the destination number.

4. Click Run Diagnostic.

For example:

442012345678

The diagnostic checks the routing decision without placing a real call.

It can show:

• Customer account

• Calling Plan

• Matched tariff

• Available credit

• Trunk Group

• Selected trunk

• Normalised destination

• Number that would be sent to the provider

Confirm the selected trunk is:

voyced

Also confirm the final number contains the country code without a leading +.

If the diagnostic fails, correct the reported routing or billing problem before placing the test call.

This function is available in supported MagnusBilling 8 releases.

For MagnusBilling 7, use the existing tariff search and route configuration tools, then verify the actual dialled number with a controlled test call.

23. Place an Outbound Test Call

Using your SIP telephone registered to MagnusBilling:

1. Dial an authorised destination.

2. Confirm Asterisk selects the Voyced trunk.

3. Check the destination rings.

4. Answer the call.

5. Check audio in both directions.

6. Test keypad input if required.

7. Confirm the correct caller ID appears.

8. End the call normally.

Example number sent to Voyced:

442012345678

The final destination must not contain an unwanted access prefix or leading +.

24. Create the Incoming DID

MagnusBilling manages incoming telephone numbers under its DIDs menu.

Navigate to:

DIDs → DIDs

Click New.

Enter:

For example:

442012345678

The DID must match the destination number MagnusBilling receives from Asterisk.

If your system uses several servers, assign the DID to the correct receiving server.

Complete any additional DID settings required by your installation.

These may include incoming call charges, monthly fees and channel limits.

Save the DID.

25. Configure the DID Destination

Creating a DID alone does not determine which telephone should ring.

Navigate to:

DIDs → DID Destination

Click New.

Select:

The destination type determines how MagnusBilling handles the incoming call.

Available destination methods may include:

• SIP user

• Queue

• IVR

• Another supported call destination

For a simple reception telephone, select the SIP user.

Save.

When an incoming call reaches MagnusBilling and matches the DID, the system should route it to the selected SIP account.

26. Configure a Queue or IVR

If several users should receive calls to the same Voyced number, you can route the DID to a Queue.

Navigate to:

DIDs → Queues

Create or select an existing queue.

Configure the required agents and queue settings.

Then return to:

DIDs → DID Destination

Edit the Voyced destination.

Select:

For an automated menu, choose the IVR destination type and select the appropriate IVR.

Keep your existing queue or IVR configuration if it already handles the intended calls.

27. Configure Multiple Incoming Numbers

If several telephone numbers are delivered through the same Voyced SIP account, they can share the same trunk registration.

For each additional number:

1. Open DIDs → DIDs.

2. Create the DID.

3. Assign it to the correct customer.

4. Open DIDs → DID Destination.

5. Create the destination.

6. Save.

Example:

Each number must match the incoming called number seen by MagnusBilling.

Separate SIP registrations are not normally needed when several numbers belong to one registered Voyced account.

28. Check Incoming Number Recognition

The trunk registration tells Voyced where your MagnusBilling system can receive calls.

When a call arrives, Asterisk must identify the correct called telephone number.

For example:

442012345678

The DID in MagnusBilling must match that number after any normalisation.

Check:

• SIP Request-URI

• SIP To header

• Asterisk destination number

• MagnusBilling DID record

• DID Destination

In MagnusBilling 8, PJSIP must also associate the incoming SIP INVITE with the correct provider endpoint.

Successful registration does not guarantee that endpoint identification or DID routing works.

If several DIDs arrive through one account, test each separately.

29. Test the DID Routing

Supported MagnusBilling 8 releases provide an administrator DID diagnostic.

Navigate to:

DIDs → DIDs

1. Select exactly one DID.

2. Click Check DID.

3. Enter an originating caller ID if needed.

4. Click Run Diagnostic.

The diagnostic checks the DID destination without placing a real call.

It can identify:

• DID status

• Destination type

• Receiving customer

• Selected SIP account

• Queue or IVR destination

• Routing restrictions

• Missing destination information

Correct any blocking errors before testing an actual inbound call.

For older MagnusBilling releases, inspect the DID and destination settings directly.

30. Configure Firewall and NAT

Your MagnusBilling server must communicate with:

sip.voyced.eu

Recommended settings:

If Your Server Is Behind NAT

Check:

• External SIP address

• External RTP address

• Local network settings

• Firewall rules

• RTP port range

MagnusBilling 8 uses PJSIP transport settings.

MagnusBilling 7 uses the corresponding chan_sip network configuration.

Retain working NAT settings where possible.

Your firewall must permit the signalling and audio traffic required for incoming and outgoing calls.

31. Check Simultaneous Call Capacity

Your effective calling capacity depends on:

• The number of simultaneous calls included with Voyced

• The trunk's Max use setting

• Available Asterisk resources

• Customer-level calling limits

For example:

Use your actual service limits.

When several MagnusBilling customers share one Voyced trunk, consider their combined calling capacity.

Testing Your Setup

SIP Registration Test

For MagnusBilling 8:

asterisk -rx "pjsip show registrations"

For MagnusBilling 7:

asterisk -rx "sip show registry"

Expected registration state:

Registered

If the account is not registered, check the SIP server and authentication settings.

Outbound Test

1. Confirm the test telephone is registered to MagnusBilling.

2. Confirm the customer has the correct Plan.

3. Check that a matching tariff exists.

4. Confirm the Voyced Trunk Group is selected.

5. Confirm the customer has permission and available credit.

6. Dial an authorised international destination.

7. Check the call connects.

8. Test audio in both directions.

9. Confirm the caller ID.

Expected number sent to Voyced:

442012345678

Inbound Test

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

2. Confirm Asterisk receives the call.

3. Check the DID matches.

4. Verify the configured destination rings.

5. Answer the call.

6. Check two-way audio.

Test every additional DID separately.

Billing Test

After a successful outbound call:

1. Navigate to Reports → CDR.

2. Find the test call.

3. Check the destination number.

4. Confirm the selected trunk.

5. Review the call duration.

6. Check the customer selling price.

7. Check the recorded provider cost.

8. Confirm the customer balance changed as expected.

This verifies the telephone connection and MagnusBilling's billing rules.

Troubleshooting

SIP Registration Fails

Check:

• Host is sip.voyced.eu.

• Username is correct.

• Password is correct.

• Register Trunk is Yes.

• Provider Tech matches your MagnusBilling version.

• Destination port is 5060.

• DNS resolution works.

• Asterisk is running.

For MagnusBilling 8, check PJSIP registration status.

For MagnusBilling 7, check chan_sip registration status.

401 or 407 Error

These responses indicate SIP authentication is required.

An initial challenge is normal.

If registration repeatedly fails, check:

• SIP username

• Password

• Authentication realm

• Registrar hostname

• Subsequent authenticated REGISTER requests

403 Error

Check:

• Voyced account status

• Authentication

• Outbound calling permissions

• Caller ID authorisation

• Account restrictions

404 Error

Check:

• Destination telephone number

• Prefix handling

• Matched tariff

• Trunk selection

• SIP Request-URI

• Incoming DID matching

• Which system returned the response

Trunk Is Active but Not Registered

An Active trunk is available for routing inside MagnusBilling.

It does not confirm that the registrar has accepted the SIP connection.

Check registration using the appropriate Asterisk command.

Outbound Calls Fail

Check:

• SIP registration

• Customer Plan

• Destination prefix

• Tariff

• Trunk Group

• Trunk status

• Customer credit

• Calling permissions

• Max use limit

MagnusBilling can reject a call before it reaches Voyced if a rate, route or account permission is missing.

No Matching Tariff

Navigate to:

Rates → Tariffs

Check that the customer's Plan has a tariff matching the dialled destination.

Also check that the tariff selects the Voyced Trunk Group.

Outgoing Number Has the Wrong Format

Voyced expects digits-only international telephone numbers.

Correct:

442012345678

Review:

• Trunk Add Prefix

• Trunk Remove Prefix

• Customer number normalisation

• Destination prefix matching

• Final number sent to the trunk

Do not remove or add the same prefix in several places.

Incorrect Outbound Caller ID

Check:

• Customer CallerID

• SIP User caller ID

• Trunk Fromuser

• Trunk Fromdomain

• CID Add Prefix

• CID Remove Prefix

Use an authorised Voyced telephone number.

Incoming Calls Do Not Ring

Check:

• SIP registration

• Incoming provider identification

• Received destination number

• DID record

• DID Destination

• Receiving SIP user or queue

• Customer account status

If the incoming call reaches Asterisk but does not match a DID, inspect the called number.

All Incoming Numbers Reach One Destination

Check whether Asterisk passes the registered account number instead of the actual called DID.

Inspect the incoming SIP Request-URI and To header.

Confirm MagnusBilling receives a distinct destination number for each DID.

SIP Telephone Cannot Register

Check:

• SIP account username

• SIP account password

• MagnusBilling server address

• Local SIP port

• Account status

• Firewall restrictions

For MagnusBilling 8, use the PJSIP endpoint diagnostics.

For MagnusBilling 7, use the traditional SIP peer and registration diagnostics.

One-Way Audio

Check:

• RTP port range

• Firewall settings

• NAT configuration

• Public IP address

• Codec negotiation

• SIP ALG

Successful SIP registration does not guarantee working RTP audio.

Calls Disconnect After Approximately 30 Seconds

Check:

• SIP ACK delivery

• NAT handling

• Firewall timeouts

• SIP signalling addresses

• Session timers

Calls Fail Because of Balance

Check the customer's balance or postpaid credit limit.

For prepaid accounts, use:

Billing → Refills

to add the required credit.

Then repeat the outbound test.

Too Many Simultaneous Calls

Check:

• Voyced service capacity

• Trunk Max use

• Customer call limits

• Current active calls

Use:

Customers → Calls Online

to review active calls.

Reviewing SIP Logs

For MagnusBilling 8, open the Asterisk CLI:

asterisk -rvvv

Enable PJSIP logging:

pjsip set logger on

Repeat the failed registration or call.

Look for:

• REGISTER

• INVITE

• Request-URI

• From

• To

• SIP response code

• Authentication challenges

• SDP audio information

Disable logging afterwards:

pjsip set logger off

For MagnusBilling 7 using chan_sip:

sip set debug on

Disable it afterwards:

sip set debug off

Remove authentication details before sharing SIP traces.

Registration Works but Calls Still Fail

A successful SIP registration confirms authentication.

It does not prove the entire connection is working.

Test separately:

1. SIP registration

2. Customer SIP account

3. Outbound tariff matching

4. Trunk Group selection

5. Number formatting

6. Caller ID

7. Incoming DID routing

8. RTP audio

9. Billing and CDR records

Final Tips

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

• Use your Voyced telephone number as the SIP username.

• Use your Voyced service password for authentication.

• Set Register Trunk to Yes.

• Use PJSIP for MagnusBilling 8.

• Use the legacy SIP driver only for installations that support it.

• Use UDP port 5060 for the SIP destination.

• Enable G.711 A-law and G.711 μ-law.

• Keep the trunk's billing context correctly configured.

• Create a Voyced Provider, Trunk and Trunk Group.

• Link customer tariffs to the Voyced Trunk Group.

• Use actual calling rates and billing increments.

• Send international telephone numbers without a leading +.

• Configure each DID and its receiving destination.

• Present an authorised outbound caller ID.

• Limit concurrent calls to your Voyced service capacity.

• Use Voyced for normal business conversations, not automated bulk calling.

• Test registration, inbound calls, outbound calls and billing separately.

MagnusBilling supports external SIP providers through its Asterisk trunk and routing system.

With the correct registration credentials, SIP trunk, calling Plan, tariffs and DID destinations, MagnusBilling can use Voyced for incoming and outgoing 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.