Adaptation For The Verizon Business Ipcc Services; Sip Entities - Avaya Aura Communication Manager 7.1 Application Notes

5.3.2 Adaptation for the Verizon Business IPCC Services

The Adaptation administered in this section is used for modification of SIP messages from
Communication Manager to Verizon. Repeat the steps in Section 5.3.1 with the following changes.
Step 1 - In the Adaptation Details page, enter:
1. A descriptive Name, (e.g., SBC1-Adaptation for Verizon).
2. Select VerizonAdapter from the Module Name drop down menu.
Step 2 - In the Module Parameter Type field select Name-Value Parameter from the menu.
Step 3 - In the Name-Value Parameter table, enter the following:
1. Name – Enter eRHdrs
 Value – Enter the following Avaya headers to be removed by Session Manager.
"AV-Global-Session-ID, Alert-Info, Endpoint-View, P-AV-Message-Id,
P-Charging-Vector, P-Location, AV-Correlation-ID, Av-Secure-
Indication"

5.4. SIP Entities

In this section, SIP Entities are administered for the following SIP network elements:
 Session Manager (Section 5.4.1).
 Communication Manager for Verizon trunk access (Section 5.4.2) – This entity, and its
associated Entity Link (using TLS with port 5071), is for calls from Verizon and
Communication Manager via the Avaya SBCE.
 Communication Manager for local trunk access (Section 5.4.3) – This entity, and its associated
Entity Link (using TLS with port 5061), is primarily for traffic between Avaya SIP telephones
and Communication Manager, as well as calls to Messaging.
 Avaya SBCE (Section 5.4.4) – This entity, and its associated Entity Link (using TLS and port
5061), is for calls from the Verizon Business IPCC Services via the Avaya SBCE.
 Messaging (Section 5.4.5) – This entity, and its associated Entity Link (using TLS and port
5061), is for calls to/from Messaging.
DDT; Reviewed:
SPOC 10/18/2017
Solution & Interoperability Test Lab Application Notes
©2017 Avaya Inc. All Rights Reserved.
21 of 95
CM71SM71-VzIPCC