Installation guide

Additional Information

RN-001039-00 REV00 – 10.2014 83

Logging In and Out

For logging in and logging out, a NOTIFY message containing an XML body that

includes the parameter “hot desk username” with a valid username value to the

phone must be triggered. The method of triggering this NOTIFY message can be

phone-initiated (by configuring a “Login” key) or initiated through a different method

(e.g. through use of an Interactive Voice Response [IVR] system).

To log in to a specific user profile, the user could, if configured, press the “Login” key

on the phone or call an IVR set up for the VDP log in/log out process (or any other

alternative method configured).

If the “Login” key is pressed, the phone will prompt the user for the username and

password. If the server does not support authentication or if the server is set up for

anonymous connections, the username is all that is required and corresponds to the

filename of the <user>.cfg file (e.g. john). If the server is configured with login creden-

tials, both the username and password are required. The username in this case corre-

sponds to both the server username credential and <user>.cfg file (i.e. the server user-

name and <user>.cfg file name must match) and the password corresponds to the

server password credential.

When the user’s credentials are confirmed, this triggers the call manager to send an

unsolicited NOTIFY message containing an XML body that includes the parameter

“hot desk username” with a valid value to the phone. The phone then contacts the

configuration server (defined by the “user config url” parameter) and downloads the

subscribers profile contained in the “<user>.cfg” and “<user>_local.cfg” files.

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 follow-

ing XML body is received by phone:

<Parameter>hot desk username</Parameter>

</ConfigurationItem>

</AastraIPPhoneConfiguration>

Note:

The “<user>.cfg” file contains read-only server-related configuration information

that is not configurable by the user and the “<user>_local.cfg” file contains the user

configuration information that has been changed by the user locally either through

the phone’s UI or through the Web UI.