Search this site
- @patrichard @tomarbuthnot @DomKent @expta It is more fun to put images that are are inappropriate or mention they s… twitter.com/i/web/status/1… 1 week ago
- @tomarbuthnot @DomKent @expta @patrichard Check and see if they scraped the images or just the URL to the image, if… twitter.com/i/web/status/1… 1 week ago
- @JacobUC @patrichard @We_are_Jabra @mostlyuc Jacob has given me a great idea for you. 2 weeks ago
- I'm talking about the new normal and getting "back to work" this Wednesday for a @UnifySquare webinar. Sign up if y… twitter.com/i/web/status/1… 3 weeks ago
- @mostlyuc is so nice, sending me and the fam a bag of..... Hot dogs. And a nice note :-) https://t.co/JVY1XRszIJ 1 month ago
Tag Archives: Voice
As OCS becomes more popular we find more companies deploying it with diverse needs. During a recent deployment I worked with a client that had over 100 speed dial numbers for various partner companies that they regularly dialed. Each speed dial was a 3 digit number starting with a # (pound/hash symbol), some of the numbers translated to 10 digit dials, others only 6 digits with 4 more digits dialed by the user added to the end. As this was in place with the existing PBX it was important to bring this functionality to OCS as well. After discussing the requirements with the client I used my lab to verify the solution was feasible and consistent to their request. A few minutes of tweaking the normalization rules and I had a plan.
I started with the companies “Location Profile” (in the OCS Snap-in Right click Forest>Properties>Voice Properties), for this example it will be HQ.ocsguy.local:
Recently I was working on an Exchange UM and Cisco Call Manager integration. The company who already owned Exchange E-CALs wanted to upgrade to Exchange 2010, and as part of the process we discussed having Exchange handle the voicemails instead of Cisco Unity which was not supported with Exchange 2010 at the time. Another big advantage was the customer could stop paying the “Cisco Tax” on Unity just by using what they already had in Exchange server and client licensing (over 15k in savings year one).
After a quick configuration of the UM role and the Call Manager we had Unity and Exchange playing nice (reference config here). Test users were moved and things were going as planned up until we tried to configure the Auto Attendants. We took an existing recording and converted it over to a 16bit 8000 HZ PCM WAV file. We then cut the file into 2 pieces, one for the “Business Hours Greeting” and the other for “Business Hours Main Menu”. There was no need for any key mappings as the default operator extension of 0 was already configured. Here is what our auto attendant configuration looked like:
After working with Microsoft for the passed few weeks on a significant audio quality issue we have found what’s causing the problem and a good workaround until a fix is released. Continue reading
Doug L from Microsoft was nice enough to take a look at this issue and point out a possible cause and resolution. After checking over an environment experiencing the problem I was able to verify his suggestions were right on. … Continue reading
Let’s start with a statement about this post: THIS IS NOT AN OCS PROBLEM 🙂
With the July hotfix Microsoft introduced the ability to add Display Names sent from the PBX to the toast in MOC.
From the original article here, the new UCUpdates package released today addresses the issue. Here’s a KB from Microsoft detailing the issue.