Simplified port requirements for Skype for Business Online

Microsoft has announced that the 50,000-59,999 port range (UDP and TCP) no longer is a requirement for Skype for Business endpoints to communicate with Skype for Business Online.

Earlier this year Microsoft talked about making simplification for network connectivity for Skype for Business Online (see blog article) and they recently updated the guidance and removed the mentioned port range as a requirement: Office 365 URLs and IP address ranges

So which ports are required for clients?All clients need to be able to directly connect to Skype for Business Online on the following destination ports: (the IP addresses and FQDNs can be found in the Office 365 URLs and IP address ranges)

  • TCP 443
  • UDP 3478, 3479, 3480, 3481
  • Optional: UDP/TCP 50,000-59,999

Is there a minimum client version required to benefit from the port changes?

This change applies to all clients supported against Skype for Business Online. No clients are excluded and there are no specific minimum version required (although it is always recommended to run the latest and greatest version).

For more information read the blog post from Microsoft

Skype for Business Setting Up Rights Monitoring Server

In order to give some people read only rights to the monitoring reports we’ll need to setup some settings in SQL Reporting.

Go with Internet Explorer to your monitoring server webpage: http://sql01/Reports/  (Replace sql01 with your host).

SQL Report Settings

Click Manage to access the settings page for the LyncServerReports database.

On the left side you will find Security, Click on it.

SQL Report Settings Security

Now click on the Add group or User.

You have to options to enter:

  • Use Security Group (via Active Directory)
  • Use a specific User

In my case i’ve made a new group in Active Directory (i don’t want to give the user also right in Skype for Business Control Panel).

Make sure you’ll add the user who needs to view reports to the group 😉

Active Directory Security Group

Let’s add the Group name in SQL Reporting.

SQL Reports Security Rights

Copy the AD Group name in the field. Select Monitoring Reports Browser as role. With this role it’s only possible to view. Click OK.

Now login as the user and try to reach the monitoring URL: http://sql01/ReportServer/Pages/ReportViewer.aspx?%2fLyncServerReports%2fReports+Home+Page

sfb monitoring reports


Configure call forwarding on unassigned number ranges in Skype for Business

Skype for Business

One of the great (for some people unknown) features introduced in Lync Server 2010 is the ability to assign a block of numbers to Lync and have Lync handle a call made to an unassigned number a specific way rather than just have a (fast) busy signal or the 404 error in SIP. This great feature is still availlable in Lync Server 2013 and Skype for Business Server 2015.

Let’s build a text-to-speech message and forward the call to the reception for example:

Open the Skype for Business Management Shell and choose on of the following:

  • Route to a Response Group or User
     New-CsAnnouncement -Identity -Name “Forward Announcement” -TextToSpeechPrompt “Thank you for calling Contoso, please wait while we redirect your call.” -Language “en-US” -TargetUri
  • Route to a specific (SIP) phone number
     New-CsAnnouncement -Identity -Name “Forward Announcement” -TextToSpeechPrompt “Thank you for calling Contoso, please wait while we redirect your call.” -Language “en-US” -TargetUri “;user=phone”

Execute the following powershell command to create the unassigned number range and assign our announcement/forward to the unassigned number range. This is also possible via the Skype for Business Control Panel.

New-CsUnassignedNumber -Identity “Unassigned Number Range” -NumberRangeStart “+31884461000” -NumberRangeEnd “+31884461999” -AnnouncementName “Forward Announcement” -AnnouncementService

Skype for Business Management Shell

Now everything is set up, call one of the unassigned numbers and check if everything works like you build. It will take some minutes before it will be active.


SIP Error 485 Ambiguous

A customer was facing the problem that it was not possible to reach a certain contact person on his E164 number.

The first thing to check was in this case the Audiocodes Syslog Viewer. What is happening with the call? Does the call reach the Mediant or Skype for Business Server?

So i called the number from my own Skype for business Client. I received the following error.

Let’s check the Syslog Viewer:

The first thing i saw was the 485 Ambiguous SIP response from the Skype for Business Mediation role.

Error 485 means there are more destinations with the same LineUri, this can be in Users but also with Response Groups

Fire up Powershell with the script from Andrew Morpeth (Lync Get All Assigned Numbers), This script will export all objects with a LineUri to CSV. Make sure you edit the location in the script, by default it will write in C:/ Root.

Go to the location and open the CSV file with Excel or any other editor. Search for the number and you’ll see what is causing the problem. 2 Users where assigned with the same number.

Remove the number from one of the users and your problem is fixed.