Remove From My Forums

Cisco UCM 6.0.1(a) and OCS 2007 Enterprise - Remote Call Control

Question
0

Sign in to vote

I am having some issues getting an Communicator 2007 client connected to my Cisco IP Phone using CallManager 6.0. I have gone through the OCS VOIP Guide and setup the Mediation Server and configured all of the settings that are required by OCS for RCC support, but I can not get the MOC client connected to Call Manager. When I log into the MOC client I get "Phone Integration Failed". Can not connect to remote PBX. I have a SIP trunk configured to my mediation server and I can telnet to port 5060 from the mediation server, so I know that it is not a network problem.

I also have the server URI configued in AD for my account, and the correct Telephone number is displayed using the "+" sign. Which leads to me one question does the phone attached to Call Manager have to be either a SIP or SCCP (skinny) endpoint? I have tried both and I am having the same result.

What are some things that I can try to get this working? I have also read that some people have gotten this to work without the CUPS Server, if so, how?

Thanks is advance.

Chris

Monday, January 7, 2008 10:50 PM

All replies

0

Sign in to vote

Hi Chris - welcome to the forums....there's a few of us now working on this whole Cisco/Microsoft UC thing....we're making progress but it's slow so stick with us and share your achievements and we'll all get there much quicker.

If you want to do RCC, you will need CUPS. CUPS does CSTA to SIP conversion (and vice versa) and this allows MOC to send commands to CUCM via CUPS. I have read here about using TAPI to do RCC but CUPS is far easier.

That said, you can still use MOC as an end point to make calls though CUCM but 6.0 doesn't like E.164 - OCS and MOC only support numbers in E.164. Just set up a user as an Enterprise Voice user and use a tel:+xxxx string as the Line URI - you must have the + for MOC to work but CUCM won't understand it but you'll still be able to make calls.

You won't be able to receive calls in this manner as CUCM does not know how to fork a call down to the SCCP phone and the SIP trunk at the same time - if I am wrong in this regard then someone let me know cos I'd love to get this running.

I hope to have CUCM 6.1 up and running here in our lab soon and I will see if things are improved on that front.

In short - it's the Line URI setting that is causing this error message for you - change it to E.164 and you should be OK to make calls.

Cheers!

Hendo

Tuesday, January 8, 2008 7:14 AM
0

Sign in to vote

Just fyi: when you are implementing RCC the OCS 2007 Mediation Server is not involved. It's not involved since all media exchange is happening between your PBX end-points, i.e. desk-phones or soft-client connected to the PBX. OC 2007 is involved in signaling, but not in the media exchange.

best regards

Jens

Tuesday, January 8, 2008 7:36 AM
0

Sign in to vote

Thanks for the replies, I am going to try some of the recommendations and let you know what I experience.

Thanks again, Chris

Tuesday, January 8, 2008 3:38 PM
0

Sign in to vote

Yep - forgot to mention that re the mediation server.

You only need the mediation server if you're going to to RCC and EV at the same time.....which you kind of can't at this time.

Cheers!

Hendo

Wednesday, January 9, 2008 12:51 AM
0

Sign in to vote

it is simple, u just go to OCS server,go to user then click properties for user. and go for server URI:

dont put anything for server URI:

if you fill with your usename@domain.com,then on your communicator it will show no phone integration

Wednesday, January 9, 2008 3:03 AM
0

Sign in to vote

HI Hendo,

You wrote:

"You won't be able to receive calls in this manner as CUCM does not know how to fork a call down to the SCCP phone and the SIP trunk at the same time - if I am wrong in this regard then someone let me know cos I'd love to get this running."

This statement is correct. you cant do it yet. Call forking is on the roadmap of both Cisco and MS so just hang in there. It should be a nice solutions when it comes. You are alos completly correct about the + sign. Callmanager at present doesnt understand the plus sign when doing call routing from OCS to Callmanager. RCC on the other hand Cisco have come up with a solution with 6.0 called application dialing rules. There isnt much information on their website other than the document outlined below. This shows how to integrate CUPS 6.X and Callmaanger 6.X to OCS for RCC.

http://www.cisco.com/application/pdf/en/us/guest/products/ps7240/c1237/ccmigration_09186a00808aea28.pdf

As for direct calls from OCS to Callamanger via a SIP trunk there are two solutions. A direct SIP trunk from the OCS mediation server to Callmanager 5.x or 6.x or from OCS mediation server to a Cisco router acting as a IP-IP GW which can interface to a 5.x,6.x or 4.x(using H3232) Callmanager. There is a third I forgot to mention. You can use back to back PSTN gateways between the two systems. Not very practical but I am sure it can be done.

Cheers

Chris

Wednesday, January 9, 2008 5:58 AM
0

Sign in to vote

Well I have been reading the Cisco document (you know the really well written one with all the Screenshots and no text to go with it) and I am still having issues getting RCC to connect, I am still getting "Cannot connect to the phone system" error message. I have tried to debug my CUPS server and I don't believe that the OCS is even making a connection to it. Also in regards to a previous post about leaving the Server URI field blank, I can not enable RCC with a Server URI in there.

Thanks in advance.

Chris

Wednesday, January 9, 2008 5:34 PM
0

Sign in to vote

Just another update, I configured the Cisco Personal Communicator to test my Cisco setup and it is all working fine. Just an update, I am still getting the message that " The call control server is not available."

Thanks, Chris

Thursday, January 10, 2008 5:30 PM
0

Sign in to vote

Don't forget to add a static SIP route in OCS to your CUPS server.

Go to Pools/Front Ends, right click properties. Select the routing tab. Add a static route where the domain is the FQDN of your CUPS server and put in the IP address of your CUPS server and port 5060 and TCP transport.

Don't forget to restart CUPS (this worked for me).

You should then set your Server URI for your user account to sip:username@yourcups.fqdn

You can leave the Line URI blank if you just want RCC but I have tel:7785.

I hope that helps!

Hendo

Friday, January 11, 2008 7:35 AM
0

Sign in to vote

Hi there,

A few things to check:

1) do your cisco usernames (in the cisco directory) match your OCS SIP usernames? they need to match exactly. Here's more on that

2) are you trying to get this to work on a phone that has a number that is shared between 2 other phones? if so, you will need to do some tweaking. Here's more on that...

3) make sure that you've created entries in CUPS for your inbound/outbound ACLs. don't forget the domain name.

4) make sure that in your server URI you have "sip:username@fqdn-of-cups-server.com" for example "sip:joesmith@cups.company.com" (and obviously you need a DNS entry for that servername) where "username" is both your OCS sign-in name AND your CallManager userID

5) for Line URI - I have "tel:1234;phone-context=dialstring"

Regards,

Matt

Monday, January 14, 2008 10:08 PM
0

Sign in to vote

Hello everybody,

I'm working to OCS 2007 and in my company we want to integrated a cisco callManager 6.0 with OCS but we don't know how configure them.

We succeeded in configuring the mediation server with a audiocode but we don't know how configured the callmanager and the mediation server. Is this the same configuration of mediation server?

Can you help me please, have you got a document which explain how configure them? (except the document Microsoft OCS_VoIP_Guide_FR.doc)

Thanks,

P.S: we have OCS Standard Edition, CallManager 6.0 and Gateway Cisco 2851.

Wednesday, January 16, 2008 8:57 AM
0

Sign in to vote

Hi,

I've succesfully integrated an OCS 2007 with UCM 6.1.1a and CUPS 6.0.2 in our lab. I configure my users for "Remote Call Control", and that works flawlessly.

The only trick is indeed to have the E.164 notation everywhere in your AD. From the moment you have a phone number which doesn't has one, the Address Book Server complains about it. That being said, is there a way to tell the AB Server to ignore certain fields?

Close to that question, I have also another question: it seems that the MOC client, will use the Work Telephone Number, as primary number to do the RCC. Is there a way to change all this? Let's say, I want to use the AD field "IpPhone"?

Thanks a lot!

Cedric

Monday, February 11, 2008 2:31 PM
0

Sign in to vote

Hi Cedric,

In answer to your question: "it seems that the MOC client, will use the Work Telephone Number, as primary number to do the RCC". It actually uses the number that you put into the Line uri field. So if you have it set up like this:

tel:1234;phone-context=dialstring

Then it's going to use 1234 as the RCC number. Most times that matches the work# (because that's often the "primary" number for a user at the office) but you can definitely change what number MOC controls by putting in a different number in the line URI field. If you do that, don't forget that you need to make sure that the Cisco user is associated with a phone that has the same extension.

And to your earlier point: you don't necessarily need E.164 all throughout AD, but it really does make things a bit easier. I've done it when the numbers aren't normalized & it causes you to have to mess with normalization rules. See this post from one of my co-workers on fun with normalization & RCC: https://blogs.pointbridge.com/Blogs/schertz_jeff/Pages/Post.aspx?_ID=17

Regards,

Matt

Wednesday, February 13, 2008 4:09 AM
0

Sign in to vote

Folks,

While we're on this CIsco/OCS topic, I was wondering if I could lay out our environment and ask you with what we have now, if it's possible to get UM working?

2 x Cisco VG200

2 x Cisco 7835 Devices running Cisco Call Manager 4.1 I believe

Exchange 2007 UM Server

OCS Mediation Server

I do have a Quintum Gateway as well. Is there any chance I can get this up and running without having to make a further investment into Cisco (i.e. upgrade CCM)?

Thanks

Thursday, February 21, 2008 5:40 PM
0

Sign in to vote

I think you're going to have to upgrade Call Manager mate.

Firstly, Exchange UM isn't supported with CUCM 4.x - only 5 and above. http://www.microsoft.com/technet/prodtechnol/exchange/telephony-advisor.mspx

I'm not sure about CUCM 4 and OCS support.

I hope that helps!

Hendo

Sunday, February 24, 2008 11:38 PM

mmcgille wrote:

Hi Cedric,

In answer to your question: "it seems that the MOC client, will use the Work Telephone Number, as primary number to do the RCC". It actually uses the number that you put into the Line uri field. So if you have it set up like this:

tel:1234;phone-context=dialstring

Then it's going to use 1234 as the RCC number. Most times that matches the work# (because that's often the "primary" number for a user at the office) but you can definitely change what number MOC controls by putting in a different number in the line URI field. If you do that, don't forget that you need to make sure that the Cisco user is associated with a phone that has the same extension.

And to your earlier point: you don't necessarily need E.164 all throughout AD, but it really does make things a bit easier. I've done it when the numbers aren't normalized & it causes you to have to mess with normalization rules. See this post from one of my co-workers on fun with normalization & RCC: https://blogs.pointbridge.com/Blogs/schertz_jeff/Pages/Post.aspx?_ID=17

Regards,

Matt

Hi Matt,

Thanks for your answer! In fact, I managed to solve my problem using the normalization rules using the Company_Normalization_blablarules file. Worked out great! Except for one thing, and I don't understand why:

- I create a new user in AD
- I give the user an exchange mailbox
- I make him OCS enabled

The user can use his or her moc client.

When a user that has RCC clicks on the user, it sees the new users phone numbers, as it is
supposed to be. So far so good. The normalization is also working great: In AD the number is: +3216382XXX, and on the communicator client I end up with 0016382XXX.

When a user that has RCC clicks the number, the ip phone of that user calls the clicked contact.
Wonderful! :-)

Ofcourse, I also want to enable Remote Call Control for that newly created user, so on the user's properties, I select Enable Remote Call Control and give the proper fields for Server and Line URI.

The stuff I put there are for example:
- Server URI: sip:<samaccount>@<fqdnofCiscoCUPS>
- Line URI: tel:0016382XXX;phone-context=dialstring

I resync everything from AD to OCS's SQL database using abserver.exe -regenUR and make sure that the Addressbook server recreates its flat files from the new data in SQL, using abserver.exe -syncNow.

From that moment on, when I click that "new" user on the contact list, his phone number is no longer there?!
What happened? What changed?

When I remove the RCC configuration, and put it back to what it was, (with the necessary resyncs and stuff), it still doesn't work.

When I view the AD properties of a "good" user which hasn't had any RCC config enabled, and I compare it with a user that has had RCC, using adsedit, I don't see any difference between the two, so there's nothing cached.

But why can't I see the numbers anymore?

This is quite frustrating as for this project, RCC is an absolute requirement :\

I tried removing the ";phone-context=dialstring", but that's obligated for Cisco Presence Server.

Even when just ignoring the Presence Server, it does not work when using the Line URI, without that string... .

Any help is really welcome,

Thanks a whole lot already,
Cédric

Thursday, February 28, 2008 4:15 PM

Heh.. I found out myself... .

And to me it's still pretty weird... . I know microsoft really likes the E.164 notation, but this doesn't make any sense:

Apparently, MOC requires that the phonenumbers of a person that has RCC enabled, are in e.164 format.

Because, I just removed my normalization rules that converted them from e.164 to internal dialplannumbers so that the callmanager could easily use them.

Right now, they show up, as perfectly as they can show up :-).

They do show the + sign, which I'll have to strip using the callmanager (no problem).

But what I don't get is why MOC doesn't care about this, when a new user is created (standard communicator-to-communicator). As said in my previous post, the numbers showed up just fine. They were converted from E.164 in AD, to 001638XXXX (internal).

I changed the user to RCC enabled and the numbers were gone.

I changed the user back to standard, and the numbers didn't show up again.

I'd say this is a bug, or something really inconsistent.

Either it should require e.164 on both RCC and standard, or not complain about it on both.

Or at least have it logged somewhere... it took me a lot of pain to find out that this was the actual problem! :-)

Anyway, thanks. I hope my experiences here might help someone later when he or she has the same issue. This is one I'll never forget though ;-)

Cédric

Friday, February 29, 2008 4:03 PM

Cedric,

You may want to check that the Address Book Service can normalize the number that is in AD. I had a site in which we integrated the OCS client for RCC utilizing the Avaya Application Enablement Services (AES) to an Avaya Communication Manager (CM aka PBX). You could not see the phone numbers for the user in your MOC Contact list. Once we fixed the normalization rules, you could then see them after you re-synch the address book service & update the local Global Address file on the client

by default:

%user profile%\Local Settings\Application Data\Microsoft\Communicator

You can test the normalization rules w/ abserver.exe

ie abserver.exe -testphonenorm <phone number>

by default abserver.exe should be in:

\Program Files/Microsoft Office Communications Server 2007\Server\Core

Regards,

Ken

Friday, March 7, 2008 7:10 PM

Okay, new question that I don't see specifically addressed here. I have most features of the CUPS-OCS integration working, but there is one thing that doesn't seem to work. When I use MOC to initiate an RCC call, the MOC client reflects my line status (In a call) until I hang up. But if I use the IP phone to make the call directly, the MOC client does not seem to reflect my line status. Is this working for other people or is this a functional limitation?

Fred Nielsen

Monday, April 21, 2008 6:57 PM

Okay, update... nevermind. I needed to restart services on my CUPS apparently. It is now working fine.

Monday, April 21, 2008 7:53 PM

Hey there Cedric. Do you have this documented somewhere? I'd appreciate if you could send more info on what guides you used to "succesfully integrated an OCS 2007 with UCM 6.1.1a and CUPS 6.0.2 in our lab. I configure my users for "Remote Call Control", and that works flawlessly"

Thanks in advance.

- R.

Monday, April 28, 2008 3:35 PM

You mentioned stipping the + sign is no problem in CallManager... I am trying to figure out how to do this and haven't had any luck yet. I'll have to strip the + from extensions like +3350 and full numbers like +912123531234

Saturday, May 3, 2008 1:28 AM

I don't know how to do it in Cisco - I never used it, sorry...

In OCS it is impossible by design & possible by patching it (OCS).

That's the answer.

As for me, I write the SIP interoperability proxy to fix the problem without violating Microsoft EULA on OCS server to deploy OCS in mixed topology.

Saturday, May 3, 2008 1:35 AM

Hi Markus,

To strip the + in Call Manager, you need to create an "Application Dial Rule". This only affects calls initiated via CUPS (and therefore OCS).

I hope that helps!

Hendo

Saturday, May 3, 2008 1:42 AM

Hey Cedric - would you be able to post a copy of your Normalisation Rules file so we can get some idea as to how you're doing it?

Cheers!

Hendo

Saturday, May 3, 2008 1:45 AM

Yes indeed! I finally found a Cisco document for integration and I saw what you talk about in there as well. I created the rules and everything is working great. Now of course reverse number lookup is another story!

Saturday, May 3, 2008 1:05 PM

The regedit update to HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Communicator\

Is a DWORD parameter named EnablePhoneControl = 1.

Do both EnablePhoneControl = 1 and TelephonyMode =2 have to be added?

Thanks

Dan

Monday, November 3, 2008 6:28 PM

Asked by:

Cisco UCM 6.0.1(a) and OCS 2007 Enterprise - Remote Call Control

Question

All replies