from the switch. If a device is not using external power, the switch provides
inline power through the Ethernet cable that is attached to the device. The
Starting up... screen appears for about 30
attempts to detect an Ethernet connection. If an Ethernet connection is
detected but no IP address is assigned, the user is prompted to contact
the administrator for assistance. If an Ethernet connection is not found, the
device attempts to establish a wireless network connection.
(In a wireless LAN only) Scan for an access point. The
device scans the RF coverage area. The device searches
the network profiles and scans for access points that contain a matching
Service Set Identifier (SSID) and authentication type. The device associates
with the access point that matches the network
(In a wireless LAN only) Authenticate with the access point.
device begins the authentication process.
stored device image. The
device has nonvolatile flash memory in which the device stores
firmware images and user-defined preferences. At startup, the device runs a
bootstrap loader that loads a firmware image that is stored in flash
memory. Using this image, the device initializes the software and hardware.
VLAN. If the
device is connected to a Cisco Catalyst switch, the switch next
informs the device of the voice VLAN that is defined on the switch. The device
needs the VLAN membership information before it can proceed with the Dynamic
Host Configuration Protocol (DHCP) request for an IP address.
Obtain an IP
address. If the
device is using DHCP to obtain an IP address, the device queries the
DHCP server to obtain one. If you are not using DHCP in your network, you must
assign static IP addresses to each device locally.
TFTP server. In addition to assigning an IP address, the DHCP server directs
the device to a TFTP Server. If the device has a statically defined IP address,
you must configure the TFTP server locally on the device; the device then
contacts the TFTP server directly.
also assign an alternate TFTP server to use instead of the server that DHCP
CTL file. The TFTP server stores the CTL file. This file contains the
certificates that are necessary to establish a secure connection between
the device and
Cisco Unified Communications Manager.
ITL file. The device requests the ITL file after it requests the CTL file. The
ITL file contains the certificates of the entities that the device can trust.
The certificates are used to authenticate a secure connection with the servers
or to authenticate a digital signature that is signed by the servers.
Cisco Unified Communications Manager 8.5 and later supports the ITL file.
configuration file. The TFTP server has configuration files, which define
parameters for connecting to
Cisco Unified Communications Manager and other information for the device.
Cisco Unified Communications Manager. The configuration file defines how the
device communicates with
Cisco Unified Communications Manager and provides a device with the load ID. After it obtains the
file from the TFTP server, the device attempts to make a connection to the
Cisco Unified Communications Manager on the list.
security profile of the device is configured for secure signaling (encrypted or
authenticated) and the
Cisco Unified Communications Manager is set to secure mode, the device makes a TLS connection.
Otherwise, the device makes a nonsecure TCP connection.
If the device
was manually added to the database,
Cisco Unified Communications Manager identifies the device. If the device was not manually added to
the database and autoregistration is enabled in
Cisco Unified Communications Manager, the device attempts to autoregister in the
Cisco Unified Communications Manager database.
Autoregistration is disabled when you configure the CTL client.
In this case, you must add the device to the
Cisco Unified Communications Manager database manually.
If the device
is booting for the first time, display the
Welcome screen and run the Setup Assistant.