Installation guide

Advanced Operational Features

6-47 41-001561-00 REV00 – 10.2014

For example, if the “user config url” parameter is defined with valid HTTP, HTTPS, FTP, or TFTP server credentials and an

unsolicited NOTIFY message containing the following XML body is received by phone:

<Parameter>hot desk username</Parameter>

</ConfigurationItem>

</AastraIPPhoneConfiguration>

the phone connects to the defined server, downloads the “john.cfg” and “john_local.cfg” files containing all the applica-

ble saved settings and information for that particular user, and configures the phone according to the “john.cfg” and

“john_local.cfg” files.

The phone is updated with the respective user’s profile, which contains the user’s phone preferences (e.g. key configura-

tion as well as settings configurable through the Options List), Callers and Redial Lists, Directory contents, etc...

When the user logs out ( through an IVR for example, or by pressing the “Log Out” softkey), the “<user>_local.cfg” file is

saved and another unsolicited NOTIFY message (containing an XML body without a value defined for the “hot desk user-

name” parameter) as per the following:

<Parameter>hot desk username</Parameter>

</ConfigurationItem>

</AastraIPPhoneConfiguration>

is sent by the call manager to the phone. Without a value defined for the “hot desk username” parameter in the XML

body, the user is logged out and the phone reverts back to the generic visitor account.

If using the “Login” key method, Administrators can define in the configuration files a programmable key, top or bottom

softkey, or expansion module key type as “hotdesklogin” or configure a “Login” key using the Web UI.

Note:

For details on how to configure softkeys and programmable keys using the configuration files see

Softkey Settings on

page A-175

, Programmable Key Settings on page A-183, and Top Softkey Settings on page A-187.