The Hostname and Domain Name parameters are part of the overall IP Deskphone
configuration and are not configurable within each DCP.
- If AutoCN is configured as 1 (True), then the CN is constructed as
Hostname@Domainname.
- If AutoCN is configured as 0 (False), then the CN is configured as the value of the CN
parameter in the DCP.
• Purpose The Purpose attribute uses bit masks to identify what features a particular device
certificate is used for. Two bytes allows for any combination of up to 16 uses. For example, a
certificate that is used for EAP-TLS, DTLS and SCR have the purpose value of 97 (1+32+64).
The following table defines the values of the device certificate profile purposes.
Table 76: Device certificate profile purpose definitions
Application purpose of usage Value (hexidecimal) Value
EAP-TLS 0x0001 1
SIP-TLS 0x0002 2
HTTPS 0x0004 4
LICENSING 0x0080 128
ALL 0xffff -1
The default configurations for DCP #1 allow DCP #1 to be active and to use SCEP to retrieve a
device certificate that can be shared among all applications (purpose is ALL). All remaining profiles
are configured for PKCS#12 and to be inactive by default. The default configurations are compatible
with UNIStim 4 software. SIP 3.0 supports two profiles; SCEP and PKCS12.
To configure applications on the IP Deskphone, you must know which certificates are required and
what methods of device certificate installation are available. You can use this knowledge to
determine which profiles must be configured and how the certificates are shared among the different
applications. You must als
To configure applications on the IP Deskphone, you must know the following information:
• the required certificates
• the methods of device certificate installation
• the profiles that must be configured
• the method of sharing certificates among different applications
• the certificate attribute requirements (such as, subject, subjAltName, and key usage) for each
use
The profile index is part of the provisioning parameter name. For example, the parameter to assign
the source (SCEP or PKCS#12) for DCP #2 is the following: dcpsource2
The following is an example of the provisioning file, system.prv, that shows some of the device
certificate profile attributes that are provisioned when SCEP is used to install a device certificate.
Device certificate profiles
March 2015 SIP Software for Avaya 1200 Series IP Deskphones-Administration 251
Comments? infodev@avaya.com
To Next Page
Loading...
