Nortel CS1000 Branch Office Solutions Asko Hotakainen Senior Sales Engineer

Agenda Introduction Call Server and Media Gateways High Availability N-Way Geographic Redundancy (MG1000E) Branch Office (MG1000B) IP Phones Building Resilient Networks to support CS1000

Introduction The goal of building a resilient CS1000 branch office solution is to minimize downtime and impact of software and hardware failures to the end-user Resiliency comes with a price - in many cases – possibly requiring extra / duplication of hardware Be aware of how applications (e.g. CallPilot, CCMS, MLS, ICD, ICB etc.) can be connected and integrated Remember that the CS1000 is inherently reliable

Branch Office considerations What are the needs at the branch office Which kind of extensions? Analog, digital, IP, local mobility (DECT, WLAN..) Is there an need to host applications? Contact Center, IVR, etc Local PSTN breakout? To help traffic engineering, numberingplan issues and survivability The answers to these questions will mainly dictate the solution.

What are the Options for a remote site Call Server (traditional PBX networking) MG1000E No survivability SMG1000E Survivable limited application support MG1000B SW compatibility with core, limited configuration integration, limited scalability max 400 users SRG Survivable (up to 80 IP users) no configuration integration

PBX Networking Site 2 Site 1 PSTN PSTN QOS IP Network Call Server SS SS MG Scenario 1 Campus Redundancy Applies to a CS1000E system All components in the system communicate to a single IP address In case of a switchover, the processor taking control also assumes this IP address Both processors MUST be on the same subnet Physical separation of redundant call server is over a layer 2 network This allows the subnet to be extended to the locations of both processors This can be accomplished by setting up a VLAN through the layer 3 infrastructure Seamless switchover No impact to active calls IP sets do not need to re-register Applications are not affected by the switchover No additional management Data on active is automatically duplicated on the inactive processor Switchover can be configured to occur daily Supports Branch Office, SRG and remote media gateways Protects users at these locations from IP network failure Branch and SRG are managed independently MG PSTN PSTN QOS IP Network

Core site(s) with High Availability Secondary Data Center Primary Data Center Synchronization and Graceful switchover Call Server Active Core Call Server Inactive Core Layer 2 Connection Same ELAN Subnet Could be via VLAN through routers that support this. SS SS MG Scenario 1 Campus Redundancy Applies to a CS1000E system All components in the system communicate to a single IP address In case of a switchover, the processor taking control also assumes this IP address Both processors MUST be on the same subnet Physical separation of redundant call server is over a layer 2 network This allows the subnet to be extended to the locations of both processors This can be accomplished by setting up a VLAN through the layer 3 infrastructure Seamless switchover No impact to active calls IP sets do not need to re-register Applications are not affected by the switchover No additional management Data on active is automatically duplicated on the inactive processor Switchover can be configured to occur daily Supports Branch Office, SRG and remote media gateways Protects users at these locations from IP network failure Branch and SRG are managed independently MG PSTN PSTN QOS IP Network

Branch Solution Options Secondary Data Center Primary Data Center Synchronization and Graceful switchover Call Server Active Core Call Server Inactive Core Layer 2 Connection Same ELAN Subnet Could be via VLAN through routers that support this. SS SS MG MG PSTN PSTN QOS IP Network Branch 3 Branch 1 Branch 2 MG SS IP Sets PSTN PSTN SS = Signaling Server MG = Media Gateway TDM Sets

MG1000E with Survivable Media Gateways N-Way Replication system provides up to 2 levels of geographic redundancy: Primary CS failure - each configured Alternate CS 1 provides service to all the resources in its responsibility (to the equipment on which it is configured as second choice) WAN failure - each configured Alternate CS 2 provides service only to the resources in its own area (to the equipment on which it is configured as third choice) Primary Call Server can replicate its database to 50 Call Servers (Can be PIV Call Server pair or CPPM CS (SA or HA)) No need to manage Branch systems Configured centrally, with automatic database replication Automatic failover and failback of Survivable Media Gateways Redundancy provided applies to both IP & TDM resources Potentially support ALL IP and TDM users in Survivable Mode

MG1000B Standalone ‘traditional’ Branch offering for up to 400 IP phones Supports TDM sets and Trunks as well as some applications also (see Compatibility NTP for more details) Consists of 1 Media Gateway (Chassis or Cabinet) plus 1 Media Gateway Expander (Chassis) License limit to operate in Survivable Mode for 90 Days TM3.1 can manage Moves, Adds and Changes for Branch IP users from Main Site

SMG1000E versus MG1000B MG1000B SMG1000E Main Office can be any CS1000 system. Requires a Branch system and signaling server at the remote site to provide survivability. Main Office must be a CS1000E system with distributed Media Gateways. Requires an alternate processor and signaling server at the remote site to provide survivability. Enables IP Survivability only Enables both IP an TDM Survivability Uses BUID for IP survivability Uses NUID for IP survivability Limited to 400 IP users and 8 card slots for trunking DSPs, TDM sets. No limit. Uses same TDM resources as main. Can support all IP sets of main. No permanent IP users allowed on the Branch. No permanent IP or TDM users allowed on the alternate processor of a Survivable Media Gateway. 90 day license period for all Branch IP Users. Package 405 is required, and will limit use of IP sets and TDM sets on a Media Gateway to 90 days when in survivable mode.

Geographic Redundancy Positioning Recommendations Where possible, we position “GR – Survivable Media Gateway” for customers who want a survivable system and/or survivable gateways, i.e. Branch office customers We assume this solution will be most popular with our branch customers due to new enhancements, i.e. database synchronization, no duplicate configuration, both TDM & IP survivability, Local Music/RAN, etc. Position “GR – Survivable Media Gateway” if: Customer does not require more than 50 Survivable Gateways per Main office Customer meets WAN RTD & packet loss requirements

GR Positioning Recommendations Continued In cases where “GR- Survivable Media Gateway” is not appropriate, we position either “GR- Controlled Load sharing” or “MG 1000B” solution If customers want a branch office solution with 400 IP users or less and within 8 card slots, and the limitations above preclude “GR – Survivable Media Gateway”, position MG 1000B. For smaller branch offices below 50 users, we position SRG We position “GR – Controlled Load sharing” if: Customer wants full IP Peer systems backing each other up Customer wants back-up systems to be flexible: Mixture of Temporary IP users and Permanent IP or TDM users. Different database/configuration allowed on back-up systems Customer is only interested in IP survivability Customer views the limitations with “GR Survivable Media Gateway” in previous slide unacceptable. Customer wants large branch office in excess of 400 IP users, or with more than 8 card slots, and limitations with “GR – Survivable Media Gateway” are unacceptable.

MG 1000B Resiliency H.323/SIP WAN Gateway in remote branch offices, enables local PSTN access Users configured, and managed centrally from Main site Survivable in the event of a WAN failure Main Site Large Campus Site Branch Office Rest of World Campus Media Gateways MG 1000B Call Server PSTN LAN Survivability Sets Register to local gateway in the case of a WAN failure LAN IP WAN Normally Sets Configured and Managed from Main Site NRS MG1000B Call Server Does not need to reboot to take control of IP phones in local Mode – IP phones rehome and hence fallback is faster!

Geographic Redundancy – Survivable Media Gateways Primary Data Center Redundant Call Processor Secondary Data Center Synchronization and Graceful switchover Alternate Call Processor PSTN PSTN QOS IP Network Database Replication Branch 3 SS Branch 1 Can mix CPPIV and CPPM as processor types in single system… SS Branch 2 Survivable MG Includes Alternate Call Server Branch Office IP Sets PSTN Survivable MG (no Call Server) TDM Sets PSTN PSTN

Geographic Redundancy – Survivable Media Gateways Primary Data Center Redundant Call Processor Secondary Data Center Synchronization and Graceful switchover Alternate Call Processor Primary Failure – Media Gateways register to an alternate processor PSTN PSTN QOS IP Network Branch 3 SS Branch 1 Branch 2 Survivable MG Includes Alternate Call Server IP Sets PSTN Survivable MG (no Call Server) MG SS = Signaling Server MG = Media Gateway TDM Sets PSTN

Geographic Redundancy – Survivable Media Gateways Primary Data Center Redundant Call Processor Secondary Data Center Synchronization and Graceful switchover Alternate Call Processor IP Network Failure – Media Gateways register to a local processor PSTN PSTN QOS IP Network Branch 3 SS Branch 1 Branch 2 Survivable MG Includes Alternate Call Server IP Sets PSTN Survivable MG (no Call Server) SS = Signaling Server MG = Media Gateway TDM Sets PSTN

Network Resiliency Survivability at the branch Site’s for telephony is in many cases based on decisions made from a telephony perspective (quite natural !) Local PSTN access to use if service is lost from Main site. Survivability can also be based on IP network and resilient core (High Availability) by using redundant network links, possibly with a lower capacity on the backup link.

Redundancy for the remote sites WAN CORE SITE Datacenter 1 Datacenter 2 PSTN MG1000E MG1000E Primary NRS/GK Secondary NRS/GK Call Server CPU0 Call Server CPU1 MG1000E WAN MG1000E MG1000E MG1000E

Frågor ?