People Communicate

Microsoft Unified Communications Blog

Category Archives: OCS 2007/R2

Welcome To My Page

welcome to my page Pictures, Images and Photos

Integrating OCS 2007, Cisco Call manager, Tandberg MCU 4200 all together

I have to say that all of you will like this topic a lot, I have been doing a lot of work in the previous 2 months to mount my new infrastructure in my new company, and one of the challenges that I had is to provide a centralized conferencing and unified communication solution.

The challenge that I had is providing UC service across different sites (I had many), Audio conferencing, Video conferencing, Web conferencing , Telephony conferencing , Voice mail and all of nice stuff all together; well it wasn’t an easy task.

When I came to my company I found CCM 4.3 mounted already and in place, so I had to work it out with OCS 2007, we decided to have a HW video conferencing solution and not relying on the round table since it is not available in the middle east yet so we investigated Cisco/Polycom and Tandberg and we chose Tandberg.

At the early time I wasn’t involved yet in the vendor selection for the video conferencing, so I was working in choosing a telephony conferencing solution, knowing that OCS R2 will provide that module for me made it much harder to choose between Alcatel, Cisco and Nortel.

When Tandberg solution mounted in our HQ and was in place in 3 of our sites I found that it is amazingly works with OCS 2007 and Cisco Call Manager, so I decided to integrate them together which worked so perfectly after, I will share my experience with you across several configuration notes, solution design posts and Finally showing you how an End to End solution will be implemented between the 3 island and connecting them together.

Now will walk through how to install and configure Tandberg Video conferencing, Codian MCU 4200 and OCS 2007 along with CCM support to provide end to end unified communication experience, in the first part I made a small introduction about the subject in this part I will describe the End to End experience and going to the basic configuration of the MCU 4200.

What do you want exactly, this is a so hard to answer, especially in the UC field, all of the vendors as well as partners are introducing end to end UC solutions, so what to chose and where to place is the hardest question.

What do you want, let us talk about that part a little bit, what do you want from UC, what you can achieve, to tell you the truth, you can do almost anything, from launching you mail/voicemail/IM end point from your mobile phone, until mounting you desktop phone from your PC or mobile, do FMC, bypass toll charges, doing audio/video/web conferencing and mixing all of them together, now you can place calls to PSTN network over GSM using E1 modules that carries SIM cards, typically anything.

So where to go, it is up to you, your budget, organization and how you do work internally, some companies work with other parties externally WW so they might need web conferencing, or you might have international branches where they want to minimize their phone bill, so ultimately there are no best fit for you, you have to note that when you ask consultants to do assessment for your organization because vendors will start talking and talking but you need to decide what you need exactly.

Let us go back to my solution, let me give you a brief about the architecture:

  • And E1 connection from my service provider that hosts 100 extension over ISDN.
  • One Cisco Voice gateway.
  • 2 Cisco Call Manager (publisher/subscriber).
  • 1 Codian MCU 4200 V2.3
  • 5 Tandberg Endpoints in site1
  • 1 Tandberg conferencing unit in each branch office.

In this part I will walk into configuring the MCU 4200, step by step:

On the OCS create a normal user, you don’t need to create and email, you can give him an email address and enable OCS 2007 for him, don’t login with OC to the user as this will remove the LCS 2005 attributes from the user and MCU will lose its presence.

After giving the IP of the MCU, and configuring the initial configuration like system name…etc follow the below steps:

  • From the settings page go to the SIP pane.
  • Enter the SIP address and the SIP proxy address for the MCU; this will be dialed from the OCS clients to join the Conf.

Note that in version 2.3.1.8 you cannot use the authentication since the firmware support basic auth, you need to upgrade to version 2.4 to support NTLM, I upgraded to 2.4 but it didn’t work so I rolled back and I work with Tandberg support on it.

  • To overcome the auth, issue you need to add the IP of the MCU in OCS server in the authorized hosts tab and you need to mark it tread as authenticated.
  • Once finished you will note that registered mark appears as above.
  • Now you can add the MCU in your buddy list and you can dial it, once dialed you will be prompted for the conf. ID enter it and you can see/hear the conf.

I have tried to register the MXP 75, but it looks that the firmware 6.3 has a bug in registering the GRUU, so I will acquire the latest MXP firmware (v7).

And now the final part of this article, we will talk about configuring the CCM/Tandberg to work all together, this will let you leverage the conferencing capability from any phone anywhere, it is cool and very important and I found that most of the Tandberg customers don’t know about it.

To make it works, make sure to do the following steps at the 4200 MCU:

  • From the Gateway menu, add a new gateway, type in the IP of the Cisco Call manager, and you are done.

From the Cisco Call manager, follow the below steps:

  • Add the MCU as a gateway.
  • From the routing plans, add a new route pattern, this will match a number (for example 1000) and route this pattern using the gateway you just configured.

Using the above if a user internally calls 1000, he will be prompted with the Codian MCU auto attendant, the 1000 extension should be reachable from the outside using either digits manipulation..Etc so users from the external telephone network can dial that number.

No users in the OCS can add the conference ID as a user and call that user, also call from the phone the MCU and amazingly they can hear users from the Video Conference points and on the OC clients.

Note: I have been working on this for 2 weeks now, I have upgraded my MCU from 2.3 to 2.4, this “as Tandberg” allows me to use NTLM authentication rather than anonymous authentication for MCU registration, but it didn’t work.

For some reason the MCU cannot obtain the GRUU that is returned from the OCS and cannot register itself in OCS, I believe that this is a bug in OCS (as far as I can see) because the OCS is using some SIP extension that has make my life harder before, I am working with Tandberg folks on it now, So keep your MCU at 2.3 until further update.

OCS/E12 and CCM

This is my configuration notes for configuring OCS2007/E12 and Cisco Call manager, I did a test lab and I came up with the following results:

  1. Integration was for simple, configuring the CCM as a GW for the mediation server was very enough to do phone calls.
  2. To do phone to PC call, you will need to configure a SIP trunk and add phone route plan to it.
  3. I did dual forking configuration and it worked, I didn’t find any document that explains how to it in details “If someone has such a guide please send it”, but after little testing I found that enabling enterprise voice with PBX integration and configuring the server URI to be (user@domain.com “Sip Name’), and the Tel URI to be (tel:xxxx “where xxxx is the telephone extension) did the trick for call coming from OCS to user “Note that we will use single extension in this case.
  4. Missed call notification get delivered to the user’s mailbox in the phone to PC, PC to phone, and dual forking.
  5. To do dual forking for calls coming to from phone to PC, we need Cisco unified presence server, this is very new Cisco product, attached the CUPS document “we will try to set this up next week”
  6. User’s phone numbers has to be in E.164 format in AD, redirecting the calls to CCM directly fails in this case because CCM fails to remove the + , so calls need to be forwarded to the Voice gateway first “we need to test that next week”.
  7. To have CCM/OCS integration you will need to have a SIP trunk between the Mediation server GW facing NIC and the CCM, otherwise it will not work (calls will get service unavailable errors).
  8. To have Voice-mail auto redirection (a phone missed called redirected directly to the extension’s Voice mail) you will have to enable caller-ID on the SIP trunk, otherwise the user will get an auto-attendant.
  9. For Auto-attendant feature in Exchange, just create a new auto-attendant as voice enabled, assign an extension and create an Extension routing rule on the CCM to redirect the call to the Exchange feature and it will work.
  10. To do presence integration you will need CUPS in-place, we didn’t have the time to test that.
  11. Feature that has been tested successfully:
  • PC to phone calls.
  • Phone to PC calls.
  • Dual forking (from calls coming from OC).
  • Multi-group conferencing (OC – Phone – phone).
  • Voice mail and missed call notification.
  • Call forwarding to phone, PC and VM.
  • OVA.

Notes from the field configuring and installing OCS and MP114

Here is a nice tip for MP114 configuration and implementation:

OCS is installed in Site1, MP114 installed in site2.

This decision was taken to test the functionality of MP-114 across multiple sites, and then MP-114 will be moved to Site1.

Configuring the OCS consists of the following steps:

  • Install Mediation server.
  • Configure the mediation server and add MP-114 as PSTN GW.
  • Configure default location profile, normalization rules for all of BMW sites, external call, and mobile calls.
  • Enable users for enterprise voice:

♦ Add telephone number, mobile number and work number in user’s properties in AD in E.164 format (+XXXXX)

♦ Enable PBX integration and add the Tel: URI

  1. Currently each user has to have separate extension for phone numbers and OCS number (to call the user fro phone to communicator), this is because dual forking is not currently available (simultaneous ringing on phone and OC), this will be available in the second quarter of 2008, for example to dial user x on phone call from OC he has to have extension 14000 (which is configured in the Tel: URI) and to call him from OC to phone he has extension 4000 (which is configured in the phone properties.

♦ Synchronize the Database with the new numbers:

  1. C:\Program Files\Microsoft Office Communications Server 2007\Server\Core>ABServer.exe –regenUR to synchronize the users from AD to OCS DB.
  2. C:\Program Files\Microsoft Office Communications Server 2007\Server\Core>ABServer.exe –synchnow to synchronize the address book with the users DB.
  • Configure the MP-114.

♦ The current PBX (HIPATH 5000) doesn’t understand the phone numbers in E.164 format, when we dial 4000 the normalization rule translate the number to +4000 format, this number is not understandable by the PBX, we use the protocol management > manipulation Table in the MP-114 GW to manipulate the destination number to remove the + (by stripping 2 numbers and adding the dial plan identifier) (attached the INI file for final MP-114 configuration).

  • Test the calls from OC to PSTN, PBX.
  • Calls are successfully done in local sites, across the sites (OC > GW > Local PBX > remote Site PBX), and thus we need single GW and single Mediation server for the implementation.

CCM 6 + CUPS + OCS 2007 integration notes:

I would like to summarize the integration notes for the above configuration, kindly find below the latest notes for OCS/CUP integration:

  1. To have CCM/OCS integration you will need to have a SIP trunk between the Mediation server GW facing NIC and the CCM, otherwise it will not work (calls will get service unavailable errors).
  2. To have Voice-mail auto redirection (a phone missed called redirected directly to the extension’s Voice mail) you will have to enable caller-ID on the SIP trunk, otherwise the user will get an auto-attendant.
  3. For Auto-attendant feature in Exchange, just create a new auto-attendant as voice enabled, assign an extension and create an Extension routing rule on the CCM to redirect the call to the Exchange feature and it will work.
  4. To do presence integration you will need CUPS in-place, we didn’t have the time to test that.
  5. Feature that has been tested successfully:
  • PC to phone calls
  • Phone to PC calls.
  • Dual forking (from calls coming from OC).
  • Multi-group conferencing (OC – Phone – phone).
  • Voice mail and missed call notification.
  • Call forwarding to phone, PC and VM.
  • OVA

Inbound/outbound faxing option with Cisco CM and OCS 2007

I have been asking a lot of MS and Cisco folks about the options of inbound and outbound faxing with Exchange 2007 UM and Cisco CM also known as CCM, I didn’t have a clear answer so I tried to figure it out, please keep in mind that the below lines doesn’t hold any official responses neither from MS nor from Cisco.

Let us summarize what we want to do:

  • Outbound faxing, meaning that the user will send an email to whatever server then it is sent as a fax to its destination.
  • Inbound fax, meaning that a sender send a fax to a user, the user gets the fax in his mailbox and open it using the outlook.

Pretty simple but hard to achieve, why, well I believe that this problem occur because Microsoft folks are not focusing in this part “looks like the R2 will have something to bring”, and Cisco is not playing fair with MS since they don’t let their technology work with MS specially in this part.

Let us design a simple design for inbound faxing:

The problem that we want to deliver the fax to the user’s mailbox, we will have UM and typically OCS, to achieve those 2 things has to be known:

  • Users’ external extension which must be unique.
  • Users’ email address.

The exchange 2007 UM server can intercept the fax signal and deliver the message correctly to the user’s mailbox, the problem that it doesn’t work fine with CCM, although that Microsoft inbound faxing relies on using t.38, Cisco uses t.38 as well but Cisco’s implementation relies on UDP while Microsoft relies on what…yes TCP and there is no way to change any of them to the other protocol.

So using t.38 while a Cisco voice GW inplace is not possible, so we will have to let the UM server intercept the fax signal and tries to do the job by enabling EnableInbandFaxDetection, I tried it with CCM 4.3 but it didn’t work “I will upgrade mine within 2 weeks to CCM6 so I shall give you what it does with CCM 6”.

So what is the available option, I believe that onramp http://www.cisco.com/en/US/docs/voice_ip_comm/unity_exp/rel3_1/administration/guide/voicemail/fxgatewy.html

And trying to deliver the fax either to a shared mailbox or specifically to the user.

Note: you can deliver the message directly to the user by configuring you DID distribution to be as following for example: suppose that you have xxxx5000 up to xxxx5100 as DID, so distribute odd numbers for users direct phone and even numbers for direct fax.

Configuring such a configuration poses a real challenge for organizations with large number of employees, but configuring a single extension for everything in the world relies on CCM to talk to Exchange server nicely.

For outbound faxing, Exchange UM doesn’t support using outbound faxing, but if you have Cisco GW inplace you can use offramp faxing, I didn’t go into designing it since I am waiting for my CCM6 boxes, once they are here I will post an update about if anything make any feature works, and about offramp design and implementation.

Restricted OCS Deployment ports requirements and firewall rules details

Here you can find a detailed table for ports requirements and firewall configuration for restricted OCS deployments.

The difference in this table that we have detailed as much as we can the different communication ports and firewall requirements for all of the segmented including internet, internal and enterprise voice communications.

We also detailed the ports and communication paths so it can be reader-friendly for the Security/Firewall engineers.

The wiki assumes that servers are deployed in the same VLAN and separated by a very restricted firewall configuration, Edge is deployed in the DMZ and again restricted firewall configuration is required.

Currently the document still being reviewed, but if you are interested in following it you will find it on the wiki, here http://social.technet.microsoft.com/wiki/contents/articles/ocs-2007-r2-firewall-port-settings.aspx

We will be publishing another one for Lync as well linked to the wiki and we will validate the wiki this week at a customer location and we will publish the updates later.

Reference: http://www.shudnow.net/2009/08/29/office-communications-server-2007-r2-audiomedia-negotiation/

Office Communicator cannot place calls to the Exchange Unified Messaging Auto Attendant

Over the past 1 minutes Office Communications Server has experienced TLS outgoing connection failures 1 time(s). The error code of the last failure is 0×80090322

In OCS 2007 R2 you might get the following error:

TLS outgoing connection failures.

Over the past 1 minute Office Communications Server has experienced TLS outgoing connection failures 1 time(s). The error code of the last failure is 0×80090322 (The target principal name is incorrect.) while trying to connect to the host “serer FQDN”.

Where Wrong principal error could happen if the peer presents a certificate whose subject name does not match the peer name. Certificate root not trusted error could happen if the peer certificate was issued by remote CA that is not trusted by the local machine.

Resolution:

For untrusted root errors, ensure that the remote CA certificate chain is installed locally. If you have already installed the remote CA certificate chain, then try rebooting the computer.

Cause:

This is mainly because of wrong certificate names, validate that edge and OCS front end have the correct FQDN (((Recently I found that FQDN configured in the OCS 2007 R2 Administrative console on Edge and on the front End is case sensitive and has to match the server FQDN and the Certificate FQDN letter cases so make sure that you have the FQDN has the correct letter cases so EDGE.domain.com is not like edge.domain.com)))

Poor OCS voice quality with Dell 760 onboard NIC

Well if you don’t know then it has been on the forums, some users complained from poor voice quality (OCS displays poor network quality), this has been reported with the onboard NIC, once changing the NIC problem solved.

This issue is with Windows XP, looks like something is wrong with the driver.