Explanation
SBC states:

References: Avaya Aura Session Border Controller Enterprise Implementation and Maintenance (2012), page
201

Explanation
BD: Administering Entity Link between Presence Services Cluster SIP Entity and Session Manager Procedure
1. On the System Manager web console, navigate to Elements > Routing > Entity Links.
2. In the Name field, enter a name for Entity Link.
3. In the SIP Entity 1 field, select the Session Manager instance.
4. In the Protocol field, select TLS.
5. In the Port field, type 5062.
Note: Note that this port number cannot be the same as the port number administered in
"Administering Entity Link between Avaya Breeze and Session Manager".
CD: Administering Entity Link between Avaya Breeze and Session Manager.
About this task
Create an En2tity Link to connect Session Manager to Avaya Breeze. You must administer separate Entity Links for Avaya Breeze servers in order to open SIP listeners on the designated ports.
Session Manager requires a Listen Port with the Listen Port as 5061, Protocol as TLS, and Default Domain as the login domain of endpoint devices. Without this, PPM will fail for SIP endpoints.
References: Avaya Aura Presence Services Snap-in Reference. Release 7.0.1 (December 2016), pages 25-26
https://downloads.avaya.com/css/P8/documents/101013646

Explanation
traceSM is an interactive perl script that allows an administrator to capture, view, and save call processing activity on a Session Manager. While not as powerful or versatile as wireshark, traceSM is absolutely essential when it comes to working with Avaya SIP. First off, it allows you to view SIP messages even if they have been encrypted with TLS.

Explanation
Adding a switch connection
The procedure include the following steps:
1.From the AE Services Management Console main menu, select Communication Manager Interface > Switch Connections.
2. On the Switch Connections page, in the Add Connection field, type a switch connection name (for example Switch1) For the Secure H323 Connection check box, do one of the following:
* For Communication Manager6.3.6 or later and TLS for the H.323 Signaling Channel (normally associated with FIPS Mode), select the Secure H323 Connection check box.
* For any previous release of Communication Manager without TLS for the H.323 Signaling Channel, uncheck the Secure H323 Connection check box.
Etc.
References: Avaya Aura Application Enablement Services Administration and Maintenance Guide, page 73
https://downloads.avaya.com/css/P8/documents/100171737

Explanation
The Avaya WebRTC Snap-in enables users inside or outside the Enterprise to make a secure call from their web browser to any endpoint to which Avaya Aura can deliver calls.
References: Avaya WebRTC Snap-in Reference, Release 3.1 (May 2016), page 6
https://downloads.avaya.com/css/P8/documents/101013939