Hello,

In the AES 8.0 overview document it does not show support for the J series sets from a SIP interop perspective in the SIP supported endpoints table. However on page 28 of the AES 8 document it discusses the J series endpoints as SIP endpoints and refers only to 1PCC. And in the AES overview for 7.1.3 it doesn't have either reference, yet we know that 3PCC with AES 7.1.3 for J series phones work. So the questions are:

1) are the J series endpoints supported with SIP firmware for 3PCC via AES Services?
2) What specific version of AES services are required for J series SIP endpoint support?

Thank you,

Alan

The Avaya Compatibility Matrix lists the J100 series SIP phones as compatible with AES release 7.1.3, 8.0 and 8.1

AES 7.1.3 shows J100 versions of 2.0, 4.0. 4.0.1 and 4.0.2 as compatible
AES 8.0 shows J100 versions of 2.0, 3,0, 4.0. 4.0.1 and 4.0.2, 4.0.3 as compatible
AES 8.1 shows J100 versions of 2.0, 4.0. 4.0.1 and 4.0.2 as compatible

Note that accessing the Avaya comparability matrix (link below) requires an Avaya SSO login
https://secureservices.avaya.com/compatibility-matrix/menus/product.xhtml?name=J100+-+SIP&solution=false&version=4.0.2

Endpoints listed in the table in the AES Overview document were tested by the AES product team. Endpoints tested by other product teams appear in that product's release notes (e.g. Equinox, J-series, Client SDK).


It is not clear on page 28 of what document and what version of the document (URLs are helpful) you are looking at.
My guess is this document
https://www.devconnectprogram.com/fileMedia/download/c5062e2d-b4ed-4a5f-8574-7f6f2461ea64

I think the "1PCC" in the paragraph discussing J169 and J179 is a typo; SIP stations are not supported with 1PCC. Only 3PCC is supported for some Avaya SIP endpoints.

There is a difference between appearing to work, and supported. With SIP devices while some CTI operations 'work' it is important to find a supported indication in print (product documentation) before committing to a deployment/investigation.