Cisco Unity Express Configuration

This section examines the configuration needed for Cisco Unity Express to communicate with Cisco Unified CME. This includes the final Cisco Unity Express CLI configurations and the Cisco Unity Express web initialization. The CME CLI configurations needed for interoperability between Cisco Unified CME and Cisco Unity Express are also discussed.

Cisco Unity Express Post-Installation Configuration

After an installation or upgrade of Cisco Unity Express software, the system will run the service-engine post-installation configuration tool. This tool allows the installer to implement the following Cisco Unity Express configurations:

■ Primary and secondary Domain Name System (DNS) servers

■ Primary and secondary Network Time Protocol (NTP) servers

■ Administrative credentials

Example 10.12 shows modified output from the post-installation configuration tool (output not relevant to this example has been removed).

Example 10.12 Post-Installation Configuration Tool

IMPORTANT IMPORTANT IMPORTANT IMPORTANT IMPORTANT IMPORTANT IMPORTANT IMPORTANT IMPORTANT IMPORTANT IMPORTANT IMPORTANT

Welcome to Cisco Systems Service Engine post installation configuration tool.

This is a one time process which will guide you through initial setup of your Service Engine. Once run, this process will have configured the system for your location.

If you do not wish to continue, the system will be halted so it can be safely removed from the router.

Do you wish to start configuration now (y,n)? y Are you sure (y,n)? y

Enter Hostname (my-hostname, or enter to use se-10-100-1-10): cue

Enter Domain Name

(mydomain.com, or enter to use localdomain): cisco.com Would you like to use DNS (y,n)?y

Enter IP Address of the Primary DNS Server

Found server 10.1.1.15

Enter IP Address of the Secondary DNS Server (other than Primary)

Found server 10.1.1.16

Enter Fully Qualified Domain Name(FQDN: e.g. myhost.mydomain.com)

or IP address of the Primary NTP server

(FQDN or IP address, or enter for 10.100.1.1): 10.100.1.1 Found server 10.100.1.1

Enter Fully Qualified Domain Name(FQDN: e.g. myhost.mydomain.com) or IP address of the Secondary NTP Server (FQDN or IP address, or enter to bypass):

Please identify a location so that time zone rules can be set correctly.

Example 10.12 Post-Installation Configuration Tool continued Please select a continent or ocean.

1) Africa 4) Arctic Ocean 7) Australia 10) Pacific Ocean

2) Americas 5) Asia 8) Europe

3) Antarctica 6) Atlantic Ocean 9) Indian Ocean #? 2

Please select a country.

1

Anguilla

18)

Ecuador

35)

Paraguay

2

Antigua & Barbuda

19)

El Salvador

36)

Peru

3

Argentina

20)

French Guiana

37)

Puerto Rico

4

Aruba

21)

Greenland

38)

St Kitts & Nevis

5

Bahamas

22)

Grenada

39)

St Lucia

6

Barbados

23)

Guadeloupe

40)

St Pierre & Miquelon

7

Belize

24)

Guatemala

41)

St Vincent

8

Bolivia

25)

Guyana

42)

Suriname

9

Brazil

26)

Haiti

43)

Trinidad & Tobago

10

Canada

27)

Honduras

44)

Turks & Caicos Is

11

Cayman Islands

28)

Jamaica

45)

United States

12

Chile

29)

Martinique

46)

Uruguay

13

Colombia

30)

Mexico

47)

Venezuela

14

Costa Rica

31)

Montserrat

48)

Virgin Islands (UK)

15

Cuba

32)

Netherlands Antilles

49)

Virgin Islands (US)

16

Dominica

33)

Nicaragua

17

Dominican Republic

34)

Panama

#?

45

Please select one of the following time zone regions.

1) Eastern Time

2) Eastern Time - Michigan - most locations

3) Eastern Time - Kentucky - Louisville area

4) Eastern Time - Kentucky - Wayne County

5) Eastern Standard Time - Indiana - most locations

6) Eastern Standard Time - Indiana - Crawford County

7) Eastern Standard Time - Indiana - Starke County

8) Eastern Standard Time - Indiana - Switzerland County

9) Central Time

10) Central Time - Michigan - Wisconsin border

11) Central Time - North Dakota - Oliver County

12) Mountain Time

13) Mountain Time - south Idaho & east Oregon

14) Mountain Time - Navajo

15) Mountain Standard Time - Arizona

16) Pacific Time

17) Alaska Time

18) Alaska Time - Alaska panhandle

19) Alaska Time - Alaska panhandle neck

20) Alaska Time - west Alaska

21) Aleutian Islands

The following information has been given:

United States Eastern Time

Therefore TZ='America/New_York' will be used. Is the above information OK?

Configuring the system. Please wait... Changing owners and file permissions. Change owners and permissions complete.

IMPORTANT::

IMPORTANT:: Administrator Account Creation

IMPORTANT::

IMPORTANT:: Create an administrator account. With this account, IMPORTANT:: you can log in to the Cisco Unity Express GUI and IMPORTANT:: run the initialization wizard. IMPORTANT::

Enter administrator user ID:

(user ID): cueadmin Enter password for admin:

(password): cisco Confirm password for admin by reentering it: (password): cisco

SYSTEM ONLINE cue>

The service-engine post-installation configuration tool begins by prompting the installer to start the configuration, followed by a prompt confirming that the configuration process should proceed.

Next the installer is prompted to either enter a hostname for the Cisco Unity Express module or take the default hostname. The default hostname in this example is se-10-100-1-10, which is "se" followed by the IP address of the service-engine. In this example, the hostname of cue was specified over the default hostname.

A prompt for a domain name follows. The installer has the option of entering the company's domain name or using the default domain name of localdomain. In this example, the domain name is configured as cisco.com.

The installer is asked if DNS will be used by the Cisco Unity Express module. If yes, the installer is prompted to enter the primary and secondary DNS server IP addresses. If no, a message appears stating that IP addresses must be used for all configurations.

Note Although Cisco Unity Express has the capability to use DNS to resolve IP addresses from hostnames, this means that the DNS server must be operational and accessible for Cisco Unity Express to interact with any host or endpoint that is defined by a hostname. For this reason, specifying IP addressing over hostnames is best practice.

Next the installer is prompted to enter the IP address of the primary and secondary NTP servers. If a DNS server has been configured in the previous step, the installer has the option of entering the fully qualified domain name (FQDN) of the NTP server. Unlike DNS, Cisco Unity Express assumes that an NTP server will be configured, because time is critical to the delivery and time-stamp information of voice-mail messages. In this example, Cisco Unity Express is configured to use Cisco Unified CME as the NTP server because CME is synchronized with an authoritative NTP server.

For Cisco Unity Express to be configured for the proper time zone, the installer is prompted to enter their location, country, and time zone. In this example, Americas, United States, and Eastern Time were chosen. This causes Cisco Unity Express to ask if it is in the same time zone as New York City.

Finally, administrative credentials are entered. These credentials will be used when accessing the Cisco Unity Express GUI later in this chapter. In Example 10.12, the administrative user ID is configured as cueadmin and the password is configured as cisco.

At this point, Cisco Unity Express has completed the post-installation configuration and the system is brought online.

Configuring Cisco Unified CME to Support Cisco Unity Express

This section focuses on the Cisco Unified CME configuration necessary to support Cisco Unity Express. This includes the HTTP server configuration, dial-peer configurations, message waiting indicator (MWI) configurations, and changes required in the telephone services configuration of Cisco Unified CME.

HTTP Server Options

Although Cisco Unity Express does support CLI configuration, most administration and management of Cisco Unity Express is accomplished via a web browser. Because Cisco Unity Express is a module inserted into a Cisco router, the router itself must have the capability to serve HTTP traffic. On a Cisco router, this capability is controlled with the ip http command. To turn on the HTTP server on a Cisco router, use the ip http server command. Once the HTTP server has been enabled, the server needs to be configured to host the proper files to the HTTP clients. The HTTP server is configured to point to the proper files using the ip http path command. Example 10.13 shows the configuration necessary to enable and configure HTTP support on a Cisco router.

Example 10.13 Enabling the HTTP Server CME# show run

! Output omitted for brevity !

ip http server ip http path flash:

In this example, the HTTP server is enabled on the Cisco router, and the files being hosted by the server are located in the router's flash memory.

When the HTTP server is enabled on a Cisco router, the authentication method uses the enable password configured on the router. An authentication, authorization, and accounting (AAA) server or a locally configured username and password should be used to provide security to the HTTP server. This can be accomplished using the ip http authentication command with either the aaa or local option. Example 10.14 shows the HTTP server using AAA authentication.

Example 10.14 HTTP Server Using AAA Authentication

! Output omitted for brevity !

ip http server ip http path flash: !

ip http authentication aaa

Dial Peers for Cisco Unity Express

A dial peer is used to route a telephony call based upon the number that is dialed. In the case of Cisco Unity Express, dial peers are used to route calls from Cisco Unified CME

to Cisco Unity Express. Example 10.15 shows the dial-peer configuration needed to route calls inbound to Cisco Unity Express.

Example 10.15 Dial Peer Configuration for Cisco Unity Express

CME# show run i

! Output omitted for brevity i

dial-peer voice 7000 voip

description VoiceMail

destination-pattern 7000

session protocol sipv2

session target ipv4:10.100.1

10

dtmf-relay sip-notify

codec g711ulaw

no vad i

dial-peer voice 7001 voip

description AutoAttendant

destination-pattern 7001

session protocol sipv2

session target ipv4:10.100.1

10

dtmf-relay sip-notify

codec g711ulaw

no vad i

dial-peer voice 7002 voip

description AVT

destination-pattern 7002

session protocol sipv2

session target ipv4:10.100.1

10

dtmf-relay sip-notify

codec g711ulaw

no vad i

Example 10.15 shows three dial peers defined. Dial peer 7000 will be used to route calls to the voice-mail application, dial peer 7001 will route calls to the auto-attendant application, and dial peer 7002 will route calls to the Administration via Telephone (AVT) application. The destination-pattern command on the dial peer defines the dialed number that this dial peer will route. For example, a dialed number of 7000 will match the statement destination-pattern 7000 in dial peer 7000 and therefore use that dial peer to route the call. Because each dial peer has a similar configuration, the dial peers can be condensed into a single dial peer using the statement destination-pattern 700[0-2]; however, defining each dial peer independently allows for more granular control over the routed calls and provides for easier troubleshooting.

Example 10.16 shows the dial-peer options that must be configured to properly route calls between Cisco Unified CME and Cisco Unity Express.

Example 10.16 Dial-Peer Options

Example 10.16 Dial-Peer Options

Key Topic

Cisco Unity Express uses the Session Initiation Protocol (SIP) to provide call control. Therefore, Cisco Unified CME must be configured to communicate with Cisco Unity Express using SIP. This is accomplished using the session protocol sipv2 command on the dial peer.

Because a dial peer is used to route calls, the dial peer must have a target destination defined to route received calls. The definition of the target is configured using the session target command. In this example, received calls on this dial peer are being routed to the version 4 IP address of 10.100.1.10, which is the IP address of the service-module. The static IP route added earlier in this chapter will route the calls to the service-engine to be passed to the service-module.

Dual-tone multifrequency (DTMF) signals are the tones that are played when a key is pressed on a traditional phone or an IP phone. Because Cisco Unified CME and Cisco Unity Express are using IP to provide signaling, and not traditional audio paths, these tones are not played as audio tones between the two systems. In order for Cisco Unified CME to instruct Cisco Unity Express that a tone was received from a caller, CME must relay the tone in a format that Cisco Unity Express can interpret. This is done using the dtmf-relay sip-notify command on the dial peer.

The codec defined on a dial peer defines what type of encoding the voice stream will use as it traverses the dial peer. Although Cisco Unified CME can support multiple codecs, currently Cisco Unity Express supports only the G.711 codec specification for all voice streams. The command codec g711ulaw is used to instruct Cisco Unified CME to use only the G.711 codec. If no codec is configured, the dial peer will default to the G.729a codec specification.

Finally, Voice Activity Detection (VAD) is a feature that allows a dial peer to stop sending IP packets when silence is detected and to begin sending IP packets once again if speech, or voice, is detected. In order for the CME dial peer to interact with Cisco Unity Express, VAD must be disabled. This is accomplished by using the no vad command on the dial peer.

The CME dial peers are now ready to route calls to Cisco Unity Express.

Telephony Service Configurations for Cisco Unity Express

As discussed in previous chapters, the telephony service configuration defines how the IP phones will interact with Cisco Unified CME. If Cisco Unity Express is integrated with Cisco Unified CME, additional changes are needed in the telephony service configuration to support the integration. Example 10.17 shows abbreviated output from a show run command listing these changes.

••■ Example 10.17 Telephony Service Configurations for Cisco Unity Express

Topic CME# show run

Output omitted for brevity telephony-service max-ephones 10 max-dn 20

ip source-address 10.100.1.1 port 2000 voicemail 7000

web admin system name cmeadmin password cisco dn-webedit time-webedit

The voicemail option under the telephony service configuration defines the number that will be dialed when an IP phone user presses the voice-mail button on their IP phone. In this example, the voice-mail pilot number is 7000, matching the voice-mail dial peer defined earlier in this chapter.

The web admin system command defines the administrative credentials that Cisco Unity Express will use to access the CME GUI. This access allows for a single administrative portal to administer both Cisco Unity Express and Cisco Unified CME. You can use the secret option in place of the password option to prevent the password from displaying in clear text when a show run command is issued.

Note Although the Cisco Unity Express GUI provides a single administrative point for both Cisco Unified CME and Cisco Unity Express, CME administration and configuration through the Cisco Unity Express GUI is beyond the scope of this book. The Cisco Unified CME GUI User Guide can be found on Cisco.com at http://www.cisco.com/en/US/docs/ voice_ip_comm/cucme/gui/user/guide/ cmegui_user.pdf.

The dn-webedit command allows the system administrator to add CME directory numbers (DN) to IP phones using the Cisco Unity Express GUI.

The "Cisco Unity Express Post-Installation Configuration" section of this chapter discussed the importance of an NTP server. Using an authoritative NTP server is strongly recommended, but in rare circumstances, time may have to be configured locally without an authoritative NTP server. In these instances, using the time-webedit command permits the system administrator to change the system time using the Cisco Unity Express GUI.

MWI Configuration

A message waiting indicator (MWI) is sent from Cisco Unity Express to Cisco Unified CME to inform CME that a new message has arrived in a subscriber's mailbox. Cisco Unity Express does this by sending a static string of unique digits to CME and then appending the extension of the subscriber's mailbox. Example 10.18 shows the MWI configuration necessary.

Example 10.18 MWI Configuration

Key Topic

CME# show run

! Output omitted for brevity ephone-dn 19 number #40 mwi on

ephone-dn 20 number #41 mwi off

As discussed in previous chapters, the ephone-dn command is used to create and customize a directory number. This is how Cisco Unified CME assigns a static string of digits to turn the MWI on or off. In this example, if Cisco Unity Express sends the digits #401000 to Cisco Unified CME, CME will match the digits to ephone-dn 19. This ephone-dn will strip the static digits #40, leaving the digits 1000, and then, because of the command mwi on, Cisco Unified CME will turn on the MWI light for extension 1000. If Cisco Unity Express sends the digits #411000 to CME, CME will match ephone-dn 20. Similarly, ephone-dn 20 will strip the static digits #41 and turn off the WMI light for extension 1000, because of the mwi off option configured on ephone-20.

Note The digits #40 and #41 can be dialed from any phone. This means that dialing #401000 from a Cisco IP phone will turn the MWI light on for extension 1000. To prevent this from occurring, a nondialable number can be used. For example, A40xxxx could be assigned to ephone-dn 19 to turn the MWI light on and A41xxxx could be assigned to ephone-dn 20 to turn the MWI light off. In this case, Cisco Unity Express would send the digits A401000 to turn on the MWI light for extension 1000, but the keypad of a Cisco IP phone cannot dial A401000.

Cisco Unity Express GUI

As mentioned earlier in this chapter, using the Cisco Unity Express GUI is the most common method of configuring and administering the Cisco Unity Express module. To access the Cisco Unity Express GUI, open Microsoft Internet Explorer version 6 or later, and point the browser to http://CUE Server, where CUE Server is either the IP address assigned to the service-module or a hostname that can be resolved to the IP address of the service-module. Figure 10.1 shows the initial login screen of the Cisco Unity Express GUI.

Unity Cisco Cli
Figure 10.1 Cisco Unity Express GUI Initial Login

Notice that the system states that only administrators can log in because the system has not yet been initialized. You must log in using the credentials configured in the postinstallation configuration tool. In this example, the username is cueadmin and the password is cisco.

The following sections discuss the final configurations necessary to import the CME settings and bring Cisco Unity Express online, and describe how to use the Cisco Unity Express CLI to verify proper configuration.

Cisco Unity Express Initialization Wizard

After you have successfully logged into the Cisco Unity Express module, you can complete the Cisco Unity Express installation process. You have the option of using the Cisco Unity Express GUI or the Cisco Unity Express CLI to complete the installation, as shown in Figure 10.2.

'Key Topic

Figure 10.2 Cisco Unity Express Initialization Wizard

'Key Topic

Figure 10.2 Cisco Unity Express Initialization Wizard

Note Although it is possible to configure Cisco Unity Express through the CLI, it is a complex process compared to the GUI option; therefore, the GUI method is recommended.

After you click the Run Initialization Wizard link, the first page of the Cisco Unity Express Initialization Wizard asks for the IP address and login credentials that Cisco Unity Express will use to access Cisco Unified CME. Note that these login credentials are not the administrative credentials configured in Cisco Unity Express, but rather the login credentials that were configured in Cisco Unified CME using the web admin system command. In the present example, the username is cmeadmin and the password is cisco. Figure 10.3 shows the login configuration needed for this example.

Figure 10.3 Cisco Unified CME IP Address and Login Credentials

Next, the Initialization Wizard lists the currently configured users in Cisco Unified CME. You can then import the desired users into Cisco Unity Express. Upon import, you can choose a primary extension for the user, create a mailbox for the user's primary extension, place the user's ID in the Cisco Unity Express administrator's group, and set the call forward busy (CFB) and call forward no answer (CFNA) treatment of the primary extension to be forwarded to the voice-mail application. Figure 10.4 shows the Import Cisco Unified CME Users page.

'Key Topic

Figure 10.4 Importing Cisco Unified CME Users

In this example, user1, user2, and user3 will be imported into Cisco Unity Express. User1's primary extension will be configured as 1000, user2's as 1001, and user3's as 1005. Each user will have a Cisco Unity Express mailbox created for their respective primary extensions, and each primary extension will be configured in Cisco Unified CME to forward all busy and unanswered calls to Cisco Unity Express. User1 will be imported as an administrator.

'Key Topic

Figure 10.4 Importing Cisco Unified CME Users

After the users have been identified, you need to define the defaults that will be used for the imported users. Figure 10.5 shows the Defaults page of the Initialization Wizard.

Key Topic

Key Topic

Figure 10.5 Imported Cisco Unified CME Users Defaults Page

In this example, all users will be configured with English as their system language. Cisco Unity Express will assign a random password and PIN for each user. Each mailbox will hold 3000 seconds of recorded voice, with a maximum message size of 60 seconds, and messages older than 30 days will be marked as expired.

Figure 10.6 shows how Cisco Unity Express will route calls.

'Key Topic

Figure 10.6 Cisco Unity Express Call Handling

'Key Topic

Figure 10.6 Cisco Unity Express Call Handling

This page mirrors the configuration performed in Cisco Unified CME to prepare for Cisco Unity Express integration. Notice that the voice-mail number, auto-attendant number, and AVT number entered on this page match the SIP dial peers created in the "Dial Peers for Cisco Unity Express" section of this chapter.

The voice-mail and auto-attendant operator extensions are the directory numbers that will ring if a caller presses the 0 key on their phone while listening to a voice-mail greeting and auto-attendant prompt, respectively. In this example, Cisco Unity Express will send a 0 digit to Cisco Unified CME if either of these conditions occurs.

During the initialization, Cisco Unity Express was able to identify the mwi on command configured on ephone-dn 19 and the mwi off command configured on ephone-dn 20. Because of this, Cisco Unity Express automatically populates the MWI fields with the correct values.

The Commit page, shown in Figure 10.7, gives you one last chance to review and change your selections before committing the configurations to memory.

Figure 10.7 Commit Page

Notice that all configuration options selected during the Initialization Wizard are listed on the Commit page. Use the Back button to change any selection, or check the Finally, Save to Startup Configuration box and click Finish to commit the selections to memory. As noted on this page, after you click Finish, all changes become permanent.

The final page lists the success or failure of each process within the Cisco Unity Express Initialization Wizard. Figure 10.8 shows that each process was successful in this example.

Key Topic

Figure 10.8 Initialization Wizard Completion Page

Key Topic

Figure 10.8 Initialization Wizard Completion Page

While configuring the imported user defaults in Figure 10.5, the Cisco Unity Express was configured to generate a random password and PIN for each imported user. This page lists the password and PIN values that were generated for each user. You can record these values and deliver them to the appropriate user.

Note In case the auto-generated password and PIN are not recorded during this step, the auto-generated value will appear on the appropriate user's configuration page within the Cisco Unity Express GUI. Once the user performs their initial login, the system forces a password and PIN change. The user-defined passwords and PINs are not displayed on the user's configuration page.

CLI Verification

Saving the configuration to startup configuration means that all selections chosen during the Initialization Wizard are written to the Cisco Unity Express CLI. Example 10.19 shows abbreviated output from a show run command in the Cisco Unity Express CLI.

Example 10.19 Cisco Unity Express CLI show run Command Output cue# show run Output omitted for brevity

Generating configuration:

username cueadmin create username userl create username user2 create username user3 create username userl phonenumber "1000"

username user2 phonenumber "1001"

username user3 phonenumber "1005"

groupname Administrators member cueadmin groupname Administrators member user1

ccn application ciscomwiapplication aa description "ciscomwiapplication" parameter "strMWI_OFF_DN" "#41" parameter "strMWI_ON_DN" "#40"

ccn subsystem sip gateway address "10.100.1.1"

ccn trigger sip phonenumber 7000 application "voicemail" maxsessions 8

ccn trigger sip phonenumber 7001 application "autoattendant" maxsessions 8

ccn trigger sip phonenumber 7002 application "promptmgmt" maxsessions 1

voicemail default mailboxsize 3000 voicemail operator telephone 0

voicemail

mailbox

owner

"userl"

size

3000

voicemail

mailbox

owner

"user2"

size

3000

voicemail

mailbox

owner

"user3"

size

cue#

Notice that the configuration entered into the Initialization Wizard is now saved as part of the Cisco Unity Express configuration.

Was this article helpful?

0 0

Responses

  • LEYTON
    Does cisco unity support multiple codecs?
    1 year ago

Post a comment