Snom Hot Desking with 3CX Phone System
pixel500w-500x1
Zero Admin
With the new Dashboard
pixel500w-500x1
Bulletproof Security
With SSL certs and NGINX
pixel500w-500x1
Install on $150 Appliance
Intel MiniPC architecture
pixel500w-500x1
New, Intuitive Windows Client
More themes, more UC
pixel500w-500x1
More CRM Integrations
Scripting Interface to add your own
pixel500w-500x1
Improved Integrated Web Conferencing
iOS and Android apps included
pixel500w-500x1
Personal Click2Meet URLs

Snom Hot Desking with 3CX Phone System

Snom Hot Desking with 3CX Phone System

Snom Hot Desking with 3CX Phone System

Introduction

Prerequisites

Step 1: Installing Extended Service Package

Step 2: Provisioning Extensions for Hot Desking

Step 3: Switch extensions on same IP Phone

Limitations and general notes

Technical Information / Restoring Functionality

Step 4: Configuring SSO Functionality (Optional)

Step 4.1: Configure the User Accounts in Active Directory

Step 4.2: Configure Computer Settings in you AD

Step 4.3: Create Group Policy (Logon/Logoff) Scripts

Customising Scripts

Assigning Scripts

Limitations

Introduction

Hot Desking allows multiple employees to share the same IP Phone. For example in a 24 hour call center, multiple agents can share the same desk/IP Phone, at different times of the day. This in turn leads to a more efficient use of office space and equipment. Additionally you can configure SSO so that when a user logs in to a computer that is next to a Snom IP Phone the Phone will automatically log in and be configured to the user's extension based on their AD credentials.

To configure hot desking for your snom IP Phones:

  • Step 1: Install Extended Services
  • Step 2: Provision extensions for Hot Desking
  • Step 3: Switch extensions on the same IP Phone
  • Step 4: Configure SSO Functionality (Optional)

Prerequisites

  • 3CX Phone System V14 Single Instance
  • Snom IP Phone with Firmware 8.7.5.35

Step 1: Installing Extended Service Package

  1. Download the Extended Service Package

  1. Extract the ZIP files on the desktop of the 3CX Phone System host machine.
  2. Launch the install.bat which will only take a few seconds to complete.
  3. Once the installation has completed, a message box will appear, click ok.

      The extracted files will now be automatically deleted leaving behind only the files required for the snom sso.

Step 2: Provisioning Extensions for Hot Desking

  1. Visit our 3CX Support page and find the provisioning guide for your snom phone model. Follow the guide until you reach the Edit Extension settings” page .
  2. In the “Model” drop-down menu, instead of the default selected “Snom XXX” template, choose the “Snom XXX HotDesk” template. Where where XXX  is the model number of your phone.. For example: “Snom 320 HotDesk”.

Note: Each extension participating in Hot Desking, must be provisioned using the “Snom XXX HotDesk” template. After provisioning the first user, all subsequent users must be provisioned using a fake MAC address in the “MAC Address” field. This can be any 12 digit numeric string, for example: 012345678901

The first extension that is provisioned will be logged in and ready to use.

Step 3: Switch extensions on same IP Phone

The “Line 3” button on the phone will be used as the logoff key. Once pressed, the ID on the phone will be removed and a logon screen will be presented to the user.

To logon:

  1. Press a key to start the procedure.
  2. Enter the Extension Number.
  3. When prompted for the “Registrar” press ✓”. This is automatically filled in by the provisioning template to the IP:Port of the PBX)
  4. Enter the Extension Password.

After logon, extensions will receive their individual BLF key setup and their name/logo on the screen. In addition 3CXPhone CTI mode can also be used.

Limitations and general notes

  • Hot Desking can be only used in office mode (LAN).
  • Firmware updates via the 3CX Management Console are only possible when the phone is registered to the extension that the phone was first provisioned.
  • An AutoLogOff timer can be added if needed: http://wiki.snom.com/Settings/auto_logoff_time
  • Support for SideCar D7 is Supported
  • Call History can not restored on the phone. To see call history use 3CXPhone.
  • On snom 300 no BLF keys will be restored to assure the basic functionality of the phone, as features like transfer use all available BLF keys on the phone.

Technical Information / Restoring Functionality

In case changes for a hot desking phone do not appear correct (the phones MAC address is in the provisioning tab) the phone has to be rebooted. The reason is that the web password for the phone itself is overwritten by the 3CX Management Console causing mismatches to the currently running web password that is taken from the logged on extension. An indicator for this can be seen on the phone after the user logs in - the display shows (ext@pbxip:port ) and not the full user name / logo as set in the management console. In this case reboot the phone from the device itself by dialing ‘**#’ and holding down ‘#’ on the keypad.

Step 4: Configuring SSO Functionality (Optional)

The Hot Desking functionality can be integrated with Active Directory. Once you complete these steps, when a user logs on to the computer using their AD credentials, the IP Phone configured with the computer will automatically switch to the user's extension.

To achieve this you will need to complete the following steps:

  • Configure the user accounts in Active Directory
  • Configure Computer Settings in you AD
  • Create Group Policy (Logon/Logoff) Scripts

Step 4.1: Configure the User Accounts in Active Directory

To enable SSO for users, the extension number of the user in 3CX Phone System must be set in the “IP phone” section of the user’s AD account.

To do this:

  1. Open “Active Directory Users and Computers” on your AD server
  2. Find and double click on the AD user that you want to enable SSO for, and switch to the “Telephones” tab. In the “IP phone” field, enter the extension number that the user is assigned to. For example, the user shown here is assigned the 3CX Phone System extension number 118.
  3. Repeat this step for all users requiring SSO.

Step 4.2: Configure Computer Settings in you AD

The computer that the users will be logging in to needs to be paired with the MAC address of the IP Phone that is located next to it.

To do this:

  1. Open “Active Directory Users and Computers” on your AD server.
  2. From the list of Computers, locate the name of computer that is located next to the IP Phone and double click on it.
  3. Switch to the “Location” tab, in the “Location” entry field enter the MAC address of the IP Phone that is participating in Hot Desking.
  4. Repeat this step for all the computers & snom IP Phone pairs.

Step 4.3: Create Group Policy (Logon/Logoff) Scripts

The next step is to create a Group Policy and apply it to all users participating in Hot Desking. You will need to assign one Logon and one Logoff script to this Policy.

Customising Scripts

Before assigning the scripts, you will need to customise them for your 3CX Phone System installation:

  1. From the ExtendedServices.zip locate the folder “SSO Snom”
  2. Edit both the “tcxlogonsso.bat” and “tcxlogoutsso.bat” files with a text editor like Notepad++.
  3. Locate “SET provdir=” in both files and replace the value with the FQDN which has been used to setup your 3CX Phone System. In case your Installation is not running on port 80 enter the port of your web server http://MYFQDN:5000 for example.

Keep the Explorer window containing the SSO files open as we will need to copy these files to the correct location in the SysVol folder

Assigning Scripts

  1. Open “Group Policy Management”.
  2. Navigate to Your Forest” > “Domains” > “Your Domain” > Right click on “Group Policy Objects” and select “New”.
  3. Name the new GPO “3CX SSO Scripts” and click “OK”.
  4. Select on the newly created GPO and switch to the “Settings” tab.
  5. Right click on “Users Configuration (Enabled)” and select “Edit”. The “Group Policy Management Editor” will open.
  6. Go to “User Configuration” > “Windows Settings” > Select “Scripts”.
  7. Double click on “Logon” and click “Show Files” in the “Logon Properties” window.
  8. An explorer window will open. Copy and paste all the three files in the “SSO Files directory”, that you have downloaded, to this folder. Close the window.
  9. Go back into the “Logon Properties” window, Click “Add...”, followed by “Browse” and locate the “tcxlogonsso.bat” file, in the “Add a Script” dialog. Click “OK” and then again in the “Logon Properties” window.
  10. Repeat the steps from “Step 7” onwards, but this time for the “Logoff” script and in “Step 9” choose the “tcxlogoutsso.bat” file.

11. When you have assigned both the Logon and Logoff scripts, return to the “Group Policy Management” window, right click on “3CX SSO Scripts”, in the tree view, select “Refresh” and verify that the correct script has been assigned to the correct action.

Note: Windows 8.1, Windows RT 8.1 and 2012 R2 server, delay executing logon scripts is set to 5 minutes by default. This will cause the IP Phone not to logon with the user's extension during this time. You may configure this to a smaller value, or 0 if your network link is directly available after boot up. To do this, go to: “Computer Configuration” > “Administrative Templates” > “System > Group Policy” > “Configure Logon Script Delay”.

Limitations

  • This cannot be used on Terminal Server as only one MAC address can be associated with the TS Server.
  • SSO does not support fast user switching.
  • Locking the desktop will not log off the IP Phone.

You might also be interested in:


Ask a Question

Please only post questions in regards to the document you are currently reading.
Technical support or pre sales questions must be posted via the support or sales channels and such comments will be deleted. Thank you for understanding

Leave a Reply

  1. Kevin Jones

    Can You confirm whether this is possible when using Abyss as the web server, as the Action URL settings used for log on and Log off are snom_hot.aspx which is an IIS file only, and the extended services files only update IIS not Abyss?

    November 17, 2016 at 8:39 pm Reply
    • @Kevin – no it was only for IIS. however in V15 going forward, Hotdesking will be integrated in the product. This will be available in upcoming updates.

      November 18, 2016 at 12:57 pm
  2. Kevin Jones

    Thanks Nicky, It’s very disappointing that this is not made clear in the prerequisites above. We have now wasted multiple hours trying to get this to work, and now have an unhappy client. Can you please confirm when this functionality will be available in V15? Otherwise we will have to do yet another reinstall to get them onto IIS instead of Abyss, which of course is not ideal as then we are forced to use port 80 and 443 rather than 5000 and 5001.

    November 22, 2016 at 12:24 pm Reply
    • @kevin Actually it seems that Abyss also works..
      We have no date when this functionality will be available in V15 however this time it will be INCLUDED in the product. That’s when you can definitely rely on this feature. Why not tell the client to wait until it is officially released? What was made in v14 was like an integration plugin. This feature should be included in the product like we are planning to do now.

      November 22, 2016 at 1:48 pm
    • Kevin

      Thanks again Nicky. Do you have a guide to doing Hotdesking on Version 14 when using Abyss then please?

      November 28, 2016 at 2:26 pm
    • Not really because it is not part of the product. But all you need to do is add an alias and a couple of files.
      Anyways – by suggestion would be to wait for when v15 has it. (now with beta programs we will have this for trial outs sooner.)
      Just wait a bit – you have been waiting for this say for 1-2 years right? There will be no harm done if you wait for another 1-2 months.

      November 28, 2016 at 3:42 pm
<