Release Note

Contents

Introduction

As of February 1, 2012, Genesys is no longer an affiliate of Alcatel-Lucent; any indication of such affiliation within Genesys products or packaging is no longer applicable. Please see the Genesys website at http://www.genesyslab.com for more details.

This release note applies to all 7.6 releases of T-Server for Cisco CallManager.

• Links in the Contents section enable you to access information regarding a specific release. Releases are listed by version number rather than in date order. For this reason, a recent release may be listed after earlier releases, if the version number is lower. Except when otherwise noted in the information for a specific release, each release includes all of the features and corrections that were introduced for the applicable operating system at earlier dates, regardless of the version numbering.
• The Release Number table lists the supported operating systems for each release at a high level. For more detailed information, see the Genesys Supported Operating Environment Reference Manual.
• The Known Issues and Recommendations section is a cumulative list. It includes information on when individual items were found and, if applicable, corrected.
• The Corrections and Modifications section for each release may list additional issues that were corrected without first being documented as Known Issues.
• The Discontinued Support section is cumulative. It lists functionality that is no longer supported and the release number of the version in which support was discontinued.
• You can find information about changes and corrections to functionality common to all T-Servers in the release note for T-Server Common Part release 7.6.x.
• Your T-Server’s name correlates generally with the name of the switch you intend to use, but vendor switch names often change. For full details on the name(s) of the switch intended for use with this T-Server, see the Genesys Supported Media Interfaces Reference Manual.

Use of Third-Party Software

Genesys follows applicable third-party redistribution policies to the extent that Genesys solutions utilize functionality of commercial or non-commercial third parties. For specific information on any third-party software used in this product, see the Read Me.

Supported Operating Systems

New in This Release

This release of T-Server is built with the T-Server Common Part (TSCP) release number 7.6.008.20. TSCP is the shared software that all T-Servers use. Consult the TSCP release note for information on changes to the Common Part that may affect the functionality of your particular type of T-Server.

This is a hot fix for this product. This release does not contain any new features or functionality.

Corrections and Modifications

This release includes the following correction and modification:

T-Server now checks the validity of unmonitored objects in memory before applying processing algorithms. Previously, T-Server may have become unstable while processing an EventEstablished event for an unmonitored DN. (ER# 266397949)

Top of Page

Supported Operating Systems

New in This Release

This release of T-Server is built with the T-Server Common Part (TSCP) release number 7.6.008.20. TSCP is the shared software that all T-Servers use. Consult the TSCP release note for information on changes to the Common Part that may affect the functionality of your particular type of T-Server.

This is a hot fix for this product. This release does not contain any new features or functionality.

Corrections and Modifications

This release includes the following corrections and modifications:

T-Server now validates an AgentLogin request before trying to distribute the call. Previously, T-Server could become unstable, because of a race condition, when a call was just about to be distributed from an ACD Queue to an agent. (ER# 245966797)

T-Server has been improved to better handle pending events from the switch while it processes established events. Previously, T-Server may have become unstable after a call was established with a non-monitored party. (ER# 236367732)

Top of Page

Supported Operating Systems

New in This Release

This release of T-Server is built with the T-Server Common Part (TSCP) release number 7.6.008.19. TSCP is the shared software that all T-Servers use. Consult the TSCP release note for information on changes to the Common Part that may affect the functionality of your particular type of T-Server.

This is a hot fix for this product. This release does not contain any new features or functionality.

Corrections and Modifications

This release includes the following corrections and modifications:

T-Server now checks the transfer controller and does not force a hold state for a main call if a consultation call already has a party on a hold. Previously, T-Server may have incorrectly put a main call on hold if an AlternateCall request was issued the between initiate transfer and complete transfer requests in a two-step transfer scenario. (ER# 244572930)

T-Server now checks terminal information provided in JTAPI events and ignores out-of-service events that are received for the wrong terminal. Previously, T-Server may have incorrectly set an Extension Mobility (EM) address to an out-of-service state if the autologout feature was configured for EM addresses on the CUCM switch. (ER# 246513904)

T-Server now remembers client registrations and will register DNs for terminal events after a DN is placed back in service. Previously, T-Server did not register DNs that were in an out-of-service state for terminal events. (ER# 246280530)

Top of Page

Supported Operating Systems

New in This Release

This release of T-Server is built with the T-Server Common Part (TSCP) release number 7.6.008.19. TSCP is the shared software that all T-Servers use. Consult the TSCP release note for information on changes to the Common Part that may affect the functionality of your particular type of T-Server.

This is a hot fix for this product. This release does not contain any new features or functionality.

Corrections and Modifications

This release includes the following corrections and modifications:

T-Server now uses improved party matching detection for EventRouteUsed/EventQueued and EventRinging events. Previously, T-Server may not have started the No-Answer Supervision feature for an agent that did not answer an inbound call that was routed to this agent from a Routing Point. The following option is used to enable party matching detection:

This option is configured in the globalgroup section on the Options tab for the T-Server Application object in the Configuration Layer.

observer-latency-timeout
Default Value: 0
Valid Values: Any positive integer
Changes Take Effect: Immediately

To enable party matching detection, specify a value other than the default (a value of 20 (msec) is recommended). The default value of 0 (zero) disables the functionality of this option.

(ER# 237580996)

Top of Page

Supported Operating Systems

New in This Release

This release of T-Server is built with the T-Server Common Part (TSCP) release number 7.6.008.18. TSCP is the shared software that all T-Servers use. Consult the TSCP release note for information on changes to the Common Part that may affect the functionality of your particular type of T-Server.

This is a hot fix for this product. This release does not contain any new features or functionality.

Corrections and Modifications

This release includes the following corrections and modifications:

T-Server now correctly clears the screen on Cisco IP phones by using Init:services. Previously, XML data could have stayed on the phone screen after a call was ended.

T-Server now verifies that no duplicate messages are sent to an IP phone immediately one after another. Previously, T-Server in high-availability (HA) mode might have sent duplicate XML data to an IP phone, preventing the model 7940 Cisco IP Phone from displaying the data.

(ER# 238800808)

Top of Page

Supported Operating Systems

New in This Release

This release of T-Server is built with the T-Server Common Part (TSCP) release number 7.6.008.09. TSCP is the shared software that all T-Servers use. Consult the TSCP release note for information on changes to the Common Part that may affect the functionality of your particular type of T-Server.

This is a hot fix for this product. This release does not contain any new features or functionality.

Corrections and Modifications

This release includes the following corrections and modifications:

A new restricted option called ignore-released-nonexist-ext-party has been added to T-Server.

This option is configured in the globalgroup section on the Options tab for the T-Server Application Object in the Configuration Layer.

ignore-released-nonexist-ext-party
Default Value: false
Valid Values: true, false
Changes Take Effect: Immediately

When set to true, T-Server, in a multisite environment, ignores JTAPI released events sent for an external party with digits that are equal to a monitored internal DN, when the call is returned to Cisco CallManager after a transfer completion.

(ER# 223121488)

A new restricted option called ignore-ext-establ-if-other-not-oncall has been added to T-Server.

This option is configured in the globalgroup section on the Options tab for the T-Server Application Object in the Configuration Layer.

ignore-ext-establ-if-other-not-oncall
Default Value: true
Valid Values: true, false
Changes Take Effect: Immediately

When set to true, T-Server ignores JTAPI established events sent for an external address if otherDN is internal, monitored, and not part of the call. In this scenario, T-Server prints the following log message: Check CCM_TEVENT_ESTABLISHED for Unmonitored Address/OtherDn: <EXTERNAL_ADDRESS_DIGITS> Skip unmonitored established since <otherAddressDigits> is non existing party on call.

(ER# 216572365)

Top of Page

Supported Operating Systems

New in This Release

This release of T-Server is built with the T-Server Common Part (TSCP) release number 7.6.008.09. TSCP is the shared software that all T-Servers use. Consult the TSCP release note for information on changes to the Common Part that may affect the functionality of your particular type of T-Server.

This is a hot fix for this product. This release does not contain any new features or functionality.

Corrections and Modifications

This release includes the following corrections and modifications:

T-Server now correctly detects that the first leg of a call is already ended, and does not try to recreate a missing controller party on the main call in a transfer scenario where the external party hangs up at the same moment as the transfer is complete. Previously, this scenario could result in a stuck controller of the call. (ER# 189387566)

Top of Page

Supported Operating Systems

New in This Release

This release of T-Server is built with the T-Server Common Part (TSCP) release number 7.6.008.07. TSCP is the shared software that all T-Servers use. Consult the TSCP release note for information on changes to the Common Part that may affect the functionality of your particular type of T-Server.

This is a hot fix for this product. This release does not contain any new features or functionality.

Corrections and Modifications

This release includes the following corrections and modifications:

T-Server no longer distributes AddressOutOfService for all addresses when the primary T-Server, in a high-availability (HA) configuration, performs a graceful shutdown. As a result, the backup T-Server now immediately controls all addresses after a switchover. Previously, T-Server distributed out of service events that could have potentially confused T-Server clients. (ER# 192806307)

T-Server now correctly ignores JTAPI Established events between two unmonitored addresses. Previously, T-Server incorrectly interpreted JTAPI Established events issued on behalf of a trunk and an external address as an Established event on the agent's phone. (ER# 191807477)

T-Server now verifies that the correct Link object is associated with an Address and, in those situations where the Link object is not yet available, T-Server generates a warning in the log file. Previously, T-Server may have become unstable if the Address switched between InService and OutOfService states multiple times over a short period of time. (ER# 206478667)

Top of Page

Supported Operating Systems

New in This Release

This release of T-Server is built with the T-Server Common Part (TSCP) release number 7.6.008.07. TSCP is the shared software that all T-Servers use. Consult the TSCP release note for information on changes to the Common Part that may affect the functionality of your particular type of T-Server.

This is a hot fix for this product. This release does not contain any new features or functionality.

Corrections and Modifications

This release includes the following corrections and modifications:

T-Server now checks the association between a DN and the corresponding JTAPI link before trying to access this DN. Previously, T-Server could become unstable when processing events from the switch while deleting a DN from Cisco CallManager if in Socket mode. (ER# 189050316)

T-Server now distributes EventLinkDisconnected to clients if all Cisco CTI managers are out of service. Previously, T-Server did not send EventLinkDisconnected to clients if multiple JTAPI links were used to connect to a Cisco CallManager cluster, and all Cisco CTI managers in the cluster went out of service. This affected the high-availability (HA) functionality. (ER# 190266169)

Top of Page

Supported Operating Systems

New in This Release

This release of T-Server is built with the T-Server Common Part (TSCP) release number 7.6.008.07. TSCP is the shared software that all T-Servers use. Consult the TSCP release note for information on changes to the Common Part that may affect the functionality of your particular type of T-Server.

There are no restrictions for this release. This section describes new features that were introduced in release.

• T-Server is now capable of applying a treatment with a RingBack type to a new call without a charge to the customer. This treatment uses the Cisco CallManager native ringback feature rather than connecting a customer with Stream Manager to play a predefined audio file with a ringback sound. This treatment should be the first treatment in a strategy.

• T-Server 7.6.x supports all versions of Cisco UCM v6.0(x) and v6.1(x), and all versions of JTAPI supported by these releases of Cisco.

• T-Server has been successfully tested against version 6.1.1.2107-1 with JTAPI 6.1(1.1000)-2 of Cisco CallManager.

Corrections and Modifications

This release includes the following corrections and modifications:

T-Server now sends an EventReleased to the originating bridged party if a Shared Line DN dials a busy destination then releases. Previously, in this scenario, T-Server occasionally sent an EventAbandoned. (ER# 179488796)

T-Server now correctly handles calls where JTAPI RouteRequest and Released events arrive at the same time. Previously, a call could have become stuck on a Routing Point in this scenario. (ER# 182662433)

When operating in a high-availability environment and in JVM mode, T-Server no longer incorrectly distributes DNBackInService events at startup. (ER# 181659045)

T-Server now correctly distributes an EventAbandoned if a call is dropped when a treatment is not applied. Previously, T-Server could have occasionally suppressed the EventAbandoned event on a Routing Point if an error condition was detected before the call was dropped by the customer. (ER# 180946424)

T-Server now correctly checks for pending requests and distributes an EventError instead of event TreatmentNotApplied on route attempt failures. (ER# 180946497)

T-Server now correctly matches an EventError Reference ID with a RequestRouteCall Reference ID in scenarios where T-Server tries unsuccessfully to route a call from a Routing Point after successfully applying a treatment to that call. (ER# 176500689)

Top of Page

Supported Operating Systems

New in This Release

This release of T-Server is built with the T-Server Common Part (TSCP) release number 7.6.008.06. TSCP is the shared software that all T-Servers use. Consult the TSCP release note for information on changes to the Common Part that may affect the functionality of your particular type of T-Server.

This is a hot fix for this product. This release does not contain any new features or functionality.

Corrections and Modifications

This release includes the following corrections and modifications:

T-Server now correctly processes improper requests that have DN digits of more than 1000 characters. Previously, T-Server became unstable while processing these requests. (ER# 173383387)

T-Server now uses the correct data format for EventLocationInfo when used in an environment with ISCC connections to many other T-Servers. Previously, T-Server became unstable and/or consumes a large amount of memory while processing a RequestQueryLocationInfo due to incorrect data packaging in the respective EventLocationInfo. (ER# 177468284)

T-Server now correctly processes abandoned inbound calls to a Shared Line DN by distributing EventAbandoned for all Shared Lines in scenarios where an external party abandons the call. This scenario applies when T-Server is connected to Cisco CallManager version 4.x, and the enable-pickup-jtapi-workaround option is set to true. Previously, T-Server incorrectly distributed EventReleased. (ER# 174571834)

Top of Page

Supported Operating Systems

New in This Release

This release of T-Server is built with the T-Server Common Part (TSCP) release number 7.6.008.04. TSCP is the shared software that all T-Servers use. Consult the TSCP release note for information on changes to the Common Part that may affect the functionality of your particular type of T-Server.

There are no restrictions for this release. This section describes new features that were introduced in the initial 7.6 release of T-Server for Cisco CallManager.

• T-Server now supports four simultaneous JTAPI links for a Call Manager deployment with up to four Cisco CTI managers.

• T-Server has been successfully tested against the following versions of Cisco CallManager:

  • Version 4.1(3)sr1 with JTAPI 2.1(3.9).
  • Version 4.2(1) with JTAPI 2.2(1.5).
  • Version 5.1.3.2104-1 with JTAPI 3.1(3.10).
  • Version 6.0.1.2000-3 with JTAPI 6.0(1.1000)-5.

Corrections and Modifications

This release includes the following corrections and modifications that were made between Release 7.5 or earlier releases and the initial 7.6 release:

T-Server now correctly processes EventEstablished messages from the switch. Previously, T-Server could redial a new call with the same CallID and drop the call instead of distributing the EventEstablished. (ER# 141753096)

T-Server now determines the correct dialing event, and attaches user data to the correct call during predictive dialing. Previously, T-Server could attach user data to the wrong call. (ER# 111954932)

Backup T-Server now establishes a predictive call leg on Stream Manager (SM). Therefore, after a switchover, the leg is now ready to play the file on SM for the backup T-Server. Previously, in High Availability mode, a predictive call that was dialed but not established could be deleted by T-Server after a switchover. (ER# 143522934)

The default call cleanup timeout value has been increased to 100 minutes. Previously, T-Server could abandon a predictive call if multiple treatments were applied for a call in a dialing state. (ER# 147113598)

T-Server now correctly handles a large volume of messages. Previously, T-Server could become unstable with excessive SESSION_INFO messages from SM. (ER# 139950631)

T-Server now correctly handles cleanup events. Previously, T-Server could become unstable after a normal shutdown. (ER# 144120922)

T-Server now correctly applies treatments to calls that have just been transferred and both CompleteTransfer, and ApplyTreatment are issued very close to each other. Previously, T-Server responded with an Error in this scenario. (ER# 121614490)

T-Server now correctly accepts RouteCall requests when an error is being processed. Previously, T-Server could fail to route the call off a Routing Point when an EventError was distributed with an Error "Invalid state TREATMENT" message. (ER# 155570944)

T-Server now verifies that no timing issues exist when registering a media terminal and a Routing Point address on CallManager. Previously, T-Server would possibly not register some Routing Points if it was connected through Configuration Server Proxy. (ER# 121902083)

T-Server now waits until the last call is dropped to send EventAgentReady. If the completion of AfterCallWork (ACW) is interrupted by the existence of a non-customer-related (personal) call, ACW will only be completed when the last call is dropped. Previously, an agent could be left in a NotReady state when on a non-customer-related call. (ER# 146022517)

The T-Server functionality to set the Call Type based on a DNs location reported by JTAPI rather than based on Configuration Manager has been restored in 7.6. (ER# 162948116)

T-Server no longer sets an invalid Call Type after a transfer completion from a unmonitored party.

Note: See ER# 172504401 in the Known Issues and Recommendations section for more details.

(ER# 149660247)

T-Server now correctly requests SM to stop playing a treatment. If T-Server is now stopped unexpectedly, SM will stop playing a treatment based on the Keep-Alive messages between T-Server and SM. Previously, T-Server did not force SM to stop playing treatment on switchover, and a customer could hear treatments from multiple sources. (ER# 159554280)

T-Server now correctly processes moved call events (an event that comes to a consultation call after it is merged to the main call) and verifies that the correct call is released. Previously, T-Server sometimes released the main call after a ReconnectCall request. (ER# 169102968)

T-Server now properly processes AddresAddedToTerminal, AddressRemovedFromTerminal, AddressCreated, and AddressRemoved events from JTAPI, and verifies that the Extension Mobility (EM) address has the correct terminal associated with it. Previously, if an EM user shut down IP Communicator and then logged on another IP Communicator, T-Server could leave the EM address associated with the wrong terminal. (ER# 168039611)

T-Server now verifies the buffer length for incoming events. Previously, T-Server could print large amounts of debug information and become unstable under a heavy load resulting from JTAPI internal errors. (ER# 168157086)

T-Server now correctly processes alerting messages for unmonitored DNs. Previously, T-Server did not properly complete a Mute Transfer to an unmonitored internal number.

Note: See ER# 172504401 in the Known Issues and Recommendations section for more details.

(ER# 169411754)

The ISCC component of the destination T-Server fails to track call merge and destruction operations, leading to the External Routing Point being blocked after several unsuccessful attempts to route this call. (ER# 118283338)

Top of Page

Known Issues and Recommendations

This section provides the latest information on known issues and recommendations associated with this product.

Because of JTAPI limitations, when using Cisco Unified CallManager release 4.x, T-Server for Cisco CallManager does not support scenarios with Call Pickup or Auto Call Pickup features invoked for a call ringing on Shared Lines. (ER# 177974731)

If an inbound call to an unmonitored DN is mute-transferred to a monitored DN, T-Server may distribute extra EventAbandoned, and EventRinging messages after the completion of the transfer. (ER# 172504401)

If the CallManager Extension Mobility (EM) autologoff feature is turned on and an EM profile was logged in while a call is in progress on another terminal, T-Server will see this profile address as Out Of Service. To bring it back In Service, the EM profile should be logged out and logged in once again after the call is completed. (ER# 171336601)

During a Group Call Pickup or Auto Group Call Pickup of an inbound call, T-Server may distribute extra EventPartyAdded, EventPartyChanged, and EventPartyDeleted events for a Group Pickup access DN. (ER# 165260564)

If a call on an ACD Queue is transferred to an endpoint with a different codec, and Stream Manager needs to change the codec to a music treatment in the queue, T-Server stops playing the music treatment on the ACD Queue. The call, however, remains active. (ER# 147159941)

A blind conference to an ACD Queue that contains no available agents may fail. This issue is only applicable to CCM 6.0. (ER# 162516884)

A blind conference to an ACD Queue that contains no available agents may fail. (ER# 73145058)

The following phones support text messages when they have no active calls:

• Cisco 7940
• Cisco 7960
• Cisco 7970

Note: This feature is not applicable for the Cisco 7980 phone (video phone).

(ER# 101378851)

When configuring a DN of type Access Resource in the Configuration Layer for Shared Lines DNs (such as, DN@MAC1,DN@MAC2,DN@MAC3) that use any Direct ISCC transaction type, in the Advanced tab of the DN's Properties dialog box, select the Use Override check box and set a value of the DN in the corresponding field.

Example: To configure the DN 1111@MAC1 that uses the direct-notoken ISCC transaction type, in the Advanced tab of the DN's Properties dialog box, select the Use Override check box and type 1111 in the corresponding field.

If an agent in a conference call transfers the call to an external number, and then releases the call, T-Server will incorrectly report AttributeOtherDN as the external number in the EventPartyDeleted message. (ER# 6702559)

The CallType may be incorrectly marked as Internal, instead of Inbound, when an outbound call is tromboned back to the original CallManager. (ER# 96902)

Top of Page

Discontinued Support

This section documents features that are no longer supported in this software. This cumulative list is in release-number order with the most recently discontinued features at the top of the list.

The Solaris 2.6 operating system is no longer supported.

Top of Page

Internationalization

Information in this section is included for international customers.

There are no known internationalization issues for this product.

Top of Page

Additional Information

Additional information on Genesys Telecommunications Laboratories, Inc. is available on our Technical Support website. The following documentation also contains information about this software. Please consult the Deployment Guide first.

• The Framework 7.6 T-Server for Cisco CallManager Deployment Guide contains detailed reference information for the Genesys Framework 7.6 T-Server for Cisco CallManager, including configuration options and specific functionality.

• The Framework 7.6 Deployment Guide helps you configure, install, start, and stop Framework components.

• The Voice Platform SDK 7.6 .NET (or Java) API Reference and the Genesys 7 Events and Models Reference Manual and contains the T-Library API, information on TEvents, and an extensive collection of call models.

• The Genesys Migration Guide contains a documented migration strategy for each software release. Please refer to the applicable portion of this guide or contact Genesys Technical Support for additional information.

• The Genesys Licensing Guide contains information about the licensing requirements for this software. Please refer to the applicable portion of this guide or contact Genesys Technical Support for additional information.

Product documentation is also provided on a Documentation Library DVD, which is produced monthly. The New Documents on this DVD page on the DVD indicates the DVD production date. Because the DVD is produced monthly, documentation on the Technical Support website may be more up-to-date than that on the DVD. To verify the latest version of a document, check the version number, located on the second page in PDFs and on the "About This File" topic for Help files.

Top of Page