A free, simple, easy-to-implement, standards-based,
feature-rich dialtone for your SIP hardware or softphone...

Engineers Testing or Implementing Plug-N-Dial

Provisioning Method:

The TFTP Provisioning Method is defined as follows:

Step 1: Retrieve Configuration File

The directory structure of the APS server is "2 deep". To determine the directory location of a given device's SIP configuration file, use the first four digits of the MAC address as the parent directory and the second four digits of the MAC address as the subdirectory. For example, the path of the SIP configuration file for a device identified by MAC address 000b820c2371 is as follows:

/000b/820c/000b820c2371.txt

At boot time the SIP device should initially attempt to download the MD5 checksum from the Automatic Provisioning System. This is done by placing a TFTP request to the APS server which has a TFTP server running to accomodate this request.

Example: A TFTP get request is sent to an APS server to retrieve /000b/820c/000b820c2371.md5

If the checksum has not changed since the last reboot. The SIP device should jump to Step 2 .

Otherwise the device will determine that the checksum differs from that of the currently loaded SIP configuration file, the device must then request the SIP configuration file from our APS server.

Example: A TFTP get request is sent to an APS server to retrieve /000b/820c/000b820c2371.txt

After downloading the SIP configuration file the device must load the settings from the file, perform a soft reboot and the device will return to beginning of the Auto Provisioning Process.

The checksum file must be stored in a file with the same path and filename as the SIP configuration file with the a ".md5" extension.

Example: /000b/820c/000b820c2371.txt is in the same directory as /000b/820c/000b820c2371.md5

Step 2: Automatic Firmware Updates

Current Version URI $/firmware/<OEM>/<Model/Make>/currentversion.txt

Example:A TFTP get request is sent to an APS server to retrieve /firmware/leadtek/BVA8051/currentversion.txt

The currentversion.txt file must contain the current firmware version to be used, and may contain OEM specific information that applies to all the devices for that manufacturer

Example:

Image_file="some_file_format.bin"
Prom_file="some_other_format.blah"

The device should then determine from the currentversion.txt file whether a firmware update is required. If an update is not required then the device should then continue in the boot process, otherwise the device must download the file from our server.

To download the firmware the format of the request should be like the following:

Firmware File URI $/firmware/<OEM>/<Model/Make>/<filename_from_currentversion.txt>

Example:A TFTP get request is sent to an APS server to retrieve /firmware/leadtek/BVA8051/some_file_format.bin

After the device has downloaded the firmware the device must update, reboot, and return to the beginning of the Auto Provisioning process.