Category:HowTo:Hot Desking

Configuration

Follow the instructions given in the User Manual, page 79/80:

Basic Support

You can log off all SIP accounts from the Web User Interface:

 Setup -> Identity X -> Login Tab -> Login Information -> Remove all identities
 Setup -> Identity X -> Login Tab -> Login Information -> Remove all identities

or by pressing a pre-defined key from the Phone User Interface:

Therefore one has to configure the following settings via Web User Interface first:

 /  Setup -> Function Keys -> Px -> Context: <Active>
 /  Setup -> Function Keys -> Px -> Type: <Key Event>
 Setup -> Function Keys -> Number: F_LOGOFF_ALL
 Setup -> Function Keys -> Number: F_LOGOFF_ALL

Additionally the "Logon Wizard" has to be activated:

 /  Logon Wizard: ON

Enhanced Support

You can log off all SIP accounts by pressing a pre-defined key from the Phone User Interface and log on a new user

Note: Your VoIP PBX must support this functionality. This feature is only available from firmware release 7 onwards. The following settings must have been configured on the Web User Interface in advance:

Setup -> Function Keys -> Px -> Context: <Active>
Setup -> Function Keys -> Px -> Type: <Key Event>
 (7.1.33) Setup -> Function Keys -> Number: F_LOGON_USER

Additionally the "Logon Wizard" has to be activated:

 Logon Wizard: ON

In order to use automatic provisoning the following Action URLs have to be configured as well:

 Setup -> Action URL Settings: Log Off: This URL should be used to inform the web server about the deregistration, e.g.:
http://server/usermanagement.php?logoff=true&user=$user_name1
 Setup -> Action URL Settings: Log On:  This URL should be used to inform the web server about the successful registration (SIP OK), e.g.:
http://server/usermanagement.php?logon=true&user=$user_name1&registrar=$user_host1
 Setup -> Action URL Settings: Registration Failed:  This URL should be to inform the web server about a unsuccessful registration, 
which might be a desired effect in case of incomplete authentication e.g.:
http://server/usermanagement.php?logon=true&user=$user_name1registrar=$user_host1

Process Flow

1) We consider the following configuration has been provided via Mass Deployment in advance

...
dkey_snom!: keyevent F_LOGON_USER
..
action_log_on_url!: http://192.168.0.80/test.htm?logon=true&user=$user_name1&registrar=$user_host1
action_log_off_url!: http://192.168.0.80/test.htm?logoff=true&user=$user_name1&registrar=$user_host1
action_reg_failed!: http://192.168.0.80/test.htm?logon=false&user=$user_name1&registrar=$user_host1
..
logon_wizard!: on
...

2) By pressing the pre-programmed "snom" function key, the following screen is shown:

3) If you confirm, all currently configured extensions (SIP identities) will be unregistered immediately and their configuration data deleted from the phone:

The SIP Trace page shows:

Sent to ...

REGISTER sip:intern.snom.de SIP/2.0
Via: ...
From: <sip:484@intern.snom.de>...
To: <sip:484@intern.snom.de>
Call-ID: ...
CSeq: 30 REGISTER
Max-Forwards: 70
Contact: ...
...
Expires: 0
Content-Length: 0

Received from ...

SIP/2.0 200 Ok
Via: ...
From: <sip:484@intern.snom.de>...
To: <sip:484@intern.snom.de>...
Call-ID: ..
CSeq: 30 REGISTER
Content-Length: 0

The Log Trace page shows:

[2]10/6/2008 11:25:56: Sending post request host = 192.168.0.80:80, file = /test.htm?logoff=true&user=484&registrar=intern.snom.de&mac=0004132XXXXX
[1]10/6/2008 11:25:56: Received 200 Ok on REGISTER without expiry indication, assuming 0s

Result:

1. The SIP registrar, e.g. "intern.snom.com", confirmed the de-registration of "484@intern.snom.de".
2. The Webserver, e.g. 192.168.0.80, has been informed that "484@intern.snom.de" has logged off from the phone with mac address 0004132XXXXX.

In addition the logon wizard will be shown on the display:

4) Press a key and enter the new extension to log on, e.g. 484

5) Confirm with . and enter the registrar of the new extension to log on.

Note: If the registrar configuration parameter (user_host is empty the DNS domain delivered via DHCP will be used here instead.

6) The phone attempts to register the new user. Usually an authentication is required and the user will be prompted for:

Note: This is done for security reasons; however the administrator should consider defining passwords which can be entered easily by the user, e.g. only numbers to avoid switching the input mode.

7) If the registration succeeds the "Log On" Action URL will be send to the web server:

[2]10/6/2008 11:45:47: Registered at registrar as 484@intern.snom.de (Expires: 178 secs)
[2]10/6/2008 11:45:47: Sending post request host = 192.168.0.80:80, file = /test.htm?logon=true&user=484&registrar=intern.snom.de&mac=0004132XXXXX

8) In order to provide a fully customized configuration to user "484@intern.snom.com" the web server should send a reboot request to the phone. This can be done via

• HTTP GET:

http://phone_IP_address/advanced.htm?reboot=Reboot

or preferrably via

• SIP NOTIFY:

NOTIFY sip:484@phone_IP_address SIP/2.0
Via:
From:
To:
Event: check-sync;reboot=true
Call-ID: 123456789@192.168.1.130
CSeq: 1300 NOTIFY
Contact:
Content-Type: application/simple-message-summary
Content-Length: 0

9) The phone reboots and retrieves its configuration parameter set from the web server, e.g. 192.168.0.80, according to its MAC address and user account information.

This category currently contains no pages or media.