| User Provisioning | |||
|
| GO | |
|
Users can be completely defined using the Lucent CM Explorer. There is no need to use the Lucent FS 3000 interfaces.
User - Call Server parameters:
|
Parameter |
Description |
|
Phone Number |
The telephone number for the user. |
|
Extension |
The phone extension number. |
|
Feature Package |
The feature package for the user. This can be the user feature package the group uses (Use Group Policy), or another available user feature package. |
|
Alias |
The alias for the user. The domain is shown behind the Alias box. For example @enterprise.com The alias will be the user identifier that is added to the Lucent FS 3000 call server. |
|
User Password |
The password for the user login to the Lucent FS 3000 call server. This will assign the password for the user. |
|
Verify Password | |
|
Device Name |
The device name of the phone. The device name must match the device name on the FS 3000 call server. |
|
Line Port |
The line port (or directory number) that is associated with the hard phone. Typically, the identifier is the user's phone number or alias and, if this user's phone number appears on multiple devices, a suffix. The line port must match the line port on the Lucent FS 3000 call server. |
|
Phone Password |
The password for the phone to register with the Lucent FS 3000 call server. |
|
Verify Password |
User - Messaging parameters:
|
Parameter |
Description |
|
Messaging User ID |
IMAP4 authentication user identifier for the messaging service. |
|
Email ID |
The E-mail identifier that is used to identify the user at the message server. |
|
Password |
The password for the user to access the messaging system. |
|
Verify Password |
Initial provisioning of a system must be done through the respective Lucent CM and Lucent FS 3000 interfaces.
Partition and service provider provisioning must be done through both the Lucent CM and Lucent FS 3000 interfaces
Hardphone or softphone device provisioning is done through the Lucent FS 3000 interface.
User provisioning is completely automated by the Lucent CM.
|
|
GO | |
|
| © Lucent Technologies | |||