Interoperability Compliance Testing - Avaya Aura Communication Manager 7.1 Application Notes

For the testing associated with this Application Note, the interface between Avaya systems and
Verizon Business IPCC Services did not include use of any specific encryption features as
requested by Verizon.
Encryption (TLS/SRTP) was used internal to the enterprise between Avaya products wherever
possible.

2.1. Interoperability Compliance Testing

The interoperability compliance testing included the execution of test cases details in the Verizon-
authored interoperability test plan.
 SIP OPTIONS monitoring of the health of the SIP trunks was verified. Both the Avaya
enterprise equipment and Verizon Business can monitor health using SIP OPTIONS.
 Incoming calls from the PSTN were routed to the toll-free numbers assigned by Verizon
Business to the Avaya location. Configuration was varied such that these incoming toll-free
calls were directed to Communication Manager telephone extensions, and Communication
Manager VDNs containing call routing logic to exercise SIP Network Call Redirection.
 Proper disconnect when either party hangs up an active call.
 Proper disconnect when the PSTN caller abandons (i.e., hangs up) a toll free call before the
call has been answered.
 Proper SIP 486 response and busy tone heard by the caller when a PSTN user calls a toll-
free number directed to a busy user or resource when no redirection on busy conditions was
configured (which would be unusual in a contact center).
 Proper termination of an inbound IP Toll Free call left in a ringing state for a relatively
long duration, which again would be unusual in a contact center. In the sample
configuration, Verizon sent a SIP CANCEL to cancel the call after three minutes of ring no
answer conditions, returning busy tone to the PSTN caller.
 Privacy requests for inbound toll-free calls from the PSTN were verified. That is, when
privacy is requested by a PSTN caller (e.g., dialing *67 from a mobile phone), the inbound
toll-free call can be successfully completed while withholding presentation of the PSTN
caller ID to user displays. (When the caller requests privacy, Verizon IPCC sends the caller
ID in the P-Asserted-Identity header and includes "Privacy: id" which is honored by
Communication Manager).
 Inbound toll-free call long holding time call stability. The Avaya CPE sends a re-INVITE
with SDP to refresh the session at the configured session refresh interval specified on the
Communication Manager trunk group handling the call. In the sample configuration, the
session refresh re-INVITE was sent after 900 seconds (15 minutes), the interval configured
for the trunk group in Section 6.8.1. The call continued with proper talk path.
 Telephony features such as hold and resume. When a Communication Manager user holds
a call in the sample configuration, Communication Manager will send a re-INVITE to
Verizon IP Toll Free service with a media attribute "sendonly". The Verizon 200 OK to
this re-INVITE will include media attribute "recvonly". While the call remains on hold,
RTP will flow from the Avaya CPE to Verizon, but no RTP will flow from Verizon to the
Avaya CPE (i.e., as intended). When the user resumes the call from hold, bi-directional
media path resumes. Although it would be unexpected in a contact center, calls on hold for
DDT; Reviewed:
SPOC 10/18/2017
Solution & Interoperability Test Lab Application Notes
©2017 Avaya Inc. All Rights Reserved.
7 of 95
CM71SM71-VzIPCC