Auto provisioning with TFTP

Needed:

  • 1 DHCP server which one can manage the options
  • 1 TFTP server
  • 1 Thomson ST2030 (SIP or MGCP)
  • Several files which one can need (correctly filled) are:
    • SIP: File INF, Firmware, File "common_config", File MAC specific and File "Telconf"
    • MGCP: File INF, Firmware, Files Desk, File "common_config", File MAC specific and File "Telconf"

The files:

File INF: (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

File "common_config": (extension .txt). informs the phone about configurations which need to be upgrade on the level network, SIP (or MGCP), auto provisioning, etc...

File MAC: (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.

File "Telconf": (extension .txt), a continuation of Telnet command, which configure the phone on many parameters.

Files Deck: (ONLY MGCP) (extension .thd), allow phone to know how to display some flows (xml) on screen. Generally, it is files which are sent via the operator chosen to connection to the service.

Note: We provide often to the customer only the upgrade firmware. The other files are normally managed by the administrator who takes care of the procedure of auto provisioning.

(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: File INF's name on TFTP server

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

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

Option Next server address: IP address of TFTP server used in some case when the other options are not manageable but this one yes.

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" (ear-phone) and "transfert" (dumb) of the phone.
  3. Connect phone with electricity. Maintain the keys "headset" (ear-phone) and "transferts" (dumb) 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 of file INF which will be downloaded) and will begin the process of auto provisioning.

1/ In the order:
  • Remote of file INF
  • Remote loading of the firmware
  • (Remote loading of the files Deck for MGCP)
  • Reboot
  • 2nd Remote loading of file INF
  • (2nd Remote loading of the files Deck for MGCP)
  • Remote loading of the file TelConf
  • Remote loading of the file Common_config
  • Attempt of remote loading of the specific file MAC if he is
  • Reboot
  • Remote loading of file INF
  • (2nd Remote loading of the files Deck for MGCP)


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 compared to the last upgrade.

  • The specific file MAC is downloaded (if there exists) if his parameter "config_sg" was incremented.

  • It is imperatively necessary to download the file TelConf before returning it to the customer.

  • It is possible to pass from aphone SIP and quite simply to transform it into MGCP (but not the reverse) by providing on phone SIP a firmware corresponding to MGCP protocol as well as the good files which go with.


Needed:

  • 1 DHCP server which one can manage the options
  • 1 TFTP server
  • 1 Thomson ST2030 (SIP or MGCP)
  • Several files which one can need (correctly filled) are:
    • SIP: File INF, Firmware, File "common_config", File MAC specific and File "Telconf"
    • MGCP: File INF, Firmware, Files Desk, File "common_config", File MAC specific and File "Telconf"

The files:

File INF: (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

File "common_config": (extension .txt). informs the phone about configurations which need to be upgrade on the level network, SIP (or MGCP), auto provisioning, etc...

File MAC: (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.

File "Telconf": (extension .txt), a continuation of Telnet command, which configure the phone on many parameters.

Files Deck: (ONLY MGCP) (extension .thd), allow phone to know how to display some flows (xml) on screen. Generally, it is files which are sent via the operator chosen to connection to the service.

Note: We provide often to the customer only the upgrade firmware. The other files are normally managed by the administrator who takes care of the procedure of auto provisioning.

(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: File INF's name on TFTP server

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

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

Option Next server address: IP address of TFTP server used in some case when the other options are not manageable but this one yes.

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" (ear-phone) and "transfert" (dumb) of the phone.
  3. Connect phone with electricity. Maintain the keys "headset" (ear-phone) and "transferts" (dumb) 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 of file INF which will be downloaded) and will begin the process of auto provisioning.

1/ In the order:
  • Remote of file INF
  • Remote loading of the firmware
  • (Remote loading of the files Deck for MGCP)
  • Reboot
  • 2nd Remote loading of file INF
  • (2nd Remote loading of the files Deck for MGCP)
  • Remote loading of the file TelConf
  • Remote loading of the file Common_config
  • Attempt of remote loading of the specific file MAC if he is
  • Reboot
  • Remote loading of file INF
  • (2nd Remote loading of the files Deck for MGCP)


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 compared to the last upgrade.

  • The specific file MAC is downloaded (if there exists) if his parameter "config_sg" was incremented.

  • It is imperatively necessary to download the file TelConf before returning it to the customer.

  • It is possible to pass from aphone SIP and quite simply to transform it into MGCP (but not the reverse) by providing on phone SIP a firmware corresponding to MGCP protocol as well as the good files which go with.


Created by: bringe, Last modification: Tue 24 of Apr, 2007 (04:05 UTC) by chandave
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+