© 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 is an interoperability Note, which is not intended to be a full Configuration Guide/Interoperability Guide. This is an informational document that briefs on the interoperability achieved between Ribbon products and various third-party products.
This document focuses on the feasibility aspects in providing a Ribbon interoperability solution instead of the actual configuration involved for the Ribbon and third-party product(s). Details of the test setup used will be included, along with full details of the Ribbon and third-party products, including details of any hardware and software versions used. The document will also detail results of the interoperability and any notes or caveats related to the interworking.
This interoperability note is available for all telecom-aware professionals, which includes Ribbon customers and partners. It provides high-level information of the interop solution provided.
The sample configuration uses the following equipment and software:
Requirements
Product | Equipment | Software Version |
---|---|---|
Ribbon Communication | SBC Core PSX EMS | V08.01.00-R000 V12.00.00-R000 V12.02.00-R000 |
Group 2000 | Group 2000 | N/A |
The following figure illustrates the IOT high-level architecture that covers call flows and overall topology.
Test Scenario 1
Lawful Intercept (LI) enables a Law Enforcement Agency (LEA) to perform lawfully authorized electronic surveillance of communication that involves users or subscribers against whom a warrant has been issued. This document discusses the implementation of the Lawful Intercept solution with Group 2000 and Ribbon.
Group 2000's LIMA Lawful Intercept server is connected to the Ribbon devices over an IPsec tunnel. For the provisioning of targets, LIMA connects over the X1 interface to the Ribbon EMS. For call content and call data, the Ribbon SBC is connected over the X2/X3 interface to the LIMA server. In this interop, SBC uses the IMSLI variant of the LI.
To configure the SBC using IMS LI, refer to IMS LI Configuration.
The EMS receives and processes Lawful Intercept target provisioning data from the LIMA server via SOAP-based API. The EMS then distributes this data to all primary PSXs and generates success or failure responses to the LIMA server. The following are the operations performed: target provisioning, target removal, and target query.
Modification of the exiting target is not supported.
When the SBC Core identifies a call to be trapped, the SBC sends Call Data messages to the LIMA server over UDP on the X2 interface at various stages of the call. In response, the LIMA LI server tells the SBC the IP address and port number(s) to send the collected call content RTP streams over the X3 interface.
The SBC also sends the call voice streams (call content) RTP copy to an IP address and port provided by the LIMA LI server.
The SBC always sends call content and call data over UDP on the X2 and X3 interfaces.
For information regarding SBC Core configuration, refer to the product documentation on https://doc.rbbn.com/display/SBXDOC81/SBC+Core+8.1.x+Documentation
The following checklist depicts the set of services and features covered through the configuration defined in this Interoperability Guide.
Services and Features Checklist
Serial No. | Supplementary Features/Services | Coverage |
---|---|---|
1 | Basic Registration over UDP | |
2 | Basic Call Setup | |
3 | Basic Call Termination | |
4 | Call Hold/Unhold | |
5 | Call Forward Scenarios | |
6 | Call Transfer | |
7 | SMS | |
8 | Video | |
9 | DTMF Interwork |
Legend
Supported | |
Not Supported | |
N/A | Not Applicable |
For any support related queries about this guide, contact your local Ribbon representative or use the following details:
For detailed information about Ribbon products and solutions, refer to https://ribboncommunications.com/products.
This Interoperability Note describes a successful configuration covering Group 2000's Lawful Intercept solution with Ribbon products. All the necessary features and serviceability aspects stand covered as per the details provided in this interoperability document.
© 2021 Ribbon Communications Operating Company, Inc. © 2021 ECI Telecom Ltd. All rights reserved.