Archive for the ‘Lync 2013’ Category

Meet innovators and explore tomorrow’s tech at Microsoft Ignite 2017

Microsoft Ignite 2017 is around the corner and you can Join us at Microsoft Ignite! Connect with your community, choose from over 900 sessions, and explore new tools and tech.

Go Here for registration

Also you can Sway your boss using email template 🙂

How to remove old StaticRoute for a particular sipuri and add new

December 14, 2016 Leave a comment

a) Before you start , take the backup of static route using below cmdlet

Get-CsStaticRoutingConfiguration | Export-Clixml C:\Temp\StaticRout_Backup.xml

Get-CsStaticRoutingConfiguration | Select-Object -ExpandProperty route | Out-File C:\Temp\Stati.txt

b) Find out the SIPUri which need to remove:-

  • Below cmdlet will provide all the static route  configured in the Lync Topology, and choose sipuri name which need to remove

Get-CsStaticRoutingConfiguration | Select-Object -ExpandProperty route

     Get-CsStaticRoutingConfiguration -Identity   Service:Registrar:LYNCPOOL-FQDN | Select-Object -ExpandProperty route | Where-Object{$_.matchuri -eq “vcservice”}

c) Take output of StaticRoute into a vairiable using belowcmdlet

$apmatchuri = Get-CsStaticRoutingConfiguration -Identity Service:Registrar:LYNCPOOL-FQDN | Select-Object -ExpandProperty route | Where-Object{$_.matchuri -eq “vcservice”}

d) Use below cmdlet to remove route for required Sipuri (example :- vcservice)

Set-CsStaticRoutingConfiguration -identity Service:Registrar:LYNCPOOL-FQDN -Route @{Remove=$apmatchuri}

e) Verify output to make sure the route is removed

Get-CsStaticRoutingConfiguration -Identity Service:Registrar:LYNCPOOL-FQDN | Select-Object –ExpandProperty

f) Add new static route with new DMA name , use below cmdlet

$routePool = New-CsStaticRoute -TLSRoute -destination “dma-FQDN” -port 5061 -matchuri “vcservice” -usedefaultcertificate $true

Set-CsStaticRoutingConfiguration -identity service:Registrar:LyncPool-FQDN -route @{Add=$routePool}

g) Verify that new route is added and shoing in below cmdlet.

Get-CsStaticRoutingConfiguration -Identity Service:Registrar:LYNCPOOL-FQDN | Select-Object –ExpandProperty

New Skype for Business 2016 look and feel coming your way…

November 7, 2016 Leave a comment

New Skype for Business 2016 look and feel coming your way…

Application sharing failed with external Partner (Non-Federated)

Working with one of the vendor who is not federated with us and doing application  sharing and come-up with an strange issue which is telling many story.

First-of-All, I would like to beat Microsoft for the wrong documentation they have furnished for ports requirement into Edge Server for Media traffic.

The client will ALWAYS try to connect over the 50k (50000-59999) port range. If it fails to do this, than it will fail back to the 443/3478 ports. This is not mentioned by Microsoft at all in TechNet Documentation below.

Note: Desktop/App sharing & file transfer always use TCP port (same AV ports) not UDP.

Port summary – Scaled consolidated edge, DNS load balancing with public IP addresses in Lync Server 2013


So, Let jump into the problem been faced and how it was working with a workaround (Guess ??).


Corp User is doing application sharing with remote user (Non federated but use lync) from corporate network and its failed with as usual error “We Could not connect the presentation due to network issue



I did not do many traces as I am more relying lync CDR database which tells you exact issue and help to start with a basic troubleshooting. I looked into user CDR logs and see that “ICEWarn=”0x120“;”


Has generated is BYE message from client logs which itself is sufficient to explain that remote firewall is not allowing outbound TCP connections in 50000-59999 port range and hence application sharing was failing.


This is the GOTCHA which is not clearly explained by MS documentations.


Now we understand that high port range is not allowed by remote network firewall and causing this issue, So I thought to force remote user to open this conf in WEB/443 and test it.

I edited the meeting conference by adding “?sl=1” in conference URL and tried testing.

Yes, Its worked now J.

I have asked remote customer to work with his network team and make sure that 50k outbound ports is opened to work.

Identify Lync/Skype Caller and Callee location

I have got several calls recently with my other UC expert friend eager to know “How Can identify Lync caller location“. There are several option to trace it including wire shark, Fiddler and Netmon live traces. But instead of siting to do live trace you can do it offline with the help of lync CDR monitoring console.

Of course you must have it, no choice 🙂 !!

Its pretty simple, login to your Lync monitoring console and search with Caller “User URI prefix”. Click on the audio call which you want and jump directly into “Media Line (Main Audio)” section.

I have two example as below

a)Caller is in outside/internet and callee is in corporate network


b)Caller and callee both is in corporate network


Hope it will help you 🙂

Categories: Lync 2013, Skype For Business Tags:

Lync dropping calls after 1-2 seconds!

Problem Description:-

Dealing with a single user problem which is complaining that when someone call him to Lync, the call popup appear for 1-2 second and disappear.


Disabling Enterprise voice feature solved the problem but left user to do not make call outside which was another problem/Limitation.


We started looking the UCCP and CDR logs from monitoring server for user SIP URI and understand that call is getting transfer to UM and failing as we do not have UM integration.



I also tested “Test-CSPSTN” call to user SIP and see the different error message which was pulling us to check routing problem. Most of the call were test by lync-lync  call which does not use gateway so Below error was surprises.



We started to think the use CSData corruption which may causing the problem. I follow below steps

## Backup specific user data
a) Export-CsUserData -PoolFqdn “POOL-FQDN” -UserFilter “” -FileName “C:\temp\ ”
## this command will remove all Lync attributes from the AD accounts, it’s identical to the “Remove from lync server” in control panel.
b) Remove-CsUser –Identity
c) Re-create user in Lync, manually assign polices, enterprise voice extension etc..
## this command will restore Lync user data (contact list, logs etc..) it will append the user data instead of overrating data like in the “Import-CsUserData” cmdlet.
d) Update-CsUserData -Filename “C:\temp\” -UserFilter

Problem Solved ?? , UHH, Guess ??.  NO NO L, We have still same issue !!!!!

Again tried to above steps but did not use “Update-CsUserData” as I thought there could be some stale/bad entry in the contacts, Conference, LIS data which may be causing the issue.
Now, The problem is solved.

“We can’t get more message right now” Error in Lync 2013 chat room

July 28, 2015 2 comments

You are laughing to see the subject line I have used in this post “We can’t get more message right now”. Yes this is one of the error message been reported by one of my Lync 2013 persistent chat user.

He is active member of many chat room and use it very often. Other members of chat room can use the room without any issue. I did lots of research over web and also thought to open case with Microsoft but doing it before i tried something funny.

The error message got by user is below.


I added user as additional manager in the room as below.


User exit lync clients and tried to post message back the chat rooms, all’s started working fine. I am still not sure what is the root cause of this behavior and trying to get it from MS :).