While rolling out snom IP phones for a recent Lync enterprise voice deployment, I needed a way to control a phone while working remotely. Snom’s FAQ: http://wiki.snom.com/FAQ/Can_I_control_my_snom_phone_remotely provides details on this built-in functionality using the snom phone’s Web User Interface: http://wiki.snom.com/Category:Web_User_Interface and command.htm to simulate key presses. After entering a few control commands into a browser and monitoring the phone’s display with my Get-snomScreen PowerShell GUI: Get-SNOMScreen. I figured there must be a better way!

While deploying a Lync 2013 pool for a client, we ran into issues publishing the new Lync Topology and installing databases. Looking at the Create database log, the issue occurs while the database owner is being set: Setting owner for database xds to sa. Exception Stack: Type: Microsoft.SqlServer.Management.Smo.FailedOperationException, Message: Set owner failed for Database ‘xds’. Type: Microsoft.SqlServer.Management.Smo.SmoException, Message: An exception occurred in SMO. Type: System.ArgumentException, Message: The login ‘sa’ does not exist on this server.

While rolling out snom IP phones for a recent Lync Enterprise voice deployment, I found it handy to monitor a specific phone’s screen while working remotely. I wrote a small PowerShell GUI script that can access the snom phone’s Web User Interface: http://wiki.snom.com/Category:Web_User_Interface and pull the display screen. Additionally the script can set a reload/refresh interval, zoom level and ignores SSL errors like self-signed device certificates. Screenshots: Snom phone models tested ( http://www.

During a recent Lync Server 2010 to 2013 migration project, it was reported that a few Exchange resource mailbox accounts enabled for Lync Enterprise Voice were unable to make outbound PSTN calls. However inbound and Lync to Lync calls were successful. Reviewing the Lync client logs from these conference room accounts showed: SIP/2.0 400 Bad request ms-diagnostics: 1;reason=“Service Unavailable”;AppUri=“http%3A%2F%2Fwww.microsoft.com% 2FLCS%2FOutboundRouting”; reason=“Failed when constructing the outgoing request”; source=“fe2013.domain.com”. After staring at the traces for a bit, the “From” address popped to my attention, why would there be a backslash in the account’s name?

Certificates for Lync Phone Edition TechNet article was updated Jan 7,2014 ( http://technet.microsoft.com/en-us/library/gg398270 ). The Trusted Authorities Cache now includes DigiCert and a few more 2048-bit (Key Length) Root certificates. The January 2014 Lync Phone Edition (LPE) CU includes the updated list of trusted public certificates. January 2014 CU for LPE (Aastra 6721ip/6725ip) January 2014 CU for LPE (HP 4110/4120) January 2014 CU for LPE (Polycom CX500/CX600/CX3000) January 2014 CU for LPE (Polycom CX700 and LG-Nortel IP Phone 8540) Prior to the January update, certificates issued from DigiCert had to be requested in the Legacy format to work with LPE.

During a recent project deploying SBAs for Lync 2013, I came across an issue where the Lync Front-End service would not start. The SBA was an AudioCodes Mediant 1000 SBA running version 1.1.12.0 Going through the Deployment Web GUI, the error would occur at “Start MCS Services” Looking at the Deployment Log, the Front-End (RTCSRV) service would timeout. Connecting to the SBA using RDP and reviewing Event logs showed: System Event Log with Event ID: 7024

This is a multi-part article that goes through the Dossier for Lync product suite from Event Zero. If you would like to read the other parts in this series please go to: Part 1 – Overview: Event Zero Dossier Part 2 – Installation: Event Zero Dossier Installation Part 3 – Lync Essentials: Event Zero Dossier Essentials Part 4 – Lync IM: Event Zero Dossier IM Part 5 – Lync Devices Part 6 – Lync Response Groups Part 7 – Lync Conferences The Dossier for Lync product suite allows environments using Microsoft Lync to gain in depth insight into the way Lync is being used in real time within an organization.

After installing Lync Server 2013 Cumulative Update 3 - October 2013 ( http://support.microsoft.com/kb/2809243), the CSClientPolicy now exposes two new parameters for High Performance Application Sharing. Looking at the Parameters for Set-CSClientPolicy on TechNet ( http://technet.microsoft.com/en-us/library/gg398300.aspx) EnableHighPerformanceP2PAppSharing: “When set to True, allows a peer-to-peer application sharing session to exceed the maximum frame rate of 2.5 frames per second. The default value is False.” EnableHighPerformanceConferencingAppSharing: “When set to True, enables high performance application sharing in conferences.

This is a multi-part article that goes through the Dossier for Lync product suite from Event Zero. If you would like to read the other parts in this series please go to: Part 1 – Overview: Event Zero Dossier Part 2 – Installation: Event Zero Dossier Installation Part 3 – Lync Essentials: Event Zero Dossier Essentials Part 4 – Lync IM: Event Zero Dossier IM Part 5 – Lync Devices Part 6 – Lync Response Groups Part 7 – Lync Conferences The Dossier for Lync product suite allows environments using Microsoft Lync to gain in depth insight into the way Lync is being used in real time within an organization.

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: The 710 I received was shipped with 8.8.2.8 UC firmware, which didn’t include the Call Park+Orbit Function: 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.