Welcome to MSDN Blogs Sign in | Join | Help

Cristiano WebLog

Microsoft Infrastructure & Development Tips and Tricks
How to setup Live Communications Server 2005 and Cisco Call Manager 4.1 to VoIp –PSTN convergence

Hello! Now I want to share with you some tips on configuring LCS and its client  Office Communicator to originate VoIp calls to a Cisco SCCP IP Phone or conventional PSTN phones through a Cisco Call Manager 4.1 SR3.

 

Many companies setup Cisco Telephony over IP environments and don’t know they can use Office Communicator and LCS 2005 to place calls to the VoIp and PSTN clouds just using the already in-place Cisco infrastructure.

 

I mean, the companies do not need a special gateway just to make VoIP and PSTN calls from Office Communicator using their in-place Cisco Call Manager 4.1.

 

In fact, they still need a gateway if the goal is to make signaling (3PCC/CSTA) integration.

 

Actually I have a customer using Cisco Call Manager 4.1 to place VoIP calls to all their IP and PSTN phones using the integration already made between the CCM 4.1 and the corporative PBX.

 

Before to start with the configuration steps I’d like to list what will work after the setup:

 

  • Calls can be placed from LCS (Office Communicator) to another VoIP phone “connected” through CCM.
  • Calls can be placed from LCS (Office Communicator) to PSTN phones through CCM. 

What will not work?

 

  • Transfer, conferencing and call forwarding from Office Communicator (LCS) side. [Requires a CSTA/3PCC gateway]

First let’s check the network topology.

 

 

 

Now the steps.

  

  1. Open the Microsoft Office Live Communications Server 2005 MMC administrative console.
  2. Expand the forest node, the domain node and the Live Communications Servers and Pools node.
  3. Click with the right button on the LCS Pool and create an outbound static route pointing to the Cisco Call Manager with the following information:
    • User: *
    • Domain: <LCS POOL FQDN>
    • Next Hop IP address: the IP address used by Cisco Call Manager
    • Next Hop Transport: TCP
    • Port: 5060
    • Phone URI: Checked
  4. On the Host Authorization Tab, include the IP of the Cisco Call Manager as a Authorized Host. Use the following options:
    1. Server IP Address: the IP address used by Cisco Call Manager
    2. Settings:
      • i.      Throttle as Server: Checked
      • Treat as Authenticated: Checked
  5. Open the CCM Administration web page and create an incoming partition (probably it will already have one).
  6. Create a new SIP Trunk with the following options:

Device Information

 

    1. Device name: LCSSIP
    2. Device Pool: Default
    3. Call Classification: Use System Default
    4. Media Resource Group List: Select appropriate list.
    5. Location: None
    6. AAR Group: None
    7. Media termination point required: Checked
    8. Destination address: the IP address used by LCS
    9. Destination port: 5060
    10. Incoming port: 5060
    11. Outgoing transport type: TCP
    12. Preferred Originating codec: 711ulaw

Call Routing Information

 

a.      Significant Digits: All

b.      Connected Line ID Presentation: Default

c.      Connected Name Presentation: Default

 

  1. Create a Media Termination Point using the Add Media Termination Point on the CCM web administration.

You also need to setup a registry key (manually or using Group Policies) to enable the PC2Phone functionality on your Office Communicator.

 

[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Communicator]
"EnablePC2Phone"=dword:00000001

On the COMMUNICATOR.ADM template this configuration is named "Enable Computer to Phone Calls".

 

Now go to the Office Communicator and just type the phone number on the Find box, click on Call to place Voip or PSTN calls through the CCM 4.1. You will also notice that the combo box on the side of your contacts is now enabled.

 

Regards, Cris.

This posting is provided "AS IS" with no warranties, and confers no rights.

Posted: Thursday, September 28, 2006 11:48 AM by crisag

Comments

jslande said:

I understand that the optimal way to test this would be to have both a test server for LCS and a test server for cisco call manager.  We currently have a test server for CCM, but do not have a test LCS server, because we would need to build a new forest to set this up.

What is the level of risk to the LCS farm to set this up?  Is there any easy way to set this up without the need for the additional forest?  I realize that a new farm could be setup for LCS, but then that farm would be available to "mispick" in our account creation process.  We are looking for a good way to test this with minimal amount of work and risk.

# October 13, 2006 9:46 AM

crisag said:

Hi. I guess the minimum level of risk is create a LCS setup with a new forest (LCS requires some schema changes). For test purposes you can create the environment using virtual machines. You can download virtual server for free on www.microsoft.com/virtualserver

Regards, Cris.

# October 17, 2006 8:26 AM

John Gruber said:

OK.. tried this..

LCS sends the invite from first.last@domain to number@ccm.  CCM says: I don't know who the invite is. How do I get LCS to rewrite the invite to work through the trunk.  I.O.W invite from my from :phoneextension@lcsserver to number@ccm.  

Thanks in advance...

# November 30, 2006 3:01 PM

crisag said:

John. Have you configured the ip phone (number) on CCM? Can you make a call to the phone using the number? you don't need to rewrite the invite to get this working. I've configured on two customers and I didn't need to rewrite the invitation.  

# November 30, 2006 3:31 PM

jens said:

Hi Chris,

is the way back form CCM to LCS working as well? or just one way call setup?

Cheers jens

# December 18, 2006 10:32 AM

Ted said:

Wow, this is pretty neat. I just tried this out and it works. The only issue I have is that the audio sounds weird. Any ideas why this would be?

# January 20, 2007 4:10 PM

tgann said:

I followed your setup and everything works great as long as the call is initiated from the LCS client. I can not figure out how to call the LCS client from the SCCP phone. Any thoughts?

# February 5, 2007 4:00 PM

Simon said:

Cris,

Does this communication allow the Cisco IP phone presence to be passed back to LCS ?

# February 8, 2007 12:58 PM

Ray Ryan said:

iQ NetSOlutions offers a  CSTA/3PCC gateway for the Cisco CallManager. iQ's LCS Gateway for CallManager will provide the telephony presence and control needed to fully integrate the Office Communicator with CCM.

# March 22, 2007 4:51 PM

Bin Liu said:

We  got 404(user not found) error ,when try  to setup Live Communications Server 2005 and Cisco Call Manager 4.1 to VoIp –PSTN convergence.

Following is our environment

LCS(2005 SP1): 10.140.15.160

Call Manager (4.1 SR3): 10.199.47.1

LCS   Call manager  SCCP Phone

We following setup guide, setup

1. Open the CCM Administration web page and use an incoming partition.

2. Create a new SIP Trunk with the following options:

Device Information

a. Device name: LCSSIP

b. Device Pool: Default

c. Call Classification: Use System Default

d. Media Resource Group List: Select appropriate list.

e. Location: None

f. AAR Group: None

g. Media termination point required: Checked

h. Destination address: 10.140.15.160

i. Destination port: 5060

j. Incoming port: 5060

k. Outgoing transport type: TCP

l. Preferred Originating codec: 711ulaw

Call Routing Information

a.      Significant Digits: All

b.      Connected Line ID Presentation: Default

c.      Connected Name Presentation: Default

3. Media Termination Point was created.

The Sip Trunk was established, but CISCO return 404 error following is detail message.

Date: 2007/03/26 03:49:11

Direction: Incoming

Peer: 10.199.47.1:5060

Message-Type: Response

Start-Line: SIP/2.0 404 Not Found     

To:  <sip:8326@gzvs160.amwaylcstest.com;user=phone>;tag=16926471

From:  "user5" <sip:user5@amwaylcstest.com>;tag=1e6d2d62df;epid=16abd61012

Call-ID:  aaa5b9d0fa364c1f8772a52e3e029f3b

CSeq: 1 INVITE

Via:  SIP/2.0/TCP 10.140.15.160:4473;branch=z9hG4bKE36047D3.9AA65DF4;branched=FALSE,SIP/2.0/TCP 10.140.164.131:9122;ms-received-port=3274;ms-received-cid=200

Content-Length:  0

Other-Headers: Date:  Mon, 26 Mar 2007 03:47:28 GMT

Other-Headers: Allow-Events:  telephone-event

Could you give us any advice? Is there something we missed ?

# March 26, 2007 5:20 AM

Kanexu said:

I'm trying to use a CCM 4.1 R3 as a voip gateway for LCS in a PC2Phone only scenario.

I can use a Softphone and dial 3001@10.10.1.250 (where 10.10.1.250 is CCM address) but when I try to call using Communicator/LCS I get an error. When looking at the network capture the error is:

SIP/2.0 404

What's the problem?

Thanks, Kane

# March 27, 2007 3:50 AM

crisag said:

Kanexu. 404 states to not found. Please check if the outbound route is correct. Could you please post more information about the error... it's hard looking just the error code. :) Bye!

# May 3, 2007 2:56 PM

crisag said:

Bin Liu, can you use the standard IP phone to dial to 8326 extension? Could you please share the outbound route information? And about the LCS log, any error message?

# May 3, 2007 3:04 PM

crisag said:

Simon, answering your question. No with the out of the box product. With LCS 2005 there is no out of the box functionality allowing a reverse search against Active Directory, as a result you cannot answer calls using Office Communicator.

There are two solutions: 1. Develop a LCS script that makes the reverse search. There is a sample on SDK. 2. Wait of OCS 2007 and Office Communicator 2007. It will support Phone2PC scenario.

Regards!

# May 3, 2007 3:09 PM

crisag said:

Ted. Check your codec configuration.

# May 3, 2007 3:13 PM

drumania said:

Hi Cris,

We tried these steps and getting error code 403 now. I pasted error message below.

P/S : OCS server and CCM servers are not in the same domain. Is that causes to a problem?

Could you please help us?

Error message :

Session State: Idle->Connecting

Provisional Response: 100 Trying

Provisional Response: 101 Progress Report

Diagnostics: Error ID=14011

  Reason=Called Number translated

Source=ocsserver.domain.ist

  rulename=rulename

  appname=TranslationService

  translatednumber=+902123650369

  callednumber=1369

ruledn=CN={6D7747ED-E05E-4137-A380-030ACEE2B8A3},CN=Location Normalization Rules,CN=RTC Service,CN=Microsoft,CN=System,DC=domain,DC=ist

Exception Message: Not authorized to perform the requested operation, request is refused

Response Code: 403 Forbidden

Diagnostics: Error ID=12004

  Reason=No route found

  Source=ocsserver.domain.ist

  appname=OutboundRouting

Session State: Connecting->Idle

Ozan Oguz

mail : ooguz@inteltek.com.tr

# April 14, 2008 7:02 AM

AndreiGosman said:

Hi Cris,

I have a problem regarding OCS and CCM 5.1.

I have followed you post step by step and I still get some errors from Ofice Comunicator when I try to place a call.

I have installed OCS Standard Server and the eror message is : "Dialstring phone context used no translation" and "No route found"

I've tried to define a route, but in the route definition I have no gateway listed and I also cannot install mediation server.

Do you haped to have a clue about all of these?

Regards

Andrei Gosman

# June 4, 2008 10:16 AM
Anonymous comments are disabled
Page view tracker