espace ems product description (v200r001c02spc200_04)

eSpace EMS V200R001C02SPC200

Product Description

Issue 04

Date 2012-06-08

HUAWEI TECHNOLOGIES CO., LTD.

Issue 04 (2012-06-08) Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd. i

Copyright © Huawei Technologies Co., Ltd. 2012. All rights reserved.

No part of this document may be reproduced or transmitted in any form or by any means without prior

written consent of Huawei Technologies Co., Ltd.

Trademarks and Permissions

and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.

All other trademarks and trade names mentioned in this document are the property of their respective

holders.

Notice

The purchased products, services and features are stipulated by the contract made between Huawei and

the customer. All or part of the products, services and features described in this document may not be

within the purchase scope or the usage scope. Unless otherwise specified in the contract, all statements,

information, and recommendations in this document are provided "AS IS" without warranties, guarantees or

representations of any kind, either express or implied.

The information in this document is subject to change without notice. Every effort has been made in the

preparation of this document to ensure accuracy of the contents, but all statements, information, and

recommendations in this document do not constitute the warranty of any kind, express or implied.

Huawei Technologies Co., Ltd.

Address: Huawei Industrial Base

Bantian, Longgang

Shenzhen 518129

People's Republic of China

Website: http://www.huawei.com

Email: [email protected]

http://www.huawei.com/

mailto:[email protected]

eSpace EMS

Product Description Contents


Copyright © Huawei Technologies Co., Ltd.

ii

Contents

1 Overview ......................................................................................................................................... 1

1.1 Product Positioning .......................................................................................................................................... 1

1.2 Managed Objects .............................................................................................................................................. 2

1.3 Product Features ............................................................................................................................................... 4

2 System Structure ........................................................................................................................... 7

2.1 System Architecture ......................................................................................................................................... 7

2.2 Configuration Requirements ............................................................................................................................ 9

2.3 External Interfaces ......................................................................................................................................... 11

3 Functions and Features .............................................................................................................. 13

3.1 NE Access ...................................................................................................................................................... 14

3.2 NE Management ............................................................................................................................................. 17

3.2.1 IP PBX Management ............................................................................................................................. 17

3.2.2 IP Phone Management .......................................................................................................................... 19

3.2.3 EGW Management ................................................................................................................................ 21

3.2.4 IAD Management .................................................................................................................................. 23

3.2.5 SBC Management ................................................................................................................................. 25

3.2.6 GS8 Management .................................................................................................................................. 26

3.2.7 Voice Quality Monitoring ..................................................................................................................... 27

3.2.8 Automatic NE Connection .................................................................................................................... 28

3.2.9 NE Information Export ......................................................................................................................... 28

3.2.10 eSpace UC Management ..................................................................................................................... 28

3.3 Topology Management ................................................................................................................................... 34

3.4 Fault Management .......................................................................................................................................... 35

3.5 Performance Monitoring ................................................................................................................................ 38

3.6 Security Management ..................................................................................................................................... 41

3.7 Log Management ........................................................................................................................................... 42

3.8 Message Tracing ............................................................................................................................................. 43

3.9 Northbound Interface ..................................................................................................................................... 44

4 System Reliability ....................................................................................................................... 46

5 Technical Specifications ............................................................................................................ 47

6 Acronyms and Abbreviations ................................................................................................... 49

eSpace EMS

Product Description 1 Overview



1

1 Overview

About This Chapter

1.1 Product Positioning

This topic describes the background and purpose of the eSpace EMS.

1.2 Managed Objects

The eSpace EMS can manage IP PBXs, IP Phones, eSpace EGWs, eSpace IADs, SBCs.

1.3 Product Features

This topic describes the eSpace EMS features. These features meet the O&M requirements of

telecom operators in the scenarios such as product deployment, daily maintenance, upgrade

and expansion, and troubleshooting.

1.1 Product Positioning

This topic describes the background and purpose of the eSpace EMS.

The eSpace EMS, developed by Huawei, is a new-generation web-based software platform

that can run on different operating systems. The eSpace EMS provides rapid and competitive

network management solutions for Huawei UC products. It meets operation and maintenance

requirements of the deployment, routine maintenance, troubleshooting, upgrade, and

expansion scenarios, helping increase network management performance and efficiency.

Centralized network management

High-Efficient deployment

Rapid fault location

Effective analysis of network performance

Quick response to service requirements

As the local NMS for Huawei products on the network, the eSpace EMS implements

operations and maintenance requirements such as deployment, routine maintenance,

troubleshooting, upgrade, and expansion.

The eSpace EMS and this product are deployed together. The eSpace EMS manages only

this product.

eSpace EMS




2

The eSpace EMS can use its northbound interface (NBI) to access a carrier's NMS.

Figure 1-1 eSpace EMS's position in the UC solution

1.2 Managed Objects

The eSpace EMS can manage IP PBXs, IP Phones, eSpace EGWs, eSpace IADs, SBCs.

Table 1-1 lists the specific NEs that can be managed by the eSpace EMS.

eSpace EMS




3

Table 1-1 Managed objects

NE Type Model

IP PBX eSpace U1910, eSpace U1930, eSpace U1980, SoftCo9500, SoftCo5500,

SoftCo5816

IP Phone eSpace 6805, eSpace 6810, eSpace 6830, eSpace 6850, and eSpace 6870

eSpace 7810, eSpace 7820, eSpace 7830, eSpace 7850, and eSpace 7870

eSpace 8850

EGW EGW1500 series

eSpace

IAD

eSpace IAD1224, eSpace IAD132E(T), eSpace IAD208E(M), eSpace

IAD104H, eSpace IAD102H, eSpace IAD101H

SBC SX1000

GS8 -

eSpace

UC

application

s

Business Management Point (BMP)

Access Agent (AA) Service

Enterprise Service Gateway (ESG) Service

Mobile Access Agent (MAA) Service

Call Application Server (Call AS)

The Call AS has the following components:eSpaceCTD, UCCBB, and

UCCallAS.

Presence, Group, and Messaging (PGM)

The PGM has the following components: eCorpServer, GnsService,

PublicGroup, AccountManagement, SoapToXcap, IWF, SM, GMService,

GroupManagement, PGMConfig, and ChatServer.

eSpace

Meeting

hw_IMS_Conference_CBU, hw_IMS_Conference_CMU,

hw_IMS_Conference_CSipServer, hw_IMS_Conference_focus, conference

Portal, MS, Cache, MGW, Agent, WTS, and CIU

SuSE

Linux

SuSE Linux Enterprise Server 9 SP4

SuSE Linux Enterprise Server 10 SP2

SuSE Linux Enterprise Server 11

Windows Windows 2000/2003 Server

Windows 2008 R2

Windows XP/2000/win7 Professional

Oracle Oracle 9i/11g

SQL

Server

SQL Server 2000, SQL Server 2005, and SQL Server 2008

Huawei

switch

Quidway S2300, Quidway S3300, Quidway S5300C, and Quidway S9300

Huawei AR-28 and AR-46

eSpace EMS




4

NE Type Model

router

Cisco

switch

Cisco 2900 series

Cisco

router

Cisco 3600 series

SBC SBC 2100 and SBC 2300

Huawei

SVN

Quidway SVN3000 and Quidway SVN5300

Disk array

ISM

S2300E, S2600, S3900, and S5300

Eudemon

firewall

Eudemon 200, Eudemon 500, and Edudemon 1000E

F5 load

balancer

BIG-IP 1600, BIG-IP 3600, BIG-IP 3900, BIG-IP 8400, and BIG-IP 8900

Radware

load

balancer

AppDirector 508, AppDirector 1008, AppDirector 2008, AppDirector 4016,

AppDirector 8016, and AppDirector 12016

In this document, IAD and EGW are short for eSpace IAD and eSpace EGW.

1.3 Product Features

This topic describes the eSpace EMS features. These features meet the O&M requirements of

telecom operators in the scenarios such as product deployment, daily maintenance, upgrade

and expansion, and troubleshooting.

Comprehensive Network Management Functions

You can perform topology management, fault management, and performance management to

achieve local maintenance and centralized management.

Centralized topology management

Topology management enables you to manage and browse topology objects, and receive

topology change notifications.

Centralized fault management

Fault management enables you to receive, synchronize, filter, restore, clear, and identify

alarms, which helps you understand alarms and perform troubleshooting based on

alarms.

Comprehensive performance management

eSpace EMS




5

Performance monitoring enables you to understand the performance indicators of NEs

and trends of the performance indicators. The indicators and their trends help to optimize

and maintain the network.

Perfect security management

Security management involves authentication, authorization, user management, and role

management. These operations ensure user account security and system running safety.

Comprehensive configuration management

Configuration management enables you to add, modify, delete, import and export

configurations.

Convenient message tracing

Message tracing enables you to create a task to obtain real-time information about UC2.0

service handling processes and use the traced messages to locate faults. The tracing

result can be displayed in a list or chart.

Clear NE upgrade management

The IP PBX, IAD, EGW, IP phone, GS8, and SBC (SX1000) can be upgraded in batches.

Upgrade wizard, upgrade monitor, upgrade history, and version management make NE

upgrade clearer and simpler. The eSpace EMS can be upgraded instantly or scheduledly.

In case of IP PBX or UAP3300 upgrade failure, the eSpace EMS supports upgrade retry

and rollback.

Easy Maintenance

The Web-based client of the eSpace EMS does not require installation or upgrade. You can

access the client by using Internet Explorer or Mozilla Firefox.

Standard Interfaces

NEs access the eSpace EMS over Simple Network Management Protocol Version 3(SNMPv3),

Simple Network Management Protocol Version 2c(SNMPv2c), Simple Network Management

Protocol Version 1(SNMPv1), TR069, and SOAP. The upper-layer NMS uses northbound

interfaces to satisfy various access requirements of users over SNMP.

High Security

A secure transmission mechanism is used to ensure access and data security through

hierarchical user management and data encryption.

You can grant device operation rights to specified user groups to improve reliability and

security of the eSpace EMS.

When the production machine (PM) is down due to a disaster, the redundancy machine (RM)

can take over the eSpace EMS service to ensure service continuity.

License Control

The eSpace EMS provides the following license control items:

Expiration date of a license

Number of allowed NEs

Whether the SNMP northbound alarm function is supported

eSpace EMS




6

When the value of a license control item exceeds the specified threshold, an alarm is

generated.

The eSpace EMS allows you to query the license validity period. License states include

normal, expired, invalid, and no license file.

eSpace EMS

Product Description 2 System Structure



7

2 System Structure

About This Chapter

2.1 System Architecture

The eSpace EMS is deployed in the single-node system mode or Geography Disaster

Recovery (GDR) mode.

2.2 Configuration Requirements

The eSpace EMS configuration contains the configuration of hardware and software of the

eSpace EMS server and client.

2.3 External Interfaces

External interfaces of the eSpace EMS include northbound interfaces and interfaces between

the eSpace EMS and NEs.

2.1 System Architecture

The eSpace EMS is deployed in the single-node system mode or Geography Disaster

Recovery (GDR) mode.

eSpace EMS




8

Single-Node System Mode

Figure 2-1 Network diagram in the single-node system mode

GDR mode

A PM and an RM are deployed in the GDR mode. The eSpace EMS is installed on each

machine. The PM provides eSpace EMS services externally. When the PM is faulty, the

service must be manually switched to the RM, and the RM provides the service.

eSpace EMS




9

Figure 2-2 Network diagram in the GDR mode

2.2 Configuration Requirements

The eSpace EMS configuration contains the configuration of hardware and software of the

eSpace EMS server and client.

Hardware Configuration Table 2-1 shows the hardware requirements on the eSpace EMS server.

Table 2-1 Recommended hardware requirements of the eSpace EMS server

Number of NEs

Model Configuration Requirement

0-20,000 E6000/RH228 CPU 2 x Intel Xeon E5606

eSpace EMS




10

Number of NEs

Model Configuration Requirement

5 Memory 2 x 4 GB

Hard disk 2 x 300 GB

20,000-50,000 E6000/RH228

5

CPU 2 x Intel Xeon E5506

Memory 32 GB

Hard disk 2 x 300 GB

Table 2-2 shows the hardware requirements of the eSpace EMS client.

Table 2-2 Hardware requirements of the eSpace EMS client

Hardware Requirement

CPU P4 2.8 GHz or faster

Memory 2 GB or higher

Hard disk 80 GB

Network adapter 10/100 Mbit/s network adapter

Audio adapter Integrated audio adapter

Monitor 17" color monitor or larger

Recommended resolution: 1024 x 768

Software Configuration Table 2-3 shows the software requirements of the eSpace EMS server.

Table 2-3 Software requirements of the eSpace EMS server

Installation Scenario Software Version

When Linux is installed Operating system SuSE Linux Enterprise

Server 11 SP1

Database Oracle Database 11g

Release 11.1.0.7.0 - 64bit

Production

Note: The Oracle standard

edition is used in the

single-node system mode,

and the Oracle enterprise

edition is used in the DR

mode.

eSpace EMS -

eSpace EMS




11

Installation Scenario Software Version

When Windows is installed Operating system Windows Server 2008 R2

Database Built-in MySQL database

eSpace EMS -

Table 2-4 shows the software requirements of the eSpace EMS client.

Table 2-4 Software requirements of the eSpace EMS client

Software Version

Operating system Windows XP or Windows 7

Web browser Internet Explorer 8.0 or Mozilla Firefox

3.6.16

CAUTION

If you do not use the recommended browser

version, some software functions of eSpace EMS

may be unavailable.

2.3 External Interfaces

External interfaces of the eSpace EMS include northbound interfaces and interfaces between

the eSpace EMS and NEs.

Interfaces Between the eSpace EMS and NEs

Table 2-5 lists the mapping between NEs and interfaces.

Table 2-5 Mapping between NEs and interfaces

NE Interface

eSpace EMS-IP PBX Telnet/SSH

eSpace EMS–UAP3300 Proprietary protocol

eSpace EMS-IAD SNMP-based interface

eSpace EMS-GS8

eSpace EMS–HWLog

eSpace EMS-SBC(SX1000) TR069-based interface

eSpace EMS-IP Phone

eSpace EMS-EGW

eSpace EMS




12

NE Interface

eSpace EMS–AT

eSpace EMS–UC SOAP/SNMP

eSpace EMS–eSpace Meeting

Northbound Interfaces

Northbound interfaces are provided for external systems, including the upper-layer NMS or

third-party analysis software. Northbound interfaces include SNMP alarm interfaces, SNMP

topology interfaces, and FTP interfaces. Table 2-6 describes the functions of northbound

interfaces.

Table 2-6 Description of northbound interfaces

Interface Function

SNMP alarm

interface

The upper-layer NMS uses this interface to receive alarms from the

eSpace EMS and handle alarms existing in the eSpace EMS. The SNMP

alarm interface performs the following functions:

Forwards alarms in real time.

Synchronizes alarms.

Acknowledges or unacknowledges alarms.

Clears alarms.

Forwards heartbeat messages.

eSpace EMS

Product Description 3 Functions and Features



13

3 Functions and Features

About This Chapter

3.1 NE Access

Only connected NEs can be managed on the eSpace EMS. NEs can be connected in the

following three ways.

3.2 NE Management

The eSpace EMS can manage IADs, IP PBXs, SBCs, GS8s, IP phones and EGWs.

3.3 Topology Management

In the eSpace EMS, the topology view displays NE status and links. With this function, you

understand the network structure and operating status of network devices.

3.4 Fault Management

With this function, you can learn about and rectify critical faults in a timely manner based on

the alarm information.

3.5 Performance Monitoring

With this function, you can understand the performance indicators of NEs and trends of the

performance indicators. This information provides a reference to optimize and maintain the

network.

3.6 Security Management

Security management is to control the eSpace EMS user permission and user roles, and ensure

security of user accounts and managed devices by means of authentication, authorization, and

encryption.

3.7 Log Management

Logs are stored in the eSpace EMS database. You can query logs on the eSpace EMS client.

3.8 Message Tracing



3.9 Northbound Interface

eSpace EMS




14

Northbound interfaces are the external interfaces to connect the eSpace EMS and the

upper-layer NMS or other systems.

3.1 NE Access

Only connected NEs can be managed on the eSpace EMS. NEs can be connected in the

following three ways.

GUI Page

Figure 3-1 NE access page

Creating an NE

You can create information about subnets, applications, and physical devices on the eSpace

EMS.

eSpace EMS




15

Figure 3-2 Page for creating an NE

Automatic NE Discovery

The system supports automatic detection. After you configure the IP and port ranges, devices

are detected and accessed automatically.

To enable the automatic IP PBX detection, specify the user name and password for logging in

to the IP PBX.

eSpace EMS




16

Figure 3-3 Automatic NE discovery page

The IP address or port number can be customized on the device.

Port mapping must be configured when the device and eSpace EMS are connected over networks.

Batch NE Import

If you need to create a large number of NEs, you can fill in the device list with information

about these NEs and import the device list to the eSpace EMS.

Figure 3-4 Page for importing NEs in batches

eSpace EMS




17

3.2 NE Management

The eSpace EMS can manage IADs, IP PBXs, SBCs, GS8s, IP phones and EGWs.

3.2.1 IP PBX Management

IP PBX management includes configuration management, performance management,

maintenance management, and alarm management.

IP PBX Management Page

Figure 3-5 IP PBX management page

Configuration Management

The eSpace EMS can manage a single IP PBX or IP PBXs in a batch.

Batch configuration

The eSpace EMS enables you to configure SIP trunks for IP PBXs, active and standby IP

PBXs, and the call forwarding offline service in a batch.

Single configuration

Single configuration can be implemented in the following ways:

− Command tree

You can use IP PBX-specific commands in the command tree to configure a single IP

PBX.

− Device panel

eSpace EMS




18

The IP PBX device panel provides a GUI that allows you to query the IP PBX's

running status and manage components such as boards.

Performance Management

The eSpace EMS provides performance management so that you can query IP PBX's E1 and

DSP resource usage, and the CPU usage, memory usage, and transmit and receive bandwidth

for boards.

Maintenance Management

The eSpace EMS provides IP PBX maintenance management, which enables you to upgrade

IP PBXs, back up configuration data, trace signaling and trunks, view device information and

operation logs, perform ping tests, and manage patches.

Upgrading IP PBXs

You can upgrade the main program for IP PBXs in batches. If an upgrade fails, you can

retry or roll back the upgrade on the eSpace EMS.

Backing up configuration data

The IP PBX configuration data in the data.bin file can be backed up and restored

automatically or manually on the eSpace EMS, and can be saved to a local computer.

Tracing signaling

The eSpace EMS provides real-time signaling tracing management to dynamically trace

and monitor protocol messages, transmission over ports' signaling links, and service

flows.

The eSpace EMS traces:

− SIP signaling

− H248 signaling

− PRA signaling

− R2 signaling

− SS7 signaling

− QSIG signaling

− User messages

Traffic statistics

You can collect the statistics of IP PBX traffic, set the execution period of traffic

statistics collection tasks, set the start time and end time of a traffic statistics collection

task, and export and delete traffic data. The statistics items include the number of global

Real-Time Transfer Protocol (RTP) messages, number of SIP sessions, number of SIP

sessions on the outgoing trunk, number of SIP sessions on the incoming trunk, and

duration of a SIP session.

Tracing trunks

The eSpace EMS traces IP PBX trunks based on the office direction. You can view the

real-time or historical usage of trunks.

Managing patches

You can view, load, activate, deactivate, save, and delete patches on the eSpace EMS.

Operation log

Operation logs record operations that users perform on the IP PBX. You can search for

and export operation logs.

eSpace EMS




19

Ping test

You can run the ping command to test the connection between an IP PBX and other

devices.

Viewing device information

You can view the basic information about IP PBXs, license information, version

information, and patch information on the eSpace EMS.

Alarm Management

The eSpace EMS monitors IP PBX alarms. You can view alarms and rectify them on the

eSpace EMS.

3.2.2 IP Phone Management

This topic describes management functions of IP phones.

IP Phone Management Page

Figure 3-6 IP phone management page

Automatic Deployment Create IP phone subnets.

You can create IP phone subnets on the eSpace EMS. When an IP phone registers with

the eSpace EMS for the first time, the eSpace EMS automatically adds the IP phone to an

appropriate subnet.

Create configuration files.

After creating a subnet, you are advised to create a configuration file for the subnet. Then,

the eSpace EMS automatically delivers the configuration file to an IP phone when the IP

phone is added to the subnet.

Query IP phones that have not been added to a subnet.

If the IP address of an IP phone is beyond the IP address range of the available subnets,

the eSpace EMS saves the IP phone information to the cache. You can query the IP

phone in the cache, and add a subnet for this IP phone, or change the IP address range of

subnets.

eSpace EMS




20


Configuration management includes:


You can restart a single IP phone, view or modify its TR069 settings, and load the

configuration file.

Batch configuration

You can restart IP phones and load configuration files in batches.


Maintenance management includes:

Manually upgrade an IP phone.

Automatically upgrade an IP phone.

You can upload an IP phone version file to the eSpace EMS. When the automatic

upgrade function is enabled on the IP phone, the IP phone periodically detects the

version number on the eSpace EMS server. If the version is different from the local

version, the IP phone automatically upgrades.

Download configuration files.

Download logs.

Manage configuration file templates.

Alarm Management

The eSpace EMS monitors IP Phone alarms. You can view alarms and rectify them on the

eSpace EMS.

Function Comparison of IP Phones

Table 3-1 compares functions of various IP phones.

Table 3-1 IP phone function list

Function eSpace 6805, eSpace 6810, eSpace 6830, eSpace 6850, and eSpace 6870


eSpace 8850

Automat

ic

deploym

ent

Creating IP

phone subnets

Supported Supported Supported

Managing

configuration

files

Not supported Supported Supported

Querying IP

phones that have

not been added to

a subnet

Supported Supported Supported

eSpace EMS




21

Function eSpace 6805, eSpace 6810, eSpace 6830, eSpace 6850, and eSpace 6870


eSpace 8850

Configur

ation

manage

ment

Device restart Supported Supported Supported

Loading a

configuration file


Querying and

modifying TR069

configuration


Mainten

ance

manage

ment

Manual

upgrading

devices


Automatically

upgrading

devices

Not supported Supported Not

supported

Managing

configuration file

templates


Downloading

configuration

files


supported

Downloading

logs


supported

Managing alarms Supported Not supported Not

supported

3.2.3 EGW Management

The EGW management includes configuration management, maintenance management, and

alarm management.

eSpace EMS




22

EGW Management Page

Figure 3-7 EGW management page


Table 3-2 lists configuration management functions.

Table 3-2 Configuration management functions

Category Function

Basic

configurati

on

Load configuration files, back up configuration files, and restore factory

settings or common settings.

Local area

network

(LAN)

configurati

on

Configure the firewall and LAN.

Voice

configurati

on

Configure the SIP server, FXO outgoing prefix, and data synchronization

server.


The eSpace EMS provides EGW maintenance management so that you can:

Upgrade EGWs in batches.

Check basic EGW information.

Restart EGWs.

Alarm Management

The eSpace EMS monitors EGW alarms. You can view alarms and rectify them on the eSpace

EMS.

eSpace EMS




23

3.2.4 IAD Management

IAD management includes configuration management, performance management,

maintenance management, and alarm management.

IAD Management Page

Figure 3-8 IAD management page


The eSpace EMS can manage a single IAD or IADs in a batch.


Table 3-3 lists the all the single configuration functions provided by the eSpace EMS.

eSpace EMS




24

Table 3-3 Single configuration functions

Function Description

Basic

configurati

on

Configures network parameters, the network management system's (NMS)

IP address, device time, and whitelist.

Advanced

configurati

on

Configures the protocol, Trap switch, Real-Time Transport Control Protocol

(RTCP) alarm threshold, and when to report an alarm when a port is locked,

and SIP soft parameters.

Service

configurati

on

Configures the DigitMap, proxy server, SIP user table, voice parameters, fax

parameters, dual-tone multi-frequency (DTMF) signal collection mode, local

switch, local-switch route, media gateway control protocol (MGCP)

authentication mode, MGCP protocol parameters, media gateway controller

(MGC), media gateway (MG) interface parameters, test operating system or

chip operating system (TOS/COS), port attributes, traffic control, IP address

authentication switch, IP address authentication, SIP trunk, public switched

telephone network (PSTN) server, polarity reversal switch, hotline number,

three-way conversation, short number, wildcard group, and multi-country

adaptation.

System tool Used to query version information, display the DSP channel status, configure

the network port status, save settings, restore the default or original settings,

restart devices, query country codes, collect statistics on ports, display the

MG link status, and network detection.

Upgrade

managemen

t

Supports the automatic upgrade.

The eSpace EMS provides single configuration functions for IADs based on the IAD model and the

protocol used by the IAD.

Batch configuration

− Configure network parameters

− Configure the proxy server

− Configure NMS's IP address

− Configure the read and write community

− Save settings


The eSpace EMS provides the performance management function so that you can monitor the

CPU usage of an IAD.


The eSpace EMS provides the following functions of managing IADs:

Upgrade

eSpace EMS




25

− Automatic upgrade: When the automatic upgrade is enabled, an IAD periodically

checks the latest version recorded in the upgrade file on the FTP server. If the IAD

detects a file with a different version on the FTP server from that in the upgrade file,

it is upgraded automatically.

− Manual upgrade: The Complex Programmable Logic Device (CPLD) software and

host software can be manually upgraded for IADs in batches. Only the CPLD

software on IAD132E (T) needs to be upgraded.

The IAD configuration data can be backed up and restored automatically or manually on

the eSpace EMS and can be saved to a local computer.

The IAD user information can be backed up and restored on the eSpace EMS and can be

saved to a local computer.

You can run the ping command to check the connection between an IAD and other

devices.

Alarm Management

The eSpace EMS monitors IAD alarms. You can view alarms and rectify them on the eSpace

EMS.

3.2.5 SBC Management

The SBC management includes the configuration management, upgrade management, and

alarm management.

SBC Management Page

Figure 3-9 SBC management page


The eSpace EMS enables you to configure a single SBC or SBCs in batches.


The eSpace EMS enables you to perform the following operations on a single SBC:

− Start the device

− Perform soft switch

eSpace EMS




26

− Configure network parameters

− Configure service ports

Batch configuration

The eSpace EMS enables you to perform the following operations on a batch of SBCs:

− Start the device

− Perform soft switch

− Configure service ports

Upgrade Management

The eSpace EMS enables you to upgrade SBCs in batches.

Alarm Management

The eSpace EMS monitors SBC alarms. You can view alarms and rectify them on the eSpace

EMS.

3.2.6 GS8 Management

The GS8 management includes the configuration management, upgrade management, and

alarm management.

GS8 Management Page

Figure 3-10 GS8 management page


The eSpace EMS enables you to perform the following operations for GS8s:

Restart the system

Configure network parameters

Configure the IP line

Configure the GSM line

Configure routes

eSpace EMS




27

Upgrade Management

The eSpace EMS enables you to upgrade GS8s in a batch.

Alarm Management

The eSpace EMS monitors GS8 alarms. You can view alarms and rectify them on the eSpace

EMS.

3.2.7 Voice Quality Monitoring

The eSpace EMS enables you to monitor the voice quality of eSpace U1910, eSpace U1930,

eSpace U1980 and IAD1224.

Configuring monitoring-related parameters

You can specify monitored areas, start and end times of a monitoring task, and data

collection periods on the eSpace EMS.

Viewing data

You can view the calling and called devices, mean opinion score (MOS) value, delay,

jitter, packet loss ratio, and codec settings on the eSpace EMS.

eSpace EMS




28

Figure 3-11 Report View

3.2.8 Automatic NE Connection

When there are SIP registration relationships or SIP trunks between NEs or when IP PBXs

work in active/standby mode, the eSpace EMS automatically creates connections between

NEs in the topology.

3.2.9 NE Information Export

The eSpace EMS enables you to export device information to .csv files, including the device

name, type, IP address, version information, model, and description.

3.2.10 eSpace UC Management

The eSpace EMS manages eSpace UC V200R001 system, including the following services:

BMP, AA Service, ESG Service, MAA Service, Call AS, eSpace Meeting, and PGM.

eSpace EMS




29

BMP Management

The BMP management includes system management, log management, and alarm

management.

Introduction

The BMP is a unified service management platform and supports the combination of various

services. When logging in to the BMP, the enterprise administrator can maintain enterprise

information and register and deregister enterprise members.

BMP System Management

You can directly access the BMP system after you log in to the eSpace EMS.

Log Management

The eSpace EMS enables you to perform following operations:

Query security logs

Security logs record all security operations in the BMP. The operations include login,

logout, password change, and user creation.

Query operation logs

You can query operation logs to obtain information about historical operations.

Download log files

You can download log files from the BMP server to the local host.

Search for logs

You can set the search criteria to search for logs.

Alarm Management

The eSpace EMS monitors BMP alarms. You can view alarms and rectify them on the eSpace

EMS.

AA Service Management

The AA Service management includes configuration management, performance management,

message tracing, and alarm management.

Introduction

The AA connects eSpace Desktop to ASs. eSpace Desktop obtains login information from the

AA and uses other service capabilities of eSpace UC through the AA.


The eSpace EMS provides AA configuration tables for easy configuration.


The eSpace EMS enables you to query the number of users who log in to the AA Service

successfully.

eSpace EMS




30

Message Tracing

The eSpace EMS traces the messages transmitted between AA Service components. The

traced messages help you to locate and rectify faults if any.

Alarm Management

The eSpace EMS monitors AA Service alarms. You can view alarms and rectify them on the

eSpace EMS.

ESG Service Management

The ESG Service management includes configuration management, performance management,


Introduction Provides a service openness and integration platform.

Connects to or integrates with IT, Social Networking Service (SNS), and Internet

systems of enterprises.


The eSpace EMS enables you to configure:

Database

ESG service

ESG time

PGM

Conference

ESG callback service


The eSpace EMS enables you to obtain the values of Count of ESGCallbackNum, Count of

ESGInvokedFail, Count of ESGInvokedNum, and Count of ESGInvokedSucc.

Message Tracing

The eSpace EMS traces the messages transmitted between ESG Service components. The


Alarm Management

The eSpace EMS monitors ESG Service alarms. You can view alarms and rectify them on the

eSpace EMS.

MAA Service Management

The eSpace EMS monitors MAA Service alarms. You can view alarms and rectify them on the

eSpace EMS.

eSpace EMS




31

Introduction

The MAA connects third-party clients, especially mobile clients, to ASs and provides the

following functions:

Interface conversion: The MAA converts various interface messages from eSpace UC's

ASs into Transmission Control Protocol (TCP) interface messages and sends them to

third-party clients.

Client session maintenance: After third-party clients connect to the MAA, the MAA

generates a session for each client and maintains the session status based on the client

status.

Service processing: The MAA processes service logic, such as the logic for heartbeat

mechanism, reconnection after a short disconnection, and IM timeout processing.

Call AS Management

The Call AS management includes configuration management, performance management,


Introduction

The Call AS is a core component of eSpace UC and provides call control and service

processing capabilities.


The eSpace EMS enables you to configure the following items for the eSpaceCTD:

Voice files

CalleePAS

CallerPAS

Default language

ESG service name

Maximum no-answer duration

Route header


The eSpace EMS enables you to collect performance statistics on the following Call AS

components:

eSpaceCTD

The performance indicators of the eSpaceCTD are: number of CTD call failures due to

offline, number of CTD call failures due to busy, and number of CTD call failures due to

no answer.

UCCallAS

The performance indicators of the UCCallAS are: Count of Hunting Group calls in

STC Flow, Count of Hunting Group Calls failed in STC Flow, Count of release calls

for Called party number analyze failed in STC Flow, and Count of release calls for

Called party number authentication failed in STC Flow.

eSpace EMS




32

Message Tracing

The eSpace EMS traces the messages transmitted between eSpaceCTD and UCCallAS. The


Alarm Management

The eSpace EMS monitors the alarms about the eSpaceCTD and UCCallAS. You can view

alarms and rectify them on the eSpace EMS.

PGM Management

The PGM management includes configuration management, performance management,


Introduction

The PGM has the following components: eCorpServer, GnsService, PublicGroup,

AccountManagement, SoapToXcap, IWF, SM, GMService, GroupManagement, PGMConfig,

and ChatServer.


The eSpace EMS enables you to configure the following PGM components:

PGMConfig

You can set the following PGMConfig configuration items: common PGM

configurations, contact group, group message, message service management, and SP

number.

ChatServer

You can set the following ChatServer configuration items: conference site and network.


The eSpace EMS enables you to collect the performance statistics on the following PGM

components:

GMService

The performance indicators of the GMService are: count of SM success message, count

of IM success message, count of GM success message, count of SM message, count

of IM message, count of GM message, count of SM fail message, count of IM fail

message, and count of GM fail message.

ChatServer

The performance indicators of the ChatServer are:

− Total number of users in temporary groups, including online users and offline users.

− Total number of temporary groups that have been created, including those that are

created successfully and those that failed to be created.

− Total number of group messages in a temporary group

− Total number of temporary groups that are created successfully

− Total number of temporary groups that are deleted

eSpace EMS




33

Message Tracing

The eSpace EMS enables you to trace the messages transmitted between the eCorpServer,

GnsService, PublicGroup, AccountManagement, SoapToXcap, SM, GMService,

GroupManagement, and ChatServer. The traced messages help you to locate and rectify faults

if any.

Alarm Management

The eSpace EMS monitors PGM alarms. You can view alarms and rectify them on the eSpace

EMS.

eSpace Meeting Management

The eSpace Meeting management includes configuration management, performance

management, and alarm management.

Introduction

The Meeting Service provides the conference function, including voice and multimedia

conferences.

Voice conference

The MS supports instant and scheduled voice conferences. It provides a distributed

conference system to allow users to join a remote conference locally, which reduces the

bandwidth usage.

Multimedia conference

Functions such as e-whiteboard, program sharing, document sharing, and e-voting are

provided. Video conferences can be held by terminals with cameras. The MS also

supports license control.


The eSpace EMS enables you to configure the hw_IMS_Conference_focus.


The eSpace EMS enables you to collect performance statistics on the following

hw_IMS_Conference_focus components:

Number of multimedia conferencesa at a certain time.

Number of multimedia users at a certain time.

Number of voice conferences at a certain time.

Number of voice users at a certain time.

Alarm Management

The eSpace EMS monitors eSpace Meeting alarms. You can view alarms and rectify them on

the eSpace EMS.

eSpace EMS




34

3.3 Topology Management

In the eSpace EMS, the topology view displays NE status and links. With this function, you

understand the network structure and operating status of network devices.

Basics

Table 3-4 Topology objects

Topology Object

Description

NE Devices managed in the eSpace EMS are referred to as NEs, for example,

the LocalNMS NE in Figure 3-12. In the topology view, different icons

represent different types of NEs.

Subnet For easy management, a large network is divided into several subnets (for

example, the spring subnet in Figure 3-12) based on a specific rule, such

as by region or device type.

Link Links represent physical or logical connections between communications

devices, for example, the link between SEE_1 NE and SEEL_2 NE in

Figure 3-12.

Figure 3-12 Topology management UI

Browsing the Topology View

Topology objects are displayed by layer.

eSpace EMS




35

In the topology view, you can view the layout of all topology objects including NEs, subnets,

and links. If there are a large number of topology objects, you can also use browse them in an

aerial view.

Creating Virtual NEs

Virtual NEs are not actual devices, and they are only for display purposes in the topology

view.

You can create or delete virtual NEs in the topology view.

Creating Virtual Links

Virtual links are not actual links, and they are only for display purposes in the topology view.

You can create or delete virtual links in the topology.

Understanding Alarm Severities

If an alarm is raised, the topology object is displayed in a color corresponding to the alarm

severity. You can easily understand the alarm conditions of NEs.

Accessing the Object Manager UI

You can quickly open the object manager UI using the shortcut menu in the topology view.

The object manager UI displays the monitoring information about NEs, such as the

performance monitoring result and alarm information.

Searching For a Topology Object

You can set a search criterion to quickly search for required topology objects.

3.4 Fault Management



eSpace EMS




36

Basics

Figure 3-13 Fault management UI

Alarm Collection Monitoring All the Alarms in Real Time

The eSpace EMS receives alarms raised by the managed NEs in real time and displays

these alarms in different ways.

You can be alerted to alarms using the alarm board, alarm sounds, and current alarm list

in real time.

Defining an Alarm

You can set the eSpace EMS to generate a performance alarm and display the alarm in

the alarm window on the client when a performance indicator reaches the specified

threshold.

Alarm Notification Alerting by Alarm Sounds

Users can be alerted by alarm sounds when alarms are raised.

You can set different alarm sounds and play durations for alarms of different severities.

Browsing the Alarm Board

You can view the number of alarms of each severity on the alarm board.

Remote Alarm Notification

The eSpace EMS can notify users of both alarms and events. If remote notification is

enabled, maintenance personnel can still learn about the alarm conditions on the entire

network outside the equipment room.

eSpace EMS




37

Maintenance personnel can be notified of alarms by email or short message.

− By short message

If remote notification by short message is enabled, you must set the short message

service (SMS) gateway and the phone number to receive short messages.

− By email

If remote notification by email is enabled, you must set the Simple Mail Transfer

Protocol (SMTP) server address and the email address to receive emails.

Maintenance personnel can set filter criteria based on alarm severity and type, to avoid

receiving alarm notifications that do not require immediate attention.

PerceivedSeverity

The perceivedSeverity field indicates how severe the corresponding fault is. There are four

severity levels: critical, major, minor, and warning.

Critical: This kind of fault has seriously affected service and broken down the system,

and it must be fixed at once. A recovery is needed in case some equipment or resource is

totally unavailable.

Major: This kind of fault has degraded the service quality and must be fixed at once in

working hours. A recovery is needed in case the service quality of some equipment or

resouce degrades.

Minor: This kind of fault has not degraded the service quality, but will bring about

damage if not checked or handled in time.

Warning: This kind of fault has not damaged the service, but the damage is potential.

Alarm Query Browsing Current Alarms

Current alarms are dynamically refreshed.

You can view uncleared or unacknowledged alarms in the current alarm list. You can

also filter out required alarms by setting a filter criterion.

Browsing Masked Alarms

You can browse and query masked alarms.

Filtering Alarms by Status

You can filter alarms by status.

Alarm status:

− Unacknowledged and uncleared

− Acknowledged and uncleared

− Unacknowledged and cleared

− Acknowledged and cleared

Querying Historical Alarms

You can set multiple search criteria to query historical alarms. Only cleared and

acknowledged alarms are recorded in the alarm history.

Viewing Alarm Details

You can view alarm details, including the alarm name, alarm severity, device name,

acknowledgement status, possible cause, and alarm location information.

You send the details to related personnel for fault identification.

eSpace EMS




38

Querying and Browsing Events

You can set multiple search criteria to query events.

Alarm Processing Disabling Alarm Reporting

Alarm records are updated dynamically. The eSpace EMS always displays the latest

alarms on the top of the alarm browse window.

When viewing an alarm, you can disable reporting of new alarms to prevent the alarms

that you are viewing from scrolling down due to newly reported alarms. You can then

enable reporting of new alarms.

Masking Alarms

If a large number of alarms are reported, you can set mask conditions based on alarm

name or alarm severity to discard alarms that do not need to be noticed. The masked

alarms will not be saved to the alarm database.

You can also set mask conditions for a certain NE or for a type of NEs.

Managing Alarm Mask Rules

You can view, add, modify, and delete alarm mask rules.

You can set an alarm mask rule for a specified MO to mask its alarms.

Clearing Alarms

You can manually clear a certain alarm or a type of alarms. In addition, the system can

automatically clear a certain alarm or a type of alarms by following the instructions from

the upper-level NMS or based on a specified rule.

Acknowledging and Unacknowleging Alarms

You can acknowledge and unacknowledge alarms.

You can unacknowledge the alarms that you have acknowledged. Then the status of the

alarms is changed to unacknowledged.

Alarm Auditing Exporting Alarm Data

You can export current alarms, historical alarms, masked alarms, and events.

Maintaining Alarm Data

You can set the maximum retention period (for example, six months) for historical

alarms. The system automatically deletes and dumps related data as specified.

You can set whether to dump the outdated data while deleting the data. If data needs to

be dumped, you also need to set a destination path for the dump.

3.5 Performance Monitoring

With this function, you can understand the performance indicators of NEs and trends of the

performance indicators. This information provides a reference to optimize and maintain the

network.

eSpace EMS




39

Basics

Figure 3-14 Performance Monitoring UI

Defining Performance Indicators

You can select the performance indicators to monitor.

After you set the performance indicators and statistical period, the eSpace EMS collects

performance data based on the specified conditions. The results are displayed in the real-time

performance monitoring view.

Monitoring Performance Indicators in Real Time

You can monitor the performance indicators of MOs in real time and therefore notice

exceptions quickly.

The monitoring results can be displayed in different types of charts (such as a bar chart or a

line chart). The charts help you learn about the changes and trends of the performance

indicators. Based on the changes and trends, you can take measures before the key indicators

reach their thresholds.

eSpace EMS




40

Figure 3-15 Real-time performance monitoring view

Defining Monitoring Views

You can add, modify, and delete monitoring views, and adjust the locations of monitoring

views.

Setting Alarm Thresholds of Performance Indicators

You can set alarm thresholds for the performance indicators of an NE, and learn about the

operating status of the NE based on the generated performance alarms.

Managing Performance Monitoring Templates

You can add, modify, delete, and define performance monitoring templates.

Querying Historical Performance Data

You can set search criteria to query historical performance data.

eSpace EMS




41

Exporting Performance Data

You can export performance data to .csv files.

Maintaining Performance Data

You can set the retention period for performance data. When the overflow conditions are met,

the performance data is automatically dumped.

3.6 Security Management

Security management is to control the eSpace EMS user permission and user roles, and ensure

security of user accounts and managed devices by means of authentication, authorization, and

encryption.

Role Management

Role management enables you to add, delete, modify, and query roles. Role permission of the

eSpace EMS is a binary group of the MO list and operation list, which means that the user can

perform the operations in the operation list for the objects in the MO list.

When you create or modify a role, you can set or modify the role permission.

By default, the system has a super administrator role which cannot be deleted and whose

permission cannot be modified. You can only modify the description and members.

User Management

User management enables you to add, delete, modify, and query users.

The administrator can set and modify user roles and the access control policies. The access

control policies control login time and login IP addresses. User role is not mandatory for a

user. If you do not have a user role, you can perform only the operations that are not

controlled by permission after login.

User status is normal, disabled, and locked.

If the consecutive failed login attempts exceed the threshold, the user account is locked.

The locked user account can unlock automatically at the configured time or can be

unlocked by the administrator.

If a user has not logged in for a long time, the user account is disabled automatically. In

addition, the user accounts can be disabled by the administrator. Only the administrator

can recover the disabled user account.

Security Policy Management

Security policies can ensure security of user accounts, passwords, and eSpace EMS.

Table 3-5 Security policies

Security Policy

Description

Password You can specify the following settings for the password policy:

eSpace EMS




42

Security Policy

Description

policy Minimum password length

Maximum attempts to enter the password the same as old passwords

Maximum number of occurrences of a character in a password

Allow special characters: space!"#$%&'()*+,-./:;<=>?@[\]^`{_|}~

Minimum time interval between password change attempts

Forcibly change an expired password

Account

policy

You can specify the following settings for the password policy:

Minimum account length

Disable account if no login for specified days

Lock duration

Automatic disable user accounts

Access

control

policies

Access control policies include:

Login time control policy

You can set the login date, time, and days of the week.

Login IP address control policy

You can set the login IP address segment.

Screen Lock

You can set whether to enable the screen lock function and the timeout duration.

For security purpose, if you want to stop performing operations for a certain period of time,

you can enable the eSpace EMS to lock the client automatically. If the screen is locked, you

need to enter the password to unlock the client.

User Session Monitoring

The eSpace EMS provides user session monitoring to monitor the login user, login time, and

login IP address to prevent attacks from malicious users and to monitor online users. The

administrator can force a user to exit the eSpace EMS.

Password Change

You can change your password and the administrator can reset the user password. New

passwords must comply with the password policy.

3.7 Log Management

Logs are stored in the eSpace EMS database. You can query logs on the eSpace EMS client.

The log information helps you rapidly identify and analyze the faults. You can set the search

criteria to query logs and analyze the query results, helping you learn about the user

operations and operation status of the eSpace EMS.

eSpace EMS




43

Table 3-6 Log types

Log Type Description

Operation logs Operation logs record all user operations, including users, operation

names, operation time, operated objects, and operation results.

System logs System logs record the significant events occurring in the system,

including system exceptions, and network faults. System logs record the

basic information, modules, severities, and operation results. System logs

help you analyze the system status and troubleshoot the faults.

Security logs Security logs record information about security operations, for example,

login or logout, password change, and user creation.

3.8 Message Tracing



Basics

Figure 3-16 Message tracing UI

Managing a Tracing Task

You can create, delete, start, or stop a tracing task and browse task attributes.

Parsing the Message

The client parses the tracing result reported by the NE.

eSpace EMS




44

Displaying Tracing Results

Tables and sequence diagrams are used to show tracing results. In addition, each record is

displayed in a tree diagram and in hexadecimal.

Analyzing Tracing Results

You can analyze the service flow and reported content in the tracing result.

Parsing the service flow: distinguishes the incomplete flow from the complete flow in

the reported message and Locates the problem through the incomplete flow. If the device

provides the flow identification, compare flows based on identifications. Messages with

the same identification are in the same flow. If the device does not provide the flow

identification, compare flows based on the sequence of the report time.

Analyzing reported content: The tracing message reported can be divided into three

levels: normal, warning, and error. Messages of different levels are in different colors.

Managing Tracing Files

After saving tracing results in files, you can download, query, or delete the tracing files.

3.9 Northbound Interface

Northbound interfaces are the external interfaces to connect the eSpace EMS and the

upper-layer NMS or other systems.

Table 3-7 Description of northbound interfaces

Interface

Function

SNM

P

Alar

m

Supports SNMP V1, SNMP V2C, and SNMP V3.

Report and

filter alarms in

real time

-

Acknowledge

and

unacknowledg

e alarms

-

Synchronize

alarms

If the connection between the upper-layer NMS and the eSpace

EMS is abnormal or the upper-layer NMS is restarted, the

upper-layer NMS can deliver the command of synchronizing

alarms to the eSpace EMS. After the eSpace EMS receives the

command, the eSpace EMS reports all active alarms to the

upper-layer NMS again. The upper-layer NMS updates the

alarms based on alarm serial number to make the alarms

consistent with those on the eSpace EMS.

Transfer clear

alarms in real

time

If the NE fault is rectified or the local maintenance personnel

manually clear an alarm, the eSpace EMS reports a clear alarm to

the upper-layer NMS. The upper-layer NMS finds the

eSpace EMS




45

Interface

Function

corresponding active alarms based on the serial numbers of the

clear alarms and clears them.

Heartbeat

mechanism

The SNMP interfaces for heartbeat check are provided for

external systems to query and set the heartbeat period. The

eSpace EMS periodically sends the heartbeat information to the

external systems to monitor the status of communication links.

eSpace EMS

Product Description 4 System Reliability



46

4 System Reliability

The eSpace EMS supports self-monitoring, backup and restoration, security hardening, and

geography disaster recovery (GDR) to ensure system reliability.

Self-Monitoring Capabilities

To ensure reliability, the eSpace EMS provides the watchdog process to monitor its own

applications and processes. If a process abnormally exits, the watchdog process automatically

restarts the process.

Backup and Recovery Capabilities

When Linux is used, the system provides the backup and recovery capabilities to full backup

and restore eSpace EMS files and database data. This ensures the reliability of the system and

database data.

Security Hardening Capability

Security of the system host is reinforced to ensure safe and stable running of the operating

system. Therefore, system services can run safely and stably.

The eSpace EMS server has the following security risks:

A large number of services and ports are opened during operating system installation,

which leaves the system vulnerable to malicious attacks.

No strict restrictions are imposed on the file rights and environment variables, which

increases security vulnerabilities of the system.

To achieve security hardening, you can add, modify, or tailor the modules and components of

the system, and shield and eliminate the defects and security vulnerabilities of the system.

Geographical Redundancy Capability

To ensure service continuity, establish the same service system of the PM in the RM. The PM

synchronizes data to the RM periodically. When a disaster such as fire or earthquake occurs in

the PM, services can be switched to the RM. This is called geographical redundancy.

Generally, the PM provides services. When a disaster occurs in the PM, the eSpace EMS

service can be switched manually to the RM, which reduces the service interruption duration.

When Linux is used, the eSpace EMS provides GDR to support geographical redundancy.

eSpace EMS

Product Description 5 Technical Specifications



47

5 Technical Specifications

Table 5-1 Performance indicators

Indicator Value

Maximum number of

topology nodes allowed

The values vary according to server configurations:

20,000 for a Linux server with the following minimum

configuration: 2 CPUs (for example, 2 x E5506), 8-GB

memory, 2 x 300-GB disks

50,000 for a Linux server with the following minimum



1000 for a Windows server with the following minimum



Maximum number of

current alarms allowed

20,000

Maximum number of

historical alarms allowed

15,000,000

Maximum number of

events allowed

15,000,000

Maximum number of logs

allowed

300,000

Maximum alarm delay 30 seconds

Delay for querying 100,000

alarms

5 seconds

Maximum alarm

processing capabilities

100 alarms per second

Maximum number of

objects under a subnet

500

Maximum number of

layers supported in the

topology view

11

eSpace EMS

Product Description 5 Technical Specifications



48

Indicator Value

Maximum number of users

logged into the eSpace

EMS at a time.

100

One IP phone or SBC is equal to one equivalent NE, one IAD, GS8 or EGW is equal to five

equivalent NEs, and one IP PBX is equal to 50 equivalent NEs.

The equivalent NEs managed by the eSpace EMS are calculated in the following formula: IP PBX x

50 + (IAD + GS8 + EGW) x 5 + IP Phone + SBC. The total number cannot exceed the maximum

number of topology nodes allowed.

eSpace EMS

Product Description 6 Acronyms and Abbreviations



49

6 Acronyms and Abbreviations

A

AA Access Agent

AS Application Server

B

BMP Business Management Point

C

Call As Call Application Server

CSV Comma-Separated Values

E

eConf AS Enterprise Conference Application Server

EMS Element Management System

ESG Enterprise Service Gateway

F

FTP File Transfer Protocol

G

GDR Geography Disaster Recovery

I

ICMP Internet Control Message Protocol

eSpace EMS

Product Description 6 Acronyms and Abbreviations



50

IP Internet Protocol

L

LAN Local Area Network

M

MAA Mobile Access Agent

MOS Mean Opinion Score

N

NGIN Next Generation Intelligent Network

NMS Network Management System

P

PGM Presence Group Messaging

PM Performance Management

S

SFTP Secure File Transfer Protocol

SMTP Simple Mail Transfer Protocol

SNMP Simple Network Management Protocol

SOAP Simple Object Access Protocol

T

TCP Transmission Control Protocol

TOPO Topology Management

U

UOA Uniform Operation Maintenance Agent

espace ems product description (v200r001c02spc200_04)

Documents