Specifications

Aastra July 2014 PA-001011-03-04
242
10 Phone Self-Configuration using XML
10.1 Introduction
The deployment of a SIP phone is not a simple task; you have to face 2 challenges:
1. Provide the address of the configuration server to the phone
2. Link the MAC address of the phone with a SIP extension
The first challenge is usually solved by using DHCP option 66 (bootp) to provision the phone with
the IP address/name of the configuration server (TFTP, FTP, HTTP or HTTPS).
The second challenge is more difficult as you have to know the MAC address of the phone in
advance in order to prepare the specific configuration file the phone will use. Usually, each phone
is identified (scan of the MAC address) and then linked to an extension.
It is possible to have a complete self-configuration of the phone using an XML application called by
the action uri startup at the end of the boot sequence.
10.2 Message flow
It is possible for a third-party to develop an automatic configuration process. The following is a
description of how this can be done using existing phone features.
1. The aastra.cfg file sets the startup action uri configuration parameter to point to the
configuration script and configuration download information.
2. Phone downloads the aastra.cfg file, ignores missing <MAC>.cfg file and continues boot
process.
3. Phone executes startup uri, running the configuration script. The MAC address of the
phone and the phone model are in the HTTP headers of the request.
4. The script uses XML to gather required configuration information and creates <mac>.cfg
file. The <mac>.cfg file must reset the startup action uri to avoid the configuration script
being called on subsequent boots.
5. The script reboots the phone via XML reboot command or via SIP check-sync message.
6. Phone reboots, directly downloads both aastra.cfg and newly created <MAC>.cfg file