Skype for Business 2016 Network routing RRS feed

  • Frage

  • Hi all,

    I hope someone can finally clear things up for me because I can't finde any useful help in the internet. I want to know how we can set certain routing rules for Skype for business Clients.

    Let me start of first with our Network environment. We use the Office 365 Enterprise E3, where the SfB is also included. We don't have a SfB Server, we use the online hosted. Now we have 5 office sites around the world which are almost all connected with MPLS (VPN), 2 sites only have internet connection. 

    What we try to achieve is that when colleagues in our offices site try to communicate with each other (Call/IM/Screensharing), that the SfB Clients 1st try directly to connect over the internal network or via MPLS to other sites and if not possible, then go via default Gateway over the internet.

    Trough certain changes in our network, we got it to work almost the way we need it. SfB Clients seem to work this way described above per default. We set default gateways pointing to the internet, so if an internal connection is not possible, it goes this way.

    Now we are standing in front of 2 problems. 1st we are not able to route the SfB clients over certain internet connections (we have more than one at certain sites because of failover and bandwith). The 2nd Problem we have, we notice that when colleagues connect to a SfB Meeting via Webscheduler, even if the colleagues are at the same site, all SfB Clients connect over the internet and ignore the direct way via internal network.

    I've found a SfB Support Manual that listed over 100 IPs (!!) for SfB Online Servers to be added to as a routing rule, if we want to accomplish what we need. Is this really the only way?
    Here the link:

    Has anyone the same issue and can clear me up on how we can solve this? I would appreciate that very much!
    Thanks in advance.

    Best Regards

    Freitag, 25. November 2016 09:15

Alle Antworten

  • Hi Michael,

    first of all let's differentiate a bit between P2P and Multipary/conference sessions. P2P sessions try to flow directly if possible. Multiparty not, the go to the SFB frontend server or in your case to O365 SFB Online because the Conference MCU (AVMCU, ASMCU, ...) is hosted in the cloud... So mulitparty sessions (> 2 participants) will go to O365. For details you can search for the SFB Workload poster and the Lync Server 2013 networking guide.

    Topic 1: Route SFB client traffic over (one of many) internet breakouts of a (branch) site
    Uh ...
    Bascially clients will use the def gw, sec. gw or proxy to get out to the cloud. If you really want to differentiate which one is primarily used and which internet connection as a backup you need to configure routing rules for the clients accordingly.

    Topic 2: SFB Meetings with SFB clients on the same site
    See above. This is mulitparty (in this case even with one participant joining). Why? Because if you schedule an SFB online meeting it is intended or assumed to be a mulityparty session with more than two participants. So this can only be avoided if it stays a ad hoc P2P SFB session.

    I hope it helps.


    Samstag, 14. Januar 2017 19:53