© 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.
Scope / Non-Goals
This is an Interoperability Note and is not intended as a full Configuration Guide / Interoperability Guide.
This Interoperability Note is an informational document that briefs on the interop achieved between Ribbon products and various third-party products.
It focuses on the feasibility aspects in providing a Ribbon interoperable solution instead of the actual configuration involved for the Ribbon and third-party product(s).
It includes the test setup details used, along with full details of the Ribbon and third-party products, including details of any hardware and software versions used.
It also details results of the interop, and any notes or caveats related to the interworking.
This read-out document is open for all telecom-aware professionals, including Ribbon customers and partners. It gives high-level information of the interop solution provided. Steps will require navigating the Microsoft Windows Server as well as the Ribbon SBC Core Command Line Interface. Understanding the basic concepts of TCP/UDP, IP/Routing, and SIP/RTP is necessary to support the troubleshooting aspects.
Product and Device Details
|Ribbon SWe Core||V09.00.00R000|
|Third-Party Products||Microsoft Skype For Business 2015||6.0.9319.0|
Network Topology Diagram
Interoperability Test Lab Topology
The IOT high level architecture covering call flows and overall topology is shown below.
This document discusses the implementation of the Ribbon SBC Core/Edge SBC and the Skype for Business Video Interop Server (VIS) for audio-video connectivity between Microsoft Skype for Business endpoints and Cisco video endpoints.
At the time this document was created, VIS supports only inbound calls into the VIS server. No outbound calls are allowed. For achieving the interop aspects, peer-to-peer bidirectional video calls were tried between Cisco video endpoints and Skype For Business clients through Ribbon SBC Core and Edge.
For more information on Skype For Business VIS implementation and deployment, refer to the following:
- Skype For Business endpoints were registered locally with a SFB FrontEnd Server and Cisco video endpoints were registered to CUCM.
- Trunk between Skype For Business and Ribbon SBC was TLS/RTP.
- ICE-Lite was enabled on Ribbon SBC (Core and Edge) towards Skype For Business and CUCM trunk groups.
- Sufficient Video BW was allocated on the Ribbon SBC (Core and Edge).
- SBC supports relaying of video codecs (passthru mode).
- Skype For Business Video Interop Server (VIS) supports X-264UC/90000 and payload type 122.
For information regarding SBC Core and Edge configuration, refer to the product documentation on https://support.sonus.net/
Supplementary Services and Feature Coverage
The following checklist depicts the set of services and features covered through the interop:
|Sr. No.||Supplementary Services/ Features||Coverage|
|1||Basic Call Setup & Termination (CUCM Video EP to SFB client)|
|2||Basic Call Setup & Termination (SFB client to CUCM Video EP)|
- Outbound calls from Skype For Business Clients get rejected by Skype For Business FrontEnd Server.
- New calls from the Skype For Business deployment to the video teleconferencing server (VTC) over the video SIP trunk are not supported.
This means that only inbound call into the Skype For Business deployment are supported over the video SIP trunk.
For any support related queries about this note, please contact your local Ribbon representative, or use the following details:
- Sales and Support: 1-833-742-2661
- Other Queries: 1-877-412-8867
- Website: https://ribboncommunications.com/about-us
For detailed information about Ribbon products and solutions, please visit:
This Interoperability Note describes successful testing of Inbound calls to Skype For Business Video Interop Server (VIS) interop involving Ribbon SBC Core/Edge and Cisco Unified Communications Manager.
© 2021 Ribbon Communications Operating Company, Inc. © 2021 ECI Telecom Ltd. All rights reserved.