Test Results - Avaya Aura Communication Manager 7.1 Application Notes

longer than the session refresh interval were tested, and such calls could be resumed after
the session refresh re-asserted the "sendonly" state.
 Transfer of toll-free calls between Communication Manager users.
 Incoming voice calls using the G.729A and G.711 ULAW codecs, and proper protocol
procedures related to media.
 DTMF transmission using RFC2833. For inbound toll-free calls, PSTN users dialing post-
answer DTMF digits are recognized properly by the Avaya CPE.
 Proper DiffServ markings for SIP signaling and RTP media flowing from the Avaya CPE
to Verizon.
 Incoming fax calls using T.38.
 Remote Avaya SIP endpoints connected through Avaya SBCE were used along with local
Avaya endpoints in the verification of these Application Notes.

2.2. Test Results

The interoperability compliance testing of the sample configuration was completed with successful
results as described in Section 2.1. The following observations may be noteworthy:
 Verizon Business IPCC Services suite does not support History Info or Diversion Headers.
The Avaya CPE will not send History-Info or Diversion header to Verizon IPCC in the
sample configuration.
 Verizon Business IPCC Services suite does not support SIP 302 Redirect.
 Verizon Business IPCC Services suite does not support G.729 Annex B. When using G729,
the Avaya CPE will always include "annexb=no" in SDP in the sample configuration.
 Section 3.2.3 summarizes a call flow that would theoretically allow a call to remain in
Communication Manager vector processing upon failure of a vector-triggered REFER
attempt. However, most such call scenarios could not be verified on the production Verizon
circuit used for testing. On the production circuit, Verizon would send a BYE to terminate
the call upon encountering REFER transfer failures, so there was no opportunity for the call
to remain in Communication Manager vector processing. See Section 3.2.3 for additional
information.
 During testing, Verizon's IP Interactive Voice Response (IP-IVR) service did not accept
the SIP REFER method unless the URI in the Refer-To header included the IP address
presented in the From header within the original SIP INVITE. This IP address was different
from the IP address included in the Contact header. The Avaya SBCE Topology Hiding
profile was used to populate the From header IP address in the Refer-To header for both the
IP-IVR and IP Toll Free services. Calls were successfully diverted using REFER for both
Verizon services with this Topology Hiding profile in place. See Section 7.3.9 for
additional information.
DDT; Reviewed:
SPOC 10/18/2017
Solution & Interoperability Test Lab Application Notes
©2017 Avaya Inc. All Rights Reserved.
8 of 95
CM71SM71-VzIPCC