Enabling the Cme Gui

Cisco provides a graphical user interface (GUI) that allows you to manage some of the CME basic functions through a web interface. These basic functions include configuring and managing ephones, ephone-dns, some system and voice-mail functions, and reports.

Note After being in the Cisco world for some time, you will definitely get the feeling that real Cisco techs use the command-line interface (CLI). Seeing the CME GUI will only reinforce that feeling; although it does enable you to configure some basic settings, you can accomplish far more by using the command line. The GUI would suffice for a phone administrator whose primary job is the configuration of new phones and phone lines.

Before you are able to access the GUI, there are a few preliminary configuration steps you need to have in place. First and foremost, you need to ensure that you have loaded into the flash memory of the CME router the files that power the GUI. If you extracted the TAR file that contains the full CME installation into the flash of the CME router, the GUI files should be included. If you installed the CME files individually, be sure to download and install the CME GUI TAR file pack from Cisco.com. For more information on downloading and installing CME files into the flash of the router, check out Chapter 4, "Installing Cisco Unified Communications Manager Express."

Tip You can always verify that you have installed the GUI files by performing a directo

ry list of your router's flash. Different CME versions organize the file structure differently,

but should have relatively the same files. Here's a directory listing of CME version 4.3:

CME_Voice# dir

flash:

Directory of flash:/

1

drw-

0

Jun

10

2008

14

57

20

-07:

00

bacdprompts

13

-rw-

22224

Jun

10

2008

14

57

30

-07:

00

CME43-full-readme-

v.

2.0.txt

14

drw-

0

Jun

10

2008

14

57

30

-07:

00

Desktops

27

drw-

0

Jun

10

2008

14

57

36

-07:

00

gui

45

-rw-

496521

May

12

2008

21

30

00

-07:

00

music-on-hold.au

46

drw-

0

May

12

2008

21

30

00

-07:

00

phone

127

drw-

0

May

12

2008

21

35

46

-07:

00

ringtones

161

-rw-

45460908

Jun

12

2008

15

17

22

-07:

00

c2801-adventerprisek9_

ivs-mz.124-

15.T5.bin

129996800 bytes total (16123904

bytes free

CME_Voice# dir

flash:gui

Directory of flash:/gui/

28

-rw-

953

Jun

10

2008

14

57

36

-07:

00

Delete.gif

29

-rw-

3845

Jun

10

2008

14

57

38

-07:

00

admin_user.html

30

-rw-

647358

Jun

10

2008

14

57

40

-07:

00

admin_user.js

31

-rw-

1029

Jun

10

2008

14

57

40

-07:

00

CiscoLogo.gif

32

-rw-

174

Jun

10

2008

14

57

40

-07:

00

Tab.gif

33

-rw-

16344

Jun

10

2008

14

57

42

-07:

00

dom.js

34

-rw-

864

Jun

10

2008

14

57

42

-07:

00

downarrow.gif

35

-rw-

6328

Jun

10

2008

14

57

42

-07:

00

ephone_admin.html

36

-rw-

4558

Jun

10

2008

14

57

42

-07:

00

logohome.gif

37

-rw-

3724

Jun

10

2008

14

:57

42

-07:

00

normal_user.html

38

-rw-

0

Jun

10

2008

14

:57

42

-07:

00

normal_user.js

39

-rw-

843

May

12

2008

21

29

56

-07:

00

sxiconad.gif

40

-rw-

1347

May

12

2008

21

29

56

-07:

00

Plus.gif

41

-rw-

2399

May

12

2008

21

29

56

-07:

00

telephony_service.html

42

-rw-

870

May

12

2008

21

29

56

-07:

00

uparrow.gif

43

-rw-

9968

May

12

2008

21

29

56

-07:

00

xml-test.html

44

-rw-

3412

May

12

2008

21

29

58

-07:

00

xml.template

129996800 bytes total (16123904 bytes free)

129996800 bytes total (16123904 bytes free)

Because you will be accessing the GUI through a web interface, you need to turn the CME router into a mini-web server to serve up the CME pages. The configuration in Example 6.17 accomplishes this feat.

Example 6.17 Configuring the CME Router as a Web Server

CME_Voice(config)# ip

http server

CME_Voice(config)# ip

http secure-server

% Generating 1024 bit

RSA keys, keys will be non-exportable.

.[OK]

CME_Voice(config)# ip

http path flash:/gui

CME_Voice(config)# ip

http authentication local

Example 6.17 enables both the HTTP (ip http server) and HTTPS (ip http secure-server) services on the router. Of course, HTTPS is the preferred method of accessing the CME GUI because the CME router encrypts all communication. The ip http path flash:/gui command sets the HTTP server to use files from the GUI subdirectory of flash memory of the CME router for HTTP requests. Finally, the CME router will use its local user database to authenticate users attempting to access the web interface.

Note You might need to change the argument of the ip http path command based on where the HTML files are located for the CME GUI. Earlier versions of CME placed all CME files directly into flash without any directory structure. In this case, the command should be entered as ip http path flash:.

The next step in enabling the CME GUI is to create a user account with permission to access and manage the CME router. Example 6.18 configures this.

Chapter 6: Configuring Cisco Unified CME Voice Productivity Features 207 Example 6.18 Creating a CME Web Administrator Account and Adding Permissions

CME_Voice(config)# telephony-service

CME_Voice(config-telephony)# web admin ?

customer customer admin

system system admin

CME_Voice(config-telephony)# web admin system

?

name admin username

password admin password

secret secret password

CME_Voice(config-telephony)# web admin system

name

?

WORD username for admin

CME_Voice(config-telephony)# web admin system

name

NinjaAdmin

?

password admin password

secret secret password

CME_Voice(config-telephony)# web admin system

name

NinjaAdmin

secret

?

0 UNENCRYPTED password will follow

5 ENCRYPTED password will follow

CME_Voice(config-telephony)# web admin system

name

NinjaAdmin

secret

0 ?

WORD Admin password

CME_Voice(config-telephony)# web admin system

name

NinjaAdmin

secret

0 cisco

CME_Voice(config-telephony)# dn-webedit

CME_Voice(config-telephony)# time-webedit

Key Topic

The CME router is now equipped with a user account called NinjaAdmin with the password cisco.

By default, the CME GUI is not able to add ephone-dns to the CME configuration or modify the time on the CME router. The dn-webedit and time-webedit commands unlock these functions.

Note If you are synchronizing your router's clock via NTP, do not enter the time-webedit command, to ensure that the time remains set to the more accurate NTP server.

The CME router's web interface is now ready to go. The final step is to connect to the CME router using a supported web browser platform.

Note At the time of this writing, the only supported web browser for CME is Internet Explorer version 6 or later. However, with the continued popularity of alternative browsers such as Mozilla Firefox and Safari, this is likely to change in the near future.

From the supported web browser, enter the URL http-J/<CME_IP_Address>/ccme.html to access the CME GUI. After authenticating with your web admin account, the CME management console is displayed, as shown in Figure 6.11.

Expert System Interface
Figure 6.11 CME Web-Based Management Interface

Note The image shown in Figure 6.11 was captured after clicking Configure > Phones in the CME GUI. This gives you something a little more exciting to look at than the opening gray screen.

Was this article helpful?

0 0

Post a comment