With which of the following can users manage IP phone settings? (Choose two.)
- a CME router console session
- the CME browser-based GUI
- the telephone keypad
Users can manage IP phone settings either by using the telephone keypad or by logging on to the Cisco Unified Communications Manager Express (CME) browser-based graphical user interface (GUI). In order for a phone user to log on to the GUI, a systems administrator must create a phone user account for that user and associate that account with a device. The phone user can then access the GUI by using the Uniform Resource Locator (URL) http://ipaddress/ccme.html, where ip-address is the IP address of the CME router. To create a phone user account in the CME GUI, you should click Configure > Phones in the GUI.
You can also create phone user accounts by using the command-line interface (CLI) on the CME router. To create a phone user by using the CLI, issue the username user-name password password command in ephone configuration mode, where username is the user name you want to assign to the user and password is the password that you want to assign to the user. You should issue the username user-name password password command only in ephone configuration mode of the device that you want to assign to the user you are creating. For example, if you want user John to be able to manage the device settings of ephone 5 by using the CME GUI, you should issue the following commands on the CME router:
username john password b0s0n
The ephone 5 command places the router into ephone configuration mode for ephone 5. The username john password b0s0n command creates a new user name of john for ephone 5 and assigns that user name the password b0s0n.
A phone user cannot typically manage phone settings by using a CME router console session or Telnet. Although you could provide users with access to the CME CLI via either a console session or a Telnet session, users do not need access to the CLI to manage end-user phone settings. In addition, providing phone users with administrative access to the CLI is a security risk.