Displays the name of the configured SIP domain name.

If SIP Domain is nonblank, create an Avaya SIP communication address for the user.

The system changes the SIP domain for all selected users with the value you provide.

Displays the name of the configured Presence domain name.

If Presence/IM Domain is nonblank, create an Avaya Presence/IM communication address for the user.

The system changes the Presence/IM Domain domain for all selected users with the value you provide.

The option to automatically generate the communication profile password.

If you select the Auto Generate Communication Profile Password option, the system disables the Communication Profile Password field.

The communication profile password.

The field is available only if you enable the communication profile. The password policy is configured on the UsersUser ManagementCommunication 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.

The link to change the Communication Profile password.

When you click the Edit link, the system displays the Confirm Password field along with the Generate and Cancel links.

The communication profile password to reenter for confirmation.

The option to automatically generate the communication profile password.

System Manager sends the generated password to the user, if:

Cancels the password change operation.

The digits that the system must prefix to the telephone number or Avaya E.164 handle. The default is plus (+).

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

An option to create the profile for the user if a profile does not already exist.

The system displays the check box only when you select the communication profile. If the communication profile already exists, the system does not make any changes to the profile data.

For more information, see Create new profile option.

When you enable the Enable Policy Based Assignment of Session Managers field on the ElementsSession ManagerGlobal 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:

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 ElementsSession ManagerSession Manager AdministrationGroupsSession 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 ManagerApplication ConfigurationConference 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.

An option to create the profile for the user if a profile does not already exist.

The system displays the check box only when you select the communication profile. If the communication profile already exists, the system does not make any changes to the profile data.

For more information, see Create new profile option.

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

An option to create the profile for the user if a profile does not already exist.

The system displays the check box only when you select the communication profile. If the communication profile already exists, the system does not make any changes to the profile data.

For more information, see Create new profile option.

The option to instruct the system to create a new extension for the user.

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

This field is configured for CS 1000 station types only. You can select the specific set for Set Type. On the Manage Endpoint page, Sub Type is labeled as Set.

This field is configured for CS 1000 station types only. This field allows you to leave the field blank or enter a string of up to 9 characters. With Release 8.0, more than one station can use the combination of System ID and Terminal Number.

With Release 8.0.1, each station must have a unique combination of System ID and Terminal Number.

The security code for authorized access to the endpoint.

Avaya SIP or Avaya E.164 handle administered for the user. The field is optional. By default, the field is blank.

The password to gain access to the endpoint.

The system displays the field if you select Agent in Profile Type.

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.

An option to create the profile for the user if a profile does not already exist.

The system displays the check box only when you select the communication profile. If the communication profile already exists, the system does not make any changes to the profile data.

For more information, see Create new profile option.

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

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

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

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

An option to specify whether to delete the endpoint from the CS 1000 system when you unassign the endpoint from the user.

An option to create the profile for the user if a profile does not already exist.

The system displays the check box only when you select the communication profile. If the communication profile already exists, the system does not make any changes to the profile data.

For more information, see Create new profile option.

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

The mailbox number of the subscriber. The options are:

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.

An option to create the profile for the user if a profile does not already exist.

The system displays the check box only when you select the communication profile. If the communication profile already exists, the system does not make any changes to the profile data.

For more information, see Create new profile option.

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 option to specify if the system must use the next mailbox number to associate with this profile.

The range of mailbox numbers assigned to the Avaya Messaging system.

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

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

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:

The mailbox NT account name for the Avaya Messaging profile. The options are:

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

The options are:

An option to create the profile for the user if a profile does not already exist.

The system displays the check box only when you select the communication profile. If the communication profile already exists, the system does not make any changes to the profile data.

For more information, see Create new profile option.

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:

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:

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

An option to create the profile for the user if a profile does not already exist.

The system displays the check box only when you select the communication profile. If the communication profile already exists, the system does not make any changes to the profile data.

For more information, see Create new profile option.

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 extension of the endpoint to which you associate the profile. The options are:

A list of user templates from which you can select a template to set the user configurations.

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

An option to create the profile for the user if a profile does not already exist.

The system displays the check box only when you select the communication profile. If the communication profile already exists, the system does not make any changes to the profile data.

For more information, see Create new profile option.

The password that is used to log in to the Avaya Workplace Client Management.

The number of a virtual room that is used to create a conference.

By default Virtual Room Number serves as Meeting ID when a conference is created. The options are:

Runs the bulk user edit job immediately.

Schedules the bulk user edit job.

Cancels the edit operation and returns to the User Management page.