Cisco Unified JTAPI Developers Guide for Cisco Unified Communications Manager Release 7.1(2)
New and Changed Information
Downloads: This chapterpdf (PDF - 135.0KB) The complete bookPDF (PDF - 9.51MB) | Feedback

New and Changed Information

Table Of Contents

New and Changed Information

Cisco Unified Communications Manager Release 7.1(2)

Features Supported in Previous Releases

Cisco Unified Communications Manager Release 7.0(1)

Cisco Unified Communications Manager Release 6.1

Cisco Unified Communications Manager Release 6.0

Cisco Unified Communications Manager Release 5.1

Cisco Unified Communications Manager Release 5.0

Backward Compatibility


New and Changed Information


This chapter describes new and changed JTAPI information for Cisco Unified Communications Manager, release 7.1(2) and features supported in the previous releases. It contains the following sections:

Cisco Unified Communications Manager Release 7.1(2)

Features Supported in Previous Releases

Backward Compatibility

For more information, go to the Programming Guides website at http://www.cisco.com/en/US/products/sw/voicesw/ps556/products_programming_reference_guides_list.html.

Cisco Unified Communications Manager Release 7.1(2)

This section describes the new and changed features in Cisco Unified Communications Manager Release 7.1(2):

Drop Any Party—Provides the capability to drop any participants from a conference call. For more information, see Drop Any Party, page 3-1.

IPv6—Supports IPv6 addresses and Cisco JTAPI is enhanced to support IPv6 connectivity to CTIManager. For more information, see IPv6 Support, page 3-2.

Direct Transfer Across Lines—Allows support for connected transfer across lines. For more information, see Direct Transfer Across Lines, page 3-3.

Join Across Line or Connected Conference Across Lines—This feature has been enhanced in this release by introducing new phone models that fall outside the purview of existing Join Across Lines feature always Enabled without any service parameter. For more information, see Join Across Lines or Connected Conference Across Lines, page 3-7.

Swap or Cancel and Transfer or Conference Behavior—Enables Cisco Unified JTAPI support for Swap and Cancel operations on supported IP phones. For more information, see Swap or Cancel and Transfer or Conference Behavior, page 3-12.

Enhanced MWI—Allows applications to provide the following message counts to be displayed on phones that support the enhanced message waiting counts. For more information, see Message Waiting Indicator Enhancement, page 3-13.

Park Monitoring and Assisted DPark Support—Provides a new park reversion behavior to applications invoking the park request from newer phones. For more information, see Park Monitoring and Assisted DPark Support, page 3-13.

Logical Partitioning—Allows administrators to configure geographical locations and restrict calls that pass through a PSTN gateway to be connected directly to a VoIP phone or VoIP PSTN gateway in another geographic location. For more information, see Logical Partitioning, page 3-15.

Component Updater—This feature has been enhanced to allow applications to specify the location of updater log. Currently updater log is created in the same directory as the application. For more information, see Component Updater, page 3-16.

Support for Cisco Unified IP Phone 6900 Series—Allows Cisco Unified JTAPI applications to control terminals with rollover mode enabled. For more information, see Support for Cisco Unified IP Phone 6900 Series, page 3-16.

Features Supported in Previous Releases

This section describes the features supported in the releases prior to 7.1(2) and contains the following

sections:

Cisco Unified Communications Manager Release 7.0(1)

Cisco Unified Communications Manager Release 6.1

Cisco Unified Communications Manager Release 6.0

Cisco Unified Communications Manager Release 5.1

Cisco Unified Communications Manager Release 5.0

Cisco Unified Communications Manager Release 7.0(1)

This section describes the new and changed features in Cisco Unified Communications Manager from Release 6.1 to Release 7.0(1) and Cisco Unified JTAPI enhancements. It has the following sections:

Join Across Lines with Conference Enhancements, page 3-17

Locale Infrastructure Development, page 3-18

Do Not Disturb-Reject, page 3-19

Calling Party Normalization, page 3-20

Click to Conference, page 3-20

Extension Mobility Username Login, page 3-20

Java Socket Connect Timeout, page 3-21

selectRoute() with Calling Search Space and Feature Priority, page 3-21

Call Pickup, page 3-21


Note Cisco Unified Communications Manager Release 7.0(1) does not support the following IPv6 related methods:

canSupportIPv6()
setProviderOpenRetryAttempts (int retryAttempts)
getProviderOpenRetryAttempts()
getIPAddressingMode() (available on CiscoMediaTerminal and CiscoRouteTerminal interfaces)
register(java.net.InetAddress address, int port, CiscoMediaCapability [] capabilities, int[] algorithmIDs, java.net.InetAddress address_v6, int activeAddressingMode)
register(CiscoMediaCapability [] capabilities, int[] int registration Type, int[] algorithmIDs, int activeAddressingMode)
getTerminals() (available on new interface CiscoProviderTermCapabilityChangedEv)
getAddressingModeForMedia()
getCallingPartyIpAddr_v6() (available on CiscoCallCtlConnOfferedEv and CiscoRouteEvent interfaces)
CTIERR_IPADDRMODEMISMATCH
CTIERR_DYNREG_IPADDRMODE_MISMATCH
hasIPv6CapabilityChanged()
CiscoTerminal.IP_ADDRESSING_MODE_IPv4
CiscoTerminal.IP_ADDRESSING_MODE_IPv6
CiscoTerminal.IP_ADDRESSING_MODE_IPv4_v6
CiscoTerminal.IP_ADDRESSING_MODE_Unknown
CiscoTermRegistrationFailedEv.IP_ADDRESSING_MODE_MISMATCH



Note For the features, Join Across Lines, Do Not Disturb-Reject, and Calling Party Normalization, each JTAPI application must be upgraded to a version that is compatible with these features. Additionally, if you are upgrading from Release 5.1 and you use Join Across Lines, the Conference Chaining feature must not be enabled or used until all applications are either upgraded to a version compatible with the new CUCM version. Also, you should verify that the applications are not impacted by the Conference Chaining feature.


Cisco Unified Communications Manager Release 6.1

This section describes the new and changed features in Cisco Unified Communications Manager from Release 6.0 to Release 6.1 and Cisco Unified JTAPI enhancements. It has the following sections:

Certificate Download API Enhancement, page 3-22

Join Across Lines, page 3-22

Intercom Support for Extension Mobility, page 3-23

Cisco Unified Communications Manager Release 6.0

This section describes the new and changed features in Cisco Unified Communications Manager, Release 6.0 and Cisco Unified JTAPI enhancements. It has the following sections:

Recording and Silent Monitoring, page 3-23

Intercom, page 3-26

Arabic and Hebrew Language Support, page 3-27

Do Not Disturb, page 3-28

Secure Conferencing, page 3-29

Cisco Unified IP 7931G Phone Interaction, page 3-30

Version Format Change, page 3-31

Calling Party IP Address, page 3-31

Multilevel Precedence and Preemption Support, page 3-31

Noncontroller Adding of Parties to Conferences, page 3-31

Conference Chaining, page 3-31

Forwarding on No Bandwidth and Unregistered DN, page 3-33

Directed Call Park, page 3-33

Voice MailBox Support, page 3-34

Privacy On Hold, page 3-34

CiscoRTPHandle Interface on Cisco RTP Events, page 3-35

Hold Reversion, page 3-35

Translation Pattern Support, page 3-35

Calling Party IP Address, page 3-36

Cisco Unified Communications Manager Release 5.1

This section describes the new and changed features in Cisco Unified Communications Manager, from Release 5.0 to Release 5.1 and Cisco Unified JTAPI enhancements. It has the following sections:

Join Across Lines, page 3-37

New Error Code in CiscoTermRegistrationFailedEv, page 3-37

Star (*) 50 Update, page 3-38

Call Forward Override, page 3-38

Cisco Unified Communications Manager Release 5.0

This section describes the new and changed features in Cisco Unified Communications Manager, from Release 4.x to Release 5.0 and Cisco Unified JTAPI enhancements. It has the following:

Partition Support, page 3-39

Hairpin Support, page 3-42

QoS Support, page 3-42

Transport Layer Security (TLS), page 3-43

SIP Phone Support, page 3-49

Secure Real-Time Protocol Key Material, page 3-52

SIP REFER or REPLACE, page 3-59

SIP 3XX Redirection, page 3-61

Terminal and Address Restrictions, page 3-62

Unicode Support, page 3-65

Linux, Windows, and Solaris Installation, page 3-68

Silent Install, page 3-69

Command Line Invocation, page 3-69

JTAPI Client Installer, page 3-69

JRE 1.2 and JRE 1.3 Support Removal, page 3-70

Superprovider and Change Notification, page 3-71

Alternate Script Support, page 3-73

Half-Duplex Media Support, page 3-73

Network Alerting, page 3-75

Auto Updater for Linux, page 3-75

Call Select Status, page 3-76

JTAPI Version Information, page 3-76

Backward Compatibility

This release of JTAPI is backward compatible with applications written for Cisco Unified Communications Manager Release 6.0. CiscoJtapiClient upgrade is not mandatory.

Cisco JtapiClient upgrade is not mandatory. Applications are required to upgrade to Cisco Unified Communications Manager Release 6.1, CiscoJTAPIClient only if using any of the new features developed in Cisco Unified Communications Manager Release 6.1.

Operating System Independence (OSI) support is added in Cisco Unified Communications Manager Release 7.0(1) and Cisco Unified JTAPI also. This supports telephony features of Cisco Unified Communications Manager Release 7.0(1) in both Linux and Windows 2003 server.

The Cisco Unified Communications Manager features are ported from Cisco Unified Communications Manager Release 6.0(x) (Appliance) to Cisco Unified Communications Manager Release 7.0(1) (Win2003).

When a user upgrades from Cisco Unified Communications Manager 4.x (Windows) to Cisco Unified Communications Manager 7.0(1) (Windows/Linux), the plugin URL to download the jtapi.jar is different. In Cisco Unified Communications Manager Release 7.0(1), the plugin URL from 6.x releases is maintained.

The applications should comply with the following rules:

The order of Cisco Unified JTAPI events, beyond that which is required for JTAPI protocol operation, may change. Application developers should not depend upon the order of events, beyond that which is required for JTAPI protocol operation. Applications should be able to recover from out of order events, even when the order is required for (API Name) protocol operation.

Applications should avoid using deprecated methods.

Application should expect to see new behavior and/or event order with new phones.

Application should gracefully ignore events it does not handle. For example: CiscoCallChangedEv can be ignored if applications chooses to use CiscoTransferStart and End events.

Application should have a default behavior for reasons that it is not aware of.

Applications should have a default behavior for undefined error codes.

Any behavior not defined in JTAPI 1.2 specification and not described in Cisco Unified JTAPI Developers Guide should not be considered as a feature.

For Cisco Unified Communications Manager Administration Release 4.x (Windows), the URL is http://<servername or ip address>/CCMPluginsServer/jtapi.jar.

For Cisco Unified Communications Manager Administration Release 6.x and 7.0(1) (Linux), the URL is

http://<server name or ip address>/plugins/jtapi.jar.

For Cisco Unified Communications Manager Administration Release 7.0(1) (Windows), the URL is http://<server name or ip address>/plugins/jtapi.jar.

The backward compatibility with regard to the plugin URL is not maintained between Cisco Unified Communications Manager Release 4.x and Cisco Unified Communications Manager Release 7.0(1).