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’.
The interoperability compliance testing focuses on verifying inbound and outbound call flows between Ribbon SBC Edge and OBS.
This is a technical document intended for telecommunications engineers for configuring both the Ribbon SBC and the third-party product. Users will perform steps to navigate the third-party products as well as the Ribbon SBC Command Line Interface (CLI). Understanding the basic concepts of TCP/UDP, IP/Routing, and SIP/RTP is also essential for completing the configuration and for troubleshooting, if necessary.
This configuration guide is offered as a convenience to Ribbon customers. The specifications and information regarding the product in this guide are subject to change without notice. All statements, information, and recommendations in this guide are believed to be accurate, but are presented without warranty of any kind, express or implied, and are provided “AS IS”. Users must take full responsibility for the application of the specifications and information in this guide.
The following equipment and software were used for the sample configuration:
Equipment | Software Version | |
---|---|---|
Ribbon Communications | Ribbon SBC SWE-Lite | 9.0.0 |
Third-party Equipment | CISCO CUCM | 12.5 |
Other software | VentaFax | 7.3.233.582I |
The following reference configuration shows connectivity between the third-party and Ribbon SBC Edge.
For any questions regarding this document or its content, please contact your maintenance and support provider.
You must have a valid SWE-Lite (key-based) license with the features to run the tests.
The following sections describe and provide new procedures for configuring the following:
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.
Click Add New to add a new Trunk.
Set the trunk configuration.
Select the device (trunk) name, the profiles, and the destination IP address that the trunk uses. The following figure shows an example of the Device Information screen.
The IP address on the SWE-Lite towards the CUCM is 192.168.191.216.
A route group allows you to designate the order of selecting gateways and trunks. It allows you to prioritize a list of gateways and ports for outgoing trunk selection.
In the Cisco Unified Communications Manager, use the Call Routing > Route/Hunt > Route Group menu path to configure route groups.
Click Add New to add a Route Group.
Specify the Route Group name, and select the devices that this Route Group uses. In the following example, the selected device is OrangeSBCLite that you created in the SIP Trunk section.
A route list associates a set of route groups in the specified priority order. It associates with one or more route patterns and determines the order of accessing those route groups. The order controls the progress of the search for available devices for outgoing calls.
A route list can only contain route groups. Each route list must contain at least one route group. Each route group must include at least one device.
In the Cisco Unified Communications Manager Administration, use the Call Routing > Route/Hunt > Route List menu path to configure route lists.
Click Add New to add a Route List.
Specify the Route List Name and Description and select the Cisco Unified Communications Manager Group that this Route List uses.
Click Add Route Group to add the Route Group to the Route List.
A route pattern comprises a string of digits (an address) and a set of associated digit manipulations that you can assign to a route list or a gateway. Route patterns provide flexibility in the network design. They work in conjunction with route filters and route lists, directing calls to specific devices and including, excluding, or modifying specific digit patterns.
In the Cisco Unified Communications Manager Administration, use the Call Routing > Route/Hunt > Route Pattern menu path to configure route patterns.
Click Add New to add a Route Pattern.
Specify the Route Pattern and Description and select the Gateway/Route List.
The X wildcard matches any single digit in the range 0 through 9. For instance, the route pattern 9XXX routes or blocks all numbers in the range 9000 through 9999.
See Appendix A for more information on special characters and settings on the CISCO CUCM.
Click Save.
All traffic matching the route pattern you just created will now route through the route list Orange_SBC_Lite.
This section provides the following information:
The System > Node-Level settings menu path allows you to set the Host name, Domain name service, and Time management.
The following figure shows an example of the system settings.
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. Use the Static IP or DHCP for running the initial setup of the SBC SWe Lite system.
You must use the Administrative IP interface for Running Initial Setup, as well as all management-related functions from the web browser.
Ethernet IP
The SBC SWe Lite system has four logical interfaces. In most deployments, one of the logical interfaces (typically Ethernet 1 IP) is assigned an IP address for transporting all VoIP media packets (for example, RTP, SRTP) and all protocol packets (for example, SIP, RTCP, TLS). Make sure that the DNS servers of the customer's network map the SBC SWe Lite system hostname to this IP address. You can use the hostname or IP addresses for 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. Use this IP address for performing the initial setup on the SBC SWe Lite. Refer to Running Initial Setup for more information. The default IP address for the logical interface named Ethernet 2 IP is 192.168.129.2. After the initial configuration, you can configure the logical interface from the Settings or Tasks tabs in the WebUI.
The following figures show examples of the Admin and Ethernet IP interfaces configuration.
The Protocols > IP > Static Route Table menu path allows you to manually specify the next hop routers used for reaching other networks. It also specifies the default routes for the connected IP networks that use 0.0.0.0
as the Destination and Mask.
When you configure a DHCP on an interface, the default Static Route (0.0.0.0/0) is removed and configured dynamically. To view the dynamically created default route, access the WebUI and navigate to Protocols > IP > Routing Table.
To add a new Static Route, click the plus (+) icon.
Specify the fields in the Create Static IP Route Entry screen.
Specifies the destination IP Address.
Specifies the network mask of the destination host or subnet. If the value of the 'Destination IP Address' field and 'Mask' field is 0.0.0.0, the static route is called 'default static route'.
Specifies the IP Address of the next hop router used for this Static Route.
Specifies the cost of this route, hence indirectly defining the preference of the route. Lower values indicate more preferred routes. The typical value is 1 for most static routes, indicating that users prefer static routes over dynamic routes.
The SIP > SIP Profiles menu path controls how the SBC Edge communicates with SIP devices. The profiles control important characteristics, such as session timers, SIP header customization, SIP timers, MIME payloads, and option tags.
To add a new SIP Profile, click the plus (+) icon.
To configure the OBS SIP Profile, modify the highlighted fields in the following figure to fulfill the OBS requirements. The rest of the features use the default settings.
The CUCM SIP Profile uses the default settings.
The Ventafax SIP Profile uses the default settings.
You must first generate the CSR (Certificate Signing Request) and then send it to the Certificate Authority (CA) to get the Signed Certificate. Once you receive the Signed Certificate, upload the certificate to the SBC along with the Root and Intermediate certificates you received from the CA.
Use the following procedure to generate the CSR.
On the left menu, go to Security > SBC Certificates > Generate SBC Edge CSR.
Add the information in the CSR template.
Click OK to generate the CSR.
Once you generate the CSR, be sure to send it to a CA (Certification Authority) to get the signed certificate.
A trusted certificate authority issues a Trusted CA Certificate. Trusted CA Certificates are imported to the SBC Edge to establish its authenticity on the network.
On the left menu, go to Security > SBC Certificates > Trusted CA Certificates.
Click the Import Trusted CA Certificate icon to import the certificates.
The Import Trusted CA Certificate pop-uup window prompts you to copy and paste the certificate.
Paste the certificate and click OK to save the changes.
Repeat the procedure to import additional certificates.
By default, after the Ribbon SBC 1000/2000 system is initialized for the first time, or after a factory reset, the Ribbon SBC 1000/2000 system is pre-configured with a Self-signed Server Certificate.
Installing a new Signed Certificate on the Ribbon SBC 1000/2000 comprises the following three procedures that you must perform in the specified order:
Use the following steps to generate the SBC Primary Certificate.
On the left menu, go to Security > SBC Certificates > SBC Primary Certificate.
Click Import > X.509 Signed Certificate.
The Import > X.509 Signed Certificate pop-up window prompts you to copy and paste the certificate.
After the Ribbon SBC 1000/2000 obtains the required certificates, be sure to configure several options and attributes on both the server and client so that the TLS can employ the certificate(s) to establish a secure connection. Configure the attributes in the TLS profiles. Attributes include, but are not limited to items, such as Client Ciphers, and inactivity timeouts.
SIP Signaling Groups use the TLS Profiles when you select the TLS transport type for incoming and outgoing SIP trunks (Listen Ports), and in SIP Server Tables when you select the TLS as the Server Host protocol.
On the left menu path, go to Security > TLS Profiles.
Click the plus (+) icon to add a new entry.
Set the TLS Profile as shown in the following figure.
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 you use for troubleshooting. The SIP Server supports either an FQDN or IP Address (V4 or V6).
To add a new SIP Server Table, click the plus (+) icon.
Specify the Description and select the SIP Server.
Select the SIP Server Table that you just created.
Click Create SIP Server > IP/FQDN to add a new SIP Server.
Set the new entry as shown in the figure. Modify the highlighted fields to fulfill the OBS requirements. The rest of the features use the default settings.
To add a new SIP Server Table, click the plus (+) icon.
Specify the Description and select the SIP Server.
Select the SIP Server Table that you just created.
Click Create SIP Server > IP/FQDN to add a new SIP Server.
To add a new SIP Server Table, click the plus (+) icon.
Specify the Description and select the SIP Server.
Select the SIP Server Table that you just created.
Click Create SIP Server > IP/FQDN to add a new SIP Server.
The SIP > Message Manipulation menu path allows you to manipulate the incoming or outgoing messages. The Message Manipulation feature enhances the interoperability with different vendor equipment and applications. It also corrects any fixable protocol errors in SIP messages spontaneously without requiring any changes to the firmware or software.
Although SIP is considered a mature protocol, devices running old firmware and systems interpret the SIP standard in a non-conforming way. Additionally, in some instances, a compliant message may potentially modify to adapt to an application-specific requirement.
This capability consists of two components: condition rules and message rules.
The Condition rules identify the messages and components required within a message to make any modifications. For example, I want to modify all INVITE messages with a from uri host of "ribbon.net".
The Message rules perform 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".
See Appendix A for more information about SIP Message Manipulation.
Condition rules are simple rules that apply to a specific component of a message (for example, diversion.uri.host, from.uri.host, and so on). You can match the value of the field specified in the Match Type list box against a literal value, token, or REGEX.
The Condition Rule Table stores a collection of all user-created Condition Rules.
This Condition Rule matches only if SG User Value 1 = application/sdp. This condition identifies whether the SDP is present or not in the SIP messages.
The SG User Value 1 is stored using a Message Rule (Store_Content-Type). (See Message Rule Tables for more information.)
SG User Value 1 is the predefined name that the SBC uses.
To add a new Condition Rule, go to the SIP > Message Manipulation > Condition Rule Table menu path, and click the plus (+) icon.
Set the new entry as shown in the following figure.
This Condition Rule matches only if from.displayname = Anonymous.
This rule compares whether the display name in the From header is equal to Anonymous.
Message Rule Modify_From_Anonymous uses this condition rule. (See Message Rule Tables for more information.) This rule sets the format that the OBS requested: (sip:anonymous@anonymous.invalid)
To add a new Condition Rule, go to the SIP > Message Manipulation > Condition Rule Table menu path, and click the plus (+) icon.
Set the new entry as shown in the following figure.
Message Rule Tables are simply sets of Condition Rules. Users apply these rules in the SIP Signaling Groups after enabling the Message Manipulation.
The Message Rule Tables collect SIP Messages Manipulations Rules and apply them according to the Message Type value set in the Message Rule Tables. The following tables define the settings of format that the OBS requested.
Table Description | Rules | Result Type | Message Type | Comments |
---|---|---|---|---|
Add_P-Early-Media | Add P-Early-Media supported | Optional | 180, 183 | This table applies only to 180 and 183 response messages. It collects the rules for inserting the P-Early-Media header requested by the OBS. |
Del_P-Early-Media | ||||
Add_P-Early-Media sendrecv | ||||
Store_Content-Type | Store Content-Type | Optional | 180, 183 | This table applies only to 180 and 183 response messages. It collects the rules for storing the Content-type header value. The value determines whether the SIP message contains an SDP or not. |
Store_User-Agent_Value | Optional | All | This table applies to all messages. It collects the rules for storing the IPPBX User-Agent and Server headers values. | |
OBS_SIP_Profile_Adaptation_01 | Remove_SGID_From_Header | Optional | All | This table applies to all messages. It collects the rules for setting the format that the OBS requested. |
Remove_SGID_To_Header | ||||
Modify_User-Agent_Header | ||||
Modify_Server_header | ||||
Modify_Allow_header | ||||
OBS_SIP_Profile_Adaptation_02 | Modify_PAI | Optional | Requests | This table applies only to request messages. It collects the rules for setting the format that the OBS requested. |
Add plus P-Asserted-Identity | ||||
Modify_From_Anonymous | ||||
Modify_Diversion |
This table collects the rules for adding 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 the plus (+) icon.
Set the new entry as shown in the following figure.
Description | Rule Type | Result Type | Comments |
---|---|---|---|
Add P-Early-Media supported | Header Rule | Optional | Adds the P-Early-Media header value = supported |
Del_P-Early-Media | Header Rule | Optional | Deletes the P-Early-Media header to avoid duplicate headers. |
Add_P-Early-Media sendrecv | Header Rule | Optional | Adds the P-Early-Media header value = sendrecv |
To add a new Message Rule, access the left menu path, and click the Add_P-Early-Media table you just created.
Click Create Rule > Header Rule.
Set the new entry as shown in the following figure.
Click Add/Edit.
Set the values as shown in the Edit Message Field window.
To add a new Message Rule, click the Add_P-Early-Media table on the left menu path.
Click Create Rule > Header Rule.
Set the new entry as shown in the following figures.
Click Add/Edit in the Condition Expression field.
When the Message Rule Condition window displays, set the following fields.
To add a new Message Rule, click the Add_P-Early-Media table on the left menu path.
Click Create Rule > Header Rule.
Set the new entry as shown in the following figures.
Click Add/Edit in the Condition Expression field.
When the Message Rule Condition window displays, set the following fields.
Click Add/Edit.
Set the values as shown in the Edit Message Field window.
This Store_Content-Type table collects the rule for storing the Content-Type value in the SG User Value 1. This rule applies only to 180 and 183 response messages.
You must apply this table on the Signaling Group facing the IPPBX, and set it as Inbound Message Manipulation.
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 shown in the following figure.
Description | Rule Type | Result Type | Comments |
---|---|---|---|
Store Content-Type | Header Rule | Optional | It stores the Content-Type value in the SG User Value 1. |
To add a new Message Rule, go to the left menu path, and click the Store_Content-Type table you just created.
Click Create Rule > Header Rule.
Click Add/Edit.
Set the value as shown in the Edit Message Field window.
The Store_User-Agent table collects the rules for storing the User-Agent and Server headers values received from the IPPBX.
To add a new Message Rule Table, go to the SIP > Message Manipulation > Message Rule Tables menu path, and click the plus (+) icon.
Set the new entry as shown in the following figure.
Description | Rule Type | Result Type | Comments |
---|---|---|---|
Store_User-Agent_Value | Header Rule | Optional | Stores the User-Agent value in the SG User Value 2. |
Store_Server_Value | Header Rule | Optional | Stores the Server value in the SG User Value 3. |
To add a new Message Rule, click the Store_User-Agent table on the left menu path.
Click Create Rule > Header Rule.
When the Header Value field displays, select Copy Value to.
Click Add/Edit.
Set the values as shown in the Edit Message Field window.
To add a new Message Rule, click the Store_User-Agent table on the left menu path.
Click Create Rule > Header Rule.
Click Add/Edit.
Set the values as shown in the Edit Message Field window.
The OBS_SIP_Profile_Adaptation_01 table collects rules for setting the format that the OBS requested. 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 the plus (+) icon.
Set the new entry as shown in the following figure.
Description | Rule Type | Result Type | Comments |
---|---|---|---|
Remove_SGID_From_Header | Header Rule | Optional | Removes the SGDI parameter from the FROM header. |
Remove_SGID_To_Header | Header Rule | Optional | Removes the SGDI parameter from the TO header. |
Modify_User-Agent_Header | Header Rule | Optional | Sets the User-Agent value as per OBS requirements. |
Modify_Server_header | Header Rule | Optional | Sets the Server value as per OBS requirements. |
Modify_Allow_header | Header Rule | Optional | Sets the Allow value as per OBS requirements. |
To add a new Message Rule, access the left menu path, and click the OBS_SIP_Profile_Adaptation_01 table you just created.
Click Create Rule > Header Rule.
Click the Add/Edit icon under the Header Parameters.
Set the field values as shown in the Edit Parameter window.
Click Apply to save the changes.
To add a new Message Rule, click the OBS_SIP_Profile_Adaptation_01 table on the left menu path.
Click Create Rule > Header Rule.
Click the plus (+) icon under the Header Parameters.
Set the field values as shown in the Edit Parameter window.
Click Apply to save the changes.
To add a new Message Rule, click the OBS_SIP_Profile_Adaptation_01 table on the left menu path.
Click Create Rule > Header Rule.
Click Add/Edit.
Set the field values as shown in the Edit Message Field window.
Click Apply to save the changes.
To add a new Message Rule, click the OBS_SIP_Profile_Adaptation_01 table on the left menu path.
Click Create Rule > Header Rule.
Click Add/Edit.
Set the field values as shown in the Edit Message Field window.
Click Apply to save the changes.
To add a new Message Rule, click the OBS_SIP_Profile_Adaptation_01 table on the left menu path.
Click Create Rule > Header Rule.
Click Add/Edit.
Set the field values as shown in the Edit Message Field window.
Make sure the Value field contains the following values:
INVITE, ACK, BYE, CANCEL, OPTIONS, UPDATE
Click Apply to save the changes.
The OBS_SIP_Profile_Adaptation_02 table collects rules for setting the format that the OBS requested. It applies to all messages.
To add a new Message Rule Table, access the SIP > Message Manipulation > Message Rule Tables menu path, and click the plus (+) icon.
Set the new entry as shown in the following figure.
Description | Rule Type | Result Type | Comments |
---|---|---|---|
Modify_PAI | Header Rule | Optional | Sets the host part of the URI as the local SWeLite IP address. |
Add plus P-Asserted-Identity | Header Rule | Optional | Adds a plus (+) icon in the user part of the URI. |
Modify_From_Anonymous | Header Rule | Optional | When the SBC receives an anonymous call, the FROM header is modified according to OBS requirements. |
Modify_Diversion | Header Rule | Optional | Adds a plus (+) icon in the user part of the URI and adds the counter parameter. |
To add a new Message Rule, access the left menu path, and click the OBS_SIP_Profile_Adaptation_02 table you just created.
Click Create Rule > Header Rule.
Set the new entry as shown in the following figure.
Select Modify in the Header Action field.
Click Add/Edit.
Set the field values as shown in the Edit Message Field window.
Click Apply to save the changes.
To add a new Message Rule, click the OBS_SIP_Profile_Adaptation_02 table on the left menu path.
Click Create Rule > Header Rule.
Click Add/Edit.
Set the field values as shown in the Edit Message Field window.
Click Apply to save the changes.
To add a new Message Rule, click the OBS_SIP_Profile_Adaptation_02 table on the left menu path.
Click Create Rule > Header Rule.
Click Add/Edit in the Condition Expression field to set the Message Rule Condition.
Set the Message Rule Condition as shown in the following figure.
Click Add/Edit.
Set the field values as shown in the Edit Message Field window.
Make sure the Replace Regex field contains the following values:
<sip:anonymous@anonymous.invalid>
To add a new Message Rule, click the OBS_SIP_Profile_Adaptation_02 table on the left menu path.
Click Create Rule > Header Rule.
Click Add/Edit.
Set the field values as shown in the Edit Message Field window.
Click the plus (+) icon under the Header Parameters.
Set the field values as shown in the Edit Message Field window.
Click Apply to save the changes.
The Media > Media Profiles menu path allows you to specify the individual voice and fax compression codecs and their associated settings to include in a Media List. Different codecs provide varying levels of compression, allowing a user to reduce the bandwidth requirements at the expense of voice quality.
To Create a new Media Profile, go to Media > Media Profiles on the left menu path.
To create a profile for the G.722 codec, click Create Media Profile > Voice Codec Profile.
Specify the following values to set the new G.722 codec.
Click Apply to save the changes.
To create a profile for the G711A codec, click Create Media Profile > Voice Codec Profile.
Specify the following values to set the G.711 A-law codec.
Click Apply to save the changes.
To create a profile for the G.729 codec, click Create Media Profile > Voice Codec Profile.
Specify the following values to set the G.729 codec.
Click Apply to save the changes.
To create a profile for the default G711U codec, click Create Media Profile > Voice Codec Profile.
Specify the following values to set the G.711 U-law codec.
Click Apply to save the changes.
To create a profile for the T.38 codec, click Create Media Profile > Fax Codec Profile.
Specify the following values to set the T.38 codec.
Click Apply to save the changes.
SDES-SRTP Profiles define a cryptographic context and used in SRTP negotiation. SDES-SRTP Profiles are required for enabling encryption, and SRTP are applied to Media Lists.
On the left menu path, go to Media > SDES-SRTP Profiles.
Click the plus (+) icon to add a new entry.
Specify the following values to set the new SDES-SRTP Profile.
Click Apply to save the changes.
The Media > Media List menu path enables you to specify a set of codecs and fax profiles that are allowed on a given SIP Signaling Group. Media Lists contain one or more Media Profiles that you define 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.
To add a Media List, go to Media > Media List on the left menu path.
Click the plus (+) icon to add a new entry.
Specify the following values to configure the new entry.
Click Apply to save the changes.
To add a Media List, go to Media > Media List on the left menu path.
Click the plus (+) icon to add a new entry.
Specify the following values to configure the new entry.
Click Apply to save the changes.
SIP and ISDN use different response messages to communicate why a call failed or could not connect (Q.850 for ISDN and SIP Responses for SIP). By default, the SBC Edge uses RFC 4497 to map these responses 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, an effective method 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 the plus (+) icon.
Specify the Description value.
On the left menu path, click on the OBS Mapping Table.
Click the plus (+) icon to add a new entry.
Specify the following values to configure the new entry.
Signaling groups can group telephony channels for routing and shared configuration. You use the Signaling groups to route calls, select call routes, and select Tone Tables and Action Sets.
To add a new Signaling Group, go to the Signaling Groups menu path.
Click Add SIP SG.
Set the new entry as shown in the following figures.
Click Apply to save the changes.
To add a new Signaling Group, go to the Signaling Groups menu path.
Click Add SIP SG.
Set the new entry as shown in the following figure.
Click Apply to save the changes.
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 selected from the Transformation Table.
See Appendix A for more information about Regular Expressions (REGEX) that help to configure Transformation Tables.
To add a new Transformation Table, go to Call Routing > Transformation on the left menu path.
Specify the Description value.
On the left menu path, click the CUCM_Prefixes table.
To add a new entry, click the plus (+) icon.
Specify the following values to configure the new entry.
Click Apply to save the changes.
To add a new Transformation Table, go to Call Routing > Transformation on the left menu path.
Specify the Description value.
On the left menu path, click the Orange_TLS table.
To add a new entry, click the plus (+) icon.
Specify the following fields to configure the new entry.
Click Apply to save the changes.
To add a new entry, click the plus (+) icon.
Specify the following fields to configure the new entry.
Calling Routing tables carry calls between signaling groups, thereby transferring calls between ports and protocols. They allow users to define routes, specifying which calls to transfer and how to translate the calls. 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 Group.
To add a new Call Routing table, go to Call Routing > Call Routing Table on the left menu path.
Set the Description value as shown in the following figure.
On the left menu path, click the To_Private table.
To add a new entry, click the plus (+) icon.
Configure the new entry as shown in the figure.
Click Apply to save the changes.
To add a new Call Routing table, go to Call Routing > Call Routing Table on the left menu path.
Set the Description as shown in the following figure.
On the left menu path, click the To_Orange table.
To add a new entry, click the plus (+) icon.
Configure the new entry as shown in the following figure.
Click Apply to save the changes.
These Application Notes describe the configuration steps required for Ribbon to successfully interoperate with OBS. All feature and serviceability test cases were completed and passed with the exceptions/observations noted in Test Results.
JIRA NUMBER | Name | Description |
---|---|---|
CHOR-7729 | SWe Lite: T.38 FAX over TLS not working | Orange telecom is trying to send and receive FAX over TLS using T.38. They have requested to use SRTP instead of UDPTL to handle the media stream as UDPTL is not encrypted. |