Installation guide

Additional Information
84 RN-001039-00 REV00 – 10.2014
the phone connects to the defined server, downloads the “john.cfg” and
“john_local.cfg” files containing all the applicable 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 configuration 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 username” param-
eter) as per the following:
<AastraIPPhoneConfiguration setType="override">
<ConfigurationItem>
<Parameter>hot desk username</Parameter>
<Value></Value>
</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 “hotdesk-
login” or configure a “Login” key using the Web UI.
Note:
Screen language settings are also updated to match the user’s configuration, but
the language file must be loaded on the phone for the screen language setting to
take effect.