Is anyone presently running the $subj scenario?
To be more specific - we are presently setup with a hosted Skype for Business provider (in a few of our outsourcer services data centers, distributed globally), which tie into our network utilizing our MPLS, in order to preserve the quality of service demand for voice and video conferencing.
We are contemplating deployment of SD-WAN, with SD-WAN devices being installed in each remote, replacing our routers. The challenge comes in the migration process, during which it seems that we may need to double up the MPLS connections in each Skype hosting data center, so that one is used "under" the SD-WAN overlay, for sites being migrated to SD-WAN, in need to use Skype, while the other MPLS leg is left for the still-to-be-migrated sites, for their Skype needs.
As this migration (few hundred sites, globally dispersed) is a long duration process, and it is hard to anticipate the pattern of traffic, we will probably end up supporting the MPLS dual connectivity for quite a while, unless we could somehow leverage Internet connectivity into some of the Skype hosting data centers ... ?!?
Extra challenge: MPLS is fully meshed. SD-WAN won't be (appliances in remotes won't support so many simultaneous tunnels), so a further regionalization of Skype access may be needed, but with some ability to still get multiple regions into the same conference calls, or having end points talk to each other across multiple regions (for which we think of having some hub-and-spoke with our data centers, from everywhere).
Anyone having run into this issue, and having some suggestions / recommended design patterns?
No comments:
Post a Comment