Rate this page:

Routing rules

Routing rules allow developers to launch one or several scenarios, and make and receive calls. When a call arrives to the platform or you make a call via an SDK client, routing rules choose what scenario(s) to execute. Launching a routing rule executes all the attached scenarios.

In this article, you will learn how to create routing rules, attach scenarios, set up patterns for inbound calls, and execute routing rules and therefore, scenarios.

Warning

Without a routing rule you cannot make or receive a call, create a conference and execute any scenario logic.

Contents

Copy URL

Creating a routing rule

Copy URL

In your application, navigate to the Routing tab and either click Create in the center of the screen or New rule in the upper right corner:

Create a rule

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

New rule editor

Enable the Video conference switch if you plan to use the scenario for video conferencing. Without this paramater, 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 matches the pattern, the routing rule executes the attached scenario(s). If the call's destination does not match the pattern, the attached scenario(s) does not execute and the call passes to the next routing rule.

The application checks the routing rules from top to bottom. The higher routing rules have higher priority. When the call's destination matches one of the rules, the rule executes and the application ignores further rules, so only one rule executes.

Note

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

The Pattern field uses regular expressions to create masks for phone numbers or usernames. There are most common expressions:

  • .* 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.

You can read more on how to build a regular expression on Wikipedia.

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

You can attach multiple scenarios to one rule. In this case, the rule executes all the attached scenarios one by one in one context, allowing code reuse. This allows you to write all the functions in one scenario, and use them in another scenario.

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

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

Checking a routing rule

Copy URL

To check if a certain phone number or a username matches any rule's pattern, click Testing tools at the top right corner, and choose Rule checker.

Rule checker

Enter a phone number or username and click Test. If the entered data matches any rule, the rule and its pattern appear below.

Additionally, you can use the integrated Softphone to make calls to your applications. To use it, click Testing tools at the top right corner, and choose Softphone. To make calls via the softphone, you need to authorize with the username and password.

Launching a routing rule

Copy URL

There are several ways of launching a scenario.

  • An inbound call to the platform. If the call's destination matches any rule's pattern, the corresponding scenario(s) launches and the call processes according to the scenario.

  • An outbound call from an SDK also creates an inbound call to the platform (a call leg). If the destination property of the SDK's call method matches any rule's pattern, the corresponding scenario(s) launches.

  • Management API methods. Use the StartScenarios to launch rule for a common scenario, such as audio/video calls, or an audio conference; or the StartConference to launch a video conference.

  • Manual launch from the control panel. In your application, navigate to the Routing tab, choose the necessary routing rule to launch and click the Run button.

Frequently asked questions

Copy URL

Q: Can I execute a scenario without a routing rule?
A: No. Routing rules are necessary to execute inbound and outbound scenarios.

Q: Can I attach more than one scenario to a routing rule?
A: Yes. If you attach more than one scenario to a routing rule, they execute in one context, allowing code reuse. This allows developers to write all the functions in one scenario, and use them in another scenario.

Q: Do patterns work for outbound calls?
A: No. The patterns work for inbound calls only. For outbound calls, it is enough to create a rule and attach a scenario.

Q: Do pattern work for SIP calls?
A: Yes, patterns also work for SIP usernames. You can create a special prefix or format for SIP usernames and route them to a specific scenario.

Q: Does a pattern check the caller ID, or the destination number?
A: The destination number. The rule does not check matching of your CallerID.

Q: What if a phone number matches several rule patterns?
A: Only the first rule will be executed. The application checks the number against all the rules from top to bottom, and when a suitable rule is found, it stops checking the number.

Q: What if I do not enable the "Video conference" switch in the routing rule settings?
A: All attempts to start a video conference with this rule will fail with an error.

Q: What if I enable the "Video conference" switch in the routing rule settings but will make only audio calls?
A: The audio calls will work without errors, but they will be billed as video conference.

Q: How can I pass custom data to the scenario?
A: If you start a scenario via Management API, pass the data to the script_custom_data parameter. If you start the scenario manually via the control panel, pass the data to the "Custom data" window.

Q: How do I setup two different rules for inbound and outbound calls?
A: You can create a rule for inbound calls with the .* pattern (accepts all calls) and place it above the rule for outbound calls. As the inbound calls rule will intercept all the calls, you can launch the rules below the inbound calls rule only manually, for example with Management API.

Q: How do I prioritize the routing rules?
A: Reorder them. The highest rule has the highest priority.