In a single FQDN model, you require one FQDN that represents all services. For example: webservices.company.com.

From the internet, the FQDN resolves to the IP address of the external Avaya SBC interface. Internally, from the enterprise, it resolves to the IP address of the internal Avaya SBC interface.

The certificate includes the FQDN and must be signed by a public CA.

FQDN for the Avaya Meetings Server Management service. For example: conferencing_management.company.com.

Internally the FQDN resolves to the virtual IP address of the Avaya Meetings Server Management system.

In a multiple FQDN deployment, the FQDN resolves externally to the IP address of the external Avaya SBC interface.

In a single FQDN deployment, the certificate is signed by the System Manager CA.

In a multiple FQDN deployment, the certificate is signed by a public CA.

FQDN for each Web Collaboration Services server IP address. For example: webconference1.company.com, webconference2.company.com and so on.

Internally, the FQDN resolves to the IP address of the Web Collaboration Services server.

In a multiple FQDN deployment, the FQDN resolves externally to the IP address of the external Avaya SBC interface.

In a single FQDN deployment, the certificate for each Web Collaboration Services server is signed by the System Manager CA.

In a multiple FQDN deployment, the certificate is signed by a public CA.

FQDN for the Avaya Aura® Web Gateway portal server virtual IP address. For example: webgateway.company.com.

Internally, the FQDN resolves to the virtual IP address of the Avaya Aura® Web Gateway portal service.

In a multiple FQDN deployment, the FQDN resolves externally to the IP address of the external Avaya SBC interface.

The certificate must include the global services FQDN in the SAN.

In a single FQDN deployment, the certificate for each server IP address is signed by the System Manager CA.

In a multiple FQDN deployment, the certificate is signed by a public CA.

FQDN for TURN media tunneling. For example: turnmedia.company.com.

The FQDN resolves to the IP address of the external Avaya SBC interface used for TURN media.

The certificate is signed by a public CA.

FQDN for HTTP media tunneling. For example: media.company.com.

The FQDN resolves to the IP address of the external Avaya SBC interface used for HTTP media tunneling.

The certificate is signed by a public CA.

FQDN for the Avaya SBC management interface. For example: sbce_management.company.com.

The FQDN resolves to the IP address for the internal Avaya SBC interface used for management.

The certificate is signed by the System Manager CA.