I received a call from one of our account managers yesterday in regards to a client’s question for Exchange Unified Messaging. The radio stations here in Toronto have been talking about an impending snowstorm for
I think what I like most about getting into the voice world 2 years ago was that I’ve been able to come across interesting legacy PBXs and when I say interesting, I mean extension designs.
I received a escalated UM related ticket passed on to me this week because the colleague who was looking at the issue wasn’t a UM expert and while I was able to identify the issue
Due to the various OCS and Exchange UM services we had to change for client, a significant amount of changes were also required to their public certificates. I had to go through the exercise of
We’ve finally completed a company wide migration from a Nortel BCM PBX to OCS 2007 R2 with Exchange UM as their auto attendant and voicemail solution just before the holidays and with migration of all
For those who have implemented Exchange 2007/2010 Unified Messaging voicemail to operate with OCS 2007 and other phone systems (i.e. Cisco or Nortel), you may know that in order for the auto attendant to be
I’m not sure if it’s just me but I find the GUI to customize the business hours schedule from within Exchange 2007 and 2010 somewhat cumbersome to work with. This is especially the case when
As simple as the options within Exchange Server 2010’s Unified Messaging Greetings look, I find that it can operate extremely different than you would expect if you don’t take the time to think about all
I had written a post about speech enabled and not enabled Exchange 2010 Auto Attendant prompts (https://blog.terenceluk.com/2010/11/how-speech-enabled-and-non-speech.html) but forgot to mention a critical “by design” behavior about key mappings and because I ran into this
I’ve been meaning to write a blog post about an interesting challenge I faced a few months ago while doing a hardware refresh for a client with their Exchange 2007 environment. They had one hub
