Installation guide

Operational Features
5-203 41-001561-00 REV00 – 10.2014
Enabling the beep is an indication to the phone to sound a beep when it receives an AastraIPPhoneStatus object. If you
disable the beep, or no AastraIPPhoneStatus object appears in the status message, then the default behavior is no beep
is heard when the object arrives to the phone.
The value set in the configuration files and Mitel Web UI override the attribute you specify for the AastraIPPhoneStatus
object.
For example, if the AastraIPPhoneStatus object has the attribute of Beep=”yes”, and you uncheck (disable) the “XML
Beep Support” in the Mitel Web UI, the phone does not beep when it receives an AastraIPPhoneStatus object.
Setting the BEEP option in the configuration files and the Mitel Web UI applies to the phone immediately.
Reference
For information about enabling/disabling the XML beep in the Mitel Web UI, see “XML Beep Support” on page5-60.
Scroll Delay Option for Status Messages
The IP phones support a scroll delay option that allows you to set the time delay, in seconds, between the scrolling of
each status message on the phone. The default time is 5 seconds for each message to display before scrolling to the next
message. You can configure this option via the configuration files or the Mitel Web UI.
You can use the following to set the scroll delay for status messages:
• xml status scroll delay (via the configuration files)
• Status Scroll Delay (seconds) (via the Mitel Web UI)
Changes apply to the phone immediately.
Reference
For more information about configuring status scroll delay, see “Status Scroll Delay” on page5-61.
XML Configuration Push from the Server
The IP phones provide an XML feature that allows you to make configuration changes to the phone that take affect
immediately, without having to reboot the phone. This feature involves creating XML scripts that push the changed con-
figuration parameter(s) from the server to the IP phones.
You can use the AastraIPPhoneConfiguration object in the XML scripts to change configuration parameters or config-
ure new parameters. However, since the IP phone does not save new parameters created in XML scripts to the local.cfg
file, when the phone reboots, it does not save the new parameters on the phone. In order for the phone to apply new
configuration parameters, you have to enter the parameters via the user interfaces (Telephone User Interface, Web User
Interface, or configuration files), or reapply the new parameters using the XML scripts after every boot.
Specific configuration parameters are dynamic on the phone when pushed from XML scripts on the server. See the XML
Developer’s Guide for more information about XML configuration scripts and dynamic configuration parameters.
For more information about creating XML configuration scripts and for XML script examples, see the XML Developer’s
Guide.
Configuring the Phone to use XML
You can configure the phone to request the XML objects you create by configuring specific parameters via the configura-
tion files or the Mitel Web UI.
Users can access XML applications via softkeys configured on the IP phones. The phone performs an HTTP GET on the
URI configured in the Mitel Web UI or configuration files.
You configure the following parameters for object requests:
• xml application URI
• xml application title
The xml application URI is the application you are loading into the IP phone.