A free, simple, easy-to-implement, standards-based,
|
|
At boot time the SIP device should initially attempt to download the encrypted configuration file from the Automatic Provisioning System. This is done by placing a HTTPS request to the APS server which has a HTTPS server running to accomodate this request.
Example: A HTTPS get request should be formatted as follows:
https://<SERVER>/<Make/Model>/app?class=<Make/Model>;mac_address=xxxxxxxxxx
The format of the return file can be either in plaintext / XML / encrypted:
For example:
The SIP device updates via HTTPS with a plaintext response then the field format will be as follows
sip_server="proxy01.sipphone.com"
sip_server_port="5060"
local_rtp_port="5004"
local_sip_port="5060"
codec3="G711u"
The SIP device updates via HTTPS using XML then the field names would directly translate as follows:
<sip_server>
proxy01.sipphone.com
</sip_server>
<sip_server_port>
5060
</sip_server_port>
The SIP device updates via HTTPS w/ encryption then the field names would directly translate as follows:
<xml>
<flat-profile>
<ENC>
c7fc19404e0b0bcc8885d31f2d8ff7e8e09f0e28......
</ENC>
</flat-profile>
<sessionData>
<proc>provision</proc>
<class>OEM</class>
</sessionData>
</xml>
The firmware updating process is accomplished by first grabbing a file "currentversion.txt" and determining from the contents of that file whether it is necessary to download the new firmware.
https://<SERVER>/firmware/<OEM>/<Model/Make>/currentversion.txt
An Example of this would be: https://aps.sipphone.com/firmware/leadtek/LR8051S/currentversion.txt
Contents Example:
Image_file="some_file_format.bin"
Prom_file="some_other_format.blah"
After the device has downloaded the firmware the device must update, reboot, and return to the beginning of the Auto Provisioning process.