Microsoft Skype for Business Server 2015
Problem this snippet solves:
New release candidate iApp template and deployment guide for Microsoft Skype for Business Server 2015 (formerly Lync Server 2010/2013). For more information and complete guidance on configuring the iApp template, see the associated deployment guide: http://www.f5.com/pdf/deployment-guides/microsoft-skype-for-business-dg.pdf
f5.microsoft_skype_server_2015.v1.0.0rc9: posted to downloads.f5.com in 11/2017
RC-9 was posted to downloads.f5.com (as will most new versions of this template). It contained the following changes: new BIG-IP AFM IP Intelligence threat categories to support BIG-IP v13.1 and support for route domain 0 from non-Common partitions.
f5.microsoft_skype_server_2015.v1.0.0rc7: posted 09/21/2016
RC-7 provides additional SIP domain support within reverse proxy, a monitor schema change for reverse proxy to make use of the 200 OK response when querying lyncdiscover/lyncdiscoverinternal, support for the director service standalone use case(separate LTM from Front End service), added support to ask for the IP phone update url to allow connections through reverse proxy and added a port 80 Virtual Server in addition to the existing 443 Virtual Server for reverse proxy.
RC 5 and 6 were never released to the public, this includes changes as a part of those RC's
f5.microsoft_skype_server_2015.v1.0.0rc4: posted 02/16/2016
RC-4 Fixes a security log profile error when deploying on versions of BIG-IP earlier than 11.4, where AFM is not available.
f5.microsoft_skype_server_2015.v1.0.0rc3: posted 01/22/2016
RC-3 attaches a supplemental ICMP monitor to the Edge internal UDP virtual server. See https://support.f5.com/kb/en-us/solutions/public/6000/100/sol6143.html for more information.
f5.microsoft_skype_server_2015.v1.0.0rc2: posted 01/11/2016
RC-2 contains only a small correction to the iRule produced by the iApp template. The iApp will now always force the FQDN written to lowercase in the iRule, even if the user enters CAPITAL letters.
f5.microsoft_skype_server_2015.v1.0.0rc1: posted 07/06/2015
New iApp template for Skype for Business.
Code :
70782
Published Jul 06, 2015
Version 1.0
Hello Renato, Mobile clients should not be connecting to the AV virtual server to login successfully but instead to the reverse proxy virtual server on port 443 which (in single BIG-IP scenario) will in turn load balance traffic to port 4443 on the Lync FE's. To get mobile clients working through F5 using the iApp the reverse proxy section is key to getting this working ("thick" clients do not necessarily need reverse proxy to login and, depending on configuration/client/location, may not even be going through your BIG-IP currently).
Here is a useful technet article that goes through how lync mobility works: https://technet.microsoft.com/en-us/library/hh690030(v=ocs.15).aspx.
Let me know if i can help further once you attempt via reverse proxy Virtual Server.
robgeach_351055Nimbostratus
am I blind? where is the rc9 download link?
on further review, you have to go to and use your support account to download the 2+MB iapps template, then extract the skype4b template from the zip file. ez pz but inconsistent with the rest of this page.
Renato_AbreuAltostratus
Hello James.
Thank you very much for the reply and the technet link.
I have changed some configurations on skype topology like the FE's FQDN and the certificate that I was using on the reverse proxy virtual server.
After changing this configuration, the mobile client still can't login, but now I see at the tcpdump that it's reaching the reverse proxy virtual server. That "Can't connect to server" error is not appearing on the mobile client any more, but it keeps trying to connect forever without showing any error.
Looking at the tcpdump filtering on my mobile IP address, I can see some intial communication with the FE server, but after some seconds the virtual server starts to send Resets to the client.
I will analyse this pcap files and try to understand why is this happening.
If you have any clue about it please let me know.
Thank you again.
Hello Renato, Glad to hear you got further along. Understanding mobile client flow, setting it up and then troubleshooting it can be tough so good luck!
My only advice at this point is to continue to do some research on how to properly set up mobility on the Lync side as well as take a look at the reverse proxy section of our deployment guide for additional tips: https://www.f5.com/pdf/deployment-guides/microsoft-lync-iapp-dg.pdf
Only other thing to mention is if you are still stuck and are fairly confident the F5 configuration is the problem you could open an F5 support case to get official assistance.
