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
application delivery
devops
iApps
LTM
lync
  • mikeshimkus_111's avatar
    mikeshimkus_111
    Historic F5 Account
    Mar 17, 2017

    Hi Christian, I think this should work. Are the two external clients able to set up peer-to-peer communication using STUN (i.e., they aren't using TURN, which would proxy all A/V traffic through the Edge servers).

     

  • ChristianH_1903's avatar
    ChristianH_1903
    Icon for Nimbostratus rankNimbostratus
    Mar 17, 2017

    Should this iApp allow to do video calls to external parties while using 4G? We currently can do video calls between 2 internal users while one or both of them are on 4G but not with externals. Video calls between 1 internal user on premise and 1 external party work fine.

     

  • JG's avatar
    JG
    Icon for Cumulonimbus rankCumulonimbus
    Jan 12, 2017

    On rc8:

     

    1.

     

    Would like the option of selecting which port to use in the reverse proxy scenario. The default is 8081.

     

    2.

     

    The monitors use double backslashes for escaping.

     

  • Giovanni_Ceci_1's avatar
    Giovanni_Ceci_1
    Icon for Nimbostratus rankNimbostratus
    Dec 27, 2016

    Can we please get an update to the template to include names for the Nodes instead of just using IPs? It's just a good way to add the hostnames for the actual servers. Also, Descriptions would be a nice add too.

     

  • JamesSevedge_23's avatar
    JamesSevedge_23
    Historic F5 Account
    Nov 08, 2016

    Correct, to fix the port sharing issue the solution(in this scenario of split LTM's and shared IP) will use 8081 in between the LTM's to carry that traffic, but front end and back end ports will stay as expected. Thanks for pointing out the double underscore.

     

  • LH_55870's avatar
    LH_55870
    Icon for Nimbostratus rankNimbostratus
    Nov 08, 2016

    Hello James, finally I have used the latest template, so I can confirm, there is no more a ilegal sharing error. But I have noticed that the name of the Virtual server is ending with _reverse_proxy_front_end_8081. Is this the solution or a typo? Also there is a double underscore in both the pool names.

     

    thanks

     

    LH

     

  • JamesSevedge_23's avatar
    JamesSevedge_23
    Historic F5 Account
    Oct 08, 2016

    Hello Amolari, This is not in our roadmap as of now... thanks for bringing this edge case to our attention though and we will log it for possible inclusion in future versions of the iApp as suggested.

     

    Thanks,

     

  • amolari's avatar
    amolari
    Icon for Cirrostratus rankCirrostratus
    Oct 08, 2016

    Hello James would it be possible to make the SIP monitor optional in future version? Some customers do use the iApp exclusively for Reverse Proxy and do not run sip services on their pool, which makes them remove the strict update and remove that monitor.

     

    Thanks

     

    Alex

     

  • JamesSevedge_23's avatar
    JamesSevedge_23
    Historic F5 Account
    Oct 06, 2016

    Hello LH, If you take a look at the following link that shows the HLB ports for front end services it has 8080 on there for client/device retrieval of root certs. https://technet.microsoft.com/en-us/library/gg398833.aspx

     

    So that is why the port exists, however the sharing issue you ran into is also fixed, please download the template and retry with shared IP's.

     

    Thanks,

     

  • LH_55870's avatar
    LH_55870
    Icon for Nimbostratus rankNimbostratus
    Oct 03, 2016

    Hi James, I think I understood the issue and that another IP would solve that. What I don't understand is why there is 8080 being created as part of the reverseproxy-less frontend iApp. IMHO the 8080 is supposed to be used just in the reverse proxy scenario.

     

    regards

     

    LH