lsp,ess,sls

1© 2007 Avaya Inc. All rights reserved. Avaya – Proprietary & Confidential. Under NDA

STANDARD LOCAL SURVIVABILITY

STANDARD LOCAL SURVIVABILITY


Standard Local Survivability (SLS)Overview

Entry level survivability option for a single branch office– Alternative to Local Survivable Processor if only basic telephony

survivability is required– Similar to Cisco’s SRST

Survivable call processing integrated in gateway– Build-in software module– Provides call engine and routing functionality for local lines/trunks when CM

or LSP are not reachable– Administrable via PIM or local gateway CLI

Available in for:– G250 (all models)– G350 (hardware suffix C and above)– G450– IG550 gateways (4350, 6350)

Customer benefit: integrated, no-cost survivability

for branch gateways

G350

G250

G700

G350

G250

G450

IG550


Standard Local Survivability (SLS) Positioning

Standard Local Survivability (SLS)

Local Survivable Processor (LSP)

Feature set basic call functionality full CM functionality

Inbound/outbound dialing ✓ ✓

Call hold/transfer ✓ ✓

Voice mail coverage/access - ✓

3-way conferencing - ✓

High-capacity branches - ✓

Business critical branches, applications

- ✓

SLS offers reliable, entry-level survivability

for cost-sensitive branch deployments


SLS Becoming Active

Registration to CM attempted according to the MGC list. If all options fail → enter survivability mode (last option on the MGC list)

In survivability mode:

– Internal H.323 Gatekeeper and H.248 Media GW Controller activated

• Configures dial plan tables and gateway’s legacy stations/trunks

• Phones re-register to the internal gatekeeper

– Distinct SLS dial tone

– During transition to survivability mode, only local IP-IP calls will be preserved

Keep trying to re-register to CM, according to the MGC list and recovery timers


SLS Feature SummaryStations and Trunks Supported

Supports calls between local stations and to/from local PSTN trunks

Local station support includes:

– Analog, DCP, IP phones, IP Softphones (Road Warrior)

H.323 Gatekeeper supports max of

– G250: 12 IP stations



No limitations on number of analog, DCP stations (except G450 – 240 overall maximum stations)

All trunk types supported

– Analog

– ISDN BRI, PRI (all 25 country codes)

– E1/T1


Features Not Supported in SLS

3-party conference call

Call forward on busy/don’t answer

Auto-hold

Caller-ID for analog phones

MOH or playback of announcements

Call center features

Voice mail coverage/access

Connection preservation of failure to SLS or fall-back to CM


SLS Feature SummaryStation, Trunk Call Capability

Local station to local station calls

Local station to local trunk calls

All calls covered by simple call detail recording

– Up to 72 hours of call records

Same password, same extension number plan as CM

– Max of 13 digits

Trunk groups maintain the same relationship as when CM manages the gateway


SLS H.248 Link Recovery & Fallback

While SLS is enabled and processing, MG continues to re-register with alternative Call Controller (CM), per the MGC list

If CM or LSP accepts the registration, SLS will stop processing new calls

– Unregister the legacy station/trunk ports on the gateway

– Issue H.323 un-registration to IP phones

– IP shuffled calls are preserved between two IP phones

– No connection preservation on fallback

The SLS application will go to inactive mode


LOCAL SURVIVABLE PROCESSOR

LOCAL SURVIVABLE PROCESSOR


Local Survivable Processor (LSP)in H.248 Gateways

Local S8300 configured as secondary MGC

– prompted to action when primary call controller is unavailable

– provides comprehensive local call processing capabilities

Preserves all features available in normal operation

– call center agents

– local announcements

Customer benefit: complete local network outage protection

G350

G250

G450

G700


H.248 Local Survivable Processor (LSP)

Locally installed S8300 can configured to serve as:

– primary MGC (Integrated Call Controller)

– secondary MGC (Local Survivable Processor)

System translations are automatically propagated to local processors – station, trunking, applications, and system programming are up to

date if the LSP needs to take over

Optional Local Survivable Processor in G350


CommunicationManager

IP Phones

Central Data

Applications

Router

AnalogPhones

DCPPhones

MediaGateways

Digital/AnalogTrunks

PSTN

IP

IPPhonesH24

8 Contro

l

Voice

Beare

r

GatewayPrimary Link

Failure

H225

Central Location Branch Location

Analog, DCPPhones

H248 Registration Attempts

H.248 Local Survivable Processor (LSP)Failover to LSP


H.248 Local Survivable Processor (LSP)Transitioning to/from Back-up Modes

Connection preserving failover/fall back

– existing stable calls where the talk path exists between two or more parties are not dropped

– connection cannot be preserved for:

• calls that are not in stable state (on-hold, ringing, etc.)

• calls using IP or ISDN-BRI trunks, or ISDN stations

Configurable auto fall-back to primary connection

– gateway will automatically reconnect to the primary server when available after having failed over to the Local Survivable Processor (LSP) per the MGC list

– automatic reconnect can be administered to allow for orderly return to service without manual intervention

Failover/fall back normally takes ~3 minutes


S8500 as an LSP and Processor Ethernet

• Direct connectivity of endpoints, gateways, and adjuncts to the server (performing part of the functions of a CLAN)

• This approach has always existed on the S8300 servers• Extended to the S8500 servers with CM 3.1 • Along with it also came support for the S8500 as an LSP

8500

IP phones

H.248 Gateways


S8500 as an LSP

Supports up to 2,400 IP phones and 800 trunks

Supports adjuncts through new administration that allows association of different addresses to point to the active LSP

More cost effective to use compared to S8500 ESS

IP trunks currently not supported in LSP mode

CDRAE Services

CMSPMS

Active Standby


ENTERPRISE SURVIVABILITYENTERPRISE SURVIVABILITY


What is ESS?

Enterprise Survivable Servers allow backup servers to be placed at various places in a network so that communications can continue in the event that the main server(s) fails, or when connectivity to the main server(s) is lost

Enterprise Survivable Servers can be deployed where needed throughout your network to provide increased communications continuity

Enterprise Survivable Servers provides service to IPSI cards which automatically request service from an ESS server(s) if the control signal to the main server is lost


ESS versus LSP

ESSESS LSPLSPDescription S8500, S87xx S8300/S8500

Supported Port Networks/ Gateways

Port Networks: MCC, SCC, CMC, G650, G600

H.248 Gateways w/CLAN:G700, G450, G350, G250

H.248 Gateways:

G700, G450, G350, G250

Licenses to the:Reference IPSI

Need 1 IPSI for each ESS plus 1 for main

Gateway

Timer when contact is lost w/main

Administrable 3 – 15 minutes 1 minute & >

Failover/Fallback

Non-Connection PreservingConnection Preserving w/CM

3.0

Return to Primary Scheduled or Manual Automatic or On Demand

Capacities Up to 63 ESS servers Up to 250 LSPs


Enterprise Survivable Servers (ESS)

• The S8500 Media Server or S87xx Media Servers can act as an ESS

• All ESSs have full translations

• All ESSs connect to all IPSIs advertising their factors

• The IPSIs dynamically create preference lists of backup clusters (based on those supplied factors) that it can communicate with

• The IPSIs will request service from an ESS or the main cluster based on the highest ranked cluster it can communicate with when port network is not being controlled

• The preference list is dynamically changing based on connectivity changes

lsp,ess,sls

Documents