Auto provisioning with TFTP for ST2030

Needed:

  • 1 DHCP server with manageable options
  • 1 TFTP server
  • 1 ST2030 (SIP or MGCP)
  • Several specific files:
    • SIP: INF file, Firmware, "common_config" file, MAC specific file and "Telconf" file.
    • MGCP: INF file, Firmware, Deck files, "common_config" file, MAC specific file and "Telconf" file.

The files:

INF file: (extension .txt or .inf) informs about the place of the various files to download (relative way or absolute)

Firmware: Version's code which needs to be upgrade by the phone

"common_config" file: (extension ".txt"). informs the phone about its configuration: Network, Users, Provisioning...

MAC file: (extension ".txt"). Same that the file "common_config" but its name is based on phone's MAC address which needs to be upgrade and the configuration which is made inside will concern only the phone which has this MAC address. It has priority if the two files are on TFTP server.

"Telconf" file: (extension ".txt"), specific low level commands.

Deck files: (ONLY MGCP) (extension ".thd"), allow phone to know how to display some flows (xml) on screen. Generally, those are sent by the operator.

(See examples of these files in Appendix)

DHCP option:

Option 66: IP address of TFTP server where are the files which need to be download.

Option 67: INF filename on TFTP server

Option 150: IP address of TFTP server used if this option (optional) is in DHCP options

Option 43: Used for HTTP upgrade. If options 66 or 150 are not present, option 43 will be chosen.

Option Next server address: IP address of TFTP server used in some case when all other options were not set.

Put in the following way in the file of configuration of DHCP (dhcpd.conf)
Click on the picture
Image



Plateform's installation

  • Installation of the DHCP server: To set up all the necessary options (option 66 and 67)

  • Installation of the TFTP server: To put in the repertory of the TFTP server the last version of the firmware

  • Provisioning process

Process of auto provisioning in theory:
At time of the connection of a phone to the network, it will ask an IP address to DHCP server. This one will provide him an IP address but also the address of TFTP server where file INF is. This file will indicate on the phone the configuration file names which it must upgrade.

Process of auto provisioning in the practice:
  1. Do not connect the phone with electricity. To put the cable (RJ45) in the Ethernet LAN port at the back of the phone
  2. Restore the default parameters. With this intention, it is necessary to maintain inserted the keys "headset" and "mute" of the phone.
  3. Connect phone with electricity. Maintain the keys "headset" and "mute" of the phone inserted, until seeing that the provisioning is carried out.
  4. The phone will start (it will recover an IP address by DHCP server, the IP address of TFTP server and the name INF file which will be downloaded) and will begin the process of auto provisioning.

1/ In the order:
  • INF file download
  • Firmware download
  • Reboot
  • INF file download
  • TelConf file download
  • Common_config file download
  • MAC specific file download (if present)
  • Reboot
  • INF file download

2/ The phone is connected to the service of the operator.

Some precise details:

  • If phone doesn't receive an IP address, you need to check up that the parameter Mode->DHCP is activated

  • The file "Common_config" will be downloaded only if the file's name has been change since the last upgrade.

  • The MAC specific file will be used only if it exists and if parameter "config_sn" was incremented into it.



Created by: bringe, Last modification: Mon 19 of Feb, 2007 (16:14 UTC) by bpy


Please update this page with new information, just login and click on the "Edit" or "Discussion" tab. Get a free login here: Register Thanks! - Find us on Google+

Page Changes | Comments

 

Featured -

Search: