Find answers to your technical questions and learn how to use our products
Search suggestions:
Find answers to your technical questions and learn how to use our products
Search suggestions:
Name |
Description |
|---|---|
Tenant |
The name of the tenant that you select. |
Level 1 |
The name of the level 1 hierarchy of the tenant organization. For example, Site. The tenant administrator provides the hierarchy on the Tenant Management page. |
Level 2 |
The name of the level 2 hierarchy of the tenant organization. For example, Department. |
Level 3 |
The name of the level 3 hierarchy of the tenant organization. For example, Team. |
Name |
Description |
|---|---|
User Provisioning Rule |
The name of the user provisioning rule. You can provide only one user provisioning rule. |
When you use the user provisioning rule to create a user, the system populates the values of user attributes from the user provisioning rule.
Name |
Description |
|---|---|
Last Name |
The last name of the user. For example, Miller. |
Last Name (Latin Translation) |
The user-preferred last name that the system must display on the endpoints. For example, Miller. Typically, the name is in the written or spoken language of the user. Last Name (Latin Translation) can be up to 256 characters.
Note:
When you create a user, if the Last Name (Latin Translation) and First Name (Latin Translation) fields are:
|
First Name |
The first name of the user. For example, John. |
First Name (Latin Translation) |
The user-preferred first name that the system must display on the endpoints. For example, John. Typically, the name is in the written or spoken language of the user. First Name (Latin Translation) can be up to 256 characters. |
Middle Name |
The middle name of the user, if any. |
Description |
A brief description of the user. |
Status |
The login status of the user. |
Update Time |
The time when the user details were last modified. |
Login Name |
The unique system login name given to the user. The login name takes the form of username@domain. You use the login name to create the user's primary handle. The login name is not case-sensitive. For example, if you enter JMILLER@AVAYA.COM, the system converts the login name to lowercase, that is, jmiller@avaya.com. However, on the login page, you can enter the login name in uppercase or lowercase. You cannot edit the Login Name field for users with the login name admin. |
Email Address |
The email address of the user. |
Authentication Type |
Authentication type defines how the system performs user authentication. The options are:
|
Source |
The entity that created this user record. The options are IP Address/Port, or a name representing an enterprise LDAP, or Avaya. |
Localized Display Name |
The localized display name of a user. Usually, the name is the localized full name. |
Endpoint Display Name |
The full text name of the user represented in ASCII. The field supports display names that cannot handle localized text, for example, some endpoints. |
Title |
The personal title for address a user. Usually, the title is a social title and not the work title. |
Language Preference |
The preferred written or spoken language of the user. |
Time Zone |
The preferred time zone of the user. |
Employee ID |
The employee number for the user. |
Department |
The department to which the user belongs. |
Company |
The organization where the user works. |
Name |
Description |
|---|---|
Name |
The unique label that identifies the address. |
Address Type |
The type of the address. Types of addresses are:
|
Street |
The name of the street. |
City |
The name of the city or town. |
Postal Code |
The postal code used by postal services to route mail to a destination. In United States, this is Zip code. |
Province |
The full name of the province. |
Country |
The name of the country. |
Name |
Description |
|---|---|
Language |
The localized languages for displaying the user name. |
Display Name |
The user name in the localized language you choose. |
Button |
Description |
|---|---|
New |
Allows you to add a new localized name for the user. |
Edit |
Allows you to edit the localized name for the user. |
Delete |
Deletes the localized names you select for the user. |
Add |
Adds or edits the localized name for the user. |
Cancel |
Cancels your add or edit of the localized name. |
Use this section to create, modify, and delete a communication profile of the user. Each communication profile can contain one or more communication addresses for a user.
Name |
Description |
|---|---|
Communication Profile Password |
The communication profile password. The field is available only if you enable the communication profile. The password policy is configured on the Users > User Management > Communication Profile Password Policy page. When you provide the communication password value during bulk edit of users, the system overwrites any existing communication profile passwords of the user. For information about password policy, see |
Generate |
The option to automatically generate the communication profile password. System Manager sends the generated password to the user if you:
By default, the Generate link is available for creating a new user account. The Edit link is available for modifying user accounts. When you click the Edit link, the system displays Confirm Password along with the Generate and Cancel links. |
Name |
The name of the communication profile that you must select . |
Button |
Description |
|---|---|
New |
Creates a new communication profile for the user. |
Delete |
Deletes the selected communication profile. |
Done |
Saves the communication profile information that you updated or added for a profile. |
Cancel |
Cancels the operation of adding a communication profile. |
The system enables the following fields when you click New in the Communication Profile section.
Name |
Description |
|---|---|
Type |
The type of the handle. |
Handle |
The unique communication address for the user. |
Domain |
The name of the domain with which the handle is registered. |
The system displays the following fields only if a communication profile of the user exists for the product:
Name |
Description |
|---|---|
Policy |
When you enable the Enable Policy Based Assignment of Session Managers field on the Elements > Session Manager > Global Settings page, the system displays the Policy field to select the required policy for the Session Manager communication profile. For more information, see Administering Avaya Aura® Session Manager. Based on the policy selection, the system displays the relevant fields. The options are:
Note:
If the Enable Policy Based Assignment of Session Managers field on the Elements > Session Manager > Global Settings page is not enabled, the system displays the Primary Session Manager and Secondary Session Manager fields similar to the Release 8.1.x and earlier system. |
Primary Session Manager |
The instance that you want to use as the home server for the currently displayed communication profile. As a home server, the selected primary Session Manager instance is used as the default access point for connecting devices associated with the communication profile to the Avaya Aura® network. You must select the primary Session Manager server. |
Secondary Session Manager |
The Session Manager instance that you select as the secondary Session Manager. It provides continued service to SIP devices associated with this communication profile when the primary Session Manager server becomes unavailable. This is an optional field. All the four Session Manager values must be unique. For example, if you select the same Session Manager server instance in the Secondary Session Manager field as the Primary Session Manager field, the system displays the following error message: The Secondary Session Manager cannot be the same as the Primary Session Manager. |
Third Session Manager |
The Session Manager instance that you select as the third Session Manager. It provides continued service to SIP devices associated with this communication profile when the primary or the secondary Session Manager server becomes unavailable. This is an optional field. You must select the value of the Session Manager servers as per the order of display. For example, if you select the third Session Manager value before the secondary Session Manager, the system displays the following error message: Selection of Session Managers should be as per their order of display. Select Secondary Session Manager before Third Session Manager. |
Fourth Session Manager |
The Session Manager instance that you select as the fourth Session Manager. It provides continued service to SIP devices associated with this communication profile when the primary, secondary, or third Session Manager server becomes unavailable. This is an optional field. |
Primary Region |
The Session Manager region that you select as the primary region. You must select the primary region of the Session Manager server. You can create the regions on the Elements > Session Manager > Session Manager Administration > Groups > Session Manager Groups page. You must select the value of regions as per the order of display. For example, if you select the secondary region value before the primary region, the system displays the following error message: Selection of regions should be as per their order of display. Select Primary Region before Secondary Region. |
Secondary Region |
The Session Manager region that you select as the secondary region. This is an optional field.
Note:
If you select the same region and the region does not have sufficient Session Managers, the system displays the following error message: <Secondary Region> - <Name_of_the_Region> the assigned regions must contain enough SMs to satisfy the Primary/Secondary/Third/Fourth region selection count. |
Third Region |
The Session Manager region that you select as the third region. This is an optional field. |
Fourth Region |
The Session Manager region that you select as the fourth region. This is an optional field. |
Survivability Server |
For local survivability, you can specify a survivability server. The server provides survivability communication services to devices associated with a communication profile, when the local connectivity to Session Manager instances in Avaya core is lost. If you select Branch Session Manager, and the termination and origination application sequences contain a Communication Manager application, sequencing to this application continues, locally, to Communication Manager survivable remote server. This survivable remote server is resident with the Branch Session Manager selected. A selection is optional.
Note:
If a termination or origination application sequence contains a Communication Manager application, the Communication Manager instance associated with the application must be the main server for the Communication Manager survivable remote server that resides with Branch Session Manager. After typing a minimum of 3 characters, wait for three seconds to capture the final keyword and fetch the required results. |
Max. Simultaneous Devices |
The maximum number of endpoints that you can register at a time by using this communication profile. If you register more than one endpoint, all the endpoints receive calls simultaneously. |
Block New Registration When Maximum Registrations Active |
If you select the check box, the system denies any new registrations with Session Manager when an endpoint attempts to register using this communication profile after the registration requests exceed the administered limit. The system sends a warning message and stops the SIP service to the endpoint. If you clear the check box, the system accepts the new registration and unregisters the endpoint with the oldest registration. However, if the endpoint with the oldest registration is active on a call, then the system does not affect the call and keeps that device registered for that call only. |
Origination Application Sequence |
The application sequence the system invokes when routing calls from this user. A selection is optional.
Note:
If you specify origination and termination application sequences, and if each sequence contains a Communication Manager application, Communication Manager must be the same in both the sequences. |
Termination Application Sequence |
The application sequence invoked when the system routes calls to this user. A selection is optional.
Note:
If you specify origination and termination application sequences, and if each sequence contains a Communication Manager application, Communication Manager must be the same in both the sequences. |
Emergency Calling Origination Sequence |
The list of application sequences invoked when the system routes emergency calls from this user. |
Emergency Calling Termination Sequence |
The list of application sequences invoked when the system routes emergency calls to this user. |
Home Location |
The home location to support mobility for the currently displayed user. Session Manager uses the home location when the IP address of the calling phone does not match the IP Address Pattern of any location. You must specify a value. |
Conference Factory Set |
The conference factory set to enable media capability-based call routing to the Conferencing SIP entities. Use the Session Manager > Application Configuration > Conference Factories page to administer the Conference Factory Sets. |
Enable Centralized Call History |
The option to enable the call history feature for SIP users. By default, the system disables the call history feature. The maximum number of call logs per communication profile is 100. |
Enable Client |
The drop-down list of the supported clients. Select the required client. |
Name |
Description |
|---|---|
Service Profile |
The profile that you assign to the user. The user can gain access to the service contained in the profile. |
The system displays these fields only if a Communication Manager Endpoint profile exists for the user.
Name/Button |
Description |
|---|---|
System |
Communication Manager on which you add the endpoint. The Communication Manager system on which you add the endpoint. You must select the system. |
Profile Type |
The type of the profile for the user. |
Extension |
The extension of the endpoint that you associate with this profile. You must select the extension. |
View Endpoint |
The list of existing or available endpoints based on the selection of the Use Existing Endpoints check box. |
Set Type |
The set type of the endpoint. When you select a template, the system populates the corresponding set types. |
Security Code |
The security code for authorized access to the endpoint. |
Port |
The relevant port for the set type you select. You must select the port. |
Voice Mail Number |
The voice mail number of the endpoint.
Note:
You must clear Local Device Services Data on all Avaya Aura® Web Gateway nodes if you change the value of Voice Mail Number. |
Preferred Handle |
Numeric only handles, SIP handles, or non-SIP handles, that are administered for a user. The Preferred Handle field is optional. Select numeric handle for alphanumeric support. By default, the field is blank. If SIP entity is of the Communication Manager type, Session Manager uses preferred handle in CM Endpoint profile. |
SIP URI |
A unique alphanumeric communication address of the user to make and receive voice or video calls. The SIP URI address can be: <username-projectname>@<xyz.com>. |
Attendant |
The option to enable the attendant feature on the endpoint. If you select this check box, you can administer the endpoint as an attendant. When you select the 9641SIP template type from Template, the system enables the Attendant check box. |
Enhanced Callr-Info display for 1–line phones |
The option to activate the enhanced Callr-info operation on the phone. The Enhanced Callr-Info display for 1-line phones field on the station form is valid for the following set types:
The options are:
|
Delete Endpoint on Unassign of Endpoint from User or Delete User |
The option to specify whether to delete the endpoint from the Communication Manager device when you remove the association between the endpoint and the user or delete the user. |
Override Endpoint Name |
The option to override the following:
|
Name |
Description |
|---|---|
System |
The CS 1000 system of the endpoint. |
Target |
The system customer number for the Communication Server. |
Template |
The phone or endpoint template that you can choose for the user. The element manager maintains all templates. |
Update |
The option to update the endpoint profile information for the user. When you click Update, the system takes displays the element manager cut through for the updates. |
Service Details |
The service details, such as set type of endpoints that the system displays after phone creation. |
Primary DN |
The primary directory number of the phone. You can enter only numeric values. |
Include in Corporate Directory |
The option to add this profile to the CS 1000 corporate directory. |
The system displays the following fields only if you can configure a messaging profile for the user
Name |
Description |
|---|---|
System |
The messaging system on which you add the subscriber. |
Template |
The template, system-defined or user-defined, that you associate with the subscriber. |
Mailbox Number |
The mailbox number of the subscriber. |
Password |
The password for logging on to the mailbox. |
Delete Subscriber on Unassign of Subscriber from User |
Provides the option to specify whether to delete the subscriber mailbox from the Messaging device or Communication System Management when you remove this messaging profile or when you delete the user. |
Name |
Description |
|---|---|
Officelinx System |
The Avaya Messaging system to which you add a mailbox. |
Refresh |
The option to get information about company, departments, and feature groups from Avaya Messaging and save locally on System Manager for future use. You do not require to refresh for every user. |
Mailbox Number |
The mailbox number of the subscriber. It should be numeric only. |
Numeric Password |
The numeric password used to log in to the Avaya Messaging system. |
Confirm Numeric Password |
The numeric password you retype to confirm. |
Application User Password |
The password used to gain access to non-telephone applications, such as Web Client, iLink Pro, iLink Pro Mobile, and iLink Pro Desktop. |
Confirm Application User Password |
The password you retype to confirm. |
Company |
The name of the company to which the user belongs. |
Department |
The department to which the user belongs. |
Feature Group |
The feature group name that determines the rules for the mailboxes associated with it. |
Capability |
The type of functionality the user contains. The values are:
|
Domain Account Name |
The mailbox NT account name of the Avaya Messaging profile. |
Synchronization User Name |
The account name used to gain access to the email server, for example, Microsoft Exchange and Google Gmail. |
Only one-way update is supported for Officelinx elements. If you make any change directly on Officelinx, it does not reflect on System Manager. If you edit the user from System Manager, it overrides the changes you made directly on Officelinx.
Use this profile to assign a new or an existing user to a System Manager device in User Management.
While adding a user, if you choose to assign a CM endpoint profile and an IP Office endpoint profile to the user, then the system uses the IP Office endpoint profile as the survivability option for the CM endpoint profile. That is, the endpoint extension used in the CM endpoint profile is also used for creating an IP Office endpoint profile so that when Communication Manager is unavailable, the IP Office device can serve the extension.
If a Communication Manager endpoint profile is present while adding or editing a user, the user administration functions in the centralized mode. If a Communication Manager endpoint profile is not present, the user administration functions in the distributed mode.
Commit the Communication Manager endpoint profile and the Session Manager endpoint profile before you add an IP Office endpoint profile for a centralized user.
Name/Button |
Description |
|---|---|
System |
The list of IP Office device names from which you can select the IP Office device you associate with the user. |
Template |
The list of user templates from which you can select your preferred template to set the user configurations. |
Use Existing Extension |
Select the check box to use an existing endpoint extension to associate with this profile. If you do not select this check box, the system uses the available extensions. |
Extension |
The extension of the endpoint you associate. The field lists the endpoints, existing or available, based on option you selected in the Use Existing Endpoints check box. |
Endpoint Editor button |
Starts the IP Office application, where you can edit or view the details of the IP Office endpoint. After you save the changes in IP Office manager, the system does not update the modified data on the device or database until you commit the changes on the User Profile | Edit | <User Name> page. |
Module-Port |
The module port combination list for IP Office analog extensions. You must select Module-Port for centralized users with Set Type as Analog. |
Set Type |
The set type for the IP Office endpoint profile. By default, the Set Type field is disabled. If you select a template, the set type is auto populated. |
Delete Extension On User Delete check box |
Provides the option to delete the extension associated with the user while deleting the user. By default, this check box is clear. This option is available for communication profiles associated with Analog and Digital set types. |
Name |
Description |
|---|---|
Equinox User Password |
The Equinox user password. |
Virtual Room Number |
The virtual room number of the Equinox user. |
Name |
Description |
|---|---|
System |
The Presence Services instance that is the home Presence Services server for the user. You must select an instance. As a home server, the Presence Services instance can perform the following for the communication profile:
|
SIP Entity |
The option to route the SIP-based messages through Presence Services. This system selects the SIP entity if you select a Presence Services instance in the System field. SIP Entity is read-only. If the system cannot identify a SIP entity, an appropriate error message is displayed in the field. |
IM Gateway SIP Entity |
The Presence Services instance for the user. |
Publish Presence with AES Collector |
The option that determines if Presence Services must publish presence with AES Collector. The options are:
The default is System Default. You can change the default value. You do not require to configure AES Collector in the Presence Services server. |
Name |
Description |
|---|---|
Account |
The account name. |
Account Address |
The account address. |
Source |
The source name. |
Source Address |
The source address. |
When you click Resource Details, Account Details, or Source Details, the system displays the Assignment Management page in Work Assignment.
Button |
Description |
|---|---|
Resource Details |
Displays the Assignment Management page where you can configure assignment targets for the user. You can assign resource details to an agent only when the user has the Work Assignment profile assigned to the user. |
Account Details |
Displays the text box where you can add or modify the account name and account address. You can add attributes to the account when the account is added to the agent. |
Source Details |
Displays the text box where you can add or modify the source name and source address. You can add properties and attributes to the source when the source already exists. |
Name |
Description |
|---|---|
Name |
The name of the role. |
Description |
A brief description about the role. |
Name |
Description |
|---|---|
Name |
The name of the group. |
Type |
The group type based on the resources. |
Hierarchy |
The position of the group in the hierarchy. |
Description |
A brief description about the group. |
Name |
Description |
|---|---|
Description |
A brief description of the contact list. |
Adding a private contact to a user is a two-step process. First, you add the private contact and then you add the new private contact to the associated contacts. Ensure that you commit your updates after you add the private contact.
Name |
Description |
|---|---|
Last Name |
The last name of the contact. |
First Name |
The first name of the contact. |
Scope |
The categorization of the contact based on whether the contact is a public or private contact. |
Speed Dial |
The value that specifies whether the speed dial is set for the contact. |
Speed Dial Entry |
The reduced number that represents the speed dial number. |
Presence Buddy |
The value that specifies whether you can monitor the presence information of the contact or not. False indicates that you cannot track the presence of the contact. |
Button |
Description |
|---|---|
Filter menu |
You can find the Filter menu icon next to the name of each column. Filters the data based on the search criteria. |
Adding a private contact to a user is a two-step process. First, you add the private contact and then you add the new private contact to the associated contacts. Ensure that you commit your updates after you add the private contact.
Name |
Description |
|---|---|
Last Name |
The last name of the private contact. |
First Name |
The first name of the private contact. |
Display Name |
Display name of the private contact. |
Contact Address |
The address of the private contact. |
Description |
A brief description about the contact. |
Button |
Description |
|---|---|
Filter menu |
You can find the Filter menu icon next to the name of each column. Filters the data based on the search criteria. |
Button |
Description |
|---|---|
Edit |
Displays the User Profile | Edit | <User Name> page. Use the User Profile | Edit | <User Name> page to modify the details of the user account. |
Done |
Closes the User Profile | Edit | <User Name> page and returns to the User Management page. |