SOSE CS 1000 Release 5'0 ESAESCM Review - PowerPoint PPT Presentation

1 / 63
About This Presentation
Title:

SOSE CS 1000 Release 5'0 ESAESCM Review

Description:

The last date to have clean orders into Nortel for expansion of existing Release ... a unique number indicating the nearest pillar or an individual office or cubicle. ... – PowerPoint PPT presentation

Number of Views:218
Avg rating:3.0/5.0
Slides: 64
Provided by: markfl9
Category:

less

Transcript and Presenter's Notes

Title: SOSE CS 1000 Release 5'0 ESAESCM Review


1
(No Transcript)
2
Quick Update on release 3.0
  • Release 3.0 Software was introduced on October
    27, 2003 and Order Deadline for R3
  • ExpansionsThe last date to have clean orders
    into Nortel for expansion of existing Release 3
    systems is June 16, 2008. Expansions after that
    date will require an upgrade to current release.
  • Upgrading to CurrentThe least expensive way to
    upgrade is to use SRS to upgrade a Release 3
    system to Release 5 (or 5.5 planned for March
    28th). Even though Release 3 will be Retired in
    July, you will still be able to purchase SRS to
    upgrade to R5 or R5.5 until R6 becomes available
    next year (currently planned for 1Q09).
  • Support of Retired SoftwareLimited Nortel
    Enterprise Technical Support (NETS/GNTS) support
    is available once a software release is Retired.
    Currently the policy is that no new PEP's
    (patches) would be created to solve a customers
    problem however a PEP will be provided if one
    already exists.

3
Release 5.5 April GA
  • Mobile X
  • Subscriber Management
  • Enterprise Communication Manager Enhancements
  • NRSM Enhancements
  • EM Enhancements
  • Call Diversion
  • Enhanced Fax and Modem Support
  • 1200 Series IP Set Introduction
  • AST Expansion (up to 4 DNS)
  • Microsoft UM2007 Integration

4
CS 1000 Emergency Services Review - E911 Update
5
DISCLAIMER
  • PLEASE NOTE 911 LAWS AND REGULTIONS GREATLY VARY
    BY GEOGRAPHIC LOCATION
  • ALL LOCAL LEGISLATION AND CAPABILITIES MUST BE
    CLEARLY UNDERSTOOD AS PART OF SETTING UP CUSTOMER
    911 SOLUTIONS

6
Why the increased awareness?
Situations such as the one above are becoming
more frequent Recent occurrences at various
Universities and schoolsIP telephony and
mobility
7
Facts about the incident
  • Known Facts about the Incident
  • Company has 15 different locations working from 1
    PBX. Location information for all these buildings
    was the address associated with the companys
    billing address.
  • Fatality occurred because the emergency crew
    arrived at this listed address determined from
    the CLID the employee was in an adjacent
    MedImmune building with a different street .
  • Companies IP-PBX was a well known PBX Vendor with
    VoIP deployed however there was no E911
    Emergency Responder
  • Source familiar with the Company network revealed
    there were no local trunks at each location that
    would have enabled site location.
  • UnKnown Facts about the incident
  • Company, a multinational company with 2200
    employees and 7 U.S. locations  Did they have an
    emergency policy? Would notification to local
    security have helped? The employee died on 9 am
    on Tuesday and not during off hours.
  • Does the distributor or installation prime bear
    any liability for failing to provide sufficient
    information on 911 practices or recommendations?

8
What is the Law?Laws Vary by Country, State,
Province
  • The CRTC regulations state only the billing
    address of the PSTN Service must be sent to the
    Emergency Response Center and that a callback
    must be answered
  • Today this policy is consistent across Canada
  • Some carriers provide a chargeable service
    whereby PBX DID numbers can be used to identify
    more specific locations within a location.
  • This service may not be available in all regions
  • Carrier manually enters these numbers in the 911
    database and uses the modified record to send
    the refined location

9
Lets start with simple Caller ID
  • When a call is presented to your home phone, your
    local Central Office looks up the calling number,
    and adds name information.

973-285-7745Maersk Data, USA1 Campus Drive
Parsippany, NJ 07054
ANIDatabase
973-285-7745Maersk Data USA
10
PBX Systems and CLID
  • PBX system software sends the CLID via a PRI
    based on programming. It is not assigned
    automatically by the Central Office. It can be
    changed, or spoofed by the originating PBX.

973-285-5745Nortel Networks10 Sylvan
WayParsippany, NJ 07054
ANIDatabase
No verification is made by the end Central Office
of the validity of the calling number!
973-285-5745Nortel Networks
11
What is E911 and how does it work
  • In its most simplistic definition, E911 is
    nothing more than a Call Center Screen Pop
    application, based on the ANI (caller ID) of the
    caller.

ANI973-285-5745
ANI973-285-7745
ALIDatabase
973-285-5745Nortel Networks10 Sylvan
WayParsippany, NJ 07054
PSAPPublic Safety Answer Point
973-285-7745Maersk Data USA1 Campus
DriveParsippany, NJ 07054
12
So where is the problem?
Incorrectly Programmed or multiple line
appearances?
13
Sending the wrong number can be fatalIt is
Imperative E911 calling is configured correctly
911 call placed from second line
ANI973-285-7745
ALIDatabase
973-285-5745Nortel Networks10 Sylvan
WayParsippany, NJ 07054
PSAPPublic Safety Answer Point
973-285-7745Maersk Data USA1 Campus
DriveParsippany, NJ 07054
14
CLID and ANI There IS a Difference
  • LECs may treat the CLID differently when a call
    is made to 911. Depending upon the functionality
    available in the Class 5 switch, the CLID may not
    be used as the ANI for 911 call routing. Instead,
    the network may be programmed to use the listed
    directory number (LDN) or the bill-to number
    (BTN) for ANI purposes.
  • If the CLID is not used for ANI, then 911 calls
    coming from a PRI interface all look the same to
    the 911 network because they all have the same
    ANI.
  • Many LECs offer CLID transparency through a PRI
    interface for 911 calls. With this feature, the
    CLID presented is used as ANI to route the call.

15
The E911 Selective Router
  • Selective Routers provide routing from the
    Emergency Caller to the PSAP servicing their
    physical address.
  • These are usually dedicated Telco based Tandem
    COs, however the Selective Router could be
    virtual using a database dip to provide the
    proper endpoint PSAP termination.
  • It is important to understand the Selective
    Router topology in the customers service area
    before attempting to design an E911 routing plan
    for them.

PSAPPublic Safety Answer Point
16
The ALI Database
973-555-5000 The ABC Company 973-555-5001 The ABC
Company 973-555-5002 The ABC Company 973-555-5003
The ABC Company 973-555-5004 The ABC
Company 973-555-5005 The ABC Company 973-555-5006
The ABC Company 973-555-5007 The ABC
Company 973-555-5008 The ABC Company 973-555-5009
The ABC Company . . . 973-555-5098 The ABC
Company 973-555-5099 The ABC Company
  • ALI (Automatic Line Identification)
  • Database is owned by the Telco
  • Provides number to name translation for all
    numbers
  • Used by the PSAP for ANIscreen pop lookup
  • Companies with DID rangeshave an entry in the
    databasefor each number in the range if service
    is purchased today in Canada
  • Only 1 entry per number isallowed
  • Maintained by Telco billing records

ALIDatabase
PSAPPublic Safety Answer Point
17
The PS-ALI Database
973-555-5000 The ABC Company Reception 973-555-50
01 The ABC Company 1ST Floor NW 973-555-5002 The
ABC Company 3rd Floor Lobby 973-555-5003 The ABC
Company 1st Floor Com Room . . . . 973-555-5098 T
he ABC Company UNASSIGNED 973-555-5099 The ABC
Company 2nd Floor Cube 123
PS-ALIDatabase
  • PS-ALI (Private Switch Automatic Line
    Identification)
  • Database is owned by the Telco
  • Provides additional location detail format
    usually dictated by local Fire Marshall
  • Companies with DID rangeshave an entry in the
    databasefor each number in the range if service
    is purchased today in Canada
  • Only 1 entry per number is allowed
  • Maintained by Customer or Telco if service
    available (varies by Country/Region)

ALIDatabase
PSAPPublic Safety Answer Point
18
CS1000/Meridian E911 capabilities
  • Today Many systems in Canada utilize a basic form
    of access to the PSTN for 911 calling.
  • The use of an SPN allows users dialing 911 or
    9911 to reach a trunk route and send 911 to the
    Central Office
  • This method has been used to adhere to the
    Canadian and other regions basic 911 laws
  • This method does not allow for the use of
    Emergency Services Access that was introduced
    many years ago to enhance E911 capabilities and
    meet more stringent regional regulations

19
Nortels ESA Software
  • Handles the proper calling numberpresentation to
    the PSAP
  • Provides ESA CLID services to locations by
  • Identifying E911 calls
  • Provides proper call handling and priority
    routing
  • Supports Multiple NXX Exchanges
  • Supports Non-DID telephones
  • Support for Tandem 911 calls in a campus
    environment
  • Supports Multiple appearance numbers
  • On site notification to OSN Telephone
  • On site notification to TTY device
  • ESA Audit Capabilities WITHOUT Calling 911

20
Emergency Service Directory Number (ESDN)
  • ESDN is a number assigned within a
    CS1000/Meridian that when dialed alerts the
    system that a call requires emergency treatment.
  • If an ESDN is defined as 911 an SPN can be
    defined as 9911 which is re-ranslated to 911 to
    receive ESA treatments (this is shown later)
  • Allows Primary ESDN up to 15 additional ESDNs
  • Independent routing per ESDN in ESA Data Block
  • Required for EMEA or international enterprises,
    i.e.
  • North America 911
  • Mexico 060, 066, 080
  • UK 999, 112
  • Europe 112, 118, 117, 144, 145, 140, 143, 147,
    1414
  • Asia 108, 119, 999
  • Internal ESDNs
  • i.e. 2222 for internal hospital emergencies
    calls can locally terminate in the customer
    network based on the originators location (i.e.
    per floor)

21
Location Values
  • In CS 1000, release 5.0, the location of an
    telephony client is represented as
  • ERL (Emergency Response Location) - a 16 bit
    value indicating the ERL in which the client is
    currently located.
  • A value of 0 indicates that the ERL is unknown.
  • ERL values must be unique network wide.
  • ECL (Emergency Caller Location) - a 16 bit value
    indicating a more granular location that may be
    described in the PS-ALI record for an individual
    telephone DID number.
  • For example it may be a unique number indicating
    the nearest pillar or an individual office or
    cubicle.
  • ECL values may be defined at the same granularity
    as an ERL, as long as the PS-ALI records are
    configured at the same granularity.
  • ECL locations must fall within the boundary of an
    ERL.
  • ECL values are unique network wide and may NOT be
    re-used within a different ERL.
  • A value of 0 indicates that the ECL is unknown.
  • Location Description a 20 character string
    indicating the location of the IP client.
  • The description may be configured to correspond
    to the 20 character free form location field
    contained in the PS-ALI record used to identify
    the location of a caller within a building.
  • The string may contain any characters except
    quotation marks () and colons ().
  • The location description is not mandatory,
    however it can provide useful information for On
    Site Notification reports, location reports and
    other functions.

22
Emergency Response LocationsContinued
  • ERLs apply to every station TN in the system,
    including non-IP phones TDM stations all
    maintain static location data
  • If the ERL is not configured, or the ERL0, the
    call server uses the default ESA Data Block
    parameters that were defined and available prior
    to Emergency Service Client Mobility) ESCM and
    Release 5.0
  • In addition to telling the call server to fall
    back to ESA Data Block parameters, ERL 0
    indicates an Unknown location for IP stations.

23
Dynamic ELIN
  • ELINs (Emergency Location Identification Number)
    can be automatically assigned to an emergency
    caller based on the ERL in which they are
    located.
  • ELINs are assigned whenever the DID number of a
    phone either doesnt exist or it is not usable
    based on the location of the caller or if not
    maintained in a PS-ALI database.
  • Static ELINs represent a fixed phone in the area
    of the caller(within the ERL)
  • Dynamic ELINs do not have a permanently assigned
    physical phone
  • They are dynamically assigned to an emergency
    caller and forwarded to the call originator to
    facilitate call back from the PSAP.
  • Dynamic ELIN overflow/re-use
  • Can be configured to re-use the oldest dynamic
    ELIN or overflow to the static ELIN.
  • Callback fallbacks
  • Dynamic ELINs use phantom or virtual TNs and can
    be configured to route calls appropriately in the
    event the originating phone is not available.
  • Default Call Forward, Flexible Call Forward no
    Answer

24
Automatic Switching between Personal DID and ELIN
  • Each IP phone is configured with a home ECL
    value if it has a DID with corresponding entry
    in the PS-ALI database.
  • The home ECL value represents the location that
    is described in the PS-ALI record for the DID
    number associated with the phone.
  • If the current ECL value reported by the location
    service is the same as the configured home ECL,
    the DID, as configured in the ESA portion of the
    associated CLID block, is used for signaling
    location to the PSAP.
  • If the values do not match, then an ELIN is
    selected based on the current ERL of the phone.
  • This enables the conveyance of location at a
    station level to the PSAP for phones that are at
    their normal (configured) location.
  • Automatic ALI updating (3rd party) can be used to
    automate the move/add/change process by updating
    the PS-ALI database.

25
E911 Zones Using ERLs ECLs
DN Ranges 1000 1999 non-DID 4500 4599
DID (613-765)
DN 1002 ECL 101
DN 1001 ECL 100
DN 4504 ECL 103
DN 1004 ECL 104
ANI 613-765-4501 (In this example uses ELIN)
ERL 68 Static ELIN 613-765-4504
ERL 67 Dynamic ELIN(s)613-765-4501
ERL 80, ECL 80 Subnet 10.1.1.0/24 Dynamic
ELIN 613-765-4505
DN 1003 ECL 102
DN 1005 ECL 0
ANI 613-765-4504 (In this example a DID phone
within the ERL is used for ANI and CallBack)
ANI 613-765-4510 (DID is used as set is In its
home ECL)
ERL 81, ECL 81 Subnet 10.1.2.0/24 Dynamic
ELIN 613-765-4506
Callback
DN 4510 Home ECL 81
PSAP
ESA Call
26
Location Discovery MechanismsAllows Dynamic
Updates as IP Movement Occurs
  • In Release 5.0 two mechanisms are available for
    Location Discovery with ESCM
  • I-LIS
  • An internal subnet lookup mechanism that will map
    specific IP address ranges to a specific ERL
  • Package enabled in EC less than 10,000 US
  • E-LIS
  • An external interface available to any 3rd party
    Discovery Manager
  • Provides a simple way to collect information
    about registered sets
  • List of all sets currently registered
  • List of sets requiring a location update
  • Mechanism to update the Call Server for any IP
    set that was discovered
  • The E-LIS interface is provided with the base
    software package
  • Several 3rd party Development Partners are
    working on Release 5.0 Compatibility
    Certifications
  • E-LIS interface no longer ties up the Overlay
    space as was in the case in Release 4.5

27
Internal Location Information Service (LIS)
  • Assumes network architecture lines up with
    enterprise geography (i.e. floors within a
    building)
  • Relies on DHCP server assigning IP addresses by
    subnet, i.e. by location
  • Looks up phones IP address in subnet table and
    assigns location data associated to subnet entry
  • Implemented on Call Server
  • Handles re-location of desktop phones, Virtual
    Office, etc.

28
Internal Subnet LIS
Subnet Lookup Table Example
Station Config

Local CO or 911 Tandem
ISDN or CAMA
Extension 1111
Call Server Media Gateway
IP 47.11.214.65
Call Server sends ELIN (613-555-5555) when DN
1111 dials 911
3
6
9

Subnet LIS
ERL Table


IP Range
ELIN
ERL
ERL

47.11.214.0/24
101
613-555-5555
101
102
613-555-6666
47.11.215.0/25
102
103
613-555-7777
47.11.215.128/25
103
104
613-555-8888
47.11.216.0/24
104
)
  • Solution integrated in Call Server
  • No external device
  • Economical

29
E911 Mobility External LIS SolutionL2 Port
Mapping
Layer 2 Switch
Call Server
E-LIS
30
E911 Mobility External LIS SolutionSubnets
Layer 2 Switch
Call Server
Wire map Database
E-LIS
31
ESA On-Site Notification
  • OSN Telephone
  • TTY Output
  • Feed to 3rd Party Application
  • COST EFFECTIVE!
  • EFFICIENT!

32
OSN Enhancements
  • OSN logs re-formatted to include additional
    information
  • Caller Location information is expanded.
  • OSN set can be specified for ERLs as well as in
    ESA data block.
  • Only one phone is alerted per call.
  • ERL table entry overrides customer data block
    entry
  • OSN SNMP Traps re-formatted to eliminate
    truncation of important data.
  • SNMP traps still not recommended as primary
    notification mechanism to do un-reliability of
    underlying UDP transport.
  • A separate OSN TTY user can now be used to define
    a log device with only OSN log reports.

33
Optional, Simple script to send OSN information
to useful applications.
TIME 140752 SEPT 13, 2007 NAME Dave
Thomas ORIG DN 21745 SITE RICH1 Lakeside
Avenue LOC 4th Floor Lab 7
OSN000 CUST 0 911 CALL ALERT TIME 140752
SEPT 13, 2007 NAME Mark Fletcher ORIG DN
21745 SITE RICH1 Lakeside Avenue LOC 4th Floor
Lab 7 DES 1140E SET IP SET ERL 417 TER RTMB
20-16 ACOD 4420020 CALLED 911 CALLING SENT
9723621745 OSN0000 RECORD END
Dave Thomas Diabetic Allergic to
Penicillin Supervisor Mark Fletcher ext.
7202 Emergency ContactDiane Thomas 973-970-4301
34
Misdialed Emergency Call Prevention
  • Enabled Recognition of potentially misdialed
    Emergency Calls
  • This functionality MUST be explicitly enabled
  • A warning message is displayed prior to
    activation of this feature.
  • Additional digits dialed following ESDN within
    wait period cause call intercept.
  • Wait period configurable from 1 To 4 Seconds
    (default 2 seconds)
  • Wait period will delay origination of emergency
    call.
  • will terminate wait period and process call
    immediately
  • A repeating final digit can optionally be allowed
    without intercept
  • E.g. 9-1-1-1-1 or 1-1-2-2 would not be
    intercepted if enabled.
  • Intercepted Call Treatment can be configured
  • OVERFLOW, BUSY, ATTENDANT, RAN ROUTE xxx
  • On Site Notification
  • Call Intercept log generated.
  • Call Intercept SNMP Trap generated.
  • OSN set alerted as per normal ESA call.
  • Local responders must immediately investigate ALL
    intercepted emergency calls to ensure that an
    actual emergency did not occur.

35
ESA CLID Audit
ClID Audit was introduced in release 4.0 and s a
useful tool for Validating CLID for all types of
calls. With E911 it allows Verification before
test calls to a 911 provider
  • TN KEY DN ZN CTYP CLID
    RT CALLED
  • 005 0 00 00 00 SCR 3015 --- 911 C
    9735553015 003 911
  • NATL
    9735553015
  • INTL
    9735553015
  • UDP 2873015
  • CDP 3015
  • 005 0 00 00 01 SCR 4015 --- 911 C
    9735553015 003 911
  • NATL
    9735554015
  • INTL
    9735554015
  • UDP 2874015
  • CDP 4015
  • 005 0 00 00 05 SCR 3101 --- 911 C
    9735553015 003 911
  • NATL
    9735553101
  • INTL
    9735553101
  • UDP 2873101
  • CDP 3101

36
CLIDVER Audit Enhancement
  • Location denoted by ERL instead of Zone
  • Support for Multiple ESDNs
  • Support for Dynamic ELIN
  • Support for Enhanced Routing (RLIs, LTER)
  • Printing of Called Number

37
ESA for Virtual Office Enhancement
  • Previously, VO user that invoked ESA was
    re-directed back to its Host CS to complete the
    ESA call
  • Now, if the VO users location is known, Home CS
    routes the ESA call to the Host CS
  • More reliable than blind redirection
  • Fallback options are possible via RLI

38
ESA for Virtual Office Enhancement
TN 04 00 10 0 ERL DN 2000
TN 04 00 10 1 ERL 20 DN 3000
10
  • Set A is Homed to Edmonton CS1000
  • Set B is homed to Toronto CS1000
  • User A implements Network Virtual Office on Set B
  • Set B redirects to User As TN on Edmonton system
  • Set B ERL cookie updates ERL field on TN
  • ERL 20 in Edmonton now used for 911 calls
  • User A in Toronto dials 911
  • ERL 20 prepends AC2333 1 to 911
  • Call is routed over vTRKs to NRS
  • NRS Resolves 333 1 to Toronto Endpoint
  • Call is tandemed over vTrks to Toronto and out to
    local PSAP

20
Set A
Set B
DN 2000
DN 3000
Logged Out
Edmonton
39
Description Of FeatureBasic Emergency Service
When VO Logged Out
  • The E911 Virtual Office Logged Out (VOLO) feature
    will allow the Virtual Office Logged Out Set to
    make an emergency call. The feature will work on
    all the phones which support the Network Wide
    Virtual Office.
  • The feature depends upon the ESA feature to route
    the call. Non-ESA call will result in a overflow.
  • No other feature such as transfer, conference,
    redial, mail box, directory etc. are provided to
    this set
  • IP Phones CANNOT register to VOLO TN Type
  • This feature is to allow VO Logged out sets to
    make an ESA call without having to login.
  • Up to 255 VOLO TNs can be configured
  • Must be contiguous in the system
  • DO NOT use IP Licenses

40
Branch Office Normal Mode Operation
Main
Branch
41
Telecommuter
Location is known route emergency call to
appropriate PSAP. Can provide users home
telephone number as ANI.
Call Server
User is off-net, but location is static and known
and in same Selective Router Area as Main CS1000!
42
Road Warrior
Location is unknown (ERL 0) route emergency
call to local PSAP or terminate internally if
allowed by local laws.
Call Server
User is off-net and could be anywhere Location
cannot be determined!
43
Putting it all togetherFunctional Flow of ESA
Look for ESDN as digits are being dialed
911 detected as SPN entry
NARS BARS Processing
User goes off hook and dials
Sent to RLI specific for ESA Calls
LTERM applied to call
Apply ESA CLID Parameters
Trigger OSN Alerts
The LTERM programming of 9-911 in NARS/BARS is
critical for the proper operation of ESA.
Terminate Call on ESA Route
44
Nortel PBX Packages for ESA
  • Emergency Services Access (ESA) is package 329
    and provides
  • Included in Enhanced services Software Level
  • Emergency Services Access Call Recognition
  • Emergency Services Access Call Routing to
    dedicated trunks
  • Basic Number translations such as NXX and NPA but
    excluding non-DID translations
  • ESA Call Termination Identification
  • ESA (ESA_SUPP) is package 330 and provides
  • Included in Enhanced services Software Level
  • Networking conversions such as incoming ISDN to
    CAMA conversions (Tandem E911 calls)
  • On-Site Notification
  • ESA Calling Number Mapping (ESA_CLMP) is package
    331 and provides
  • Included in Enhanced services Software Level
  • Translation of non-DID numbers (Use of ELIN)
  • Package 336 ESA Subnet LIS
  • Optional Chargeable
  • Package 337 ESA External DM
  • Included in Enhanced services Software Level

45
  • Nortel ESA Solutions
  • Feature Rich ESA solutions included at no charge
  • Integrated into Call Server to provide a Superior
    Total cost of Ownership
  • No PS-ALI synchronization required
  • Optional Dynamic Solutions available
  • Low Cost
  • No external Server Required
  • Interface to External Solutions
  • Included at no charge

46
Backup
  • Acronyms
  • Configuration and Management
  • NENA Reference Site

47
Acronyms
  • ALI Automatic Location Identification
  • ANI Automatic Number Identification
  • CLID Caller Line Identification
  • DM Discovery Manager (i.e. Qovia LGS)
  • ECL Emergency Caller Location
  • ESA Emergency Services Access
  • ESCM Emergency Services for Client Mobility
  • ESDN Emergency Services Directory Number

48
AcronymsContinued
  • ELIN Emergency Location Identification Number
  • ERL Emergency Response Location
  • LGS Location Gateway Server
  • LIS Location Information Service
  • OSDN OSN DN
  • OSN On Site Notification
  • PSAP Public Safety Answering Point

49
References
  • Emergency Services Access NTP (553-3001-313)
  • National Emergency Number Association
    http//www.nena.org

50
Configuration and Management
  • Can be conducted from Command Line, element
    Manager or Telephony Manager
  • Examples shown on Next Slides are From Element
    Manager

51
Trouble-shooting
  • Review configuration (LD 11, 17, 24, etc)
  • Print current phone location data (LD 117 LOCRPT)
  • Look at system messages (ESAxxx)
  • Enable debugging (pdtgt esaDebugLevelSet 0-3)
  • Prints strategic debug statements to indicate
    background processing status

52
EM Manage ESA System Data(Config Record)
53
EM Manage ESA Customer Data(ESA and ESDN Data
Blocks)
54
EM Manage ERLs
55
EM Manage Subnet LIS
56
EM Manage Dynamic ELINs
57
EM ERL Maintenance
58
EM Subnet LIS Maintenance
59
EM Dynamic ELIN Maintenance
60
EM Search for IP Phone Location(LOCRPT)
61
EM General Commands(Methods For External DM)
62
Element Manager Virtual Office Phone Page
63
Element Manager Add Virtual Office Phone
Write a Comment
User Comments (0)
About PowerShow.com