eSpace UC Feature Description Ver 1 - Huawei - Building … Call Barring Policies ..... 29 2.4...

eSpace UC

Feature Description

Issue 04

Date 2013-05-08

HUAWEI TECHNOLOGIES CO., LTD.

Issue 04 (2013-05-08) Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd. i

Copyright © Huawei Technologies Co., Ltd. 2013. 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 a 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://enterprise.huawei.com

eSpace UC

Solution Description Contents


Copyright © Huawei Technologies Co., Ltd.

ii

Contents

1 Overview ..................................................................................................................................... 8

1.1 UC Product Overview ................................................................................................................................................... 8

1.2 UC Network ................................................................................................................................................................ 11

2 IP Telephony Functions ............................................................................................................ 12

2.1 Basic Voice Services ................................................................................................................................................... 12

2.1.1 Voice Communication .............................................................................................................................................. 12

2.1.2 Point-to-Point Video Call ......................................................................................................................................... 12

2.1.3 Call Rights Control .................................................................................................................................................. 12

2.1.4 Number Analysis and Processing............................................................................................................................. 13

2.1.5 Voice Processing and Codec .................................................................................................................................... 13

2.1.6 SNTP ....................................................................................................................................................................... 13

2.1.7 Fax ........................................................................................................................................................................... 13

2.2 Supplementary Voice Services .................................................................................................................................... 14

2.2.1 Local Number Query Service .................................................................................................................................. 14

2.2.2 Calling Line Identification Services ........................................................................................................................ 14

2.2.3 Call Forwarding Services ......................................................................................................................................... 15

2.2.4 Call Transfer Service ............................................................................................................................................... 16

2.2.5 Call Hold Service ..................................................................................................................................................... 17

2.2.6 Call Park Service ..................................................................................................................................................... 17

2.2.7 Call Waiting Service ................................................................................................................................................ 17

2.2.8 Three-Party Call Service .......................................................................................................................................... 18

2.2.9 Password Change Service ........................................................................................................................................ 18

2.2.10 Number Portability Service ................................................................................................................................... 18

2.2.11 Simultaneous Ringing Service ............................................................................................................................... 19

2.2.12 Sequential Ringing Service .................................................................................................................................... 20

2.2.13 Abbreviated Dialing Service .................................................................................................................................. 20

2.2.14 Co-Group Pickup Service ...................................................................................................................................... 20

2.2.15 Designated Pickup Service .................................................................................................................................... 21

2.2.16 Multi-Number Service ........................................................................................................................................... 21

2.2.17 Number Replacement Services .............................................................................................................................. 21

2.2.18 ACB Service .......................................................................................................................................................... 22

2.2.19 Secretary Services .................................................................................................................................................. 23

2.2.20 DND Service .......................................................................................................................................................... 24

eSpace UC




iii

2.2.21 Absent User Service ............................................................................................................................................... 24

2.2.22 Alarm Clock Service .............................................................................................................................................. 24

2.2.23 Hotline Services ..................................................................................................................................................... 25

2.2.24 Privilege Services .................................................................................................................................................. 25

2.2.25 DID Service ........................................................................................................................................................... 26

2.2.26 IVR ........................................................................................................................................................................ 26

2.2.27 PBX Group Line Selection Service ....................................................................................................................... 26

2.2.28 Distinctive Ring Tone Service ............................................................................................................................... 27

2.2.29 Remote Service Activation .................................................................................................................................... 27

2.2.30 Deregistration of All Services ................................................................................................................................ 27

2.2.31 Hunting Group ....................................................................................................................................................... 27

2.2.32 Phone to Phone Paging Group ............................................................................................................................... 28

2.3 Advanced Services ...................................................................................................................................................... 28

2.3.1 User Rights Management by Level .......................................................................................................................... 28

2.3.2 Call Barring Policies ................................................................................................................................................ 29

2.4 Intelligent Routing ...................................................................................................................................................... 33

2.4.2 Routing by Time Segment ....................................................................................................................................... 33

2.4.3 Routing by Charge Rate ........................................................................................................................................... 33

2.4.4 Rerouting upon Call Failures ................................................................................................................................... 33

2.4.5 Route Load Balancing ............................................................................................................................................. 34

2.4.6 Routing by Percentage ............................................................................................................................................. 34

2.4.7 Routing by User Right Level ................................................................................................................................... 34

2.4.8 Trunk Link Balancing .............................................................................................................................................. 34

2.5 Voice Conference ........................................................................................................................................................ 35

2.5.1 Scheduled Conference ............................................................................................................................................. 36

2.5.2 Instant Conference ................................................................................................................................................... 36

2.6 IP Phone Services ....................................................................................................................................................... 37

2.7 SoftPhone .................................................................................................................................................................... 37

2.8 Console System .......................................................................................................................................................... 38

2.8.1 ACD ......................................................................................................................................................................... 38

2.8.2 Basic Call ................................................................................................................................................................. 38

2.8.3 Agent Functions ....................................................................................................................................................... 38

2.8.4 Night Service ........................................................................................................................................................... 40

2.8.5 Corporate Directory ................................................................................................................................................. 40

2.8.6 Call History .............................................................................................................................................................. 41

2.8.7 Notifying Incoming Calls ........................................................................................................................................ 41

2.8.8 Service Management................................................................................................................................................ 41

2.8.9 Other Functions ....................................................................................................................................................... 42

2.8.10 System Configuration ............................................................................................................................................ 43

2.9 CDR ............................................................................................................................................................................ 43

2.9.1 CDRServer ............................................................................................................................................................... 43

eSpace UC




iv

3 UC Functions ............................................................................................................................ 45

3.1 ONLY Service ............................................................................................................................................................. 45

3.2 IM Service .................................................................................................................................................................. 45

3.2.1 Two-Party Conversation .......................................................................................................................................... 45

3.2.2 Group Chat .............................................................................................................................................................. 45

3.2.3 File Transfer ............................................................................................................................................................. 46

3.2.4 Emoticon or Image Sending and Receiving ............................................................................................................. 46

3.2.5 IM History ............................................................................................................................................................... 46

3.2.6 Special Content Identification ................................................................................................................................. 46

3.2.7 System-Level Configuration .................................................................................................................................... 46

3.2.8 Avatar and Signature Customization ........................................................................................................................ 46

3.2.9 Area and Communication Control ........................................................................................................................... 46

3.2.10 User Permission Control ........................................................................................................................................ 47

3.2.11 Statistics Collection and Audit ............................................................................................................................... 47

3.3 Status Presentation ...................................................................................................................................................... 47

3.4 Directory ..................................................................................................................................................................... 48

3.4.1 Corporate Directory ................................................................................................................................................. 48

3.4.2 Personal Directory ................................................................................................................................................... 48

3.5 eSpace Desktop and IP Phone Interaction .................................................................................................................. 49

3.5.1 Binding .................................................................................................................................................................... 49

3.5.2 Enabling/Disabling the Interaction Function ........................................................................................................... 49

3.5.3 Status Synchronization ............................................................................................................................................ 49

3.5.4 Call Control ............................................................................................................................................................. 49

3.5.5 Assistant Dialing ...................................................................................................................................................... 49

3.5.6 Controlling the Called IP Phone .............................................................................................................................. 49

4 Multimedia Conference ............................................................................................................ 50

4.1 Document Sharing ...................................................................................................................................................... 50

4.2 Desktop Sharing.......................................................................................................................................................... 51

4.3 e-Whiteboard .............................................................................................................................................................. 51

4.4 Poll .............................................................................................................................................................................. 51

4.5 File Transfer ................................................................................................................................................................ 52

4.6 Note Taking ................................................................................................................................................................ 52

4.7 Bulletin ....................................................................................................................................................................... 52

4.8 Text Chat ..................................................................................................................................................................... 52

4.9 Video Conference ....................................................................................................................................................... 52

5 eSpace UMS .............................................................................................................................. 54

5.1 T-Star UMS ................................................................................................................................................................. 54

5.1.2 Voice Mailbox .......................................................................................................................................................... 55

5.1.3 Fax Mailbox ............................................................................................................................................................. 55

5.1.4 Message Forwarding ................................................................................................................................................ 56

5.1.5 Restrictions .............................................................................................................................................................. 56

eSpace UC




v

5.1.6 Others....................................................................................................................................................................... 56

5.2 Movius UMS .............................................................................................................................................................. 56

5.2.1 Voice Mailbox .......................................................................................................................................................... 57

5.2.2 Fax Mailbox ............................................................................................................................................................. 57

5.2.3 Direct Callback ........................................................................................................................................................ 58

5.2.4 Restrictions .............................................................................................................................................................. 58

5.2.5 Greetings .................................................................................................................................................................. 58

6 eSpace Desktop ......................................................................................................................... 59

6.1 Basic Call .................................................................................................................................................................... 60

6.1.1 Voice Call ................................................................................................................................................................. 60

6.1.2 Video Call ................................................................................................................................................................ 60

6.1.3 Call Transfer ............................................................................................................................................................ 60

6.1.4 Call Hold and Unhold .............................................................................................................................................. 60

6.1.5 Two-Stage Dialing ................................................................................................................................................... 61

6.1.6 Call Recording ......................................................................................................................................................... 61

6.1.7 CLIP......................................................................................................................................................................... 61

6.1.8 Historical Records ................................................................................................................................................... 61

6.1.9 Integration with USB Phones .................................................................................................................................. 62

6.1.10 Status-based Incoming Call Routing ..................................................................................................................... 62

6.1.11 Call Redirection ..................................................................................................................................................... 62

6.1.12 MWI....................................................................................................................................................................... 62

6.2 eSpace Desktop and IP Phone Interaction .................................................................................................................. 62

6.3 Status Presentation ...................................................................................................................................................... 62

6.4 IM Service .................................................................................................................................................................. 62

6.5 Instant Conference ...................................................................................................................................................... 62

6.5.1 IM Conference ......................................................................................................................................................... 63

6.5.2 Instant Voice Conference ......................................................................................................................................... 63

6.5.3 Instant Multimedia Conference................................................................................................................................ 63

6.5.4 Smooth Conference Upgrade ................................................................................................................................... 63

6.6 Scheduled Multimedia Conference ............................................................................................................................. 63

6.7 ONLY Service ............................................................................................................................................................. 64

6.8 SMS Messages and Emails ......................................................................................................................................... 64

6.9 Corporate Directory .................................................................................................................................................... 64

6.10 Personal Directory .................................................................................................................................................... 64

6.11 Enterprise Bulletin .................................................................................................................................................... 65

6.12 Self-Service .............................................................................................................................................................. 65

6.12.1 Conference Management ....................................................................................................................................... 65

6.12.2 Service Registration ............................................................................................................................................... 65

6.12.3 CDR Query ............................................................................................................................................................ 65

6.12.4 ONLY Service Configuration................................................................................................................................. 65

6.12.5 Personal Account Maintenance .............................................................................................................................. 65

eSpace UC




vi

6.13 My Workspace .......................................................................................................................................................... 65

6.14 Other Functions ........................................................................................................................................................ 66

6.14.1 Login ...................................................................................................................................................................... 66

6.14.2 System Configuration ............................................................................................................................................ 66

6.14.3 Installation and Upgrade ........................................................................................................................................ 66

7 eSpace Mobile ........................................................................................................................... 67

7.2 Startup and Login ....................................................................................................................................................... 68

7.3 Personal Information .................................................................................................................................................. 68

7.4 Personal Directory ...................................................................................................................................................... 68

7.5 Corporate Directory .................................................................................................................................................... 69

7.6 IM Service .................................................................................................................................................................. 69

7.7 Audio Service.............................................................................................................................................................. 69

7.8 Multiple Languages .................................................................................................................................................... 70

7.9 Configuration .............................................................................................................................................................. 70

8 Operation and Maintenance .................................................................................................... 71

8.1 eSpace BMU ............................................................................................................................................................... 71

8.1.1 Common User Functions ......................................................................................................................................... 71

8.1.2 Administrator Functions .......................................................................................................................................... 73

8.2 esight ........................................................................................................................................................................... 84

8.2.2 NE Connection......................................................................................................................................................... 85

8.2.3 NE Management ...................................................................................................................................................... 86

8.2.4 Topology Management ............................................................................................................................................ 88

8.2.5 Alarm Management ................................................................................................................................................. 89

8.2.6 Performance Monitoring .......................................................................................................................................... 92

8.2.7 Security Management .............................................................................................................................................. 93

8.2.8 Log Management ..................................................................................................................................................... 94

8.2.9 Northbound Interface ............................................................................................................................................... 95

8.2.10 Multiple Languages ............................................................................................................................................... 95

8.3 eSpace LMT ............................................................................................................................................................... 95

8.3.2 System Architecture ................................................................................................................................................. 96

8.3.3 System Network ....................................................................................................................................................... 97

8.3.4 Configuration Management ..................................................................................................................................... 97

8.3.5 Maintenance Management ....................................................................................................................................... 98

8.3.6 Fault Management ................................................................................................................................................... 99

8.3.7 Log Management ..................................................................................................................................................... 99

8.3.8 LMT Specifications ................................................................................................................................................. 99

9 Reliability ............................................................................................................................... 101

9.1 IP PBX Reliability .................................................................................................................................................... 101

9.1.1 Power Module Backup........................................................................................................................................... 101

9.1.2 Main Control Board Hot Standby .......................................................................................................................... 101

9.1.3 Load Balancing of Resource Boards ...................................................................................................................... 101

eSpace UC




vii

9.1.4 Single/Dual/Triple Network Port Mode ................................................................................................................. 101

9.1.5 Traffic Control and Overload Protection ............................................................................................................... 102

9.1.6 Connection Event Recording and Attack Detection............................................................................................... 102

9.2 Network Reliability .................................................................................................................................................. 102

9.2.1 Service Server in Two-Node Cluster ..................................................................................................................... 102

9.2.2 Two-Node Clusterand Local Regeneration ............................................................................................................ 103

10 Openness and Integration .................................................................................................... 104

10.1 Integration with Outlook ......................................................................................................................................... 104

10.2 Synchronization on the Active Directory ................................................................................................................ 104

10.3 Connecting to Huawei Telepresence ....................................................................................................................... 105

10.4 Integration with the OCS ........................................................................................................................................ 107

1 Overview

1.1 UC Product Overview Huawei Unified Communications (UC) is a new communications mode that integrates

computer technologies with traditional communications technologies. Based on our

experienced application of communications technologies and understanding of customer

requirements, Huawei developed the UC solution based on Voice over IP (VoIP) and Next

Generation Network (NGN). Huawei UC solution complies with various standards such as

those of the International Telecommunications Union - Telecommunication Standardization

Sector (ITU-T) and Internet Engineering Task Force (IETF). The solution provides

distinguished services and flexible networks, which helps enterprise customers improve

benefits and efficiency.

Huawei UC solution is an end-to-end solution composed of three architectural layers: service

application layer, control layer, and terminal access layer. The solution provides:

� Various supplementary services, multimedia services, and unified messaging services in

addition to basic voice services.

� Open interfaces and flexible networks.

� Backup and redundancy, load sharing, and overload control functions.

� Powerful management tools for users to easily perform operations and maintenance.

The solution also meets carrier-class performance requirements and ensures service quality.

Figure 1-1 Huawei eSpace UC products

Main network elements (NEs) on the Huawei UC solution network are:

� IP private branch exchange (PBX)

eSpace U19xx series IP PBX is a core device of Huawei UC solution. As a small-scale

NGN system and an IP PBX device, eSpace U19xx series IP PBX integrates functions of

all NGN components and provides efficient and high-quality voice services for

enterprise and industry customers. eSpace U19xx series IP PBX can be connected to the

Public Switched Telephone Network (PSTN) using a digital trunk or an analog trunk.

− eSpace U1910 supports a maximum of 100 IP phone users or 96 analog phone users.

− eSpace U1930 supports a maximum of 300 IP phone users or 224 analog phone users.

− eSpace U1980 supports a maximum of 20,000 users.

� eSpace Business Management Unit (BMU)

Deployed in the Browser/Server (B/S) structure, eSpace BMU integrates the functions of

self-service, service configuration and management, CDR management, conference call

management, number management, department management, and system management,

and provides them to users on web pages. In addition, the BMU can easily integrate

third-party services.

� eSpace Element Management System (eSight)

Deployed in the B/S structure, esight manages all devices and terminals (such as eSpace

U19xx IP PBX, IAD, IP phone, SBC, wireless gateway, and switch) on the UC network.

SBC is short for Session Border Controller. On ESIGHT web pages, users can deploy a

site, perform routine maintenance, rectify faults, and perform upgrade and capacity

expansion.

� eSpace Local Management Terminal (LMT)

eSpace LMT is used to quickly deploy sites and manage faults, configuration,

maintenance, security, and logs. eSpace LMT can manage eSpace U19xx series IP PBX.

� Console system

Communicating with the IP PBX, the console system provides functions for attendants

who can use the basic voice call, incoming call forwarding, incoming call queuing,

specified-attendant answering, call hold for multiple calls, break-in, and forced release

services.

� eSpace Desktop

eSpace Desktop provides audio and video call functions, email sending, instant

messaging (IM), instant conference, scheduled conference, and call fee query.

� eSpace integrated access device (IAD)

eSpace IAD is a VoIP and fax over IP (FoIP) media access gateway. The IAD provides

efficient and high-quality voice services based on the world-wide IP network (Internet or

enterprise intranet).

� IP phone

IP phone is a multimedia terminal that supports Session Initiation Protocol (SIP). IP

phones are connected to the IP network, instead of PSTN. Popular IP phone models are

eSpace 7810, eSpace7820, eSpace 7830, eSpace 7850, eSpace 7870, eSpace 6805,

eSpace 6810, eSpace 6830, eSpace 6850, and eSpace 6870.

Figure 1-2 IP phone series

� Unified Message System (UMS) server

The UMS stores and manages messages from different sources in a unified manner, and

provides voice mailbox and fax mailbox services. Users can retrieve voice and fax

messages anytime, anywhere.

Users can obtain voice messages using phones, from the mailbox, or on web pages.

Messages retrieved from emails and web pages are audio recordings.

Users can retrieve fax messages from fax machines and mailbox, or on web pages. Users

can also use phones to send fax messages to a specified fax machine for printing by

following interactive voice response (IVR) announcements.

� eSpace Meeting server

eSpace Meeting server provides multimedia conferences. They provide data

collaboration and video conference functions in addition to the voice conference

function. In a multimedia conference, users can share the desktop, files, and media, use

e-whiteboard, polling, text chat, bulletin, and note, and transfer files.

1.2 UC Network

Huawei UC solution V1.1 uses eSpace U19xx series IP PBX as the access gateway to

construct the unified call control module. The IP PBX works with various UC service servers

to provide UC services. eSpace U19xx series IP PBX or enterprise gateway (EGW) is

deployed based on user capacity and other requirements. Working with SBC and SSL VPN

(SVN), access gateways ensures access security of voice and UC services.

Figure 1-3 shows the typical network of Huawei UC solution.

Figure 1-3 Typical network of Huawei UC solution

� eSpace U1980 is deployed at the headquarters to control calls on the entire network.

eSpace U1980, eSpace U1930, eSpace U1910, IAD, or EGW can be deployed in a

branch as a local gateway to allow local outgoing PSTN calls and provide self switching.

� Various service servers at the headquarters provide multimedia conference, IM, eServer,

MAA , and SoftConsole services on the entire network. eSpace BMU manages services.

esight manages devices such as IP PBX, IAD, IP phone, SBC, EGW, and wireless

gateways. eSpace LMT deployed in branches provides local deployment and

maintenance functions.

� The UC solution provides various types of terminals including analog phone, IAD, IP

phone, video phone, eSpace Desktop, eSpace mobile client, and SoftConsole.

Huawei Confidential Page 12

2 IP Telephony Functions

2.1 Basic Voice Services

2.1.1 Voice Communication

eSpace U19xx series IP PBX supports basic voice communication, including:

� Intra-office call

Intra-office users under eSpace U19xx series IP PBX can call each other. A user terminal

can be a broadband or narrowband terminal that the IP PBX supports. Voice calls can be

made between intra-office users.

� Narrowband trunk-based communication

eSpace U19xx series IP PBX connects to the PSTN or TDM PBX through AT0 analog

trunks or digital trunks such as primary rate interface (PRI), R2, SS7 (ISUP/TUP), or Q

Signaling (QSIG). SS7 is short for signaling system No. 7, ISUP for integrated services

digital network user part, and TUP for telephone user part. Users can make voice calls

and receive incoming calls based on narrowband trunks.

� Broadband trunk-based communication

eSpace U19xx series IP PBX uses the SIP trunk to connect to the IP PBX, softswitch, or

IMS. Voice calls can be made between intra-office users and the users under other

devices.

eSpace U19xx series IP PBX can be connected to narrowband and broadband terminals

(including analog phones, IP phones, eSpace Desktops, and SIP SoftConsole), and access

devices (including IAD).

2.1.2 Point-to-Point Video Call

eSpace U19xx series IP PBX supports point-to-point video communication between intra-

office users and enables users to use eSpace Desktops to communicate with each other

through the SIP trunk. The video codec is H.263.

2.1.3 Call Rights Control

eSpace U19xx series IP PBX allows users to make intra-office calls, local calls, national toll

calls, and international toll calls. In addition, a maximum of 32 types of call rights can be

defined to restrict users from making specified types of calls.


2.1.4 Number Analysis and Processing

eSpace U19xx series IP PBX analyzes the calling and called numbers based on their prefix

and length to control incoming and outgoing call rights. The calling number is analyzed

before the called number. Numbers with the same prefix are analyzed based on the length.

� A number prefix is the first digit or first few digits in a number to specify the number

attribute.

� eSpace U19xx series IP PBX can analyze and process a regular number or prefix

containing a maximum of 32 digits and an intra-office number containing a maximum of

eight digits.

� eSpace U19xx series IP PBX can analyze a maximum of 1024 calling numbers and a

maximum of 2048 called numbers.

� Prefixes can identify emergency, intra-office, local, intra-office and local, national, and

international calls, and support 32 levels of customized call rights. The intra-office and

local prefixes are applied when the intra-office prefix is the same as the local outgoing

prefix.

� eSpace U19xx series IP PBX can insert, change, or delete digits in calling and called

numbers. The length of a changed number cannot exceed the maximum value. A

maximum of 1024 change types are supported.

2.1.5 Voice Processing and Codec

eSpace U19xx series IP PBX supports various codec formats including G.711 (A-Law/U-

Law), G.723.1 (5.3K/6.3K), G.729a/b, and Internet Low Bitrate Codec (iLBC), and G.722.1

negotiation. In addition, eSpace U19xx series IP PBX supports voice codec switch and

selection of their priorities.

� eSpace1910 and eSpace1930 do not support G.723.1.

� G.722.1 is a broadband codec mode, and eSpace U19xx series IP PBX supports only

negotiation.

eSpace U19xx series IP PBX supports voice activity detection (VAD), comfort noise generator

(CNG), echo cancellation (EC), automatic gain control (AGC), jitter buffer, and packet loss

compensation (PLC) to provide high-quality voice services. In addition, eSpace U19xx series

IP PBX supports type of service (TOS) and differentiated services code point (DSCP) to make

voice streams be transmitted preferentially, supports Real-Time Transport Control Protocol

(RTCP), and provides statistical items including the number of received and sent RTP packets,

number of received and sent bytes, time delay, jitter, and packet loss rate.

2.1.6 SNTP

eSpace U19xx series IP PBX can function as both the Simple Network Time Protocol (SNTP)

server and the SNTP client to synchronize time to or from other network devices. Time

synchronization is implemented in the unicast mode.

2.1.7 Fax

eSpace U19xx series IP PBX supports T.30 faxes in the circuit switched domain and T.38

faxes in the packet switched domain, and transparent transmission of G.711 faxes.

� The end-to-end delay for transmitting signals using a fax machine cannot exceed 3

seconds.


It is recommended that no more than four T.38 code switching gateways be deployed on

the network.

� For transparent transmission, eSpace U19xx series IP PBX converts voice calls in G.723

and G.729 encoding modes into G.711 faxes.

2.2 Supplementary Voice Services

2.2.1 Local Number Query Service

This service allows users to dial a specified prefix to query the local number or the one

number link you (ONLY) number.

� If the user is an intra-office user, the number that the user queries is the one configured in

the IP PBX. If the user has enabled the ONLY service, the user dials *128 to query the

local number and *125 to query the ONLY number.

� This service requires voice resources. If all voice resources are occupied, an intra-office

user can hear only the busy tone after dialing the specified prefix.

2.2.2 Calling Line Identification Services

2.2.2.1 CLIP

The calling line identification presentation service (CLIP) service allows a user's phone to

display the calling number if the calling party does not subscribe to the calling line

identification restriction (CLIR) service.

� The maximum length of the calling number displayed on the called party's phone is also

32 digits.

2.2.2.2 CLIR

The CLIR service prevents the calling number from being displayed on the called party's

phone even if the called party has enabled the CLIP service.

2.2.2.3 Calling Party Name Display

This service allows the IP phone of the called party to display the calling party's name stored

by the BMU in the eSpace U19xx series IP PBX during registration. eSpace U19xx series IP

PBX enables signaling to carry the calling party's name.

� eSpace 68xx and 78xx series IP phones support the calling party name display service.

�

CNIP

After user A (an enterprise member) enables the calling name identification presentation

(CNIP) service, the name of the calling party can be displayed on user A's terminal.

The CNIP service is available only to called parties.

When there is an incoming call to user A who enables the CNIP service, user A's terminal

queries the name of the calling party from the personal address book based on the calling

number and displays the name if it is found.


If the name is not found in the personal address book, user A's terminal queries the name from

the corporate directory, outlook or lotus address book (LDAP) and displays the name if it is

found.

If the name is not found in the corporate directory, user A's terminal extracts the name from

the call signaling and displays the name.

If the name cannot be extracted from the call signaling, user A's terminal displays the calling

number.

The CNIP service is valid only when the CLIP service is enabled.

� If user A enables the CLIP and CNIP services and the calling party enables the CLIR service,

the name of the calling party cannot be displayed on user A's terminal.

2.2.2.4 CLIRO

The calling line identification restriction override (CLIRO) service allows the calling number

to be displayed on the called party's phone even if the calling party has enabled the CLIR

service.

2.2.3 Call Forwarding Services

Users can configure the default call forwarding mode and the forwarded-to number in

batches.

Table 2-1 describes call forwarding specifications supported by eSpace U19xx series IP PBX.

Table 2-1 Call forwarding specifications

Specification eSpace U1980

eSpace U1930

eSpace U1910

Total number of forwarded calls 1024 300 300

Number of concurrently forwarded calls

(When the call forwarding tone is not played)

1000 100 30

2.2.3.5 CFU

The call forwarding unconditional (CFU) service allows all calls destined for a user to be

forwarded to a specified number unconditionally.

2.2.3.6 CFB

The call forwarding busy (CFB) service allows a call destined for a user to be forwarded to a

specified number when the user is busy.

� The priority of the CFU service is higher than that of the CFB service.


2.2.3.7 CFNR

The call forwarding on no reply (CFNR) service allows a call destined for a user to be

forwarded to a specified number when the user does not answer within 20 seconds.

� The priority of the CFNR service is lower than those of the CFU service and call waiting

service.

2.2.3.8 CFO

The call forwarding offline (CFO) service allows a call destined for a user to be forwarded to

a specified number when the user is not registered.

� The priority of the CFO service is lower than that of the CFU service.

� The users of IP phones and eSpace Desktops can enable the CFO service.

2.2.3.9 CFC

If a user enables the Call Forwarding Conditional (CFC) service, all incoming calls are

forwarded to a specified number according to the preset forwarding conditions. The

forwarding conditions are as follows:

� Call forwarding according to a calling number.

� Call forwarding by time segment and user status (busy, no reply, or unconditionally).

� Call forwarding by intra-office calls, inter-office calls, and user status (busy, no reply, or

unconditionally).

If the forwarded-to user or all ONLY users do not answer, the calling party is asked to leave a

message in the voice mailbox.

Table 2-2 describes service specifications supported by eSpace U19xx series IP PBX.

Table 2-2 Service specifications


eSpace U1930

eSpace U1910

Total number of users 2000 30 10

Number of forwarding conditions preset for a user

10 10 10

Total number of forwarding conditions

2000 x 10 30 x 10 10 x 10

2.2.4 Call Transfer Service

The call transfer service enables a user to transfer an ongoing call to a third party.

� To transfer a call on an analog phone, press the hookflash or the R (Flash) key during a

conversation and dial the called number.

� To transfer a call on an IP phone, press the Hold or Transfer key.


2.2.4.10 Unconditional Call Transfer

If a user enables the unconditional call transfer service, the user can hold an ongoing call and

make a call to a third party. When the third party's phone rings, the user exits the

conversation, and the call is transferred to the third party.

2.2.4.11 Negotiated Call Transfer

If a user enables the negotiated call transfer service, the user can hold an ongoing call and

make a call to a third party. After negotiating with the third party, the user exits the

conversation, and the call is transferred to the third party.

2.2.5 Call Hold Service

This service enables a user to hold an ongoing call and unhold it when necessary.

� To hold a call on an analog phone, press the hookflash or the R (Flash) key.

� To hold a call on an IP phone, press the Hold key.

2.2.6 Call Park Service

This service allows a user to hold a call on a phone and unhold the call on another intra-office

phone. If the call is not resumed within the park duration specified in the LMT or ESIGHT,

the system releases the call, and the user hears the busy tone.

� IP phones use the call transfer mode. After a call is established, press the TRNF key on

an IP phone and dial the call park service prefix to park the call.

� Analog phones use the following mode: After a call is established, press the hookflash or

R (Flash) key and dial the prefix of the call park service to park the call after hearing the

special dialing tone.

2.2.7 Call Waiting Service

This service allows a user already on a call to hear the call waiting tone when a third party

calls the user. The user can choose to accept, reject, or ignore the new call.

� The priority of call waiting service is lower than the priorities of the do not disturb

(DND) service, alarm clock service, and absent user service.

� The call waiting service is exclusive to the CFU service, CFB service, and instant hotline

service.

The following describes an application scenario of the call waiting service:

Assume that user A has enabled the call waiting service.

� If user A uses a POTS telephone, the procedure for using the call waiting service is as

follows:

User A is in a conversation with user B. User C calls user A. User A hears the call

waiting tone, and user C hears the ring back tone (RBT). Within 15 seconds, user A can:

− Reject the call from user C.

Continue the conversation with user B. The call waiting tone automatically

disappears after 15 seconds, and user C hears the busy tone.

− End the call with user B, and start talking with user C.

User A presses the hookflash and then presses 1 after hearing an announcement.


− Hold the call with user B, and start talking with user C.

User A presses the hookflash and then presses 2 after hearing an announcement.

When talking with user C, user A can press the hookflash and then 2 to resume the call

with user B, and user C listens to the waiting tone.

When talking with user A, user C hangs up. After hearing an announcement, user A can

press the hookflash to resume the call with user B. If user A hangs up during the

conversation with user C, users B and C will hear the busy tone.

� If user A uses a SIP phone supporting the call waiting service, for example, eSpace 6850,

the procedure for using the call waiting service is as follows:

Assume that user A and user B are in a conversation at line 1. The line 1 indicator is on.

User C calls user A. The corresponding indicator of another line (for example, line 2) on

the user A's phone is on.

If user A wants to talk with user C, user A presses the key corresponding to the line (line

2 in the preceding example) and begins talking with user C.

The call between user A and user B is held, and user B hears the call hold tone. When

talking with user C, user A can press the key corresponding to line 1 to hole the call with

user C and resume the call with user B.

2.2.8 Three-Party Call Service

This service allows a calling or called party to initiate a call to a third party without ending the

current conversation. The party who initiates the call can then start a three-party conversation

or talk to the other two parties separately.

¡Error! No se encuentra el origen de la referencia. Describes three-party call service

specifications supported by eSpace U19xx series IP PBX.

2.2.9 Password Change Service

This service allows users to change the service password as prompted. The maximum length

of a password is 4 digits. The service password is used in the outgoing call barring, password-

based call barring, ONLY, and all services cancellation services.

2.2.10 Number Portability Service

When a user's location changes, this service allows the user to retain the original phone

number. This service is implemented based on the ONLY service. Users can bind a fixed-line

phone number to another intra-office phone. For details, see ONLY service.

The following describes an application scenario of the number portability service:

Assume that user A has enabled the number portability service. User A needs to change the

location and use another phone (phone B) instead of phone A.


Figure 2-1 Number portability scenario

User A wants to retain the original phone number 8000 after moving to the new location. To

implement this, user A must proceed as follows:

In this example, the number portability service code is 85.

� Before moving from office A

Dial #85*password# on phone A to unbind the ONLY number 8000 from phone A. In

the preceding number, password is the ONLY password. The default password is

1234. You can use the password change service to change the password. For details,

see 2.2.9 Password Change Service.

� After arriving at office B

− Dial #85*password# on phone B to unbind the ONLY number 9000 from phone B. In

the preceding number, password is the ONLY password.

− Hang up.

− Dial *85*TN*password# on phone B. In the preceding number, TN is the original

ONLY number 8000, and password is the password corresponding to the ONLY

number 8000.

After the preceding procedure, the original phone number 8000 becomes the number of the

new phone, and all services and rights are retained.

2.2.11 Simultaneous Ringing Service

If user A has enabled the simultaneous ringing service and sets user B's phone number to the

simultaneous ringing number, user B's phone will also ring when a user calls user A.

� The simultaneous ringing service can be enabled only for intra-office users; however,

simultaneous ringing users can be set to outer-office users. If an AT0 user is set to a

simultaneous ringing user, the peer device must support polarity reversal signals, and the

IP PBX must be configured correctly.

� A maximum of 10 simultaneous ringing numbers can be configured for a user.

� eSpace U19xx series IP PBX allows forwarding between all intra-office users to enable

the simultaneous ringing service and sequential ringing service. The total number of

these users cannot exceed the maximum value.

� The maximum length of the simultaneous ringing number is also 32 digits.


� When an analog phone number is set to an ONLY number, the phone user does not

support simultaneous ringing when busy.

2.2.11.12 Sequential Ringing Service

If user A has enabled the sequential ringing service and sets user B's phone number to the

sequential ringing number, user B's phone will start ringing when user A does not answer an

incoming call within 20 seconds.

� The sequential ringing service can be enabled only for intra-office users; however, the

sequential ringing users can be set to outer-office users. If an AT0 user is set to a

sequential ringing user, the peer device must support polarity reversal signals, and the IP

PBX must be configured correctly.

� A maximum of two sequential ringing numbers can be configured for a user (excluding

the local number).

� eSpace U19xx series IP PBX allows all intra-office users to enable the simultaneous

ringing service and sequential ringing service. The total number of these users cannot

exceed the maximum value.

� The maximum length of the simultaneous ringing number is also 32 digits.

� When an analog phone number is set to an ONLY number, the phone user does not

support sequential ringing when busy.

2.2.12 Abbreviated Dialing Service

This service allows a user to dial a one-, two-, or three-digit abbreviated code instead of a

complete called number to connect to the called party.

� A maximum of eight one-digit abbreviated codes or a maximum of 30 two-digit

abbreviated codes can be configured for a user.

� A single IP PBX supports a maximum of 2048 abbreviated codes.

2.2.13 Co-Group Pickup Service

This service allows a user in a pickup group to dial a pickup access code to answer calls for

any members in the group.

Table 2-3 describes co-group pickup service specifications supported by eSpace U19xx series

IP PBX.

Table 2-3 Co-group pickup service specifications


eSpace U1930

eSpace U1910

Total number of pickup groups 500 255 255

Total number of users in a pickup group 1024


2.2.14 Designated Pickup Service

This service allows a user to dial a pickup access code and a phone number of the ringing

terminal to answer the call.

The following describes an application scenario of the designated pickup service:

In this example, the designated pickup access code is 11.

Assume that user A has enabled the designated pickup service. User B is in the same pickup

group with user A, and user C is in another group.

User C calls user B.

User B's phone rings.

User A dials *11*TN#. In the preceding number, TN is user B's number.

User B's phone stops ringing.

User A talks with user C.

The preceding steps are also used when users A and B are not in any pickup groups.

2.2.15 Multi-Number Service

A user can call another user who registers the multi-number service by dialing the primary

number or a secondary one. A primary number can have multiple secondary numbers, while a

secondary number can correspond to only one primary number. When the user who has

enabled the multi-number service calls another user, the called party's phone displays the

primary number by default. The user can determine the number displayed on the called party's

phone.

Table 2-4 describes multi-number service specifications supported by eSpace U19xx series IP

PBX.

Table 2-4 Multi-number service specifications


eSpace U1930

eSpace U1910

Total secondary numbers

(Including those shared by the service of number replacement on the same phone)

1000 308 308

� A primary number can have a maximum of 10 secondary numbers.

� Secondary numbers of the multi-number service do not occupy users' license resource.

2.2.16 Number Replacement Services

2.2.16.13 Service of Number Replacement on the Same Phone

When making a call to a user whose number is changed, the calling party can hear a number

replacement announcement, asking the calling party to decide whether to connect to the new

number. The user uses the same line after the number is changed.


� New phone numbers used by the service of number replacement on the same phone

source from the same number pool of the standby phone numbers used by the multi-

number service.

� This service does not support batch operations.

� The old and new numbers of the user occupy user license resources. The license resource

occupied by the old number is released only after the old number is deleted.

� The service of number replacement on the same phone is exclusive to the ONLY service.

2.2.17 ACB Service

The automatic call back (ACB) service provides the following subservices:

2.2.17.14 CBB

If user A who has enabled the call back on busy (CBB) service calls a busy intra-office user B,

user A can register the CBB service and hang up the phone. The system can automatically initiate a

call to user A when detecting that user B is idle or has made a call, and user A hears the CBB tone.

� When a user registers the CBB service, the system will call back to the user. If the user

does not pick up the phone within one minute, the CBB service is automatically

deregistered.

� The calling party and called party involved in the CBB service must be intra-office users.

� eSpace U19xx series IP PBX supports a maximum of 1024 users to enable the CBB

service.

� SIP users cannot hear the CBB tone.

� The CBB service is exclusive to the DND service, absent user service, CFU service,

CFNR service, CFB service, and instant hotline service.

� The service registration process of analog phone users is different to that of SIP phone

users.

− When an analog phone user calls a busy intra-office user, the analog phone user can

press the hookflash and dial the service code (for example, *59#) to register the CBB

service.

− When a SIP phone user calls a busy intra-office user, the SIP phone user can press the

key corresponding to an idle line and dial the service code (for example, *59#) to

register the CBB service.

2.2.17.15 CBNR

If user A who has enabled the call back on no reply (CBNR) service calls an intra-office user B but

user B does not answer the call, user A can register the CBNR service The system will detect user

B's calling status. If detecting that user B has a new call record, the system initiates a call to user A

when user B is idle.

� When a user registers the CBNR service, the system will call back to the user. If the user

does not pick up the phone within one minute, the CBNR service is automatically

deregistered.

� The calling party and called party involved in the CBNR service must be intra-office

users.

� SIP users cannot hear the CBNR tone.

� The service registration process of analog phone users is different to that of SIP phone

users.


− When an analog phone user calls an intra-office user but the user does not answer the

call, the analog phone user can press the hookflash and dial the service code (for

example, *60#) to register the CBNR service.

− When a SIP phone user calls an intra-office user but the user does not answer the call,

the SIP phone user can press the key corresponding to an idle line and dial the service

code (for example, *60#) to register the CBNR service.

2.2.17.16 RCB

If user A who has enabled the registered call on busy (RCB) service calls a busy user B, this

call is registered. When the calling party does not dial a number within five seconds after

picking up the phone next time, the system automatically initiates a call to the same called

party. If the called party is connected, the registered call is canceled automatically.

� SIP users cannot register the RCB service. The calling party and called party must be

intra-office users.

� The RCB service is canceled automatically 20 minutes after registration.

� The priority of the RCB service is lower than that of the instant hotline service.

� eSpace U19xx series IP PBX supports a maximum of 1024 users to enable the RCB

service.

2.2.18 Secretary Services

2.2.18.17 Secretary Service

This service allows a manager to specify any intra-office user as the secretary. All the calls

made to the manager are forwarded to the secretary, and only the secretary can put calls

through to the manager. The manager's outgoing calls are not affected.

� A manager can appoint multiple secretaries, and a secretary can work for multiple

managers.

� If another user calls the manager who is talking with the secretary, the user will hear the busy

tone.

� Managers and secretaries must be intra-office users.

2.2.18.18 Secretary Station Service

This service allows the system to hold a new incoming call to a busy user and unhold the call

when the user becomes idle. Generally, the secretary station service is used together with the

secretary service.

� If another user calls the manager who is talking with the secretary, the user will hear the

RBT.

� Managers and secretaries must be intra-office users.

2.2.18.19 Advanced Secretary Service

This service allows an authorized manager and the manager's secretary to share a phone line.

When either of them answers the call, the other one can know the peer's phone status according to

the corresponding line indicator. When a call comes in, the manager's phone rings or the

indicator blinks. Both the manager and the secretary can answer the call, and the manager can

take the call answered by a secretary.


The advanced secretary service provides the following functions:

� A manager and a secretary can call each other directly.

� Managers and secretaries can view the phone status of each other.

� The manager can have a private line.

� Before transferring a call to the manager, the secretary can ask the manager in advance.

The service restrictions are as follows:

� At most two secretaries can work for four managers.

� The advanced secretary service is exclusive to the ONLY service.

� eSpace68xx and eSpace78xx series IP phones support the advanced secretary service.

2.2.19 DND Service

This service allows the calling party to hear a DND announcement or the busy tone. A user

who does not want to answer calls can register this service. After registering this service, the

user cannot receive any calls but can still make calls.

� The priority of the DND service is lower than that of the alarm clock service.

� The DND service is exclusive to the absent user service, CBB service, CFU service,

CFNR service, CFB service, and instant hotline service.

2.2.20 Absent User Service

This service allows the calling party to hear the user absence announcement. After registering

this service, the user can still make calls.

The absent user service is exclusive to the DND service, CBB service, alarm clock service,

CFU service, CFNR service, CFB service, and instant hotline service.

2.2.21 Alarm Clock Service

This service allows a phone to ring at scheduled time to notify users. Users can pick up the

phone and hear the notification announcement. Then the alarm clock service is automatically

disabled.

If no one picks up the ringing phone at the scheduled time in one minute, the phone

automatically stops ringing, and starts ringing five minutes later. If no one picks up the phone

again, the service is automatically canceled.

� Only one notification can be added in the next 24 hours. The last notification will be

played at the scheduled time if a user adds multiple notifications.

� Users can dial a service code to cancel the alarm clock service or cancel it in the BMU.

� If the scheduled time is earlier than the current time, the alarm clock service will be

enabled the next day. If the user is busy at the scheduled time, the alarm clock service is

disabled.

� The wake-up times and interval can be configured.

� eSpace U19xx series IP PBX supports a maximum of 1024 users to enable the alarm

clock service.

� The priority of the alarm clock service is higher than that of the DND service.

� The alarm clock service is exclusive to the absent user service, CFU service, CFNR

service, CFB service, and instant hotline service.


2.2.22 Hotline Services

2.2.22.20 Delay Hotline Service

This service allows a phone to automatically dial a preset number (hotline number) when a

user does not dial within 5 seconds after picking up the phone.

� SIP users such as IP phone users, IAD users and eSpace Desktop users cannot register

the delay hotline service.

� The priority of the delay hotline service is lower than those of the instant hotline service

and the RCB service.

� eSpace U19xx series IP PBX supports a maximum of 1024 users to enable the delay

hotline service.

2.2.22.21 Instant Hotline Service

This service allows a phone to automatically dial a preset number (hotline number)

immediately after off-hook.

� SIP users cannot register the instant hotline service. However, IADs and IP phones

support this service.

� The priority of the instant hotline service is lower than that of the outgoing call barring

service.

� The instant hotline service is exclusive to the DND service, CBB service, alarm clock

service, absent user service, CFU service, CFNR service, CFB service, and call waiting

service.

� eSpace U19xx series IP PBX supports a maximum of 1024 users to enable the instant

hotline service.

2.2.23 Privilege Services

2.2.23.22 Break-in Service

This service allows an attendant to break in an intra-office or inter-office call to start a three-

party call.

The break-in service is only applicable to a single phone.

� If both parties in a call have the break-in override right, an attendant cannot break in the

call. The attendant can only hear the busy tone, and the call continues.

� If only one party in a call has the break-in override right, the break-in of an attendant

depends. If the attendant performs the operation on the party who has the override right,

the attendant can only hear the busy tone, and the call continues. If the attendant

performs the operation on the party who has no override right, the attendant hears the

break-in tone, and a three-party call is initiated.

2.2.23.23 Forced Release Service

This service allows an attendant to forcibly release an ongoing call of an intra-office user

when there is a toll call to this user or for other reasons. The attendant will hear the forced

release tone, and the parties in the call hear the busy tone.

The forced release service is only applicable to a single phone.


� If both parties in a call have the forced release override right, an attendant cannot

forcibly release the call. The attendant can only hear the busy tone, and the call

continues.

� If only one party in a call has the forced release override right, the forced release

operation of an attendant depends. If the attendant performs the operation on the party

who has the override right, the attendant can only hear the busy tone, and the call

continues. If the attendant performs the operation on the party who has no override right,

the attendant hears the forced release tone, and two parties in the call hear the busy tone.

2.2.23.24 Privileged User Service

This service allows a user to break in an ongoing call and talk with a user in the call.

� A user generally cannot enable the privileged user service together with the break-in and

forced release services. If a user enables these three services at the same time, the

priority of the privileged user service is higher than those of the break-in and forced

release services.

2.2.24 DID Service

The direct-inward-dialing (DID) service allows an out-office user to directly make a call to an

intra-office user by dialing the PSTN long number, instead of being forwarded by the

automatic switchboard.

2.2.25 IVR

The IVR service, also called automatic switchboard service, allows all incoming calls to be

transferred to the switchboard. By default, the system plays an announcement asking the

calling party to dial the extension number.

� A maximum of 256 switchboard numbers (0–255) can be configured. Switchboard

numbers from 4 to 254 support script customization.

� The customization of switchboard allow to receive fax or transfer to any extension or,

mobile phone or to send to attendant in order to search a user into the corporative

directory

� A maximum of 480 concurrent calls can be connected to a switchboard number. The

capability is restricted by media resources.

� If calls are connected through an analog trunk, users cannot dial the switchboard number

followed by the extension number to make a call.

� Different IVR announcements can be played in time segments.

� Different IVR announcements can be recorded by local gateway U19xx

� When a called party hangs up the phone, the calling party can switch to the switchboard

again.

� If the call coming from a digital trunk is possible to transfer the call

�

2.2.26 PBX Group Line Selection Service

The system selects a called party from a PBX group according to the preset selection mode (in

ascending order, descending order, or polling mode) when a non-PBX group user makes a call

to the primary number of the PBX group.

� A maximum of 255 PBX groups ranging from 0 to 254 is supported.


� Each PBX group contains a maximum of 50 users.

The following describes an application scenario of the PBX group line selection service:

Assume that there are users A, B, and C in a PBX group, and their values of GlobalPortNo are in

ascending order (A < B < C). User B's number is the primary number, and users A and C's numbers are

secondary numbers. The PBX group selects a line based on the GlobalPortNo value in ascending order.

When a user who is not in the PBX group calls user B:

1. If the PBX group does not set the line selection mode to the primary number preferred mode:

According to the line selection mode, the ringing order is A > B > C. The call is forwarded to user

A first. If user A is idle, user A's phone rings. If user A is busy, the call is forwarded to user B. If

user B is also busy, the call is forwarded to user C.

2. If the PBX group sets the line selection mode to the primary number preferred mode.

According to the primary number preferred mode and line selection mode, the ringing order is B >

A> C:

1) If user B is idle, user B's phone rings.

2) If user B is busy, the call is forwarded to user A first. If user A is idle, user A's phone rings. If

user A is also busy, the call is forwarded to user C.

2.2.27 Distinctive Ring Tone Service

This service allows that different ring tones can be played for different users: intra-office

users, outer-office users, Centrex group users, and users who register the CBB service.

� Two IP PBXs connected to the same SIP trunk can be in the same office. This allows

users under different IP PBXs to hear the same intra-office ring tone.

� Users under IADs can specify different ring tones only for intra-office and outer-office

users.

2.2.28 Remote Service Activation

A user can dial the remote service activation access code to register or deregister call

forwarding services (including CFU, CFB, CFNR, and CFO) and advanced secretary service.

� A user must enter a service number and password to register or deregister the service.

� The total length of the phone number and the forwarded-to number cannot exceed 24

digits.

2.2.29 Deregistration of All Services

This service allows a user to deregister all the registered supplementary services on the phone.

Basic service rights are not affected. The password is required to deregister all services.

2.2.30 Hunting Group

A hunt group is a group of phones that you can access when you dial a single phone number.

A call routed to the hunt group number can reach any member of the group who is currently

logged into the group.

A static hunt group is one in which all members are permanently logged in.

A dynamic hunt group allow phone users to log into or out of the group.


They are three ringing types for hunt group: linear hunt group, circular hunt group, or parallel

hunt group.

2.2.31 Phone to Phone Paging Group

The phone to phone paging using the speakers of your IP phones to broadcast the paging

audio output.

A paging number can be defined to a group of phones.

When a caller dials the paging number of paging group, each idle IP phone of the paging

group automatically answers using its speakerphone mode.

The audio paging provides a one-way voice path to receive phones.

The system allows multiple simultaneous paging groups.

2.3 Advanced Services

2.3.1 User Rights Management by Level

2.3.1.25 Right Levels for Supplementary Services

IP PBX users are assigned four right levels in ascending order: default, normal, advanced, and

super. Users at different right levels have different rights to use new services or make calls. If

no right level is configured for a user, the user is at the default level.

Users of a higher authority level have more new service rights, including all those users of

lower authority levels have. The new service right allocation can be modified by running

commands. By default, new service rights are allocated as follows:

� Default level: Users have rights to use local number query, call transfer, call forwarding,

call waiting, abbreviated dialing, outgoing call barring, alarm clock, CLIP, password

change, phone conference, unified access to the fax mailbox, call park, call right, ONLY,

DND, and absent user services.

� Normal level: In addition to services that users can use at the default level, users at the

normal level have rights to use RCB, CBB, designated pickup, and instant conference

services.

� Advanced level: In addition to services that users can use at the normal level, users at the

advanced level have rights to use three-party call, call hold for multiple calls,

simultaneous and sequential ringing, break-in, and forced release services.

� Super level: In addition to services that users can use at the advanced level, users at the

super level have rights to use privileged user, secretary, and secretary station services.

2.3.1.26 Right Levels for Call Rights and Call Control by Time Segment

Users at different right levels have different rights to make calls. Call rights can be control by

time segment so that users at a level can make calls only in a specified time segment. Table 2-

5 describes call rights of users at different levels.


Table 2-5 Call right

Outgoing Call Right

User Level

Intra-Office Call

Local Call National Toll Call International Toll Call

Default Yes Yes No No

Normal Yes Yes OnlyWorkingTime No

Advanced Yes Yes Yes OnlyWorkingTime

Super Yes Yes Yes Yes

� A user can set and query the working time that is related to right levels and call rights. In

Table 2-5, OnlyWorkingTime indicates that users at specified levels can make calls

only in working time. If no working time is set, all time segments are working time by

default. This means that users at specified levels can make calls at any time segment.

2.3.1.27 Trunk Preemption for Higher-Right-Level Users

If trunks are insufficient, reserved trunks can be used based on the preset user level.

If there is no available reserved trunk, higher-right-level users who make outgoing calls can

preempt the trunks assigned for lower-right-level users. For example, a user at the super level

can preempt trunks occupied by users at the advanced, normal, and default levels. When the

trunk of a lower-right-level user is preempted, the user hears the busy tone (configurable), and

the call is released.

� Users at the same level cannot preempt trunks of one another.

� By default, the busy tone is played when a trunk is preempted. An announcement can be

also played.

2.3.2 Call Barring Policies

2.3.2.28 Call Barring by Calling Number

Call rights that are classified by calling number include incoming and outgoing call rights, for

example, local call rights, toll call rights, and trunk call rights.

2.3.2.29 Call Barring by Called Number

Call rights that are classified by called number include incoming and outgoing call rights, for

example, local call rights, toll call rights, and trunk call rights.

2.3.2.30 Call Barring by Blacklist or Whitelist

Call barring by blacklist or whitelist allows a user to accept or reject calls made by a list of

users. Figure 2-2 shows call barring relationships by blacklist and whitelist.


Figure 2-2 Call barring by blacklist or whitelist

� Users in the blacklist group can call only users in the whitelist group.

� Users in the ordinary call barring group can call users in the same group or in the

whitelist group, but cannot call users in the blacklist group.

� Users in the whitelist group can call users in any of the three groups.

Table 2-6 describes service specifications of call barring by blacklist or whitelist supported by

eSpace U19xx series IP PBX.

Table 2-6 Service specifications of call barring by blacklist or whitelist


eSpace U1930

eSpace U1910

Total number of calls made by users

both in the blacklist and whitelist

groups

(Both the calling number and the called

number are in the blacklist and

whitelist, and each accounts for 50% of

the total number that is supported.)

20,000 2500 2500

2.3.2.31 Call Barring by Personal Blacklist

The personal blacklist has a lower priority than the system blacklist. The personal blacklist is

configured on the command-line interface (CLI) or the BMU.

Table 2-7 describes service specifications of call barring by personal blacklist supported by

eSpace U19xx series IP PBX.

Table 2-7 Service specifications of call barring by personal blacklist


eSpace U1930

eSpace U1910

Total number of personal blacklists 10,000 2500 2500

Number of personal blacklists

configured for a single user

10


2.3.2.32 VoIP Domain-based Call Barring

eSpace U19xx series IP PBX logically assigns some local users or office routes to a VoIP

domain for barring calls and sets the maximum number of concurrent calls for this VoIP

domain. When receiving a new call request, the IP PBX checks the calling and called parties'

domains and the maximum number of calls allowed. If the maximum number of calls allowed

is reached, the call fails, and the calling party hears an announcement.

� eSpace U19xx series IP PBX supports a maximum of 255 VoIP domains for barring

calls.

2.3.2.33 Password-based Call Barring

eSpace U19xx series IP PBX determines whether a user can make calls by asking the user to

enter a password. The password is bound to the user's phone.

� The password consists of four digits. The password is also used in the outgoing call

barring service and password change service. Users can change the password. For

details, see 2.2.9 Password Change Service.

� IVR announcements guide users to perform operations after dialing a number.

� All users in the system can register this service concurrently.

2.3.2.34 Call Barring by Card Number and Password

Users can use authorized card numbers and passwords to make calls from any phones in the

office.

� All users in the system can register this service concurrently.

� This service supports the following dialing modes:

− IVR navigation dialing mode

Users enter the password-based call barring prefix, and dial a number as prompted.

− Full number dialing mode

Users directly enter outgoing prefix*call barring service ID*password*called

number# to make a call.

By default, a new call barring user added by the administrator has the Inter and Local call

rights. The administrator can customize call rights for users.

The administrator provides users' initial passwords. Users can dial the call barring prefix and

change the password as prompted. The system plays an announcement to tell the operation

result.

� The user ID and password consist of 4 to 8 digits.

� Dialing fails if a user enters incorrect passwords for three consecutive times.

� If a user does not have the corresponding call right, the system will tell the user that the

call is restricted.

2.3.2.35 Calling Number Authentication

If the calling number authentication service is configured for the called number prefix

involved in an incoming call from a local user or a trunk, the IP PBX initiates a request to the


remote authentication dial-in user service (RADIUS) server to authenticate the calling

number. If the authentication is successful, the IP PBX connects the call. If the authentication

fails, the call fails.

� If calling number authentication fails, automatic card number authentication can be

enabled.

2.3.2.36 Call Barring by Region

The IP PBX manages call rights for users who use different types of phones in various

regions.

� After users under the IP PBX are assigned to different VoIP domains, the IP PBX

determines whether a call can be established based on the calling number, called number,

or domain type.

� This service meets VoIP restriction requirements of India offices. Incoming and outgoing

calls cannot be routed through broadband and narrowband trunks. Different rights can be

assigned to trunks to prevent trunk tandem calls.

2.3.2.37 Anonymous Call Barring

This service allows the system to restrict anonymous calls (including intra-office calls and

outer-office calls) to a user.

2.3.2.38 Restriction on Outer-Office Call Duration

When a user under eSpace U19xx series IP PBX makes an outgoing call to or receives an

incoming call from an outer-office user, the IP PBX controls the call duration as configured

and plays an announcement to the user when there is only one minute left.

� The maximum call duration ranges from 0 to 300, in minutes.

� The conference duration determines the call duration of IP PBX users in a local

conference.

� If an IP PBX user joins a conference through the trunk by dialing the conference access

code or clicking a link in the conference invitation mail, the maximum duration is

determined by the call duration specified for the user.

� When an IP PBX user dials a PSTN switchboard number through the trunk, the IP PBX

counts the call duration from the time when the switchboard starts to play an

announcement.

� If an outer-office user dials the extension number through the switchboard to call an IP

PBX user, the IP PBX counts the call duration from the time when the IP PBX user picks

up the phone.

� The duration of an emergency call or a call made between intra-office users is not

restricted.

If a user enables call duration restriction on outgoing calls, the call duration is restricted only

when the user is the calling party. If a user enables call duration restriction on incoming calls,

the call duration is restricted only when the user is the called party.


2.4 Intelligent Routing

The intelligent routing service automatically selects office routes when an IP trunk or a TDM

trunk is faulty, and provides routing polices to increase communication reliability and

minimize communication costs.

Figure 2-3 Intelligent routing application scenario network

The following shows the application scenario of intelligent routing.

The IP PBX connects to carrier A's network through the Primary Rate Adaptation (PRA) and

ISUP trunks. The office route selection code is 1. The IP PBX connects to carrier B's network

through the PRA trunk. The office route selection code is 2. Intra-office users are 7000 to

7079 and trunk and user data have been configured.

2.4.2 Routing by Time Segment

Different time indexes are set for different office routes. Each time index corresponds to a

specified time segment (accurate to hour). Based on the current time, the IP PBX searches for

the time index for an outgoing call and selects the related office route.

The IP PBX allows multiple office route selection codes to share one office route. When an

office route is added to multiple office route selection codes, multiple routing policies apply

to the office route. The IP PBX automatically selects the routing policy based on the outgoing

prefix that a user dials.

For example, the function can be implemented in the following application scenario: If an IP

PBX user dials PSTN user number 0xxxxxxxx in the time segment from 08:00 to 18:00, carrier

A's PRA trunk is used to route the call. If calls are made in other time segments, carrier A's

ISUP trunk is used.

2.4.3 Routing by Charge Rate

Different charge rate reference values are set for different office routes. The IP PBX

preferentially selects the office route with the lowest charge rate reference value for outgoing

calls. If all trunk circuits are busy for this office route, the IP PBX selects the office route with

the second lowest charge rate reference value.


PBX user dials PSTN number 0xxxxxxxx, the IP PBX selects office routes based on the charge

rate reference values in ascending order.

2.4.4 Rerouting upon Call Failures

When a call fails to be routed based on the office route selection code, the IP PBX selects a

new route based on the standby office route selection code corresponding to the failure

processing index.


For example, the following function can be implemented in the application scenario: If an IP

PBX user dials PSTN number 0xxxxxxxx, carrier A's trunks are used preferentially to route the

call. When carrier A's network is faulty, carrier B's trunk is used to route the call.

2.4.5 Route Load Balancing

The IP PBX balances traffic among multiple preset routes. The IP PBX polls office routes

based on office route IDs in ascending order till an office route that contains idle circuits is

found. The later calls will poll from the next office route after an office route is selected by

the preceding call.


PBX user dials PSTN number 0xxxxxxxx, the IP PBX polls office routes based on office route

IDs in ascending order till an office route that contains idle circuits is found.

2.4.6 Routing by Percentage

Different percentages are set for different office routes. The IP PBX selects office routes in

turn based on the preset percentages. Except the office routes whose percentages are set to

100%, office routes are polled based on preset percentages in descending order.

For example, the function can be implemented in the following application scenario: If IP

PBX users dial PSTN number 0xxxxxxxx, 70% of the calls are routed through carrier A's PRA

trunk, and the remaining calls are routed through carrier A's ISUP trunk.

2.4.7 Routing by User Right Level

Different office routes are set for different user right levels. When a higher-right-level user

makes an outgoing call, the IP PBX preferentially selects the office route that is set for the

user right level. If selecting the office route fails, the IP PBX selects the office route that is set

for a lower user right level.

When routing by user right level is used, the IP PBX preferentially uses an office route at the

user right level to route calls. If no circuit is idle, the office route that is set for a lower user

right level is used. Office routes that are set for the same level are polled based on office route

IDs in ascending order. To ensure good voice quality of calls for higher-right-level users,

these users are allocated with high-performance office routes. Lower-right-level users,

however, are not allowed to use these office routes.

For example, the function can be implemented in the following application scenario:

� Calls made by users 7000 to 7009 are routed through office route 1. If no circuit is idle,

office route 2 will be used.

� Calls made by users 7010 to 7079 can only be routed through office route 2.

2.4.8 Trunk Link Balancing

The IP PBX preferentially selects a trunk with more idle circuits to balance loads among

available trunk links.


PBX user dials PSTN number 0xxxxxxxx, the IP PBX polls the office routes based on office

route IDs in ascending order and selects an office route that contains most idle circuits.


2.5 Voice Conference

The voice conference service allows three or more users in a conversation.

Huawei eSpace UC solution provides scheduled and instant conferences. Scheduled

conferences can be classified into the following types:

� Conference through individual dialing-in

� Conference through host convening

� Conference through system convening

Users can schedule and manage conferences on the BMU.

� eSpace U1980 supports a maximum of 320 conference sites and 960 participants (when

eight MRSs are installed). Each MRS supports a maximum of 40 conference sites and

120 participants. Each conference site supports a maximum of 120 participants.

eSpace U1930 supports a maximum of 4 conference sites and 12 participants. Each

conference site supports a maximum of 12 participants.

eSpace U1910 supports a maximum of 4 conference sites and 12 participants. Each

conference site supports a maximum of 12 participants.

The maximum number of conference sites refers to the number of conference sites where

conferences are convened at the same time. The number is worked out with each

conference site holding no less than 3 participants.

� Once time the conference has scheduled the system will send an email invitation to

participants with the phone number, conference number and password of the conference.

� All types of terminals can be used to join conferences through system convening and

conferences through individual dialing-in.

� Voice control: The moderator has the control using DTMF, and he can allow or forbid

one or more participants to speak.

� Voice recording: The moderator or presenter can record meeting audio on the meeting

client and save the recorded file locally. Before recording, the system plays an

announcement, indicating that conversations will be recorded.

� When common users (except the moderator) are in an intra-office conference, they are

not allowed to press the hookflash and register other supplementary services. The IP

PBX does not restrict outer-office users from registering other supplementary services by

pressing the hookflash in an intra-office conference.

� The moderator can press the hookflash on an analog phone or asterisk key on an IP

phone to invite other users or register other supplementary services.

� User name broadcasting (supported when an MRS is installed)

When a user joins a conference, the user pronounces the name as prompted. The system

plays an announcement telling other participants that the user joins the conference. When

the user leaves the conference, the system plays an announcement telling other

participants that the user leaves the conference.

� The moderator can transfer moderator rights to a participant during a conference.

� The announcement indicating that someone joins or leaves a conference can be

configured.

� Users can press 8# to mute the terminal, and press 7# to unmute the terminal.

� Flexible control of conference duration


− Users must set the start time and end time when scheduling a conference. Users can

schedule a conference in seven days. A conference cannot last for two days. The start

time and end time cannot be modified after a conference starts.

− Participants can join a conference 5 minutes in advance. A conference automatically

ends 15 minutes after all participants quit.

− If participants are still in a conference when the end time is due, the conference is

prolonged on a 30-minute basis as long as resources are available.

2.5.1 Scheduled Conference

2.5.1.39 Individual Dialing-In

Participants dial a conference access code and enter the conference ID and password as

prompted to join a conference. If the conference ID or password that a participant enters is

incorrect, the participant returns to the upper-level menu.

2.5.1.40 Host Convening

The moderator joins a conference and performs operations on the phone to invite or remove

participants.

2.5.1.41 System Convening

The moderator sets a participant list in advance, and the system calls the listed participants at

the scheduled time. Participants can simply pick up phones to join the conference.

2.5.2 Instant Conference

Users can directly initiate an instant conference without scheduling the conference in advance.

An authorized user dials the conference prefix and creates an instant conference as prompted.

The user who initiates the conference is the moderator. The moderator can invite more

participants.

� The moderator can invite two participants by default (which can be set). The moderator

can invite a maximum of 29 participants.

� The default number of participants that the moderator can invite can be set to 11 at most.

It means that the system can reserve resources for holding a maximum of 12 participants.

� When a user wants to join a conference by dialing the access code, the user must join the

conference 5 minutes in advance.

� A conference can have only one moderator.

� A common participant can be an intra-office or outer-office user. The moderator must be

an intra-office user.

� A common participant cannot press the hookflash in a conference.

� When the number of participants reaches the maximum limit, the system informs the

moderator that no more participants can be invited.

� When a conference starts but no user join the conference in 15 minutes, the conference

automatically ends.

� When resources are sufficient, participants can join a conference 5 minutes in advance

and prolong the conference when the end time is due.

� The moderator cannot dial the access code when inviting users to join a conference.


� If the first few digits of a user's number are the same as the access code, the user cannot

be invited. For example, if the access code is set to 343, users whose numbers start with

343 cannot be invited.

2.6 IP Phone Services

Notes: Different types of phones have different features. Please reference to IP Phone’s specification List and feature description.

2.7 SoftPhone

2.7.1.42 Login

On the login page, users can use their accounts to log in to eSpace SoftPhone and customize

eSpace SoftPhone settings. They can set the automatic login mode, select a login server,

configure whether eSpace SoftPhone starts together with the Windows operating system, and

clear all login account information from eSpace SoftPhone. VoIP

2.7.1.43 Voice Call

Users can click a record in the corporate or personal directory, or enter the called number in

the search bar to make a voice call between PCs or between a PC and an IP phone, thru the

multimedia PC audio control.

2.7.1.44 CLIP

A window will be displayed in the lower right corner on an eSpace Desktop when there is an

incoming call. The window provides operation buttons (end or answer) and calling party

information such as the calling party's name and phone number. When the call is connected,

the window changes to the call control window. The window displays the real-time call

duration and call control buttons.

2.7.1.45 Historical Records

Users can save call records on local hosts. Available disk space determines the maximum

number of records that users can save.

Users can click a call history record to initiate a call.

2.7.1.46 VAD and EC

2.7.1.47 Multi-Language

SoftPhone supports Chinese (Simplified and Traditional) and English.


2.8 Console System

The Console system is an IP-based (Computer & Telephony Integration) CTI platform

installed on PCs. The Console system has all functions of an ordinary phone and agent

functions. The Console system consists of the Console server and SoftConsole, and supports

hardware terminals to allow the SoftConsole to answer incoming calls.

UC users dial the SoftConsole access code to make calls to the Console group.

A single Console server can connect a maximum of 30 eSpace U19xx IP PBXs and supports

dual-host redundancy of IP PBXs.

2.8.1 ACD

The SoftConsole supports the following automatic call distribution (ACD) schemes:

� Calls can be allocated to idle attendants based on the login sequence.

� Users can import and run customized IVR scripts to implement voice play, digit

collecting, and call transfer functions.

� Calls can be transferred to the night service when all attendants are busy, offline, or have

quit the Console group.

� Calls can be transferred to a virtual user (VU) when all attendants are busy, offline, or

have quit the Console group.

� Calls can be transferred to a waiting queue when all attendants are busy.

� Calls can be transferred to a waiting queue when all attendants are busy, and transferred

to a VU if timeout occurs.

The SoftConsole also supports registration and deregistration of the forcible transferring to

night service, setting of the night service number, and setting of the queuing timeout duration

(59 seconds by default).

2.8.2 Basic Call

eSpace U19xx IP PBXs use SIP to communicate with the SoftConsole, and regard the

SoftConsole as an SIP user. The Console system, like a common user, has the following basic

call functions: answers and rejects incoming calls, initiates and ends calls, holds and unholds

calls, breaks in to calls, forcibly releases calls, and performs two-stage dialing.

� Breaking in to a call forcibly

An attendant can break in to customers' calls to start a three-party call.

� Releasing a call forcibly

An attendant can forcibly release an ongoing call on the SoftConsole.

� Two-stage dialing

The Console system provides a switchboard number. Outer-office users can dial this

number to call the Console switchboard, and dial the attendant's phone number after

hearing the system announcement. In some cases, the Console switchboard automatically

transfers the call to attendants.

2.8.3 Agent Functions

After being added to the Console group, attendants can use agent functions, such as setting

attendant status to busy or idle, answering incoming calls, queuing incoming calls, changing

the call queuing priority, and recording calls.


� eSpace U1980 using the super main control unit (SMCU) supports a maximum of 256

Console groups.

� eSpace U1980 using the SMCU supports a maximum of 1024 attendants.

� Each Console group contains a maximum of 64 attendants.

� The SoftConsole can save a maximum of 10,000 call records.

2.8.3.48 Adding Attendants to or Deleting Attendants from a Console Group

Attendants can use the SoftConsole on their agents only when they have been added to the

Console group. When deleted from the Console group, attendants become common SIP users.

2.8.3.49 Setting Attendant Status to Busy or Idle

After being added to a Console group, an attendant can show busy to prevent incoming calls

or show idle to receive and handle incoming calls.

2.8.3.50 Queuing Incoming Calls

If all attendants in a Console group are busy, all calls to the Console group are responded with

a ringing tone and are queued in time order for attendants to answer. When an attendant

becomes idle, the incoming call queued the earliest is connected to the attendant.

Attendants can change the call queuing priority to adjust the sequence for answering incoming

calls, and can double-click an incoming call record to move the call to the top of the queue.

� Agents in the same Console group display the same incoming call queue information,

including incoming call numbers, waiting time, and departments and positions of intra-

office users.

� The maximum waiting time can be configured for each Console group.

� When all attendants are busy, calls can be transferred to a waiting queue. When queuing

times out, the calls can be transferred to a VU.

� A Console group supports a maximum of 64 calls in a call waiting queue.

2.8.3.51 Transferring Calls

The SoftConsole supports the following functions:

− Transfers calls.

− Holds multiple calls.

− Specifies a call to answer.

− Transfers multiple calls concurrently.

− Displays the queue of held calls.

− Selects a held call to answer, end, or transfer.

� Call transfer includes unconditional call transfer and negotiated call transfer.

� Only one call can be activated.

� Attendants can hold a maximum of six calls, display the queue of held calls, and selects a

held call to answer, end, or transfer.

� Attendants can transfer a maximum of five calls at the same time.

� Attendants can specify a call to answer based on the customer priority to optimize

customer experiences.


2.8.3.52 Recording Calls

An attendant with recording rights can record local calls.

� Recordings are uploaded in the FTP mode to and saved on the Console server.

� Attendants can record local calls and play voice files only on the SoftConsole.

2.8.3.53 Displaying Attendant Status

The SoftConsole obtains the statuses of attendants and users in real time and displays the

statuses in the busy/idle status area.

� The administrator can view all attendants' statuses. Other attendants can view only the

statuses of attendants in the same Console group.

� The Console server notifies the SoftConsole of attendant status change, including

calling, ringing, idle, and offline. The SoftConsole displays attendant statuses.

� A maximum of 128 attendant statuses can be displayed.

2.8.3.54 Querying User Status

Attendants can query user status by clicking the status icon or clicking a user number in the

directory.

Attendants can view only the statuses of intra-office users under the same IP PBX with the

SoftConsole.

2.8.3.55 Binding Hardware Terminals

The SoftConsole can be bound to hard phones so that calls can be answered on hard phones

while controlled on the SoftConsole. Call control functions include assistant dialing,

specified-attendant answering, and call transfer, release, holding, and unholding.

2.8.4 Night Service

Night service numbers can be configured for Console groups. When all attendants are busy,

offline, or have quit the Console group, calls are forwarded to the night service number or VU

with announcements.

Attendants can register and deregister the function of forcibly forwarding calls to the night

service after entering the SoftConsole password.

2.8.5 Corporate Directory

The corporate directory can be connected to, bound to, and disconnected from the lightweight

directory access protocol (LDAP) server that is provided by the open-source software

OpenLDAP and is integrated with the Console server. In the corporate directory, an attendant

can fuzzily query records, view record details, and initiate calls to contacts in the directory. In

addition, the SoftConsole can automatically search the directory for calling numbers. The

corporate directory is organized and displayed based on the department tree. An attendant can:

� Obtain, query, and update a department tree

� Query and display contacts under a node in a department tree

� Expand and collapse nodes in a department tree


An attendant can back up and restore LDAP data, and add, delete, query, and modify

customized contact information.

2.8.6 Call History

Call records are displayed in real time on the SoftConsole. Attendants can manage call

records, such as querying, adding, and deleting call records. Attendants can click a call record

to initiate a call.

The SoftConsole displays missed call records for all attendants in the Console group if no

attendant has answered the call.

Call record categories include outgoing, received, and missed calls. Each call record includes

the user name, calling number, and start time and end time of the call.

The SoftConsole supports a maximum of 10,000 call records.

2.8.7 Notifying Incoming Calls

� The SoftConsole supports the following incoming call notifications:

− Ring

− Automatic display of an incoming call dialog box when the SoftConsole is minimized

− Calling line identification presentation

− Announcement play from the PC loudspeaker

� The SoftConsole automatically displays the calling number, called number, calling party

names, call duration, and call status (such as held or resumed) after a call is connected.

� The SoftConsole that supports the hotel middleware system can automatically obtain

calling party names from the hotel middleware systems such as JDS, FCS, and RMD,

and displays the names.

2.8.8 Service Management

� This service can be used only in small-sized offices where no hotel middleware is used.

� The BMU is mandatory.

2.8.8.56 Setting Call Rights

The administrator can configure intra-office users' rights to make intra-office, local, national,

and international calls. Setting the DND Service

The administrator can configure the DND service for intra-office users.

2.8.8.57 Setting the Wake-up Service

The administrator can set the common wake-up service or VIP wake-up service for a specified

number based on the time segment, and collect wake-up records.

2.8.8.58 Setting the One-Key Restore Service

The administrator can click one key to restore all services that are configured for a specified

number to initial services.


2.8.8.59 Setting the Night Service

After the night service is configured, all calls to the Console system will be forwarded to a

preset night service number.

The administrator can configure the night service based on the time segment.

2.8.8.60 Querying CDRs

The administrator can query call detail records (CDRs) of a specified number. CDRs include

information such as bills, summary, calling numbers, call fees, number of calls, call duration,

call time, called numbers, and call types.

2.8.8.61 Modifying User Information

The administrator can modify user information in the corporate directory.

2.8.9 Other Functions

2.8.9.62 Login Authentication

The SoftConsole supports:

� SIP registration authentication

After an attendant logs in to the SoftConsole successfully, the SoftConsole automatically

obtains the SIP device ID and password, and completes the registration authentication on the

IP PBX.

� Attendant login authentication

When an attendant enters the user name and password to log in to the Console server, the

SoftConsole authenticates the user name and password.

2.8.9.63 GUI Display � The SoftConsole can be displayed in full screen mode.

� The SoftConsole graphical user interface (GUI) can be automatically locked if

operations time out. An attendant must enter the password to unlock the GUI.

� The SoftConsole can be displayed in Chinese (simplified/traditional) or English while

cannot be switched between Chinese and English.

2.8.9.64 Online Help

The SoftConsole provides online help.

2.8.9.65 Shortcut Keys

Attendants can perform common operations on the SoftConsole by clicking shortcut keys.

2.8.9.66 Log Management

Attendants can view or record software operation information in logs, save logs, set the log

polling policy, set the log level, and enable or disable the log function.


2.8.10 System Configuration

On the SoftConsole, attendants can configure connection information (such as the IP address

and port number), special prefixes, audio, security, corporate directory, and bind phone

numbers to hard phones such as IP phones.

The server IP address, port number, directory number (DN) number, and password can be set

for the corporate directory.

The following audio parameters can be set:

� EC

� CNG

� AGC

� Audio codec mode and priority

� Audio input and output devices

� Announcements played by the PC speaker

� Two-stage dialing

� Microphone or speaker volume

2.9 CDR

eSpace U19xx IP PBXs generate user CDRs and save them to the CDR pool where binary

CDR information is buffered.

� An eSpace U1980 CDR pool can save a maximum of 240,000 CDRs.

� An eSpace U1930 or eSpace U1910 CDR pool can save a maximum of 30,000 CDRs.

2.9.1 CDRServer

The BillServer can save and handle binary CDR information of multiple IP PBXs at the same

time.

� The BillServer can connect to a maximum of 30 IP PBXs.

� The BillServer can handle a maximum of 1200 CDRs every second.

� The BillServer can back up two copies of CDRs.

� Each CDR cannot exceed 240 bytes.

� The BillServer must use the BMU or a third-party system to obtain, query, and collect

CDRs.

2.9.1.67 FTP Interface for Uploading CDRs

The FTP interface enables the SoftCo IP PBX system to provide CDRs for third-party billing

systems and billing centers openly and securely.

2.9.1.68 Integrating Bill Console Functions

The BillServer provides a graphical man-machine interaction interface to manage CDRs.

� Query CDRs


Users can use any of the following search criteria to query CDR files on the BillServer:

calling number, called number, IP address of the device where CDRs are located, and

CDR generation time.

� Delete historical CDRs

Users can delete CDR files from the BillServer to free up disk space. To ensure data

security, the BillServer only allows users to delete CDR files saved one month before the

current day.

� View CDR pool information

Users can view the CDR pool information of an IP PBX on the BillServer based on the

IP PBX IP address.

� Control CDR transfer

Users can enable or disable the CDR transfer function. When new CDRs are generated in

the IP PBX CDR pool, the BillServer determines whether to move these CDRs to the

BillServer if the CDR transfer function is enabled. (The CDR transfer function is enabled

by default.)


3 UC Functions

3.1 ONLY Service

The ONLY service allows multiple terminals of a user to share the same number and same

supplementary services.

The ONLY number is the number of an intra-office user. When the ONLY number is dialed,

the user's multiple terminals ring sequentially or simultaneously according to the preset

ringing rule, and the user can answer the call on one of these terminals.

3.2 IM Service

The IM service allows users to perform text chat, send emoticons, and transfer files with

online contacts anytime, anywhere. Users can query history chat records and drag multiple

contact avatars to add contacts to join an IM discussion group. In addition, offline users can

receive IMs and view these IMs in the displayed IM page when they log in to the eSpace

Desktop next time. IM functions include:

3.2.1 Two-Party Conversation

The eSpace Desktop supports point-to-point (P2P) message sending and receiving. Users can

receive messages from or send messages to contacts.

� Users can initiate an IM from the corporate or personal directory.

� Users can initiate an IM on the IM page.

3.2.2 Group Chat

Users can create chat groups or join other chat groups after being approved. After joining a

group, users can send group messages, view text chat records of the group, and leave the

group. The creator can modify the group information and dismiss the group.

The eSpace Desktop supports group message sending. Users can manually add a group of

contact numbers, or select multiple contacts from the corporate or personal directory and send

an IM to them at the same time.

A user can send a group message to a maximum of 30 contacts in a temporary group.


3.2.3 File Transfer

The eSpace Desktop supports point-to-point file transfer. Users can send files to contacts.

� A maximum of 10 files can be transferred simultaneously, and the maximum file size

varies according to the eSpace Desktop configuration.

� The maximum transfer rate is 1080 kbit/s.

� The maximum size of transferred files is 2000 MB.

� The administrator can restrict the file transfer rate to different levels (20 kbit/s, 30 kbit/s,

50 kbit/s, 80 kbit/s, 120 kbit/s, 180 kbit/s, 360 kbit/s, 720 kbit/s, and 1080 kbit/s).

3.2.4 Emoticon or Image Sending and Receiving

Users can send and receive emoticons or images on eSpace Desktops.

3.2.5 IM History

The eSpace Desktop automatically saves the IM history to the BMU server. The IM history

includes information about contacts, groups, IMs, and temporary messages, and provides

contacts' names, time for sending and receiving messages, and message contents.

3.2.6 Special Content Identification

� Email address identification

The eSpace Desktop can recognize email addresses in IM records.

� URL identification

The eSpace Desktop can recognize URL information. Users can click a URL to access

the web page directly in IMs and bulletins.

� Sensitive word filtering

3.2.7 System-Level Configuration

� Maximum number of characters in an IM

� Image size supported in an IM

� Bandwidth for transferring files

3.2.8 Avatar and Signature Customization

Users can change their avatars and personal signatures.

3.2.9 Area and Communication Control

� Interaction control among IM service areas

The interaction policy for IM service areas is set on the server. Based on the policy,

clients can determine whether users can transfer IMs among these areas.

� Interaction control among file transfer areas

The interaction policy for file transfer areas is set on the server. Based on the policy,

clients can determine whether users can transfer files among these areas.

� Area function control


The administrator configures different functions in different areas so that users logging

in to different areas are provided with different functions. In practice, only enabled

functions that overlap with area functions are available to users.

3.2.10 User Permission Control

Lower-level users cannot directly communicate with higher-level users.

3.2.11 Statistics Collection and Audit

The BMU collect information from all the terminals (eSpace desktop, eSpece mobile, and

eSpace IP Phone) associated at some user, and provides statistics collection and audit

functions from:

� Field and behavior mode query and log audit

� Collection of statistics on the number of online users, conference information, and

system information

� Collection of statistics on the number of logins, users, and messages based on the day,

week, month, or year

3.3 Status Presentation

The eSpace Desktop and eSpaces IP Phones 79xx displays real-time contact status, so that

users can choose from various communication methods based on the contact status. This

improves communication efficiency.

� Default statuses: online, busy (showing busy, talking, and conferencing), away, offline,

and DND.

� Users can set the interval for automatically switching the user state to away when they

perform no operation or lock the screen. Users can enable or disable this function.

� Users can change the personal status. The change will be synchronized in real time on

online contacts' eSpace Desktops.

� Users can view the input status of the other party.

� Users can subscribe to the contact status notification service. After selecting a contact list

or a specified status, users are notified of status change of certain contacts or when the

specified status changes.

� If a contact is in a user's status blacklist, the contact learns that this user is always in the

offline status.

� If a user puts the mouse pointer on an offline contact, the eSpace Desktop automatically

displays the offline duration of the contact.

� The eSpace Desktop displays the geographic area of the other party based on the IP

address.

� Users can set the personal status on the taskbar menu.


3.4 Directory

3.4.1 Corporate Directory

The corporate directory is deployed on the BMU server and managed by enterprise

administrators. Enterprise administrators can enable or disable the corporate directory

function.

� Users can maintain the corporate directory on the eSpace Desktop, and perform the

following operations:

− Changing personal information

− Viewing contact information

− Querying contacts

− Adding personal directory records to the corporate directory

− Updating data

� Users can query contacts by name, phone number, work ID, and email address, and can

view detailed contact information.

� Users can initiate an IM or call by clicking the icon in the corporate directory.

� The corporate directory is displayed in a department tree. Users can select a department

from the department tree on the PC client to initiate an instant conference.

� Users can set default contacts in a department. The users in the same department can

view the default contacts in the contact list after logging in to the client.

3.4.2 Personal Directory

Personal directories store users' contact information, including name, phone number,

department, mobile number, office phone number, fax number, position, email address,

contact address, and post code.

� Users can maintain personal directories on the eSpace Desktop, and perform the

following operations:

− Search, add, sort, and delete contacts

− Manage personal directories

− Import contacts to, or export contacts from personal directories

� A personal directory must be supported by the BMU server and contains a maximum of

1000 contact records.

� Users can initiate IMs and calls, and transfer files by clicking the icon in personal

directories.

� The eSpace Desktop automatically records recent contacts, and users can clear the recent

contact list.

� Contacts in a personal directory can be sorted by status (online, busy, away, and offline)

or by group. After being sorted by group, contacts are further sorted by status or name.

� Users can import contact information from .xls or .csv files or from the local Outlook.

� Users can view contact information.

Contact information shows the image, name, status, position, department, address,

signature, and device information on camera and microphone. Users also can know

whether a contact has been offline for a long time.

� Users can view personal contact list.


The eSpace Desktop provides personal contact lists for users so that contacts in personal

contact lists can communicate with users in DND status.

� Users can view nicknames.

Users can set nicknames for contacts to easily name and distinguish them.

� Users add contacts based on the email address.

3.5 eSpace Desktop and IP Phone Interaction

3.5.1 Binding

The eSpace Desktop and an IP phone are bound when they are deployed. Users must set the

same DN number to the eSpace Desktop and the IP phone.

The eSpace Desktop can only bind one IP phone and has only one DN number.

3.5.2 Enabling/Disabling the Interaction Function

Users can enable or disable the interaction function on the eSpace Desktop.

3.5.3 Status Synchronization

eSpace Desktop can pop-up the prompt window, which shows hooking, calling and the

number IP Phone dials. Call Information Display

The eSpace Desktop bound to an IP phone displays a notification page displaying the IP

phone operation information, including the call status, incoming call notification, calling

number, and call process.

3.5.4 Call Control

Users can control the bound IP phone on the eSpace Desktop interface to hang up, hold, and

invite contacts to join a voice conference.

3.5.5 Assistant Dialing

When a user enters a contact number or selects a contact number from the corporate directory

on the eSpace Desktop, a call control page is displayed on the eSpace Desktop. Meanwhile,

the bounded IP phone automatically picks up and connects the call with the called party. The

call control page displays the call status as talking on the eSpace Desktop.

3.5.6 Controlling the Called IP Phone

The eSpace Desktop displays the call control page when a bound IP phone is called,

displaying the incoming call information and the call control icons for users to answer,

forward, or reject the incoming call.


4 Multimedia Conference

Multimedia conferences provide collaboration functions including video, desktop sharing, file

transfer, e-whiteboard, and text chat in addition to audio conference functions. Multimedia

conferences are implemented based on the eSpace Meeting server and built-in voice

conference server.

� A single eSpace Meeting server supports a maximum of 400 participants in data

conferences with 400 standard definition (SD) video channels or 400 participants in data

conferences with 100 high definition (HD) video channels. A single conference site

supports a maximum of 400 participants in data conferences with 400 SD video channels

or 400 participants in data conference with 100 HD video channels. The eSpace Meeting

client can display 16 channels of concurrent videos.

� English and Chinese languages are supported.

� Integration with Huawei Telepresence solution (MCU’s) allow to create multipoint Video

Call between any on the video codecs standard H.261, H,263 and H.264 and it support

bridge between SIP and H.323

� Users can create scheduled and instant multimedia conferences.

� Scheduled multimedia conference: A user can create a scheduled conference in the

eSpace BMU. After creating a scheduled conference, the creator notifies participants of

the conference information by sending emails or short message service (SMS) messages

using the SMS modem or customized management application server (MAS). The MAS

must be customized, and its customization workload is calculated based on the

integration interfaces provided by the local carrier.

� Instant multimedia conference: A user can hold an instant multimedia conference on the

eSpace client.

4.1 Document Sharing

Participants can view shared documents in real time, which improves communication

efficiency.

Supported documents formats include PPT, Word, Excel, PDF, and other formats that support

the Print command.

Diversified comment functions such as page control, text entering, and figure insertion are

provided.

� Document management: Participants can open, save, and close shared documents.


� Page control: Participants can page up, page down, and view document titles on the

document title list to view the document content.

� Display control: Participants can display documents in full screen mode and use the laser

pen function to mark a document.

� Annotation:

− Freehand draw: Participants can use it to draw smooth curves in colors.

− Text area: Participants can enter text annotations and set text properties.

− Tick, cross, and pointers.

− Drawing: Participants can draw hard curves with a pencil, select shapes (such as

those generating rectangles, lines, and ovals), and set drawing properties.

− Annotation handling: Participants can select and remove annotations, and use

multiple tools to delete annotations.

The moderator can assign rights to participants so that they use authorized functions.

Common rights include opening, saving, and printing documents, paging up and down, and

annotation.

4.2 Desktop Sharing

� The presenter can share the desktop, or share one or more operating applications with

participants. This synchronizes the presenter's operating applications on all participants'

screens.

� The presenter can share a participant's personal desktop or running applications with

other participants, remotely control the desktop, and annotate on the desktop. If the

participant agrees to share the personal desktop or running applications, the operations

on the desktop or applications are synchronized to all participants' screens in real time.

A participant can assign the desktop operation right to another remote participant so that the

remote participant can control the desktop remotely.

4.3 e-Whiteboard

Participants can draw structural diagrams and write on the e-whiteboard. Participants can also

create blank pages, and copy or delete the whiteboard.

All participants can write on the e-whiteboard and control e-whiteboard pages based on

assigned rights.

4.4 Poll

In a multimedia conference, participants can take a poll. The presenter can initiate a poll, ask

participants to complete questionnaires, and collect feedback. Only the presenter can initiate a

poll. The moderator and participants have rights to take a poll.

In a conference, the presenter can:

� Initiate a poll.


The presenter can add questions to a questionnaire, set the end time to submit the feedback,

and start the poll. The poll ends when the preset end time arrives.

� Modify and delete questionnaires that the presenter designs.

� View the detailed poll statistics and end a poll before the preset end time arrives.

After receiving a questionnaire, participants can answer questions on the questionnaire and

submit the feedback.

4.5 File Transfer

The moderator can transfer local files to other participants. After being authorized by the

moderator, a participant can also transfer and save files. Only the moderator can delete files.

The maximum size of a file that can be transferred is 25 MB.

4.6 Note Taking

Participants can take and save notes.

Notes taken in different conferences are stored in the same .txt file. Each note is marked with

the time.

4.7 Bulletin

On the bulletin, participants can view the latest conference information and various types of

information sent by the moderator.

4.8 Text Chat

Participants can chat by text messages in the public or private chat window.

� Public chat: In the text communication area, a participant selects all participants, enters a

message, and clicks Send or presses Enter to send the message to all participants.

� Private chat: Authorized participants can select one or more participants to initiate a

private text or voice chat.

The moderator can assign text chat rights to a participant so that the participant can chat with

the moderator, presenter, or other participants.

4.9 Video Conference

A video conference allows participants to:

� View the standard video window, video display alternating windows, and video windows

managed by cameras.

� Control a video window:


− Display the camera control panel.

− Allow an authorized participant to control another participant's camera.

− Modify video settings.

− Capture screenshots.

− Process a video.

� Adjust the video display layout:

− A maximum of 16 videos can be displayed simultaneously or in the alternating video

display mode.

− A common display provides 15 video display layouts.

− A (16:9) wide display provides 8 video display layouts.

� Display videos alternately. The system can cyclically display all available videos in turn.

The moderator assigns rights to participants so that they can control audio and video effects of a

conference. For example, they can enable the camera and microphone, and play videos.


5 eSpace UMS

The UMS stores and manages messages such as voice messages and fax messages, in a

unified manner.

5.1 T-Star UMS

The T-Star UMS communicates with eSpace U19xx series IP PBX through a SIP trunk to

provide voice and fax mailboxes. All voice and fax messages are stored on the UMS server.

The IP PBX and UMS server are core devices in the T-Star UMS solution. The UMS server

and email server must be connected properly, and the email server must support standard

simple mail transfer protocol (SMTP) and POP3 protocols.


Figure 5-1 T-Star UMS network

5.1.2 Voice Mailbox

The voice mailbox allows users to:

� Leave a voice message: Users can register the following services:

− Call transfer to voice mailbox unconditional (CTVMU)

− Call transfer to voice mailbox on no reply (CTVMNR)

− Call transfer to voice message on busy (CTVMB)

− Call transfer to voice message on offline (CTVMO)

� Receive a voice message notification through:

− MWIs on PC clients and specified IP terminals

− Calls

− Emails

� Retrieve a voice message by using phones, from emails, and on web pages.

5.1.3 Fax Mailbox

The fax mailbox allows users to:

� Leave a fax message after dialing the unified access code or unique access code assigned

for one account.

� Receive a fax message notification through:



− Calls

− Emails

� Retrieve a fax message:

− Using a fax machine

− From an email

− Following IVR announcements on a phone to send the fax message to a specified fax

machine to print

− In the UMS web system

5.1.4 Message Forwarding

After users log in to the UMS web system, they can forward received messages to other users.

Voice messages and fax messages can be forwarded to a group of recipients.

5.1.5 Restrictions

� IVR announcements and web pages are supported in both English and Chinese.

� A maximum of 8000 users and 400 concurrent voice and fax messages are supported.

� Voice files are in the WAV format. In addition, a-law and µ-law codec modes are

supported.

� Each mailbox stores a maximum of 1000 messages (20 voice and fax messages by

default).

� The default duration of a voice message is 2 minutes. Users can set the duration to 1 to

15 minutes as required.

� The UMS and IP PBX use the T.38 fax mode.

� Fax files are sent on G3 Tagged Image File Format (TIFF) A4 pages. Fax contents

cannot exceed 50 KB on each page.

5.1.6 Others

� Mailbox users can obtain unified mailbox information from multiple channels, such as

answering notification calls, dialing query numbers, checking emails, checking the MWI

on the phone.

� The administrator can make outgoing call notification policies to remind users of voice

or fax messages. In an outgoing call notification policy, the administrator can set the

maximum number of call attempts upon a failure, interval for remaking calls, start time

and end time for remaking calls, and time segments when the policy takes effect.

� Users can set personal greetings for message leaving.

5.2 Movius UMS

For detailed Movius UMS functions, see the Huawei Movius Mereon Technical Proposal.


Huawei Movius

Mereon Technical Proposal Template_v2_rev02.doc

5.2.1 Voice Mailbox

The voice mailbox allows users to:

� Leave a voice message: Users can register the following services:

− CTVMU

− CTVMNR

− CTVMB

� Receive a voice message notification through:


− Calls

− Emails

− SMS messages (The short message service center (SMSC) must be deployed.)

� Retrieve a voice message by using phones, from emails, and on web pages.

� Be notified of missed calls. These calls are transferred to the UMS when no voice

message is left.

� The user can turn on or turn off their voice mail

� All system administration accessible through web interface

� Class-Of-Service means the ability to apply a set of parameters to a subscriber's account

by associating the account with a COS. All subscribers assigned to a particular COS use

the values set in the assigned COS.

� Voice Message length: 1-15 minutes configurable in COS; Default 90 sec.

� Message per Mailbox: 1-255 messages configurable in COS; Default 20 messages

5.2.2 Fax Mailbox

The fax mailbox allows users to:

� Leave a fax message after dialing the unified access code or unique access code assigned

for one account.

� Receive a fax message notification through:


− Calls

− SMS messages

− Emails

� Retrieve a fax message:

− Using a fax machine

− From an email

− Following IVR announcements on a phone to send the fax message to a specified fax

machine to print

− In the UMS web system


5.2.3 Direct Callback

This service enables the system to call back users when they retrieve messages and on busy

mode.

5.2.4 Restrictions

� IVR announcements and web pages are supported in English, traditional Chinese, Spanish,

or Brazil Portuguese. A project only supports one local language in addition to English

that is the default language.

� A maximum of 2,000,000 mailboxes are supported. The mailbox capacity (in MB) is

configurable. Each mailbox saves a maximum of 1000 voice or fax messages. The

duration of a voice message ranges from 1 to 10 minutes.

� Voice files are in the WAV format. In addition, adaptive multirate (AMR) and µ-law

codec modes are supported.

� The UMS and IP PBX use the T.30 or T.38 fax mode.

� Fax files are sent on TIFF A4 pages. Fax contents cannot exceed 20 KB on each page.

5.2.5 Greetings

Users can set personal greetings, such as greetings on busy, holiday greetings, off-work

greetings, and voice recording of user names.


6 eSpace Desktop

Huawei PC client eSpace Desktop is an application with special value-added features that

runs on the Windows operating system. The eSpace Desktop supports functions such as CLIP,

call history, call status display, and personal and corporate directories.

The eSpace Desktop also integrates functions such as IM, SMS, email, and personal service

management, which improves the work efficiency and employee satisfaction.

The eSpace Desktop supports Chinese (simplified and traditional), Portuguese and English

languages.

The eSpace can make a call to a contact using the Outlook address book or lotus

The eSpace Desktop support the follow voice features: Transfer, conference, hold, mute,

secretary services, call park, call pick-up, with/black list, sequential ring, call history,

(incoming call records, outgoing call records, and missed call).


6.1 Basic Call

The eSpace Desktop supports basic voice calls, P2P video calls, call transfer, and CLIP. Basic

voice calls include calls between eSpace Desktops and between eSpace Desktops and other

intra-office or outer-office clients. P2P video calls include calls between eSpace Desktops and

between eSpace Desktops and intra-office video phones.

The eSpace Desktop supports VAD and EC.

6.1.1 Voice Call

The Space PC client supports basic voice calls, including calls between eSpace Desktops and

between eSpace Desktops and phones. eSpace Desktops provide the following functions:

initiate calls, hang up outgoing calls, hang up incoming calls, answer incoming calls, and

display calling party information.

6.1.2 Video Call

The eSpace Desktop supports P2P video calls, including calls between PC clients and between

PC clients and video phones.

6.1.3 Call Transfer

eSpace Desktop users can enter a phone number during a conversation and click to

transfer a call to a third party. The third party can receive an incoming call notification and

answer the call.

Figure 6-1 Call transfer on the eSpace Desktop

When there is an incoming call, a eSpace Desktop user can click and enter a phone

number to transfer the call to a third party immediately.

6.1.4 Call Hold and Unhold

On the eSpace Desktop, a user can hold the current call before calling another contact or

answering another call. The held user hears the call waiting music and can resume the

conversation after the call is unheld.

Requirements:

� Users can hold only one contact while talking with another contact, and click to

switch the call between them.


� A held call is automatically unheld when the ongoing call is released or when the other

contact cannot be connected.

6.1.5 Two-Stage Dialing

During a conversation, eSpace Desktop users can click and perform two-stage dialing

using the displayed dial plate.

Figure 6-2 Two-stage dialing on the eSpace Desktop

6.1.6 Call Recording

As a software terminal, the eSpace Desktop allows a user to directly talk to users that use any

terminals. The user can record the ongoing conversation, and query recordings in the

recording history. Recordings are saved on a local disk. Available disk space determines the

maximum number of recordings that users can save.

6.1.7 CLIP

6.1.7.1 Caller ID Display

When there is an incoming call, the eSpace Desktop displays the calling party

information such as the calling party's number and name on the screen, and displays the

call duration when the call is connected.

6.1.7.2 CLIP on the Tray

When there is an incoming call, a window is displayed at the lower-right corner of the

screen, containing operation buttons and calling party information such as the calling

party's name, phone number, and home area. The window disappears only when the call

is either answered or ended without being answered. The called party can reject or

answer the call by clicking the corresponding button in the window.

6.1.8 Historical Records

The eSpace Desktop stores historical chat records, call records, and SMS message records.

Call records are composed of details about missed calls, received calls, outgoing calls, and all


calls. Call information includes the peer party's name, phone number, start time, and call

duration. Users can delete a call record or clear all records, and can initiate a call to a numbers

in call records.

Call history is saved on a local disk. Available disk space determines the maximum number of

records that users can save.

6.1.9 Integration with USB Phones

The eSpace Desktop can be integrated with USB phones to provide users with the same VoIP

experience as using mobile phones or telephones, higher voice quality, and lower costs.

6.1.10 Status-based Incoming Call Routing

The eSpace Desktop supports status-based incoming call routing. For example, an incoming

call is automatically transferred to the mobile phone if the user's client status is Away, or to

the fixed-line phone if the user's client status is Idle.

6.1.11 Call Redirection

The eSpace Desktop can redirect incoming calls to other phone numbers (internal extension

numbers or external numbers) or voice mailboxes.

6.1.12 MWI

The MWI blinks when the eSpace Desktop receives a voice or fax message.

6.2 eSpace Desktop and IP Phone Interaction

The eSpace Desktop interacts with IP phones. For details, see 3.5 eSpace Desktop and IP

Phone Interaction.

6.3 Status Presentation

The eSpace Desktop supports status presentation. For details, see 3.3 Status Presentation.

6.4 IM Service

The eSpace Desktop supports IM services. For details, see 3.2 IM Service.

6.5 Instant Conference

Users can create and join an instant conference on the eSpace Desktop. Users can create a

conference, invite participants by using personal or corporate directories or entering

participants' numbers, remove participants from a conference, change participants' rights, re-

invite participants, control participants' talk rights or data operation rights, and display

participants' statuses.


6.5.1 IM Conference

An eSpace Desktop user can select multiple contacts to invite them to join an IM conference

where they can communicate using IM messages.

A user can create an IM conference in the following ways:

� In an IM window, click to add contacts to an IM conference, or drag the contact

avatars directly to the window from the corporate or personal directory.

� On the eSpace Desktop main page, click and select contacts to join an IM

conference.

� In the corporate or personal directory, click contacts when pressing Ctrl, right-click on

selected contacts, and choose from the shortcut menu to initiate an instant conference.

� A maximum of 30 participants are supported in a conference.

6.5.2 Instant Voice Conference

Users can communicate in an instant voice conference on the eSpace Desktop.

In an instant voice conference, the eSpace Desktop displays participants and their statuses in

the conference participants' list. During a conference, the conference creator can invite other

participants to join the conference, remove participants from the conference, allow or forbid

participants to talk, and end the conference.

A maximum of 30 participants are supported in a conference.

6.5.3 Instant Multimedia Conference

In an instant multimedia conference, eSpace Desktop users can draw or write on the e-

whiteboard, initiate a voting session, share desktops, use moderator functions, and

communicate in text.

For details, see 4 Multimedia Conference.

A maximum of 30 participants are supported in a conference.

6.5.4 Smooth Conference Upgrade

Users can easily upgrade conferences in the following sequence: IM conference > voice

conference > multimedia conference.

During a two-party IM or voice conversation, a participant can add more participants to form

an instant IM, voice, or multimedia conference.

6.6 Scheduled Multimedia Conference The eSpace Desktop allows users to schedule multimedia conferences. User can:

� Create scheduled multimedia conferences that provide audio, video, and data functions

� Join or leave conferences

� Control participants' speak and data operation rights

� Display participants' statuses


� Share desktops, documents, and videos

� Draw or write on the e-whiteboard

� Initiate voting

� Raise hands

� Take notes

� Communicate by text

� Release bulletins

6.7 ONLY Service

The eSpace Desktop supports the ONLY service. For details, see 3.1 ONLY Service.

In the ONLY service, the same calling number (ONLY number) is displayed for calls made

using different terminals. When the ONLY number is called, terminals to which the ONLY

number is bound ring simultaneously or sequentially. In addition, bound terminals share the

same supplementary services.

6.8 SMS Messages and Emails

The eSpace Desktop can receive SMS messages, send SMS messages to a single recipient or a

group of recipients, and send conference notifications by SMS messages. The eSpace Desktop

can use an SMS modem or MAS to send SMS messages. Users can query SMS message

records on the eSpace Desktop.

� The eSpace Desktop can receive SMS messages only in MAS mode.

� The MAS must be developed and configured based on the site requirements for sending

and receiving SMS messages. The MAS integration capability depends on the integration

interfaces provided by the local carrier.

On the eSpace Desktop, a user can select contacts from the personal directory and send emails

to them if their email addresses are provided. This automatically starts the default email

program on the PC.

6.9 Corporate Directory

The eSpace Desktop supports the corporate directory. For details, see 3.4.1 Corporate

Directory.

6.10 Personal Directory The eSpace Desktop supports the personal directory. For details, see 3.4.2 Personal Directory.


6.11 Enterprise Bulletin

The eSpace Desktop supports bulletin management, bulletin pushing, online bulletins, offline

bulletins, and bulletin history. The BMP server pushes bulletins to the eSpace Desktop and

displays them in pop-up windows. If a user is offline, the server pushes a bulletin to the

eSpace Desktop when the user logs in to the PC client next time. In addition, bulletins can be

pushed to specified users.

6.12 Self-Service Self-services include conference management, service registration, bill information query, and

ONLY service configuration. This allows users to conveniently serve themselves. For

example, users can update personal information in the corporate directory, modify the ONLY

service configuration, register services with IP PBXs, and schedule conferences. Users can

add, modify, and delete customized tasks.

6.12.1 Conference Management

Users can create and manage scheduled conferences, and view information about the

scheduled conferences that they have created or will participate in.

6.12.2 Service Registration

Users can view services registered on UC accounts. They also can register other enabled

services that have not been registered or used, such as the call waiting service and DND

service.

6.12.3 CDR Query

eSpace Desktop users can query detailed CDR based on search criteria, collect statistics on

CDR, and export query results to excel files.

6.12.4 ONLY Service Configuration

eSpace Desktop users can manage the ONLY service information, including viewing and

modifying the ONLY account information and viewing, adding, modifying, and deleting

bound terminals.

6.12.5 Personal Account Maintenance

Users can release, update, and maintain their personal information on the corporate directory

server.

6.13 My Workspace

Users can add frequently-visited URLs to My workplace on the eSpace Desktop, and click a

URL to display the page in Internet Explorer. This integrates My workplace with the

enterprise system.


6.14 Other Functions

6.14.1 Login

The administrator sets the IP address and port number of the eSpace server before user login

so that the eSpace Desktop automatically obtains information from the eSpace server and

supports automatic login and automatic startup with the Windows operating system.

Users can log in to the eSpace Desktop with their unique UC accounts. A user cannot log in to

multiple PC clients with the same account. If a user logs in to client B with an account that

has been used to log in to client A, the user automatically logs out of client A and receives a

logout prompt message.

The login UC account and BMU account are the same, and contains digits, letters, and

underscores. Case sensitivity is ignored.

� The login account is a string of 2 to 64 characters containing digits, letters, and

underscores. The password is a string of 6 to 15 characters that cannot contain the

following special characters:

− Angle bracket (< and >)

− Ampersand (&)

− Double quotation marks (")

− Single quotation marks (')

� Users can clear the historical login accounts on the login page.

� Users can log in to PC clients offline and view historical records.

6.14.2 System Configuration

On the eSpace Desktop, users can modify personal information, change status, set parameters

about automatic login, automatic IM reply, shortcut keys, audio parameters, audio devices,

GUI modes, and languages.

6.14.3 Installation and Upgrade

The eSpace Desktop can be installed, uninstalled, and automatically upgraded. After

accepting the license agreement, users can select an installation directory, choose whether to

add installation and uninstallation programs to the startup menu, and whether to create a

shortcut icon for the eSpace Desktop. During uninstallation, installation files, shortcut icons,

and programs in the startup menu are deleted. During automatic upgrade, the upgrading

process and new features of the latest version are displayed.


7 eSpace Mobile

Huawei mobile client eSpace Mobile is installed on a mobile phone. After being registered

with the enterprise UC system, the eSpace Mobile provides the following functions:

� IM

� Group chat

� Contact list management

� Status presentation

� Corporate and personal directories

� Click to dial (CTD) service

Figure 7-1 eSpace Mobile access

The eSpace Mobile interacts with the mobile access agent (MAA). The MAA functions as a

third-party server to invoke interfaces provided by the UC to provide functions.

The BMU provides simple object access protocol (SOAP) interfaces and BIN channels, to

interact with IP PBX to offer CTD services, and provides HTTP interfaces and user datagram

protocol (UDP) channels to interact with the eSpace server to offer other services.

� ESpace Mobiles support iPhones and Android-based mobile phones.

� Users cannot create and manage chat groups on eSpace Mobiles.

� A user can use the same user name and password to log in to the eSpace Mobile and PC

client. If a user has logged in to one client and attempts to log in to another client, the

system automatically logs the user out of the preceding client.


7.2 Startup and Login � Setting login domain name

Users on the mobile phone clients can enter the domain name to log in to the server.

� Querying and upgrading the mobile client version

Transmission control protocol (TCP) is used as the handshake protocol between the

mobile client and MAA server to obtain upgrade information for the mobile client.

� Logging in, logging out, and obtaining server information on the mobile phone client

Users on the mobile clients can log in to eSpace server to obtain server information after

logging in to MAA. Users can log out of the mobile clients.

� Binding the account to the universally unique identifier (UUID) or international mobile

equipment identity (IMEI) of the mobile phone.

The mobile client automatically sends UUID or IMEI to the server during user login.

The server authenticates the binding relationship based on the user account, password,

and the UUID or IMEI of the mobile phone.

� Detecting the network and automatically reconnecting the mobile client to the network

after an intermittent disconnection

After the TCP link is established for the mobile client, the mobile client is automatically

connected to MAA when the network is restored from intermittent disconnection.

7.3 Personal Information � Upgrading the personal status and signature

After logging in to the mobile client, users can update the personal status and signature.

7.4 Personal Directory � Completely downloading the personal directory

The mobile client can completely download the personal directory that is saved on the

server after user login.

� Incrementally updating the personal directory

If directory information is updated on the server, the mobile client automatically updates

the personal directory when a user logs in to the mobile client. Users can also click a

button on the mobile client to update the personal directory data.

� Managing contacts in groups

Users can store their information such as the UC numbers and phone numbers in the

personal directory.

� Integrating the local mobile phone directory

Users can view the local directory of mobile phones in the personal directory.

� Viewing detailed contact information

Users can view detailed contact information on the mobile client.

� Calling contacts

Users can select contacts from the personal directory to initiate CTD calls to them.

� IM session


Users can select contacts from the personal directory to initiate IM sessions with them.

� Querying contact information

Users can query contact information by keyword in the personal directory.

� Deleting contacts

Users can delete contacts from the personal directory after logging in to the mobile

client.

7.5 Corporate Directory � Querying a corporate directory

Users can query contact information by keyword (such as user name and user ID) in the

corporate directory. Fuzzy query is supported.

� Viewing detailed contact information

Users can query contact information by keyword and view detailed contact information.

� Adding contacts to the friend list

Users can query contact information by keyword and add contacts to the friend list.

� Initiating IM sessions

Users can query contact information by keyword and select contacts to initiate IM

sessions with them.

� Making calls

Users can query contact information by keyword and select contacts to make calls to

them.

7.6 IM Service � Two-party IMs

Users can send IMs to contacts after logging in to the mobile client.

� IM emoticons and common statements

Users can transfer emoticons and common statements provided by the system during IM

sessions.

� Obtaining offline IMs

Users can obtain offline IMs after logging in to the client.

� IM history

The mobile client stores IMs that users have received and sent on a local mobile phone.

Users can manage historical IMs using the uniform message manager provided by the

mobile client. For example, the user can delete IM records or set the IM storage period.

The user cannot view historical IMs when logging in to the mobile client using another

mobile phone.

7.7 Audio Service � Initiating CTD calls


Users logged in to the mobile client can select contacts in the corporate or personal

directory or dial the contact number in the dial plate to initiate CTD calls.

� Support VOIP call within Wi-Fi network

The VOIP call is not support within 3G network.

� Viewing historical calls

Users can view historical calls on the mobile client. Historical calls include outgoing,

received, and missed calls.

7.8 Multiple Languages

Users can switch between Chinese (simplified and traditional)，Portuguese

and English languages on the user interface.

7.9 Configuration � Setting personal status

Users can set the personal status.

� Others

Users can set the online/offline notification, message pop-up, automatic response,

session reminding, and interface language.


8 Operation and Maintenance

8.1 eSpace BMU The BMU is a service management system based on the B/S architecture. The BMU provides

an easy-to-operate and self-service UC platform for common enterprise users and an easy-to-

operate service management UC platform for enterprise administrators.

The BMU integrates functions such as account management, service management, statistics

collection and query, department information management, conference resource management,

bulletin, and system management, and provides these functions for users on web pages.

� The response time for an HTTP connection request is 3 seconds.

� The maximum number of concurrent connections is 20.

� The maximum number of online users is 1500.

� The maximum number of eSpace U19xx series IP PBXs managed by the BMU is 8.

8.1.1 Common User Functions

All users can use the self-service to query call fees of phones bound to the current account,

register services, maintain account information, and manage conferences.

8.1.1.1 Scheduling a Conference

Users can schedule a voice or voice + data + video conference as required.

Parameters for scheduling a conference include:

� Conference topic

� Number of participants

� Moderator's password

� Participants' password

� Start time

� Conference duration

� Conference mode

� Announcement played when a participant joins a conference

� Announcement played when a participant leaves a conference

� Conference information description


8.1.1.2 My Conference

Users can view conference information, join and manage conferences (such as modifying

conference information and canceling conferences).

Users can query and manage ongoing conferences, scheduled conferences, and conferences to

join, query information about historical conferences based on the conference topic, conference

ID, voice/data start time, and voice/data end time, view detailed conference histories, and

export conference histories.

8.1.1.3 Self-Service

Self-service contains personal information maintenance, ONLY service configuration, service

registration, and call fee query.

� Personal information

This function is used to maintain the information about the current account. Once the

information is modified, the related personal information is refreshed in the corporate

directory at the same time.

� ONLY service

The ONLY service refers to a service in which multiple terminals of a user share the

same number and the same supplementary service. The number is the number of an

intra-office terminal. If a number is called the ONLY number, the terminal functions as

the main terminal. Users can select the main terminal. When other users call the ONLY

number of a user, the terminals of the user ring according to the preset rules, and the user

can answer the call on any one of these terminals.

Users can use the ONLY service to configure ONLY number information about the

current account to bind, change, unbind a phone number, and set the ringing mode and

the set time segment when the ONLY number takes effect.

� Service registration

This function is used to register voice services for phone numbers bound to the current

account. Voice services can be registered only when the BMU communicates with the IP

PBX, the account is bound to the allocated phone number on the IP PBX, and the service

right of the phone number is enabled.

� Call fee query

A user can query fees of a phone number bound to the current account. The user can also

query fees according to the time and phone number of the other party. In addition, a user

cannot query fees for an account that is not bound to phone numbers. A user can export

the query result to an Excel file as required.

8.1.1.4 Changing a Password

This function is used to change the login password.

8.1.1.5 Multiple Languages

Simplified Chinese, traditional Chinese, Portuguese and English are supported.


8.1.2 Administrator Functions

8.1.2.6 Account Management � Account list

Administrators can operate the department tree, query, add, and delete a UC account,

query account information based on the role level, account type, UC account, name, self-

service ID, or position, and export the query result.

− Adding a UC account

Administrators can use the following methods to add UC accounts:

Creating a single UC account by configuring the following information:

� UC account

� Number allocation policy

� Name

� Gender

� Password allocation mode

� Role

� User level

� Whether to keep secret

� Email address

� Department

� Work ID

� Position

� Mobile phone number

� Other phone number

� Fax

� Personal home page

� Postcode

� Address

Creating UC accounts in batches according to the phone number by configuring the

following information:

� Number allocation policy

� Number segment

� Number interval

� Whether to enable the UC service

� Password

� Confirming the password

� Role

� User level

� Department

After the information is configured, UC accounts are generated in batches. By

default, the gender is male and the information is public.

Creating a UC account by importing an Excel file:


Download the Excel file template

Configure the UC account information in the template

Upload the Excel file. (A maximum of 5000 UC accounts can be imported at a time.)

Set the account importing policy:

Select the imported accounts or the original accounts if the imported accounts are the

same as accounts exit in the system

Select the passwords of the imported accounts or the original accounts if the imported

accounts are the same as accounts exit in the system

Select the default values or values corresponding to the original accounts if the

mandatory parameters are invalid

Select the default values if the optional parameters are invalid

After UC accounts are imported in batches, the importing result is displayed.

− Modifying UC account information

− Deleting a UC account

Administrators can delete a UC account, and can view the details of the UC account,

perform service configuration, and manage restricted accounts.

− Service configuration

For details, see the single number service configuration in Number Service

Configuration.

− Call-restricted account management

Administrators can add, modify, and deleted call-restricted accounts under the current

UC account. Administrators can make calls on any phones with call-restricted

accounts and passwords. Each call-restricted account corresponds to specified outer-

office call rights, which are irrelevant with phones.

Administrators can add call-restricted accounts by selecting an IP PBX, and setting

the call-restricted account, password generation mode, call-restricted password, and

call rights.

eSpace UC provides the following call rights:

Intra-office call

Local call

National call

International call

Administrators can change the passwords and call rights of call-restricted accounts

but cannot change call-restricted accounts.

After the call-restricted account service is disabled, no call-restricted account exists

under the current UC account.

� Department Management

1. Users can add departments, and specify the administrator of the designated

department;

2. By default, the rights are not related to departments.

3. If the feature is enabled, the rights of a department administrator can only be used

within the specified department. Multiple administrators can be specified for a

department.

� Number allocation policy maintenance


Before adding a UC account, administrators need to specify the number allocation

policies. Number allocation policies indicate the attributes of the service numbers bound

to the UC account.

− Adding policies by configuring the following information:

Policy name

IP PBX

Local gateway ID (When both active and standby IP PBXs are faulty, the local

gateways enables local survival.)

Whether to add the intra-office prefix automatically (If the intra-office prefix is not

set on the IP PBX, set this parameter to Yes. Then the system automatically set the

first digit of the number as the intra-office prefix.)

Authentication mode (not authenticated, authentication based on the IP address,

authentication based on the password, authentication based on the password and the

IP address)

Rights (Different rights are assigned to users of different levels, including default,

common, advanced, and super users.)

Whether to enable the policy

− Changing policies

Administrators can change policy-related parameters as required.

− Deleting policies

Delete policies.

� Role management

Each role can have different rights. The BMU supports the default role and customized

roles. Administrators can allocate rights flexibly to customized roles.

Administrators are allowed to set the maximum number of roles, and add, modify, and delete

roles.

− Setting the maximum number of roles

Administrators can set the maximum number of roles from 1 to 9999.

− Adding a role

Administrators can set the role name, description, and rights.

− Modifying a role

Administrators can modify the role description and rights as required.

− Deleting a Role

Administrators can delete a role.

� User level maintenance

Administrators can manage users in levels. With this function, users in lower levels using

an eSpace PC or mobile client, or other terminals cannot view information about users in

higher levels in the corporate directory. User levels are classified into 20 levels in an

ascending mode.

Administrators can add, modify, and delete a user level.

− Adding a user level

Administrators can set the user level name, user level, and description.

− Modifying a user level

Administrators can modify the user level name, user level, and description as

required.


− Deleting a user level

Administrators can delete a user level.

� SIP number maintenance

SIP numbers indicate the numbers of analog phones, IP phones, SoftConsole clients,

and eSpace Desktops that are connected to the IAD.

This function is used to manage all SIP numbers on the managed IP PBXs, including

adding, modifying, and deleting SIP numbers in batches.

� POTS number maintenance

POTS numbers are analog user numbers on the IP PBX.

This function is used to manage all POTS numbers on the managed IP PBXs, including

adding, modifying, deleting, and managing number status in batches. Number status

includes all, idle, busy, faulty, and conferencing.

� Service configuration for numbers

After authorizing a user to customize services, the administrator can use services

provided by the IP PBX after service registration. Before configuring the service, the

administrator must select one of the following modes to add the number to configure

services with.

− Service configuration of a single number

Administrators can configure services for a single number or a number segment. The

BMU supports simple and complicated configurations.

The following simple services can be configured on the BMU:

� Call Forward Unconditional

� CFNR

� CFB

� Call forwarding offline (CFO)

� Call transfer internal and external

� Call waiting (CW)

� Call out restriction

� Three-party call

� Local number query

� Anonymous call restriction

� Listening

� CLIP

� Secretary

� Secretary station

� DND

� Absent subscriber

� Multiple calls

� Status-based call forwarding

� CBNR

� Ringing

� Alarm

� Hotline

� Abbreviated dialing


� Pickup

� Call-out restriction

� Instant conference

� Conditional call forwarding

� Status checking

� Break-in

� Forced release

� Attendant override

� Privilege user

� Call back on busy (CBB)

� Last number redial

� Registered call on busy (RCB)

� Call park

� Transferring missed call to SMS

� Calling line identity restriction override (CLIRO)

� External RBT

The following complicated services also can be configured on the BMU:

� Advanced secretary

� Voice playing and recording

� Multi-number

� Call rights

� Authorization codes for toll numbers

� Number replacement on the same phone

� Number replacement on different intra-office phones

� Voice mailbox

� Fax mailbox

� ONLY

� Group pickup

� PBX line selection

− Service configuration for numbers in batches

After downloading the Excel template, setting the numbers to configure services

with, and uploading the Excel file, the administrator selects the IP PBX, and

configures services for numbers in batches.

− Service configuration for sporadic numbers in batches

After the IP PBX and enterprise domain is selected, the administrator adds sporadic

numbers, and configures services for sporadic numbers in batches.

8.1.2.7 Console Group Management

The Console system provides services by communicating with the IP PBX. A Console group

consists of multiple Consoles.

Administrators can query, add, modify, and delete Console groups on the BMU, and can add

and delete Console numbers in Console groups.


� The administrator can configure multiple access codes for a Console group so that

different numbers can be displayed for internal and external users. The Console number

is displayed by default.

� The administrator can configure night service number, VU number, queuing duration,

Console all busy/all offline/all logout time segment, and processing policies for new

calls.

8.1.2.8 Statistics Collection and Query

System and common administrators have rights to collect CDR statistics, statistics on eSpace

Desktop information, and conference statistics, query CDRs, and manage conferences.

� CDR statistics collection and query

Queries CDR information by different criteria and exports query results to Excel files.

− CDR query

Queries detailed CDRs by call number, home location, and exports query results to

Excel files as required.

− CDR statistics

Collects statistics on CDRs by different criteria and exports CDRs to Excel files. For

example, if the administrator collects statistics by department, the information such as

number of calls made by a specified department and its sub-departments is displayed.

� eSpace Desktop information statistics

Queries and collects statistics on eSpace Desktop information by different criteria,

displays query results and statistics on pages, and exports query results and statistics to

Excel files.

− Voice quality statistics

Measures the conversation quality. The voice quality is classified into the following

six levels:

� 5.0 (very good)

� 4.0–4.9 (good)

� 3.0–3.9 (average)

� 2.0–2.9 (poor)

� 1.0–1.9 (very poor)

� <1.0 (extremely poor)

Queries voice quality by calling party, called party, voice quality, report party's IP

address, and time to collect statistics.

− User number view

Displays the total number of online eSpace clients and license information.

License information contains:

� Maximum number of available eSpace clients

� Total number of eSpace clients in use

� Total number of idle eSpace clients

− Enterprise user statistics

Queries and collects statistics on the number of enterprise users, including the total

number of enterprise users, total number of eSpace clients in use, and statistics time

based on the start and end dates.

− Log auditing


� Queries message and login logs, collects log statistics, and configures the

processing time.

� Queries message and login logs and collects log statistics by log type, sending

party account, receiving party account, sending party's IP address, receiving

party's IP address, receiving time, and message content.

� Conference management and statistics

Manages conferences and collects conference statistics by different criteria.

− Conference management

Queries all conferences by different criteria, and modifies and deletes conferences.

− Conference statistics

Queries and collects statistics on conferences by IP PBX, start date, and end date, and

displays results in graphics.

8.1.2.9 Function Maintenance � IP PBX maintenance

Manages all resources on managed IP PBXs, including IP PBX interconnection

configuration, ONLY time segment management, SMS templates for notifying of missed

calls, and enterprise domain management.

− IP PBX interconnection configuration

Adds, modifies, and deletes IP PBX-related parameters, including IP PBX name, IP

PBX IP address, port, whether to enable the active/standby IP PBX server, IP PBX

area code, access prefix, and description. Views the IP PBX connection status, IP

PBX run logs, and CDR pool, and synchronizes data.

− ONLY time segment management

Queries ONLY time segment information by start time, end time, IP PBX, and day,

and adds, modifies, and deletes ONLY time segments.

− SMS templates for notifying of missed calls

Sets the SMS for notifying of the missed calls for enterprise users.

− Enterprise domain management

Views and changes enterprise domains. The following table describes the enterprise

domain-related parameters.

Enterprise Domain-Related Parameter

Description

Enterprise name A node is added in the navigation tree on the left of the page

displayed after you choose UC Account > UC Account List. The

node name is the enterprise name.

Enterprise domain When multiple enterprises are supported, specify a domain name for

each enterprise. The format of the UC account is xx@Enterprise

domain name, for example, test@huawei.

Enterprise domain

ID

Enterprise domain ID on the IP PBX.


Enterprise Domain-Related Parameter

Description

Maximum number

of users

Maximum number of conference participants that the enterprise

domain supports. The value depends on the license of the IP PBX.

Values 1 and 2 are invalid. In addition, for all the enterprise domains

under the same IP PBX, the total number of conference participants

cannot exceed the upper limit specified by the license of the IP PBX.

The total number of participants in all conferences cannot exceed the

value of this parameter.

Maximum number

of conference

rooms

Maximum number of conferences that the enterprise domain

supports. The total number of conferences cannot exceed the value of

this parameter.

Maximum number

of trunks

Maximum number of trunks that the enterprise domain supports.

Conference

internal displayed

number

Incoming call number that is displayed on intra-office participants'

terminals.

Conference

external displayed

number

Incoming call number that is displayed on outer-office participants'

terminals.

External number of

the enterprise

Enterprise number that is displayed when an enterprise user talks

with a user in other enterprise domains.

� Console maintenance

Tests and saves Console parameters, and synchronizes Console data. The following table

describes Console parameters.

Console Parameter Description

Address /Alternative address in

the Console address book

IP address of the enterprise address book server. The

alternative address is optional and you can set it when

the enterprise address book server and the eSpace server

are not on the same network.

Root directory name Root directory name of the enterprise address book

server.

Console directory user name User name for logging in to the enterprise address book

server.

Enterprise address book server

password

Password for logging in to the enterprise address book

server.

� eSpace client maintenance

System and common administrators have rights to maintain eSpace-related parameters

and configurations, including eSpace service maintenance, default friend configuration,


group maintenance, eSpace area rights, client parameter control, and eSpace service

configuration.

− eSpace service maintenance

Adds, deletes, and modifies services, sets the eSpace server IP address, and

downloads run logs.

− Default friend configuration

Administrators can add and delete default friends. The added friends will be

displayed in the friend list when a user logs in to the eSpace client.

− Group maintenance

A group enables enterprise users to communicate conveniently. Administrators can

manage groups and group members. Group members can view all groups that they

join in on the group tab page on the eSpace client.

− eSpace area rights

Areas are classified by IP address segment. Administrators can set area rights based

on IP address segments. An area belongs to only one role and an IP address belongs

to only one area. Administrators can set rights for users to send IMs and transfer files in

different areas.

− Client parameter control

Manages and sets eSpace-related parameters, for example, the file transfer mode.

Adds, modifies, and deletes eSpace client plug-ins, sets plug-in parameters, and

provides restoring functions.

− eSpace service configuration

Sets eSpace service-related parameters. The following table describes the eSpace

service-related parameters.

eSpace Service-Related Parameter

Description

Maximum number of

groups created by a user

Maximum number of groups that a user can create on the

eSpace client.

Maximum number of

group members

Total number of members in groups that are directly created

on the eSpace client.

Maximum number of login

users

Maximum number of users that log in to the eSpace client.

User level function After this function is enabled, users in lower levels cannot

query users in higher levels.

� Conference maintenance

System and common administrators have rights to maintain conference-related

parameters and configurations, including conference interconnection, conference access

code, and conference SMS and email notification template functions.

− Conference interconnection configuration

Configures the default number of participants and whether to enable the data

conferencing function in a voice conference. If the data conferencing function is

disabled, users cannot schedule a voice + data + video conference and data

conferences are unavailable on eSpace clients.

− Conference access code configuration


A conference access code is used for accessing a conference on the IP PBX. After a

voice conference is initiated, users can use different access codes to access the

conference on the IP PBX as prompted.

This function enables administrators to query, add, and delete conference access

codes.

Parameters related to conference access codes include:

� IP PBX

� Whether to allow PSTN incoming calls (If you select Yes, outer-office users can

also make PSTN calls. If you select No, only intra-office users can make PSTN

calls.)

� Conference access code (A string of characters consist of digits or two special

characters * and #. The string cannot end with #. The characters cannot be

duplicated.)

− Conference SMS notification template

Administrators can set a content template for conference SMS notifications in

enterprises.

− Conference email notification template

Administrators can set a content template for conference email notifications in

enterprises and restore the template's default settings.

8.1.2.10 System Management

System administrators have rights to maintain the client version and manage the system

bulletins, operation logs, and system configurations.

� Client version maintenance

� Releases new versions and deletes original versions.

� Releases version package, including installation files, version number, and

parameters about full upgrade, forcible upgrade, scheduled version, and remarks.

� System bulletin

Creates and edits bulletins, and sends them to eSpace Desktops. Queries bulletins by

topic, start time, and end time, and adds, modifies, and deletes bulletins.

Parameters related to system bulletins include:

� Recipient

� Bulletin topic

� Bulletin content

Administrators can select departments and users at the same time and set them as

recipients. Administrators can select multiple users at a time.

� Operation log

Operation logs record operations that are performed by users with different UC accounts,

such as changing binding policies and registering services. Administrators can query and

delete operation logs based on UC account, module, start time, end time, and operation

type.

� System configuration

Provides password, log, SMS service, and email service configuration functions.

− Password configuration

The following table describes the password-related parameters.


Password-Related Parameter

Description

Password validity

period

The value of this parameter ranges from 0 to 999, in days. The

default value is 90. It indicates that the system prompts users to

change passwords after 90 days. If this parameter is set to 0, the

current password is valid and the system does not prompt users to

change passwords.

Password security

level

The password consists of digits, upper-case letters, lower-case

letters, and special characters. The password has the following

levels:

� Level 1 (low): indicates a string of 6 to 15 characters.

� Level 2 (medium): indicates a string of 6 to 15 characters, which

must contain at least two options among digits, upper-case letters,

lower-case letters, and special characters.

� Level 3 (medium): indicates a string of 6 to 15 characters, which

must contain at least three options among digits, upper-case

letters, lower-case letters, and special characters.

Number of

password validity

times

When changing the password, the new password cannot be the same

as the passwords that have been used within the number password

validity times. Assume that the number of password validity times

is set to 2, and the original password huawei is changed to 123456.

If users want to change the password, the new password cannot be

huawei or 123456.

Forcible password

changing during

first login

If this parameter is selected, the system prompts a user to change

the password after the user logs in to the BMU system for the first

time.

Login restriction

after consecutive

login failures

If this parameter is selected and the number of consecutive login

failures reaches the specified value, the login of the user is restricted

during the specified period.

− Log configuration

The following table describes parameters related to the system log.

Log-Related Parameter

Description

Run log level Run logs of the BMU are stored in $logfileBMUbmu.log. In the

preceding directory, $ indicates the directory for installing the BMU

server.

Log levels in descending order are Error, Warn, Info, and Debug.

After the run log level is set, users can print logs in the current level

and higher levels.

Whether to delete

operation logs

If you select to delete the operation logs, the system automatically

deletes the operation log whose saving duration exceeds the

maximum value.


Whether to delete

historical

conferences

If you select to delete the historical conferences, the system

automatically deletes the historical conference whose saving

duration exceeds the maximum value.

− SMS service configuration

After the SMS service is configured, a user can send a conference notice in an SMS

message if the conference is scheduled successfully. The user can also use the SMS

service on the eSpace Desktop. The SMS modem and MAS services are provided for

different mobile phone clients to receive messages.

� If the MAS service is used, the eSpace Desktops can send and receive SMS

messages.

� If the SMS modem service is used, the eSpace Desktops can only send SMS

messages.

− Email service configuration

After configuring the email service, administrators can send the conference site

information to specified users in emails if the telephone conference is scheduled

successfully. After adding a single UC account, administrators can send the account

information to the user's mailbox.

This function takes effect after conference and account information is sent to a

configured SMTP server. The SMTP server sends emails to conference participants.

8.1.2.11 LDAP Integration

− Synchronization from Active Directory

The system periodically synchronizes user information into the enterprise address book

from Active Directory. The structures of synchronized departments and accounts remain

unchanged.

− Third-party LDAP authentication

Third-party LDAP authentication is enabled to authenticate user names and passwords

on a third-party LDAP server.

8.1.2.12 Multiple Languages

Simplified Chinese and English are supported.

8.2 esight

The eSpace Element Management System (ESIGHT) can manage devices and terminals on

the UC network, including IP PBX, IAD, IP phone, SBC, EGW, and wireless gateway. The

eSight uses the B/S architecture and is used for deployment, routine maintenance,

troubleshooting, upgrade, and capacity expansion based on web pages to improve network

management performance and efficiency.


Figure 8-1 eSight typical network

8.2.2 NE Connection

Figure 8-2 eSight NE connection

After connecting to the eSight, NEs can be managed by the eSight. The eSight provides the

following NE connection methods:

� Manual creation


Users can use the manual creation function to connect NEs to subnets, applications, and

physical devices.

� Automatic detection

Users can set the IP address and port number segment, and the system automatically

detects devices and connects NEs to them. If the IP PBX is found, users must set the user

name and password for logging in to the IP PBX.

If the firewall is deployed on the user side, the function is available only when the

corresponding port is enabled on the firewall.

� Batch import

When creating large amounts of NEs, users can enter NE information in the device list

file and import the file in the eSight to connect the NEs quickly.

8.2.3 NE Management

The eSight can manage the IP PBX, IAD, IP phone, EGW, SBC. The following table lists

available NEs.

NE Type Model

IAD IAD132E(T), IAD208E(M), IAD101H, IAD102H, IAD104H, and

IAD1224

IP PBX eSpaceU1910, eSpace U1930, and eSpace U1980

SBC SX1000

IP phone � eSpace 6805, eSpace 6810, eSpace 6830, eSpace 6850, and eSpace 6870

� eSpace 7810, eSpace 7820, eSpace 7830, eSpace 7840, eSpace 7850, and

eSpace 7870

EGW eSpace EGW1500E

8.2.3.13 IP PBX Management

The eSight manages the configuration, performance, upgrade, and maintenance of IP PBXs.

� Configuration management

− Batch configuration: The eSight can configure the SIP trunk, active and standby

servers, and call forwarding offline service for eSpace U19xx series IP PBXs in

batches.

− Single configuration: Users can use the command tree to configure an IP PBX. The IP

PBX provides a visual device simulation GUI on the device panel, where users can

query device status and manage hardware devices such as boards.

� Performance management

Users can view the following information in real time:

� E1 resource usage

� Digital Signal Processing (DSP) resource usage

� Board's CPU usage and memory usage

� Bandwidth for sending data

� Bandwidth for receiving data


� Upgrade management

The eSight can upgrade the main processes of U1910, U1930, and U1980 IP PBXs in

batches. Five IP PBXs can be upgraded concurrently. The eSight supports retry and

rollback if an upgrade fails.

� Maintenance management

− Data backup and restore: The eSight can back up, restore, and save IP PBX

configurations. The eSight can back up the configuration file in scheduled periods or

allow users to back up the configuration file manually.

− Signaling tracing: The eSight provides the signaling tracing management function for

the IP PBX to trace and monitor the protocol messages, connection of port signaling

links, and service flows of the IP PBX dynamically in real time. The eSight can trace

the SIP, PRA, R2, and SS7 signaling and user messages.

− Operation log: Users can view the IP PBX operation logs.

− Ping test: Users can run the Ping command to test the connection between IP PBXs

and other devices.

8.2.3.14 IAD Management

The eSight manages IAD configuration, performance, upgrade, and maintenance.


− Single configuration:

� Basic configuration

� Advanced configuration

� Service configuration

� System tool


− Batch configuration:

� Network parameter setting

� Proxy server configuration

� NE management configuration

� Storage configuration

� Performance management

Users can monitor the CPU usage of IADs.


− Automatic upgrade: After this function is enabled, the IAD can detect the upgrade file

on the FTP server. If the upgrade file is not compatible with the current version, the

IAD automatically upgrades.

− Manual upgrade: The complex programmable logical device (CPLD) version (applied

only to the IAD132E(T) device) and NE software can be upgraded manually. The

batch upgrade is supported.

� Maintenance management

− Data backup and restore: The eSight can back up, restore, and save IAD

configurations. The eSight can back up the configuration file in scheduled periods or

allow users to back up the configuration file manually.

− User information backup and restore: The eSight can back up, restore, and save IAD

user information.


− Ping test: Users can run the Ping command to test the connection between IADs and

other devices.

8.2.3.15 IP Phone Management � eSpace 79xx IP phone management

− The eSight manages the IP phone configuration:

� Deploys IP phones automatically

� Manages the configuration file

� Downloads log files

� Configures TR069 common services

− IP phones report the alarm time to the eSight.

− The eSight manages the IP phone upgrade:

� Loads the IP phone software version file

� Manages the software version

� Provides the upgrade wizard

� Monitors the upgrade

� Queries the upgrade history

8.2.4 Topology Management

The eSight displays NEs and links between NEs in the topology view. Users can master the

hierarchical structure and running status of the entire devices in the topology view.

Item Description

NE Core unit in topology management. An NE is used to identify a managed

device. In the topology view, different icons identify different types of

NEs.

Subnet To simplify the network management, the user can separate a network into

several subnets according to a certain principle based on the region or the

device type.

Link A link identifies the physical or logical connections between devices.


Figure 8-3 Topology management

� Viewing the topology

The objects are displayed at layers. Users can view the distribution of all objects (NEs,

subnets, and links) in the topology view. If the number of objects is large, users can view

all objects in the aerial view.

� Creating and deleting virtual NEs

Virtual NEs represent actual NEs in the topology view. Users can create virtual NEs.

� Creating and deleting virtual links

Virtual links represent actual links in the topology view. Users can create and delete

virtual links.

� Displaying the alarm severity dynamically

The topology view displays objects in real time in different colors according to different

alarm status.

� NE management

Users can right-click an NE in the topology view to access the NE management page.

The current NE monitoring information such as the performance monitoring result and

alarm information is displayed on the NE management page.

� Searching for an object

Users can set searching criteria in the topology view to quickly search for an NE.

8.2.5 Alarm Management

Users can monitor, view, analyze, and clear NE alarms to prevent system crash.


Figure 8-4 Alarm management

� Monitoring alarms in real time

The eSight receives alarms generated by the NEs in real time. The esight provides the

alarm panel, alarm sound, and current alarm list for users to monitor alarms in real time.

� Viewing current alarms

The esight allows users to view the current alarms. The alarm records refresh in real

time.

Users can view unclear or unacknowledged alarms in the system and can view alarms

that meet the filter criteria.

� Viewing masked alarms

Users can query and view masked alarms as required.

� Displaying the alarms status

In routine maintenance, users can view and process alarms based on alarm status.

Alarm status can be classified into the following types:

� Unacknowledged and uncleared

� Acknowledged but uncleared

� Unacknowledged but cleared

� Acknowledged and cleared

� Alarm sound

The system plays the corresponding sound to notify a user of an alarm when the EMS

reports an alarm. Users can set different sound types and play durations based on

different alarm severities.

� Alarm panel

Users can view the number of alarms in each alarm severity on the alarm panel.

� Querying historical alarms

Users can query and view acknowledged and cleared historical alarms by different

criteria.


� Viewing alarm details

Alarm details include alarm name, level, device name, acknowledgment status, cause,

and alarm location.

Users can view alarm details and copy the details for locating faults.

� Remote alarm notification

The system can remotely notify users of alarms and events. After the remote notification

service is configured, the maintenance personnel can learn about alarms of the entire

network in real time when they are not in the equipment room. Maintenance personnel

can obtain remote alarm notifications in either of the following ways:

− Set the SMS gateway and number for receiving SMS messages, and receive alarm or

event notifications in SMS messages.

− Set the SMTP server and email address, and obtain alarm or event notifications by

email.

Maintenance personnel can filter alarm notifications by alarm severity and type.

� Alarm display locking

Alarm records refresh in real time. The eSight always displays the latest alarm

information at the top of the alarm browse window.

When viewing an alarm, users can lock the current alarm report to prevent it from

moving down because of newly reported alarms.

� Alarm severity redefinition

Users can redefine alarm severities as required.

Users can redefine alarm severity for an NE or NEs of a specified type.

� Alarm masking

Users can mask unnecessary alarms by alarm name and severity. The masked alarms are

not stored in the alarm database.

Users can set alarm masking conditions by time segment to mask an NE or NEs of a

specified type.

� Alarm masking rules

The system allows users to view, add, modify, and delete alarm masking rules. Users can

set alarm masking rules to mask specified alarms.

� Alarm customization

Users can set an alarm threshold. When a performance counter exceeds the preset

threshold, the eSight automatically generates an alarm and displays it in the alarm

browse window.

� Alarm clearance

The system provides the alarm manual clearance function for users to clear an alarm or

alarms of a specified type. The system can automatically clear an alarm or alarms of a

specified type according to commands from the NMS or preset rules.

� Alarm acknowledgment/unacknowledgment

The system provides the alarm acknowledgment and unacknowledgment functions for

users to manage alarm on the entire network.

� Alarm data exporting

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

� Event query and browse

Users can query and obtain event by different criteria.


� Alarm data maintenance

Users can set the maximum capacity for storing historical alarms, for example, the

eSight can store alarms for six months at most. The eSight automatically deletes and

dumps alarm data saved longer than six months.

Users can decide whether to dump expired data and specify a path to store expired data.

8.2.6 Performance Monitoring

By monitoring performance data, maintenance personnel can understand in real time the

current performance trend of each NE, which provides a basis for network optimization and

maintenance.

� Performance counter customization

Users can select performance counters to be monitored.

Maintenance personnel can set performance counters and durations for collecting

statistics. Based on the settings, the eSight collects statistics on performance data. The

statistics are displayed in real time in the performance monitoring window.

� Real-time performance monitoring

Maintenance personnel can monitor performance counters of NEs in real time to detect

exceptions.

The eSight displays the monitoring results in bar charts or line charts to clearly show the

performance trend. Maintenance personnel can avoid potential risks by taking active

measures before a performance counter reaches its threshold.

Figure 8-5 Monitoring performance in real time

� Monitoring view customization

Users can add, modify, and delete a monitoring view, and can adjust the location of a

monitoring view.

� Performance threshold alarm function


Users can set an alarm threshold for NE performance counters. When the performance

counter of an NE exceeds the threshold, the performance alarm generates.

� Performance monitoring template

Users can add, modify, delete, and customize the performance monitoring template.

� Historical performance data query

Users can query and browse historical performance data by criteria.

� Performance data exporting

Users can export performance data to .csv files.

� Performance data maintenance

Users can set the duration for storing the performance statistics data. When data

overflow occurs, the eSight automatically dumps the data.

8.2.7 Security Management

The eSight controls the eSight user and role rights. The eSight ensures the security of its user

accounts and system running by authentication, authorization, and encryption.

� Role management

The role management provides the role adding, deleting, and changing functions. Users

can set or modify rights for a role when creating or changing a role.

The default role of the super administrator cannot be modified or deleted.

� User management

eSight administrators can add, delete, modify, and query users.

Administrators can set and change the user role, and set and modify a user's access

control policies. Access control policies include login time control and login IP address

control. A login user who does not have a user role can use only functions that do not

require role rights.

User status includes enabled, disabled, and locked.

− Locked: Accounts are locked upon consecutive login failures. The system

automatically unlocks an account when the lock times out. Administrators can unlock

accounts as required.

− Disabled: Accounts that are not used for login within a specified period are disabled.

Only administrators can enable these accounts.

� Security Policy management

� The eSight ensures the security of user account, password, and eSight running.

Security Policy Description

Password policy � Minimum number of digits in a password

� Number of the latest historical passwords that cannot be re-used

� Times of using a character repeatedly in a password

� Special character requirement

� Minimum time interval for changing passwords

� Policy for forcibly changing expired passwords


Security Policy Description

Account policy � Minimum length of a user name

� Policy for locking accounts after consecutive login failure within a

specified period

� Duration for locking accounts

� Policy for disabling accounts automatically

Access control

policy

� Login time control policy

Sets the allowed login date, time, and day.

� System access control policy

Sets the IP address segment to which users can log in.

� Automatic screen lock

Users can enable and disable the automatic screen lock and set the timeout duration.

When stopping operation for a period, users can enable the screen lock function to

ensure the system security. Users must enter the password to unlock the screen.

� User conversation monitoring

To prevent the system from unauthorized users' attacks and monitor online users'

operations, the eSight provides the user conversation monitoring function. This function

monitors the current user's login time and IP address. Administrators can force a user to

log out of the eSight.

� Password changing

The user password can be changed by the user or by the administrator.

The new password must comply with the password setting policies.

8.2.8 Log Management

Logs are stored in the eSight database. Users can manage logs on the eSight web client

interface.

Users can view logs to locate and analyze faults. Users can query logs by preset query criteria

and analyze query results.

Log Type Description

Operation

log

Operation logs record all operation information, such as the user name,

operation, content, time, and result.

Users can query operation logs to obtain the historical system operations.

System log System logs record major events occurred in the system, such as user

logins, system running faults, and network faults. The system log content

includes the module, level, basic information, and operation result. System

logs are used to analyze the system running status and rectify faults.

Security log Security logs record the security operation information, such as login and

logout, password changing, and user creation.

Users can view security logs to obtain information about the system

operation security.


8.2.9 Northbound Interface

Northbound interfaces are external interfaces that the eSight provides for the NMS and other

systems.

The following table lists the functions of northbound interfaces.

Interface Function

SNMP SNMPV1, V2C, and V3 protocols are supported.

Alarm report

and filter in real

time

N/A

Alarm

acknowledgment

and

unacknowledgm

ent

N/A

Alarm

synchronization

If connection exceptions occur between the NMS and

the eSight or when the NMS restarts, the NMS can

deliver the alarm synchronization command to the

eSight. The eSight receives the command and reports

current alarms to the NMS. The NMS checks and

updates the alarms according to the alarm serial

number.

Alarm clearance

report in real

time

When the local maintenance personnel rectify NE

faults or clear alarms, the eSight reports the alarm

clearance information to the NMS. The NMS clears

the alarms according to the alarm clearance serial

number.

Heartbeat

mechanism

The eSight monitors the communication link on this

interface. External systems can query and set the

heartbeat cycle. The eSight sends heartbeat

information to external systems regularly.

8.2.10 Multiple Languages

The eSight supports simplified Chinese and English.

8.3 eSpace LMT

eSpace LMT is the NE management system of the IP PBX, which provides the following

functions:


� Alarm management


� Monitoring management

� Signaling tracing

� Fault rectification

� Patch management


� Log management

eSpace LMT can manage U19xx series IP PBX.

Figure 8-6 eSpace LMT system

8.3.2 System Architecture

eSpace LMT uses the Client/Server architecture and consists of the LMT server and client.

Figure 8-7 shows the LMT system architecture.

Figure 8-7 eSpace LMT system architecture

� LMT server


The LMT server is installed on an independent computer and connects to an IP PBX

using Telnet or Socket. It manages alarms, performances, devices, and logs for the IP

PBX, and displays related information to end users on the LMT client.

� LMT client

The LMT client is installed on an independent computer and communicates with the

LMT server using TCP. It provides the management functions on the graphical user

interface (GUI).

8.3.3 System Network

The relationship among the LMT client, LMT server, and IP PBX is as follows:

� An LMT server and client can be installed on different computers or the same computer.

� An LMT client can be connected to an LMT server installed on another computer. An

LMT server can be connected to an LMT client installed on another server.

� An LMT client can be connected to only one LMT server, while an LMT server can be

connected to a maximum of four LMT clients.

� An LMT server can manage multiple IP PBXs, while an IP PBX can be managed only by

one LMT server.

Figure 8-8 shows the LMT system network.

Figure 8-8 LMT system network

8.3.4 Configuration Management

The LMT manages the IP PBX configuration to allow users to configure IP PBXs quickly.

The LMT supports the following service configuration functions:

� License management

� Offline configuration

� Scenario selection


� Hardware data configuration

� Number allocation management

� Service configuration

� Office route configuration

� Prefix configuration

� Trunk data configuration

� Connection parameter configuration in IMS mode

� Registration group configuration in IMS mode

� User management

� Security management

8.3.5 Maintenance Management

8.3.5.16 Upgrade Management

The LMT provides the following upgrade management functions for the IP PBX:

� Version upgrade

The LMT can upgrade the main processes and configuration data of the IP PBX.

� Version rollback

When upgrade fails, the LMT rolls back the IP PBX to the source version.

� Upgrade status monitoring

The LMT allows users to print logs and display the upgrade progress dynamically.

8.3.5.17 Signaling Tracing

The LMT manages and traces IP PBX signaling to dynamically trace and monitor the protocol

messages, connection process of port signaling links, and service flows on the IP PBX.

The following signaling is supported:

� SIP

� H.248

� PRA

� R2

� SS7

8.3.5.18 Resource Monitoring

The LMT monitors the following resources:

� Boards

� CPU

� E1

� DSP channel resources

� Trunk link

� Terminals


8.3.5.19 Data Backup

The LMT can back up the main processes and patches of the IP PBX.

8.3.5.20 Hot Patch Management

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

8.3.5.21 Maintenance Management

The LMT remotely captures packets to locate and analyze faults.

� The LMT can remotely capture packets only when connected to U19xx gateways.

8.3.6 Fault Management

The LMT allows users to rectify faults help users monitor gateway alarms, view alarms, and

analyze and clear alarms.

The LMT receives and automatically stores alarms in real time and allows users to:

� Brows alarms in real time

� Clear alarms manually

� Acknowledge alarms manually

� Export alarm data

� Report alarms to the I2000 using the UOA

� Process and store multiple alarms in real time

The LMT obtains fault information from the system or black box.

8.3.7 Log Management

The LMT manages logs so that users can view logs to locate and analyze faults. Users can

query logs by preset query criteria and analyze query results.

Logs are classified in to operation logs, run logs, and debug logs.

Operation logs and run logs are stored in .txt files on the LMT server and can be viewed by

users.

The LogServer is embedded in the LMT.

8.3.8 LMT Specifications

Item Specification

Maximum number of connected

devices

16 (including eSpaceU1980, eSpace U1930, and

eSpace U1910)

Maximum number of online

LMT clients

4

Maximum number of historical

alarms that can be saved

100,000


Number of reported alarms that

are processed every second

20 per second

Maximum number of devices

that can be updated concurrently

4 (The devices must be updated concurrently to the

same version.)

Maximum number of device

versions that can be loaded

concurrently

4 (The device versions that are loaded concurrently

must be the same.)

Maximum number of device

licenses that can be loaded

concurrently

4

Maximum number of patches

that can be loaded concurrently

4

Maximum number of remotely

captured packets that can be

saved

255 (When the number reaches 255, the packets must

be deleted. Otherwise, packets cannot be captured.)

Maximum number of logs that

can be stored on the host

The value depends on the available hard disk space of

the host.

Minimum configuration

requirements on the LMT server

Operating systems:

Windows XP

Windows 7

Windows 2003 Server

Windows 2008 Server

64-bit SuSE 11 SP2

CPU: dual core 2.0 GHz or above

Memory: 2 GB or greater

Hard disk: 80 GB or greater

DVD-ROM, USB keyboard and mouse, and standard

extension interfaces

Minimum configuration

requirements on the LMT client

PC

Operating system: Windows XP and Windows 7

CPU: dual core 2.0 GHz or above

Memory: 2 GB or greater

Hard disk: 80 GB or greater

DVD-ROM, USB keyboard and mouse, and standard

extension interfaces

Multiple languages Simplified and traditional Chinese and English


9 Reliability

9.1 IP PBX Reliability

9.1.1 Power Module Backup

eSpace U1980's power module supports hot swap and 2+1 backup.

9.1.2 Main Control Board Hot Standby

eSpace U1980 supports 1+1 hot backup for main control boards. When the active board fails,

the standby board takes over services automatically. The takeover process is free from service

interruption, which increases the mean time between failures (MTBF).

9.1.3 Load Balancing of Resource Boards

eSpace U1980 supports the load sharing of multiple MRSs. When a fault occurs on an MRS,

the media resources can be allocated to other MRSs. In this way, the reliability of media

resources is improved.

9.1.4 Single/Dual/Triple Network Port Mode

The IP PBX supports the single-network-port, dual-network-port, and triple-network-port

work modes.

9.1.4.1 Single-Network-Port Mode � The IP PBX provides service network port backup function. When one service network

port is faulty, the other service network port takes over services. This function ensures

the reliability.

� The IP PBX supports the single-network-port and dual IP address. The service and

management data IP addresses belong to different IP address segments but the service

and management data shares a network port.

9.1.4.2 Dual-Network-Port Mode � The service network port is separated from the management network port.

� Network port 0 is the management network port, and network port 1 is the service

network port.

� eSpace U1980 supports the dual-network-port mode.

9.1.4.3 Triple-Network-Port Mode � Network port 0 is the management network port, network port 1 is the service network

port, and network port 2 supports no service.


� External devices cannot use the same IP address to communicate with multiple network

ports on the IP PBX simultaneously.

� eSpace U1980 supports the triple-network-port mode.

9.1.5 Traffic Control and Overload Protection

The IP PBX supports the advanced traffic control and overload protection technologies. New

calls are restricted automatically when the load exceeds the threshold, to ensure smooth

proceeding of the ongoing calls and prevent system breakdown due to burst traffic.

� When the CPU load exceeds the threshold, intra-office and inter-office calls are

restricted.

� Users can decide whether to restrict calls before the CDR pool is full and set the call

restriction policy according to the attributes of the calling party or the called party.

9.1.6 Connection Event Recording and Attack Detection

The system:

� Records the user connection events.

� Checks for unauthorized connections according to statistics.

� Rejects unauthorized connections.

� Records the time and number of times for enabling and disabling TCP and UDP ports.

� Processes ICMP and ARP packages so that these packages can be pinged.

� Prevents the UDP from flooding attack

� Prevents the TCP connection from flooding attack

� Prevents ARP gateway address spoofing

� Prevents port 23 from flooding attack

9.2 Network Reliability

9.2.1 Service Server in Two-Node Cluster

Huawei UC supports the local service servers in the two-node cluster mode. The Veritas

Cluster Server (VCS) manages the local service server in two-node cluster, monitors the

system and application services, and implements switchover between active and standby

nodes in a quick manner. When faults occur, the VCS:

Stops applications, uninstalls disks, and releases the floating IP address on the active server

Binds the floating IP address to the standby server, mounts disks, and starts applications on

the standby server

A minimum of three network adapters must be configured on each server. One network

adapter is used for loading the floating IP address and providing services. The other two

functions as the heartbeat network adapters of the VCS.


Figure 9-1 Service server in two-node cluster

The active and standby servers run properly. The active server provides services while the

standby server is in waiting state. When resource errors occur on the active server, for

example, a service process is down, the active server releases the service IP address. The

service IP address is bound to the standby server. The standby server automatically takes over

services from the active server.

When the active server restarts or is powered off, the standby server automatically binds to

the floating service IP address and takes over services from the active server.

� During the switchover between the active and standby servers, services on the eServer,

BMU, and OMS are interrupted.

� Box-type eSpace UC 10000 supports the BMU, database, and eServer cold two-node

cluster.

9.2.2 Two-Node Clusterand Local Regeneration

Huawei UC solution supports the two-node cluster and local regeneration functions. Data is

synchronized between the active and standby devices and between devices on the central node and

local gateway in real time. When the active device fails, the standby device takes over services

without interrupting services to ensure smooth system operation. When devices on the central nodes

fail, the local gateways control and route local calls to improve system reliability.

� eSpace U1980 supports the two-node clusterfunction only when the SMCU board is

configured.

� The Console server, CDRServer, and BMU support the IP PBXs in the two-node cluster

mode.

� When switchover between active and standby devices fails, a user must log in to the

SoftConsole again to use the device.


10 Openness and Integration

10.1 Integration with Outlook

After being integrated with the Outlook, Huawei UC solution can:

� Compatibly with Microsoft Exchange 2010, IMAP4, Outlook 2003

� Make a call to a contact using the Outlook address book.

� Synchronize the user status that is set in the schedule reminder on the Outlook with the

UC platform.

� Create a scheduled conference in the schedule reminder on the Outlook.

� Recognize phone numbers in emails and enable users to select these phone numbers to

make calls.

Specific functions are as follows:

� Searching for Outlook contacts by email address or phone number, viewing contact

details, and adding contacts on the UC client.

� Distinguishing common contacts, friends, or Outlook contacts by avatar on the search

result page.

� Transferring Outlook contacts into common contacts.

� Querying information about contacts in the Outlook directory on the terminal that has

Outlook add-ins installed.Right-clicking a contact to view the contact ID that matches

the contacts' email address in the Outlook address book.

� Right-clicking a contact to view the IM menu after a contact ID is displayed.

� Right-clicking a contact to combine the phone number obtained on the terminal and the

phone number of the Outlook contact. The level-2 menus are for calls and SMS

messages.

� Right-clicking a contact to use the UC terminal to send IMs, SMS messages, or calls.

10.2 Synchronization on the Active Directory

The UC system can integrate with the active directory (AD) and synchronize corporate

directory data from the AD domain to the UC platform in a scheduled time or allow users to

synchronize the data manually. After synchronization, all clients manage the corporate

directory on the UC server. Full synchronization and incremental synchronization modes are

supported. The full synchronization mode is used in the first initialization. The follow-up


synchronizations are incremental synchronizations. Administrators can select the full

synchronization mode as required.

Figure 10-1 Synchronization in the AD domain

The enterprise administrator uses the AD corporate directory to maintain the current enterprise's

corporate directory.

After deploying the UC platform on the enterprise side, connect the regular synchronization

module to the current enterprise's corporate directory. Synchronize the corporate directory in

a specified time in the incremental synchronization mode.

Enterprise members log in to the PC clients and view the corporate directory. The corporate

directory is synchronized with the current enterprise's corporate directory.

10.3 Connecting to Huawei Telepresence

Figure 10-2 Connecting to telepresence MCU

U19xx gateway is connected to the telepresence conference system MCU through the SIP

trunk and supports the audio and video conferences. Users can log in to eSpace Desktops to


join the telepresence video conferences. Local and mixed conference videos can be displayed

on the eSpace Desktop.

Figure 10-3 Displaying multiple eSpace Desktop videos in the telepresence conference window

Figure 10-4 Displaying the mixed videos and local video in the video conference window on the

eSpace Desktop

Methods for joining a telepresence conference are as follows:

� Log in to the eSpace Desktop and dial the telepresence video conference access code to

join the conference.

� Initiate a call to an eSpace Desktop in a telepresence conference.

The restrictions are as follows:

� The telepresence conference system MCU must support the SIP protocol.

� The data conference is not supported.


The following table describes audio and video encoding protocols.

Type Protocol

Audio encoding G.711 (A-Law/µ-Law)

G729

iLBC

Video encoding H.263

10.4 Integration with the OCS

Figure 10-5 OCS integration solution network

In the OCS integration solution, Huawei IP PBX and Microsoft OCS are integrated and

communicate with each other through TCP and SIP trunks. Huawei IP PBX registers and

manages IADs and IP phones, and functions as a voice gateway to connect to the PSTN and

Microsoft OCS. The mediation server of Microsoft OCS converts signaling and media

streams to enable the communication between Huawei IP PBX and Microsoft OCS. Users

under the IP PBX can use functions of Microsoft OCS. Microsoft OCS users are connected to

the PSTN through Huawei IP PBX. The OCS integration solution provides the following

functions:

� Dual Forking

Each user has a fixed phone and a Microsoft Office Communicator (MOC) under the IP

PBX at the same time. When receiving an incoming call, the fixed phone and MOC ring

simultaneously. The user can select a terminal to answer the call.

� Binding a phone number to multiple terminals


A number can be bound to a fixed phone, MOC, and mobile phone. The three terminals

ring sequentially or simultaneously.

� Audio and video calls and IM

Convenient and flexible voice call, video call, and IM functions are provided. The three

functions can be integrated.

� Voice and video conferences

PSTN phones, mobile phones, fixed phones, and MOCs can be used to join voice

conference simultaneously. MOCs and video phones can be used to join video

conferences.

� Status presentation

Users can view the friend status (including talking, idle, away, and offline) and location

on the MOC at any time.

� Call control

Users can log in to the MOC to dial for the fixed phone, forward, transfer, hold, or

resume a call.

� Collaboration

The audio and video collaboration functions, including application, desktop, web page,

and file sharing, questionnaire, e-whiteborad, conference recording, and conference

control are provided.

� Mobility

With the OCS integration solution, users can use the IM, conferencing, and web

collaboration functions on the MOC that is connected to the Internet properly.

� Unified Messaging

Messages are sent to users' mail boxes by the exchange server. Users can log in to the

Outlook client or use the Outlook Web Access to play voice messages. Users also can

use common phones to listen to the voice messages.

eSpace UC Feature Description Ver 1 - Huawei - Building … Call Barring Policies ..... 29 2.4...

Documents

Transcript of eSpace UC Feature Description Ver 1 - Huawei - Building … Call Barring Policies ..... 29 2.4...