Page tree
Skip to end of metadata
Go to start of metadata


This page details the steps necessary to configure an SBC to work properly with D-Series phones and Switchvox.  These same steps can also be applied to D-Series phones operating outside of Switchvox, in a DPMA environment.

It is recommended that your SBC be reset to factory default configuration, and that the default internal SIP profile be deleted before undertaking these steps. Note that factory defaulting your SBC configuration will remove all existing configurations and settings you may have made.

Below is a diagram showing example D-Series phones, an SBC, and a Switchvox system:

 Click here to expand...


The specific configuration steps and examples will be provided below.

Create SIP MESSAGE Routing Plans

D-Series phones have out-of-dialog communication with Switchvox using SIP MESSAGE packets.  These SIP MESSAGE packets are used to provision telephones as well as to exchange application specific information such as presence and parking lot information.  In order to ensure that these SIP MESSAGE packets are marshaled properly between the telephones and Switchvox, we need to create SIP MESSAGE Routing plans.

We will create two Routing Plans: External_swvx and Internal_swvx

It is recommended to save after completing each step, and then apply the configuration after all parameters have been set.

Create and edit External SIP MESSAGE Routing Plan:

From the SBC's Web UI Configuration/Routing/SIP Message Routing:

Routing for External_swvx: →  External_swvx.xml

as seen here:

Create and edit Internal SIP MESSAGE Routing Plan:

From the SBC's Web UI Configuration/Routing/SIP Message Routing:

Routing for Internal_swvx: →  Internal_swvx.xml

as seen here:

Create SIP Advanced Call Routing Plans

Having create routing plans for the SIP MESSAGE packets, we also need routing plans for the calls to/from the phones and Switchvox.  First, we will create an Internal-to-External routing plan, and then we will create an External-to-Internal routing plan.

Create and Edit Internal to External Routing Plan

From the SBC's Web UI Configuration/Routing/Call Routing:

Routing for advanced_internal_to_swvx: →  advanced_internal_to_swvx.xml

***NOTE: Please replace with the Domain the Remote Phones will Register to. ***

as seen here:

Create and Edit External to Internal Routing Plan

From the SBC's Web UI Configuration/Routing/Call Routing:

Routing for advanced_external_to_swvx: → advanced_external_to_swvx.xml

as seen here:

Create SIP Profiles and assign SIP MESSAGE and Call Routing Plans

Now that we have created the SIP MESSAGE and Call Routing plans, we need to create SIP Profiles and assign these routing plans to them.  We will first create an external SIP profile for remote telephones to connect externally, and then an internal SIP profile for telephones to connect internally.

Create and Edit the External profile

From the SBC's Web UI Configuration/Signaling/SIP Profiles:

Summary of external profile:

Assign SIP IP Address in General Section

Set Network Validation ACL to "IP Address" in Authentication section

Ensure all the NAT rules are enabled exactly as shown below. This will ensure phones out on the internet behind NAT have no connectivity issues. Ensure Symmetric Response Routing is set to Force Always

Assign Call Routing Plan, enable and SIP Message routing plan and set Siprelay Allow Method to Message 

Create and Edit the Internal profile

From the SBC's Web UI Configuration/Signaling/SIP Profiles:

Summary of internal profile:

Assign SIP IP Address in General section

Assign Call Routing Plan, enable and SIP Message routing plan and set Siprelay Allow Method to Message 

Create Trunk

Now that SIP MESSAGE and Call Routing and SIP Profiles have ben built, we need to create a SIP Trunk between the SBC and Switchvox.  To do this, we will first set some SIP trunk parameters, and we will then assign the Internal SIP Profile to use this new Trunk.

From the SBC's Web UI Configuration/Signaling/SIP Trunks:

Create and Edit Domain(s)

Having created the Trunk, we now need to create a Domain for the trunk - swvx_trunk.

From the SBC's Web UI Configuration/Signaling/Domains:

In the Domain's configuration, we need to perform three actions:

  1. Enable Forward Registration / Authentication
  2. Set Forward SIP Profile to "Internal_swvx"
  3. Move swvx_trunk to the Used Trunk List

Bind Domain

Next, we need to bind the domain to the External_swvx SIP Profile.

Apply Configuration Changes and Start the SBC

Having completed the above steps, you may now apply the configuration changes and start the SBC.  The SBC is now configured.

Next, you will need to configure the phones from within Switchvox.

Switchvox Configuration

The sections below describe the Switchvox settings involved if you have a Sangoma SBC, and D-Series Phones on remote networks. Switchvox version 7.3 is required. 

Configure Outbound Proxy in Phone Configuration

Within Switchvox, the D-Series phones need to be told to relay their traffic through the SBC. To accomplish this, the phones are configured with an Outbound Proxy which is the address of the SBC.  From within Switchvox, this can be found in Server/Phone Networks.

Local and Internally connected phones do not need the Outbound Proxy definition as they can reach Switchvox directly

For information on configuring the Outbound Proxy setting for phones that aren't attached to Switchvox, please see phone configuration documentation at

For this specific example, one might apply:

<outbound_proxy network_id="1" server="" port="5060" />

to a phone's account element.

Phone Networks

In your Phone Network items, remote networks should be instructed to use the SBC. This way, D-Series Phones will conduct all SIP interactions with the SBC, when the phone starts up on a network that's outside of your local network.

In the Switchvox Administrator web suite, navigate to Server > Phone Networks. For each Phone Network item that is for remote D-Series Phones, provide the SBC's information in the Outbound Proxy settings host and port.

1) In most cases select the network, as this will be the settings for any undefined network. Since remote phones will come from my IP on the internet, then this is the rule to change. Edit this rule. 

2) Next then set the outbound proxy to the public IP address of the SBC. In the example below the SBC's public IP is, replace this with your SBC's public IP. 

Access Control

For each Access Control rule you have defined for a remote network where D-Series Phones will sit:

  • Do not allow SIP service. D-Series Phones on this remote network will interact with the SBC for SIP, not Switchvox. (The phone was instructed to use the SBC when it started up on a remote network defined in Phone Networks.) 
  • Do allow User API service (this is for the apps on the phone such as voicemail, the call log, etc.). And, allow User web portal service if the user will also log into the Switchvox web suite from this network.

In your Access Control rules, include a rule for the SBC. Indicate its network address, and allow SIP service.

Verify Phones Connection via SBC to Switchvox

To verify that the phones are connected to Switchvox correctly, view Server>Connection Status> SIP Phones

From within this screen, you should see successful connection of phones to Switchvox.  Note that phones registering through the SBC will all appear to be registered via the SBC's internal address.

  • No labels