Specifications

Aastra July 2014 PA-001011-03-04
154
3.11 PhoneConfiguration Object (all models)
The PhoneConfiguration object allows an external application to modify the phone
configuration dynamically. The configuration parameters are the ones that are used in the
configuration files (aastra.cfg and <MAC>.cfg) and detailed in the administrator guide.
3.11.1 Implementation
The phone parameters have 2 levels of precedence: ‘server’ where the parameters are coming
from the configuration files and ‘local where the parameters are locally set via the TUI or WebUI.
The ‘local’ parameters override the ‘server’ parameters.
The AastraIPPhoneConfiguration object supports a parameter called ‘setType’ which allows
defining at which level the parameter change will apply.
 remote - parameter will be saved with the same precedence as the server settings. This
set will not persist through a reboot.
 local - parameter will be saved with the same precedence as TUI or WebUI settings. This
set will persist through reboots of the phone. The only way to unset this type is via the TUI,
WebUI, or another local type set.
 oneBoot - parameter will be saved with a precedence above server settings and below
local settings. This parameter will persist through a single reboot and be lost after that.
Using this value for setType anywhere in the object will cause the phone to reboot when
the AastraIPPhoneConfiguration object is done parsing
 override - parameter will be saved with the same precedence as server settings. This is
different from remote because it will also override a conflicting local value. This override
will persist through a reboot but the new value will be lost.
Note: Default value is ‘remote’ as it was the object behavior prior to firmware release 2.4.0.
If setType is set in the AastraIPPhoneConfiguration root tag, it affects all of the ConfigurationItem
sub-elements but when set in the ConfigurationItem tag it will affect that set only (override the
global setting for the object).
The number of parameters to be sent in a single Phoneconfiguration object is only limited by
the overall size of the XML object (10000 bytes). Practically 30 parameters can be sent in a single
object.
Note: Not all the configuration parameters are dynamic; specifically the network parameters
are static and need a reboot.
The list of the dynamic configuration parameters is detailed in section 14.
Default Softkeys
Not Applicable, this object is a non UI XML object and has no predefined softkey.
3.11.2 XML Description
<AastraIPPhoneConfiguration
Beep = “yes/no”
triggerDestroyOnExit = “yes/no”
setType = “remote/local/oneBoot/override”
>