Revert Back to a Cisco CallManager SCCP Image

In order to revert the SIP phone back to a Cisco CallManager Skinny phone, edit the OS79XX.TXT file to change the file name reference back to the Cisco CallManager load ID. The next time that the phone connects to the TFTP server, it loads the CallManager load file.

Navigate to the Cisco7940/7960 SCCP software download page at the Cisco Downloads (registered customers only): click Voice Software, and then click SIP IP Phone 7940/7960. Download the latest version of the

7940/7960 software. If you convert from an early version of the 7940/7960 SIP software (3.x or earlier), try to convert to the latest version of the SCCP 4.x chain before you convert to the SCCP 5.x chain. Once you convert to the 5.x chain, you are not able to revert back to an earlier image. For more information about the difference between versions, refer to Release Notes for Cisco SIP IP Phone 7940/7960 Release 5.0.

· SIP Images 4.x/Earlier to SCCP Images 5.x/Earlier

· SIP Images 4.x/Earlier to SCCP Images 6.x/Later

· SIP Images 7.x/Later to SCCP Images 5.x

SIP Images 4.x/Earlier to SCCP Images 5.x/Earlier

If your current SIP image is 4.x or earlier, complete these steps in order to convert to the desired SCCP

images 5.x or earlier:

1. Run the executable file in order to install the SCCP software. Ensure that the new files are in your TFTP main folder.

2. Change the OS79XX.TXT file to reflect the new file name. For example, if you download version 5.0(1.1), your BIN file is P00305000101.bin. Change the text in the OS79XX.TXT file to reflect this file name, without the .bin extension.

3. Reset each phone.

Note: Ensure that all of the required Cisco CallManager files are on the TFTP server before you reboot the phones.

SIP Images 4.x/Earlier to SCCP Images 6.x/Later

If your current SIP images is 4.x or earlier, complete these steps in order to convert to the desired SCCP

images 6.x or later:

1.Complete these steps in order to convert to the 6.3 image first:

a. Copy the desired binary image from Cisco.com to the root directory of the TFTP server.

b. Open the OS79XX.TXT file with a text editor and edit the file to include the desired image.

c. Specify the desired image in the protocol configuration files.

d.Reset each phone.

The phone contacts the TFTP server and requests its configuration files. The phone compares the image that is defined in the configuration file to the image that it has stored in Flash memory. If the phone determines that the image in the configuration file differs from the image in Flash memory, it downloads the image in the configuration file (which is stored in the root directory on the TFTP server). Once the new image downloads, the phone programs that image into Flash memory and reboots.

2. Complete these steps in order to convert to the desired image:

a. Unzip the software_version.zip file to the root (top level) TFTP directory.

b. Reset the phone.

The phone contacts the TFTP server and requests its configuration files. The phone compares the image defined in the OS79XX.TXT and protocol configuration files to the image that it has stored in Flash memory. If the phone determines that the image defined in the files differs from the image in Flash memory, it downloads the image that is defined (which is stored in the root directory on the TFTP server). Once the new image downloads, the phone programs that image into Flash memory and reboots.

SIP Images 7.x/Later to SCCP Images 5.x/Later

If your current SIP image is 7.x or later, complete these steps in order to convert to the desired SCCP images 5.x or later:

In the configuration file for the protocol that the phone currently runs, change the image in the load_information parameter (SCCP) or the image_version parameter (SIP) to represent the protocol that you

want to run. For example, if the image on the phone is SIP and the image desired is SCCP, change the image_version parameter to reflect the SCCP image (P00306000200).

DHCP, TFTP, or Cisco CallManager:

· Cisco TFTP

· Configuring Windows 2000 DHCP Server for Cisco Call Manager

· Configuring Cisco CallManager 3.x with IOS MGCP Gateways (Analog FXO, FXS Ports)

Converting SCCP Phones to SIP and reverse in Cisco Unified Communication Manager 5.x and 6.x

Complete these steps in order to convert the SCCP IP Phones to SIP:

1. Go to Cisco CallManager Administration and choose Bulk Administration > Phones > Migrate Phones > SCCP to SIP.

2. Click Find after you select/enter the appropriate search criteria to list the phones that need to be migrated.

3. Click Next and choose the phone template from the drop?down.

4. Enter the job description in the Job Information area.

5. Click Run Immediately in order to migrate phone records immediately or click Run Later in order to migrate at a later time.

6. Click Submit in order to create a job for migrating the phone records.

Note: After you submit a job for migrating phones from SCCP to SIP, make sure that you reset these phones. In order to reset the phones, choose Bulk Administration > Phones > Reset/Restart Phones > Query.

7. When the Migrate job is submitted, choose Bulk Administration > Job Scheduler in order to schedule and/or activate this job. If it remains in the Pending state, you might need to activate the Bulk Provisioning Service under the Serviceability > Tools > Service Activation page. Refer to Activating Bulk Provisioning Service for

more information.

8. Go to Cisco CallManager Administration, choose System > Enterprise Parameters and change Auto Registration Phone Protocol to SIP (SCCP is the default). Then restart the Cisco CallManager service.

Note: In order to revert back to SCCP, you need to delete the SIP phone, set Auto Registration Phone

Protocol to SCCP and then let the phone re?register as SCCP.

TFTP Accessibility and Impact on Network

If you want to update only one phone in a production network, be sure to use a different TFTP server than the one that is listed on the DHCP server. If you use the listed TFTP server, you can potentially cause all phones on the network to convert to the new firmware. If you only attempt to convert one phone, use a different TFTP

server and enter the IP address of the server manually in the phone settings (Settings > Network Configuration > Alternate TFTP Server [Change to Yes] > TFTP Server [Change IP address]). Always

take great care when you upgrade phones, as changes to these configurations have the potential to bring down the entire phone system, if they are not properly implemented.

SIP Phone not Accepting SCCP Load

For SIP software version 2.1 and earlier, the phone does not accept an SCCP load whose file name is longer than eight characters. There are two options to work around this problem:

· Upgrade the SIP software to a newer version, then revert back to the SCCP software.

. Rename the SCCP load file so that it meets the 8.3 DOS standard naming convention (maximum file

name length is xxxxxxxx.yyy).

Call Handler Part1

Call Handler Settings Overview

Call handlers answer calls, greet callers with recorded prompts and provide them with information and options, route calls, and take messages. They are a basic component of Cisco Unity. Your plan for call handlers can be simple, using only the predefined Cisco Unity call handlers, or you can create an unlimited number of new call handlers. You may want to use call handlers in the following ways:

As an automated attendant—A call handler can be used in place of a human operator to answer and direct calls by playing greetings and responding to touchtones. The automated attendant can provide a menu of options (for example, “For Sales, press 1; for Service, press 2; for our business hours, press 3.”).

To offer prerecorded audiotext—A call handler can be used to provide information that customers request frequently (for example, “Our normal business hours are Monday through Friday, 8 a.m. to 5 p.m.”).

As a message recipient—A call handler can be used to take messages for the organization (for example, “All of our customer service representatives are busy. Please state your name, phone number, and account number, and we will return your call as soon as possible.”).

To transfer calls—A call handler can be used to route callers to a subscriber (for example, after hours, you could transfer calls that come to a technical support call handler directly to the cell phone of the person who is on call), or to another call handler.

To Modify a Call Handler in the Cisco Unity Administrator:-

Step 1In the Cisco Unity Administrator, go to any Call Management > Call Handlers page.

Step 2Click the Find icon.

Step 3Double-click the call handler that you want to modify.

Step 4Change settings as applicable, and then click the Save icon.

To Create a New Call Handler in the Cisco Unity Administrator:-

Step 1In the Cisco Unity Administrator, go to any Call Management > Call Handlers page.

Step 2Click the Add icon.

Step 3In the Add a Call Handler dialog box, enter information as applicable in the Name field.

Step 4Select New Handler or Based on Existing Handler. If you select Based on Existing Handler, select the applicable call handler in the Based On field.

(Note that if you based your new call handler on an existing one, you reuse all of the settings, including recorded greetings. For this reason, make sure to rerecord the greeting for the new call handler).

Step 5Click the Add button.

Step 6Enter settings for your new call handler, and then click the Save icon.

Creating and Modifying Directory Handlers:-

You can use the default pre-defined directory handler or any other existing directory handler as a template to create additional directory handlers. Create as many directory handlers as needed to route calls to subscribers by using available filters such as location, class of service, and public distribution list membership.

You can also modify or delete directory handlers; however, note that the default directory handler can be modified, but not deleted.

Subscribers can be listed in more than one directory handler.

Because directory handlers do not have greetings, use call handlers or one-key dialing to route callers to a directory handler, and use the call handler greeting to explain caller options for each directory handler.

To Create a Directory Handler:-

Step 1In the Cisco Unity Administrator, go to any Call Management > Directory Handlers page.

Step 2Click the Add icon.

Step 3In the Add a Directory Handler dialog box, enter information as applicable in the Name field.

Step 4Select New Handler or Based on Existing Handler. If you select Based on Existing Handler, select the applicable directory handler in the Based On field.

If you base a new directory handler on an existing one, all of the settings are copied except for the extension and recorded name. If you select New Handler, the new directory handler is based on the default directory handler.

Step 5Click the Add button.

Step 6Specify the settings for your new directory handler, as applicable, and then click the Save icon.

To Modify a Directory Handler:-

Step 1In the Cisco Unity Administrator, go to any Call Management > Directory Handler page.

Step 2Click the Find icon.

Step 3Double-click the directory handler that you want to modify.

Step 4Change settings as applicable, and then click the Save icon.

To Delete a Directory Handler:-

Step 1In the Cisco Unity Administrator, go to any Call Management > Directory Handler page.

Step 2Click the Find icon.

Step 3Double-click the directory handler that you want to delete.

Step 4Click the Delete icon.

Step 5On the Cisco Unity server desktop, double-click the Cisco Unity Tools Depot icon.

Step 6In the left pane, under Diagnostic Tools, double-click DbWalker.

Step 7In the Automatic Repairs tab, check the following check boxes, as applicable, to initiate repairs:

•Remove Orphaned Call Handlers

•Delete Empty Private Distribution Lists

•Set Broken User Keys to Ignore

•Remove References to Missing Greeting or Voice Name WAV Files

Step 8In the Logging pane, enter the location for the output log file.

Step 9Click Walk Database.

Step 10Click OK, then click OK again to view the output log to see the errors that were identified and what automatic repairs, if any, were made.

Step 11Click Exit.

Recording Greetings and Names:-

You can record names for subscribers, public distribution lists, private lists, and call handlers (including interview handlers and directory handlers), and greetings for subscribers and call handlers, by using a Media Master control bar on the pages within the Cisco Unity Administrator. In addition, in circumstances when you cannot access the Cisco Unity Administrator, you can access the Cisco Unity Greetings Administrator from any phone to manage greetings for call handlers.

Before you begin recording subscriber and call handler names and greetings, consider the following:

Who will record the greetings? For example, do you want to hire a professional to record the call handler greetings?

What will the greetings say? Write detailed scripts for the greetings before beginning to record.

(Note that subscribers can record their own names and personal greetings by accessing the Cisco Unity conversation by phone, or by using a Media Master on the pages within the Cisco Unity Assistant).

Using the Media Master to Record Greetings and Names:-

The Media Master control bar appears on each page of the Cisco Unity Administrator on which recordings can be made.It allows you to make and play recordings, either with a phone or with your computer microphone and speakers, by clicking the Media Master controls.

The Media Master control bar relies on DCOM (Distributed Component Object Model), and does not work through a firewall that blocks DCOM communications. It also requires that your browser is able to download and run ActiveX controls.

Media Master Control Bar

<!–[if mso & !supportInlineShapes & supportFields]> SHAPE * MERGEFORMAT <![endif]–><!–[if mso & !supportInlineShapes & supportFields]> <![endif]–>

Media Master Control Bar Options Menu

Option

Meaning

New

Use this option to start a new recording.

Paste

Paste a copied recording of a voice message, name, or greeting into this recording.

Paste from file

Paste a WAV file that you have stored on your computer into this recording. Note that when you do, the file is converted (if applicable) and saved on the Cisco Unity server in the G711 format—even when this is not the recording and storage codec specified for the Cisco Unity server.

(For consistent sound quality, the codec format of all greetings and recorded names should match the message recording and storage codec being used by Cisco Unity. You can view the codec format of greetings and recorded names by using the Codec Checker utility. You change the codec format for greetings and recorded names by using the Set WAV Format utility. Both utilities are available in the Cisco Unity Tools Depot.)

Copy

Copy this recording so that you can paste it into another voice message, name, or greeting recording.

Copy to file

Save this recording as a WAV file to a location that you specify.

Playback devices

Select the phone or the multimedia speakers used with your computer. If you select the phone, you must click Options on the Media Master Control Bar Options menu and enter an extension and server name.

Recording devices

Select the phone or the multimedia microphone used with your computer. Note that if you select the phone, you must click Options on the Media Master Control Bar Options menu and enter an extension and server name.

Options

Enter an extension and the Cisco Unity server name here when you want to use the phone as the playback and recording device for the Media Master.

Selecting a Recording and Playback Device:-

Step 1Go to any Media Master control bar in the Cisco Unity Administrator.

Step 2From the Options menu, click Playback Devices. (The Options menu button is on the far left of the Media Master control bar.)

Step 3Select the device that you want to use from the list.

The <Use Preferred Device> option refers to the recording and playback devices that you have already selected for your computer (click Settings > Control Panel > Sounds and Multimedia on the Windows Start menu to set your preferred devices). See the Windows Help for more information on preferred recording and playback devices.

Step 4From the Options menu, click Recording Devices, and repeat Step 3.

To Use the Cisco Unity Greetings Administrator to Manage Call Handler Greetings:-

Step 1 On the phone, dial the phone number for access to the Cisco Unity Greetings Administrator.

Step 2 At the prompt, enter the ID of the call handler owner, and press #.

Step 3 At the prompt, enter the password of the call handler owner, and press #.

Step 4 At the prompt, enter the extension of the call handler.

Step 5 Follow the Cisco Unity conversation to toggle between the alternate and standard call handler greetings,or to record the call handler greeting.

Toggle between greetings Press 1.

Record the greeting Press 2.

Changing Call Transfer Options:-

This section contains two procedures. Do the applicable procedure to change your call transfer settings by phone (when using standard or Optional conversation 1 styles) or from the Cisco Unity Assistant.

To Change Call Transfer Settings by Phone (Standard and Optional Conversation 1 Styles):-

Step 1Log on to Cisco Unity.

Step 2Press 4 4.

Step 3After Cisco Unity announces your current call transfer settings, use the following keys to change them.

Key

Task

1

Switch between transferring calls to a phone and to voice mail.

2

Change your transfer phone number. To transfer calls to an external phone number, contact your Cisco Unity administrator.

(NoteSimply changing your transfer number does not change whether calls are transferred to a phone or sent to voice mail. Cisco Unity transfers calls to your transfer number only if you also specify that Cisco Unity transfers your calls to a phone.)

Key

Task

Key

Task

*

Cancel or back up

0

Help

To Change Call Transfer Settings from the Cisco Unity Assistant:-

Step 1In the Cisco Unity Assistant, on the Preferences menu, click Transfer and Screening.

Step 2In the Transfer Calls To field, choose whether to transfer calls to your extension, or another number, or transfer calls directly to voice mail:

To transfer calls to your extension, click Extension <Your Extension>.

To transfer calls to another number, click the radio button for the unlabeled box, then enter a transfer number. (To transfer calls to an external phone number, such as a home or cell phone, contact your Cisco Unity administrator.)

To transfer calls directly to voice mail, click My Personal Greeting.

(NoteAs a convenience, you can edit the transfer number in the unlabeled box even when you have specified that Cisco Unity transfers calls to your extension or sent to voice mail. Cisco Unity will transfer calls to the number in the box only if you also click the radio button adjacent to it).

Step 3If you choose to transfer calls to your extension, in the If My Extension Is Busy list, choose how you want Cisco Unity to handle calls when your phone is busy.

Step 4Click Save.

Changing Caller Message Options:-

Caller message options allow you to choose what callers can do when they leave messages for you. Cisco Unity provides the following options:

You can change your caller message options only from the Cisco Unity Assistant, not by phone.

Callers Can Edit the Message

Cisco Unity gives callers the options of listening to, adding to, rerecording, or deleting their messages.

Callers Can Mark the Message as Urgent

Cisco Unity asks callers if they want to mark their messages urgent.

To Change Caller Message Options:-

Step 1In the Cisco Unity Assistant, on the Preferences menu, click Transfer and Screening.

Step 2Check or uncheck one or both of the Listen To And Re-Record The Message and Mark The Message As Urgent check boxes.

Step 3Click Save.

Call Handler Part2

To Create a New Call Handler in the Cisco Unity Administrator:-

Step 1 In the Cisco Unity Administrator, go to any Call Management > Call Handlers page.

Step 2 Click the Add icon.

Step 3 In the Add a Call Handler dialog box, enter information as applicable in the Name field.

Step 4 Select New Handler or Based on Existing Handler. If you select Based on Existing Handler, select the applicable call handler in the Based On field.

Note that if you based your new call handler on an existing one, you reuse all of the settings, including recorded greetings. For this reason, make sure to rerecord the greeting for the new call handler.

Step 5 Click the Add button.

Step 6 Enter settings for your new call handler, and then click the Save icon.

To Modify a Call Handler in the Cisco Unity Administrator:-

Step 1 In the Cisco Unity Administrator, go to any Call Management > Call Handlers page.

Step 2 Click the Find icon.

Step 3 Double-click the call handler that you want to modify.

Step 4 Change settings as applicable, and then click the Save icon.

To Add a Routing Rule to Forward Calls to the Cisco Unity Greetings Administrator:-

Step 1 In the Cisco Unity Administrator, go to the Call Management > Call Routing > Direct Calls page.

Step 2 Click the Add icon.

Step 3 In the Add a Call Routing Rule – Direct dialog box, enter a name for the new routing rule, and click Add.

Step 4 In the Status field, confirm that Enabled is selected.

Step 5 In the Dialed Number field, enter the phone number that is set up for the system administrator to dial for changing call handler greetings by phone.

Step 6 In the Send Call To field, click Greetings Administrator.

Step 7 Change other fields for the routing rule as needed.

Step 8 In the routing table at the bottom of the page, confirm that the new routing rule is in an appropriate position with the other routing rules.

To change the order of the routing rules, click Change Rule Order.

Step 9 Click the Save icon.

To Assign a Unique Extension to the Call Handler:-

Step 1 In the Cisco Unity Administrator, go to the Call Management > Call Handlers > Profile page.

Step 2 Click the Find icon, and in the Select and View dialog box, click Find. A list of call handlers appears.

Step 3 Click the call handler that you want to access by using the Cisco Unity Greetings Administrator and click View.

Step 4 In the Extension field, enter the unique extension you want to assign to the call handler.

Step 5 Click the Save icon.

Call Handler Profile Settings:-

Call Management > Call Handlers > Profile Page

Name :This displays the name of the call handler. To change the name of the call handler, enter a new name here, and then click the Save icon.

Created :Display only. This setting shows the date and time that the call handler was created.

Owner :To change the owner, select an Owner Type and click Change. The owner can be any subscriber or public distribution list. The owner of the call handler can record and change the call handler greeting over the phone. Note that the owner is not necessarily the message recipient.

Owner Type :Click Subscriber to assign ownership to a single subscriber. Click Public Distribution List to assign ownership to all subscribers on a public distribution list.

Default: Subscriber.

Recorded Voice :This is the recorded name of the call handler. To record a call handler name, use the Media Master control bar. Use the Paste From File option on the Options menu of the Media Master control bar to use a prerecorded WAV file as the recording. Note that the Media Master is not available across a firewall that blocks DCOM communications.

Active Schedule :Select the schedule to determine the times that standard and closed transfer rules and greetings are in effect for the call handler. To view details of the selected schedule, click the View link. Note that when you click the link, you leave this page and move to the System > Schedules page.

Default: Weekdays.

Extension :Enter the extension, if any, that callers dial to reach the call handler. Assign an extension only if you plan to allow callers to dial the number.

When the call handler is reached only from one-key caller input, do not enter an extension here.

Note that this extension is not the same as the extension to which calls are transferred. The extension to which calls are transferred is set on the Call Management > Call Handlers > Call Transfer page.

Default: Blank.

Language:Select the language in which Cisco Unity plays the handler system prompts. If you choose Inherited, Cisco Unity determines the language to use for system prompts on a per-call basis, depending on the handler or routing rule that processed the call. If the language is set to Inherited for every rule and handler that processes a call, then the system prompts are played in the default phone language.

The default phone language and the list of languages shown here are set on the System > Configuration > Phone Languages page.

Default: Inherited.

Switch:(for dual phone system integrations only) Select the phone system that the call handler uses. If this setting is incorrect, Cisco Unity will not be able to transfer calls to or from the call handler.

Call Handler Transfer Settings:

Call Management > Call Handlers > Call Transfer Page

Transfer Rule Applies To :The settings on the rest of the page apply to the transfer rule selected here: either standard, closed, or alternate.

The schedule that is used to determine the times that standard and closed transfer rules and greetings are in effect is set on the Profile page for the call handler. When enabled, the alternate transfer rule overrides the standard and closed transfer rules and is in effect at all times.

Status:Select one of the following settings:

· Enabled—The transfer rule is active and Cisco Unity directs callers as defined by the settings within this rule.

· Disabled—The transfer rule is inactive and Cisco Unity ignores all settings within this rule.

When Transfer Rule Applies To is set to Standard, this setting is automatically set to Enabled, and it cannot be changed.

Default: Enabled.

Transfer Incoming Calls:Select one of the following settings:

· No (Send Directly)—Cisco Unity transfers the call to the call handler greeting.

· Yes, Ring the Recipient—Cisco Unity transfers calls to the extension assigned to the message recipient. Cisco Unity displays the name and extension in the adjacent box. The message recipient is set on the Messages page of the call handler.

· Yes, Ring Subscriber—Cisco Unity transfers calls to the number entered in the adjacent box. The number can be an extension or any phone number. Use digits 0 through 9, *, and #. You can also enter , (comma) to insert a one-second pause. When a SIP phone system is integrated with Cisco Unity and the transfer type is Release to Switch, using a comma to insert a pause will not work.

Default: No (Send Directly).

Transfer Type:Select how Cisco Unity transfers calls:

· Release to Switch—Cisco Unity puts the caller on hold, dials the extension, and releases the call to the phone system. When the line is busy or is not answered, the phone system—not Cisco Unity—forwards the call to the subscriber or handler greeting. This transfer type allows Cisco Unity to process incoming calls more quickly. Use Release to Switch only when call forwarding is enabled on the phone system.

· Supervise Transfer—Cisco Unity acts as a receptionist, handling the transfer. If the line is busy or the call is not answered, Cisco Unity—not the phone system—forwards the call to the subscriber or handler greeting. You can use supervised transfer whether or not the phone system forwards calls.

The Transfer Type option is unavailable when Transfer Incoming Calls is set to the No (Send Directly) option.

Default: Release to Switch.

Rings to Wait For:Select the number of times the extension rings before Cisco Unity plays the subscriber or handler greeting.

Set this value to at least 2 to give subscribers a chance to answer. Avoid setting to more than 4, especially if the call may be transferred to another extension, where the caller might have to wait for another set of rings. This value should be at least two rings fewer than the phone system setting for forwarding calls.

This option is unavailable when Release to Switch is selected or when Transfer Incoming Calls is set to the No (Send Directly) option.

Default: Two rings.

If the Call Is Busy:Select the action that Cisco Unity performs when the subscriber phone is busy. You may want to use holding options sparingly, because having calls on hold can tie up ports.

· Always Hold—Cisco Unity plays a prompt indicating that the extension is busy. The caller is put on hold. Note that this hold is not performed by the phone system.

· No Holding—Cisco Unity prompts the caller to leave a message and allows the caller to dial another extension.

· Ask Caller—Cisco Unity gives the caller the options of holding, leaving a message, or dialing another extension.

These options are unavailable when Release to Switch is selected or when Transfer Incoming Calls is set to the No (Send Directly) option.

Default: No Holding.

Announce:Check this check box to have Cisco Unity say “transferring call” when the subscriber answers the phone.

This option is unavailable when Release to Switch is selected or when Transfer Incoming Calls is set to the No (Send Directly) option.

Default: Check box not checked.

Introduce (Call for Name):Check this check box to have Cisco Unity say “call for <recorded name of the call handler>” when the subscriber answers the phone. Use this setting if the subscriber who is the message recipient takes calls for more than one dialed extension. The introduction alerts the subscriber who answers that the call is for the call handler.

This option is unavailable when Release to Switch is checked or when Transfer Incoming Calls is set to No (Send Directly).

Default: Check box not checked.

Confirm (Call Can Be Accepted or Refused):Check this check box to have Cisco Unity prompt the subscriber to accept or refuse a call. If the call is accepted, it is transferred to the subscriber phone. If the call is refused, Cisco Unity plays the applicable subscriber greeting. You use this setting with the Ask Caller’s Name setting to allow the subscriber to screen calls.

This option is unavailable when Release to Switch is selected or when Transfer Incoming Calls is set to the No (Send Directly) option.

Default: Check box not checked.

Ask Caller’s Name:Check this check box to have Cisco Unity prompt callers to say their names. When the phone is answered, the subscriber hears “Call from…” before Cisco Unity transfers the call. You use this setting with the Confirm setting to allow the subscriber to screen calls.

This option is unavailable when Release to Switch is selected or when Transfer Incoming Calls is set to the No (Send Directly) option.

Default: Check box not checked.

Call Handler Greetings Settings:-

Call Management > Call Handlers > Greetings Page

After Greeting:Indicate the action that Cisco Unity performs after the greeting plays:

· Take Message—Cisco Unity records a message from the caller. Click the Take Message link to view the Messages page.

· Say Good-Bye—Cisco Unity plays a brief goodbye, and the call is disconnected. Click the Say Good-Bye link to view the Goodbye call handler.

· Send Caller To—Cisco Unity sends the call to the destination that you select:

· Broadcast Message Administrator—Sends the call to a conversation for sending broadcast messages.

· Caller System Transfer—Sends the call to a conversation that allows callers to transfer to a number that they specify. For example, callers may want to dial a lobby or conference room phone that is not associated with a Cisco Unity subscriber. Cisco Unity performs the transfer only when the CS_Default_System_Transfer restriction table permits it.

· Call Handler—Sends the call to the call handler that you select.

· Directory Handler—Sends the call to directory assistance.

· Greetings Administrator—Sends the call to a conversation for changing call handler greetings over the phone.

· Hang Up—Disconnects the call. Use carefully; unexpected hang-ups can appear rude to callers.

· Hotel Checked Out—When the Cisco Unity Hospitality and Property Management Integration has been installed, this option sends the call to a conversation that allows hotel guests to access archived messages after they have checked out.

· Interview Handler—Sends the call to the interview handler that you select.

· Sign-In—Sends the call to the subscriber logon conversation, which prompts subscribers to enter their ID and their password.

· Subscriber—Sends the call to the subscriber that you select.

· Subscriber System Transfer—Sends the call to a conversation that allows subscribers to transfer to a number that they specify. Subscribers are prompted to log on and then can enter numbers that are not associated with Cisco Unity subscribers—such as lobby and conference room phones, and even phone numbers outside the organization. Cisco Unity performs the transfer only when the subscriber restriction table permits it.

Default: Send Caller to Hang Up.

Reprompt the User After this Many Seconds of Silence:Check this check box and enter a value in the field on the right to indicate the number of seconds of silence to allow. When Cisco Unity receives no input from a caller within this number of seconds, Cisco Unity prompts the caller again.

Default: Two seconds; check box is unchecked.

Number of Times to Reprompt:

Indicate the number of times to reprompt a caller. After the number of times indicated here, Cisco Unity performs the after-greeting action.

Default: One time.

Call Handler Messages Settings:-

Call Management > Call Handlers > Messages Page

Message Recipient:Select the subscriber or public distribution list that receives messages left for this call handler. Select a recipient type from the list, then click Select.

When you select a public distribution list, each member of the list receives the call handler messages.

Default: A selected subscriber.

Maximum Message Length in Seconds:Set the recording length allowed for messages left by unidentified callers. Recipients may want to limit the length of messages from unidentified callers. Some departments, such as Customer Service, may want to permit much longer messages. If enabled, a warning tone will sound before the maximum message length is reached.

Default: 300 seconds.

After Message Action:Indicate the action that Cisco Unity performs after an unidentified caller leaves a message:

· Say Good-bye—Cisco Unity plays a brief goodbye, and the call is disconnected. Click the Say Good-bye link to view the Goodbye call handler.

· Send Caller To—Cisco Unity sends the call to the destination that you select:

· Broadcast Message Administrator—Sends the call to a conversation for sending broadcast messages.

· Caller System Transfer—Sends the call to a conversation that allows callers to transfer to a number that they specify. For example, callers may want to dial a lobby or conference room phone that is not associated with a Cisco Unity subscriber. Cisco Unity performs the transfer only when the CS_Default_System_Transfer restriction table permits it.

· Call Handler—Sends the call to the call handler that you select.

· Directory Handler—Sends the call to directory assistance.

· Greetings Administrator—Sends the call to a conversation for changing call handler greetings over the phone.

· Hang Up—Disconnects the call. Use carefully; unexpected hang-ups can appear rude to callers.

· Hotel Checked Out—When the Cisco Unity Hospitality and Property Management Integration has been installed, this option sends the call to a conversation that allows hotel guests to access archived messages after they have checked out.

· Interview Handler—Sends the call to the interview handler that you select.

· Sign-In—Sends the call to the subscriber logon conversation, which prompts subscribers to enter their ID and their password.

· Subscriber—Sends the call to the subscriber that you select.

· Subscriber System Transfer—Sends the call to a conversation that allows subscribers to transfer to a number that they specify. Subscribers are prompted to log on and then can enter numbers that are not associated with Cisco Unity subscribers—such as lobby and conference room phones, and even phone numbers outside the organization. Cisco Unity performs the transfer only when the subscriber restriction table permits it.

Default: Hang Up.

Callers Can Edit Messages:Check this check box to allow callers to be prompted to listen to, add to, rerecord, or delete their messages. Balance giving callers the additional control of editing messages with having voice messaging ports tied up for the additional time.

Default: Check box checked.

Mark Messages as Urgent: Indicate the action that Cisco Unity will allow:

· Always—All messages left by unidentified callers are marked urgent. This may be useful for Sales or Technical Support call handlers.

· Never—Messages left by unidentified calls are never marked urgent.

· Ask Caller for Their Preference—Cisco Unity asks unidentified callers whether to mark their messages urgent.

Cisco Unity plays new urgent messages before other messages.

Default: Never.

Routing Callers by Using One-Key Dialing :-

With one-key dialing, you can offer callers a menu of choices. One-key dialing enables you to designate a single digit to represent a subscriber extension, call handler, interview handler, or directory handler. Instead of entering the full extension, the caller presses a single key.

Callers can bypass one-key dialing. You set the system to pause a certain number of seconds for additional key presses before routing the call according to the way you have set up a one-key dialing menu. These pauses allow callers to press full extension IDs to bypass one-key dialing menus, even during the handler greeting.

You can also lock certain keys to take the caller directly to the action programmed for that key without waiting for an additional key press.

Use the handler greeting to tell callers about the one-key options they have, and whether they are allowed to enter an extension during the greeting.

Creating a Call Management Map :-

When you have considered how your call management plan ought to work, you can create a sketch that shows specifically how the handlers connect to one another. Include a menu of one-key dialing options and all possible navigation choices (such as reaching a call handler by dialing an extension or via a routing rule). You can also include the predefined Cisco Unity call handlers in your plan. See Figure 18-1 for a sample call management map that makes use of the automated attendant.

Figure 18-1 Sample Automated Attend ant Call Management Map

Creating and Modifying Call Routing Rules

Although you cannot modify the predefined routing rules in the Direct Calls and Forwarded Calls call routing tables, you can create additional call routing rules for each call routing table and modify them as needed.

To Create a Call Routing Rule

Step 1 In the Cisco Unity Administrator, for direct calls, go to the Call Management > Call Routing > Direct Calls page. For forwarded calls, go to the Call Management > Call Routing > Forwarded Calls page.

Step 2 Click the Add icon.

Step 3 In the Add a Call Routing Rule dialog box, enter the name of the new rule in the Name field.

Step 4 Click the Add button.

Step 5 Specify the settings for the new call routing rule, as applicable, and then click the Save icon

To Modify a Call Routing Rule

Step 1 In the Cisco Unity Administrator, for direct calls, go to the Call Management > Call Routing > Direct Calls page. For forwarded calls, go to the Call Management > Call Routing > Forwarded Calls page.

Step 2 In the routing table, click the rule that you want to modify.

Step 3 Change settings as applicable in the fields above the table, and then click the Save icon.

Direct Calls and Forwarded Calls Routing Table Settings:-

Call Management > Call Routing > Direct Calls and Forwarded Calls Pages

Rule Name: Enter a rule name. Rule names can be words or numbers. You might want the name to reflect the purpose of the rule (for example, “Sales menu”).

Status :Select one of the following settings:

· Enabled—The routing rule is active and Cisco Unity will acknowledge all settings.

· Disabled—The routing rule is inactive and Cisco Unity ignores all settings within the rule.

Default: Enabled.

Call Type :Click the applicable Call Type, either Internal Calls or External Calls. To have the rule apply to all call types, click Both. Internal calls are from subscribers, and external calls are from unidentified callers.

When a call matches all settings for the rule, the call is routed as specified in Send Call To.

Your integration may not support this option.

Default: Both.

Ports (Direct Calls page only) :Enter the port number to have the rule apply to the port on which a call arrives. To set a consecutive range of ports, enter a hyphen between the port numbers (for example, 1-4). To set a list of ports, enter a comma between the ports (for example, 1,2,4). To have the rule apply to calls on all ports, enter * or leave the box blank.

When a call matches all settings for the rule, the call is routed as specified in Send Call To.

Default: Blank.

Trunks (Direct Calls page only) Enter the trunk number to have the rule apply to the trunk on which a call arrives. To set a consecutive range of trunks, enter a hyphen between the trunk numbers (for example, 1-4). To set a list of trunks, enter a comma between the trunk numbers (for example, 1,2,4). To have the rule apply to calls on all trunks, enter * or leave the box blank.

When a call matches all settings for the rule, the call is routed as specified in Send Call To.

Your integration may not support this option.

Default: Blank.

Forwarding Station (Forwarded Calls page only) Enter the extension (station) to have the rule apply to the extension from which a call was forwarded. To have the rule apply to all extensions, enter * or leave the field blank. The * is a wildcard and can be used alone or with other numbers (for example, enter 2* to route all calls from any extension that begins with 2).

When a call matches all settings for the rule, the call is routed as specified in Send Call To.

Your integration may not support this option.

Default: Blank.

Dialed Number (DNIS) :Enter the phone number to have the rule apply to a number that callers dial to reach your organization. To have the rule apply to all numbers dialed, enter * or leave the box blank. The * is a wildcard and can be used alone or with other numbers (for example, enter 800* to control routing of all calls to 800 numbers).

When a call matches all settings for the rule, the call is routed as specified in Send Call To.

Your integration may not support this option.

Default: Blank.

Calling Number (ANI) :Enter the phone number to have the rule apply to a phone number from which calls originate. To have the rule apply to all originating phone numbers, enter * or leave the box blank. The * is a wildcard and can be used alone or with other numbers (for example, enter 212* to control routing of all calls from that area code).

When a call matches all settings for the rule, the call is routed as specified in Send Call To.

Your integration may not support this option.

Default: Blank.

Schedule :Select a schedule to apply to this call routing rule. When a call arrives during the standard (open) hours of the selected schedule, and the call matches all other settings for the rule, the call is routed as specified in Send Call To.

To have the rule apply 24 hours a day, seven days a week, click Always.

To have different rules for standard and closed hours, create a rule with a selected schedule, followed by a rule set with Always.

Default: Always.

Language :Select the language to be associated with the call. If you choose Inherited, Cisco Unity determines the language to use on a per-call basis, depending on the handler or routing rule that processed the call. If the language is set to Inherited for every rule and handler that processes a call, then the system prompts are played in the default phone language.

If your organization has purchased additional language licenses, routing rules can also be used to change the language in which Cisco Unity plays system prompts to callers. For example, you could route calls and set the language for the system prompts based on the dialed number, so that different callers can hear identical information but in different languages.

The list of languages shown here is set on the System > Configuration > Phone Languages page.

Default: Inherited.

Send Call To :Select one of the following destinations for a call that matches all settings for the rule:

· Attempt Forward—Forwards the call if the forwarding station belongs to a subscriber. The calling number is used as the ID, and if the extension is found, the call is forwarded to the subscriber greeting. If the extension is not found, the next rule in the routing table is applied to the call information.

· Attempt Sign-In—Sends the call to the subscriber logon conversation, if the calling number belongs to a subscriber. The calling number is used as the ID. If the call is not from a subscriber, the next rule in the routing table is applied to the call information.

· Broadcast Message Administrator—Sends the call to a conversation for sending broadcast messages.

· Call Handler—Sends the call to the call handler that you select.

· Caller System Transfer—Sends the call to a conversation that allows callers to transfer to a number that they specify. For example, callers may want to dial a lobby or conference room phone that is not associated with a Cisco Unity subscriber. Cisco Unity performs the transfer only when the CS_Default_System_Transfer restriction table permits it.

· Directory Handler—Sends the call to the directory handler that you select.

· Greetings Administrator—Sends the call to a conversation for changing call handler greetings over the phone.

· Hotel Checked Out—When the Cisco Unity Hospitality and Property Management Integration has been installed, this option sends the call to a conversation that allows hotel guests to access archived messages after they have checked out.

· Interview Handler—Sends the call to the interview handler that you select.

· Sign-In—Sends the call to the subscriber logon conversation, which prompts the caller to enter an ID.

· Subscriber—Sends the call to the subscriber that you select.

· Subscriber System Transfer—Sends the call to a conversation that allows subscribers to transfer to a number that they specify. Subscribers are prompted to log on and then can enter numbers that are not associated with Cisco Unity subscribers—such as lobby and conference room phones, and even phone numbers outside the organization. Cisco Unity performs the transfer only when the subscriber restriction table permits it.

Defaults: Attempt Forward for Forwarded Calls, Directory Handler for Direct Calls.

Routing Table :Display only. This setting shows the call routing rules for direct calls or for forwarded calls. The order of the rules is important. Cisco Unity compares a call to each rule in the order specified in the table from the top down until it finds a match. The first rule that matches a call determines where the call is routed.

Installing Cisco Secure ACS for Windows

Understanding Your ACS System:

You can use ACS network security software to authenticate users by controlling access to an Authentication, Authorization, and Accounting (AAA) client—any one of many network devices that you can configure to defer authentication and authorization of network users to a AAA server. ACS operates as a set of Windows-based services that controls the authentication, authorization, and accounting of user access to networks.

ACS operates on Windows 2000 server and Windows 2003 server. ACS can run on a domain controller or a member server

Preparing to Install(System Requirements):

Hardware

Operating System

File System

Memory

Virtual Memory

Hard Drive Space

Third Party Software Requirements:

Web browsers and Java virtual machines

Novell Directory Server (NDS) clients

Token-card clients

Network and Port Requirements:

RADIUS authentication and authorization UDP 1645, 1812

RADIUS accounting UDP 1646, 1813

TACACS+ TCP 49

Cisco Secure Database Replication TCP 2000

RDBMS Synchronization with synchronization partners TCP 2000

User-Changeable Password web application TCP 2000

Logging TCP 2001

Administrative HTTP port for new sessions TCP 2002

Administrative HTTP port range TCP 1024 ,65535

Backing Up Data Before Installation:

Before you install or upgrade ACS, we strongly recommend that you back up the computer on which you install ACS by using a Windows backup utility of your choice. Include the Windows registry in the backup.

If you are upgrading or reinstalling ACS, use the ACS Backup feature to back up the ACS configuration and database, and then copy the backup file to a drive that is not local to the computer on which ACS is running

Disabling NetBIOS:

Since the evolution of Windows 2000, Domain Name Service (DNS) has become the default name-resolution method for windows-based networking. Although Windows 2000, Windows XP, and Windows Server 2003 provide the option of disabling NetBIOS over TCP/IP, many corporate networks are reluctant to do so because they still use legacy machines on their networks. ACS4.2 supports the Windows server with NetBIOS disabled. You must disable NetBT in Windows.

Installation and Upgrade Scenarios:

ACS for Windows supports the following upgrade scenarios:

•ACS 3.x to ACS 3.3.x—You can upgrade ACS 3.2.x or 3.3.x (ACS 3.2.1, 3.2.2, 3.2.3, 3.3.1, 3.3.2) to ACS 3.3.3 or 3.3.4 on Windows.

•ACS 3.3.3 to 3.3.4— You can upgrade ACS 3.3.3 to ACS 3.3.4 on Windowss.

•ACS 3.3.x to ACS 4.1.1.23 or ACS 4.1.1.24— You can upgrade from ACS 3.3.x (ACS 3.2.1, 3.2.2, 3.2.3, 3.3.1, 3.3.2, or 3.3.4) to ACS 4.1.1.23 or ACS 4.1.1.24 on Windows.

•ACS 4.0 to ACS 4.1.1.23 or ACS 4.1.1.24— You can upgrade from ACS 4.0 to ACS 4.1.1.23 or ACS 4.1.1.24 on Windows.

•ACS 4.1.1.23 or ACS 4.1.1.24 to ACS 4.1.3 or ACS 4.1.4— You can upgrade from ACS 4.1.1.23, 4.1.1.24, to ACS 4.1.3 or 4.1.4 on Windows.

•ACS 4.1 to ACS 4.2— You can upgrade from ACS 4.1.1.23, 4.1.1.24, 4.1.2, 4.1.3 or 4.1.4 to ACS 4.2 on Windows.

Installing Cisco Secure ACS for Windows:

Step 1Using a local administrator account, log in to the computer on which you want to install ACS.

Step 2Insert the ACS CD into a CD-ROM drive on the computer.

If the computer does not have the minimum system requirements, a dialog box appears. You can apply these requirements before or after installing ACS. You can continue with the installation, but you must apply the minimum requirements after the installation is complete; otherwise, ACS may not function reliably.

If the CD-ROM drive supports the Windows autorun feature, the ACS for Windows dialog box appears; otherwise, run Setup.exe, which resides in the root directory of the ACS CD.

Step 3In the Cisco Secure ACS for Windows dialog box, click Install.

If the computer does not have a required service pack installed, a dialog box appears. You can apply Windows service packs before or after installing ACS. You can continue with the installation, but you must install the required service pack after the installation is complete; otherwise, ACS may not function reliably.

The Cisco Secure ACS v4.2 Setup dialog box displays the software license agreement.

Step 4If you read and accept the software license agreement, click ACCEPT.

The Welcome dialog box displays information about the setup program.

Step 5Read the information in the Welcome dialog box and click Next.

The IMPORTANT NOTICE dialog box displays information about the processes running on your computer which may affect some ACS operations.

Step 6Read the information in the IMPORTANT NOTICE dialog box and click Next.

The Before You Begin dialog box appears.

Step 7Once you complete the items in the Before You Begin dialog box, check the corresponding check box for each item, and then click Next. For more information about these items, see Gathering Answers for the Installation Questions.

If you did not complete all items in the Before You Begin dialog box, click Cancel, and then click Exit Setup. After completing all items in the Before You Begin dialog box, restart the installation. For more information, see Preparing to Install or Upgrade ACS.

After you click Next, the Choose Destination Location dialog box appears.

Step 8To change the installation location, enter the new path name or click the Browse button to choose the drive and path where the setup program installs ACS.

The installation must reside on a drive that is local to the computer. If you specified a folder that does not exist, click Yes to confirm the creation of the folder.

Step 9Click Next.

The Authentication Database Configuration dialog box appears.

Step 10Choose an option. To authenticate users with:

The ACS internal database only, check Check the ACS Internal database only.

A Windows Security Access Manager (SAM) user database or AD user database in addition to the ACS internal database, check Also check the Windows User Database.

The Yes, refer to “Grant dial-in permission to user” check box is enabled when you select the Also check the Windows User Database option. This option applies to all forms of access that ACS controls; not just dial-in access. For example, a user who accesses your network through a VPN tunnel is not dialing in to a network access server; however, if you check Yes, refer to “Grant dial-in permission to user” check box, ACS applies the Windows user dial-in permissions to determine whether to grant the user access to your network.

If you want to grant access to users who are authenticated by a Windows domain user database only when they have dial-in permission in their Windows account, check Yes, refer to “Grant dial-in permission to user” check box.

Step 11Click Next.

The setup program installs ACS and updates its configuration.

The Advanced Options dialog box appears.

Step 12Choose the features that you want to enable.

These features are not enabled by default; they appear in the ACS web interface

only if you enable them. To view the web interface:

In the navigation bar, click Interface Configuration.

Click Advanced Options.

The web interface appears.

Step 13Click Next.

The Active Service Monitoring dialog box appears.

Step 14Choose service monitoring features:

If you want ACS to monitor user authentication services, check Enable Login Monitoring. From the Script to execute list, choose the option that you want applied in the event of authentication service failure. The options are:

–No Remedial Action—ACS does not run a script. This option is useful if you enable event e-mail notifications.

–Reboot—ACS runs a script that reboots the computer that runs ACS.

–Restart All—ACS restarts all ACS services.

–Restart RADIUS/TACACS+—ACS restarts only the RADIUS and TACACS+ services.

If you want ACS to send an e-mail message when service monitoring detects an event, check the Enable Mail Notifications checkbox. The SMTP mail server and Mail account to notify fields are enabled. You must enter the following information:

–SMTP mail server – Name and domain of the mail server that is sending the notification.

–Mail account to notify- The e-mail address of the intended recipient.

Step 15Click Next.

The Cisco Secure ACS Service Initiation dialog box appears.

Step 16You must enter a password and for database encryption. The password should be at least 8 characters long and should contain characters and numbers. There are no invalid characters.

The Database Encryption Password is encrypted and stored in the ACS registry. You might have to reuse this password when critical problems arise and you have to access the database manually. Keep this password in a safe, accessible place so that technical support can gain access to the database.

Step 17Click Next.

The setup program ends and the Cisco Secure ACS Service Initiation dialog box appears.

Step 18For each option that you require, check the corresponding check box. The actions that are associated with the options occur after the setup program ends. The check boxes are:

•Yes, I want to start the Cisco Secure ACS Service now—Starts the Windows services that ACS comprises. If you do not check this check box, the ACS web interface is not available; unless you reboot the computer or start the CSAdmin service.

•Yes, I want Setup to launch the Cisco Secure ACS Administrator from my browser following installation—Opens the ACS web interface in the default web browser for the current Windows user account.

•Yes, I want to view the Readme file—Opens README.TXT in Windows Notepad.

Step 19Click Next.

The ACS service installation starts. The Setup Complete dialog box displays information about the ACS web interface.

Step 20Click Finish.

The setup program exits. If, in Step 17, you chose the options to view the web interface or README.TXT file, those options become effective now.

Step 21If you did not choose the options in Step 17. To:

Start ACS services, reboot the computer, or type net start csadmin at a DOS prompt.

Access the ACS web interface, use the ACS Admin desktop icon, or use this URL in

a supported web browser: http://127.0.0.1:2002 (or) http://localhost:2002

Configuring Local Security Policies:

This procedure is required only if one of the following conditions is true. ACS runs on a:

Member server and must authenticate users with a Windows user database.

Domain controller and must authenticate users in trusted domains or child domains.

You should have already created a user account through which you run ACS.

Configuring ACS Services:

This procedure is required only if one of the following conditions is true. ACS runs on a:

Member server and must authenticate users with a Windows user database.

Domain controller and must authenticate users in trusted domains or child domains.

You should have already created a user account through which you run ACS and assigned it the permissions necessary to run ACS services.

ACS 3.x to 4.2 ODBC Logging Updates:

If you used ACS 3.x ODBC logging and upgraded to ACS 4.2 while preserving your data, you must update the ODBC tables so that the Structured Query Language (SQL) tables continue to work.

From ACS 4.0 and later versions, changes to the SQL database present all the ODBC fields as strings rather than numbers. Field types have changed from INTEGER to VARCHAR.

Logging In and Out of the System:

To access ACS: Open a web browser by using the uniform resource locator (URL) for the machine.

http://IP address:2002

http://hostname:2002

If ACS is configured to use SSL to protect administrative sessions, you can also access the web interface by specifying the HTTPS protocol in the URLs:

https://IP address:2002

https://hostname:2002