Home > Lync > Integrating Microsoft Lync and Cisco Unified Communication Manager Part 3: Configuring CUCM to Route Calls to Lync

Integrating Microsoft Lync and Cisco Unified Communication Manager Part 3: Configuring CUCM to Route Calls to Lync

So I said I wasn’t going to do this part, but I have received some feedback that people would like one location to go to in order to get an end-to-end configuration. In Part 2 I showed the necessary configuration on the Microsoft Lync side to set the Cisco Subscribers as the PSTN gateway for Lync.

There are a number of steps that need to be done successfully for you to be able to make calls between Lync and Cisco phones, those steps are identified below:

  • Identify or create a region
  • Identify or create a device pool
  • Identify or create a partition
  • Identify or create a calling search space
  • Create the SIP trunk
  • Create the Routing Pattern
  • Create the Translation Pattern

Identifying or Creating a Region

A Region is used to specify codec and bandwidth for audio calls within that Region and between Regions. As I have already noted, the Lync Mediation Server role will take RTAudio media from a Lync Client and will transcode RTAudio media to G.711. Therefore we need a Region that supports G.711.

The image below shows a Region LyncRegion and the important part to note is the relationship LyncRegion has with other regions should always have the Audio Codec set to G.711.

 

Identifying or Creating a Device Pool

Device pools are used to define a common set of characteristics like SRST (Survivable Remote Site Telephony) gateway reference, Music on Hold sources and much more. For our purposes it tells the device which Region it belongs to. Now that we have established a Region that will dictate what codec we will use, we now need to identify or create a device pool that the SIP trunk will eventually belong to. Our Device Pool Configuration is shown below, notice that we have selected LyncRegion as our Region:

 

Identify or create a partition

Partitions are logical subsets of a route plan based typically based on location that facilitates call routing. We have created our own Partition shown below called LyncPartition

Identify or create a Calling Search Space (CSS)

A CSS is an ordered list of partitions that Cisco Unified Communications Manager uses to search when a device makes a call. Our CSS (LyncIncoming) will contain our Partition (LyncPartition) plus any other Partition configured in the organization that we want Lync to be able to call across the SIP trunk.

Creating the SIP trunk

The next step is to create the SIP trunk that will identify how Cisco and Lync will communicate. The important items to fill out:

  • Device Pool = The Device Pool we created (LyncDP) that is in the Region (LyncRegion)
  • Media Resource Group List = A list of MTP resources available at the local site. In our instance we have created a MRGL that contains the MTP resources on the Subscribers (UPXMTP1).
  • Media Termination Point Required and Retry Video Call as Audio Call must be selected
  • Inbound Calls CSS = LyncIncoming
  • DTMF Signaling Method = No Preference
  • MTP Preferred Originating Codec = G711ulaw
  • Destination Address = IP of Mediation Server (or Front End server if collocated)
  • Destination Port = 5068 (default TCP port for Mediation role on collocated FE Server)
  • Rerouting Calling Search Space = LyncIncoming


Create the Routing Pattern

A Routing Pattern is pretty self-explanatory; a pattern of digits that are entered in the Cisco environment will be handled according to a rule created in the routing pattern. For our environment we decided that the numbers 7000-7999 would be routed to Lync. Therefore, our routing pattern will be configured to send 7xxx to the SIP Trunk created above named Lync.

Create the Translation Pattern

We are going to demonstrate how to create 2 different translation patterns for our enterprise. The first will translate calls from Lync to the PSTN for calls in North America; the second will translate calls from Lync to CUCM extensions in our main office (all 248555 DIDs).

Lync to PSTN Routing Pattern

  • Translation Pattern: XXXXXXXXXXX (that is 11 X’s)
  • Partition: LyncIncoming
  • Numbering Plan: NANP
  • Discard Digits: PreDot
  • Prefix Digits (Outgoing Calls): 9

Lync to CUCM Routing Pattern

  • Translation Pattern: 1248555XXXX
  • Partition: LyncIncoming
  • Numbering Plan: NANP

 

About these ads
Categories: Lync
  1. Ojum Christian
    May 15, 2011 at 6:31 am

    I’m a Cisco UC Engineer and just visited this site for information on Cisco UC and MS Lync. I must say that the information here is a very good one – acurate and straight to the point.

    If possible i will like to be receiving posts from you on my email. You are doing a grate job. Well done !!!!

  2. James
    October 14, 2011 at 7:11 pm

    Thank you for this! This has saved me loads of time. Question on your call routing. You have Lync –> Cisco example is works flawless. What I don’t see to get is the Cisco –> Lync calling. Ideas?

    Thanks!

    J

  3. vishnu
    January 15, 2012 at 8:38 am

    Thanks a lot its

    • June 9, 2012 at 10:09 am

      Hi Sam,I too have conducted the occsoianal call on gogo wifi while at 36,000 feet. In some cases it’s been surprisingly good (latency being the most noticeable part of it). In others it’s been entirely dysfunctional. Packet loss of 30% or more, etc.Same experience at public wifi hotspots. You rarely know what you are going to be getting, regardless of whether you use a PC or a mobile wifi client. If you are planning an outbound call, you can test the network (for example with Lync’s echo service, or using the PreCallDiagnostics tool, or running some pings) and decide to use your Lync client if the network is decent. That’s your coffee shop experience, and it’s still there on your laptop (which by the way still gives us orders of magnitude more capabilities to heal the media and make it sound good as compared to a mobile device).On the other hand, as an Enterprise Grade client, you must be able to receive or place calls quasi-instantly, without having to test the network first or reconfigure everything. Most users are just not as geeky as the rest of us. They want it to just work, regardless of whether they are in the right hotspot or not.As for your last point why not enable the users for EV? I don’t care if they still have a phone on their desk or not. But what I am sure of is that you can enable them for EV for less cost than most FMC solutions out there And yes, we hear the feedback. And nobody is saying Microsoft is not working on the next layer of capabilities beyond what you just saw. Our point is only that we had to first build a very solid layer of Enterprise Grade capabilities as a foundation. We hope we have done that.Thanks

  4. Robin Prado
    January 20, 2012 at 10:26 am

    Excellent post. I appreciated the listing of the items to check on the SIP Trunk config. I had missed the Rerouting Calling Search Space = LyncIncoming section, and that solved the problem I was having with calls flowing from Lync to CUCM extension. Thanks so much!

  5. Joel
    March 7, 2012 at 11:32 am

    So I have our Lync server all set up…I can make outgoing calls, but I cannot receive them on my client. I have the URI fully populated with my direct line. Why can’t I receive calls?

  6. Sahil
    March 8, 2012 at 12:30 am

    Excellent Job–>Specially calls flowing from Lync to PSTN via CUCM

  7. hamed adel
    March 14, 2012 at 8:21 am

    i have integrated CUCM 8.5 with lync with direct sip only with hardware MTP, and the calls working good but voice only not video, what is your suggestation

    • April 26, 2012 at 9:18 am

      Calls/Video between Cisco and Lync or Lync to Lync? Have you implemented QoS and CAC?

  8. Ron
    April 25, 2012 at 10:26 am

    Mark, great posts! Can you please provide the version of CUCM & IOS/Feature level of the Cisco 2851s?

    • April 26, 2012 at 9:17 am

      Thanks Ron! This version of CUCM was 7.1 and the IOS for the 2851 was 12.4(21T) with the IPT Feature set which is not completely required, just what I had.

  9. May 15, 2012 at 2:52 pm

    Excellent posts! I came across your blog as my company has deployed Lync and I need to integrate it with CUCM. I did install the Lync-UC client side (CiscoUCIntegrationTMforMicrosoftLyncK9) and created the CSF device with same DN and it all works great without SIP trunk… but what about conferencing resources? Lync does provide these capabilities and based on this post I will need a sip trunk to Lync between servers. Being that the case, how will the client and CSF devices be used? Can I delete them and just have a new DN range for Lync client? Anyways, thanks for the post and I do appreciate your feedback!

  10. May 15, 2012 at 2:57 pm

    Reblogged this on Cisco VoIP, My Experience! and commented:
    Excellent post from UnplugThePBX!

  11. remy
    August 17, 2012 at 5:39 am

    great post, thanks so far. i have an additional question: we’ve managed to make calls from lync to cucm, but not the other way around.
    we would like to have no specific extensions for lync. no DN’s for lync users.
    instead we are trying to make use of @
    allthough we have configured this trunk in cucm the calls do not end up at lync.
    we want to keep both cisco ip phone and lync and have them ring simultaneously.
    any suggestions?

  12. April 11, 2014 at 12:09 am

    Wonderful article! This is the kind of information that
    should be shared across the internet. Disgrace on Google for now not positioning this put up upper!

    Come on over and seek advice from my web site .
    Thanks =)

    • April 11, 2014 at 8:05 am

      Thank you – I appreciate it

  13. April 11, 2014 at 12:22 am

    This post gives clear idea for the new viewers of blogging,
    that genuinely how to do blogging.

  1. March 16, 2011 at 6:59 pm

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

Follow

Get every new post delivered to your Inbox.

Join 28 other followers

%d bloggers like this: