locked
Lync 2010 with Exchange 2013 UM RRS feed

  • Question

  • Hi,

    I am currently in the early stages of a large migration from Exchange 2010 to Exchange 2013. We have moved some test user mailboxes over to Exchange 2013 however have stumbled at the UM integration.

    We have 2 x CAS and 3 x Mailbox servers with Lync 2010.

    When a user diverts his/her calls to VM, the calls just cuts off and we get "Unable to establish a connection. No connection could be made because the target machine actively refused it 1.1.1.2:5061.

    We get this message for all 3 Mailbox servers that it attempts to route the call too. Mailboxes servers listen on 5063 for TLS in Exchange 2013 and these cannot be changed. So what is going wrong with my setup?

    Only the CAS are members of the DialPlan (we have tried putting the mailboxes servers in the dial plan with no avail).

    Shouldn't the CAS servers redirect Lync to the Mailbox servers on 5063 instead of 5061? Why is Lync trying to connect on 5061 (I know why, but how do I stop it!)

    Many Thanks,

    Eddie

    Thursday, April 18, 2013 8:25 AM

All replies

  • You need both the CAS and Mailbox servers in the Dial Plan. I've actually blogged the entire process for Exchange 2013 and Lync 2010 integration.

    Follow my guide here:  http://www.exchange2010.com/2012/11/configuring-exchange-2013-unified.html

    Oliver


    Oliver Moazzezi | Exchange MVP, MCSA:M, MCITP:Exchange 2010, BA (Hons) Anim | http://www.exchange2010.com | http://www.cobweb.com | http://twitter.com/OliverMoazzezi


    Thursday, April 18, 2013 1:10 PM
  • Thanks for the response and it was your blog that I followed in the first place ;-)

    When the Mailbox servers are in the Dial Plan, the Lync front ends go straight to the Mailbox servers on port 5061. They will never attempt to connect on any other port.

    We are running Lync HP, it is based on CU4 and cannot be updated. Is this the issue?

    Thursday, April 18, 2013 3:02 PM
  • Hi there,

    I believe I had a similar issue and I had to upgrade to CU7 for the fix!. The call would just cut off otherwise. Most annoying.

    Oliver


    Oliver Moazzezi | Exchange MVP, MCSA:M, MCITP:Exchange 2010, BA (Hons) Anim | http://www.exchange2010.com | http://www.cobweb.com | http://twitter.com/OliverMoazzezi


    Friday, April 19, 2013 2:54 PM
  • Oh dear.... Thanks for the reply.

    Exactly what's happening to me.

    Eddie

    Monday, April 22, 2013 7:26 AM
  • Did anyone get resolution to this?  I have exactly the same thing happening although Lync is running the latest cumulative update in my case.  Lync tries to hand the call off to the Exchange 2013 MAILBOX server (even though both the CAS and MB  servers are associated with the dial plan) AND it tries to do it on port 5061.  Unfortunately you cannot change the listening port on an Exchange 2013 mailbox server. 

    Sigh!

    Thursday, May 9, 2013 7:24 AM
  • In my case it were Active Directory attributes of object

    CN=MCA1,CN=Servers,CN=Exchange AdmGr...DC=local,DC=com

    The attributes msExchUM* weren't configured at all, despite being set by GUI and PShell. I had to set them manually through ADSIedit.msc and UM began to work after restarting Lync Server.

    I need to investigate further why they aren't set.

    Saturday, February 14, 2015 12:41 AM