Here’s another interesting problem I came across awhile ago. During New Orleans TechEd and CS 14 training, I actually asked the Microsoft representatives about manipulating SIP addresses and REFER fields
I ran into an interesting issue while integrating Exchange Unified Messaging’s Auto Attendant with OCS and PBX. After setting up everyone who was still living on the BCM’s EUM attribute
This was a problem I ran into during an OCS deployment at a client and what was interesting was that I didn’t end up solving the issue even though I
I had to shuffle some licenses around a month ago for a client who used up their licenses for a preproduction environment but was ready to decommission those servers and
One of the first questions asked on the first day during the introduction to CS 14 was if Group Chat has been updated and the answer is no. This is
Here’s an error I ran into while working with CS 14 Beta: 1. Fresh install of CS 14. 2. Started all services. 3. Launched Communications Server Control Plane and got
As noted in one of my previous posts: CS 14 configuration information redundancy between servers (https://blog.terenceluk.com/cs-14-configuration-information/), CS 14 was designed to be less dependent on the backend SQL server and
Day 2 – Module 06 Migration restrictions: 1. Tri-mode is not supported. You cannot have R1, R2 in your environment when you migrate to CS 14. 2. LCS to CS
