2001, Cisco Systems, Inc. All rights reserved. Copyright 2001, Cisco Systems, Inc. All rights reserved. Printed in USA. Presentation_ID.

Transcription

1 2915_05_2001_c1 2001, Cisco Systems, Inc. All rights reserved. 1

2 Deploying Large-Scale H.323 oip SP Networks Session 2915_05_2001_c1 2001, Cisco Systems, Inc. All rights reserved. 3 Core Message H.323 networks can be used in large service provider oip networks, if proper architecture and features are deployed 2915_05_2001_c1 2001, Cisco Systems, Inc. All rights reserved. 4

3 Pondering H.323 for Large-Scale SP Networks What are the key components in a large-scale H.323 network? How can we design the H.323 network to scale? What are the performance criteria to design around? How can we size the network? What are some configuration examples? How do we increase availability? What are some case study examples? What else should I consider? 2915_05_2001_c1 2001, Cisco Systems, Inc. All rights reserved. 5 Today s Agenda Review of H.323 Architecture Anatomy of a Large-Scale H.323 SP Network Gatekeeper Core and Components Call Routing in the H.323 Network Network Dimensioning Case Study: Dimensioning of an ITSP Increasing Availability 2915_05_2001_c1 2001, Cisco Systems, Inc. All rights reserved. 6

4 Today s Agenda Billing in the H.323 Network Security Expanding the Coverage Area Interconnecting to TDM-Based Carriers Interconnecting to IP-Based Carriers Interconnecting with Non-Cisco-Based Carriers Other Services: Card Services Network Management Solutions What s Next? 2915_05_2001_c1 2001, Cisco Systems, Inc. All rights reserved. 7 Review of H _05_2001_c1 2001, Cisco Systems, Inc. All rights reserved. 8

5 H.323 Review ITU-T specification Defines multimedia applications over Packet Based Networks Defines call signaling Direct signaling Gatekeeper Route Call Signaling (RCS) Elements Terminal Gateway Gatekeeper Multipoint Conference Unit Registration, Admission and Status (RAS) H.225 Media establishment H.245 Fast connect H.245 tunneling 2915_05_2001_c1 2001, Cisco Systems, Inc. All rights reserved. 9 H.323 Components H.323 MCU Scope of H.323 e H.323 Gatekeeper Packet Network H.323 Terminal H.323 Gateway ISDN.70 Terminal H.324 Terminal Speech Terminal H.320 Terminal Speech Terminal 2915_05_2001_c1 2001, Cisco Systems, Inc. All rights reserved. 10

6 H.323 oip Review Signaling Call Flow Static Configuration On GW Called Number to IP Address Mapping Calling Party H.225 (TCP) H.245 (TCP) H.323 oip Network Setup Call Proceeding Alerting Connect Capabilities Exchange Open Logical Channel Open Logical Channel Acknowledge Signaling Called Party Media (UDP) RTCP Stream Bearer Or Media 2915_05_2001_c1 2001, Cisco Systems, Inc. All rights reserved. 11 H.323 oip Review Addition of the Gatekeeper Registration Registration H.323 oip Network Calling Party ARQ Called Party H.225 RAS H.225 (TCP) ACF Setup Call Proceeding ARQ ACF Signaling H.225 RAS Alerting H.245 (TCP) Connect Media (UDP) RTCP Stream Bearer Or Media 2915_05_2001_c1 2001, Cisco Systems, Inc. All rights reserved. 12

7 Anatomy of Large-Scale H.323 Network 2915_05_2001_c1 2001, Cisco Systems, Inc. All rights reserved. 13 Needs of Large H.323 Networks Accommodate large number of POPs Allow new POPs to be added Manage POPs centrally Support a scaleable dial plan Handle high volume of minutes Keep call success rates high Maintain high availability Enable only authorized usage Support interconnecting with other TDM (SS7 or non-ss7) or IP carriers 2915_05_2001_c1 2001, Cisco Systems, Inc. All rights reserved. 14

8 Large-Scale H.323 Functions Intradomain and Interdomain Call Routing Gatekeeper Core D Wholesale oip Network Shared Services OSP Billing Interdomain Call Routing Card Services Network Management RTSP TFTP BILL AAA SC SS7 POP SLT Non-SS7 POP TDM TDM Access Access 2915_05_2001_c1 2001, Cisco Systems, Inc. All rights reserved. 15 Large-Scale H.323 Network Components STP STP EO ISP SS7 IMT Prompt Server SC Managed IP Network Settlement RADIUS E1/R2, PRI, or Analog Trunks Network Management EO Aggregation Transport/Billing/Authentication Provisioning/Management Termination 2915_05_2001_c1 2001, Cisco Systems, Inc. All rights reserved. 16

9 Gatekeeper and Gateway Core 2915_05_2001_c1 2001, Cisco Systems, Inc. All rights reserved. 17 Gateways Provides interface between and IP Grooms dial plan for easier management and higher scaling Generates billing data (start/stop records) to billing server (AAA/RADIUS or OSP) Hosts Interactive oice Response (IR) application Supports redundancy mechanisms Supports bandwidth efficiency mechanisms Supports security mechanisms 2915_05_2001_c1 2001, Cisco Systems, Inc. All rights reserved. 18

10 Gatekeepers Maintain registration of GWs and administers zone Manages GW resources to increase availability Maintain call routing information (zone prefix tables) Supports redundancy mechanisms Supports TMP interface for enhanced call routing and services 2915_05_2001_c1 2001, Cisco Systems, Inc. All rights reserved. 19 H.323 Component Summary Gateway and Gatekeeper RAS Gatekeepers RAS IP E1/T1/T3 Digital oice, Fax, Modem,DTMF Bearer Gateways IPRAS IP Analog BILL AAA 2915_05_2001_c1 2001, Cisco Systems, Inc. All rights reserved. 20

11 Gateway and Gatekeeper Central Routing Table Prefix Destination 312 ChicagoGW 415 Western 212 Eastern 312 Chicago POP Central Zone 212 NY POP Eastern Zone Eastern Routing Table Prefix Destination 212 NYGW 312 Central 415 Western Western Routing Table Western Zone Prefix Destination 415 SFGW 312 Central 212 Eastern SF POP _05_2001_c1 2001, Cisco Systems, Inc. All rights reserved. 21 Adding a Directory Gatekeeper Central Routing Table Prefix Destination 312 ChicagoGW * D 312 Chicago POP Central Zone 212 NY POP Eastern Zone Eastern Routing Table Prefix Destination 212 NYGW * D IP Network Western Routing Table Western Zone D D Routing Table Prefix Destination 415 SFGW * D SF POP Prefix Destination 415 Western 312 Central 212 Eastern _05_2001_c1 2001, Cisco Systems, Inc. All rights reserved. 22

12 Directory Gatekeeper Create a hierarchical architecture of s Performs inter-regional call routing Eliminate need for fully-meshed gatekeeper configuration Maintain master zone prefix table Simplify dial-plan management when zones are added or deleted Performs interdomain call routing 2915_05_2001_c1 2001, Cisco Systems, Inc. All rights reserved. 23 SJ-GW Configuration hostname SJ-GW1 isdn switch-type primary-5ess controller T1 0 framing esf clock source line primary linecode b8zs pri-group timeslots 1-24 dial-peer voice 1 voip destination-pattern 1... session target ras dial-peer voice 408 pots destination-pattern port 0:D prefix 408 Repeat for other NPA-NXXs served gateway interface Loopback0 ip address h323-gateway voip interface h323-gateway voip h323-id SJ-GW1 h323-gateway voip id US- ipaddr h323-gateway voip tech-prefix 1# interface Ethernet0 ip address interface Serial0:23 isdn switch-type primary-5ess isdn incoming-voice modem Zone SJ-GW1 2915_05_2001_c1 2001, Cisco Systems, Inc. All rights reserved

13 US- Configuration Hostname US- interface Ethernet0 ip address gatekeeper zone local netman.com zone remote D netman.com zone prefix US- 408* zone prefix D * lrq forward-queries no shutdown US-GW1# show gateway Gateway US-GW1 is registered to Gatekeeper D US- Zone SJ-GW _05_2001_c1 2001, Cisco Systems, Inc. All rights reserved. 25 Directory Configuration Hostname dirgatekeeper interface Ethernet0 ip address gatekeeper zone local D netman.com zone remote CHI- netman.com zone remote NY- netman zone prefix US- 408* zone prefix CHI- 312* zone prefix NY- 212* lrq forward-queries no shutdown Zone CHI- NY- LRQ D LRQ US- SJ-GW _05_2001_c1 2001, Cisco Systems, Inc. All rights reserved. 26

14 Hierarchical Design - Network Scaling Small Network - Gateways only Small Network - simplified with a Gatekeeper Medium Network - Multiple Gatekeepers Medium-Large Network - Multiple Gatekeepers and a Directory Gatekeeper Gateway Gatekeeper Directory Gatekeeper 2915_05_2001_c1 2001, Cisco Systems, Inc. All rights reserved. 27 Adagio Components Gatekeeper Core Summary Directory Gatekeeper Performs call routing search at highest level Example = Country Code Distributes Service D Country codes among other Ds Forwards LRQ Provider to Partner D if call doesn t terminate in local POP-A SP D Gatekeeper Performs call routing search at intermediate level Example = NPA-NXX Distributes NPA among other s Provides GW resource management (RAI, gw-priority...) Provides Zone maintenance Gateway Acts as interface between and IP Normalizes numbers from before entering IP Normalizes numbers from IP before entering Contains the dial peer configuration Local Registers to 2915_05_2001_c1 2001, Cisco Systems, Inc. All rights reserved. 28

15 Call Routing in the H.323 Network 2915_05_2001_c1 2001, Cisco Systems, Inc. All rights reserved. 29 Creation of Call Routing Layers Master Table 408* ZONE A 415* ZONE A 312* ZONE B 212* ZONE C default * route Inter-Area Code default * route Zone A Zone B Zone C Intra-Area Code Local Local Local 2915_05_2001_c1 2001, Cisco Systems, Inc. All rights reserved. 30

16 Call Routing in the Network Coverage area POP #1 POP #2 POP #3 POP #4 Use of gatekeeper Use of directory gatekeeper International D Zone Zone Zone POP #1 POP #2 POP #3 POP #4 Local Local Local Local _05_2001_c1 2001, Cisco Systems, Inc. All rights reserved. 31 D Administration with National Dial Plan 408* CAL - 312* CHICAGO- 623* PHOENIX- D Add in the Chicago zone Add in the Phoenix zone Add directory gatekeeper US-GW US-GW2 * D 312* Chicago-GW1 * D 623* Phoenix-GW1 * D Chicago- GW1 US- US- GW1 GW2 Intra-LATA Rate Rate Center #1 Toll Center #2 California Phoenix 2915_05_2001_c1 2001, Cisco Systems, Inc. All rights reserved. 32

17 D Administration with International Dial Plan 1* US- 86* AS- 33* E- D Add in the Asia zone Add in the EMEA zone Add directory gatekeeper US-GW US-GW2 * D 8610* CHINA-GW1 * D 3303* FRANCE-GW1 * D FRANCE- GW1 US- US- GW1 GW2 Intra-LATA Rate Center #1 Toll Rate Center #2 North America ASIA CHINA- GW1 EMEA 2915_05_2001_c1 2001, Cisco Systems, Inc. All rights reserved. 33 Need for Grooming Groom the dial plan to: 1. Keep dial plan consistent 2. Reduce size of Zone tables 3. Make scaling network manageable North America 1408* 1312* 1212* Local 7 Digit: default * route Interstate 10 Digit: International: Master Table 1* North America 86* China 33* France China 8610* 8611* 8612* Local default * route France 3301* 3302* 3303* International Local Domestic 2915_05_2001_c1 2001, Cisco Systems, Inc. All rights reserved. 34

18 Gateway Number Translation Example Call Direction oip Local US Intrntl Country+Area+Local Number Manipulation On Outgoing oip Dial-Peer: For International Calls, Strip the Access Code (011) For US Calls, Different Area Code, Keep the Same Format For Local Calls, Same Area Code, Add the Country and Area Code 2915_05_2001_c1 2001, Cisco Systems, Inc. All rights reserved. 35 Translation Rules Example Translation-rule 1 Rule 0 ^ Rule 1 ^ Rule 2 ^ Rules say that for any digit pattern beginning with a 5, 6, or 7 followed by any 4 digits, then prepend with a , or i.e translates to External URL needed here pulation_enhancements.htm 2915_05_2001_c1 2001, Cisco Systems, Inc. All rights reserved. 36

19 Translation Rules Example (Cont.) Where do you apply translation rules? Method 1: Applying Rules to POTS/oIP Dial Peers Method 2: Applying Rules to a physical POTS interface Example: translation-rule 1 Rule 0 ^ Rule 1 ^ Rule 2 ^ port 1/0/0 translation called 1 Useful commands: debug translation-rule detail test translation-rule _05_2001_c1 2001, Cisco Systems, Inc. All rights reserved. 37 Exercise Translation Rules and Dial Peers hostname FRANCE-GW1 translation-rule 2 Rule 0 ^01.% 3301 Rule 1 ^02.% 3302 Rule 2 ^03.% 3303 Rule 3 ^04.% 3304 Rule 4 ^05.% 3305 Rule 5 ^06.% 3306 translation-rule 3 Rule 0 ^001.% 1 Rule 1 ^002.% 2 Rule 2 ^003.% 3 Rule 3 ^004.% 4 Rule 4 ^005.% 5 Rule 5 ^006.% 6 Rule 6 ^007.% 7 Rule 7 ^008.% 8 Rule 8 ^009.% 9 dial-peer voice 1voip destination-pattern 00T translate-outgoing called 3 session target ras dial-peer voice 2voip destination-pattern 0[1-6]... translate-outgoing called 2 session target ras gateway EMEA Zone Local FRANCE POP Assume a GW in a France POP Area Code = 03 Country Code = 33 Dialing Habits Local Include Area Code (0x) + 8 Digits Long Distance Use Area Code (0x) + 8 Digits International 00 Access Code Normalize local dialing patterns 2915_05_2001_c1 2001, Cisco Systems, Inc. All rights reserved. 38

20 Outbound Gateway Number Translation Tasks Call Direction oip Append/Remove Local Access Digits Destination # Is Normalized: (e.g. Country+City+Local) Number Manipulation On Outgoing POTS Dial-Peer: Administer Local Access Rules (e.g Prefix or Strip Digits) POTS Peers Reduced Since Number Is Always Normalized 2915_05_2001_c1 2001, Cisco Systems, Inc. All rights reserved. 39 Network Dimensioning and Hierarchical Design 2915_05_2001_c1 2001, Cisco Systems, Inc. All rights reserved. 40

21 Network Dimensioning How many GWs per POP? How many GWs per zone? How many s per D? 2915_05_2001_c1 2001, Cisco Systems, Inc. All rights reserved. 41 Designing the POP Design the SP POP with following factors Busy Hour Call Attempts (BHCA) Number of gateways required to handle the anticipated call volume Number of Gatekeepers required to process the GW signaling/ras messages 2915_05_2001_c1 2001, Cisco Systems, Inc. All rights reserved. 42

22 Sizing Exercise Given: 1,000,000 BHCA network with average hold time = 3 minutes Max BHCA per DS0 = 60 min/hour/3 min HT = 20 BCHA per GW DS0s per GW will depend on signaling type 92 T1 DS0s (PRI) max on AS5300, 92 X 20 BHCA/DS0 = T1 DS0 (CAS) max on AS5300, 96 X 20 BHCA/DS0 = E1 DS0s max on AS5300, 120 X 20 BHCA/DS0 = 2400 T1 PRI T1 CAS E1 PRI E1/R2 GW BHCA # GWs # Zones _05_2001_c1 2001, Cisco Systems, Inc. All rights reserved. 43 Case Study Part 1: Building to Core 2915_05_2001_c1 2001, Cisco Systems, Inc. All rights reserved. 44

23 Customer A Profile Customer A Network Type Growth Areas of Interest # OIP GWs Minutes of Traffic per Month Number of POPs Location Profile of PPs Traffic BHCA per POPs 50 Customers, Toll Arbitrage and Clearinghouse 100% Cisco OIP, Card, Systems Integrator OIP in Targeted Areas, Expand to ITSP in China??? 1 Million 5 San Jose, New York, Miami, Mexico, enezuela 18,000 BHCA per POP 2915_05_2001_c1 2001, Cisco Systems, Inc. All rights reserved. 45 Brand A Network Map San Jose New York Miami Mexico enezuela POP s Serviced By Customer A 2915_05_2001_c1 2001, Cisco Systems, Inc. All rights reserved. 46

24 Customer A Design Needs Allow for POPs located in 5 cities Traffic needs 18,000 BHCA for each POP Enable network to scale to allow future addition of 5 new POPs in each country Increase availability of core components Allow for billing of oip calls Allow for security 2915_05_2001_c1 2001, Cisco Systems, Inc. All rights reserved. 47 Case Study Design Coverage Area United States San Jose Miami Phoenix Mexico Mexico City enezuela City United States Zone? GWs per POP Use of gatekeeper and directory gatekeeper Create zones based on country code D Mexico Zone? GWs per POP enezuela Zone? GWs per POP Local Local Local 2915_05_2001_c1 2001, Cisco Systems, Inc. All rights reserved. 48

25 POP Sizing Number of GWs per POP Assumptions: POP must service 18,000 BHCA Each call has 3 minute Hold Time (HT) Number of DS0s per GW is platform dependent 120 E1 DS0s per GW (AS5300) 5 CPS max x 60 sec/min x 60 min/hr =18,000 BHCA for POP # GWs per POP? Local Calculating number of GWs: Calls/DS0 per hour = (60 min/hour)/(hold time) = 60/3 = 20 BHCA/DS0 BHCA capacity of AS5300 = (DS0/GW) * (BHCA/DS0) = 120 * 20 = 2,400 BHCA/GW (0.67 calls/sec) # GWs needed = (POP BHCA)/(BHCA/GW) = X/2400 GWs needed = 18,000/2400 GWs needed = 7.5 GW = 8 GWs needed To support 18,000 BHCA 2915_05_2001_c1 2001, Cisco Systems, Inc. All rights reserved. 49 Number of s Needed for Given GWs Assumptions: Consider the max CPS for a GW; This varies depending on platform I.e. AS5300 = 2 CPS # GWs x 2CPS = Max CPS on POP Local Calculating Number of s Required to Administer 8 GWs Total GWs in US x GW max CPS = 24 x 2 = 48 CPS Max Refer to performance numbers Where: # Endpoints = CPS max We have seen call success rates of 99% with 100 endpoints at 60 CPS This falls within approved range of performance 2915_05_2001_c1 2001, Cisco Systems, Inc. All rights reserved. 50

26 Dimensioning Number of Ds Needed for Given s Assumptions: Design in D to be under 65% CPU utilization Testbed: 100% of new calls on utilized D (e.g. 60 CPS); Findings determined that each uses 8 10% of the D CPU For s that send 100% of new calls to D, 6 s will use 60% of D CPU 6:1 /D ratio Typical D deployments handle less than 100% of new calls; /D ratios will increase D Calculating Number of Ds Required to Administer s For case study Total s in network = 3 The total RAS messaging sent to D is estimated at 20% Since 6:1 /D ratio for 100% new calls, then at 20% = 30:1 ratio Recommendation is 6:1 :D ratio 2915_05_2001_c1 2001, Cisco Systems, Inc. All rights reserved. 51 Case Study Design Translation rule Strip 011 access code DNIS= D Prefix Destination 1* US- 52* MEX- 58* EN- United States Mexico Zone enezuela Zone 1* Zone 52* 58* x 8 GW x 8 GW x 8 GW x 8 GW Mexico City x 8 GWs City SJ PHX MIA Local 1408* DNIS = Local 5210* Local 5810* 2915_05_2001_c1 2001, Cisco Systems, Inc. All rights reserved. 52

27 San Jose GW1 GATEWAY CONFIG hostname SJ-GW1 interface Ethernet0/0 ip address h323-gateway voip interface h323-gateway voip id US- ipaddr h323-gateway voip h323-id SJ-GW1 h323-gateway voip tech-prefix 1# isdn switch-type primary-5ess controller T1 0 framing esf clock source line primary linecode b8zs pri-group timeslots 1-24 interface Serial0:23 isdn switch-type primary-5ess isdn incoming-voice modem dial-peer voice 1408 pots destination-pattern port 0:D dial-peer voice 1voip destination-pattern 011T translate-outgoing called 1 session target ras gateway translation-rule 1 Rule 0 ^0111.% 1 Rule 1 ^0112.% 2 Rule 2 ^0113.% 3 Rule 3 ^0114.% 4 Rule 4 ^0115.% 5 Rule 5 ^0116.% 6 Rule 6 ^0117.% 7 Rule 7 ^0118.% 8 Rule 8 ^0119.% 9 <strips the 011 access code> 2915_05_2001_c1 2001, Cisco Systems, Inc. All rights reserved. 53 US- and D Configurations hostname D gatekeeper zone local D netman.com zone remote US- netman.com zone remote MEX- netman.com zone remote EN- netman.com zone prefix US- 1* zone prefix MEX- 52* zone prefix EN- 58* lrq forward-queries no shutdown hostname US- gatekeeper zone local US- netman.com zone remote D netman.com zone prefix US- 1408* zone prefix US- 1623* zone prefix US- 1305* zone prefix D * gw-type-prefix 1#* default-technology lrq forward-queries no shutdown 2915_05_2001_c1 2001, Cisco Systems, Inc. All rights reserved. 54 D 1* 52* 58* US- MEX- EN-

28 Zone Sizing Number of Busy Hour Call Attempts (BHCA) per depends upon: platform Fault-tolerance features Number of registered endpoints Dial plan complexity Average hold times 2915_05_2001_c1 2001, Cisco Systems, Inc. All rights reserved. 55 Single Gatekeeper Performance Testbed Consisting of 3660 Platform CPS Endpoints IOS version 12.1(5)XM 2915_05_2001_c1 2001, Cisco Systems, Inc. All rights reserved. 56

29 Single Gatekeeper Performance (Cont.) CPS Testbed Consisting of 7200 Platform Endpoints * IOS version 12.1(5)XM 2915_05_2001_c1 2001, Cisco Systems, Inc. All rights reserved. 57 Increasing Availability in the H.323 Network 2915_05_2001_c1 2001, Cisco Systems, Inc. All rights reserved. 58

30 Redundancy Mechanisms Gateways Multiple GWs servicing same coverage area Rotary dial peers RAI, GW priority Zone gatekeeper Alternate clustering Directory HSRP Alternate D 2915_05_2001_c1 2001, Cisco Systems, Inc. All rights reserved. 59 Rotary Dial Peers Multiple dial-peers with a preference assigned to dial-peers to establish order Zero is the highest priority (default) Nine is the lowest priority Select dial-peer based on longest matching destination pattern (e.g. select over 555.) Then use preference values for equally matching destination patterns Dial-peers with equally matching destination patterns and equal preference values are chosen at random 2915_05_2001_c1 2001, Cisco Systems, Inc. All rights reserved. 60

31 Rotary Dial Peer Benefits Simple load balancing Multiple dial-peers with equal preferences Randomly select a destination gateway if multiple terminating gateways are available Simple least-cost routing Multiple dial-peers with various preferences. Try the most preferred endpoint first fall-back (hairpinning) Re-routes incoming call back to if no gateway hop-off point is available on the oip network 2915_05_2001_c1 2001, Cisco Systems, Inc. All rights reserved. 61 Rotary Dial-Peer Example GW A 1 GW B 3 2 IP Network First choice Second choice Third choice GW A Configuration dial -peer voice 100 voip destination-pattern session target ras dial -peer voice 200 voip destination-pattern 556. session target ipv4: preference 1 dial -peer voice 300 pots destination-pattern 556. port 0:d preference _05_2001_c1 2001, Cisco Systems, Inc. All rights reserved. 62

32 Call Admission Control to Route Calls to Free Resources What happens when a Gateway is getting full? H.323 Resource Availability Indicator (RAI) informs Gatekeeper when no Circuits (DS0s) or DSPs available Gatekeeper can select best available GW the first time to increase call completion rates and lower post-dial delay RAI RAI IP Once the gatekeeper receives the RAI it will not assign a call to the gateway low on resources. 100% high low 0% GW sends RAI unavailable GW sends RAI available 2915_05_2001_c1 2001, Cisco Systems, Inc. All rights reserved. 63 RAI Configuration Example gw1(config-gateway)# resource threshold [all] [high %-value] [low %-value] default: both values are 90% E.g. resource threshold high 90 low 80 gw1(config-gateway)# resource threshold RAI RAI IP E.g. resource threshold high 90 low GW #show gateway Gateway 5300-GW is registered to Gatekeeper gk.mwest H323 resource thresholding is Enabled and Active H323 resource threshold values: DSP: Low threshold 80, High threshold 90 DS0: Low threshold 80, High threshold _05_2001_c1 2001, Cisco Systems, Inc. All rights reserved. 64

33 Call Admission Control to Assign Priority to GW GW priority selected on to prioritize GW selection Gatekeeper can select best available GW the first time to increase call completion rates and lower post-dial delay Pri Priority Pri Priority _05_2001_c1 2001, Cisco Systems, Inc. All rights reserved. 65 GW Priority Config Example Pri Priority Pri Priority 5 (config)# gatekeeper (config-gk)# zone local west-gk cisco.com (config-gk)# zone prefix west-gk gw-pri 10 gw1 (config-gk)# zone prefix west-gk gw-pri 10 gw2 default priority is 5 resultant Master list master list: gw1, gw list: pri 10 gw1; pri 5 gw list: pri 10 gw2; pri 5 gw1 2915_05_2001_c1 2001, Cisco Systems, Inc. All rights reserved. 66

34 Fault Tolerance Alternate Gateways register to the Static registration statement configured on GW Alt Lightweight RRQs sent from GW to as keepalive Alternate can be added Secondary registration statement configured with lower priority SJ POP 2 Zone If fails to send RCF back to GW, RRQ sent to Alternate GW Alt is geographic independent 2915_05_2001_c1 2001, Cisco Systems, Inc. All rights reserved. 67 GW Configuration for Alternate hostname US-GW1 interface Ethernet0/0 ip address h323-gateway voip interface h323-gateway voip id NA- ipaddr priority 1 h323-gateway voip id NA-ALT ipaddr priority 2 h323-gateway voip h323-id US-GW1 2915_05_2001_c1 2001, Cisco Systems, Inc. All rights reserved. 68

35 Fault Tolerance HSRP at the D D HSRP D Directory can use a backup D with HSRP Standard Cisco Hot Swap Routing Protocol Interval time can be configured (default = 10 sec) Convergence time Must be on same LAN HSRP only used on D, since zone HSRP cannot support GW registrations 2915_05_2001_c1 2001, Cisco Systems, Inc. All rights reserved. 69 Sample Configuration HSRP at the D D HSRP D ACTIE ROUTER interface FastEthernet0/0 ip address duplex auto speed auto standby 1 priority 110 standby 1 ip standby timers x x STANDBY ROUTER interface FastEthernet0/0 ip address duplex auto speed auto standby 1 priority 100 standby 1 ip _05_2001_c1 2001, Cisco Systems, Inc. All rights reserved. 70

36 Fault Tolerance Secondary Directory 1st LRQ D 1 HSRP D 2 2 nd LRQ Sec D Used to backup the HSRP D pair HSRP pair may take x seconds to complete failover (default = 10 sec) Calls not processed during this failover time Uses sequential LRQ from zone to enable secondary D Interval time between #1 and #2 is configurable in ms on zone Zone prefix table on Secondary configured identical to Primary D 2915_05_2001_c1 2001, Cisco Systems, Inc. All rights reserved. 71 Sample Configuration Secondary Directory 1st LRQ D HSRP D 2 2 nd LRQ Sec D Secondary D Special configuration required at Zone gatekeeper zone local netman.com zone remote D netman.com zone remote SecD netman.com zone prefix US- 408* zone prefix D * zone prefix SecD * lrq forward-queries Zone prefix table on AltD should match primary D 2915_05_2001_c1 2001, Cisco Systems, Inc. All rights reserved. 72 2

37 Fault Tolerance Clustering Gatekeepers can be configured as Cluster Cluster consists of up to 5 Gatekeepers Aimed at increasing CPS throughput and endpoints registered Allows individual s to collect group information such as Registrations, Bandwidth, and individual load Clustering benefits include redundancy, load-balancing/sharing Uses Gateway Uptime Protocol (GUP) External entity needs to only send LRQ to one member of cluster LRQ load shared between elements of the cluster 2915_05_2001_c1 2001, Cisco Systems, Inc. All rights reserved. 73 Redundancy (GUP, Message Flow) SFGW SJ1 SJ2 LAGW Comes On Line Opens TCP Listen Port Receives GRQ (w/gup Address) Opens GUP TCP Connection Comes On Line Opens TCP Listening Port Sends GRQ to All s in Local Cluster (w/gup Address) RRQ Comes On Line Registers Comes On Line Registers RRQ TCP Connect GUP Announcement GUP Announcement GUP Registration (LAGW) RCF(SJ1, SJ3, SJ4, SJ5) RCF(SJ2,SJ3, SJ4, SJ5) GUP Registration (SFGW) 2915_05_2001_c1 2001, Cisco Systems, Inc. All rights reserved. 74

38 Redundancy Endpoints are informed of the alternate Gatekeepers at Registration (RCF) in priority order Endpoints re-register with the highest priority alternate if primary fails 2915_05_2001_c1 2001, Cisco Systems, Inc. All rights reserved. 75 Redundancy (Message Flow) When One Becomes Unavailable SFGW SJ1 SJ2 RRQ RCF (Alt = SJ2, SJ3, SJ4, SJ5) LW RRQ Timeout RRQ RCF (Alt = SJ3,SJ4, SJ5) IRQ IRR (Active Call Info) 2915_05_2001_c1 2001, Cisco Systems, Inc. All rights reserved. 76

39 Load Balancing If a gets overloaded, it may ask an Endpoint to go to another in the local cluster The Endpoint gives the new a list of active calls via IRRs Does not balance loads equally but is a means to offload extra load Gatekeeper will send the list of best alternate in RCF/RRJ or ARJ to endpoints; this list changes real-time, depending on load conditions 2915_05_2001_c1 2001, Cisco Systems, Inc. All rights reserved. 77 Load Balance SFGW SJ1 GUP SJ2 SJGW SJ3 LAGW SDGW 2915_05_2001_c1 2001, Cisco Systems, Inc. All rights reserved. 78

40 Load Balance (Message Flow) SJ2 SJ3 SJGW GUP Announcement (Call Capacity = 100,000) GUP Announcement (Call Capacity = 0 ARQ ARJ (Alt=SJ3) RRQ RCF ARQ GUP Registration Indication ACF IRQ IRR(s) 2915_05_2001_c1 2001, Cisco Systems, Inc. All rights reserved. 79 US- Cluster Configuration gatekeeper zone local Zone1 cisco.com zone cluster local gozer Zone1 element Zone element Zone gatekeeper zone local Zone2 cisco.com zone cluster local gozer Zone2 element Zone element Zone gatekeeper zone local Zone3 cisco.com zone cluster local gozer Zone3 element Zone element Zone Zone SJ-GW _05_2001_c1 2001, Cisco Systems, Inc. All rights reserved. 80

41 Case Study: Adding in Redundancy 2915_05_2001_c1 2001, Cisco Systems, Inc. All rights reserved. 81 Customer A Design Needs Allow for POPs located in 5 cities Traffic needs 18,000 BHCA for each POP 5 CPS Calls Per Second for each POP Enable network to scale to allow addition of 5 new POPs in next 6 months Increase availability of core components Allow for billing of oip calls Allow for security 2915_05_2001_c1 2001, Cisco Systems, Inc. All rights reserved. 82

42 Case Study Adding Redundancy Clustering for US zone Alternate at Mexico and enezuela zone HSRP at D Alternate D D D Alt-D x 8 GW SJ US Zone x 8 GW PHX Local x 8 GW MIA Mexico Zone Local 2915_05_2001_c1 2001, Cisco Systems, Inc. All rights reserved. 83 x 8 GWs Alt- Mexico City x 8 GWs enezuela Zone Local Alt- City Billing in the H.323 Network 2915_05_2001_c1 2001, Cisco Systems, Inc. All rights reserved. 84

43 Call Legs Originating Switch Terminating Switch Ingress Egress Ingress Egress Call Legs Each Switch Has Bridged Together Two Call Legs, But the Call Legs Are of Local Significance 2915_05_2001_c1 2001, Cisco Systems, Inc. All rights reserved. 85 Call Leg Records Originating GW Ingress Call Leg oip Egress Call Leg Ingress Call Leg Terminating GW Egress Call Leg Each call leg generates start, update and stop records Each record has information specific to its call leg Each call leg reports the NTP time for when the SETUP (start) was issued, the call was CONNECTED (update) and the DISCONNECT (stop) was received The stop records have the information for billing The various call leg records for a single end-to-end call can be correlated using the conference ID 2915_05_2001_c1 2001, Cisco Systems, Inc. All rights reserved. 86

44 Billing Call Flow OGW AAA/RADIUS TGW Ingress Call Leg Answer Telephony Start Pots Billing Egress Call Leg Originate oip START Record Setup Time Stamp Ingress Call Leg Answer oip Egress Call leg Connect Originate Telephony STOP Update Record Connect Time Stamp Release Hangup STOP Record Disconnect Time Stamp 2915_05_2001_c1 2001, Cisco Systems, Inc. All rights reserved. 87 Which Call Leg Do We Bill On? Originating GW RADIUS Server Radius Server Terminating GW oip Ingress Call Leg 1 Egress Call Leg 2 Ingress Call Leg 3 4 Egress Call Leg Generally speaking, bill from call legs 2 or 3 Connect state is determined off of call leg 2 or 3 Call leg 1 will have excess time (user authentication, IR, radius authorization) 2915_05_2001_c1 2001, Cisco Systems, Inc. All rights reserved. 88

45 Timestamps Let s get in Sync.. Radius Server Ingress Call Leg oip Egress Call Leg Ingress Call Leg Egress Call Leg Each call leg reports the NTP time for when the SETUP was issued, the call was CONNECTED and the DISCONNECT was received No NTP = Invalid Timestamps *Jan 1 00:02:17.502: connect time : *16:02: PST Fri Dec *Jan 1 00:02:17.502: disconnect time : *16:02: PST Fri Dec _05_2001_c1 2001, Cisco Systems, Inc. All rights reserved. 89 Sample GW Configuration Originating GW RADIUS Server Terminating GW Ingress call leg 1 oip Egress call leg 2 Ingress call leg 3 Egress call leg OGW(config)# aaa new-model OGW(config)# aaa accounting connection h323 stop-only group radius OGW(config)# radius-server host auth-port 1645 acct-port 1646 OGW(config)# radius key test123 OGW(config)# radius-server vsa send accounting OGW(config)# gw-accounting h323 vsa OGW(config)# gw-accounting voip Don t forget to configure for NTP 2915_05_2001_c1 2001, Cisco Systems, Inc. All rights reserved. 90

46 Security Options 2915_05_2001_c1 2001, Cisco Systems, Inc. All rights reserved. 91 Security Options H.235 security Class of Restriction Access Control Lists 2915_05_2001_c1 2001, Cisco Systems, Inc. All rights reserved. 92

47 H.235 Security Can be configured for: GW registration only Per call only Both GW Registration Security Secure Registration from GWs validates source of RAS messages with AAA Server using Access Token (AT) Chap-like Access Token = GW password + H.323 ID Per Call Security For per call, authenticates users of gateways rather than the gateways themselves using ARQ/ACF 2 CPS limitation on to AAA interaction; may not be suitable for high call volumes, intra-domain 2915_05_2001_c1 2001, Cisco Systems, Inc. All rights reserved. 93 H.323 Security Options Registration Security -Formatted CHAP Challenge Radius Formulates CHAP Secret with Password in Database and H.323 ID to Compare with CHAP Challenge West Radius Accept/Reject RRQ Token Generation RCF WestGW Access Token Contains Timing Information and a Hash of the Following Gateway Password Gateway Alias H.323- ID 2915_05_2001_c1 2001, Cisco Systems, Inc. All rights reserved. 94

48 H.323 Security Configuration Registration Security H.323 id = US-GW1 Password = lab Challenge RRQ GW Radius Accept RCF gatekeeper zone local NA- netman.com security token required-for registration gw-type-prefix 1#* default-technology lrq forward-queries no shutdown radius-server host auth-port 1645 acct-port 1646 key lab radius-server retransmit 3 radius-server key cisco ntp master gateway security password lab level endpoint interface Ethernet0/0 h323-gateway voip h323-id US-GW1 ntp clock-period ntp server _05_2001_c1 2001, Cisco Systems, Inc. All rights reserved. 95 H.323 Security Options Per Call Security -formatted CHAP Challenge Radius alidation of token based On H.323 ID and password Radius Accept/Reject West ARQ w/token WestGW ACF w/token ACF w/token ARQ w/ Token Token Generation Setup w/ Token Access Token contains timing information and a hash of the following Gateway password Gateway Alias - H323-ID 2915_05_2001_c1 2001, Cisco Systems, Inc. All rights reserved. 96

49 H.323 Class of Restriction (COR) Determine inbound/outbound classification rules Administratively group dial-peers Apply to dial-peers to allow/disallow dial-peers from utilizing other groups of dial-peers COR specifies which incoming dial-peer can use which outgoing dial-peer to make a call Example A: Offnet callers cannot dial anywhere but to xxxx (PBX) Example B: FXS phones A and B can only call # s and each other, but FXS phone C and D can call anywhere 2915_05_2001_c1 2001, Cisco Systems, Inc. All rights reserved. 97 COR Sample Configuration OrigGW TermGW oip EXAMPLE: Configure TermGW to block calls originating from destined for Hostname TermGW port 1/0/0 dial-peer voice 5 pots dial-peer cor custom corlist incoming list1 name 408_call destination-pattern name 415_call port 1/0/0 dial-peer cor list list1 dial-peer voice 4voip member 408_call corlist outgoing list2 destination-pattern dial-peer cor list list2 session target ras member 415_call gateway 2915_05_2001_c1 2001, Cisco Systems, Inc. All rights reserved. 98

50 Case Study # 1: Adding in the Billing Component and Security 2915_05_2001_c1 2001, Cisco Systems, Inc. All rights reserved. 99 Customer A Design Needs Allow for POPs located in 5 cities Traffic needs 18,000 BHCA for each POP 5 CPS Calls Per Second for each POP Enable network to scale to allow addition of 5 new POPs in next 6 months Increase availability of core components Allow for billing of oip calls Allow for security 2915_05_2001_c1 2001, Cisco Systems, Inc. All rights reserved. 100

51 Case Study Adding Redundancy Add RADIUS/AAA/billing application Add H.235 security H.235 Token D Radius D Alt-D CDR x 8 GW SJ US Zone x 8 GW PHX Local x 8 GW MIA CDR Mexico Zone x 8 GWs Local Mexico City x 8 GWs enezuela Zone Local 2915_05_2001_c1 2001, Cisco Systems, Inc. All rights reserved. 101 Alt- Alt- City Expanding the Coverage Area 2915_05_2001_c1 2001, Cisco Systems, Inc. All rights reserved. 102

52 Increasing Traffic with Partnerships North America ITSP China ITSP I service North America.. I service China Partnerships made between both TDM based and IP based telephony carriers to increase traffic volume, subscriber base, and revenue generation. Minimizes investment. For IP interconnections, Cisco provides high performance call routing using standards-based methods (e.g. OSP and H.323v2 LRQ) and also flexibly accommodates non-standards based networks 2915_05_2001_c1 2001, Cisco Systems, Inc. All rights reserved. 103 Interconnection with Other Carriers (TDM and IP) Application Server ASP BILL D Transit GW BILL AAA ITSP A Settlement SS7 TDM Carrier Analog/Digital TDM Carrier BILL D BILL AAA ITSP B (D Peer) BILL OSP Clearinghouse Clarent Claren ITSP B (Clarent) Clarent Command Center Clarent GWs 2915_05_2001_c1 2001, Cisco Systems, Inc. All rights reserved. 104 BILL

53 Interconnecting to TDM-Based Carriers 2915_05_2001_c1 2001, Cisco Systems, Inc. All rights reserved. 105 Solution Components Diagram Description Details Purpose Cisco SC2200 Host Signaling Controller AKA: Cisco SC2200 Host Based on Sun Netra 1120s, 1400s and 1800s Supports Over 60 Different ISUP ariants Into Q.931+ over IP Cisco SC2200 Node SLT Signaling Link Terminal AKA: SLT Based On 2611 with Special Cisco IOS Image for the SLT Supports Terminating A or F Links and Encapsulating MTP 3 Layers and Above Over IP; Provides Muxing F Links Off E1s AS5x00 Cisco oice Gateway Based On AS5300, AS5300 H.323 oice-over-ip Media Gateway Responsible for oice Packetization, H.323 Signaling 2915_05_2001_c1 2001, Cisco Systems, Inc. All rights reserved. 106

54 SS7 POPs Cisco SC2200 Node (SLT + SC2200) STP SS7 DA A MIND/CTI RADIUS D2 2 MIND/CTI RADIUS TDM Trunk Q.931+/IP Wholesale Network ITSP-A TDM Non-SS7 Cisco AS5300 Cisco SC2200 Node Added for SS7 Interconnect; When a New SS7 POP Is Added, No Additional Changes to H.323 Network Needed 2915_05_2001_c1 2001, Cisco Systems, Inc. All rights reserved. 107 Non-SS7 POPs TDM Non-SS7 DA A MIND/CTI RADIUS D2 2 MIND/CTI RADIUS oice Network Trunks Cisco GWs Specific Signaling T1-CAS, PRI, E1/R2 etc Wholesale Network ITSP-A TDM Non-SS7 Non-SS7-based POPs Receive Signaling from TDM Network On Same Interface that Supports Bearer Traffic; Use Cisco GW that Supports Signaling Type Offered By TDM Interconnect 2915_05_2001_c1 2001, Cisco Systems, Inc. All rights reserved. 108

55 Interconnecting to IP-Based Carriers 2915_05_2001_c1 2001, Cisco Systems, Inc. All rights reserved. 109 Interconnecting to another IP based carrier OSP Clearinghouse ITSP #2 OSP Server Mediation ITSP #3 D LRQ LRQ D ITSP #1 D Radius Local Local Local 2915_05_2001_c1 2001, Cisco Systems, Inc. All rights reserved. 110

56 H.323 LRQ Forwarding ITSP #2 D LRQ forward D ITSP #1 Mediation Radius RADIUS CDR Radius Optional Billing App Server LRQ from Directory Gatekeeper Trusted Peer relationship needed between carriers Call Routing Routes queried by LRQ forwarding on each D Billing Billing settled by exchange of CDRs from dedicated RADIUS Server Optional mediation server Security H.235 Token Security, Access Control Lists, Class of Restriction 2915_05_2001_c1 2001, Cisco Systems, Inc. All rights reserved. 111 Open Settlements Protocol OSP Clearinghouse D Mediation ITSP #2 Radius Radius OSP Server Radius D ITSP #3 D Open Settlements Protocol (OSP) - server used in clearinghouse for interdomain call routing, billing, and security Call Routing - Routes configured centrally on OSP Server Billing - Billing settled centrally on OSP Server Security - Token based Each GW in wholesale network need to have OSP client. Transit GW needed to integrate existing D based network 2915_05_2001_c1 2001, Cisco Systems, Inc. All rights reserved. 112

57 OSP Configuration Example D ITSP #2 OSP Clearinghouse ITSP #2 Mediation 1 2 OSP Server ITSP #3 GW1 hostname GW1 crypto ca identity OSPserv enrcrypto ca identity OSP_clear enrollment url crl optional crypto ca certificate chain OSP_clear certificate F A D0609 settlement 0 type osp url encryption des-cbc-sha dial-peer voice 1 voip destination-pattern 1* session target ras Preference 1 dial-peer voice 2 voip destination-pattern 61* session target settlement:0 Preference _05_2001_c1 2001, Cisco Systems, Inc. All rights reserved. 113 OSP Call Flow GW1 to GW2 GW1 ARQ 1 LRQ D1 Radius1 OSP Server Radius2 GW2 ARJ LRJ Auth Request Auth Response (Term GW address + token) Setup (w/ token) Connect Token auth Start Accounting Stop Accounting Start Accounting hangup Stop Accounting Usage Indication Usage Confirmation Usage Indication Usage Confirmation 2915_05_2001_c1 2001, Cisco Systems, Inc. All rights reserved. 114

58 OSP Based Interconnect directory- HSRP LRJ LRQ Auth Request OSP AuthRsp (Rem_GW & token) West Billing <usage> AAA Billing <usage> ARQ ARJ Billing West Zone SETUP w/ Token Alerting/Connect/etc. Disconnect 2915_05_2001_c1 2001, Cisco Systems, Inc. All rights reserved. 115 Antarctica Adding the Transit GW for OSP Interconnect MIND/CTI RADIUS D1 OSP A IP DA 1 2 Wholesale Network ITSP-A Transit GW Used when ITSP-A is OSP-based, Wholesaler/Partner SP is D RAS-based Create a Transit Zone with Transit GWs Only one GW registers to OSP server, dedicated to OSP Only OSP-based calls go through the Transit GW No additional overhead (OSP) on other GWs required 2915_05_2001_c1 2001, Cisco Systems, Inc. All rights reserved. 116

59 Interconnecting to Non-Cisco-Based Carriers 2915_05_2001_c1 2001, Cisco Systems, Inc. All rights reserved. 117 Adding the Transit GW for Clarent Interconnect A IP DA POP 1 D1 2 Wholesale Network MIND/CTI RADIUS Clarent Gatekeeper Clarent Command Center Clarent Based ITSP-A Clarent GW Transit GW A single GW can only register to one Clarent Command Center does not support H.323, only proprietary Clarent protocol Clarent Gatekeeper supports H.323 on one side, proprietary Clarent on other side Transit zone created with Transit GWs, to allow Clarent Interconnect Transit GW sends SETUP message to Clarent Command Center, since it uses gatekeeper routed call signaling method 2915_05_2001_c1 2001, Cisco Systems, Inc. All rights reserved. 118

60 Other Services: Card Services 2915_05_2001_c1 2001, Cisco Systems, Inc. All rights reserved. 119 Distributed Phone-to-Phone Calling Card Solution Optional TFTP Server for Centralized Script and Prompt Storage TFTP BILL AAA Server Hosting Partner s Pre-paid Calling Application RTSP RTSP Server for Real Time Audio Streaming (Optional) Calling Party OGW TGW Called Party Originating GW supports IR capabilities Provides user authentication before entering network Processing associated with IR functions pushed to the edge Customizable scripts using TCL Multi-language support Individual service branding to simultaneously host multiple retail applications on a single network AAA server Provides real-time billing for pre-paid applications RTSP server Provides audio announcement streaming TFTP server Stores IR scripts and prompts for centralized distribution 2915_05_2001_c1 2001, Cisco Systems, Inc. All rights reserved. 120

61 Network Management Solutions 2915_05_2001_c1 2001, Cisco Systems, Inc. All rights reserved. 121 Network Management Tools CiscoWorks 2000 Cisco oice Manager SNMP element management Performance reporting with 3rd-party application CiscoWorks 2000 Internet Performance Monitor Real-time network quality-of-service monitoring IOS Service Assurance Agent CiscoWorks 2000 Remote Manager Essential IOS upgrade and release management Cisco Info Center SNMP trap correlation Standards-based SNMP Applications HP Openiew 2915_05_2001_c1 2001, Cisco Systems, Inc. All rights reserved. 122

62 Network Management Tools For more info see additional backup NMS slides Also, visit the World of Solutions for more information 2915_05_2001_c1 2001, Cisco Systems, Inc. All rights reserved. 123 What Next? 2915_05_2001_c1 2001, Cisco Systems, Inc. All rights reserved. 124

63 TMP on TMP interface on for enhanced services Northbound interface extends Cisco s Open Packet Telephony architecture philosophy to and D platforms Allows more flexibility and quicker development of new services using third party partners opposed to closed systems Can customize specific RAS messages to trigger up to the TMP server for enhanced service logic supported on various platforms depending upon desired performance 3660 (IP/H.323 feature set) 7200 (Enterprise feature set) Set Triggers TMP TMP For Enhanced Services 2915_05_2001_c1 2001, Cisco Systems, Inc. All rights reserved. 125 H.323 RAS Messages IP Questions 2915_05_2001_c1 2001, Cisco Systems, Inc. All rights reserved. 126

64 Deploying Large-Scale H.323 oip SP Networks Session 2915_05_2001_c1 2001, Cisco Systems, Inc. All rights reserved. 127 Please Complete Your Evaluation Form Session 2915_05_2001_c1 2001, Cisco Systems, Inc. All rights reserved. 128

65 2915_05_2001_c1 2001, Cisco Systems, Inc. All rights reserved. 129 BACKUP 2915_05_2001_c1 2001, Cisco Systems, Inc. All rights reserved. 130

66 CiscoWorks Cisco oice Manager v2.02 Network Performance Reporting Stand alone product not suited to service provider scaling needs Requires integration with third party partner for effective distributed reporting solution CM polls GWs for call history statistics and provides an open interface for third party management systems to gather and correlate data CM provides a clean, well-formatted oip call history file to third party applications to obscure Cisco platform specifics Reporting data is useful for troubleshooting and traffic forecasting Example reports include answer seizure rate, call success rate, call volumes, and disconnect reasons Models hierarchical design for scalability; CM resources may be inserted on demand as capacity and network coverage area grows 2915_05_2001_c1 2001, Cisco Systems, Inc. All rights reserved. 131 Cisco oice Manager v2.02 (Cont.) Element management Supports basic oip configuration parameters (e.g. interface signaling types, dial-peers, H.323 registrations) Simple dial plan provisioning within a local region only Supports SNMP MIB management of any SNMP capable device SNMP trap viewing and forwarding Can receive and collect traps from GWs via SNMP Traps may be forwarded onto Cisco Info Center for event correlation 2915_05_2001_c1 2001, Cisco Systems, Inc. All rights reserved. 132

67 NMS Architecture Using CM Regional/Centralized Reports Third Party Reporting Server Regional Reports CM Third Party Reporting Server CM Regional Reports CM Third Party Reporting Server Abstracts Platform Specifics from Upper Layers Regional Reports Third Party Reporting Server Polled Open CM Northbound Interface POP SNMP SNMP POP SNMP POP SNMP POP 2915_05_2001_c1 2001, Cisco Systems, Inc. All rights reserved. 133 Cisco Info Center Fault management and event correlation Optimizes fault management by reducing alarm information overload through de-duplication and fault correlation to enable faster problem solving and better operations scaling Flexibly manages and monitors faults and in multi-vendor, multitechnology, and multiservice environments Correlates faults received from multiple sources (e.g., SNMP traps, syslog events) Supports distributed operational environments to reduce the number of NOCs, provide centralized and regional monitoring, and eliminate costly, inefficient console farms of scrolling alarms Can translate faults and events into actions to quickly resolve problems (e.g. paging capability, issue a trouble ticket, send alarms for critical events) Distributed and redundant architecture for scaling and reliability 2915_05_2001_c1 2001, Cisco Systems, Inc. All rights reserved. 134

68 CIC Deployment Architecture Regional/Centralized Fault Monitoring Central Info Server Back up Info Server Gatherer Gatherer Gatherer Regional Fault Monitoring Regional Server/ Mediator Regional Fault Monitoring Regional Server/ Mediator Regional Fault Monitoring Regional Server/ Mediator POP SNMP syslog SNMP syslog POP SNMP syslog POP 2915_05_2001_c1 2001, Cisco Systems, Inc. All rights reserved. 135 Cisco Internet Performance Manager (IPM) Provides real-time and historical network performance reports on oip characteristics such as latency, jitter, packet errors, and packet loss for all available IP paths Measures network performance on a hop-by-hop basis to pinpoint latency and jitter causes and reduce problem isolation and resolution time Generates traps based on response time thresholds to provide real-time alerting of potential problems Works with Cisco IOS Service Assurance Agent (SAA) to support service level measurement 2915_05_2001_c1 2001, Cisco Systems, Inc. All rights reserved. 136