Device Activation
Ever wonder what happens during the activation process? This is a high-level look at the activation process. Should also help in the troubleshooting process. Activation and Download of config use ports TCP 443, UDP 5060, UDP 2222.
What you need to know about device activation
Device activation is the process of 8x8 associating a user to a device and configuring the device for that user. This is an automated process that can be done in 2 different ways
- Call from a device with an activation code
- Manual MAC address association via the Admin Console
What happens under the hood (call from the device)
Assumption user enters proper activation code and is for a Poly device. Other devices Cisco, Yealink, etc work basically the same way but deal with different servers.
The device is pulled out of a cardboard box, connected to the network. The device contacts the Poly ZTP service to configure the device (TCP Port 443). FIRST, it checks is there a config on the 8x8 side, if not then it "registers" to the "activation server"
- SIP over port UDP 5060 (not SRTP)
- Audio over UDP 2222
- MAY be affected by ALG
Next, the device reboots with a new config from the Poly ZTP server and the "activation button" appears on the device screen. IF there is NO Activation Button
- NTP is blocked, the device cannot get the correct Date & Time
- NTP is required to function as if the time/date is wrong device certificate verification cannot take place thus unable to download config
- Poly ZTP service is blocked on customers firewall/network TCP Port 443
The user presses the activation button
The user SHOULD hear activation service (a simple Auto-Attendant), if the call fails then Port UDP 5060/ALG has an issue dig into ports and if ALG is enabled. IF no audio is received then port UDP 2222 is blocked, options are to unblock port UDP 2222 or just enter the activation code (and hope for the best).
During the call setup, the activation server checks the "user-agent" UA which contains the "device type" (aka Poly VVX 500) the UA is part of the SIP Message. If the device type matches the device assigned to the user via Admin Console, the Activation Service uses the MAC address obtained from the SIP message to create the device configuration file. If the device type does not match, a message is played "Device type is incorrect..."
Once the device configuration file is built a SIP option packet is sent to the device to trigger it to update its configuration. This usually takes 2-3 reboots (1. to download the config, 2. enable/use the config 3. sometimes a firmware change). The device is registered and ready to be used at this point. Should the device reboot with the activation button again then port TCP 443 is blocked, 8x8 subnets are blocked, or NTP is not working (NTP is required to function as if the time/date is wrong device certificate verification cannot take place thus unable to download config).
Difference between "Call from device" and "Manual activation"
The only difference between the "Call from device" and "Manual activation" is that the manual activation process does not do the device check, and simply builds the config and when the device checks the server for a config file it is found and is used. Same restrictions on NTP.
------------------------------
Paul Chase
8x8 Network Engineer (Pre-Sales and Deployment)
------------------------------