Mino – The UC Guy

Microsoft Unified Communications Blog

Posts Tagged ‘Cisco’

No Name Appears When Callings from OC to Cisco or vice versa

Posted by Mino on August 10, 2009

One of the frustrating drawbacks when Implementing OCS enterprise voice integrating with Cisco Call Manager or other PBX is that No name would appear in Communicator 2007 when a telephone user calls a Communications Server 2007 user or vice versa .

The only solution by then was to place a media gateway in the middle between mediation and IP-PBX and use a translation feature built in the media gateway to edit the packet header and add Caller Name before sending it to the PBX.

But Finally Microsoft has listened to my prayers and they have released July fix for OCS 2007 R2, once they were released our team started to do the testing in our LABs. At the beginning things didn’t work fine but in the end it worked and it appeared that we only applied the server side updates while the KB 971844 includes Office Communicator update too.

However, even with these fixes, this don’t send display name by default. So, this configuration in KB 972721 will be also necessary. Below are the snapshots taken by our Engineer Amr Nassar who has worked on this and successfully made it work after applying those Fixes.

Calling from Office Communicator R2 with ext 6000 to Cisco IP Phone with ext 10000

From OCS

Calling from  Cisco IP Phone with ext 10000 to Office Communicator R2 with ext 6000 

From Cisco

But let me also share Microsoft explanation on why this problem happens in the first place and what these updates fix?

Problem Explanation:

When a Private Branch Exchange (PBX) telephone user calls a Microsoft Office Communications Server (OCS) 2007 R2 user, the calling party name that exists in PBX is stripped at the OCS 2007 R2 Mediation Server. Because the PBX telephone user does not exist in Active Directory, no name appears in Microsoft Office Communicator 2007 R2

This problem occurs because the OCS 2007 R2 Mediation Server does not forward the display name information from the Unified Communications (UC) side to the gateway side. Therefore, the Communicator 2007 R2 client does not receive the display name information.

Update 970679 introduces functionality for the Mediation Server role of Communications Server 2007 R2 to forward Display Name information that is part of the From header between its gateway side and its proxy side.

A file called MediationServerSvc.exe.config should be created in the Mediation Installation Directory which be default is at  %programfiles%\Microsoft Office Communications Server 2007\Mediation Server

This file should contain.

<?xml version=”1.0″ encoding=”utf-8″ ?>
<configuration>
                 <appSettings>
                                <add key=”forwardDisplayName” value=”True” />
                 </appSettings>
</configuration>

Advertisements

Posted in AVAYA, Cisco 4.x Integration, Cisco 5.x Integration, Cisco 6.x Integration, Cisco 7.x Integration, communicator client, Mediation Server, Nortel CS1000, OCS 2007 R2, PBX Integration, Phone Edition, Quintum's gateways | Tagged: , , , , , , , , , , , , , , | 3 Comments »

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.

cisco-unified-communications-manager-7011

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

Cisco Unified Communications Manager 6.0 PBX Configuration Note

Posted by Mino on October 9, 2008

cisco-unified-communications-manager-60

This topic provides link to configuration notes for Cisco Unified Communications Manager 6.0 that have been created and tested by Microsoft . When Microsoft or a partner deploys Exchange 2007 Unified Messaging with a new IP gateway and PBX or IP PBX configuration, the prerequisites and configuration settings are documented. This information is used to create a configuration note.

PBX configuration note contains information about how to deploy Exchange 2007 Unified Messaging with a specific telephony configuration including the manufacturer, model, and firmware version for the IP gateways, IP PBXs or PBXs. In addition, each PBX configuration note also includes other information such as:

  • Contributors in authoring the configuration note.
  • Detailed prerequisites, including the following:
    • Features that have to be enabled or disabled on the PBX.
    • Specialized hardware that has to be installed.
    • Is an IP gateway required?
    • Features that must be present on the IP gateway if one is needed.
    • Specific cabling requirements between an IP gateway and a PBX.
    • A list of Unified Messaging features that may not be available with a given telephony configuration

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

Cisco Call Manager 5.1 PBX Configuration Note

Posted by Mino on October 9, 2008

Cisco Call Manager 5.1 PBX Configuration Notes

This topic provides link to configuration notes for Cisco Call Manager 5.1 that have been created and tested by Microsoft . When Microsoft or a partner deploys Exchange 2007 Unified Messaging with a new IP gateway and PBX or IP PBX configuration, the prerequisites and configuration settings are documented. This information is used to create a configuration note.

PBX configuration note contains information about how to deploy Exchange 2007 Unified Messaging with a specific telephony configuration including the manufacturer, model, and firmware version for the IP gateways, IP PBXs or PBXs. In addition, each PBX configuration note also includes other information such as:

  • Contributors in authoring the configuration note.
  • Detailed prerequisites, including the following:
    • Features that have to be enabled or disabled on the PBX.
    • Specialized hardware that has to be installed.
    • Is an IP gateway required?
    • Features that must be present on the IP gateway if one is needed.
    • Specific cabling requirements between an IP gateway and a PBX.
    • A list of Unified Messaging features that may not be available with a given telephony configuration

Posted in Cisco 5.x Integration | Tagged: , , , , | Leave a Comment »

Microsoft Video Conferencing for Masses vs. Cisco Personal Telepresence

Posted by Mino on October 5, 2008

Cisco introduced its personal telepresence technology to the world and announced their entry into the “market for in-person virtual communications with new endpoints for the personal office and large group meetings”.

It is great to see Cisco endorsing and supporting video conferencing for the masses, something we have long felt was critical for organizations to see real benefits. But I think there are some serious limitations to the approach they have taken.

Budget and environmental impact are just a numbers game at the end of the day. There are 100’s of information workers for every executive in the world, and the impact of any technology you can give to executives will be amplified if you can do it for everyone. To see these benefits, technology must be affordable and accessible to the masses.

High end telepresence units, costing businesses $300,000 a piece before network upgrades and annual maintenance, are out of reach for all but a privileged few in the organization. If you had that kind of telepresence system for every 50 information workers in world (an expected ratio of workers to meeting rooms), it would cost more than the GDP of Spain! But while we at Microsoft were out announcing plans for a $300 high def camera that would revolutionize the accessibility of high quality video conferencing for everyone, Cisco is announcing a stripped down version of its flagship telepresence product selling for $34,000 per unit.

I just don’t believe you get mass adoption when the price point evokes the question “should I buy this or the helicopter?”. The market is limited to literally a few hundred units. Units like the Polycom HDX 4000, for example, have been around for years at a fraction of the price. Stephen Lawson at IDG sums it up well when he says “The System 500 is not the consumer device Cisco envisions, which former Chief Development Officer Charlie Giancarlo last year predicted could be sold within two to three years for about US $1,000.”

In contrast, Microsoft RoundTable sells for $3,000-$4,000 and has already built up over 700 customers and thousands of units sold after launching in October 2007. For the price of two personal telepresence units which would enable two executives to talk to one another, customers can buy 20+ RoundTables, enabling a much larger number of people in remote offices to communicate and collaborate more effectively, while reducing travel costs.

I also don’t get the argument about personal telepresence “shortening sales cycles” or to “improve productivity”? Most information workers spend a significant portion of their time collaborating using applications and yet telepresence systems don’t have an easy way to share applications with others. Sales people are often out visiting customers or on the road and more and more workers are working from home these days, but they can’t lug around a 400 pound telepresence unit with them to stay connected. While the world is moving towards integrated collaboration and mobility, personal telepresence seems to be focused on very expensive video conferencing as the one trick pony.

At Microsoft, we have really focused on building video conferencing into common applications and user experiences to make business processes more engaging. Integration into tools such as Live Meeting and Communicator, which are compatible with many third-party audio and video devices, make it easy to use video conferencing for face to face conversation, multimedia document collaboration or telework.

Finally, to make a communication tool useful and impactful, you have to make it interoperate with common legacy equipment. This includes colleagues on Tandberg or Polycom systems, which account for over 75% of the installed base of video conferencing today. Or federated customers and partners for example. The lack of interoperability makes the system  an isolated island in a customers’ broader environment. If you are going to go for a telepresence solution, you should consider systems that interop with broader installed base, such the Tandberg Experia or the Polycom RPX for example.

It’s great to see that Cisco has joined the tide of video conferencing for the masses but clearly there is a long way to go beforeGiancarlo’s vision is realized.

Moz Hussian

Director of Product Management

Posted in Miscellaneous | Tagged: , , | Leave a Comment »