Rate this page:

Connecting to SIP trunk

With Voximplant, you can connect the Ultravox LLM service to an existing SIP telephony server. This allows you to use Ultravox AI assistants to handle your calls and assist your customers right from your existing infrastructure.

Voximplant acts as a gateway, managing connection with Ultravox via WebSockets and making/receiving calls via SIP.

Gateway

Follow the steps below to connect Ultravox to your SIP PBX server.

Create a Voximplant application

Copy URL

To create an application, log in to your Voximplant account or create a new one. Then, navigate to the application section from the upper left corner of the page. Click New application in the upper right corner or Create at the bottom of the page.

Create an application

This opens a new application editor window where you can set it up and save by clicking Create. The newly created app appears in the application list. To modify its name, icon, or description, click the three dots menu and select Edit.

Edit an application

You can learn more about Voximplant applications and their sections in the Getting started → Applications section of this documentation.

Create scenarios within the application

Copy URL

Scenarios in Voximplant are JavaScript documents within a Voximplant application, where you can implement logic processing calls and messages.

To create a scenario, open your existing or newly created application application, and select Scenarios on the left menu, and click on the plus icon to create a new scenario. Give it a name.

Create a scenario

This opens a new tab in the online IDE on the right, where you can write your code. If needed, you can rename the scenario or modify the source code later.

You can learn more about scenarios and their best practice tips in the Getting started → Scenarios section of this documentation.

Utilize our ready-to-use scenarios

Copy URL

To connect your SIP PBX with the Ultravox LLM, we prepared two ready-to use scenarios for incoming and outgoing calls.

Please note

We have hidden sensitive information in these scenarios, such as API keys, with placeholders. Please, replace the placeholders with your actual Ultravox credentials.

Here is the incoming scenario for processing incoming calls:

Incoming calls scenario

Incoming calls scenario

Here is the outgoing scenario for processing outgoing calls:

Outgoing calls scenario

Outgoing calls scenario

The outgoing scenario accepts the customData parameter in the following format:

{"callerid":"16503333333", "number":"16504444444"}

You can provide this parameter when launching the scenario via a routing rule or StartScenarios Management API method.

Create routing rules

Copy URL

Routing rules in a Voximplant applications define when and on what conditions to launch existing scenarios. When an incoming call arrives or you make call via your SIP PBX server, a routing rule decides which scenario to launch.

To create a routing rule, navigate to the Routing tab in your application. You can either click Create in the center of the screen or New rule in the upper right corner:

Create a rule

This opens the New rule editor, where you can specify the rule name, properties, and attach one or more scenarios:

New rule editor

If you intend to use the scenario for video conferencing, enable the Video conference switch. Without this parameter, all video conferences fail with an error.

Warning

With the Video conference switch enabled, all the calls made via SDKs or softphones are billed as video conferences.

The Pattern field checks if the call’s destination (the dialed number or username specified in the e.destination property of the incoming call) matches any rule’s pattern. If the call’s destination aligns with the pattern, the attached scenario(s) are executed. If the call’s destination doesn’t match the pattern, the attached scenario(s) remain inactive, and the call proceeds to the next routing rule.

The application systematically evaluates the routing rules from top to bottom, with higher-priority rules taking precedence. When the call’s destination matches one of the rules, the rule is executed, and the application disregards any subsequent rules, ensuring that only one rule is executed at a time.

Note

If the destination phone number meets several rules' patterns, only the first rule executes.

The Pattern field employs regular expressions to create masks for phone numbers or usernames. Common expressions include:

  • .* means any quantity of any symbols, so all the numbers or usernames match the rule.

  • +?[1-9]\d{1,14} matches any phone number

  • 123.+ matches 1234, 12356, etc., and so on.

For more information on building regular expressions, refer to Wikipedia.

The Available scenarios dropdown list enables you to attach one or more scenarios to execute when the rule is triggered.

You can attach multiple scenarios to a single rule. In this scenario, the rule executes all the attached scenarios sequentially within a single context, promoting code reuse. This allows you to encapsulate all the functions within a scenario and utilize them in another scenario.

You can view all the attached scenarios in the Assigned scenarios field.

After specifying all the settings, click the Create rule button to create a rule.

You can learn more about routing rules and ways to launch them in the Getting started → Routing rules section of this documentation.

Setup your SIP PBX server

Copy URL

Voximplant handles the incoming calls, launching the incoming scenario automatically via a specified routing rule and its pattern.

To handle the outgoing calls, you can either configure the outgoing routing rule to a specific pattern according to your existing SIP system, passing the number to call and the caller ID to the routing rule (see the Utilize our ready-to-use scenarios section above).

Or you can manually launch the outbound scenario calling the StartScenarios Management API method from your system and passing the number and caller ID parameters as it is explained above.