Guest

Cisco Unified Application Environment

Release Notes for the Cisco Unified Application Environment Release 2.4(3) SR1

  • Viewing Options

  • PDF (211.0 KB)
  • Feedback
Release Notes for the Cisco Unified Application Environment, Release 2.4(3) SR1

Table Of Contents

Release Notes for the
Cisco Unified Application Environment,
Release 2.4(3) SR1

Contents

Related Documentation

New and Changed Information

Core Addendum and Prerequisite Update

Installation and Upgrade Notes

Upgrading From Release 2.2 or 2.3 to Release 2.4(3) SR1

Upgrading From Previous 2.4 Releases to Release 2.4(3) SR1

Documentation Updates

Installation Guide for the Cisco Unified Application Environment, 2.4

Upgrade Guide for the Cisco Unified Application Environment, 2.4

Administration Guide for the Cisco Unified Application, 2.4

Configuring the Unified Media Engine

Getting Started

Caveats

Using Bug Toolkit

Open Caveats

Resolved Caveats

Included HotFixes

Obtaining Documentation and Submitting a Service Request


Release Notes for the
Cisco Unified Application Environment,
Release 2.4(3) SR1


December, 2008

These release notes describe the enhancements and caveats for the Cisco Unified Application Environment, Release 2.4(3) SR1.

In addition to including many issue resolutions and hot fixes, this release requires an upgrade to the core addendum software. For more information, see the "Core Addendum and Prerequisite Update" section.

Contents

Related Documentation

New and Changed Information

Installation and Upgrade Notes

Documentation Updates

Caveats

Obtaining Documentation and Submitting a Service Request

Related Documentation

There are two types of related documentation: product and developer.

Table 1 provides links to product documentation.

For developer documentation, go to: http://developer.cisco.com/web/cuae

Table 1 Product Documentation 

Related Information
URL

Administration Guide for the Cisco Unified Application Environment, Release 2.4

http://www.cisco.com/en/US/docs/voice_ip_comm/cuae/2_4/english/administration/guide/admin.html

Installation Guide for the Cisco Unified Application Environment, Release 2.4

http://www.cisco.com/en/US/docs/voice_ip_comm/cuae/2_4/english/install/guide/uaein.html

Upgrade Guide for the Cisco Unified Application Environment, Release 2.4

http://www.cisco.com/en/US/docs/voice_ip_comm/cuae/2_4/english/upgrade/guide/uaeupg.html

Cisco Unified Communications Manager Documentation

http://www.cisco.com/en/US/products/sw/voicesw/ps556/tsd_products_support_series_home.html


New and Changed Information

The following section describes changes that are pertinent to the Cisco Unified Application Environment.

Core Addendum and Prerequisite Update

With this release, the core addendum includes an upgrade to Dialogic HMP 3.0 SU 225.


Note This upgrade is required for Cisco Unified Application Environment to function properly due to an issue between previous version of Dialogic HMP and the Windows 2003 Server SP2.


Production installations will be automatically updated when you run the Core Addendum updater. For more information, see the"Upgrading From Previous 2.4 Releases to Release 2.4(3) SR1" section.

SDK installations must manually upgrade to SU 225. For more information, see the Cisco Unified Application Environment wiki: http://developer.cisco.com/web/cuae.

Installation and Upgrade Notes

The following sections describe the upgrade procedures:

Upgrading From Release 2.2 or 2.3 to Release 2.4(3) SR1

Upgrading From Previous 2.4 Releases to Release 2.4(3) SR1

Upgrading From Release 2.2 or 2.3 to Release 2.4(3) SR1

To upgrade from Release 2.2 or 2.3 to Release 2.4(3) SR1, you must first upgrade to Release 2.4. To do so, refer to the Upgrade Guide for the Cisco Unified Application Environment, Release 2.4 listed in the "Related Documentation" section.


Note Refer to the "Upgrade Guide for the Cisco Unified Application Environment, 2.4" section for documentation updates to the upgrade guide.


Upgrading From Previous 2.4 Releases to Release 2.4(3) SR1


Note You are not required to uninstall the previous version of the Cisco Unified Application Environment before installing this version.


Before You Begin

1. From this location: http://developer.cisco.com/web/cuae/wikidocs?src=/wiki/display/CUAE/2.4.3+SR1, download the following executable files:

CUAE-coreadd-update-2.4.3.xxxx.exe (Cisco Unified Core Addendum Update)

CUAE-platsvc-2.4.3.xxxx.exe (Cisco Unified Platform Services)

CUAS-2.4.3.xxxx.exe (Cisco Unified Application Server)

CUME-2.4.3.xxxx.exe (Cisco Unified Media Engine)

2. Run the CUAE-coreadd-update-2.4.3.xxxx.exe self-extracting installer.

The package is extracted and runs a verification. Then end-user license agreement appears.

3. Read it, and if you agree with the terms of the agreement, select I Agree.

A console appears with output indicating the progress of the installation setup.

4. If upgrading from Release 2.4(3), stop the JTAPI service:

a. Log in to the Cisco Unified Application Environment Administration.

b. Choose Serviceability > Services. The Services page appears.

c. Select the check box next to the JTAPI service, then click Stop.

d. Log out of the Cisco Unified Application Environment Administration.

Procedure


Step 1 Use the procedures in the Installation Guide for the Cisco Unified Application Environment, Release 2.4 listed in the Related Documentation to install these components in the following order:

CUAE-platsvc-2.4.3.xxxx.exe (Cisco Unified Platform Services)

CUAS-2.4.3.xxxx.exe (Cisco Unified Application Server)

CUME-2.4.3.xxxx.exe (Cisco Unified Media Engine)


Note Refer to Installation Guide for the Cisco Unified Application Environment, 2.4 for documentation updates to the installation guide.


Step 2 When you have finished installing all the components and the server has rebooted, log into the Cisco Unified Application Server to ensure that the installation has completed.


Documentation Updates

There are changes and additions to the following guides that apply to this release:

Installation Guide for the Cisco Unified Application Environment, 2.4

Upgrade Guide for the Cisco Unified Application Environment, 2.4

Administration Guide for the Cisco Unified Application, 2.4

Installation Guide for the Cisco Unified Application Environment, 2.4

Following are changes and additions to the installation guide:

Any reference to Media Engine Configuration, which is listed under Local Environment on the Main Control Panel, is now Local System Configuration.

In the "Installing the Cisco Unified Platform Service" section, a new dialog box displays after you click Install to indicate the installation is complete.

In the "Installing the Cisco Unified Application Server" section, the last step directing you to Install the Cisco Unified Application Server should be: Install the Cisco Unified Media Engine.

In the "Installing the Cisco Unified Application Server" section, an additional step has been added and must be performed after you click Finish.

When the installation has completed, a dialog box prompts you to reboot the server. You do not need to reboot the server if you are installing the Cisco Unified Media Engine on the server.

Upgrade Guide for the Cisco Unified Application Environment, 2.4

Following are changes and additions to the upgrade guide:

Any reference to Media Engine Configuration, which is listed under Local Environment on the Main Control Panel, is now Local System Configuration.

In the "Performing the Post Upgrade Task" section, an additional step has been added and must be performed as the last step in the procedure:

After all of the services have successfully restarted, from the Main Control Panel, click Service Control, then click Restart for the Application Server Service. This ensures that the application server re-verifies the status of the Cisco Unified Application Environment components.

Administration Guide for the Cisco Unified Application, 2.4

Following are sections in the administration guide with changes and additions:

Configuring the Unified Media Engine

Getting Started

Configuring the Unified Media Engine

Following are changes to this section:

All references to the Change Password input box on the Configuring the Cisco Unified Media Engine page are now Local Engine Media Password.

All references to Media Engine Configuration, which is listed under Local Environment on the Main Control Panel, are now Local System Configuration.

A new procedure has been added to the Local System Configuration. Use this procedure to enter the Cisco Unified Media Engine's server host name or IP address to enable other servers to access the services on the Cisco Unified Media Engine.

Procedure


Step 1 Log in to the Cisco Unified Application Environment management console.

Step 2 From the Main Control Panel, under Local Environment, click Local System Configuration.

Step 3 Enter a fully qualified host name or an IP address.


Getting Started

Following is a new procedure to install the JTAPI Sample Application, which is added to the "Setting Up the Cisco Unified Application Environment" section, "Task 5: Install Sample Applications."

Use the application to verify the configuration and functionality of the JTAPI provider, which is used for third-party monitoring of changes in device state, as well as for control over devices.

Before You Begin

On the Cisco Unified Application Environment server, navigate to the directory C:\Program Files\Cisco Systems\Unified Application Environment\Tools\Apps, and locate the JTAPIConnect.mca file. If you are logged in to the Management Console remotely, you must store these files on your local machine. If you are logged in directly to the Management Console, you can copy them to the desktop.

Procedure


Step 1 Upload the JTAPI application into the Cisco Unified Application Environment.

a. Open the management console URL by entering: http://<serverIPaddress>/mceadmin.

b. From the Main Control Panel, click Applications.

c. Click Browse... and highlight the JTAPIConnect.mca file.

d. Click Open to make the file available for uploading.

e. Click Upload File.

The file is uploaded and added to the list on the Applications page.

Step 2 From the management console, create a monitored device pool and add two test devices to it. See the Cisco Unified Application Environment Administration Guide for specific instructions.

Step 3 Using the management console, select Main Control Panel > Applications > JTAPIConnect.

Step 4 In the Device1 field enter the device name of first device from the monitored device pool. In the "Device2 field enter the device name of second device from the monitored device pool.

Step 5 In the Device1_Line field enter the line number of first device from the monitored device pool. In the Device2_Line field enter the line number of the second device from monitored device pool.

Step 6 Click Apply Parameter Values.

Step 7 Test the application by opening a web browser and entering http://<Application Server IP>:8000/JTAPIConnect.

Both devices (test phones) ring, then auto answer each other. After two seconds, the phones hang up, and the browser displays "Success."

Caveats

This section contains these topics:

Using Bug Toolkit

Open Caveats

Resolved Caveats

Using Bug Toolkit

Known problems (bugs) are graded according to severity level. These release notes contain descriptions of:

All severity level 1 or 2 bugs.

Significant severity level 3 bugs.

You can search for problems by using the Cisco Software Bug Toolkit. To access Bug Toolkit, you need the following items:

Internet connection

Web browser

Cisco.com user ID and password

To use the Software Bug Toolkit, follow these steps:

Procedure


Step 1 To access the Bug Toolkit, go to http://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs.

Step 2 Log in with your Cisco.com user ID and password.

Step 3 To look for information about a specific problem, enter the bug ID number in the "Search for Bug ID" field, then click Go.


Open Caveats

Table 2 lists the open caveats. For information about an individual bug, click the Identifier to access the online record, including workarounds.


Note Because defect status continually changes, be aware that Table 2 reflects a snapshot of the defects that were open at the time the release notes were compiled. For an updated view of open defects, access Bug Toolkit and follow the instructions as described in the "Using Bug Toolkit" section.


.

Table 2 Open Caveats for the Cisco Unified Application Environment,
Release 2.4.3 

Identifier
Headline

CSCsk52936

Cisco Unified Application Designer version label is not updated when hotfixed.

CSCsl20894

No end canvas tag in script file, causing corruption of script.

CSCsm93249

Can't set max/min for config item to empty if set to another value.

CSCsm93288

Rename script does not work.

CSCsm93350

Rename application does not work.

CSCsm93685

Bool config items must have a default value to deploy.

CSCsm93722

Number config items must have a default value to deploy.

CSCsm93736

TraceLevel config items must have a default value to deploy.

CSCsm93746

DateTime config items must have a default value to deploy.

CSCsm95409

Default values for HashTable and DataTable aren't displayed in MCE Admin.

CSCsm95691

Can't build an application with a TriggerLevel with no default value.

CSCsm95729

Default values for DateTime configurations are displayed incorrectly.

CSCsm97075

Cisco Unified Application Designer Project with references does not compile in different machines.

CSCsm99866

Two Application Servers controlling two Media Engines fail sporadically.

CSCso18196

Project DLL that reference Native Action or Type fails to add to project.


Resolved Caveats

Table 3 lists Severity 1, 2 and 3 defects that are resolved since the last release of the Cisco Unified Application Environment.

For more information about an individual defect, you can access the online record for the defect by clicking the Identifier or going to the URL shown. You must be a registered Cisco.com user to access this online information.

Because defect status continually changes, be aware that Table 4 reflects a snapshot of the defects that were resolved at the time this report was compiled. For an updated view of resolved defects, access Bug Toolkit as described in the "Using Bug Toolkit" section on page 5.

.

Table 3 Resolved Caveats for the Cisco Unified Application Environment

Identifier
Headline

CSCsk33427

DeviceListX Provider does not get device pool and CSS for 5.x/6.x.

CSCsk67710

Provider does not uninstall when accessed by another process.

CSCsk76463

New devices or locales break response parse of AXL-SOAP.

CSCsk99104

cuae-common.config file missing.

CSCsl19035

Action nodes can erroneously retain loop container metadata.

CSCsl46101

Remote Console breaks after long uptime.

CSCsl46909

Configs with periods in the name cannot be updated from mceadmin.

CSCsm56058

H.323 MakeCall retries second configured gateway on REJECT.

CSCso18240

VMWare image 2.4.2 upgrade throws an exception.


Included HotFixes

Table 4 lists hot fixes that were released earlier that are included in this release.

For more information about an individual defect, you can access the online record for the defect by clicking the Identifier or going to the URL shown. You must be a registered Cisco.com user to access this online information.

Because defect status continually changes, be aware that Table 4 reflects a snapshot of the defects that were resolved at the time this report was compiled. For an updated view of resolved defects, access Bug Toolkit as described in the "Using Bug Toolkit" section.

Table 4 HotFixes Included in Release 2.4.3 SR1

Release and Hotfix
Identifier
Description

2.4.2 HF6

CSCsq32734

Incoming call failure in the SIP early media.

2.4.2 HF7

CSCsr21089

Call is established before call is answered in case of SIP early media.

2.4.3 HF2

CSCsq32734

Incoming call failure in the SIP early media.

2.4.3 HF3

CSCsq36873

For newly added devices, the QueryDevices action returns incorrect data.

2.4.3 HF4

CSCsq63135

No audio after unbridge in SIP is connected.

2.4.3 HF5

CSCsq87272

Voice rec licenses are not getting released.

2.4.3 HF6

CSCsq94869

JTAPI log messages prints password in clear text.

2.4.3 HF7

CSCsr11545

Leaving conferences while using SIP causes GatherDigits to fail.

2.4.3 HF8

CSCsr11586

While using SIP, Proxy DTMF does not work.

2.4.3 HF10

CSCsq99620

CUAE SNMP trap is sent without OID.

2.4.3 HF11

CSCsr21089

Call is established before call is answered in case of SIP early media.

2.4.3 HF12

CSCsr25473

When ConsultTransfer is completed, no more events occur.

2.4.3 HF13

CSCsr11586

While using SIP, Proxy DTMF does not work.

CSCsr21089

Call is established before call is answered in case of SIP early media.

CSCsq63135

No audio after unbridge in SIP is connected.

CSCsq32734

Incoming call failure in the SIP early media.

2.4.3 HF14

CSCsr39535

Outbound SIP Calls do not failover to other members in Call Route Group.

2.4.3 HF15

CSCsr43850

Silence detection fails when rapid silence on/off transitions occur.

CSCsr46998

Leaving conferences while using SIP causes GatherDigits to fail.

2.4.3 HF16

CSCsr58449

JTAPI provider unable to support 2500 monitoring devices.

2.4.3 HF17

CSCsu29296

MakeCall Failure EndReason is not accurate in SIP.

2.4.3 Hf18

CSCsu52891

Race condition in SCCP during reregistration due to network interruption.


Obtaining Documentation and Submitting a Service Request

For information on obtaining documentation, submitting a service request, and gathering additional information, see the monthly What's New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation, at:

http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html

Subscribe to the What's New in Cisco Product Documentation as a Really Simple Syndication (RSS) feed and set content to be delivered directly to your desktop using a reader application. The RSS feeds are a free service and Cisco currently supports RSS version 2.0.