Microsoft Skype for Business Server 2015

Hi, I am just trying to configure the S4B VIPs using the v1.0.0rc6 version of template and have discovered that the "Microsoft Skype Server Director Virtual Servers" section is part of the "Microsoft Skype Server Front End Virtual Servers" section which prevents me to do a separate configuration for the director pool which I would like to run in different trafic group thus being active on other LTM node. In Lync template there it was possible to separate the config, so my question is simple. Is this on purpose or it's a bug and it might be fixed?

thanks

LH

Had overseen that one. Is all good. Thanks

To confirm, you answered "Yes" to "Do you want to include Skype Mobility services for external clients?", and typed the FQDN into the "What is the FQDN for external Skype Mobility access?" field, and still not in the iRule?

yes, it's deployed as reverse proxy only (fwd traffic to skype servers). I've updated the tmpl to rc6 and the Irule is still the same:

when HTTP_REQUEST {
     switch -glob [string tolower [HTTP::host]] {
          sfbpoolemeaext.xyz.com* { pool create_reverse_proxy_front_end_4443_pool }
            { pool create_reverse_proxy_front_end_4443_pool }
          meet-emea.xyz.com*   { pool create_reverse_proxy_front_end_4443_pool  }
          dialin-emea.xyz.com* { pool create_reverse_proxy_front_end_4443_pool  }
            { pool create_reverse_proxy_front_end_4443_pool }
     }
}

By "pure reverse-proxy", which scenario are you using for"Are you deploying this BIG-IP system for Skype web services (reverse proxy)?" The lyncdiscover hostname is present for me in the RC6 template that's on when I choose to either forward RP traffic to Lync/Skype servers or forward it to another BIG-IP.

For Office Web Apps, we can update the guides with manual steps for colocating on the application virtual server, similar to what's in the SharePoint guide today. However, we believe that most organizations will use a dedicated WAC environment to be shared between SharePoint, Lync/Skype, and Exchange, that uses a unique IP. Also, creating separate configurations for WAC in each iApp is problematic, since the configurations in each template will drift.

I'll create an RFE for the multiple SIP domain work, but we don't have an ETA on it at the moment.

With RC4 I see that in pure Reverse-Proxy deployment

• lyncdiscover is missing in the irule

What about the suggestion from marvn to include the WAC (office web apps) in the Skype iApp as an option? His remark about the VS IP / Certificate makes sense.

More important, what about the support of multi SIP domains?

Thx

Alex