Ribbon SBC Edge Configuration with OBS (UDP)

 

Document Overview

This document provides a configuration guide for Ribbon SBC Edge Series (Session Border Controller) when connecting to OBS Business Talk (BTIP) SIP trunk.

This configuration guide supports features given in the BTIP North Profile Compliancy and Compliance tests documents.

Ribbon has configured the BTIP side in a such manner it doesn’t matter the 3rd party system connected on the SBC.

The SBC Edge is certified by Orange Business Services as a ‘certified Enterprise SBC’.

• For additional information on OBS, please visit https://www.orange-business.com/en/products/business-talk   
• For additional information on Ribbon SBC Edge, please visit https://ribboncommunications.com/ 

Introduction

The interoperability compliance testing focuses on verifying inbound and outbound call flows between Ribbon SBC Edge and OBS.

Audience

This is a technical document intended for telecommunications engineers with the purpose of configuring both the Ribbon SBC and the third-party product. There will be steps that require navigating the third-party and the Ribbon SBC Command Line Interface (CLI). Understanding the basic concepts of TCP/UDP, IP/Routing, and SIP/RTP are also necessary to complete the configuration and for troubleshooting, if necessary.

Requirements

The following equipment and software were used for the sample configuration provided:

Reference Configuration

The following reference configuration shows the connectivity between the third-party and Ribbon SBC Edge.

Support

For any questions regarding this document or the content herein, please contact your maintenance and support provider.

 

SIP Trunk

SIP trunks allow administrators to connect the Cisco Unified Communications Manager to external devices such as SIP gateways, SIP Proxy Servers, Unified Communications applications, remote clusters, or a Session Management Edition. Ribbon uses the SIP trunk to connect the CUCM to the Ribbon SBC SWE-Lite.

Login to the CUCM as an admin user and go to the following path: Device > Trunk

Click on the Add New icon to add a new Trunk.

Set the trunk configuration as shown in the figure below.

After clicking the Next button, a new screen will be shown. Set the device (trunk) name, the profiles, and the destination IP address used by the trunk. Below is an example.

The IP address on the SWE-Lite towards the CUCM is 192.168.191.216.

Click the Save button.

Route Group

In Cisco Unified Communications Manager, use the Call Routing > Route/Hunt > Route Group menu path to configure route groups.

A route group allows you to designate the order in which gateways and trunks are selected. It allows you to prioritize a list of gateways and ports for outgoing trunk selection.

Click on the Add New icon to add a Route Group.

Specify the Route Group name and select the devices that are going to be used by this Route Group.

In the example below, the device selected is OrangeSBCLite, created in SIP Trunk above.

Click the Save button. 

Route List

In Cisco Unified Communications Manager Administration, use the Call Routing > Route/Hunt > Route List menu path to configure route lists.

A route list associates a set of route groups in a specified priority order. The route list associates the route groups with one or more route patterns and determines the order in which those route groups are accessed. The order controls the progress of the search for available devices for outgoing calls.

A route list can contain only route groups. Each route list should have at least one route group. Each route group includes at least one device.

Click on the Add New icon to add a Route List.

In the next screen, specify the Route List name, description, and select the Cisco Unified Communications Manager Group used by the Route List.

Click the Save button.

After saving, you will be able to add the Route Group to the Route List.

Click the Add Route Group icon to add the Route Group to the Route List.

Click the Save button. At this point the new Routing List has been created.

Route Pattern

In Cisco Unified Communications Manager Administration, use the Call Routing > Route/Hunt > Route Pattern menu path to configure route patterns.

A route pattern comprises a string of digits (an address) and a set of associated digit manipulations that can be assigned to a route list or a gateway. Route patterns provide flexibility in network design. They work in conjunction with route filters and route lists to direct calls to specific devices and to include, exclude, or modify specific digit patterns.

Click the Add New icon to add a Route Pattern.

In the next screen, specify the Route Pattern, Description, and Gateway/Route List.

Click the Save button. At this point the new Route Pattern has been created.

All traffic matching this route pattern will be routed through the route list Orange_SBC_Lite.

SBC SWE-Lite Configuration

The following new configurations are included in this section:

1. System Settings
2. Network Interfaces
3. Static Routes
4. SIP Profiles
5. SIP Server Tables
6. Message Manipulations
7. Media Profiles
8. Media Lists
9. Q.850 to SIP Override Table
10. Signaling Groups
11. Transformations Tables
12. Call Routing Tables

System Settings

The System > Node-Level settings menu path allows you to set the Host name, the Domain name service, and Time management. Below is an example of the system settings.

Network Interfaces

The Networking Interfaces > Logical Interfaces menu path allows you to configure the IP addresses (both IPv4 and IPv6) for the Ethernet ports and VLANs.

The SBC SWe Lite supports five system-created logical interfaces (known as Administrative IP, Ethernet 1 IP, Ethernet 2 IP, Ethernet 3 IP, and Ethernet 4 IP). In addition to the system created logical interfaces, the Ribbon SBC SWe supports user-created VLAN logical sub-interfaces.

Administrative IP

The SBC SWe Lite system supports a logical interface called the Admin IP (Administrative IP, also known as the Management IP). A Static IP or DHCP is used for running Initial Setup of the SBC SWe Lite system.

Ethernet IP

The SBC SWe Lite system has four logical interfaces. In most deployments, one of these logical interfaces (typically Ethernet 1 IP) is assigned an IP address used for transporting all the VOIP media packets (e.g., RTP, SRTP) and all protocol packets (e.g., SIP, RTCP, TLS). DNS servers in the customer's network should map the SBC SWe Lite system hostname to this IP address. The hostname, or these IP addresses, may be used by UC-enabling systems such as SIP-phones, IP-PBX and Microsoft Lync Servers and for accessing the SBC SWe Lite WebUI.

In the default software, Ethernet 1 IP is enabled and an IPv4 IP address is acquired via a connected DHCP server. This IP address is used for performing Initial Setup on the SBC SWe Lite. See Running Initial Setup for more information. The default IP address for the logical interface named Ethernet 2 IP is 192.168.129.2. After initial configuration, you may configure this logical interface using Settings or Tasks tabs in the WebUI.

Below are examples of the Admin and Ethernet IP interfaces configuration.

Static Routes

The Protocols > IP > Static Route Table menu path allows you to manually specify the next hop routers used to reach other networks. This is also where you specify the default routes for the connected IP networks (which use 0.0.0.0 as the Destination and Mask).

To add a new Static Route, click on the plus (+) icon.

• Destination IP

Specifies the destination IP Address

• Mask

Specifies the network mask of the destination host or subnet. If the 'Destination IP Address' field and 'Mask' field are both 0.0.0.0, the static route is called 'default static route'.

• Gateway

Specifies the IP Address of the next-hop router to use for this Static Route.

• Metric

Specifies the cost of this route and indirectly specifies the preference of the route. Lower values indicate more preferred routes. Typical value is 1 for most static routes, indicating that static routes are preferred to dynamic routes.

SIP Profiles

The SIP > SIP Profiles menu path controls how the SBC Edge communicates with SIP devices. They control important characteristics such as: session timers, SIP header customization, SIP timers, MIME payloads, and option tags.

To add a new SIP Profile, click on the plus (+) icon.

OBS SIP Profile Configuration

CUCM SIP Profile Configuration

Ventafax SIP Profile Configuration

SIP Server Tables

The SIP > SIP Server Table menu path contains information about the SIP devices connected to the SBC Edge. The entries in the tables provide information about the IP Addresses, ports, and protocols used to communicate with each server. The Table Entries also contain links to counters that are useful for troubleshooting. The SIP Server supports either an FQDN or IP Address (V4 or V6).

OBS SIP Server Table

BTIP

To add a new SIP Server Table, click on the plus (+) icon.

Set a Description and select SIP Server.

Select the SIP server table that has just been created.

Click on the Create SIP Server > IP/FQDN icon to add a new SIP Server.

BTalk

To add a new SIP Server Table, click on the plus (+) icon.

Set a Description and select SIP Server.

Select the SIP server table that has just been created.

Click on the Create SIP Server > IP/FQDN icon to add a new SIP Server.

CUCM SIP Server Table

To add a new SIP Server Table, click on the plus (+) icon.

Set a Description and select SIP Server.

Select the SIP server table that has just been created.

Click on the Create SIP Server > IP/FQDN icon to add a new SIP Server.

The figure below depicts the CUCM SIP Server Configuration.

Ventafax SIP Server Table

To add a new SIP Server Table, click on the plus (+) icon.

Set a Description and select SIP Server.

Select the SIP server table that has just been created.

Click on the Create SIP Server > IP/FQDN icon to add a new SIP Server.

The figure below depicts the Ventafax SIP Server Configuration.

Message Manipulations

The SIP > Message Manipulation menu path is used to manipulate the incoming or outgoing messages. This feature is intended to enhance interoperability with different vendor equipment and applications, and for correcting any fixable protocol errors in SIP messages on the fly without any changes to firmware/software.

Although SIP is considered a mature protocol, there are still devices running old firmware and systems that interpret the standard in a non-conforming way. In addition, there are cases where a compliant message may be modified to adapt to an application specific requirement.

This capability consists of two components, condition rules and message rules. Condition rules provide a means to identify which messages and what components in the message must be present before any modifications are performed. For example, I want to modify all INVITE messages with a from uri host of "ribbon.net".

The message rule does the actual modification of a message. Once the conditions of a rule have been met, the message rule(s) are applied. Continuing with the example above, a message rule may change the from uri display name to "Ribbon".

Condition Rule Table

Condition rules are simple rules that apply to a specific component of a message (e.g., diversion.uri.host, from.uri.host, etc.) the value of the field specified in the Match Type list box can be matched against a literal value, token, or REGEX.

The Condition Rule Table stores a collection of all the user created Condition Rules.

Match_Content-Type

This Condition Rule matches only if SG User Value 1 = application/sdp. This condition is created to identify whether the SDP is present or not in the SIP messages.

To add a new Condition Rule, go to SIP > Message Manipulation > Condition Rule Table menu path and click on the plus (+) icon.

Set the new entry as per the following picture.

Match_Anonymous

This Condition Rule matches only if from.displayname = Anonymous

It compares whether the display name that is in the From header is equal to Anonymous.

To add a new Condition Rule, go to SIP > Message Manipulation > Condition Rule Table menu path and click on the plus (+) icon.

Set the new entry as per the following picture.

Message Rule Tables

Message Rule Tables are simply sets of Condition Rules and are applied in SIP Signaling Groups when Message Manipulation is enabled.

The Message Rule Tables collect SIP Messages Manipulations Rules that are applied according to the Message Type set in the Message Rule Tables. The following tables are defined to set the format requested by OBS.

Add_P-Early-Media Table

This table collects the rules that are used to add the P-Early-Media header in the SIP 180 and SIP 183 responses.

To add a new Message Rule Table, go to the SIP > Message Manipulation > Message Rule Tables menu path and click on the plus (+) icon.

Set the new entry as per the following picture.

Add_P-Early-Media Rules

Add P-Early-Media supported

To add a new Message Rule, go to the left menu path and click on the Add_P-Early-Media table you created, then click on the Create Rule > Header Rule icon.

Set the new entry as per the following picture.

Once you select Add in the Header Action field, the bottom section will change its options.

Select Add in the Header Value field and click on the Add/Edit icon.

Once you click on the Add/Edit icon, a popup screen appears.

Set the configuration as per the following picture.

Click on the Apply icon to save the changes.

Del_P-Early-Media

To add a new Message Rule, go to the left menu path and click on the Add_P-Early-Media table you created, then click on the Create Rule > Header Rule icon.

Set the new entry as per the following pictures.

For the Condition Expression field, click on the Add/Edit icon. A popup screen appears. Set the configuration as per the following picture.

Click on the Apply icon to save the changes.

Add_P-Early-Media sendrecv

To add a new Message Rule, go to the left menu path and click on the Add_P-Early-Media table you created, then click on the Create Rule > Header Rule icon.

Set the new entry as per the following pictures.

For the Condition Expression field, click on the Add/Edit icon. A popup screen appears. Set the configuration as per the following picture.

Once you select Add in the Header Action field, the bottom section will change its options. Select Add in the Header Value field and click on the Add/Edit icon.

Once you click on the Add/Edit icon, a popup screen appears. Set the configuration as per the following picture.

Click on the Apply icon to save the changes.

Store_Content-Type Table

This table collects the rule that is used to store the Content-Type value in the SG User Value 1. It applies only to 180 and 183 respond messages.

To add a new Message Rule Table, go to the SIP > Message Manipulation > Message Rule Tables menu path and click on the plus (+) icon.

Set the new entry as per the following picture.

Store_Content-Type Rules

Store Content-Type

To add a new Message Rule, go to the left menu path and click on the Store_Content-Type table you created, then click on the Create Rule > Header Rule icon.

Set the new entry as per the following picture.

Once you select Modify in the Header Action field, the bottom section will change its options. Select Copy Value to in the Header Value field and click on the Add/Edit icon.

Once you click on the Add/Edit icon, a popup screen appears. Set the configuration as per the following picture.

Click on the Apply icon to save the changes.

Store_User-Agent Table

This table collects the rules that are used to store the User-Agent and Server headers values sent by the IPPBX.

To add a new Message Rule Table, go to the SIP > Message Manipulation > Message Rule Tables menu path and click on the plus (+) icon.

Set the new entry as per the following picture.

Store_User-Agent Rules

Store_User-Agent_Value

To add a new Message Rule, go to the left menu path and click on the Store_User-Agent table you created, then click on the Create Rule > Header Rule icon.

Set the new entry as per the following picture.

Once you select Modify in the Header Action field, the bottom section will change its options. Select Copy Value to in the Header Value field and click on the Add/Edit icon.

Once you click on the Add/Edit icon, a popup screen appears. Set the configuration as per the following picture.

Click on the Apply icon to save the changes

Store_Server_Value

To add a new Message Rule, go to the left menu path and click on the Store_User-Agent table you created, then click on the Create Rule > Header Rule icon.

Set the new entry as per the following picture.

Once you select Modify in the Header Action field, the bottom section will change its options. Select Copy Value to in the Header Value field and click on the Add/Edit icon.

Once you click on the Add/Edit icon, a popup screen appears. Set the configuration as per the following picture.

Click on the Apply icon to save the changes.

OBS_SIP_Profile_Adaptation_01 Table

This table collects rules used to set the format requested by OBS. It applies to all messages.

To add a new Message Rule Table, go to the SIP > Message Manipulation > Message Rule Tables menu path and click on the plus (+) icon.

Set the new entry as per the following picture.

OBS_SIP_Profile_Adaptation_01 Rules

Remove_SGID_From_Header

To add a new Message Rule, go to the left menu path and click on the OBS_SIP_Profile_Adaptation_01 table you created, then click on the Create Rule > Header Rule icon.

Set the new entry as per the following picture.

Once you select Modify in the Header Action field, the bottom section will change its options. Select Ignore in the Header Value field and click the plus (+) icon in the Header Parameters section.

Once you click on the plus (+) icon, a popup screen appears. Set the configuration as per the following picture.

Click on the Apply icon to save the changes.

Remove_SGID_To_Header

To add a new Message Rule, go to the left menu path and click on the OBS_SIP_Profile_Adaptation_01 table you created, then click on the Create Rule > Header Rule icon.

Set the new entry as per the following picture.

Once you select Modify in the Header Action field, the bottom section will change its options. Select Ignore in the Header Value field and click the plus (+) icon in the Header Parameters section.

Once you click on the plus (+) icon, a popup screen appears. Set the configuration as per the following picture.

Click on the Apply icon to save the changes.

Modify_User-Agent_Header

To add a new Message Rule, go to the left menu path and click on the OBS_SIP_Profile_Adaptation_01 table you created, then click on the Create Rule > Header Rule icon.

Set the new entry as per the following picture.

Once you select Modify in the Header Action field, the bottom section will change its options. Select Modify in the Header Value field and click on the Add/Edit icon.

Once you click on the Add/Edit icon a popup screen appears. Set the configuration as per the following picture.

Click on the Apply icon to save the changes.

Modify_Server_Header

To add a new Message Rule, go to the left menu path and click on the OBS_SIP_Profile_Adaptation_01 table you created, then click on the Create Rule > Header Rule icon.

Set the new entry as per the following picture.

Once you select Modify in the Header Action field, the bottom section will change its options. Select Modify in the Header Value field and click on the Add/Edit icon.

Once you click on the Add/Edit icon, a popup screen appears. Set the configuration as per the following picture.

Click on the Apply icon to save the changes.

Modify_Allow_header

To add a new Message Rule, go to the left menu path and click on the OBS_SIP_Profile_Adaptation_01 table you created, then click on the Create Rule > Header Rule icon.

Set the new entry as per the following picture.

Once you select Modify in the Header Action field, the bottom section will change its options. Select Modify in the Header Value field and click on the Add/Edit icon.

Once you click on the Add/Edit icon, a popup screen appears. Set the configuration as per the following picture.

Click on the Apply icon to save the changes.

OBS_SIP_Profile_Adaptation_02 Table

This table collects rules used to set the format requested by OBS. It applies to all messages.

To add a new Message Rule Table, go to the SIP > Message Manipulation > Message Rule Tables menu path and click on the plus (+) icon.

Set the new entry as per the following picture.

OBS_SIP_Profile_Adaptation_02 Rules

Modify_PAI

To add a new Message Rule, go to the left menu path and click on the OBS_SIP_Profile_Adaptation_02 table you created, then click on the Create Rule > Header Rule icon.

Set the new entry as per the following picture

Once you select Modify in the Header Action field, the bottom section will change its options. Click on the arrow next to Header Value, then click on the arrow next to URI . Select Modify in the URI Host field and click on the Add/Edit icon

Once you click on the Add/Edit icon, a popup screen appears. Set the configuration as per the following picture.

Click on the Apply icon to save the changes.

Add plus P-Asserted-Identity

To add a new Message Rule, go to the left menu path and click on the OBS_SIP_Profile_Adaptation_02 table you created, then click on the Create Rule > Header Rule icon.

Set the new entry as per the following picture

Once you select Modify in the Header Action field, the bottom section will change its options. Select Modify in the Header Value field and click on the Add/Edit icon.

Once you click on the Add/Edit icon, a popup screen appears. Set the configuration as per the following picture.

Click on the Apply icon to save the changes.

Modify_From_Anonymous

To add a new Message Rule, go to the left menu path and click on the OBS_SIP_Profile_Adaptation_02 table you created, then click on the Create Rule > Header Rule icon.

Set the new entry as per the following picture.

Click on the Add/Edit icon next to Condition Expression to set the Message Rule Condition.

Set the Message Rule Condition as per the following picture

Once you select Modify in the Header Action field, the bottom section will change its options. Select Modify in the Header Value field and click on the Add/Edit icon.

Once you click on the Add/Edit icon, a popup screen appears. Set the configuration as per the following picture.

Click on the Apply icon to save the changes.

Modify_Diversion

To add a new Message Rule, go to the left menu path and click on the OBS_SIP_Profile_Adaptation_02 table you created, then click on the Create Rule > Header Rule icon.

Set the new entry as per the following picture

Once you select Modify in the Header Action field, the bottom section will change its options. Select Modify in the Header Value field and click on the Add/Edit icon.

Once you click on the Add/Edit icon, a popup screen appears. Set the configuration as per the following picture.

Click on the plus (+) icon in the Header Parameters section.

Once you click on the plus (+) icon, a popup screen appears. Set the configuration as per the following picture.

Click on the Apply icon to save the changes.

Media Profiles

The Media > Media Profiles menu path allows you to specify the individual voice and fax compression codecs and their associated settings, for inclusion in a Media List. Different codecs provide varying levels of compression, allowing one to reduce bandwidth requirements at the expense of voice quality.

To create a new Media Profile, go to Media > Media Profiles on the left menu path.

G.722

Click on the Create Media Profile > Voice Codec Profile icon.

Set the new G.722 codec as per the following picture.

Click on the Apply icon to save the changes.

Default G711A

Click on the Create Media Profile > Voice Codec Profile icon.

Set the G.711 A-law codec as per the following picture.

Click on the Apply icon to save the changes.

G.729

Click on the Create Media Profile > Voice Codec Profile icon.

Set the G.729 codec as per the following picture.

Click on the Apply icon to save the changes.

Default G711U

Click on the Create Media Profile > Voice Codec Profile icon.

Set the  G.711 U-law codec as per the following picture.

Click on the Apply icon to save the changes.

T38

Click on the Create Media Profile > Fax Codec Profile icon.

Set the T.38 codec as per the following picture.

Click on the Apply icon to save the changes.

Media Lists

The Media > Media List menu path allows you to specify a set of codecs and fax profiles that are allowed on a given SIP Signaling Group. They contain one or more Media Profiles, which must first be defined in Media Profiles. These lists allow you to accommodate specific transmission requirements, and SIP devices that only implement a subset of the available voice codecs.

CUCM_MediaList

To add a Media List, go to Media > Media List on the left menu path.

Click on the plus (+) icon to add a new entry.

Configure the new entry as per the following picture.

Click on the Apply icon to save the changes.

Orange_MediaList-UDP

To add a Media List, go to Media > Media List on the left menu path.

Click on the plus (+) icon to add a new entry.

Configure the new entry as per the following picture.

Click on the Apply icon to save the changes.

Q.850 to SIP Override Table

SIP and ISDN use different response messages to communicate why a call failed or could not be connected (Q.850 for ISDN and SIP Responses for SIP). By default, the SBC Edge uses RFC 4497 to map these to each other. The Telephony Mapping Tables > Q.850 to SIP Override Tables menu path allows you to override one or more of these mappings to a different message, which is useful for inter-operating with nonstandard equipment.

To add a new Q.850 to SIP Override Table, go to Telephony Mapping Tables > Q.850 to SIP Override Tables on the left menu path.

To add a new Q.850 to SIP Override Table, click on the plus (+) icon.

Set the Description as per the following picture.

On the left menu path, click on the OBS Mapping Table.

To add a new entry click on the plus (+) icon.

Configure the new entry as per the following picture.

Click on the Apply icon to save the changes.

Signaling Groups

Signaling groups allow telephony channels to be grouped together for the purposes of routing and shared configuration. They are the entity to which calls are routed, as well as the location from which Call Routes are selected. They are also the location from which Tone Tables and Action Sets are selected.

From-To_CUCM

To add a new Signaling Group, go to the Signaling Groups menu path.

Set the new entry as per the following picture.

Click on the Apply icon to save the changes.

From-To_OrangeBTIP

To add a new Signaling Group, go to Signaling Groups menu path.Set the new entry as per the following picture.

Click on the Apply icon to save the changes.

From-To_OrangeBtalk

To add a new Signaling Group, go to Signaling Groups menu path.Set the new entry as per the following picture.Click on the Apply icon to save the changes.

Transformations Tables

Transformation Tables facilitate the conversion of names, numbers and other fields when routing a call. They can, for example, convert a public PSTN number into a private extension number, or into a SIP address (URI). Every entry in a Call Routing Table requires a Transformation Table, and they are selected from there.

CUCM_Prefixes

To add a new Transformation Table, go to Call Routing > Transformation on the left menu path.

Set the Description as per the following picture.

On the left menu path, click on the CUCM_Prefixes Table.

To_CUCM

To add a new entry click on the plus (+) icon.

Configure the new entry as per the following picture.

Click on the Apply icon to save the changes.

Orange_Btalk

To add a new Transformation Table, go to Call Routing > Transformation on the left menu path.

Set the Description as per the following picture.

On the left menu path, click on the Orange_Btalk Table.

Add plus calling number

To add a new entry click on the plus (+) icon.

Configure the new entry as per the following picture.

Click on the Apply icon to save the changes.

To_Btalk

To add a new entry click on the plus (+) icon.

Configure the new entry as per the following picture.

Click on the Apply icon to save the changes.

Orange_BTIP

To add a new Transformation Table, go to Call Routing > Transformation on the left menu path.

Set the Description as per the following picture.

On the left menu path, click on the Orange_BTIP Table.

Add plus Calling number

To add a new entry click on the plus (+) icon.

Configure the new entry as per the following picture.

Click on the Apply icon to save the changes.

To_BTIP

To add a new entry click on the plus (+) icon.

Configure the new entry as per the following picture.

Click on the Apply icon to save the changes.

Call Routing Tables

Call Routing allows calls to be carried between signalling groups, thus allowing calls to be carried between ports, and between protocols. Routes are defined by Call Routing Tables, which allow for flexible configuration of which calls are carried, and how they are translated. These tables are one of the central connection points of the system, linking Transformation Tables, Message Translations, Cause Code Reroute Tables, Media Lists and Signaling Groups.

To_Private

To add a new Call Routing Table, go to Call Routing > Call Routing Table on the left menu path.

Set the Description as per the following picture.

On the left menu path, click on the To_Private Table.

To_CUCM

To add a new entry click on the plus (+) icon.

Configure the new entry as per the following picture.

Click on the Apply icon to save the changes.

To_Orange

To add a new Call Routing Table, go to Call Routing > Call Routing Table on the left menu path.

Set the Description as per the following picture.

On the left menu path, click on the To_Orange Table.

To_OrangeBtalk

To add a new entry click on the plus (+) icon.

Configure the new entry as per the following picture.

Click on the Apply icon to save the changes.

To_OrangeBTIP

To add a new entry click on the plus (+) icon.

Configure the new entry as per the following picture.

Click on the Apply icon to save the changes.