JR201-FK-VoIP SIP Phone with Avaya Aura® Session Manager and Avaya Aura® Communication Manager

JR201-FK-VoIP SIP Phone with Avaya Aura® Session Manager and Avaya Aura® Communication Manager

1.Introduction

The JR201-FK-VoIP SIP Phone integrates with Avaya SIP infrastructure consisting of Avaya Aura® Session Manager 8.0 and Avaya Aura® Communication Manager 8.0 as third-party SIP endpoints. These Application Notes describe the steps required to configure JR201-FK-VoIP SIP Phone to work as Avaya third party SIP endpoints. Although the compliance test was completed with and without TLS/SRTP, these Application Notes will describe the configuration with TLS/SRTP enabled.

The JR201-FK-VoIP Handset Telephone is designed to meet the need soft client who experience loss through vandalism. Ideal for parking lots, prisons, railway / metro platforms, hospitals, police stations, ATM machines, stadiums, outside building etc.

2.General Test Approach and Test Results

The general test approach was to configure the JR201-FK-VoIP SIP Phone to communicate with Session Manager as third party SIP endpoints using TLS connection.

DevConnect Compliance Testing is conducted jointly by Avaya and DevConnect members. The jointly-defined test plan focuses on exercising APIs and/or standards-based interfaces pertinent to the interoperability of the tested products and their functionalities. DevConnect Compliance Testing is not intended to substitute full product performance or feature testing performed by DevConnect members, nor is it to be construed as an endorsement by Avaya of the suitability or completeness of a DevConnect member’s solution.

Avaya recommends our customers implement Avaya solutions using appropriate security and encryption capabilities enabled by our products. The testing referenced in these DevConnect Application Notes included the enablement of supported encryption capabilities in the Avaya products.  Readers should consult the appropriate Avaya product documentation for further information regarding security and encryption capabilities supported by those Avaya products.

Support for these security and encryption capabilities in any non-Avaya solution component is the responsibility of each individual vendor.  Readers should consult the appropriate vendor-supplied product documentation for more information regarding those products.

This test was conducted in a lab environment simulating a basic customer enterprise network environment. The testing focused on the standards-based interface between the Avaya solution and the third-party solution. The results of testing are therefore considered to be applicable to either a premise-based deployment or to a hosted or cloud deployment where some elements of the third-party solution may reside beyond the boundaries of the enterprise network, or at a different physical location from the Avaya components.

Readers should be aware that network behaviors (e.g. jitter, packet loss, delay, speed, etc.) can vary significantly from one location to another and may affect the reliability or performance of the overall solution. Different network elements (e.g. session border controllers, soft switches, firewalls, NAT appliances, etc.) can also affect how the solution performs.