The installation of Microsoft Lync is fairly straight forward, but sometimes you get it all setup and configured and things just aren’t working. What do you do? Where do you start?
My first recommendation is to download Wireshark from here, this tool will help you identify problems with your network traffic. For example, if you are trying to use enterprise voice features by integrating Lync with Cisco CallManager you could filter on “sip” to see if the traffic is making it to it’s destination. Cisco could be throwing out an error that wireshark will pick up on.
Check your ports. I recommend using TCP instead of TLS when initially setting up Enterprise Voice because it eliminates the potential problem of a certificate not being registered properly. Since we are using TCP you want to make sure that you are using port 5060 (TLS is 5067). On Lync you will see this on the PSTN/gateway and also on the Mediation Server. If you are integrating with Cisco CallManager you want to look at your SIP trunk and make sure 5060 is the port you are using. Also look at your SIP Trunk Security Profile to make sure that TCP is being used for both inbound and outbound traffic, and also make sure port 5060 is listed. By the way, in Lync you will see a port setting that you cannot change “SIP Server Port” it is set to 5070. That is what it is supposed to be, so you can ignore that.
Make sure your mediation server service is running. I have seen a case where mediation server was set to be installed and for some reason the service was not installed. If you are running wireshark and notice that no traffic is leaving the Lync server it is highly likely that the mediation server service is not running and may not be installed. The quickest fix for this is to re-run the installation. Don’t worry your configuration will not disappear. I should also mention that in the one case where I saw this happen, it looked as if the mediation server service was installed when you looked at the Lync Administration Console, but don’t let that fool you. Run this commandlet (in the powershell) to view the services running: “Get-CsService”
To see a full list of commandlets you can view the document here.
Check your dial plan and voice policy. I would use the global versions rather than creating new ones just so you can make sure the right plan and policy is being applied. Check your normalization rules and use the tester to make sure the right rule is being applied. Keep in mind that Lync to Lync calling using an extension requires the number to be in e.164 format (also make sure you check the box for internal) if you are setting up a normalization rule for external calls or extensions managed by CallManager, some versions of CallManager do not support e.164 format so do not add the “+”.
My last recommendation is to avoid migrating/merging anything that is broken in OCS. If you have mediation servers on the OCS side that need to be removed make sure you run the decommission before you take them offline. If you don’t you will need to jump through some hurdles to remove them from the OCS configuration. If that has happened I would recommend that you resolve that issue before merging/migrating.