The name of the tenant that you select.

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.

The name of the level 2 hierarchy of the tenant organization. For example, Department.

The name of the level 3 hierarchy of the tenant organization. For example, Team.

The user provisioning rule that you must edit.

The last name of the user. For example, Miller.

Last Name can be up to 256 characters.

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.

The first name of the user. For example, John.

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.

The middle name of the user, if any.

Middle Name can be up to 256 characters.

A brief description of the user.

Description can be up to 1024 characters.

The login status of the user

The time when the user details were last modified.

The login name of the user.

Login Name can be up to 256 characters.

With Release 8.1.3, the Login Name field supports the login name with apostrophe (‘). For example, aine’mars@xyz.com.

The following characters are supported:

• ,

• -

• _

• ?

• %

• !

• ~

• *

• (

• )

• =

• +

• $

• ,,

• ;

• .

• ‘

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.

If you log in to the system as admin, you cannot edit the login name.

The email address of the user

The authentication type that defines how the system authenticates the user. The options are:

• Enterprise: Directory servers that are external to System Manager authenticate the user login.

• Basic: Avaya authentication service authenticates the user login.

For bulk import of users by using Excel, User Type is always Basic. Therefore, the User Type field remains invisible in the Excel file.

Displays two new fields: New Password and Confirm Password.

The new password to log in to the System Manager web console.

The password that you reenter for confirmation.

The entity that created this user record. The possible values for this field is either an IP Address/Port, or a name representing an enterprise LDAP, or Avaya.

The localized display name of a user. The name is typically the localized full name.

Localized Display Name can be up to 256 characters.

If you do not provide any value for Localized Display Name, System Manager specifies the value as a combination of First Name and Last Name.

The full text name of the user represented in ASCII. The display name supports displays that cannot handle localized text, for example, some endpoints.

Endpoint Display Name can be up to 256 characters.

If you do not provide any value for Endpoint Display Name, System Manager specifies the value as a combination of First Name (Latin Translation) and Last Name (Latin Translation).

The personal title that is set to address a user. The title is typically a social title and not the work title. For example, Mr.

Title Of User can be up to 256 characters.

The preferred written or spoken language of the user. For example, English.

The preferred time zone of the user. For example, (+05:30) Chennai, Kolkata, Mumbai, New Delhi.

The employee number of the user. For example, 20081234.

Employee ID can be up to 256 characters.

The department to which the user belongs. For example, Human Resources.

Department can be up to 256 characters.

The organization where the user works. For example, Avaya LLC

Company can be up to 256 characters.

The preferred time zone of the user. For example, (+05:30) Chennai, Kolkata, Mumbai, New Delhi.

The department to which the user belongs. For example, Human Resources.

Department can be up to 256 characters.

The type of address. The options are:

• Office

• Home

The name of the street. For example, Magarpatta.

The name of the city or town. For example, Pune.

The postal code used by postal services to route mail to a destination. For example, 411028. For United States, the postal code is the Zip code.

The full name of the province. For example, Maharashtra.

The name of the country. For example, India.

Displays the Add Address page to add the address details.

Displays the Edit Address page to modify the address.

Deletes the selected address.

Displays the Choose Address where you choose a shared or common address.

The localized language for displaying the user name. For example, English. You must select the language.

The user name in the localized language you choose. For example, John Miller.

Displays fields that you can use to create a new localized name for the user.

Displays fields that you can use to modify the localized name of the user.

Deletes the localized names that you select for the user.

Adds or edits the localized name of the user.

Cancels the addition or edits of the localized name.

The option to automatically select the route pattern based on the primary or secondary Session Manager configured in the Session Manager Communication Profile.

The system makes this field available only for the SIP set type.

If you select the Calculate Route Pattern check box, the system populates the Sip Trunk field, and makes the field read-only.

The option to register an H.323 endpoint and a SIP endpoint together at the same time to the same extension. For more information about the SIP and H.323 dual registration feature, see Avaya Aura® Communication Manager Feature Description and Implementation on the Avaya Support website at http://support.avaya.com.

Creates a new communication profile for the user.

Deletes the selected communication profile.

Saves the communication profile information that you updated or added for a profile.

Cancels the operation of adding a communication profile.

The name of the communication profile for the user.

The profile that is made default as the active profile. There can be only one active profile at a time.

The type of handle.

A unique communication address of the user. Communication Manager Release 7.1.2 and later support alphanumeric handles.

The name of the domain with which the handle is registered.

To add a new communication address.

To edit the information of a selected communication address.

To delete the selected communication address.

The type of handle. The options are:

• Avaya SIP: Indicates that the handle supports Avaya SIP-based communication.

• Avaya E.164: Indicates that the handle refers to an E.164 formatted address. E.164 numbers can have a maximum of 13 digits and are usually written with a + prefix.

• Microsoft SIP: Indicates that the handle supports SIP-based communication.

• Microsoft Exchange: Indicates that the handle is an email address and supports communication with Microsoft SMTP server.

• Lotus Notes: Indicates that the handle is for Lotus Notes and domino calendar.

• IBM Sametime: Indicates that the handle is for IBM Sametime. The address must be in the DN=IBMHandle format.

• Avaya Presence/IM: Indicates that the handle is an address that is used for Extensible Messaging and Presence Protocol (XMPP)-based Internet Messaging (IM) services and XMPP or Session Initiation Protocol-based (SIP) Presence services.

  Note:

  To create the Presence communication profile, you must select Avaya Presence/IM and provide the communication address.

• GoogleTalk: Indicates that the handle supports XMPP-based communication with the Google Talk service.

• Other Email: Indicates that the handle is an email address other than MS Exchange email addresses.

• Other SIP: Indicates that the handle supports SIP-based communication other than the listed ones.

• Other XMPP: Indicates that the handle supports XMPP-based communication other than the listed ones.

• Work Assignment: Indicates that the handle supports accounts that can be assigned to an agent for Work Assignment.

The fully qualified domain name or uniform resource identifier. The address can be an email address, IM user, or an address of a communication device using which the user can send or receive messages. You must provide a fully qualified address.

Saves the new communication address or modified communication address information in the database.

Cancels the addition of communication address.

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:

• fixed: When you select this option, the system displays the Primary Session Manager, Secondary Session Manager, Third Session Manager, and Fourth Session Manager fields.

  The default value is fixed.

• fixed-region: When you select this option, the system displays the Primary Region, Secondary Region, Third Region, and Fourth Region fields.

  The system assigns the primary, secondary, third, or fourth region to the Session Manager Communication profile.

• location-region: When you select this option, the system does not display the Primary Session Manager and Secondary Session Manager fields and dynamically assigns Session Managers based on the mapping of locations to regions on the Elements > Session Manager > Session Manager Administration > Groups > Location to Region Mapping page.

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.

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.

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.

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.

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.

The Session Manager region that you select as the secondary region. This is an optional field.

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.

The Session Manager region that you select as the third region. This is an optional field.

The Session Manager region that you select as the fourth region. This is an optional field.

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.

After typing a minimum of 3 characters, wait for three seconds to capture the final keyword and fetch the required results.

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.

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.

The application sequence the system invokes when routing calls from this user. A selection is optional.

The application sequence invoked when the system routes calls to this user. A selection is optional.

The list of application sequences invoked when the system routes emergency calls from this user.

The list of application sequences invoked when the system routes emergency calls to this user.

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.

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.

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.

The drop-down list of the supported clients. Select the required client.

The profile that you assign to the user. The user can gain access to the service contained in the profile.

The Communication Manager system on which you add the endpoint. You must select the system.

The type of Communication Manager Endpoint profile that you create. You must select the profile type.

The existing endpoint extension to associate with this profile. If you do not select this check box, the system uses the available extensions.

The extension of the endpoint that you associate with this profile. You must select the extension.

The field lists the endpoints, existing or available, based on the option you selected in the Use Existing Endpoints check box.

The template, system defined or user defined, that you associate with the endpoint. Select the template based on the set type you add.

The set type of the endpoint. When you select a template, the system populates the corresponding set types.

The security code for authorized access to the endpoint.

The relevant port for the set type you select. You must select the port.

The field lists the possible ports based on the selected set type.

The voice mail number of the endpoint.

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 the type of SIP entity is Communication Manager, Session Manager uses the preferred handle in the CM Endpoint profile. By default, for a SIP station, Communication Manager uses the extension number as the phone number entry on an OPS station-mapping table. If your enterprise dial plan has SIP handles that are different from the Communication Manager extension, then use the Preferred Handle field to change the phone number entry on the OPS station-mapping table on the Communication Manager.

To modify the phone number entry, the Communication Address in System Manager should have a SIP handle. In the CM Endpoint Communication Profile, set the Preferred Handle field to the SIP handle format. After you click Commit, System Manager sets the Phone Number field in the OPS station-mapping table on Communication Manager to the SIP handle format. If you do not need this feature, then set the Preferred Handle value to None.

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>.

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.

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:

• 1603, 1608, 1616, 1408, 1416

• 2402, 2410, 2420

• 4606, 4612, 4612CL, 4624, 4602, 4602+, 4630, 4610, 4622, 4620, 4621, 4625,

• 6402D, 6408D, 6408D+, 6416D+, 6424D+, 607A1

• 7506D, 7507D

• 8405D+, 8410D, 8405D, 8411D

• 9404, 9408, 9601, 9601+, 9610, 9620, 9621, 9608, 9611, 9630, 9640, 9641, 9650

The options are:

• No: Does not change the callr-info interactions with the connected phone. The default setting.

• Yes: Activates the enhanced Callr-info operation including the application of the existing feature related system parameters. Clear Callr-Info option settings of leave-ACW, next-call, and on-call-release. If the callr-info button is not assigned to the phone on the station form, Enhanced Callr-Info display for 1-line phones does not apply.

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.

The option to override the following endpoint names:

• The endpoint name on Communication Manager with the value you configured on the Manage users page during synchronization.

  If you clear the check box, the system does not override the endpoint name on Communication Manager with the name you configured in System Manager during synchronization.

• The localized display name on the Manage Users page in the Localized Display Name field of Communication Manager. If you clear the check box, the system does not override the localized display name in the Localized Display Name field.

The system that will be the element manager of the CS 1000 endpoint profile. You must select the system.

The customer number of the CS 1000 system. You must select the target.

The system displays the field only when you select Add new.

The phone or endpoint template that you can choose for the user. The element manager maintains all templates. You must select a template.

The system displays the field only when you select Add new.

The station profile information updated for the user. When you click Update, the system takes you to the element manager cut-through for the updates.

The service details of endpoints, such as set type, after phone creation.

The primary directory number of the phone. You can enter only numeric values in this field.

The system displays the field only when you select Add new.

The option to add this profile to the CS 1000 Corporate Directory feature.

The messaging system on which you add the subscriber. You must select the system.

The option to specify whether to use an existing subscriber mailbox number to associate with this profile.

The mailbox number of the subscriber. You must select the mailbox number.

The field takes the existing mailbox number that you associate with this profile. The value in the field is valid only if you select the Use Existing Subscriber on System check box.

The Messaging application where you can edit or view details of the profile of the messaging endpoint.

After you save the changes in the Messaging system, 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.

The system-defined or user-defined template that you associate with the subscriber.

The password for logging in to the mailbox. You must provide the password.

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 delete the user.

The Avaya Messaging system to which you add a mailbox.

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.

The mailbox number of the subscriber. It should be numeric only.

The numeric password used to log in to the Avaya Messaging system.

The numeric password you retype to confirm.

The password used to gain access to non-telephone applications, such as Web Client, iLink Pro, iLink Pro Mobile, and iLink Pro Desktop.

The password you retype to confirm.

The name of the company to which the user belongs.

The department to which the user belongs.

The feature group name that determines the rules for the mailboxes associated with it.

The type of functionality the user contains. The values are:

• Standard

• Fax

• Messaging

• Collaboration

• Messaging and Collaboration

The mailbox NT account name of the Avaya Messaging profile.

The account name used to gain access to the email server, for example, Microsoft Exchange and Google Gmail.

The list of IP Office device names from which you can select the IP Office device that you associate with the user. You must select the template.

The list of user templates from which you can select your preferred template to set the user configurations.

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.

The extension of the endpoint. You must select the extension.

The field lists the endpoints, existing or available, based on the option you selected in the Use Existing Endpoints check box.

The option to start 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.

The module port combination list for IP Office analog extensions. You must select Module-Port for centralized users with Set Type as Analog.

The set type for the IP Office endpoint profile. By default, the Set Type field is disabled. If you select a template, the system populates the set type.

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.

The Equinox user password.

The virtual room number of the Equinox user.

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:

• Aggregate presence

• Archive instant messages if the Instant Messages option is enabled

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.

The Presence Services instance for the user.

The option that determines if Presence Services must publish presence with AES Collector. The options are:

• System Default

• Off

• On

The default is System Default. You can change the default value. You do not require to configure AES Collector in the Presence Services server.

The account name.

The account address.

The source name.

The source address.

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.

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.

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.

Use this check box to select a role. Use the check box displayed in the first column of the header row to select all the roles assigned to the user account.

The name of the role.

A brief description about the role.

Displays the Assign Role page to assign the roles to the user account.

Removes the selected role from the list of roles associated with the user account.

Use this check box to select a group.

The name of the group.

The group type based on the resources.

The position of the group in the hierarchy.

A brief description about the group.

Displays the Assign Groups page to add the user to a group.

Removes the user from the selected group.

A brief description of the contact list.

The last name of the contact.

The first name of the contact.

The categorization of the contact based on whether the contact is a public or private contact.

The value specifies whether the speed dial is set for the contact or not.

The reduced number that represents the speed dial number.

The value specifies whether you can monitor the presence information of the contact or not. A false value indicates you cannot track the presence of the contact.

Displays the Edit Contact List Member page. Use this page to modify the information of the selected contact.

Displays the Attach Contacts page. Use this page to select one or more contacts from the list of contacts.

In the Multi Tenancy environment, when the tenant administrator of a tenant creates or updates the user, the administrator can attach only the following contacts:

• Private contacts of the user

• Public contacts

• Users who belong to that tenant

Removes one or more selected contacts from the list of the associated contacts.

You can find the Filter menu icon next to the name of each column.

Filters the data based on the search criteria.

The last name of the private contact.

The first name of the contact.

The display name of the private contact.

The address of the private contact.

A brief description about the contact.

Displays the Edit Private Contact page. Use this page to edit the information of the contact you selected.

Displays the New Private Contact page. Use this page to add a new private contact.

Deletes the selected contacts.

You can find the Filter menu icon next to the name of each column.

Filters the data based on the search criteria.

Saves your changes and retains you on the same page for further modifications.

Modifies the user account and returns to the User Management or User Profile | View | <User Name> page.

Cancels the operation of modifying the user information and returns to the User Management or User Profile | View | <User Name> page.