Designing and Deploying Next Generation Voice

Transcription

1 Designing and Deploying Next Generation Voice Alec Mclocklin Consulting Systems Eng. IPT Session Number 1

2 Agenda High Availability CallManager and PBX Integration CallManager and Voic Clustering Over the IPWAN System Enhancements 2

3 HA Cost/Benefit Analysis Why Does High Availability Matter? Lost revenue due to downtime (contractual obligations) Competitive pressure competitor only a point and click away Customer service or expectations Shareholder satisfaction Loss of goodwill (public image) Lost productivity when network is down Overtime Consultants Regulatory requirements Additional margins of offering higher SLAs Reduced operating costs Break fix costs Root cause analysis 3

4 Causes of Network Downtime Unscheduled Downtime Factors Physical link failures 26 Customer premises equipment failure Network hardware failures Unknown Network operations failures Network software failures Congestion/overload Physical environment failures Acts of nature 5.5 Malicious damage hours Mitigable by HA Design + Best Practices Mitigable by HA Systems and Features Mitigable by HA Protocols and Services (e.g. QoS) 4

5 HA Network Design Campus HA Systems Cisco Catalyst 6500 Hardware Redundancy High Availability Systems and Features Power Supply and Fan Redundancy Switch Fabric Module Redundancy Supervisor Redundancy MSFC Redundancy 5

6 Layer 2 High Availability Campus Design Spanning Tree Enhancements High Availability Protocols and Services Portfast set spantree portfast mod/port enable BPDU Guard set spantree portfast bpdu-guard mod/port enable Uplinkfast set spantree uplinkfast enable Backbonefast set spantree backbonefast enable Loop-guard set spantree guard loop mod/port 6

7 Scalability, High Availability and Smooth Migration Internet scalability Tens of thousands of users through Cisco clustering technology Add capacity when and where you need it Distributed application processing Network fabric resiliency and redundancy No single point of failure Smooth migration from Old World to New World Campus PSTN Catalyst Wiring Closet WAN Multiservice WAN CallManager Clusters 7

8 Layer 3 High Availability Services Configuring HSRP High Availability Protocols and Services! interface FastEthernet0/0 ip address standby 10 ip standby 10 authentication STRINGXYZ standby priority 100 preempt standby 10 timers 1 4 standby 10 track ATM3/0! Router 1 WAN or Internet Router 2 8

9 Agenda High Availability CallManager and PBX CallManager and Voic Clustering Over the IPWAN System Enhancements 9

10 CallManager and PBX Integration CallManager Legacy Voic System Gateway Trunk between CCM and PBX Telco PSTN AVVID Network IPT user Migration Legacy PBX 10

11 CallManager and PBX Integration Telco CallManager Gateway DS3 Legacy Voic System BK 7200 Trunk between CCM and PBX PSTN Telco 3700 T AVVID Network Legacy PBX 11

12 Cisco Router/Gateway Portfolio Cisco 3745 Cisco 3725 Cisco 7x00 Cisco 2600XM/2691 Cisco 3600 Cisco 1760 Cisco 1700 Cisco 800 Cisco SOHO Teleworker/SOHO SMB/Small Branch Enterprise Branch Large Branch Enterprise HQ And Beyond 12

13 Strategies for User Migration Building by Building / Floor by Floor Easy from a phone provisioning standpoint PBX s need to remain as tandem for PSTN calls and Inter- Cluster calls - more complex call routing Block of DN s at a time More difficult to provision phones (80+ buildings) Calls to PSTN direct, Inter-Cluster calls direct via IP network - easier to program on PBX Less prone to error 13

14 PBX Vendor Characteristics Avaya Definity G3 CallManager Tested Yes Calling Name Support Yes Protocol PRI NI-2 QSIG Nortel Meridian 1 Yes Yes PRI (DMS100) QSIG Siemens Hicom 300 E CS Yes No PRI NI-2 QSIG Fujitsu 9600 Yes Yes PRI NI-2 QSIG 14

15 Agenda High Availability CallManager and PBX CallManager and Voic Clustering Over the IPWAN System Enhancements 15

16 CallManager to Legacy Voic Integration Challenge: Keep existing Voic system and Integrate with both CallManager and PBX Solution differs depending on VM, PBX and type of Integration Octel is Voic market leader 16

17 CallManager Integration to Voic Octel Octel Digital FTL-N Integration SMDI Nortel 17

18 VM Vendor Characteristics Voic Vendor Certified Solutions Avaya (Octel) 250/350 SMDI Support/ CallManager Certified Dual SMDI Support Digital Phone Integration VPIM Yes/Yes Yes Yes No Avaya (VMX) 200/300 Yes/Yes No Yes No Avaya Intuity Yes/Yes Yes No Yes Nortel CallPilot Yes/No No Yes Yes Meridian Mail (GP) Yes/No Yes No No Siemens Phon Yes/No No Yes No 18

19 Dual Integration Sometimes necessary for migration or coexistence SMDI is currently only protocol that can handle this requirement 19

20 Dual SMDI Integration Octel Aria 250/350 Analog Gateway(s) VG200 or Catalyst 6K CallManager SMDI Voice Path SMDI PBXLink - formerly from Calista This Works today! Texas Instruments - EFT Nortel SL-100 Octel Aria 350 CallManager AVVID Network Gateway Legacy PBX 20

21 DPA for Octel with Avaya or Nortel PBX Octel Voic PIC CallManager Skinny DPA PIC Avaya or Nortel PBX Gateway PSTN 21

22 DPA for Octel with CallManager Octel Voic 24 PIC interfaces DPA skinny CallManager Gateway PSTN Allows for Octel PIC Integration to CallManager 22

23 Multi-Node Octel Networking with Interchange* & Unity Bridge Unity PSTN Unity Bridge Node #2001 Interchange Octel Node #5001 Messages routed through Interchange Interchange controls directory Lowers admin costs Octel Node #3001 Octel Node #

24 Cisco Unity - CallManager Dual Switch Integration Cisco Unity IP CallManager Voice Path Gateway AVVID Network Legacy PBX 24

25 Agenda High Availability CallManager and PBX CallManager and Voic Clustering Over the IPWAN System Enhancements 25

26 Clustering Over the WAN Spatial Redundancy CallManager cluster Logical PBX Voice Mail Server Voice Mail Server IP Phones L.A. Space IP Phones San Diego Spatial Redundancy = Resilience Single Point of Administration, Extension Mobility, Feature Transparency and Unified Dial Plan Can be used for Business Continuance 26

27 Clustering Over the WAN Best Practices Publisher / TFTP < 40ms RTD QoS Enabled BW WAN 40ms round-trip delay between ANY two CallManagers 900 kbps for each 10,000 BHCA within the cluster Four active locations maximum (4 active CMs) Failover across the WAN supported (Additional BW) Check out the IP Telephony Design Guide for CallManager 3.2 and 3.3 for full details 27

28 Clustering Over the WAN Remote Failover Normal Operation Primary Backup WAN Requirements Highly Available QoS Enabled WAN Prioritized Bandwidth For ICCS Additional Bandwidth for SQL, LDAP etc No Backup During WAN Outages (SRST) No Configurations Changes During WAN Outages Publisher 28

29 Agenda High Availability CallManager and PBX CallManager and Voic Clustering Over the IPWAN System Enhancements 29

30 Dial Plan Weight (cont.) 35,000 IP Phones, 20,000 Device Weight Units Pub TFTP Pub TFTP MCS 7835 s MCS 7845 s 30

31 H.323 Enhancements Auto Discovery CallManager s use H.323 or E-ICT for communication H.225 With All Other Devices Migration From Toll-Bypass Networks CM 3.2 AnonymousDevice (H.225) Standard ICT to CM s and H.225 to Others CM 3.3 H.323 Trunk Standard H.323 Gateway (H.225) GK CM 3.3 H.323 Trunk (H.225) (E)ICT to CM s and H.225 to Others CM Anonymous Device No Auto Detect (Use MTP) 31

32 H.323 Enhancements Inter-Cluster Trunks Redundancy San Jose HQ Publisher Backup st Inter-cluster Trunk 1 2 Backup New York Publisher Backup 3 3 Backup 4 2 nd Inter-cluster Trunk 4 As of CallManager 3.3, redundancy is built into the Inter-cluster Trunk (2 ICTs instead of 6) 32

33 H.323 Enhancements Multiple Gatekeeper IP PSTN VoIP Long Distance SP GK Internet Gold VPN Service GK GK Enterprise WAN Private Network Site to Site Up to 10 Physical Gatekeeper s Per Cluster Multiple H.323 Trunks Per CM Gatekeeper Different Zones and/or Tech Prefixes 33

34 V3PN (VoIP/Video enabled IPSec VPN): Deployment Models IP Phone Headquarters IP Telephony Services FR/ATM Branch Office Enet, etc. Multi-service CPN Cable DSL SOHO Access SP IP Phone SOHO/ Telecommuter Enterprise Owned/Managed Or Service Provider Managed Service 34

35 Managed IP PBX Integration with VPN Transport Single Circuit for Voice, Video and Data for the Enterprise Internet PSTN VPN for Intra-Enterprise Connectivity (IPSec/MPLS) Centralized Gateways located at Class 5 for PSTN access Ent-A GW Ent-B GW Enterprise or SP Managed VPN Service Provider Ent-A VPN Ent-B VPN IP PBX (CallManager) HQ Branch Office HQ Branch Office Enterprise A Enterprise B 35

36 SP Call Control Architecture (Cisco GK) EntA Site 1 EntB Site 1 CCM CCM AAA Billing off of Gatekeepers for On-Net Calls CM provides call duration in DRQ (CM 3.2) Enterprise Access GK GK BILL DGK NMS Universal Directory GK DGK GK V V PSTN GLD Partner EntA Site 2 PBX V GK Enterprise Access GK Service Provider GK GK PSTN Access GK V V EntB Site 2 V ITS V V PSTN AAA Billing off of PSTN Gateways For Off-Net calls PSTN 36

37 2001, Cisco Systems, 2001, Inc. Cisco All Systems, rights reserved. Inc. All rights reserved. 37