Skip to main content

Calls cannot be established to UM for external users

I have faced a problem when integrating Lync with Exchange 2010 UM , where calls could not be established to UM for external users, whenever i call the susbscriber access from the Internet i get the following error:
"call failed due to network issues. try logging out of lync logging back in, or try again later"
After revewing the logs, i found the following entry in the event viewer on the Lync front-end server :

Event ID: 1400 Source: MSExchange Unified Messaging



The following UM IP gateways did not respond as expected to a SIP OPTIONS request.


Transport = TLS, Address = lyncfe.domain.com, Port = 5061, Response Code = 0, Message = This operation has timed out.
Solution:
Issue a certificate dedicated to UM, where the subject name is the FQDN of the UM server.


Comments

Popular posts from this blog

Upgrade from Lync Evaluation edition to Lync RTM.

If you have installed Lync Server using the 180 Day  trial bits  you can upgrade to the RTM bits nsing the following easy steps: Run setup.exe on your Lync server Volume License media. Click on "Install or Update Lync server system" Click on "Setup or remove Lync server components" Open CMD and  navigate to \Setup\amd64\setup and then run msiexec.exe /fvomus server.msi EVALTOFULL=1 /qb  Open Lync Server Management Shell and then run Enable-CSComputer and then you are done !

Exchange 2010 - EMC "RBAC authorization returns Access Denied"

I was doing an Upgrade for Exchange 2003 to Exchange 2010 and after i installed the first CAS server and opened the EMC an error appeared that i have no permissions... while i was logged in with the setup account and it was a memeber of the Organization Managemnet Group. and i founbd this in the Applicaiton Log  "(Process w3wp.exe, PID 6716) "RBAC authorization returns Access Denied for user Udomain.Local/Users/AccountName. Reason: No role assignments associated with the specified user were found on Domain Controller XXXXX" " After alot of searches i was pulling my remaining hair out :)  I  found this post ( http://social.technet.microsoft.com/Forums/en-US/exchange2010/thread/fc568cc6-8691-4127-b70b-bcc82f9b1f7f?prof=required ) The issue was with 2 things : Allow inheritable permissions check Box was not enabled on the Exchange  Microsoft Exchange Organzaiton container inside the Configuration partition. The value for the attributes msExchRoleLink ...

the networkmanager has not yet been initialized

I faced a very strange case with Exchange DAG, I was doing a site resiliency test I failed over to the DR site successfully and then I failed back to the main site, after failing back I found that the DAG was in a state that looks like split brain syndrome although the DAG was running in DAC mode. the symptoms were as follows: From the DR mailbox server: Cluster Console only showed this node while the active nodes were not present. From EMC the copies on the DR server were healthy. From the Main site mailbox servers: Cluster console showed the three nodes but the DR node was stopped, and the option to start it was grayed out. From EMC the copies on the DR server were failed. The fix was as follows:  run the following command: Cluster       /forcecleanup Then run the following: Start-DatabaseAvailabilityGroup "DAGname" -MailboxServer  "DRNodeName" After the first command you will find that the DR node can see the oth...