march 29th, 2012 - meetup deck 3-29.pdf–how enterprise session management can help • content ......
TRANSCRIPT
New England User Group
New England Lync User Group
March 29th, 2012
#NELUG
SPONSORS:
WELCOME!
Sponsored by:
New England User Group
Agenda
• Welcome & Pizza
• Goals & Objectives of Lync User Group
• Thanks to our sponsors
• Lync Enterprise Voice Deployments – Sentri
• Next Meeting – Topics/Timing/Location
• Evaluation & Winner Selected
2
New England User Group
Goals of Lync User Group
- Lync users coming together to identify solutions
- Lync users maximizing investment in the technology
- Case Studies/Best Practices/Ideas
- Create a virtual support group
- Consolidate product feedback to communicate to Microsoft
3
New England User Group
Today’s Sponsors
Event Location
Food/Drinks
Headset Giveaway
Presenter
Thanks as well to our regular sponsors:
4
New England User Group
Introduction & Content
• This material is designed solution architects that want to
understand:
– The challenges of deploying Lync Enterprise Voice in multi-
vendor PBX environments
– How enterprise session management can help
• Content
– Drivers for session management with Lync
– Deployment challenges
– Session management solutions
5
New England User Group
Session Management Drivers
• Popular trends in enterprise IP
telephony & Lync usage:
– Use of SIP trunking for PSTN
interconnect (vs. TDM trunking)
– Use of Lync for enterprise voice
(vs. legacy IP PBXs)
– Use of on-net (all IP) calling in
multi-vendor environments
TDM SIP
Cisco
Avaya
Other IP-PBXs
Session
Management
6
New England User Group
Session Management Drivers (cont.)
• Most large enterprises are trying to deal with:
– Consolidation of PSTN trunks
– Distributed infrastructure
– No global dial plan or directory
– Limited on-net routing
– Limited interoperability
– Large infrastructure footprint
• Session management can help!
7
New England User Group
When to Use Session Management
• Customer wants to gradually migrate from a complex legacy multi-vendor IP PBX architecture to Lync
• Need to integrate complex legacy systems
– Multi-vendor SIP/H.323 PBX environment
– Legacy video & FMC environment
– Advanced SIP header manipulation
• i.e. caller ID, called number changes
– Legacy contact center integration
– Demarc is needed for various network segments
• Simplify dial plan
– E.164 dial plan in Lync / Non E.164 dial plan in SM
– Mix of 4/5/6 digit dialing (PBX islands)
8
New England User Group
Session Management Benefits
• Benefits to customer
– Optimal Lync deployment (no compromises)
• Supports media bypass, TLS/SRTP, SIP REFER, early media, AD
integration, SIP trunking support, etc.
• Maximizes on-net routing
– UC-vendor neutral solution
– Reduced Deployment Risk
– Transition on your own time one phone/user at a time
9
New England User Group
Session management with Lync
• Why use session management with Lync?
– Easily integrate Lync with legacy PBX elements
– Simplifies dial plan management & routing
10
New England User Group
Lync Enterprise Voice Deployment
Barrier Example
• Legacy vendors try to fight Lync deployments with their own
session management strategy or agendas
11
PSTN
“Before” view
• Legacy telephony vendor (i.e. Avaya or
Cisco) is the only voice solution
• Lync not used for ITSP/PSTN access or
interconnect to legacy phone system
• Gateway (GW) or E-SBC may be used for
PSTN trunking (depending on customer)
Legacy Telephony Vendor
Lync Environment
PSTN
Legacy Telephony Vendor
Lync Environment
“After” view (legacy telephony vendor preference)
• Enterprise wants Lync enterprise voice to coexist with
(or ultimately replace) legacy telephony vendor voice
• Legacy telephony vendor insists on routing all Lync
calls through their IP-PBX or SM (session manager)
elements
Interconnect between Lync & legacy
telephony vendor done using Direct
SIP or GWs (connection to SM
element or to IP-PBX depends on
size of company)
SM: Session
Manager element
(i.e. Avaya Session
Manager or Cisco
UCM SME)
or
New England User Group
Why Keeping Legacy Vendors in
Lync Call Paths is a Bad Thing
• Keeping legacy voice vendors in call path can:
– Introduce additional voice management costs
– Impedes full migration to Lync enterprise voice
– Complicate call troubleshooting
– Limit future Lync calling features due to incompatibilities with IP
PBX
• Legacy PBX vendors are fighting to keep their voice role
– But why should Lync deployments be limited by this?
– Shouldn’t enterprises be able to choose the call routing?
• Is there a better and UC vendor-neutral solution?
12
New England User Group
How SBCs and Gateways can Help
• E-SBCs are frequently used for SIP trunking
• Session Managers (SM) are now popular in enterprises
• Net-Net ESD integrates E-SBC and SM functions
13
PSTN
Legacy Telephony Vendor
Lync Environment
SIP trunking to
PSTN via E-SBC
E-SBC functions (examples – may not be needed for all customers)
• Interop between Lync, IP-PBX, and PSTN elements
• Security between enterprise & PSTN
• Transport protocol (UDP/TCP/TLS) interworking
• Media bypass with Lync
• Media encryption (SRTP/RTP) interworking
• Media transcoding (G.711 to other)
• Load balancing to multiple Lync or IP-PBX elements (as well as
multiple ITSPs where applicable)
SM functions (examples – may not be needed for all customers)
• Session routing for all calls from PSTN to enterprise users
• Dial plan mgmt. for all Lync and IP-PBX elements in enterprise
• Dynamic session routing (i.e. sim ring)
• H.323 / SIP interworking
• Policy enforcement via Active Directory integration
• CDR collection
Use E-SBC to route
calls, not legacy
telephony vendor IP-
PBX or SM element
E-SBC &
Session Manager
New England User Group
Migrating from TDM to SIP Trunking
• Session management helps move to SIP trunking
– With TDM trunking, calls to Lync get routed to IP-PBX first
– With SIP trunking + E-SBC & SM, calls get directly routed
14
Legacy Telephony Vendor
Lync Environment
PSTN
Enterprise Premises
SIP
SIP TDM
PSTN – Lync
call routing via
IP-PBX & GW
TDM Trunking
Legacy Telephony Vendor
Lync Environment
PSTN
Enterprise Premises
SIP
SIP
SIP
PSTN – Lync
call routing
via
E-SBC & SM
SIP Trunking
E-SBC &
Session
Manager
New England User Group
Simplicity via Session Management
• Session management & E-SBCs can simplify multi-vendor
network deployments
15
No session management =
Multi-vendor complexity
Mobile
Networks
Audio
Conferencing
Legacy
IP PBX
(SIP & H.323)
Legacy
Video &
FMC
Contact
Center
Systems
PSTN via
SIP trunking
Mobile
Networks
Audio
Conferencing
With session management =
Simplified multi-vendor operations
Legacy
IP PBX
(SIP & H.323)
Legacy
Video &
FMC
Contact
Center
Systems
PSTN via
SIP trunking
Session Management Layer (SM + Lync)
Session Border Control / Security Layer (SBC + Lync)
New England User Group
UC Endpoints Enterprise Voice Unified Comm & Messaging Contextual Collaboration & Conferencing
Dial-tone
Basic Features
Adv Features
On-net Calling
Click-2-Call
Call-by-Name
Vanity Numbers
Directory Search
Trunks / Tie Lines
GW services
Mobility & Wireless
Presence
IM / Chat
Calendaring
Voice Mail
Active Synch
Mobile Clients
Speech Access
Anywhere Comm & Collab
.NET & CTI Apps
Handsets
Softphones
Group Chat
Web Clients
Smart Phones
Tablets/Slates
IP Turrets
IP Hoot
Two-way Radios
Desktop Video
Boardroom Video
Application & Desktop Sharing
Microsoft Office Suite
Microsoft Office SharePoint
Audio Conferencing
Video Conferencing
Web Collaboration
Call Management Delegation
Team Features
3rd Party integration
IVR
Contact Centers
CRM
Dashboards
Integrated Session Management &
Border Control Architecture for Lync
• Session management & E-SBCs helps enable UC service &
feature breadth for Lync & other enterprise elements
PSTN via
SIP Trunking
Mobile
Networks Audio
Conferencing
16
Session Management Layer (SM + Lync)
Session Border Control / Security Layer (SBC + Lync)
New England User Group
Two Session Management Models
• Integrated model: Use session management on E-SBC
– All SBC & session management features performed on E-SBC
– Security, interop, routing on a single network element
• Standalone model: Use standalone session manager
– E-SBC for security, interop, and control functions
– Standalone session manager for dial plan management
E-SBC &
Session
Manager
PSTN
DMZ
PSTN
DMZ
Standalone SM Models Integrated SM Model
Product choices:
Net-Net ESD 3820
Net-Net ESD 4500
Net-Net ESD SE
or
SM element product choice depends on customer requirements
E-SBC Model #2
E-SBC
Session
Manager
New England User Group
Why Both Session Management
Models are Needed?
• Customer requirements are not all equal
• Some customers want a E-SBC integrated model
– Leverage E-SBC investment for dial plan management and
interop functions
– May not need some of the advanced capabilities available on
standalone models
• Other customers will likely want a standalone model
– Volume of PBXs & complexities of multi-vendor UC
environment drives the need for a separate element
18
New England User Group
Session Management
Deployment Models
• Multiple deployment models exist:
1. SM integrated into E-SBC with On-Premises Lync
2. Standalone SM with On-Premises Lync
3. SM integrated into E-SBC with Office 365-D Lync
4. Standalone SM with Office 365-D Lync
• More details in subsequent slides…
19
New England User Group
Use Case #1:
SM in E-SBC with On-Prem Lync
• SM integrated into E-SBC model
– Net-Net ESD performs security, interop, and SM routing functions
– SM routing functions = PSTN calls to/from legacy systems & Lync
• For calls to PSTN, IP-PBX & Lync dial plans send calls to E-SBC
• For calls from PSTN, E-SBC sends calls to legacy IP-PBX or Lync based on called party info
• E-SBC can also route calls between IP-PBX & Lync
– Lync Media Bypass supports allows for media path efficiencies
Legacy Telephony
PSTN
DMZ
Enterprise
Premises
Site A
Enterprise
Premises
Site B
Other enterprise UC apps
requiring E-SBC support
(i.e. legacy video
conferencing)
E-SBC &
Session
Manager
20
New England User Group
When Use Case #1 Would Apply
• Use Case #1 applies when:
– Customer is using on-premises (vs. O365-D) Lync
– Customer is using (or planning to use) an E-SBC for SIP
trunking
– Customer is OK with performing session routing, security,
and any necessary interop fixups in the same E-SBC element
– Customer is OK with routing internal sessions (i.e. between
Lync and legacy IP-PBX) via the E-SBC element that is
typically in the DMZ
• If the above conditions are not met, then a standalone SM
model would be more appropriate (Use Case #2)
21
New England User Group
Use Case #2:
Standalone SM with On-Prem Lync
• Standalone SM model
– SM functions separated from E-SBC element
– E-SBC element performs security and interop functions
– SM element performs routing & advanced dial plan management • For calls to PSTN, legacy IP-PBX &
Lync dial plans send calls to SM (which routes to E-SBC)
• For calls from PSTN, SM receives calls from E-SBC and sends calls to legacy IP-PBX or Lync based on called party info
• SM can also route calls between IP-PBX & Lync
– Lync Media Bypass supported
Legacy Telephony
PSTN
DMZ
Enterprise
Premises
Site A
Enterprise
Premises
Site B
Other enterprise UC
apps requiring E-SBC
support (i.e. legacy
video conferencing)
E-SBC Session
Manager
22
New England User Group
When Use Case #2 Would Apply
• Use Case #2 applies when:
– Customer is using on-premises (vs. O365-D) Lync
– Customer is using (or planning to use) an E-SBC for SIP
trunking
– Customer wants to perform session routing and any
necessary interop fixups in a SM element separate from the
E-SBC
– Customer wants to route with internal sessions (i.e. between
Lync and legacy IP-PBX) via a standalone SM element (vs.
other methods)
23
New England User Group
Use Case #3:
SM with Office 365-DLync
• Office 365 (dedicated) model uses
Net-Net ESD with integrated SM and
E-SBC functions in a manner similar to
On-Premises Lync model
• E-SBC used for security & interop
and routing
• All calls between PSTN, legacy IP-
PBX and Lync are routed via E-SBC
element
• Lync Media Bypass supports
allows for media path efficiencies
24
Legacy Telephony
Office 365 Lync Clients
PSTN
DMZ
Enterprise Premises
Other enterprise UC apps
requiring E-SBC support
(i.e. legacy video
conferencing)
Media bypass/TLS/SRTP
E-SBC &
Session
Manager
New England User Group
Use Case #: Standalone SM with
Office 365 (dedicated) Lync
• Office 365 (dedicated) model uses a standalone SM in a manner similar to On-Premises Lync model
– ESD provides E-SBC functions used for security & interop
– SM used for routing
• All calls between PSTN, legacy IP-PBX and Lync are routed via E-SBC + SM element
• Lync Media Bypass supports allows for media path efficiencies
25
Legacy Telephony
Office 365 Lync Clients
PSTN
DMZ
Enterprise Premises
Other enterprise UC apps
requiring E-SBC support
(i.e. legacy video
conferencing)
Media bypass/TLS/SRTP
E-SBC
Session
Manager
New England User Group
Next Meeting
• Topic ideas
• Timing
– Monthly
– Bi-Monthly
– Quarterly
• Location
26
New England User Group
And the Winner is…
• Fill out your Evaluation Form and…
Win a
PLATRONICS PRO UC
27