dition Date Author Modifications / Comments / Details

1 2017-06-29 Serge Le Louet Creation

2 2017-10-20 Serge Le Louet Modification : 8770 wbm

3 2017-11-03 Serge Le Louet Modification : Msad

4 2017-12-01 GilbertdeCauwer Demo script

5 2018-01-02 Serge Le Louet Modification: demo Booking

6 2018-06-29 Hervé Toulan Add selfcare demo

7 2019-03-13 Eric Pinault Add VPN connection

8 2019-05-20 Philippe Hainaut Local admin profiles

9 2019-12-10 Eric Pinault Update links

Management

Demo Guide Ed9

M a n a g e m e n t D E M O G U I D E

Sommaire

1 I n t r o d u c t i o n 3

2 A r c h i t e c t u r e 3

3 C o n ne c t i o n 4

4 O x e W b m 4

4.1 Introduction ...................................................................................... 4

4.2 High Level Architecture Diagram ............................................................ 5

4.3 Configuration .................................................................................... 5

4.4 Demo Script ...................................................................................... 6

5 O m n iv i s t a 8 7 7 0 8

5.1 Introduction ...................................................................................... 8

5.2 Access: OmniVista client ....................................................................... 8

5.3 Demo Script ...................................................................................... 8

6 O m n i V i s t a W e bC l i e n t 1 9

6.1 Introduction ..................................................................................... 19

6.2 Login and access ............................................................................... 20

7 M s a d 2 3

7.1 Introduction ..................................................................................... 23

7.2 High Level Architecture Diagram ........................................................... 23

7.3 Configuration ................................................................................... 23

7.4 Demo Script ..................................................................................... 25

8 S e l f c a re 3 1

8.1 Introduction ..................................................................................... 31

8.2 High Level Architecture Diagram ........................................................... 32

8.3 Login and access ............................................................................... 33

8.4 Demo script ..................................................................................... 34

9 P h o n e s co nn e c t i o n 3 9

9.1 RDP and IP Desktop Softphone .............................................................. 39

9.2 VPN phones capable ........................................................................... 39

9.3 Shrew VPN from a Windows PC and IP Desktop Softphone ............................. 40

1 Introduction

The aim of this document is to describe all aspects of the management. It contains the

architecture of the demo, and explains how to configure each component of the Management

demo. This document also contains demo scripts, which will help the demonstrator carry out the

various demos cases.

This demo guide includes 3 demos:

• OxeWbm

• Omnivista 8770

• Msad

• Selfcare

Before a demo please book and check system availability on:

http://edemo.al-mydemo.com/?page_id=2677

2 Architecture

3 Connection

Details for Rdp connection:

4 OxeWbm

4.1 Introduction

Key Message: This demo supports the value proposition message about

The OmniPCX Enterprise Web Based Management (OXE WBM) application is a web based interface that is part of the OmniPCX Enterprise solution. Available from R12.0, the OXE WBM enables to configure the OmniPCX Enterprise settings in a quick and user-friendly way through one single web interface. The OXE WBM is directly accessible by a dedicated URL address reachable from standard industry internet browsers. This web client does not require any plug-in to run on a web browser. It runs in a secure way (https connection to or from the OmniPCX Enterprise).

The authentication of users opening an OXE WBM session can be performed remotely by a RADIUS server. In this configuration, authentication is not handled by the OmniPCX Enterprise, which sends authentication requests to the RADIUS server. Document Reference: OXE System: Web Based Management Administrator Manual 8AL91034ENAA Ed. 01

4.2 High Level Architecture Diagram

4.3 Configuration

From the desktop select: oxewbm

Use login: mtcl And password: Aledemo2017 ! You can choose the interface language.

4.4 Demo Script

4.4.1 Introduce interface

(1) Information and command available. Available support according to their position in the tree (2).

(2) About tree positioning.

(3) Model base on OXE

(4) Command available

(5) Information area and filtering

4.4.2 Find a user

(1) Choose USERS object

(2) Select options

(3) Apply or cancel

(4) The result is display on the tree.

Information: In the filters and sort menu if you choose set function equals profile you can display Meta-Profile using in the USER application in OV8770

En

Fr

4.4.3 Create a user

We are creating Mr Utilisateur05 with extension 34025 and poste type 8068S

(1) Put in the USER object (2) Press on Create button (3) you must seize the parameters

a. Number (34025) b. Name c. First Name d. Set type (8068S)

(4) The other tabs give other parameters of management

(5) Apply. User Utilisateur05 is displayed in USER tree (1).

4.4.4 IPDSP parameters

To deploying an IPDSP user you must doing validate a “IP-SoftPhone Emulation” parameter.

1) In USER tree

• Choose the user

• set extension

• TSC IP user

• Set type 2) Check if “IP-SoftPhone Emulation”

parameter is YES

5 Omnivista 8770

5.1 Introduction

The OmniVista 8770 Network Management System suite is a comprehensive set of applications

designed to help telecom managers and administrators in their day-to-day tasks. It can aid

them in making strategic choices for their converged networks, by combining reliability, assured

availability, performance information, access security, configuration management and

telecommunication cost tracking. …. Message: This demo supports the value proposition

message about

5.2 Access: OmniVista client

From the desktop select: OmniVista8770 Client

Use login: Ov8770Demo or: BasicOV8770 Password: Aledemo2017!

5.3 Demo Script

5.3.1 Introduce the level of services between both administrators

We have 2 administrator’s logins, Ov8770 and BasicOV8770. The first have all right and the

second have restricted rights on OXE4 server.

a) Use the basic login and show the differences icons

b) Use the Ov8770 login and show them its different properties.

With the basic login,

1) the OV8770 applications (1) are limited at USER and configuration.

2) In configuration app /connect to OXE4

3) Model object (2) of OXE are limited at

• Users

• Groups

• Speed Dialing

With the complete login administration login: Ov8770Demo And password: Aledemo2017!

5.3.2 Find a user with search area on USER application.

Start USER application

Area definition (1) Ov8770 applications available (2) Tree structure. (more

information in chapter 2 in am_adminmanual

(3) Search area (4) Properties area (2).

In the field WHERE on search area Dans la zone de recherche dans le champ : Where = Last name Contains = Utili

Apply with (No case sensitive)

The result is display on area properties (2).

The icon display the result in the tree structure come back to script

5.3.3 Create a user with AD (Activ Dyretory) connector.

On the desktop

In the folder: Forum2010/MSAD

Create a new user (3)

Create a new object in MSAD

- First Name - Name - Mail address - Next - Enter a password (1234) - Next - Finish

(1) Click right on the new user

(2) Chose: Alcatel-Lucent Unified Management

(3) Enter one mail address.

(4) Chose a Meta-profil

(5) Fields available but completed automatically by the profile.

(6) Create

OXE user added successfully

You can delete or modify (be careful not all field)

Come back to chap 4.2.2 to show that user in the USER application.

The new user is created on MSAD branch.

This is administrator choice.

5.3.4 Synchronisation both OV8770 and Active Directory (AD) base.

On AD application The field “telephone” on properties of user is empty

In Administration application on OV8770 choose MSAD management and click right to choose complete synchronization. Select: simple job, apply, status, refresh in the next page. When you have: job completed successfully you can close the window

Come back in AD application and show the properties of this user.

5.3.5 Create a new user with meta profile on USER application interface

A) On the USER application and user tab, select OXE4 server

Be careful if you select the root of tree the new user will display on root (the display is

totally decorrelated on reality)

B) Click right « Create user »

C) Complete field at minimum the fields below.

- (1) user type = OXE - Salutation - Last name - First name - @mail (use by OT application) - (2) Meta profile: choose 8078S_OT Have a right on OpenTouch (you will can associate a smartphone) - (3) apply

D) After couple seconds mr USER is available

5.3.6 Append a secondary set (DECT or SmartPhone)

You can add a secondary set at on user with USER application.

The secondary set can be:

a) A user OXE if is DECT user

b) A User SIP if is user OT (OTC-PC or OTC-mobile)

DECT SET: In the user list click right and select: add a secondary set. You can choose an existing set if there is already exist or add a new set.

- case1: existing - Case2: add new

Cas1: if the DECT already exist Select in the windows the right user

Cas2: if the set does not exist Complete the OXE directory number

When you have finished the secondary set is displayed below the main user.

5.3.7 Add OpenTouch right (OTC mobile)

You can add OpenTouch right at the OXE user. The right can be voicemail or OTC mobile for

smartphone (include REX)

To open the right, you must enter the email address (2) and valid the applications OT (1)

Chose the OT instance

1) When you chose the profile (oxeUser) quite a few fields are completed automatically

2) All this fields must be

fulfilled manually.

3) This fields are mandatory to create REX and mobile parameters

Rules: xxx= 3 digits latest on directory number (34020 for this case) OT device directory number

1034 xxx or 1034020 Remote extension number

1036 xxx or 1036020 System speed dial number

AdirectoryNumber or A34020

1) Don’t forget the login (indentifiant)

2) And password user, SIP and TUI

At the end M. Utilisateur have 2 secondary’s sets. One DECT and one OTC mobile

5.3.8 Display the profile OT

In the application Select OT-OXE Click right: configure

(1) Select tab PROFIL

(2) Chose « oxeUser »

Associated applications (2) are showing in the licences tab (1)

5.3.9 Displaying and modification user’s keys

On CONFIGURATION application choose OXE4 server in tree and select a submenu CONFIGURE (1) with right click

• Choose on USER in the tree and right click to display a graphical view. Be careful choice a user with IPTouch type set

• You can be writing directly in the graphic view

6 OmniVista WebClient

6.1 Introduction

The OmniVista 8770 Web Based Management (OmniVista 8770 WBM) client is a web based

interface that is part of the OmniVista 8770 solution. This web client enables to provision users

and their devices in a quick and user-friendly way through one single web interface.

The OmniVista 8770 WBM is a lightweight client which does not require any plug-in and license

to run on a web browser. It runs in a secure way via an HTTPS connection (to or from the

OmniVista 8770 server).

The OmniVista 8770 WBM client is accessible directly by a dedicated URL address reachable from

standard industry internet browsers such as Google Chrome or Mozilla Firefox. The OmniVista

8770 WBM home page opens immediately after login.

6.2 Login and access

You can access to the web management OmniVista8770 choose OmniVista8770 URL.

1) Choose OmniVista URL

2) Choose option Directory or Management

3) Choose the usual language

6.2.1 Directory Consultation

Directory option

This option use one licence OV8770

1) Search bar 2) Display tree 3) Display area 4) Authenticatio

n and associate set (for click to call)

6.2.2 Mangement

Management option Login : Ov8770Demo Password : ALEdemo2017! You can change language

You can create a user with OT option

7 Msad

7.1 Introduction

Key Message: This demo supports the value proposition message about

The MSAD (Microsoft Active Directory) plug-in is used when the OmniVista 8770 server operates with an Active Directory server. This plug-in is installed locally on the server hosting the Active Directory. The MSAD plug-in enables to launch an OmniVista 8770 user management web tool from the Active Directory. This web tool is connected via HTTPS to the OmniVista 8770 server. The OmniVista 8770 user management web tool allows the creation, update or deletion of the OXE and OT users from the list of users declared in the Active Directory. User information is sent to the OmniVista 8770 server in the body part of HTTP requests.

7.2 High Level Architecture Diagram

7.3 Configuration

Msad Configuration :

8770 Meta Profile Configuration:

Each metaprofile is linked to:

- Oxe free range number

- Oxe Profile

- - Key Profile

- - Cost Center

- -

Range Number

Phone Type

Oxe Profile Key Profile Cost Center

ADM ADM : 34O40-34059

8068 ADM8068 Company 2 401: ADM

DSI DSI: 34020-34039

8068 DSI8068 Company 3 402: DSI

DECT DECT:34060-34079

GAP+ DECT 403: DECT

IPdsp Company: 34000-34019

8068 IPDSP Company 404: Company

7.4 Demo Script

In Organisation Unit “Msad”

Choose :

- oxe metaprofile

-

Click on Create

User is created in 8770

If User is already declared in 8770 users Management:

You can choose a metaprofile and press “Modify”

If you press “Delete”

User is deleted in Users Management and In Oxe

Switch “ip softphone emulation “ to “yes”

8 Selfcare

8.1 Introduction

Key Message:

Offer your company a simplified operation management

with the Alcatel-Lucent Enterprise SELFCARE

Delegation & Autonomy

• Daily operation made easier and faster User friendly interface, no need for extended training. Reduce your cost and improve employee autonomy and satisfaction.

• Delegate to local admin Local admin handle their own or all sites eventually according to local admin profiles Separated view

• End User Easily access to basic personal management Save time, money and frustration

8.2 High Level Architecture Diagram

8.3 Login and access

You can access to the web management with URL

https://selfcare.al-mydemo.com

Access restricted. EBC login/password required.

It is recommended to use Chrome for Demo, even if Firefox and IE are also target browsers.

Language supported are EN/FR and depend on the language of the browser.

• End User profile (LDAP account):

Login: paul.smith@ebs.net

Password: @lcatel01

• Local Administrator profile (LDAP account):

Login: clara.sheller@ebs.net

Password: @lcatel01

• Super Administrator profile (LDAP account):

Login: selfcare-admin-01@ebs.net

Password: @lcatel01

• Super Administrator profile (credentials stored locally)

In case of Active Directory is down.

Login: admin

Password: not communicated yet

8.4 Demo script

Scenario for End User

This section is for End User, in order to handle its own device.

1. login : paul.smith@ebs.net

➢ Login and password are stored in LDAP server and not in selfcare.

➢ Mandatory Fields in LDAP:

o userPrincipalName (e-mail)

o Password

o telephoneNumber (enables the association with OXE user)

2. Show available feature on first tab:

Display language, secret code, padlock, forward, eventually OT passwords

3. Show available feature on second tab:

Programmable keys (supervision, multiline, programmed)

Note that OXE prefixes can be used in programmed key and offer more possibilities

➢ Example 1: prefix 480 to set device out of service

➢ Example 2: Prefix 406 redial last number

➢ Example 3 : Prefix 45 group call pickup

➢ …

4. Logout

Scenario for Local Administrator

This section is for Local Administrator, responsible to administrate a predefined perimeter of

users. A minimum knowledge of telephony terms can help.

1. login : clara.sheller@ebs.net

➢ Login and password are stored in LDAP server and not in selfcare.

➢ Mandatory Fields in LDAP:

o userPrincipalName (e-mail)

o Password

2. Show Home page, with reminders (who is connected, role, version number, latest

features)

3. Show “Manage Users” menu

This is the main menu to access user edition

3.1 Search user

Show available sites and explain current administrator can manage the 2 available sites

and view only users declared in these sites. (site declaration will be detailed in Super

Admin section)

Perform a research on all sites.

Filter users by entering “sm” for Smith in search field.

Click on back to search to access Paul Smith directly

Enter Short number “74014” OR last name “Smith” …

3.2 Edit User

Browse all tabs for Paul Smith

▪ General

Comment: device type can be updated according to OXE and local admin profile

restrictions

▪ Rights

Comment: value displayed for all the fields are defined in OXE according to site

or local admin profile restrictions

▪ Features

Comment: DSS = Desk Sharing

▪ IP Parameter

Comment: only available for IP sets

▪ Programmable Keys

Comment: strictly the same as End User profile

▪ Open Touch and voice mail tabs

3.3 Create User

From menu Manage Users/Create user

Explain creation is available and details field.

Introduce User Profile (managed by Super Admin for all administrators)

Optional:

You can create user on Site ALE Colombes (DN computed should be 74001)

Use profile PROFILE_1_8068S_WITHOUT_VM

Back to search, show user has been created.

Use check box at the right of the user and click on “Delete Selected” to delete user for

Next Demo !

Introduce user profiles, different rights for local profiles.

3.4 User Groups

From menu Manage Users/Users Groups

Show that Local admin can manage Hunting Groups in his perimeter.

5. Logout

Scenario for SuperAdministrator

This section is for Super Administrator = advanced user, responsible to administrate the global

solution. Super administrators can do and undo everything, including breaking configuration.

A good knowledge of telephony terms and basics for LDAP are mandatory.

1. login : selfcare-admin-01@ebs.net

➢ Login and password are stored in LDAP server and not in selfcare.

➢ Mandatory Fields in LDAP:

o userPrincipalName (e-mail)

o Password

2. Show Home page, with reminders (who is connected, role, version number, latest

features)

3. Show “Manage Users” menu

One new entry “User Profiles” has been added to Local Administrator menu.

Super Administrator can create profile used as templates for user creation only and visible for all

administrators.

4. Browse “Administration” menu zoom on local admin profiles

Comment:

Selfcare configuration should not be often updated as soon as system is in production, but this

configuration is under Super Admin responsibility.

Do not change Selfcare configuration or ensure modifications are reverted at the end of the demo.

4.1 Telephony

➢ Show OXE(s) declaration

Comment: Selfcare maintains a local database with only required info from OXE, this is to avoid

requesting OXE when not necessary. Selfcare is notified in case of configuration events on OXE.

➢ Show OT(s) declaration

4.2 Authentication

➢ Declare LDAP(s)

➢ Show LDAP users tab and explain Super Administrator can grant users to different roles.

(super admin, local admin => specify affected sites for Clara Sheller, end user)

By default, all users synchronized from LDAP have USER role and can connect to the Selfcare.

From Authentication menu, explain options for all profiles.

since version Selfcare 1.5.1:

LocalAdmin profiles can be duplicated, it is usefull to manage several levels of administration.

LocalAdmin profiles can be declared without any restriction on site. It means that there is no

need to update perimeter of user in case of new site or company are created.

Both Active Directory and OmniVista 8770 are supported as LDAP server.

4.3 Ecosystem

Explain how ecosystem works and define 3 objects : Group / Enterprise (or zone) / company

Ecosystem is local to Selfcare (independent from 8770 )

➢ For one enterprise: one LDAP, one or more OXEs

➢ For one site: one OXE

In object site, show how to restrict a site with one or more range of directory numbers, and

entities.

The restrictions are combined like AND operator:

Range (If defined) AND entities (if defined) AND cost center (if defined)

4.4 History

Show that all operations done during the demo are stored and visible for super admin only.

Use “Search…” filled and filter timestamp to only show operations of the day.

Example:

Enter “03/07/2018 14:” to display all operations made the 3rd of july 2018, from 14:00

Open also combo box to show filter on operation (CREATE/DELETE,…) and return code (ERROR,

SUCCESS..)

History purge in next version.

9 Phones connection

9.1 RDP and IP Desktop Softphone

On RDP session provided when demo slot is approved (See §3), an IPDSP can be used : OXE IP is

192.168.111.104. Prefix to set a device out of service is 400.

9.2 VPN phones capable

With VPN capable phones (8028s,8058,8068s and 8078s):

• Gateway: 195.128.146.2

• Login: first login provided when demo is approved (login without “\ebs”), see §3

• Password: first password provided when demo is approved (login without “\ebs”), see §3

• Pre-shared key: @lcatel01

9.3 Shrew VPN from a Windows PC and IP Desktop Softphone

• From a windows PC, install Shrew VPN client (Available on Shrew website and eDemo website)

• Download eDemo 80x8 configuration file

• Import eDemo 80x8 configuration file into Shrew

Select new VPN and enter credentials:

o Login: first login provided (login without “\ebs”), see §3

o Password: first password provided (login without “\ebs”), see §3

You can then run an IPDSP : OXE IP is 192.168.111.104. Prefix to set a device out of service is 400.

End of document