There is not a max. number of profiles that can be created. However there are limits to the number of login/logouts and request because of the impact it would have on the CPU. And there is a service parameter which has a max of 100. Please see below for more info on these settings and it's effects:
4500 login/logout per hour is on MCS 7845. This number is low if it is MCS7835 server. When 101st user try to log in then user will see message on phone - "system busy please try later",(if max is set to 100).
Breaking point will be if 75 login/logout per min is increased to say 100 login/logout per min then CPU usage will go above 60% and might cause issues with call processing. For "Maximum Concurrent Requests" you need to limit value to 4 or max 5.
Maximum Concurrent Requests :
This parameter specifies the maximum number of login or logout operations which can occur simultaneously. This maximum prevents the Extension Mobility service from consuming excessive system resources. The number of allowed concurrent sessions may be set as an integer from 1 to 100. This is a required field. Default: 3. Minimum: 1.
Thanks for the detailed response! We'll be testing this out for a new customer in a few weeks. Can you point me to the docs where I can find this info?
Sure no problem, all this info should be available in the SRND. If you can't find it I'll post a doc with it. One other service parm. you should keep in mind as well is:
Multiple Login Behavior- the default is multiple logins are not allowed.
The following is copied and pasted from the Contextual Help within CUCM v7
Clusterwide Parameters (Parameters that apply to all servers)
This parameter determines whether a maximum login time is enforced. The Maximum Login Time parameter specifies the login time. Valid values specify True (login time is enforced) or False (no time limit for logins).
This is a required field.
Default: False
This parameter specifies the maximum time that a user is allowed to be logged in to a device, such as 8:00 (8 hours) or :30 (30 minutes). The system ignores this parameter if the Enforce Maximum Login Time parameter is set to False.
This is a required field.
Default: 8:00
Maximum length: 7
Allowed values: Valid value specifies up to 168 hours in the format HHH:MM where HHH represents the number of hours and MM represents the number of minutes. For example, for 168 hours, enter 168:00; for 25 hours, 15 minutes, enter 25:15; for 30 minutes, enter :30
Unit: Hours:Minutes
This parameter specifies the maximum number of login or logout operations which can occur simultaneously. This maximum prevents the Extension Mobility service from consuming excessive system resources. The number of allowed concurrent sessions may be set as an integer from 1 to 80.
This is a required field.
Default: 15
Minimum: 1
Maximum: 80
This parameter specifies the behavior for multiple attempted logins by the same user on different devices. Valid values specify Multiple Logins Allowed (the same user ID can be logged in to extension mobility on more than one device), Multiple Logins Not Allowed (a user ID can only be logged into one device), and Auto Logout (if a user ID is logged into extension mobility on one device, and the same user ID attempts to login to extension mobility on a different device, the first device automatically logs out).
This is a required field.
Default: Multiple Logins Not Allowed
This parameter specifies whether the user ID to be used is alphanumeric or numeric. Valid values specify True (user ID is alphanumeric) or False (user ID is numeric).
This is a required field.
Default: True
This parameter specifies whether the user ID of the last user logged in on a phone is remembered by the extension mobility application. Valid values specify True (remember the last user ID) or False (do not remember the last user ID). For greater security, use the default value of False.
This is a required field.
Default: False
This parameter determines whether the call information stored on the phone directory (missed calls, placed calls, received calls) is cleared when a user manually logs in or out of a phone. Valid values specify True (the phone deletes the call information) or False (the phone does not delete the call information and subsequent phone users can review the missed, placed, and received call information).
This is a required field.
Default: False
This parameter determines whether Cisco Unified Communications Manager (Unified CM) validates the IP address of the source that is requesting login or logout. Validation is first performed against the Extension Mobility cache for the device to be logged in or logged out; if the requesting source's IP address is not found in the Extension Mobility cache, the IP address is next checked against the list of trusted IP addresses and hostnames specified in the Trusted List of IPs service parameter; if the requesting source's IP address is not found in that list Unified CM checks the requesting IP address against the list of devices registered to Unified CM. If the IP address of the requesting source is found in the Extension Mobility cache or in the list of trusted IP address or is a registered device, the device is allowed to perform login or logout. If it is not found, the login or the logout attempt is blocked. Validating the IP address may increase the time it takes to login or logout a device but does offer a layer of additional security to help prevent unauthorized login or logout attempts, especially when used in conjunction with logins from separate trusted proxy servers from remote devices. For more information, refer to the design guidelines in the Extension Mobility documentation. Valid values specify True (validate the IP address of the source that is requesting login or logout) or False (do not validate the IP address of the source that is requesting login or logout).
This is a required field.
Default: False
This parameter specifies the list of trusted IP addresses and hostnames that Cisco Unified Communications Manager (Unified CM) use to validate the IP address of the source that is requesting login or logout. Separate each address or hostname by a semicolon; IP address ranges and regular expressions are not supported. The list in this parameter can be a maximum of 1024 characters. This parameter works in conjunction with the Validate IP Address service parameter. When the Validate IP Address service parameter is set to True, Unified CM checks three locations in succession to determine whether the source that is requesting login/logout has the authority to perform the operation. First, the IP address of the source that is requesting the login or logout is checked against the Extension Mobility cache; if the requesting source's IP address is not found in the cache, the list of trusted IP addresses/hostnames defined in this parameter is checked; if it is not found in this list, it is checked against the list of devices registered to Unified CM. If the requesting source's IP address is not found in any of these places, it cannot be validated and the login/logout operation fails.
Maximum length: 1024
Allowed values: Only valid IPv4 addresses or hostname having valid characters (a-z,A-Z,0-9,@,-,_,.) are allowed.
This parameter determines whether the use of web proxy for Extension Mobility login/logout is allowed. The service parameter, Validate IP Address, must be set to True for this parameter to take effect. Valid values specify True (allow login or logout using a web proxy that is identified in the service parameter Trusted List of IPs) or False (do not allow login or logout operation using a web proxy).
This is a required field.
Default: True
This parameter defines the maximum number of IP addresses that can be stored in the Extension Mobility cache for the purpose of validation when a device logs in to Extension Mobility or requests a logout operation. This parameter works in conjunction with the Validate IP Address parameter. When the Validate IP Address is set to True and a login or logout request is received, the IP address of the source that is requesting a login or logout must be validated before the operation is allowed to continue. The first location that gets checked is the cache. If the IP address requesting login/logout matches an IP address that is present in the cache, the device is allowed to perform the operation. If the IP address that is requesting login/logout is not present in the cache, two other locations are checked to validate the IP address: the Trusted List of IPs service parameter and the list of devices registered to Cisco Unified Communications Manager (Unified CM). If the requesting source's IP address is not found in any of these places, it cannot be validated and the operation fails. The cache is created during the Extension Mobility service initialization if the Validate IP Address is set to True during initialization. If Validate IP Address parameter is set to False and the cache is not created during initialization, it gets created when the Validate IP Address is set to True for the first time after initialization. The cache is routinely updated during device login and gets cleared when the Extension Mobility service is restarted.
This is a required field.
Default: 10000
Minimum: 1000
Maximum: 20000
Getting Started
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community:
