• You must also consult the relevant endpoint or server documentation, as supported features can vary between firmware releases.
• IP Office does not support wildcard certificates for use with Avaya SIP clients. That includes Avaya Workplace Client, Avaya Vantage™ or J100 Series endpoints.

IP Office Subject Alt Name Requirements

Notes:

1. Remote phones can securely remotely download their settings and configuration, typically using HTTPS.
2. IP Office does not request certificates from SIP clients for SIP-TLS sessions. It can request a certificate for HTTPS transfers according to the Mutual Authentication setting; see Certificate Check Controls.
3. Indicates whether the endpoint requires Subject Alternative Name support within the identity certificate received from the IP Office. Typically, when using DNS, VoIP endpoints require only the FQDN of the IP Office in the SAN and no IP Address. Public Certificate Authorities do not support IP addresses and private domain names.
4. 1100/1200 Series and J129 phones do not support FQDNs and so cannot use certificates provided by public Certificate Authorities.
5. Avaya does not recommend using IP address entries in certificates.
6. If using VoIP resilience with secure signaling or provisioning, the root CA certificate for both servers must be the same.
7. If IP address entries are required for devices with Public CAs, you can use an FQDN_IP_MAP setting to map IP addresses to FQDNs. If using an auto-generated 46xxsettings.txt file, you can add the FQDN_IP_MAP entry to a 46xxspecials.txt file. For example, to map an IP addresses to an FQDN for just 9608, 9611, 9621 and 9641 phones:IF $MODEL4 SEQ 9608 GOTO 96X1SETTINGS
IF $MODEL4 SEQ 9611 GOTO 96X1SETTINGS
IF $MODEL4 SEQ 9621 GOTO 96X1SETTINGS
IF $MODEL4 SEQ 9641 GOTO 96X1SETTINGS
GOTO END
# 96X1SETTINGS
SET FQDN_IP_MAP "ipol.ca.avaya.com=10.136.100.70,ipol2.ca.avaya.com=10.136.100.74"
# END