![]() |
You can configure all the AE Services APIs to use secure application links. The AE Services server comes pre-installed with a set of default server certificates for lab use , that is out-of-the-box deployments. These default server certificates should not be used in a production environment. It is highly recommended to replace all default installed certificates using your own Public Key Infrastructure or a third party vendor.
![]() | Note |
The CA used to sign the server default certificate has changed. In order to allow your client to connect to the AE Services 7.1.x server using a TLS socket connection for lab testing, the new AE Services CA certificate will need to be exported from the server and imported into your client trust store. |
The DMCC API provides:
Validation of the AE Services server certificate on the DMCC client application
Optional validation of the client certificate on the AE Services Server
For more information see the following documents:
Avaya Application Enablement Services Device, Media and Call Control API Java Programmers Guide, 02-300359
Avaya Application Enablement Services Device, Media and Call Control API XML Programmers Guide, 02-300358
Avaya Application Enablement Services Device, Media and Call Control API .NET Programmers Guide, 02-602658
Administering and Maintaining Avaya Aura® Application Enablement Services, 02-300357
TSAPI, JTAPI, and CVLAN provide validation of the server certificate. For more information, see the following documents:
Avaya Application Enablement Services TSAPI and CVLAN Client and SDK Installation Guide, 02-300543.
Avaya Application Enablement Services JTAPI Programmers Guide, 02-603488.
For Web Services, AE Services provides a Tomcat RPM that includes a default certificate and a default keystore of encryption keys for use in connecting to the AE Services server via Secure Sockets Layer (SSL). For more information, see the Application Enablement Services Web Services Programmer Guide, 02-300362.
![]() | Note |
Default server certificates should not be used in a production environment. It is highly recommended to replace all default installed certificates using your own Public Key Infrastructure or a third party vendor. |