© 2021 Ribbon Communications Operating Company, Inc. © 2021 ECI Telecom Ltd. All rights reserved. The compilation (meaning the collection, arrangement and assembly) of all content on this site is protected by U.S. and international copyright laws and treaty provisions and may not be used, copied, reproduced, modified, published, uploaded, posted, transmitted or distributed in any way, without prior written consent of Ribbon Communications Inc.
The trademarks, logos, service marks, trade names, and trade dress (“look and feel”) on this website, including without limitation the RIBBON and RIBBON logo marks, are protected by applicable US and foreign trademark rights and other proprietary rights and are the property of Ribbon Communications Operating Company, Inc. or its affiliates. Any third-party trademarks, logos, service marks, trade names and trade dress may be the property of their respective owners. Any uses of the trademarks, logos, service marks, trade names, and trade dress without the prior written consent of Ribbon Communications Operating Company, Inc., its affiliates, or the third parties that own the proprietary rights, are expressly prohibited.
This document depicts the configuration details for Ribbon SBC 1000 interworking & compliance against Deutsche Telekom CompanyFlex SIP Trunking solution.
The Ribbon Session Border Controller provides best-in class communications security. The SBC 1000 dramatically simplifies the deployment of robust communications security services for SIP Trunking.
Deutsche Telekom is a telecommunications company that offers a range of fixed-network services, such as voice and data communication services based on fixed-network and broadband technology; and sells terminal equipment and other hardware as well as services to resellers.
This document provides configuration best practices for deploying Ribbon's SBC 1000 /2000 and SWe Lite series when connecting with Deutsche Telekom CompanyFlex. Note that these are configuration best practices, and each customer may have unique needs and networks. Ribbon recommends that customers work with network design and deployment engineers to establish the network design which best meets their requirements.
It is not the goal of this guide to provide detailed configurations that will meet the requirements of every customer. Use this guide as a starting point and build the SBC configurations in consultation with network design and deployment engineers.
This is a technical document intended for telecommunications engineers with the purpose of configuring both the Ribbon SBC and the third-party product. Navigating the third-party product as well as the Ribbon SBC 1000 GUI is required. Understanding the basic concepts of TCP/UDP, IP/Routing, and SIP/RTP is also necessary to complete the configuration and any required troubleshooting.
The following aspects are required before proceeding with the interop:
The configuration uses the following equipment and software:
Equipment Software Version Ribbon SBC 1000 8.0.1 Third-party Equipment Administration and Debugging Tools Wireshark LX Tool 3.2.7 22.214.171.124
Product Ribbon Networks DSL Line NA Deutsche Telekom Deutsche Telekom "CompanyFlex" SIP trunks NA
Ribbon SBC 1000
Administration and Debugging Tools
Refer to the following document for installing the SBC 1000: https://support.sonus.net/pages/viewpage.action?pageId=229474498
Open any browser and enter the SBC IP address.
Click Enter and log in with a valid User ID and Password.
This section describes how to view the status of each license along with a copy of the license keys installed on your SBC. The Feature Licenses panel enables you to verify whether a feature is licensed, along with the number of remaining licenses available for a given feature at run-time.
From the Settings tab, navigate to System > Licensing > Current Licenses.
For more details on Licenses, refer to SBC 1000, SBC 2000 Licenses.
The SBC 1000 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 1000 supports user-created VLAN logical sub-interfaces.
Ethernet 2 IP, Ethernet 1 IP are used for this interop.
From the Settings tab, navigate to Networking Interfaces > Logical Interfaces.
For the interop, this app note uses the same interface for Administrator and Ethernet1.
Ethernet 1 IP
Ethernet 1 IP is assigned an IP address used for transporting all the VOIP media packets (for example, RTP, SRTP) and all protocol packets (for example, SIP, RTCP, TLS). In the default software, Ethernet 1 IP is enabled, and an IPv4 address is acquired, via a connected DHCP server or you can assign a static IP as well.
Ethernet 2 IP
Configure this Ethernet 2 interface as follows as per the requirement .This interface will face the Deutsche Telekom interface.
If you are migrating from SIP Trunk DeutschlandLAN towards CompanyFlex, please make sure that you configure either a second (different) interface IP address on SBC1000 / SBC2000, or in case of SBC SWe Lite, a second interface with different IP address.
Do not use the same IP for DeutschlandLAN and CompanyFlex on the SBC.
Static routes are used to create communication to remote networks. In a production environment, static routes are mainly configured for routing from a specific network to another network that you can only access through one point or one interface (single path access or default route).
Specifies the destination IP address.
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 the 'default static route'.
Specifies the IP address of the next-hop router to use for this static route.
Specifies the cost of this route, and therefore indirectly specifies the preference of the route. Lower values indicate more preferred routes. The typical value is 1 for most static routes, indicating that static routes are preferred to dynamic routes.
Configure the Signaling profile, Route, Media profile, SIP profile, SIP registrar, etc. based on the requirement.
For assistance visit : https://support.sonus.net/
Select Settings > Media > Media List.
Media Profiles specify the individual voice and fax compression codecs and their associated settings for inclusion into a Media List. Different codecs provide varying levels of compression, allowing the reduction of bandwidth requirements.
Use default media profile with codec G.711.
Add T.38 in the Default Media list only if fax is involved.
Select Settings > Media > Media Profiles.
Create a Media profile with T.38 codec.
It is recommended to use a maximum packet time (max pTime) of 20ms for all Voice Codecs.
Select Settings > SIP > SIP Profiles.
SIP Profiles control how the SBC Edge communicates with SIP devices. The SIP Profile controls important characteristics, such as the following: session timers, SIP header customization, SIP timers, MIME payloads, and option tags
Create a new SIP profile with the name "Telekom sip profile" with the session timer enabled. The Minimum Acceptable Timer is 600, and the Offered Session Timer is 1800.
Select Settings > SIP > Contact Registration Table.
The Contact Registrant Tables manage contacts that are registered to a SIP server. The SIP Server Configuration can specify a Contact Registrant Table. The username portion of the table is used for outbound calls.
Click on Registration status under the "Contact Registration profile" to see the status of SIP Trunk registration with Deutsche Telekom.
Select Settings > SIP > Remote Authorization Tables.
Remote Authorization Tables entries contain information for responses to request message challenges by an upstream server.
Select Settings > SIP > SIP Server Tables
SIP Server Tables contain 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.
When you configure a SIP server table entry with a DNS SRV record, Ribbon recommends that you do not configure another SIP server table entry with the IPs or FQDNs that the DNS SRV record resolves.
The Message Manipulation feature work in concert to modify SIP messages. Below Message Manipulation are used to avoid registration and call failures.
The SMM performs the following actions:
Adds FQDN provided by Deutsche Telekom in the URI host of the following headers of the outbound SIP messages .
Adds sip trunk number in URI user for CONTACT header of all outgoing SIP messages.
Add new headers for all outbound INVITE messages.
Add new header for all outbound REGISTER messages.
Select Settings > SIP > Message Manipulation > Message Rule Table
Click the Create Message Rule Table(
Message Manipulation - From, To , Request URI sends FQDN in URI host.
Under "Telekom" Repeat the same for To header.
Under "Telekom" repeat the same for request URI.
Create message manipulation under "telekom" so that the contact header has SIP trunk number in URI user for all the sip messages .
Message Manipulation - Add Allow-Events in INVITE
Click the Create Message Rule Table() icon.
Provide a suitable description for the Rule Table.
Choose "INVITE" message under Applicable Messages.
Message Manipulation - Add P-Early-Media in INVITE
Message Manipulation - Add Allow in REGISTER
Click the Create Message Rule Table() icon.
Provide a suitable description for the Rule Table.
Choose "REGISTER" message under Applicable Messages.
Message Manipulation - Add Supported in REGISTER
Signaling Groups allow grouping telephony channels 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.
Select Settings > Signaling Groups
Initially choose Default call Route. Create the Route, as shown in the call Routing section, and then update the call Route to "From Telekom".
Because a NAT is used in the test environment, add the external public IP of the NAT box under static NAT outbound of the Sig Group that is facing towards the Deutsche Telekom server.
- Enable Message Manipulation.
- Click Add/Edit on Outbound Message Manipulation.
- This displays a drop-down list of available message tables. Select an entry and click Apply.
Call Routing allows carrying of calls between Signaling Groups. Routes are defined by Call Routing Tables, which allow for a flexible configuration of which calls to carry, and how to translate them.
Select Settings > Call Routing > Call Routing Table.
Call Routing Tables are one of the central connection points of the system, linking Transformation Tables, Message Translations, Cause Code Reroute Tables, Media Lists and the three types of Signaling Groups (ISDN, SIP and CAS).
In the SBC Edge, call routing occurs between Signaling Groups.
In order to route any call to or from a call system connected to the SBC, you must first configure a Signaling Group to represent that device or system. The following list illustrates the hierarchical relationships of the various Telephony routing components of a SBC call system:
Each call routing entry describes how to route the call and also points to a Transformation Table which defines the conversion of names, numbers and other fields when routing a call.
To create an entry:
Set the following fields:
Enabled - Enables the call route entry for routing the call, displays in configuration header as
Priority of the route from 1 (highest) to 10 (lowest). Higher priority routes are matched against before lower priority routes, regardless of the order of the routes in the table.
Number/Name Transformation Table:
Specifies the Transformation Table to use for this routing entry. This drop-down list is populated from the entries in the Transformation Table.
Destination Signaling Groups:
Specifies the Signaling Groups used as the destination of calls. The first operational Signaling Group from the list is chosen to place the call. Click the Add/Edit button to select the destination signaling group.
Audio Stream Mode:
DSP (default entry): The SBC uses DSP resources for media handling (transcoding), but does not facilitate the capabilities/features between endpoints that are not supported within the SBC (codec/capability mismatch). When the DSP is configured, the Signaling Groups enabled to support DSP are attempted in order.
Enabled: Enable Transcoding on SIP-to-SIP calls.
The following checklist depicts the set of services/features covered through the configuration defined in this Interop Guide.
Supplementary Services/ Features
|1||SIP Trunk Registration|
|2||Inbound Call-Mobile PSTN|
|3||Outbound Call-Mobile PSTN|
|4||Inbound call-Landline PSTN|
|5||Outbound call-Landline PSTN|
|6||Basic Call With Different Codecs|
|8||FAX using T.38|
|10||FAX using G711 Fallback|
|11||Call Hold and Resume Outbound|
|12||Call Hold and Resume Inbound|
|13||Anonymous Calls Outbound|
|15||FAX - transcoding|
|16||Call Transfer (Blind)|
|17||Call Transfer (Attended)|
|19||487 Request Terminated|
|20||Long Duration Calls|
Observation - Any call to the PSTN mobile display the caller's number with the country code; whereas, any call to the PSTN landline exclude the country code.
For any support related queries about this guide, please contact your local Ribbon representative, or use the details below:
For detailed information about Ribbon products and solutions, please visit:
This Interoperability Guide describe the configuration steps required for Ribbon SBC 1000 / 2000 to successfully interoperate with Deutsche Telekom. All feature and serviceability test cases were completed and passed with the exceptions/observations noted in Test Results
All features and capabilities tested are detailed within this document - any limitations, notes or observations are also recorded in order to provide the reader with an accurate understanding of what is/is not covered.
Configuration guidance is provided to enable the reader to replicate the same base setup — additional configuration changes are possibly required to suit the exact deployment environment.
© 2021 Ribbon Communications Operating Company, Inc. © 2021 ECI Telecom Ltd. All rights reserved.