Design Clinic: Cisco UC Architecture for Corporate Branch

Download Report

Transcript Design Clinic: Cisco UC Architecture for Corporate Branch

Design Clinic:
Cisco UC Architecture
for Corporate Branch
Offices
Tim Wellborn – CCIE #15397
May 7, 2008
© 2007 Cisco Systems, Inc. All rights reserved.
Cisco Public
1
Point of this Session:
Two solutions –
Same destination
© 2007 Cisco Systems, Inc. All rights reserved.
Cisco Public
2
Agenda
Customer Scenario
“Standalone” Approach
“Centralized” Approach
Summary
© 2007 Cisco Systems, Inc. All rights reserved.
Cisco Public
3
Primary Focus
 Voice (Call Control)
 Voicemail
© 2007 Cisco Systems, Inc. All rights reserved.
Cisco Public
4
Customer Scenario
 Branch Offices
“X” number of sites – might acquire 10 more
12 – 75 people each
Couple just 2 users
Fax or two, some analog trunks, larger sites have PRI
 Corporate IT/Telecom (help) manage branch systems
 Standardize (features, components)
 “4-digit” dialing
 Lower Costs / Reduce Long-Distance
 Migration –
Slow rollout
Interoperate w/ HQ PBX
© 2007 Cisco Systems, Inc. All rights reserved.
Cisco Public
5
Devil’s in the details
 High level requirements can mean more than one thing
 Nip “4-digit” dialing now – look to Universal Dial Plan
 How standard? Literally one-size fits all or just similar
technology?
 Willing to adjust WAN/other to support Voice goals?
 Interop – define please
© 2007 Cisco Systems, Inc. All rights reserved.
Cisco Public
6
More devilish details
 Call Control
Single PBX? Or networked independent?
 Voicemail
All on central? Or each site have own
Voicemail?
 If each have own – still be able to
transfer/forward to central? Between
branches?
 Network with legacy VM at HQ?
We’ll explore above
© 2007 Cisco Systems, Inc. All rights reserved.
Cisco Public
7
Approach One
© 2007 Cisco Systems, Inc. All rights reserved.
Cisco Public
8
Approach One
 Per site Voice and Voicemail
 Cisco Unified Communications Manager Express
 Cisco Unity Express
© 2007 Cisco Systems, Inc. All rights reserved.
Cisco Public
9
How CUCME/CUE fits criteria
 “Buy as you grow”
 Leverage H.323 for inter-site calling
 Can use variety of ISR sizes – still ‘standardized’
 CUE for per-site VM
 Remote management by central support team
 Use Voice Gateway to connect to HQ PBX
© 2007 Cisco Systems, Inc. All rights reserved.
Cisco Public
10
CUCME/CUE - Step One
• 1861/2800/3800 size to # phones
BRANCH “A”
1861 (8) to 3845 (250)
• Local phones
• PSTN trunks
Analog VIC
PRI VWIC
• CUE licensed for # mailbox
FAX
AIM-CUE
PSTN
NME-CUE
© 2007 Cisco Systems, Inc. All rights reserved.
Cisco Public
11
CUCME/CUE – Add branch
BRANCH “B”
BRANCH “A”
CUCME/CUE
CUCME/CUE
Voice/Data
Network
PSTN
PSTN
FAX
FAX
• Configure dial-peers so can call each other
• Separate Voicemail
© 2007 Cisco Systems, Inc. All rights reserved.
Cisco Public
12
CUCME/CUE – Add HQ
BRANCH “B”
BRANCH “A”
CUCME/CUE
CUCME/CUE
Voice/Data
Network
PSTN
PSTN
FAX
FAX
WAN
router
• More dial-peers
• Still separate VM
© 2007 Cisco Systems, Inc. All rights reserved.
Voice
V
Voice
Gateway
Cisco Public
HEADQUARTERS
13
Directory Gatekeeper - Network Scaling
Small Network - simplified with a Gatekeeper
Small Network - Gateways only
Medium Network - Multiple Gatekeepers
Gateway
© 2007 Cisco Systems, Inc. All rights reserved.
Gatekeeper
Cisco Public
Medium-Large Network - Multiple
Gatekeepers and a Directory Gatekeeper
Directory Gatekeeper
14
H.323 With RAS
Registration, Admission and Status
Gatekeeper
Address Translation: Every GW needs to know
only about the GK, not about all other GWs
IP QoS Network
CUCME A
H.225 (Q.931) Call Setup (TCP)
System B
H.245 Call Control (TCP)
RTP (UDP)
© 2007 Cisco Systems, Inc. All rights reserved.
Cisco Public
15
Fancy Stuff
Voice Networking
 Make dialplan manageable
 Provide redundancy to dialplan component
SOLUTION: Cisco Gatekeeper
Voicemail Networking
 Network CUE systems
 Network w/ central Avaya
SOLUTION: Cisco Unified Messaging Gateway
© 2007 Cisco Systems, Inc. All rights reserved.
Cisco Public
16
Cisco Unified Messaging Gateway
Messaging Challenges Today
Cisco Unity
Connection
CUE with
SRST or CME
Cisco Unified Messaging Gateway Solution
CUE with
SRST or
CME
Cisco
Unity
CUE with
SRST or
CME
CUE with
SRST or
CME
CUE with
SRST or CME
Cisco Unity
Cisco ISR
with CUE
CUE with
SRST or
CME
UMG
Each UMG
Scales up to
1,000 CUE’s
Unified
Messaging
Network
Central CUE
(Upto 10 sites)
CME
 Hub in a unified messaging network, centralizes message routing and
rules
 Supports all Cisco Unified Messaging solutions
 Enables scaling of a unified messaging network as required by branch
offices or enterprises
 Simplifies configuration and management tasks
 Helps customers migrate from legacy voicemail systems to Cisco Unified
Communications solutions
© 2007 Cisco Systems, Inc. All rights reserved.
Cisco Public
17
CUCME/CUE “Final” Solution
BRANCH “B”
BRANCH “A”
CUCME/CUE
CUCME/CUE
Voice/Data
Network
PSTN
PSTN
FAX
• Build Slow
FAX
WAN
router
• Dial anyone
• Share VM
Voice
V
UMG
• Manage centrally
© 2007 Cisco Systems, Inc. All rights reserved.
GK
Voice
Gateway
Cisco Public
HEADQUARTERS
18
OPTION - CUCME with centralized voicemail
BRANCH “B”
BRANCH “A”
CUCME
CUCME
Voice/Data
Network
PSTN
PSTN
FAX
FAX
WAN
router
Unity
or
UConn
Voice
CUCME
MWI Relay
© 2007 Cisco Systems, Inc. All rights reserved.
Cisco Public
HEADQUARTERS
19
Approach Two
© 2007 Cisco Systems, Inc. All rights reserved.
Cisco Public
20
Approach Two
 Cisco’s Centralized Call-processing model
 Cisco Unified Communications Manager
 Cisco Unity (or Unity Connection)
© 2007 Cisco Systems, Inc. All rights reserved.
Cisco Public
21
How CUCM / Unity (or UConn) fit Criteria
 Single PBX
 “single” point of mangement
 Any call any (unless configured not to)
 Simpler dialplan management (dialplan itself still pain)
 Single VM for everyone
 Easy to integrate voice to 3rd-party PBX, or number of
them
 More 3rd-party voicemail integrations.
© 2007 Cisco Systems, Inc. All rights reserved.
Cisco Public
22
CUCM/Unity - Step One
• CUCM
• Unity
BRANCH “A”
• 1861/2800/3800 size to # phones
1861 (8) to 3845 (250)
• Local phones
Voice/Data
Network
• PSTN trunks
Analog VIC
FAX
PSTN
PRI VWIC
© 2007 Cisco Systems, Inc. All rights reserved.
Cisco Public
23
CUCM/Unity – Add branch
Move/Add/Change to add a site
BRANCH “B”
BRANCH “C”
BRANCH “A”
V
Voice/Data
Network
PSTN
FAX
• Can drop in remote by
adding phones
• Add gateway as/when
needed
© 2007 Cisco Systems, Inc. All rights reserved.
Cisco Public
24
CUCM/Unity – Integrate HQ
BRANCH “B”
BRANCH “A”
Voice/Data
Network
PSTN
PSTN
FAX
Voice
Gateway
FAX
V
Voice
HEADQUARTERS
© 2007 Cisco Systems, Inc. All rights reserved.
Cisco Public
25
CUCM/Unity – Build Out HQ
Add phones at HQ
BRANCH “B”
BRANCH “A”
Voice/Data
Network
PSTN
PSTN
FAX
Voice
Gateway
FAX
V
HEADQUARTERS
© 2007 Cisco Systems, Inc. All rights reserved.
Cisco Public
26
CUCM/Unity – “Final” Solution
BRANCH “B”
BRANCH “A”
Voice/Data
Network
PSTN
PSTN
FAX
Voice
Gateway
FAX
V
HEADQUARTERS
© 2007 Cisco Systems, Inc. All rights reserved.
Cisco Public
27
What about use existing VM only?

Not really possible with CUCME
No SMDI – low chance QSIG (no release transfer)

For CUCM have following options
1) Dual connect 3rd-party VM
Box not likely to be set up for dual integration
2) Use QSIG link from CUCM to PBX
© 2007 Cisco Systems, Inc. All rights reserved.
Cisco Public
28
Criteria that immediately drive Centralized
 True UM
Requires Unity w/ customer’s Exchange
or Notes
Does not require centralized CUCM
 Company-wide Presence
Requires centralized CUCM w/ CUP
 “agents any location” Contact Center
Requires centralized CUCM and UCC
Express or Enterprise, possibly CVP
© 2007 Cisco Systems, Inc. All rights reserved.
Cisco Public
29
Q and A
© 2007 Cisco Systems, Inc. All rights reserved.
Cisco Public
30
© 2007 Cisco Systems, Inc. All rights reserved.
Cisco Public
31