Lync Server 2013
Microsoft has just released CU7 for Lync Server 2013, which contains some new fixes, especially the clslogging bug that was introduced in the August security update is fixed now.
The update contains these fixes:
3003346 Cannot see presence status or send instant messages when OWA is integrated with Lync Server 2013 instant messaging
3003347 User cannot dial out to a PSTN number as a guest in an online meeting in a Lync Server 2013 environment
3003350 Cannot search users by using a keyword that differs from Lync Server 2013 AD DS display name format in a Lync client
3008181 Centralized Logging Service Agent Service cannot start after you install a September 2014 update for Lync Server 2013
Get the update here
Microsoft has released a long waiting update for Lync Server 2013, which is the first one since January 2014.
It fixes these issues:
Frontend and Edge Servers
- 2976568 Address book delta files are not generated in a Lync Server 2013 Enterprise Edition environment
- 2967626 Error “creating procedure RtcResetAbAttributes” when you run “Install-CsDatabase” for rtcab database in Lync Server 2013
- 2967629 Significant bandwidth usage increase by SIP traffic in a Lync Server 2013 environment
- 2967630 Callee receives a missed call notification after answering a call on an IP telephone in a Lync Server 2013 environment
- 2979931 Error “I can’t find the meeting with that number” when PSTN user dials in to conference in Lync Server 2013 environment
- 2978444 Update for Lync Server 2013 to disable Lync Web App users’ ability to upload and show PPT in online meetings
- 2976906 Incorrect time zone is displayed when you create a meeting by using Web Scheduler in a Lync Server 2013 environment
- 2967623 Error “This content cannot be displayed” or blank webpage when you click a dial-in URL in a Lync Server 2013 environment
- 2967624 HD video stutters in a Lync Server 2013 based video conference in Lync 2013
- 2967628 Telephone numbers are missing in a contact card in a Lync Server 2013-based Lync mobile client
- 2967621 Error 404 when Lync phones sign in to Lync Server 2013 front-end servers during SBS failure recovery
- 2967631 Error “”DistributionGroupAddress” and “AgentsByUri” must be set.” when you migrate the RG service to Lync Server 2013
And reliability, stability, and performance Updates to UCMA 4, Administrative tools and Web Conferencing Server
Get the update here
I recently had two issues at a customer that I would like to share with you:
The first one is about PSTN call looping and the second one is about Unassigned numbers which don’t work for external PSTN users:
PSTN Call is Looping
I had an issue where an PSTN user calls a phone number which belongs to the organization but is not assigned to any users or services in Lync.
In this case the customer was using a sip trunk from a Danish Vendor called Cirque, and we experience that when a call was made to an unassigned number, that call would cause a loop and in some cases causes the mediation server to fail. →']);" class="more-link">Continue reading
I stopped by one of the vendors today that I’m preferring for switchboard and contact center solutions at my customers, to talk with Bjarne Henriksen, Partner from Competella about a new product they will release within a couple of months.
The product is called: Competella Call Distributor
The Call Distributor is essential an replacement for response group service in Lync Server 2013, which in many areas are good, but after my opium is also missing some more advanced controls and call handling.
When you are using response groups in Lync, it will not be able to leverage the settings you have made like call forwarding or sim-ring etc. which for some customers is annoying because they can’t answer response group calls on their mobile phone. →']);" class="more-link">Continue reading
In my series of using Lync and Exchange better together, I’m showing how to integrate these two great products with each other.
Use Voicemail in Office 365
In part 2 we were setting up Lync to use voicemail in Exchange 2013 and that works great, but when I wrote that post, I realized that not all companies have an on premises Exchange but instead are using Exchange in Office 365.
So in this post we will have a look on how to integrate an onpremises Lync Server 2013 with Exchange Online, and place the voicemail in there. →']);" class="more-link">Continue reading
In my new series we started by looking at integrating Lync and Exchange so that we could use Chat and Presence in Outlook Web Access and get a more rich experience when these great products is used together.
In this post we will have a look at the Voicemail capabilities in Exchange Unified Messaging and how to set it up.
I will be using Exchange 2013 and Lync 2013, but the process for using Exchange 2010 is almost the same.
As you might know, in Exchange 2013 the Unified Messaging role is installed on all servers as default whereas in Exchange 2010 it was a role you need to install, either separate or together with some of the other roles. →']);" class="more-link">Continue reading
This is my brand new series on how to use Lync and Exchange better together and get the riches experience with these great products together.
I will in this series show you how Lync and Exchange can integrate with each other, so you can get the full potential with the products.
Chat and Presence in OWA
Let us start by the basic and setup chat and presence in Outlook Web Access.
When I look in my OWA, I don’t have any presence status on my contacts:
And also I’m not able to sign to Lync from OWA →']);" class="more-link">Continue reading
I have in the last couple of month’s two customers, who wanted almost as many sip domains as possible in Lync, besides the usual 2-3 sip domains I normally see.
This post is what I found and what I had setup up, at one of the customers.
I found these restrictions:
- An internal SIP certificate has a limit of 4096 characters.
- Globalsign (my public cert provider) has a limit of 100 SAN names.
First of all 100 names sub in a public certificate – that will cost a million $ K →']);" class="more-link">Continue reading
Microsoft has released new updates to Lync Server 2013.
Lync Server 2013 CU4
There is no reports yet if it contains any new features – perhaps they are saying them for Service Pack 1 which is expected soon.
But the update fixes these issues:
As a continuation to my previous post (Use Location Service on Wifi in Lync), I will in this post tell you what is hot and what is not so hot when using location service on a wired network.
So as I my previous post a customer asked me to enable location service in Lync so that the colleagues could locate each other in there fine new building.
Before I started, I might have promised the customer that Location Service was the 8 wonder in world and it was SO cool – I knew only the theory – or most of it K
Back to the customer, which is located in Denmark, Europe – so we can’t use location service for cool stuff like E911 (it’s a wonder that the ambulance can find us J)