Specifications

PA-001011-03-04 Aastra July 2014
243
Figure 100: Auto-configuration message flow
10.3 Auto-configuration policy
The auto-configuration policy which includes the flow of questions asked to the user and the script
to generate the <MAC>.cfg file is totally open with this mechanism.
Multiple options are available.
Extension is already provisioned in the IP-PBX database.
One way to implement this feature might be to have all the extensions already provisioned on the
switch side and the XML flow will be used to identify the user (extension number and voicemail
password for instance). The script must then control if the extension is not already assigned and
create the <MAC>.cfg based on the extension(s) configuration.
Another way would be to display the list of available extensions and let the user select his
extension; of course password protection is needed to avoid any hacking of the platform.
Extension is not provisioned in the IP-PBX database
A second option is to have the script to provision the extension in the database. To do so, the script
can ask for user general parameters (name…) and automatically creates an extension in the switch
Phone
Server
Request for aastra.cfg
Phone reboots
Gets IP address
Gets
Configuration
Server
parameters
Request for <MAC>.cfg
aastra.cfg (configured with a startup URI)
No <MAC>.cfg
Startup URI
XML questions and answers
XML “Reset”
Script creates
<MAC>.cfg