Boot and Provision Sequences (AudioCodes and Genesys Phones)

The behavior of AudioCodes and Genesys phones when powering on is helpful while troubleshooting a phone to understand what it is doing during startup. Unlike a Polycom phone, AudioCodes  and Genesys phones do not have separate boot and provision sequences. The units power on and then go directly into the provisioning sequence.

Firmware boot/provisioning sequence

Following is the firmware boot and provisioning sequence for AudioCodes and Genesys phones:

• Phone powers on and does CDP and/or LLDP discovery, depending upon configuratio

  • Gets port-mode configuration

  • Gets VLAN information (if any)

• Phone runs through DHCP discovery

  • DHCP must return:

    • IP Address

    • Option 1 - Subnet Mask

    • Option 15 - DNS server

  • DHCP should return:

    • Option 3 - Router to contact devices outside of subnet

    • Option 66 - TFTP Server Address

    • Option 67 - Bootfile Name (usually 420HD.img)

    • Option 160 - Provision server address (usually the CIC server or a provisioning proxy)

  • DHCP may return:

    • Option 4/42 - Network time servers

    • Option 2 - Time offset

• Phone queries DNS for the provision server found in Option 160

  • If not found, the phone boots with its old configuration

• Phone sends HTTP GET request for the Bootfile to the Provision Serve

  • It pulls a portion of the file and checks whether it matches its current firmware

  • If it doesn't match, the phone GETS the complete file, flashes the firmware to its memory, and then reboots

• Phone sends HTTP GET request for other config files listed with the CUSTOM::config_files attribute specified

• Phone sends HTTP GET request for <MAC>.cfg to the Provision Serve

• Phone attempts to register with its configured SIP prox

• If the configuration file changed, the phone reboot

Custom configuration files

The provisioning server supports the ability to add a custom attribute to AudioCodes and Genesys phones named config_files (case-insensitive), which must contain a comma-separated list of files. If the file exists in the \i3\ic\provision\AudioCodes directory on the CIC server, provisioning includes the files in the config_files list for AudioCodes phones. If the file exists in the \i3\ic\provision\Genesys directory on the CIC server, provisioning includes the files in the config_files list for Genesys phones.

The system requests these files after provisioning generates the config files and allows administrators to set custom config file attributes that provisioning doesn't handle.

Following is the format of the custom configuration files.

The Configuration file is a *.cfg file with the file name specified in the list under the config_files custom attribute.

Ensure that the configuration file adheres to the following guidelines:

• No spaces on either side of the equals (=) sign.

• Each parameter is on a new line.

• Each parameter has the following syntax: <parameter name>= <value>

Following is an example of part of a configuration file:

voip/line/0/enabled=1
voip/line/0/id=1234
voip/line/0/description=310HD
voip/line/0/auth_name=1234
voip/line/0/auth_password=4321 

Phone simulator

A quick way to check what configuration passes to a phone is to use PhoneSim.exe, a PureConnect tool that simulates the provisioning requests for managed IP phones. For more information, see "Phone simulator" in Boot and Provision Sequences (Polycom).