You are on page 1of 8

Pexip® Infinity with Microsoft® Lync®.

Integrating with Lync Online, hosted as a service, and on-premise.


Standard Lync on-premise with Pexip Infinity

 Lync has trunk to Pexip


 Lync Edge + Pexip TURN / VCS TURN for traversal DMZ
 Same domain supported (VMR != username)
 Local video integrations supported – video infrastructure does
traversal for video calls

TURN services
SIP trunk

Lync-FEP Microsoft Lync client


Lync on Edge or
federated contacts
Pexip Infinity Lync-Edge
Media

Note: Virtual Meeting Rooms can have same domain as Lync clients
Enterprises using Office 365 and
on-prem video conferencing

 Office 365 will talk to Pexip as any other federated


Lync environment
Lync Office 365
 Media will be routed locally as both Lync and Pexip
supports SIP ICE negotiation
 Pexip needs separate domain/subdomain

Microsoft Lync client


outside company network

Internal DMZ WebRTC clients


Media

Microsoft Lync client Federated


Lync contacts

Video call control


Pexip Infinity

External video
conferencing endpoints

Video conferencing endpoint


Enterprises using with no Lync
- need interop with B2B Lync/WebRTC

 Remote Lync and Office 365 connect via federation


 Video endpoints connect via normal SIP/H.323 SRV
Lync Office 365
 Pexip deployed with single domain @company.com
 _sipfederationtls._tcp.company.com (5061) points to Pexip

Internal DMZ WebRTC clients

Federated
Lync contacts

Video call control

Pexip Infinity

External video
Video conferencing endpoint conferencing endpoints
Enterprises using with Lync only
- need interop with B2B video/WebRTC

 Remote Lync and Office 365 connects normally


 Pexip deployed with single domain @company.com
Lync Office 365
 Video SRV records points to Pexip
 _sips._tcp.company.com (5061)
 _h323ls._udp.company.com (1719)

Microsoft Lync client


outside company network

Internal DMZ WebRTC clients

Microsoft Lync client


Federated
Lync contacts

Pexip Infinity
Lync-FEP

External video
conferencing endpoints
Lync Office 365 Hybrid

 Office 365 will talk to Pexip as a federated Lync


 Pexip platform operating on subdomain
(i.e. conf.domain.com) Lync Office 365
 SRV-records points to Conf Node
_sipfederationtls._tcp.conf.domain.com
 Trunk from Lync Server

Media

DMZ
Microsoft Lync client
externally on internet

Microsoft Lync client Media


internally on LAN on
Internal Lync
Pexip Conf Node
Microsoft Lync client
located in DMZ
internally on LAN on Lync-Edge @ federated
reachable by
Office 365 company
Office 365

Media Lync federated


Virtual Meeting Rooms must have different contacts
domain from Lync clients
Lync-Edge
Lync-FEP
Public Service Provider Pexip deployment

 Everyone connects natively


 Video: H323/SIP with H239/BFCP presentation
 Lync: SIP with RDP presentation Lync Office 365
 WebRTC: HTML5/web sockets with VP8 media

 Video and Lync SRV records points to Pexip


 _sipfederationtls._tcp.company.com (5061/tcp) Service
 _sips._tcp.company.com (5061/tcp) Provider Microsoft Lync client
outside company network
DMZ
 _h323ls._udp.company.com (1719/udp)
WebRTC clients
 _h323cs._tcp.company.com (1720/tcp)

Federated
Lync contacts

Pexip Infinity
media node
cluster
External video
conferencing endpoints
pdavila@inet.ec

You might also like