Design Clinic: Cisco UC Architecture for Corporate Branch Offices

1. Design Clinic:Cisco UC Architecture for Corporate Branch Offices Tim Wellborn – CCIE #15397 May 7, 2008

2. Point of this Session:Two solutions – Same destination

3. Agenda Customer Scenario “Standalone” Approach “Centralized” Approach Summary

4. Primary Focus • Voice (Call Control) • Voicemail

5. 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

6. 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

7. 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

8. Approach One

9. Approach One • Per site Voice and Voicemail • Cisco Unified Communications Manager Express • Cisco Unity Express

10. 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

11. PSTN FAX CUCME/CUE - Step One • 1861/2800/3800size to # phones • 1861 (8) to 3845 (250) BRANCH “A” • Local phones • PSTN trunks • Analog VIC • PRI VWIC • CUE licensed for # mailbox • AIM-CUE • NME-CUE

12. Voice/Data Network PSTN PSTN FAX FAX CUCME/CUE – Add branch BRANCH “B” BRANCH “A” CUCME/CUE CUCME/CUE • Configure dial-peers so can call each other • Separate Voicemail

13. Voice/Data Network V PSTN PSTN FAX FAX CUCME/CUE – Add HQ BRANCH “B” BRANCH “A” CUCME/CUE CUCME/CUE WAN router • More dial-peers • Still separate VM Voice Voice Gateway HEADQUARTERS

14. Small Network - simplified with a Gatekeeper Medium-Large Network - Multiple Gatekeepers and a Directory Gatekeeper Directory Gatekeeper - Network Scaling Small Network - Gateways only Medium Network - Multiple Gatekeepers Gateway Gatekeeper Directory Gatekeeper

15. 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 H.225 RAS (UDP) H.225 RAS (UDP) IP QoS Network H.225 (Q.931) Call Setup (TCP) CUCME A System B H.245 Call Control (TCP) RTP (UDP)

16. Voice Networking • Make dialplan manageable • Provide redundancy to dialplan component • Voicemail Networking • Network CUE systems • Network w/ central Avaya SOLUTION: Cisco Unified Messaging Gateway SOLUTION: Cisco Gatekeeper Fancy Stuff

17. Cisco Unified Messaging Gateway 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 Cisco Unified Messaging Gateway Solution Cisco Unity Cisco ISR with CUE UMG Unified Messaging Network Each UMG Scales up to 1,000 CUE’s Central CUE (Upto 10 sites) CME Messaging Challenges Today CUE with SRST or CME CUE with SRST or CME Cisco Unity Connection Cisco Unity CUE with SRST or CME CUE with SRST or CME CUE with SRST or CME CUE withSRST or CME

18. Voice/Data Network V PSTN PSTN FAX FAX CUCME/CUE “Final” Solution BRANCH “B” BRANCH “A” CUCME/CUE CUCME/CUE WAN router • Build Slow • Dial anyone • Share VM • Manage centrally Voice GK UMG Voice Gateway HEADQUARTERS

19. Voice/Data Network PSTN PSTN FAX FAX OPTION - CUCME with centralized voicemail BRANCH “B” BRANCH “A” CUCME CUCME WAN router Voice Unity or UConn CUCME HEADQUARTERS MWI Relay

20. Approach Two

21. Approach Two • Cisco’s Centralized Call-processing model • Cisco Unified Communications Manager • Cisco Unity (or Unity Connection)

22. 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.

23. Voice/Data Network PSTN FAX CUCM/Unity - Step One • CUCM • Unity • 1861/2800/3800size to # phones • 1861 (8) to 3845 (250) BRANCH “A” • Local phones • PSTN trunks • Analog VIC • PRI VWIC

24. Voice/Data Network V PSTN FAX CUCM/Unity – Add branch Move/Add/Change to add a site BRANCH “C” BRANCH “B” BRANCH “A” • Can drop in remote by adding phones • Add gateway as/when needed

25. Voice/Data Network V PSTN PSTN FAX FAX CUCM/Unity – Integrate HQ BRANCH “B” BRANCH “A” Voice Gateway Voice HEADQUARTERS

26. Voice/Data Network V PSTN PSTN FAX FAX CUCM/Unity – Build Out HQ Add phones at HQ BRANCH “B” BRANCH “A” Voice Gateway HEADQUARTERS

27. Voice/Data Network V PSTN PSTN FAX FAX CUCM/Unity – “Final” Solution BRANCH “B” BRANCH “A” Voice Gateway HEADQUARTERS

28. What about use existing VM only? • Not really possible with CUCME • No SMDI – low chance QSIG (no release transfer) • For CUCM have following options • Dual connect 3rd-party VM • Box not likely to be set up for dual integration • Use QSIG link from CUCM to PBX

29. 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

30. Q and A