A common challenge when deploying Lync in an enterprise voice environment, is to have the Lync Client behave as close to an “ordinary” phone as possible.
One common “problem” is the busy-on-busy. When an incomming call is routed to a Lync Client already in a call, you would want the caller to get a busy tone. This is, by default, not a function in Lync. To get this behavior, one would have to do it by using MSPL scripting as referred to in this article(not tested, so I don’t know if this actually Works) or use a Third party Application.
I’ve recently had a strange problem which I thought would be nice to share.
The environment is Lync 2010 Standard edition and Trio Enterprise 3.2 from Enghouse Interactive. The Lync Client is used as phone app for Trio inbound and outbound calls. When a Call comes in to the contact center, the Lync Client should automatically answer the call when the agent picks it up. Likewise, when an outbound call is made, the Lync Client should automatically pick up the outbound call from Trio Agent and route it to the PSTN Gateway.
In my case, the inbound call seemed to be working fine, but outbound calls would sometimes make the Trio agent go in to a lock. The Trio agent would also make a callback to the Lync Client, resulting in a missed call from the very same number as the Trio agent uses for outbound call. This happened all the time.
Also, the employees at the callcenter complained about poor audio quality in their headsets and the Lync klient said “Your computer is causing poor audio quality”. This set me off in a direction where I started thinking maybe there was something wrong with the headsets.The headsets are Jabra Pro 9465 Duo, and there you go 🙂
I checked the firmware on the headsets in use, and discovered it was quite old. Installed the Jabra PC Suite and ran Firmware Updater. The new firmware was 3.8.2(the old one was 3.1.5 if I remember correctly) from Sept 2012. After the firmware update, everything is working fine.
This post focuses on some key points I’ve come accross when migrating from Lync 2010 to Lync 2013(causing small delays in progress :)).
Static Routing: One of my first migrations took a bit longer to Complete due to faulty routing on the new Edge server. The static routes were created on the server prior to activating the NIC, which lead to failure to communicate. Once the routes were deleted and recreated, everything worked like a charm.
Office Web apps has to be published to the internet using HTTPS and SSL certificate, otherwise you won’t be able to share Powerpoint’s with your federated contacts. Consider using the same URL for internal and external use because this allows for the SSL certificate to be used on both sites on the IIS. How to publish Office Web Apps server
Mobility login: Problems with Exchange Web Services(EWS). Make sure Exchange Web Services External URL is set correct. Consider using the same URL for internal and external web services.
This script provided by MVP Ståle Hansen is an excellent Resource for setting Exchange URL’s.
External web services URL: Remember to change External Web Services FQDN on the new Front End pool, your web services won’t work unless you do 🙂
Client Version policy: Remember to allow legacy clients to login to the new Lync 2013 server(for Legacy). Default is Blocked for Lync 2010 Clients older than 4.0.07577.4103(CU6, June 2012).
This applies only to Lync 2013 on Windows Server 2012.
After installing Lync on Windows Server 2012, replication between Edge server and Front End stops working. This could be as a result of the stricter certificate handling on Windows Server 2012. Check out this post by Terence Luk on how to fix this problem. Another solution to the problem could be found in this article by Herman Seminiano. Both solutions fixes the problem.
This post will be updated as I discover more points to remember during future migration projects.
I recently discovered a small bump in the road when it comes to upgrading an excisting Lync 2010 Enterprise pool to Lync 2013 Enterprise.
The SQL server instance not only has to be unique to the Lync 2013 Enterprise Pool, but it also has to be on a dedicated SQL server not already in use by the Lync 2010 Pool.
This means, when upgrading from Lync 2010 Enterprise to Lync 2013 Enterprise, take into concideration that you would need a new SQL server as well.
The Microsoft documentation on the subject is not very easy to find(unless you search specifically for SQL migration scenarios), and even in this article http://technet.microsoft.com/en-us/library/gg425764.aspx it’s not clear that the requirement for a new SQL server is only for an Enterprise scenario.
A possible workaround(in a small organization) could be to install Lync 2013 Standard Edition, migrate users and move the CMS, then reinstall Lync 2010 Enterprise server as Lync 2013 Enterprise pointing towards the old SQL server and then move everything back…
This was supposed to be an article on how to integrate Lync 2013 presence and buddy lists with IBM Lotus Notes Clients.
However, this proved to be a somewhat troublesome process which ended up in a conclusion stating that this is at best a tidious process which involves making changes to excisting mailtemplates in Notes, installing specific DLL’s and Visual C++ Components on local computer in order to make Things work.
All the References regarding this process is mainly focusing on OCS/Lync 2010, and the material is designed for older Versions of Lotus Notes and Domino.
If you do need the coexcistence with Microsoft Lync and IBM Lotus Notes/Domino as a permanent solution, you would have to implement this either using this solution or some other third party utilities(there are several out there, and www.instant-tech.com could be one of them).
If the environment doesn’t depend on the coexcistense(as in my case), it might be best to leave the two systems as separate ones during the transition.