D(one) IT

IT Tips, Tricks & Such

Tag Archives: Snom

Snom Lync Call Park support 7xx

Integrating the Lync Call Park service on a Snom 7xx series phone.

Snom phones allow you to capture a screenshot of the device’s LCD screen by browsing to: http://phoneIP/screen.bmp

  • LCD Screen:
    screen

The 710 I received was shipped with 8.8.2.8 UC firmware, which didn’t include the Call Park+Orbit Function:

8.8.2.8

Looking at the New Features & Fixes list (http://www.snom.com/en/your-personal-menu/snom-uc-edition-firmware-center/snom-uc-edition-front-desk/snom-uc-edition-88216-snom-7xx-only/), Call Park support on the 7xx phones was added in 8.8.2.13 and improved upon in 8.8.2.14.

The 8.8.3.X Beta (BToE) firmware site doesn’t show a 710 version available for download, but there is a “snom710-UC-8.8.3.201309090236-SIP-r.bin” on the download site. The 8.8.3.X firmware requires the Park+Orbit to be assigned to a function key.

8.8.3.x

  • Call comes in:
    8.8.3.x-ring
  • Call is answered:
    8.8.3.x-con
  • Function key is pressed and Orbit info is displayed on screen:
    8.8.3.x-park
  • Note: To retrieve a parked call the Orbit number must be dialed, repressing the function key will not retrieve the call.

I decided to deploy the current release version and found that the 8.8.2.16 firmware adds the Park+Orbit to the LCD call handling options and does not require a programmed function key.

  • Call comes in:
    8.8.2.16-ring
  • Call is answered (Park O is shown on the LCD):
    8.8.2.16-con
  • Park option is selected and Orbit info is displayed on screen:
    8.8.2.16-park
  • Call is retrieved by keying in the Orbit number and displays who retrieved the call:
    8.8.2.16-unpark
  • The display is updated if caller hangs up:
    8.8.2.16-hung
Advertisements

Snom 8.8.3 BToE Beta Installation

This morning I received an email from Snom indicating the BToE beta has gone public.

The following are the steps I used to install snomXXX-UC-8.8.3.201309090236 firmware on my 821 Snom phone and pair using Better Together over Ethernet (BToE) with Lync 2013 client on Windows 8. Note: 821 was previously configured to register to Lync 2013 Server via Edge with my user account.

  1. Install Beta firmware using the phone’s admin page.
    snom-btoe-1
  2. Install BToE application on PC
    snom-btoe-2

    snom-btoe-3

    snom-btoe-1f

    snom-btoe-4

    snom-btoe-1e

    snom-btoe-5

    snom-btoe-1d

    snom-btoe-6

    snom-btoe-1c

    snom-btoe-7

    snom-btoe-1b

    snom-btoe-8

  3. Configure feature key on phone for Pairing. Format: Action URL –
    file:///xml/gui/decision.xml#var:dsc_title=BetterTogether&var:dsc_text=Start%20pairing%20now?&var:dsc_yes=1&var:dsc_no=1&var:action=btoe_init

    snom-btoe-9

  4. Set BToE_client_host using a web browser and a special HTTP Get request. format: https://phoneIP/dummy.htm?settings=save&btoe_client_host=PCIPaddress
    snom-btoe-1a
  5. Pairing Process, Run the Command Prompt as Administrator and run the “BteUrbDrMgr.exe” for the correct OS version (32/64bit).
    snom-btoe-10

    snom-btoe-11

    Press the BToE feature key on the phone and a PIN code is given to enter on the PC.
    snom-btoe-14

    snom-btoe-2a

    snom-btoe-12

  6. 821 now available as a primary device in the Lync client
    snom-btoe-2b

    snom-btoe-13

Impressions

  1. Pairing doesn’t require PC to be plugged into Phone, big for VDI and Remote Desktop scenarios.
  2. Command prompt running BteUrbDrMgr.exe must remain open or pairing disconnects.

Call Via Phone app Advanced review

With SNOM’s Enhanced Better Together being demonstrated at WPC 2013: http://www.snom.com/en/news/archive/article/2013/en/snom-to-demonstrate-pc-pairing-%E2%80%9Cbetter-together%E2%80%9D-features-on-its-microsoft-lync-qualified-desktop-phones-at-wpc-2013/ and availability being most likely end of 2013. I figured it would be a good time to post my review of the Call Via Phone Advanced. A 3rd party Better Together type application for Lync and SNOM phones which is currently available.

The Call Via Phone application comes in two editions (free and paid) and works with Lync 2010 and 2013.

After installing the Call Via Phone application from the MSI, the Lync client will now have a new item in the Tools drop down.
configure_call_via_phone

To configure the application enter the SNOM phone IP address, the Username/Ext, Password/Pin and Save. Note: Username/Password should be the account that can administer the SNOM phone’s web interface.
snom_device_settings

configure_call_via_phone_config

The freeware version is pretty straight forward which gives the ability to right click a contact and click “Call Via Phone”, this will establish the call on your SNOM phone.
contact_call_via_phone

The Advanced version will show an options menu after clicking “Call Via Phone”.
numbers_call_via_phone

After clicking the number to contact, the call is answered on the SNOM phone and a popup menu with Phone Call commands for the active call will be displayed.
call_option_call_via_phone

You can type in a number and click “Add Call”, this will establish a call to the added number and display additional commands like Transfer and Conference.
call_option2_call_via_phone

Originally the Call Via Phone application was just for outgoing calls. I reached out to Gianluca the author of the application and made some suggestions. A few emails later I had an updated version 1.5.6, that could handle incoming calls! Note: Account on the SNOM phone should be the same account signed into Lync to allow for incoming functionality.

In the “Call Via Phone” Configurator there is an option to “Activate” the Incoming Call via Phone service.
incoming_option_call_via_phone

This creates a system tray icon that catches incoming call events and appears next to the Lync toast.
incoming_call_via_phone

After clicking “Answer By Phone”, the call is answered on the SNOM phone and a popup option menu with available Phone Call commands for the active call will be displayed.
call_in_option_call_via_phone

Benefits of Call Via Phone vs Enhanced Better together:

  • Can be made to work with other IP Phone vendors (Cisco, Polycom, Grandstream, 3CX, Yealink)
  • Doesn’t not require Lync user to have Enterprise voice for Outgoing call functionality
  • No windows driver protocol limitations, allows for future customization (Programming Phone keys, full interaction with any functionality available on the Phone)

For more info reach out to sales@callviaphoneapp.com

Unable to Lync Device Update Snom 7XX series phones via Edge

With the recent announcement: Snom IP Phones Deliver Out-of-the-Box Provisioning Speeds and Simplify Microsoft Lync Voice Deployments. I decided to setup Lync Device Update service for my Snom 760.

A quick check on the Lync Interop Programs shows the Snom 760 as compatible with Lync 2013 and Managed Updates supported:
snom_compatible

Downloaded the snom760-8.8.2.10.cab firmware, imported and approved the update:
snom_update_approved

I found the 760 registered to our Lync 2013 environment via the Edge server but refused to attempt the firmware update, where as my Lync phone edition devices (Polycom cx600 and Aastra 6735) had no issue.

Reviewing the logs of the Snom 760 I found that the device detected “not registered locally, thus skipping update attempt”:

3/4/2013 08:45:31 [NOTICE] PHN: ProvUtils::UcSendFirmwareUpdateAvailableRequest: enabled: 1; url: >https://webext1.iluminaritech.com:443/RequestHandlerExt/ucdevice.upx<; id: >camt@ILUMINARITECH.COM<
3/4/2013 08:45:31 [NOTICE] PHN: ProvUtils::UcSendFirmwareUpdateAvailableRequest: not registered locally, thus skipping update attempt!

A bug was opened with Snom support. Internal Tracking ID is SCPP-4825, This is for Snom use, yet will be referenced in the Release Notes to indicate the solution.

Status:

UC Edition Developer is speaking with Microsoft about the apparent requirement for authentication to retrieve the firmware file. Unfortunately, this means that external updates are not yet supported. However, the Development Team is pursuing the fix as a high priority