Alcatel Unleashed

My company intends to supply a remote maintenance service to some customers, with a NOC profile.

As far as I know, I can not set in OmniVista 4760 a scenario where:

There are several systems (from different clients) registered at same OmniVista
Creation of a user
This user could access ony some of the systems (it should be configured), in all application. For example, I could give an client access to CUSTOMER A equipments, who could access only his own system (he could not see or change anything in CUSTOMER B, CUSTOMER C and so on).

In this way, we could optimize the usage of servers and licences.

Someone talked about OMNIVISTA 4760 MCS, but by sales documentation I could not see this scenario.

Is it really possible ? Or there is some way to configure it on normal OMNIVISTA ?

Regards,

If your customers have seperate PBX each, then you could seperate the access via MGR->Security and Access Control->Station Access Control you can set the PC name/s (in capital letters) that are alowed to connect to the PBX.

If your customers are sharing a PBX then you can only sperate configuration rights for the extensions. To do this you need to set up domains and the domain rights for each user via MGR->Security and Access Control->User Access Control.

Accounting rights can be set by using Accounting domains in the Omnivista 4760.

However the Omnivista 4760 is not intended for multicompany use.

You can do it actually, I am setting it up for a similar configuration.

You use 'configuration by domain' to segregate the users & Security & access control to govern the rights.

I am having some issues with the domain settings at the moment though if the user is not in domain 0 in the user access control list.

Both features are in the OXe docs

Let me know how you go

4760 MCS edition is mainly for report appli (there is a dedicated license 476 RSC fo that)
it add a new capbility report per custommer list (each list of rsc custommer have their onw pcx)
it also add some predefined report that use the rsc custommer capbility

in additon the directory creation can be also linked to such rsc custommer
consider rsc custommer has a specific department
when it exist automatic creation of directory entry dont look if same user/person exist in other rsc custommer directory branch

anyway 4760 is not fully multitenant
you have as explained the segregation of administrator pcx per domain (group of obecjt) inside a pcx
you can deny for some admin the access to some pcx by not puting them in the access cotnrol list

anyway any admin will see all pcx in configuration tree even the one they cannot manage
it is at connection time they will be rejected