Table of Contents


Interoperable Vendors


© 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 - it is not intended to be a full Configuration Guide / Interoperability Guide.

It 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 interoperable solution instead of the actual configuration involved for the Ribbon and Third Party product(s).

Details of the test setup used are included, along with full details of the Ribbon and Third party products, including details of any hardware and software versions used.

The document also details results of the interoperability, and any notes or caveats related to the inter-working between the products.

Audience

This document is open for all telecom-aware professionals to read, including Ribbon customers and partners. It provides high-level information of the interoperable solution provided.

Product and Device Details

The sample configuration uses the following equipment and software:

Requirements

Product

Equipment

Software Version

Ribbon Communications

SBC Core

V08.01.00-R000

Avaya 

Avaya Call Manager

Avaya Session Manager

6.3

6.3

Network Topology Diagram

Interoperability Test Lab Topology

The following diagram depicts the IOT high level architecture covering call flows and overall topology.

Avaya phones register to Avaya PBX via Ribbon SBC.

The interoperability testing used the following Avaya phone models:

  • Avaya J139
  • Avaya J169
  • Avaya 9611G

The preceding Network diagram mentions registration, HTTP messages path, and inbound and outbound call paths.

Interoperability Overview

In Brief

This document discusses the implementation of the access deployment of Avaya phones with Avaya CM/SM via Ribbon SBC Core.

Call Flow

Avaya phones (Avaya J139,J169 and 9611G) are registered to Avaya CM via Ribbon SBC Core.

  • As soon as the Avaya phones boot up, they communicate with the Avaya provisioning server (172.20.x.x) over HTTP port 80.
  • The phone downloads the "J100Supgrade.txt" and "46xxsettings-sip.txt" files. The phone later sends the REGISTER message followed by SUBSCRIBE to Avaya PBX.
  • Once the REGISTER and SUBSCRIBE are successful, the phone sends PPM messages to Avaya PBX over HTTP port 80 via Ribbon SBC.
  • Once all the 3 Avaya phones are registered successfully, the call is made between the registered Avaya phones.
  • All SIP messages like REGISTER, SUBSCRIBE and INVITE go via Ribbon SBC Core.

Highlights

  1. Avaya phones were registered to Avaya CM through Ribbon SBC Core as part of the hosted deployment. 

  2. Avaya phones send an off-hook INVITE. In order for the SBC to relay the off-hook INVITE, a ghost profile needs to be configured.

  3. TCP Relay needs to be configured in SBC so that it relays the http traffic sent from the Avaya phone.

  4. Media NAT should be configured in SBC for the media to work between Avaya phones and SBC.


For information regarding SBC Core configuration, refer to the product documentation on https://doc.rbbn.com/ 

Supplementary Services and Features Coverage

The following checklist depicts the set of services and features covered through the configuration defined in this Interop Guide.


Sr.No.Supplementary Features/ServicesCoverage
1Basic Registration over UDP

2Basic Call Setup

3Basic Call Termination

4Basic Subscription over UDP

5Call Hold/Unhold

6Call Forward All (CFU)

Legend

Supported

Not Supported
N/ANot Applicable

Support

For any support related queries about this guide, please contact your local Ribbon representative, or use the details below:

References

For detailed information about Ribbon products and solutions, please visit: https://ribboncommunications.com/products.

For detailed information about Avaya products and solutions, please visit: https://www.avaya.com/.

Conclusion

This Interoperability Note describes a successful configuration covering Avaya PBX interop involving the SBC Core. 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.