In Cisco Unity Connection Administration, expand Telephony Integrations > and select Phone System.

On the Search Phone Systems page, under Display Name, select the name of the default phone system.

On the Phone System Basics page, in the Phone System Name field, enter the descriptive name that you want for the phone system.

If you want to use this phone system as the default for TRaP connections so that administrators and users without voicemail boxes can record and playback through the phone in Unity Connection web applications, check the Default TRAP Switch check box. If you want to use another phone system as the default for TRaP connections, uncheck this check box.

Select Save.

On the Phone System Basics page, in the Related Links drop-down box, select Add Port Group and select Go.

On the New Port Group page, enter the applicable settings and select Save.

On the Port Group Basics page, in the Related Links drop-down box, select Add Ports and select Go.

On the New Port page, enter the following settings and select Save.

On the Search Ports page, select the display name of the first voice messaging port that you created for this phone system integration.

On the Port Basics page, enter the following settings. The fields in the following table are the ones that you can change.

Select Save.

Select Next.

Repeat Step 11 through Step 13 for all remaining voice messaging ports for the phone system.

If another phone system integration exists, in Cisco Unity Connection Administration, expand Telephony Integrations, then select Trunk. Otherwise, skip to Step 19.

On the Search Phone System Trunks page, on the Phone System Trunk menu, select New Phone System Trunk.

On the New Phone System Trunk page, enter the following settings for the phone system trunk and select Save.

Repeat Step 16 and Step 17 for all remaining phone system trunks that you want to create.

In the Related Links drop-down list, select Check Telephony Configuration and select Go to confirm the phone system integration settings.

In the Task Execution Results window, select Close.

Set up two test extensions (Phone 1 and Phone 2) on the same phone system that Unity Connection is connected to.

Set Phone 1 to forward calls to the Unity Connection pilot number when calls are not answered.

In Cisco Unity Connection Administration, expand Users > and select Users.

On the Search Users page, select the display name of a user to use for testing. The extension for this user must be the extension for Phone 1.

On the Edit User Basics page, uncheck the Set for Self-enrollment at Next Login check box.

In the Voice Name field, record a voice name for the test user and select Save.

On the Edit menu, select Message Waiting Indicators.

On the Message Waiting Indicators page, select the message waiting indicator. If no message waiting indication is in the table, select Add New.

On the Edit Message Waiting Indicator page, enter the following settings.

Select Save.

On the Edit menu, select Transfer Rules.

On the Transfer Rules page, select the active option.

On the Edit Transfer Rule page, under Transfer Action, select the Extension option and enter the extension of Phone 1.

In the Transfer Type field, select Release to Switch.

Select Save.

Minimize the Cisco Unity Connection Administration window. Do not close the Cisco Unity Connection Administration window because you use it again in a later procedure.

Sign in to the Real-Time Monitoring Tool (RTMT).

On the Unity Connection menu, select Port Monitor. The Port Monitor tool appears in the right pane.

In the right pane, select Start Polling. The Port Monitor displays which port is handling the calls that you make.

From Phone 2, enter the access code necessary to get an outside line, then enter the number outside callers use to dial directly to Unity Connection.

In the Port Monitor, note which port handles this call.

When you hear the opening greeting, enter the extension for Phone 1. Hearing the opening greeting means that the port is configured correctly.

Confirm that Phone 1 rings and that you hear a ringback tone on Phone 2. Hearing a ringback tone means that Unity Connection correctly released the call and transferred it to Phone 1.

Leaving Phone 1 unanswered, confirm that the state of the port handling the call changes to “Idle.” This state means that release transfer is successful.

Confirm that, after the number of rings that the phone system is set to wait, the call is forwarded to Cisco Unity Connection and that you hear the greeting for the test user. Hearing the greeting means that the phone system forwarded the unanswered call and the call-forward information to Unity Connection, which correctly interpreted the information.

On the Port Monitor, note which port handles this call.

Leave a message for the test user and hang up Phone 2.

In the Port Monitor, confirm that the state of the port handling the call changes to “Idle.” This state means that the port was successfully released when the call ended.

Confirm that the MWI on Phone 1 is activated. The activated MWI means that the phone system and Unity Connection are successfully integrated for turning on MWIs.

From Phone 1, enter the internal pilot number for Unity Connection.

When asked for your password, enter the password for the test user. Hearing the request for your password means that the phone system sent the necessary call information to Unity Connection, which correctly interpreted the information.

Confirm that you hear the recorded voice name for the test user (if you did not record a voice name for the test user, you hear the extension number for Phone 1). Hearing the voice name means that Unity Connection correctly identified the user by the extension.

Listen to the message.

After listening to the message, delete the message.

Confirm that the MWI on Phone 1 is deactivated. The deactivated MWI means that the phone system and Unity Connection are successfully integrated for turning off MWIs.

Hang up Phone 1.

On the Port Monitor, confirm that the state of the port handling the call changes to “Idle.” This state means that the port was successfully released when the call ended.

In Cisco Unity Connection Administration, on the Edit Transfer Rule page for the test user, in the Transfer Type field, select Supervise Transfer.

In the Rings to Wait For field, enter 3.

Select Save.

Minimize the Cisco Unity Connection Administration window. Do not close the Cisco Unity Connection Administration window because you use it again in a later procedure.

From Phone 2, enter the access code necessary to get an outside line, then enter the number outside callers use to dial directly to Unity Connection.

On the Port Monitor, note which port handles this call.

When you hear the opening greeting, enter the extension for Phone 1. Hearing the opening greeting means that the port is configured correctly.

Confirm that Phone 1 rings and that you do not hear a ringback tone on Phone 2. Instead, you should hear the indication your phone system uses to mean that the call is on hold (for example, music).

Leaving Phone 1 unanswered, confirm that the state of the port handling the call remains “Busy.” This state and hearing an indication that you are on hold mean that Unity Connection is supervising the transfer.

Confirm that, after three rings, you hear the greeting for the test user. Hearing the greeting means that Unity Connection successfully recalled the supervised-transfer call.

During the greeting, hang up Phone 2.

On the Port Monitor, confirm that the state of the port handling the call changes to “Idle.” This state means that the port was successfully released when the call ended.

Select Stop Polling.

Sign out of RTMT.