Configuring a SIP Trunk

A SIP gateway converts traditional TDM circuits to VoIP when direct SIP-trunking is not available from the carrier or switch. Prophecy is a pure SIP VoIP platform. To connect to TDM networks, Voxeo customers typically utilize standards-based SIP gateways from vendors such as Cisco and AudioCodes. These gateways perform the aforementioned TDM-to-VoIP conversion.

While the Prophecy Platform natively connects with nearly all SIP providers, gateways, and devices, Voxeo has performed extensive interoperability testing with SIP gateways from Cisco and uses these devices in its distributed hosted environment.

Voxeo also offers a turnkey Prophecy IVR Server and Prophecy SIP Appliance, which include a built-in POTS- or TDM-to-SIP gateway from AudioCodes or Cisco.

SIP Gateway Compatibility Rules

If you are looking to use a different gateway please ensure it includes support for:

Note: This documentation is for configuring the SIP gateway only. For more information on configuring registration with a VOIP provider, please see the VOIP Integration documentation.

Configuring a SIP Trunk

In order to make outbound calls, Prophecy must first be configured with a SIP Gateway. SIP Trunking - IP based authentication - is the preferred method for outbound dialing, however you can configure Prophecy to register with a VoIP provider. Go here for more info on VoIP integration.

Creating a new server

In order for Prophecy to communicate with the gateway, we'll need to tell it where the gateway is and what service it provides. Login to Prophecy Commander (http://localhost:9996) and select the Servers tab. Click New to configure a new server and fill in the details:

Site - The site this server belongs to - generally will be left at Default except for multi-site deployments

Group - The group the server belongs to - for a single gateway, select Default under Not Selected Groups and click the right arrow

To specify this server provides the gateway service, select the Configuration tab and click Add. Expand Gateway, select VoIP Gateway (v1.0) and click OK. Click Save on the right side to save the new server.

Mapping the new resource

To tell Prophecy to use the new gateway we created, we'll need to map it to the default Gateway resource. Navigate to the Virtual Platforms tab and select the Default virtual platform.

At the bottom, select the resource named * with the Role of Gateway

In the dialog box, click new and enter the following information:

Group - The group the service belongs to - for our single gateway implementation, we'll select Default

Service - Select VoIP Gateway 1.0 - Core

Priority - For a single resource, this will always be 1

Click OK twice and then Save. In a single server setup, this data should propagate immediately. For a multi-server communities, it may take a couple of minutes for all servers to update their DNS entries.

Configuring a failover SIP gateway

To enable a failover gateway, we'll just need to create a new gateway in the same manner as before. However, this time we will not add it to the Default group. Instead, we'll create two new groups under the Groups tab - one for the primary gateway and one for the failover gateway. Groups allow us to segregate services for finer grained control of their usage.

Here I've created two new groups, Primary SIP Gateways and Backup SIP Gateways and created a second SIP Gateway server. SIP Gateway 1 is then added exclusively to the Primary group and SIP Gateway 2 to the Backup group. Neither server should be a member of any other group, including Default.

Migrate back to the Virtual Platforms tab and open the Gateway role for the Default platform. Clicking New should now show us two different groups to add - add the Primary group with priority 1 and the Backup group with priority 2. Click OK twice and click Save. Prophecy will now route around the Primary gateway(s) if the initial call attempt fails.

Configuring load-balanced SIP gateways

Prophecy will load-balance any resources that share the same priority. An easy way to load-balance SIP gateways is to put all those you wish to load-balance in the same group, then set that group as priority 1 in the Gateway role for your virtual platform. You can also assign each individual gateway to a new group, setting the priority of each group to 1 in the virtual platform. In the below example, I've re-used our two groups, Primary and Backup, and added a second gateway server to each group. Using our previous virtual platform mapping, this setup with load-balance between both primary gateways. If the outbound call attempt fails, it will load-balance between the two backup gateways.

The Dialogic and Sangoma models are internal PCI cards. The Audiocodes devices are external devices. The MP-11x series are similar in size to a residential broadband router. The MP-240 is a half-depth 1U rack-mountable enclosure. The Audiocodes devices offer a number of High Availability features such as PSTN fallback, alternate routing, and Standalone Survivability that the PCI devices cannot.

↑ ab Certain versions of Paraxip only support certain versions of Dialogic drivers. Dialogic System Software SR5.11 should only be used with Paraxip Gateway 2.1.4. Dialogic System Software SR6.0red148 should be used with Paraxip 2.2.5. Check Add/Remove Programs > Dialogic System Software > Support Information for the software version. The driver version in Device Manager will always list 1.0.0 for SR6.0 and will show up under Other Devices in SR5.11 with no driver version.