Unified communications can be a priceless tool for enterprises with multiple offices and multinational or overseas clients. It means that businesses can/must spend far less on costly travel expenses and instead can catch up and update one another in an instant.
Microsoft Lync is one excellent example of the power that unified communications (UC) can have. This global UC solution empowers people to collaborate outside of their immediate team and helps to optimize traveling and roaming expenses. The solution includes instant messaging capabilities and gives users the ability to share audio, video and desktop files as they chat.
While this type of software is useful in many ways, it can also cause issues for enterprises given the numerous gateways, signaling, authentication, adaptive codes and more that enables Lync to work effectively. When Lync is implemented, a number of varying and dynamic flows of data impact on WAN bandwidth and compromise other business critical applications.
This might mean that when running Lync, an enterprise is faced with poor video conferencing and Salesforce services, which means IT managers have to make an awkward trade up between different, but equally necessary applications as they compete for sc
Configuring the Ipanema system to protect Lync traffic flows
Configuring Lync on the Ipanema multitenant central management platform (SALSA) comprises three key phases:
- First, codecs must be provisioned for audio, video, desktop sharing and common names. Recognizing audio and Lync Flows requires two Deep Packet Inspection tasks, one classifying UDP/TCP ports related to RTP/RTCP. The other recognizing corresponding Payload Types related to specific codes.
- Second, once Lync ports and ”¨codecs are included on ”¨the central management”¨ platform, we can create a”¨ QoS profile for audio and ”¨video flows to guarantee”¨“real time” quality of service. Basically, a QoS profile has”¨a unique name on the”¨SALSA management”¨platform which represents”¨every type of flow, e.g. Lync”¨Video and Lync Audio.
- After QoS profiles are configured, we can create the application groups. So, depending on the way to manage Lync, a network administrator might monitor and control separated application groups, for instance: “Lync Audio”, “Lync Video”, and “Lync Sharing”. Then by using the SALSA multitenant central management platform, we associate Audio Codecs to their specific QoS profiles, Lync Video to their specific QoS profiles and so on.
When the three provisioning phases are accomplished, Ipanema is able to recognize and protect Lync Flows. In scenarios with multiple WAN links, Ipanema can also select the best path by using DWS (Dynamic WAN Selection) solution, to increase service availability and deliver best possible application performance.
So, how can enterprises make the most of all the advantages that Lync brings, without interfering with other business critical apps? That's where Ipanema comes in and works its magic.
The Ipanema solutions solve this dilemma by accelerating the adoption of the complete Lync solution. This allows end users to enjoy an excellent experience, with the bandwidth flow for each individual video and file guaranteed. Users don't have to worry about frustrating, jittery voice calls and delayed instant messaging and can enjoy responsive and clear communications.
As well as this, by connecting branch offices to multiple network providers, such as MPLS and Internet, Ipanema also guarantees that the quality of Lync is steady even if ISP failures occur, truly safeguarding the application. In this way, Ipanema's intelligent system can select the best path to carry Lync traffic given any eventuality.
Lync promises to revolutionize how employees collaborate but CIOs and network managers shouldn't take a Lync rollout lightly. It can be one of the most disruptive applications flowing across a WAN. Without first investigating the potential impact on business critical applications any implementation runs significant risk. CEO's are asking their organisations to do more with less, in turn CIOs are looking to Lync. Our message is: please consider the network first, not second.
To know more: