Here is a list of all of end user options where we have a person, we have a person that’s going to have an interactive log in, they’re going to be able to manage their phone, it could be used within your directory, so when people pull up a directory they now can see the username and the extension associated with it. And again end users we could tie into an LDAP database that could be external and we could synchronize those end users and pull them into our environment so we don’t have to create them necessarily. We may need to do some modifications but don’t forget BAT, we could use BAT to get those users. Well first of all synchronize, get the users in, export the users make your modifications and then import them back into the system \u2013 much easier than typing in 1,000 individual users, that’s what I’m thinking. But there is application users \u2013 you’re not going to be able to use LDAP, but typically we aren’t adding quite as many application users because they’re specific to an application, such as the Contact Center Express or a Communications Manager Assistant, all of that is considered internal. So these are internal users that we’re going to be creating and storing within the Communications Manager database, not reliant on LDAP or an external environment. With our end users we still could store them in the Communications Manager database but again we could import them or synchronize them with an external LDAP directory and that makes it much easier.<\/span><\/p>\n The user locale is the language that we’re going to be selecting. Now there isn’t translation that goes on here other than the fact that what is system displayed on devices or within the user web pages can now be displayed in the language that they’ve selected or that you’ve selected. If the phone load configuration locale needs to be updated or we need to download that it’s going to come from our TFTP server. We also can see configuration files for the devices that are going to contain the locale information.<\/span><\/p>\n Any kind of language that you want displayed on that phone, because a lot of times we have topologies that may span into other countries so we don’t want to force people in Germany to have to be able to read the English language that’s going to display on their phones – we can select Germany for that locale and now their information will display in German. Like I said, it doesn’t do any translation as far as that goes, but it does display the appropriate language on that phone.<\/span><\/p>\n When we associate users with devices, these devices can include of course phones, the IP communicator and any extension mobility profiles. So end users can be associated with devices, and within that we could have unique user attributes, things like the corporate directory that allows users to display a personal name. We can have that dial by name feature, so that can also utilize the user information. We also have the ability to manage computer telephony integration (CTI) route points. This is specifically used in the contact center solution. This could be the contact center extension number, so all the call routing scripts to your agents, all can be set up and the call routing numbers can be managed.<\/p>\n Then we also have presence. Presence is the one that collects information about your availability to take a call so your user communications device such as your IP phone or your Cisco Unified Presence Communicator can all be associated with your user account. That’s how it all kind of ties together, all of your devices, all of your personal communicator information or any applications that you’re working in, can all be managed through that user account.<\/p>\n We can provide different user access level within our Communications Manager Express. We can set up a system administrator account, which can do everything. The customer administrator, which we could limit, like let’s say that we want them to manage phones and we just want them to add, change, delete maybe telephone devices. We can set up that customer administrator level. Then the phone user themselves managing their speed dials, and all the pertinent information that an end user would manage.<\/p>\n Now in order to set this up, we as the administrator can define user level access and we can do it via the command line. We could do remote Authentication Authorization and Accounting (AAA), we could have a AAA server configured with our user accounts and we’ll use the ip http authentication<\/strong><\/span> command to enable access to the remote authentication server. In other words to point to that AAA server and if authentication to the server fails the local router could also contain a database that can be configured with your users and their appropriate user level access.<\/p>\nUser Locale<\/span><\/h2>\n
![\"Different](\"\/wp-content\/themes\/learncisco\/assets\/images\/icomm\/050-user-locale.jpg\" "\\"Different")
<\/span><\/p>\nDevice Association<\/h2>\n
User Access Levels in Cisco Unified Communications Manager Express<\/h2>\n
User Locale in CME<\/h2>\n