So I recently worked with a customer that had removed their mediation servers without decommisioning them. This causes a problem because if the servers no longer exist within the directory, running the decommision will only return an error.

One approach would be to use adsiedit to locate the GUID of the mediation servers in the configuration containter and remove them. I think this is a fine method if you are comfortable with using adsiedit. If you are not comfortable, my recommendation is to use the OCS resource kit. You can download the OCS resource kit for here:

You will need to use the command prompt and navigate to the directory where the resource kit installed. Here are the commands you want to run:

cscript OCSTrustEntry.vbs /Action:List /Type:TrustedService

This will give you a list that you will need to navigate through to find the mediation server. What you will need is the GUID. Once you have found it, you then only need to run this next command to remove it:

cscript OCSTrustEntry.vbs /Action:Remove /Type:TrustedService /CN:<{your guid goes here}>

Tagged with:  

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.


Tagged with:  

Okay, I made this post because this can be a very frustrating issue to deal with. The scenario is that you may have created a voice policy or dial plan, attached them to a user and then you later delete them without removing them from the user. The Lync Administration Console will allow you to do this and the result is that you will get a warning in Lync for that user stating “DialPlan” with identity “1″ assigned to (all my Lync enabled users) has been removed from configuration store.”, or something similar.

So now what? You can’t change it in the administration console. What you need to do now is run a commandlet (from the powershell) to set the value for that user.

The first commandlet to run is Get-CsUser -Identity “<whatever username you want to view>” This will tell you details about that user including the dial plan or voice policy. You should also see an error in yellow text similar to the one seen in the administration console.

The second commandlet to run is Grant-CsDialPlan -Identity “<whatever username you want to edit> -PolicyName $null” This will set the user’s dialplan to the global dialplan. The command for changing the users voice policy follows the same syntax “Grant-CsVoicePolicy”

Afterwards you can run the Get-CsUser commandlet and see that the errors are no longer there.

Tagged with: