1 / 53

Communication Manager R5.2

Communication Manager R5.2. Jan Jiricka and Mike Armstrong. CM R5.2 Increased Capacities and New Features. Jan Jiricka. CM 5.2 - Agenda. Increased endpoint and trunking capacities Upgrades and migrations New features overview Secure Access Link. CM 5.2 - Capacity Changes.

khanh
Download Presentation

Communication Manager R5.2

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Communication Manager R5.2 Jan Jiricka and Mike Armstrong

  2. CM R5.2 Increased Capacities and New Features Jan Jiricka

  3. CM 5.2 - Agenda • Increased endpoint and trunking capacities • Upgrades and migrations • New features overview • Secure Access Link

  4. CM 5.2 - Capacity Changes

  5. CM 5.2 - Upgrades • Upgrade Paths • Release 2.x, 3.x, 4.x, 5.x  5.2 • 1.x  5.2 not supported; no 1.x platforms are supported in CM 5.2 • Upgrade sequence • LSPs, GWs, TN Packs, ESSs, Primary Servers, Standalone SES • Server/gateway compatibility • Gateway and media module firmware backward compatible with all CM 5.2 releases back N-2 • Reference: CM 5.2 Software Firmware Compatibility Matrix

  6. CM 5.2 - Survivable Servers support

  7. CM 5.2 - Error Resistant Downloads • Basic overview • Modify Manage Software web page to support block size file copying and use secure file copy protocols • Progress indicator: display of elapsed time and total byte count • Customer value • Secure downloads (https, SCP) • Block size copy only works for http/https • Support setting port for proxy sever on firewall • Resumption of downloads from point of failure

  8. CM 5.2 - Error Resistant Downloads

  9. SES 5.2 – Servers & Upgrades • Standalone SES • S8500B/C (1/3GB), S8510 (4GB) • Co-resident with CM 5.2 • S8300C (1GB), S8300D (4GB) • Upgrade Paths (Direct) • SES 3.1.1 & later SES 5.2 (Combo, Home, Edge) • CM/SES 5.0  CM/SES 5.2 (Combo, Home) • Upgrade Paths (Step) • SES 3.1 & earlier  SES 3.1.1  SES 5.2

  10. SES 5.2 Supported Migrations • Conversions • Combo SES 5.2 (S8500)  Edge SES 5.2 (S8500) AND two or more Home SES 5.2 (S85xx/S8300C/D) • Combo CM/SES 5.2 (S8300C/D)  Edge SES 5.2 (S8500C) AND CM/SES Home SES 5.2 (S8300C/D) AND one or more Home SES 5.2 (S85xx/S8300C/D) • Platform • Combo/Home/Edge SES 5.2 (S8500B/C)  Combo/Home/Edge SES 5.2 (S8510)

  11. SES 5.2 - Supported Migrations • Mixed releases: • Edge can be at SES 5.2 and Home can be at an earlier release (5.0) • Edge can be at SES 5.2 and CM/SES Home can be at an earlier release (back to 5.0)

  12. The Features Begin

  13. CM 5.2 – New Features • Improved Port Network Recovery from Control Network Outages • Maintain CLAN TCP Sockets during PN restarts • Extension to Cellular enhancements • Enhanced System Directory Completion • Team Button Enhancements and Call Rerouting • Log & Lock Features • Simplify Feature Handling

  14. Improved PN Recovery Timeline of PN Recovery Escalation in CM 5.2 x TCP/IP socket between server & IPSI Network Outage Time line MIN SST 3 sec Max SST 15 sec 60 sec Max = 120sec t=0 outage begins A B C D Maintenance suspended Data is buffered in both up/down directions SST = 3-15 seconds Outage ends:Transient calls complete (New)PktInt Warm Interrupt Connections including TCP/IP preserved Stable calls survive IP endpoints don’t lose registration Outage ends:Endpoints are back in service (New) PN Reset Delay Timer 60-120 seconds Stable calls survive Outage ends:Non-TTS IP endpoints re-register Outage > PN Reset Delay Timer Recovery escalates to PN Cold Reset -TN boards reset and calls using PN drop (New) IPSI can Failover to ESS at t ≥ 2 minutes

  15. Maintain CLAN TCP Sockets • Problem Definition: • Current Communication Manager design depends on reliable delivery of control information and socket creation between CM-TS Server and IP connected port networks. • Control flow errors resetting of CLAN socket table mass re-registration of IP clients (stations, gateways, and adjunct application servers). • Solution: • “Session layer” protocol added in the header of the RSL/RSCL messages : • sequence number with each packet • simple message set for recovery • retransmission of missing packets. • This “session layer” protocol is operated between the GIP process on CM-TS Server and the target CLAN module. • Signaling sockets will only be closed if there is an unrecoverable problem with the signaling flow to a given endpoint.

  16. Extension to Cellular enhancements 4 new features, 1 new Application Type: • Administrable EC500 state • Conditional Call Extend • Shared Voice Connections • Shared Mappings • SPFMC Off-PBX Application Type

  17. Enhanced System Directory • Added support for 96xx phones with WML browser capability to do an LDAP directory search • Administration added to Communication Manager System Management Interface Web pages • Unicode support added • Supports the Name1/Name2 design • Uses the Avaya Site Administration tool for LDAP synchronization

  18. Enhanced System Directory • Provides customers with a convenient, fast and accurate way to dial any person in the enterprise or externally thus eliminating the need to look up and then dial numbers. • Customers may search on last, first, both names in any language that their phone supports. • Eliminates the need for a directory search from a computer.

  19. Team Button, Call Rerouting • Team Button enhancements • General • Visual and audible indication • Speed dialing • Pick up • LNCC enhancements • Override SAC and CFWD for dialing and priority call

  20. Log & Lock Features • Call Log Enhancements • Hot Desking Enhancement Station Lock • Enhancements for Station Lock / TOD Station Lock • Locking of(more)switchbased capabilities • Locking ofphonebased capabilities

  21. Log & Lock feature Station Lock – Does it Really “Lock”? • Restrictions are defined by Station Lock COR (e.g. 10) • Not all features and capabilities are locked change cor 10 Page 1 of 23 CLASS OF RESTRICTION COR Number: 10 COR Description: FRL: 0 APLT? y Can Be Service Observed? n Calling Party Restriction: outward Can Be A Service Observer? n Called Party Restriction: inward Partitioned Group Number: 1 Forced Entry of Account Codes? N ... “Locked” Bridged Appearances, EC500, Call Log, Avaya Menu, etc. Not locked

  22. Log & Lock feature Phone Based Capabilities Locked by HDE • Contacts • Avaya Menu • Call Log • Redial Button • USB Access Applies only to 96xx H.323 phones • Available with firmware S3.0 • Not available with soft phones

  23. Simplify Feature Handling • Features transferred from “Special Applications” to standard features: • SA 8518 Automatic Callback With Called Party Queuing • SA 8622 Enhanced Call Pickup Alerting • SA 8623 Chained Call Forwarding • SA 8957 PIN Checking For Private Calls • SA 9011 Edit Dialing • Make Standard Phone Features Easier To Use(User Guidance Display) • Enhanced Redirection Notification

  24. Secure Access Link SAL: Outbound and Customer-Controlled Access Model, Strong Authentication of Users, Business Partner Support Advanced Offers with VPN and SIG (IPSS) IP-Based Access with VPN and SSG (SAC) EXPERT and Service Tools Access via Modem Modem-based Access

  25. SAL – Secure Enhanced Alarming

  26. SAL – Remote Access

  27. SAL Value • Greater level of security • Egress communication model • Increased customer control over network access • Customer-controlled authentication support • Detailed logging for accountability • Centralized management • Simplified firewall rule sets • Modem dependency elimination • Increased availability and reliability • Increased secure automated tool support • Additional service support options • Co-managed- Avaya, partners, andsystem integrators

  28. Thank You

  29. CM R5.2 Hardware Mike Armstrong

  30. S8300 Media Server – Rev D • Technical refresh • dual core Intel processor with 8GB DRAM • Gigabit NIC (used with G450 only) • SSD now 8GB; HDD now 160GB • No increase in existing capacities • All H.248 Media Gateways supported • All migration paths supported • Requires minimum CM R5.2

  31. S8400 Enterprise Survivable Server • Embedded solution • no external server required • S8400A and B both supported • Supports a single Port Network • G600, CMC1 or G650 cabinets only • Server adjuncts supported, e.g. CDR • Requires minimum CM R5.2

  32. WAN S8400 ESS in a Multi-Site Network S8400 ESS supports up to 5 remote H.248 gateways Single Port Network with ESS S8400 ESS supports up to 900 H.323 endpoints Single Port Network without ESS Main Server, if present, has to be S85xx or S87xx Single Port Network with ESS

  33. S8400 ESS Summary • Requires CM R5.2 minimum • both S8400A and B supported • Only supports the Port Network in which it is installed • will also support up to 5 x H.248 Media gateways • will also support adjuncts • CSS is not supported • If Main Server is present (either S85xx or S87xx) then IPSI (not SIPI) is required in each PN

  34. S87xx Processor Ethernet • Optimised configuration for large, IP-centric networks • H.248 Gateways, IP Phones and SIP Trunks register directly with the Media Server • largely removes the need for centralised G650 gateways and multiple CLANs • No loss in functionality • No change in existing capacities • Smaller, greener footprint • Clean, competitive, cost effective design

  35. S87xx PE Design TODAY MAY 2009 S8510 LSP S8510 LSP S8730 S8730 G450 G650 No extra hardware required to support remote branch gateways and phones H.248 H.323 Remote branch gateways and phones Remote branch gateways and phones

  36. S87xx PE Internal Case Study 84% footprint reduction 46% power reduction 43% heat reduction All figures internal estimates

  37. S87xx PE Overview • Supported on S8720 and S8730 only • S8700 and S8710 will both require hardware upgrade to S8730 in order to support this feature • S8710 supports R5.2, but not PE • Any mix of PE/PN connectivity is supported • PE without PN, PE with PN, PN without PE • ESS requires PE to register with the Main server • Mix of CLAN and PE does not increase existing capacity • ESS platforms may also employ duplex PE

  38. S87xx PE and Adjuncts • Some adjuncts still require CLAN connectivity • AES, IQ, CMS • resolution expected within next 12 months • Other adjuncts require careful consideration • CDR works best if connected through RSP • MM, MX and VP are currently in testing • Design guidelines will be available shortly

  39. S87xx PE Server Interchange • The process of changing from the active to the standby server • With CLAN connected devices • stable IP calls will be maintained • some signaling messages may be lost • With PE connected devices • stable IP calls will be maintained • most signaling messages will be lost • total recovery period following the interchange depends on the type of connected device

  40. S87xx PE Server Interchange • For optimal results, IP endpoints need to support • Time-To-Service (TTS) • incoming TCP connection from active server • gratuitous ARP

  41. S87xx PE Fast Server Interchange • Fast server interchange requires • latest firmware on H.248 Media Gateways and 96xx phones • Impact of older/less sophisticated endpoints on overall recovery time may be significant PE failure Begin interchange Optimal recovery Detect Failure Initiate Interchange Normal Operation Warm Start Re-connect Other Recovery 3 second ping 6-9 seconds 4 seconds arbiter 3 seconds goal 0-3 seconds 13-19 seconds or minutes TIME (s) Timings indicate best case scenario

  42. S87xx PE Design Issues • Large, H.248-based networks can significantly reduce overall processing performance • BHCC capacity may halve when compared with a similar PN-based solution • Networks with only IP trunks and endpoints will not see a reduction in performance • Adding H.248 gateways to a PN-based configuration will see a reduction in performance • no difference whether the MG is connected via CLAN or PE

  43. S87xx PE Design Summary • Be aware that some adjuncts still require CLAN connectivity • Be aware that device recovery following a server interchange is largely dependant on the type of phone • Be aware that large, H.248-based networks can significantly reduce overall processing performance • Full documentation will be available shortly

  44. G430 Media Gateway • Modular, H.248 gateway for Enterprise customers • Up to 150 IP endpoints and 80 agents supported • Up to 7 x E1 trunks • Delivers same enhanced L2/3 functionality as existing G450 • SLS, LSP, IA770 and co-res SES all supported

  45. G430 Base Unit • 1.5µ base unit supports three slots • accepts most G-series Media Modules • MM3xx and MM760 not supported • accepts only S8300 rev C/D • Single 175W PSU with three fans • 3½mm audio jack for external MoH source • 256MB SDRAM expandable to 512MB

  46. G430 Expansion Modules • 1.5µ Expansion Module (EM200) provides additional two slots • four extra slots are supported, i.e. two EM200 units, providing seven slots in total • Expansion modules are hot swappable and connect via 25cm backplane cables

  47. G430 Media Gateway • Base unit supports 20 VoIP channels • Single expansion slot accepts 10, 20 or 80 additional channels • maximum 100 channels per gateway • G.711, G.729a and G.726 supported • Codec and SRTP encryption have no impact on call processing performance • same as G450

  48. Media Gateway Enhancements • G430 and G450 only • both gateways support 256, G.711-based announcement and MoH files in NVRAM totalling 45 minutes • this can be increased to 1,024 files totalling 4 hours • requires system memory upgrade to 512MB and new 1GB Compact Flash upgrade kit • supported through VAL Manager • All Media Gateways • VPN License no longer required

  49. H.248 Media Gateway Summary

  50. Support Announcements • CM/CC/SES/AIM R3.x are no longer officially supported • consider migrating to R5.x • CM/CC/SES/AIM R4.x are no longer available • system additions are still supported • consider migrating to R5.x

More Related