© 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 outlines the configuration best practices for the Ribbon QSBC (Q20 and Q21) when deployed with SIP-RECording with NICE Recording SERVER. The Ribbon QSBC offers a choice of recording only ingress/egress leg or simultaneous recording of both ingress and egress legs. Customers can choose the recording option on the Ribbon QSBC-based deployment requirements. For the NICE recording server, it is recommended to record both ingress and egress leg simultaneously.
Section-A : About Ribbon QSBC
Section-B : About NICE Engage platform
It is not the goal of this guide to provide detailed configurations that will meet the requirements of every customer deployment.
Use this guide as a starting point and build the Ribbon QSBC configurations in consultation with network design and deployment engineers.
This is a technical document intended for telecommunications engineers with the purpose of configuring Ribbon QSBC with NICE Engage platform SIPREC server.
Steps will require navigating the third-party Product Guide, the Operations Guide and Ribbon product using graphical user interface (GUI) or command line interface (CLI). A basic understanding of the concepts of TCP/UDP, IP/Routing, and SIP/RTP is needed to complete the configuration and any necessary troubleshooting.
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, expressed 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 aspects are required before proceeding with the Ribbon QSBC and the NICE Engage Platform.
The sample configuration uses the following equipment and software:
NICE Engage Platform
Administration and Debugging Tools
The deployment topology diagram is depicted below
IOT high level architecture covering call flows & overall topology is depicted below
The following Ribbon QSBC configurations are included in this section:
Configurations towards Endpoints :
Replace "z.z.z.z" with the QSBC's Ethernet interface (eth) Gateway IP address (example eth2 IP) and "a.a.a.a" with the QSBC's Ethernet interface(eth) Gateway IP address (example eth3 IP).
Replace "x.x.x.x" with the SBC's Ethernet interface (eth) IP address (example eth2 IP), and "y.y.y.y" with its netmask. Provide mediapool id configured in mdevices.xml (example medpool 1). Replace "c.c.c.c" with the SBC's Ethernet interface (eth) IP address (example eth3 IP), and "y.y.y.y" with its netmask. Provide mediapool id configured in mdevices.xml (example medpool 2).
Replace 9876543210 with the Phone1 Endpoint Phone number and 9876543211 with the Phone2 Endpoint Phone number.
Replace "n.n.n.n" with the phone1 IP address and "y" with its Port number.Replace "m.m.m.m" with the phone2 IP address and "p" with its Port number.
Ribbon QSBC does not support recording of only ingressLeg or only egressLeg. Thus, set the "rec_stream" in the SIPREC profile on the QSBC to "both".
Replace "k.k.k.k" with the SBC's Ethernet interface (eth) IP address (example eth3 IP), and "m.m.m.m" with its netmask. Provide mediapool id configured in mdevices.xml (example medpool 2).
Replace "9876543210" with the Phone1 Endpoint Phone number and "9876543211" with Phone2 Endpoint Phone number. The call is recorded when the call is made from "9876543210" to "9876543211" endpoint.
Replace "p.p.p.p" with SIPREC server IP address and "n" with its port.
Replace "i.i.i.i" with SIPREC server IP address and "k" with its port.
Here, the endpoints shown are previously created endpoints under Section A : Common SBC Configurations.
To increase SIP stack size as Recording request is more than default value (3000) pdustack size:
To increase the max-transport-mtu-size size:
The QSBC, by default, processes the SIP packet over TCP transport if the SIP packet is greater than max-transport-mtu-size,
The following checklist depicts the set of services/features covered through the configuration defined in this Interop Guide.
|7||Session Keep Alive on Recording Session|
|11||RFC2833 DTMF digits Recording|
|13||Call modification on Communication Session|
The following items should be noted in relation to this Interop - these are either limitations, untested elements or useful information pertaining to the Interoperability.
Currently, the Ribbon QSBC does not support SRS redundancy, Quad recording, Call modification on the communication session and TLS/SRTP towards SIPREC.
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 & solutions, please visit:
For detailed information about NICE engage platform, please visit:
This Interoperability Guide describes successful configuration for NICE interop involving Ribbon QSBC & NICE Engage platform SIPREC server.
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 has been covered, and what has not.
Configuration guidance is provided to enable the reader to replicate the same base setup - there maybe additional configuration changes required to suit the exact deployment environment.
© 2021 Ribbon Communications Operating Company, Inc. © 2021 ECI Telecom Ltd. All rights reserved.