Mino – The UC Guy

Microsoft Unified Communications Blog

Archive for November, 2008

Cisco Unified Communications Manager 7.0 PBX Configuration Note

Posted by Mino on November 23, 2008

This document describes the simultaneous ring feature interoperability and documents the steps and configurations necessary for Cisco Unified Communications Manager (Cisco UCM) Release 7.0(1) to interoperate with Microsoft Office Communications Server (OCS) 2007 Enterprise Edition. It aims to provide a good understanding of what works and what does not work in terms of the feature interaction between a Cisco UCM device and Microsoft Office Communicator. It also provides guidance to deployment participants regarding the limitations, expected behaviors, and known issues. Please note that this document does not address performance and scalability, which are part of broader criteria for a deployment-ready solution.


· The simultaneous ring feature allows a Cisco UCM endpoint (IP Phone, IP Communicator, etc…) to simultaneously ring its remote destination(s) when a call is placed to that endpoint. The remote destination(s) could be Microsoft Office Communicator and/or any other device(s) including mobile phones, PSTN phones or even local PBX extensions. The remote destination feature uses the Cisco Unified Mobility functionality and can be configured to allow or block the receipt of certain numbers. For the simultaneous ring configuration, Cisco UCM has a Direct SIP connection to Microsoft Mediation Server.


Posted in Cisco 7.x Integration, PBX Integration | Tagged: , , , , , | 2 Comments »

Call unsuccessful – The Requested type of content encryption is not supported

Posted by Mino on November 17, 2008

You might get the above error message when you try to call your voice mail hosted on Exchange 2007 SP1 UM from your Office Communicator Phone Edition (OCPE) powered device. The likely cause of the issue is a mismatch between the VoIPSecurity setting of your SIP URI UM dial plan and the Security – Encryption level setting on the A/V Conferencing properties on your OCS 2007 pool.

The OCPE device use the Security – Encryption level setting to determine, if media should be encrypted or not. The default setting is Require encryption and OCPE will then send media using SRTP. If the UM dial plan VoIPSecurity parameter is set to SIPSecured Exchange 2007 SP1 UM will not accept the SRTP based media and you get the error message above on OCPE. Changing your UM dial plan to have the VoIPSecurity parameter set to Secured will fix the issue. This is the recommended setting, since this ensures that media is sent in a secure way.

Posted in Common Errors, OCS & Exchange07, Phone Edition | Tagged: , , , , , , , , | Leave a Comment »

Communicator error ” Cannot Synchronize Address Book “

Posted by Mino on November 17, 2008

A common issue we see is clients getting an error stating “Cannot Synchronize Address Book”.  It looks like this:





This is an action that the OCS installation doesn’t take care of automatically so it happens pretty regularly.  To resolve it, select the Directory Security tab and click on the Server Certificate Button


After you click on the Server Certificate button, follow the Wizard, select Assign an Existing Certificate and assign the certificate used by your OCS Server for client logins.  Once you’ve assigned the certificate the SSL port on the Web Site tab should be filled in with port 443. 

Sign your clients out of Communicator and then back in and the Address Book should be downloaded successfully


PS : if you are using Exchange 2007 Selfsigned Certificate , you should also recieve this error still and that it because the self signed certificate for exchange is not trusted by OCS 2007 . so you should either replace the exchange 2007 self signed certificate with a certificate from the same CA as the OCS 2007 or you should import the exchange self signed certificate inside the OCS 2007 servers in the Trust Certificate store  

Posted in Common Errors, communicator client, Miscellaneous, OCS & Exchange07 | Tagged: , , , | 1 Comment »

Application Notes for Microsoft Office Communicator Clients with Avaya Communication Manager Phones

Posted by Mino on November 17, 2008

These Application Notes describe the configuration procedures for enabling Microsoft Office

Communicator (MOC) clients to operate Avaya Communication Manager phones. The MOC

client and Microsoft Office Communications Server (OCS) provide the user with multiple

modes of communications, such as Instant Messaging (IM), voice, and video. The

configuration steps described herein focus on the TR/87 integration between Avaya

Application Enablement Services and Microsoft OCS. The TR/87 integration allows MOC

clients to make and answer calls on Avaya Communication Manager phones, as well as

perform basic call control operations such as hold/retrieve, transfer, and disconnect.


Posted in AVAYA, communicator client, PBX Integration | Tagged: , , | 2 Comments »

Back from the Voice Ignite

Posted by Mino on November 17, 2008


Posted in Miscellaneous | Tagged: | Leave a Comment »