VVT _05_2002_c1. Presentation_ID , Cisco Systems, Inc. All rights reserved.

Transcription

1 VVT _05_2002_c1 1

2 IP Communications Inter- Operability with PBX/Voic Systems Session Number 2

3 Agenda Overview of Issues CallManager and PBX CallManager and Voic Today s Migration Options Cisco s Network Migration 3

4 Overview of Issues Large site Co-existence with PBX Co-existence with voic Multiple-site Inter-operability with rest of network 4

5 PBX Inter-Working Capabilities CallManager PBX Gateway T1 or E1 Trunk or Analog PSTN T1/E1 CAS or Analog Voice T1/E1 PRI PSTN Protocol Voice Calling/Called # Calling Name (Maybe) 5

6 Voic Inter-Working Capabilities Voic Analog Gateway(s) VG200 or Catalyst 6K CallManager SMDI Voice Path SMDI PBXLink Gateway PBX SMDI Simplified Message Desk Interface 6

7 Agenda Overview of Issues CallManager and PBX CallManager and Voic Today s Migration Options Cisco s Network 7

8 The Requirement Inter-PBX network features Ability to have centralized voic CallManager Features Trunk Between CCM and PBX Existing Voic System PBX PSTN PSTN 8

9 Meeting the Requirement QSIG Inter-PBX network features Ability to have centralized voic CallManager 3.3 QSIG QSIG Trunk Between CCM and PBX Existing Voic System PBX PSTN PSTN 9

10 What Is QSIG? Inter-PBX signaling protocol 15+ year old industry-standard Supported by the world s leading vendors Lucent/Avaya NEC Alcatel Ascom Bosch Nortel Siemens Ericsson Matra Philips 10

11 QSIG Protocol Stack Layer Layers 4 7 QSIG Protocol Stack Standards Application Mechanisms Description End-to-End Protocols Network Transparent Numerous Standards for Supplementary Services and Advance Network Features Layers 3 Layers 2 Layers 1 ECMA-165 ECMA-142/143 ECMA-141 I.430/I.431 QSIG Generic Functional Procedures which Provides Generic Layer Services for Supplementary Services QSIG Basic Call Interface Dependent Protocols 11

12 QSIG Supplementary Services Basic Call Calling Line Identification Presentation Connected Line Identification Presentation Calling/Connected Line Identification Restriction Calling Name Identification Connected Name Identification Presentation Calling/Connected Name Identification Restriction Generic Functional Procedures Call Forwarding Unconditional Call Forwarding Busy Call Forwarding No Reply Call Deflection Path Replacement ANF Call Transfer Call Completion to Busy Subscriber Call Completion on No Reply Call Offer Do Not Disturb/Override See for further details Call Intrusion Advice of Charge, Start of Call Advice of Charge, During Call Advice of Charge, End of Call Recall CTM Incoming Call ANF CTM Location Registration Call Interception ANF Transit Counter ANF CTM Outgoing Call Handling ANF Message Waiting Indication CTM Authentication Common Information ANF Call Priority Interruption/Protection PUM Registration PUM Call Handling ANFs Call Distribution ANF ANF Additional Network Feature CTM Cordless Terminal Mobility (Wireless\Cellular) PUM Public User Mobility 12

13 Physical Implementation for CallManager 3.3 Direct QSIG Trunk on CCM MGCP* + D Channel Backhaul MGCP GW, 6608 T1/E1, VG200 T1/E1 etc CallManager 3.3 QSIG Features Gateway: 6608 T1/E1 VG200 T1/E1 *Refer to Session VVT-200 for Further Information on MGCP 13

14 ISO QSIG Features Supported by CallManager 3.3 Basic call DDI Calling number Called number Connected name 14

15 CallManager 3.3 QSIG Inter-Operability Lucent/Avaya Definity G3 Nortel Meridian 1 Siemens Hicom 300 E CS Alcatel 4400 Siemens Hicom 300 E Ericsson MD

16 Future QSIG Support for CallManager Transfer (by join) Message Waiting Indication (MWI) Divert Calling name restriction Calling number restriction Path replacement Transfer (by re-route) Callback request (CCBS and CCNR) Transit counter etc. 16

17 Agenda Overview of Issues CallManager and PBX CallManager and Voic Today s Migration Options Cisco s Network 17

18 CallManager and Voic Integration Challenges: Slow migration of phone users from PBX to CallManager Keep existing voic system and integrate with both CallManager and PBX Solution differs depending on VM, PBX and type of integration 18

19 CallManager Integration to Existing Voic Voic Voic Digital Ports SMDI Analog Ports Nortel PBX CallManager 19

20 Voic Vendor Characteristics Voic Vendor Certified Solutions SMDI Support/ CallManager Certified Dual SMDI Support Digital Phone Integration Avaya (Octel) Aria Yes/Yes Yes Yes Avaya (VMX) Serenade Yes/Yes No Yes Avaya Intuity Yes/Yes No No Nortel CallPilot Yes/No No Yes Meridian Mail (GP) Yes/No Yes No Siemens Phon Yes/Yes No Yes Please Contact Your Voic Vendor for Further Information 20

21 Dual SMDI Integration Sometimes necessary for migration or co-existence SMDI is currently only protocol that can handle this requirement Analog Gateway(s) VG200 or Catalyst 6K CallManager SMDI Existing Voic Voice Path Gateway SMDI PBXLink AVVID Network PBX 21

22 SMDI for Voic VG248 Voic Multiple SMDI links per Cisco CallManager SMDI fail-over capability Voic location independence Cisco CallManager Analog Ports VG248 SMDI 22

23 Multiple Voic s per Cluster VG248 Voic Voic Voic Analog Ports SMDI Analog Ports SMDI Analog Ports SMDI VG248 VG248 VG248 Cisco CallManager 23

24 SMDI with PBX VG248 Voic Multiple SMDI sources Smooth migration Single SMDI link to voic Analog Ports VG248 Cisco CallManager SMDI SMDI Analog Analog Ports Ports Gateway PBX 24

25 Analog Voic Scalability VG248 Voic SMDI passed between VG248 s Single SMDI port into voic Analog Ports VG248 SMDI Passed Between VG248 s SMDI Cisco CallManager 25

26 Digital Set-Emulation (DSE) Voic system ports emulate proprietary PBX digital feature phones e.g. voic system ports appear as digital extensions to the PBX Also known as Per-port Integration Card (PIC) Voice path is the same as the data path Integration information is derived from the emulated phones display MWI is set and cleared via feature access codes or buttons on dedicated ports PBX Digital Set-Emulation Voice Path Data Path Digital Voice Path Data Path UMS VMS 26

27 Cisco Digital PBX Adapter (DPA) Use Cisco DPA to provide cost-effective solution for Digital Set-Emulation enabled voic systems 27

28 DPA for Octel with Avaya or Nortel PBX Octel Voic DSE CallManager SCCP* DPA DSE Avaya or Nortel PBX PSTN Gateway *Skinny Client Control Protocol, See Session VVT-220 for More Information 28

29 DPA for Octel with CallManager Octel Voic 24 DSE Interfaces DPA SCCP CallManager Gateway PSTN Allows Digital Set-Emulation Integration to CallManager 29

30 DPA Integration Notes No changes to either the PBX or the voic system DPA must be inserted in-line between the PBX and voic system Certified by Octel/Avaya for Aria 250/350 and Serenade 200/300 30

31 Voic Summary SMDI via CallManager SMDI via VG248 Single Integration SMDI via VG248 Dual Integration DPA with Octel Single Integration DPA with Octel Dual Integration Nortel SL-100 with Meridian Mail GP (MSM) Nortel M1 with Meridian Mail EC Nortel M1 with CallPilot 31

32 SMDI via CallManager CallManager supports virtually any voic system that can provide SMDI with analog FXS ports i.e. Octel 100, 200/300, 250/350, Intuity Audix, Siemens Phon , Centigram/BayPoint (OnePoint and NuPoint Messenger), Lyrix ECS and IBM Message Centre SMDI Voic CallManager Analog Ports (via VG200 or WSX-6624) 32

33 SMDI via VG248 Single Integration Voic VG248 supports virtually any voic system that can provide SMDI with analog FXS ports i.e. Octel 100, 200/300, 250/350, Intuity Audix, Siemens Phon , Centigram/BayPoint (OnePoint and NuPoint Messenger), Lyrix ECS and IBM Message Centre Cisco CallManager Analog Ports VG248 SMDI 33

34 SMDI via VG248 Dual Integration Works with any SMDI/analog FXS ports capable voic providing: Uniform dial-plan exists Transfer and re-connect sequences are common Connectivity between CallManager and PBX exists Note: Check with voic vendor for position on support Analog Ports VG248 Cisco CallManager Voic SMDI SMDI Analog Analog Ports Ports Gateway PBX 34

35 DPA with Octel Single Integration Lucent/Avaya G3 DPA 7630 ( wire) Nortel Meridian 1 DPA 7610 ( wire) DPA Octel Voic 24 DSE Interfaces SCCP CallManager Gateway PSTN 35

36 DPA with Octel Dual Integration Works with Octel Digital Set-Emulation providing: Uniform dial-plan exists Transfer and re-connect sequences are common Connectivity between CallManager and PBX exists Note: Check with voic vendor for position on support CallManager Ethernet Gateway Octel 200/300 or 250/350 T1 PSTN Lucent/Avaya G3 or Nortel Meridian 1 36

37 Nortel SL-100 with Meridian Mail GP (MSM) Nortel Meridian Mail GP (MSM) SMDI SMDI CallManager Voice Path Nortel SL-100 Gateway 37

38 Nortel M1 with Meridian Mail EC Nortel Meridian Mail EC Checkmate Abridge Server SCCP MWI Msgs CallManager Nortel M1 Gateway 38

39 Nortel M1 with CallPilot Nortel CallPilot C-LAN CallManager SCCP Checkmate Abridge Server C-LAN Gateway Nortel M1 39

40 Agenda Overview of Issues CallManager and PBX CallManager and Voic Unified Messaging Unity Cisco s Network 40

41 Cisco Unified Messaging Unity Voic networking PBX integration See Session VVT-212 for More Information on Cisco Unity 41

42 Cisco Unity Migration Roadmap Networking Cisco Unity today Audio Message Interchange Specification Analog (AMIS-A) Octel 200/300, 250/350, Intuity Audix and Intuity Interchange Nortel Meridian Mail Siemens Phon Centigram Cisco Unity Bridge (Analog OctelNet) Cisco Unity tomorrow VPIM 42

43 Cisco Unity Bridge Essentially a protocol converter SMTP to Analog OctelNet Supports 24 analog ports per server Design issues: One Cisco Unity required per Unity Bridge Analog networking to Octel networking 43

44 Cisco Unity with Cisco Unity Bridge Multi Node Octel Cisco Unity Bridge 24 Ports per server Directory sync i.e. NameNet updates, when messages are sent between users Supports Octel 100, 200/300, 250/350 and Intuity Interchange G.729 support International support Cisco Unity IP Connection to Cisco Unity Bridge N1 N2 N3 N4 Octel Messaging Nodes 44

45 Cisco Unity Networking Today Octel Aria 250/350 Siemens Phon Digital OctelNet Intuity Interchange AMIS-A Analog OctelNet Digital Networking VPIM Cisco Unity Octel Serenade 200/300 Nortel CallPilot 45

46 Cisco Unity Networking Tomorrow Octel Aria 250/350 Siemens Phon Digital OctelNet Intuity Interchange AMIS-A VPIM Digital Networking VPIM Cisco Unity Octel Serenade 200/300 Nortel CallPilot 46

47 Cisco Unity Dual-Switch Integration with CallManager and PBX Simultaneously connects to both PBXs and Cisco CallManager Allows for seamless deployment and protects existing legacy investment during transition to IP Migrate users from one system to another at the customers pace Single server with voice card(s) for PBX and Ethernet for CallManager Requires PBXLink and voice card(s) for digital Integrations i.e. Avaya G3 and Nortel M1 47

48 Cisco Unity/CallManager Dual PBX Integration Creates a Smooth Migration from TDM World to IP World PBX Voic System Analog Lines SMDI Link Unity Server Exchange Message Store PBX Phone T-1 line Analog Lines SCCP PSTN 3600 Router Workstation with Outlook CallManager IP Phones 48

49 Supported PBX Integrations Lucent/Avaya Definity G3 Nortel Meridian 1 NEC NEAX2000, NEAX2400 Ericsson MD 110 Mitel SX-200, SX-2000 Intecom Centrex AT&T 1AESS AT&T 5ESS Nortel Networks DMS100 For more information please contact your Cisco Account Team 49

50 Agenda Overview of Issues CallManager and PBX CallManager and Voic Unified Messaging Unity Cisco s Network 50

51 Make-up of Cisco Campus SCJ-18 SCJ-19 SILVERCREEK PARKMOOR-3 BRENNAN SCOTTS VALLEY SCJ-17 SCJ-16 SCJ-14 SCJ-13 SCJ-10 TRIMBLE RIO ROBLES Walsh B Walsh C Walsh D Sites 1-3 SCJ-15 SJ-N SCJ-12 SCJ SC-J9 SCJ-8 FIRST ST SJ-M SJC-D SJC-E SJC-G Site 4 SCJ-7 SCJ-6 SCJ-5 SCJ-4 SCJ-3 SCJ-2 SCJ-1 ZANKER BAYPOINTE 0 BAYPOINTE SJ-O SJ-O 56 SJC-P SJC-P SJC-A CHAMPION SJC-B SJC-I SJC-K SJC-C Tasman VM1 VISTA MONTANA SJC-F SJC-H HIGHWAY 237 SJC-L SJC-J VM2 => 50 IP Phone Users BAYTECH < 50 IP Phone Users 60+ Buildings, 20,000+ People 51

52 History Pre IP Telephony (1998) 2 Lucent G3r PBX s Number portability across the PBX s 3 Octel 350 voic systems Networked voic to 150+ other systems Octel VM PBX OctelNet 526 NXX 527 NXX 525 NXX Octel VM DCS Link PSTN OctelNet to Cisco Remote Sites Octel VM PBX 52

53 History Introduce IP Telephony Fall 98 OctelNet OctelNet to Cisco Remote Sites 526 NXX 527 NXX 525 NXX Octel VM Octel VM Octel VM PBX DCS Link PBX CM 2.2 T1 Gateway PSTN 2.2 CallManager 200 Users 53

54 Issues with Fall 98 Introduction IP phones given new DID numbers Two numbers per subscriber not viable (running out of DID numbers) IP phones assigned real IP address Supplying IP addresses from class B pool not viable IP phone in addition to legacy phone Confused subscribers as to which number they were to use Resulted mainly in outgoing calls 54

55 Issues with Fall 98 Introduction (Cont.) Message light not operating in this mode Dual dissimilar integration not possible on Octel 350 voic system Users leaned even more to their legacy phone Variable voice quality with attached PC Older phones, 12 SP+ and 30 VIP, only had a hub Power issues IP phones required local power This proved an issue in some locations e.g. Break-rooms 55

56 Next Steps Removed existing configuration of IP phones Installed new CallManager 2.3 system with new 853 DID range (for new hires) New dedicated voic system installed Grow incrementally to over 1,900 users on single server 56

57 Telephony View of Cisco Campus Late 1999 Early 2000 OctelNet OctelNet to Cisco Remote Sites Only IP phone for 2,500 users 526 NXX 527 NXX 525 NXX Octel VM Octel VM Octel VM 853 NXX Octel VM Full voic integration Integrated dial plan Caller ID PBX DCS Link PBX SMDI Link CM PSTN 2.4 CallManager 2,500 Users 57

58 Migration from CallManager 2.4 to 3.0 April 2000 Cut over existing 2.4 CallManager to 3.0 Cluster Migrate handsets to IP Phone 7960 User self installation 58

59 Current Telephony View of Cisco Campus Summer 2000 IP address using network 10 Better voice quality with 7960 phone and QoS Octel VM PBX Octel VM DCS Link OctelNet 526 NXX 527 NXX 525 NXX Octel VM PBX OctelNet to Cisco Remote Sites 853 NXX Octel VM SMDI Link CM 3.0 In-line power availability PSTN CallManager Cluster 5,000 Users 59

60 Cluster as Deployed by Cisco Support for up to 10,000 Users 853 Cluster CM-A CM-B CM-C CM-D Backup Backup Publisher Centralized TFTP Server Supports 5 Clusters 60

61 Migrating Existing Users Moving Forward Goal was to move remainder of campus to IP telephony by late 2001 Users need to keep existing DID numbers Voic functionality must be maintained No additional investment in existing hardware 61

62 Voic Integration Challenge Digital Set-Emulation Octel Voice Mail system CallManager MWI Signaling Audio T1 Gateway PBX PSTN IP phones do not have transparent voic 62

63 The Voic Migration Solution Require new device (DPA) to allow for voic dual Integration functionality CallManager Ethernet 525 Octel 350 PIC PSTN T1 Gateway Lucent/Avaya G3r PBX 63

64 Scaling the Migration Add more voice paths to IP phone side with DPA 525 Octel 350 PSTN CallManager Ethernet T1 Gateway Lucent/Avaya G3r PBX 64

65 Hybrid Solution During Migration DPA s OctelNet OctelNet to Cisco Remote Sites 902 NXX Octel VM 526 NXX 527 NXX 525 NXX 853 NXX 902 Cluster Octel VM Octel VM Octel VM Octel VM SMDI Link DCS Link 526 Cluster PBX PBX 853 Cluster PSTN 527 Cluster 525Cluster 65

66 Strategies for User Migration Building by building 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 66

67 IP Communications After Phone Migration OctelNet OctelNet to Cisco Remote Sites 902 NXX Octel VM 526 NXX 527 NXX 525 NXX 853 NXX 902 Cluster Octel VM Octel VM Octel VM Octel VM SMDI Link 526 Cluster SJ Campus IP 853 Cluster PSTN 527 Cluster 525 Cluster 67

68 Cisco Field Offices Typically no bigger than 200 employees Flash-Cut becomes viable option Nortel PBX with Octel voic 68

69 Flash Cut PBX Keep Legacy VM Example Cisco New York Office Digital Set-Emulation Integration Octel 250 Octel 250 (Most Common Type of Octel to PBX Integration) Nortel M1 PBX SMDI Analog Ports Gateway CallManager In this Case the Octel was Converted to SMDI with Analog Ports 69

70 DPA for Octel with CallManager Octel Voic 24 Digital Set-Emulation Interfaces DPA Skinny CallManager Gateway PSTN Allows Digital Set-Emulation Integration to CallManager 70

71 Centralized Call Processing? Calling pattern to/from Field Sales Offices did not warrant cost of increasing WAN bandwidth within US Single-site deployment model was adopted Cisco PSTN rates are low 2 3 c/min WAN upgrade currently in planning stages Regional centres with centralized call processing will be implemented in the future 71

72 Lessons Learned QoS strategy to guarantee voice quality Create a simple dial-plan to: Eliminate potential routing loops with PBX Help manage going forward Take advantage of IP phone and switch features to make IP addressing easy Power planning for IP phone sets (in-line power) Using a single Codec (G.711) makes life simple Transparent voic functionality for user migration Single phone at a time on the users desk Merging/co-operation of Telecom/Data teams 72

73 San Jose Campus: 100% AVVID Complete! Legend Retrofit Complete YTD Retrofit Q1 Retrofit Q1 Partial Retrofit Year End Summary 46 Buildings Complete 18,829 employees and devices on Cisco s VoIP Network 16,000 port/stations removed H G I F J K E D L C B P A M N O from the PBX 20 EPN's disconnected 19 9,000 Lucent Phones removed Completion of Q1 will result in 99.9% AVVID Complete D C B PETALUMA

74 What s Next Continue to upgrade WAN/flash-cut branch offices In progress Trials of Telecommuter IP phones In progress Upgrade of campus LAN Infrastructure for QoS Completed Unified messaging to replace Octel In progress Replace Lucent/Avaya Call-Centres with IP Contact Centre Completed 74

75 IP Communications Interoperability with PBX/Voic Systems Session Number 75

76 VVT _05_2002_c1 76