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 8.0 releases of T-Server for Cisco Unified Communications Manager.

• 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 Guide.
• 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 8.0.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 third-party functionality. For specific information on any third-party software used in this product, see the Read Me. Please contact your Genesys Customer Care representative if you have any questions.

Supported Operating Systems

New in This Release

This release of T-Server is built with the T-Server Common Part (TSCP) release number 8.0.101.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 contains the following new feature or functionality.

• T-Server now correctly handles route and treatment requests that occur immediately following the completion of transfers and conferences. Previously, such requests sometimes failed because the transfer or conference not being completed entirely on the switch. This is a time-sensitive problem that does not always occur. (TCISCOUCM-218)

Corrections and Modifications

This release includes no corrections or modifications.

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 8.0.101.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 ignores the DN_OUT_OF_SERVICE or JTAPI_ADDR_REMOVED JAVA events if they are received on a different link, and without a terminal name. This prevents T-Server from "unobserving" the address on the switch and incorrectly distributing EventDNOutOfService for such DNs. This is controlled by the restricted ignore-oos-from-other-link option, which has a defaults value of true. (TCISCOUCM-1646)

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 8.0.101.16. 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 experiences thread deadlock between the register address request thread and the CallChangedEvent thread. (ER# 284265621)

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 8.0.101.12. 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 allows multiple T-Requests to be sent to the link within the same time period, and ensures that all client requests are properly serialized. (ER# 272251170)

T-Server, in hot standby mode, no longer generates an unexpected EventAgentReady event after being promoted to primary T-Server. Previously, the newly promoted primary T-Server may have generated an unexpected EventAgentReady event due to the incorrect processing of synchronization data by the backup T-Server; which incorrectly invoked the soft-wrap-up timer. (ER# 278699020)

When the RouteType attribute of a RequestRouteCall request is set to RouteTypeOverwriteDNIS, the value of the DNIS attribute will now be set to the value of preferredOriginalCalledParty. (ER# 278292900)

T-Server no longer links internal and external parties (DNs) as shared/bridged. Previously, T-Server treated internal and external parties with the same digits as shared/bridged, which may have caused an EventReleased event to be sent for both parties, even if only the external party released the call. (ER# 277433935)

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 8.0.101.12. 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 contains the following new features or functionality:

• For this specific release, T-Server supports Hunt Groups on Cisco Unified Communications Manager (UCM) 8.0. To support this feature, two new Application-level configuration options have been added. HUNTLIST_ENABLED in the jtapi section, and ignore-cisco-cause-500 in the globalgroup section.

  Note: For this feature to properly function, all HuntPilot DNs need to be removed from Configuration Manager.

  HUNTLIST_ENABLED
  Default value: true
  Valid value: true, false
  Changes Take Effect: After restart

  When set to true, JTAPI activates Hunt Group support.

  ignore-cisco-cause-500
  Default value: true
  Valid value: true, false
  Changes Take Effect: After restart

  When set to true, T-Server removes extra messages that are generated during conference and transfer calls.

Note: This is a restricted feature. This specific point release of Genesys T-Server and Cisco UCM v8.0.(3)SU2 are the only supported combination.

• Cisco UCM 8.5 support. T-Server has been successfully tested against CUCM version 8.5.1.10000-26 with JTAPI version 8.5(1.10000)-1.

Corrections and Modifications

There are no corrections or modifications in this release of T-Server for Cisco UCM.

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 8.0.101.12. 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.

Corrections and Modifications

This release includes the following corrections and modifications:

T-Server now correctly applies the Agent After Call Work (ACW) state to an agent when the main call is dropped while a consultation call is still in a Dialing state. Previously in this scenario, T-Server did not apply the ACW state if the consultation call was not established and the main call was released. (ER# 270512707)

Primary T-Server now correctly sends Back-In-Service events, when operating in hot standby mode, and a switchover is caused by a network failure between JTAPI and CTI-Manager, and the configuration option send-backinservice-after-switchover is set to a value of true. Previously in this scenario, the primary T-Server may not have distributed Back-In-Service events. (ER# 269671186)

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 8.0.101.11. 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.

Corrections and Modifications

This release includes the following corrections and modifications:

T-Server, in hot standby mode, now correctly determines if URS is connected after switchover to the backup T-Server, and does not attempt to route all calls to the default destination. Previously, the backup T-Server, in hot standby mode, could redirect the call to the default DN if the use-default-route option was set to a value of true. (ER# 267736266)

T-Server now completes transfer or conference requests as soon as the switch is ready, and does not cause extra wait time. Previously, T-Server may have introduced a delay between receiving a conference or transfer request from a client and the actual completion of the transfer or conference. This delay may have also interfered with the subsequent routing of consult calls. (ER# 267363796)

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 8.0.101.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.

Corrections and Modifications

This release includes the following corrections and modifications:

T-Server, in hot standby mode, no longer applies the default routing algorithm when it is the backup T-Server. Previously, the backup T-Server, in hot standby mode, could redirect the call to the default DN if the use-default-route option was set to a value of true. (ER# 264059353)

T-Server, in hot standby mode, now checks the High Availability (HA) role and does not issue disconnect requests when it is the backup T-Server. Previously, the backup T-Server, in hot standby mode, could disconnect a predictive call if the destination was busy. (ER# 263568857)

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 8.0.101.01. 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.

Corrections and Modifications

This release includes the following correction and modification:

Previously, when Universal Routing Server (URS) attempted to route a consult call, and the route request was executed in between the JTAPI consult request and the corresponding JTAPI event (CiscoTransferStartEv or CiscoConferenceStartEv), the call transfer or the conference call failed on the CUCM switch. T-Server now delays the processing of RequestRouteCall requests until a corresponding StartEv message arrives from JTAPI.

Note: This workaround only works if the transfer or conference was completed using a T-Server (3PCC) CTI request, not manually on an agent phone.

(ER# 260758790)

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 8.0.101.01. 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.

Corrections and Modifications

This release includes the following corrections and modifications:

T-Server now analyzes the CiscoCause attribute of JTAPI messaging to separate the release of an external party due to a real hangup in scenarios where the call is being torn down on one JTAPI link, while still alive on another JTAPI link. Previously, in a multilink environment, when a conference call was established between an external party and two monitored parties on different links, T-Server may have mistakenly deleted the external party from the conference if the conference controller left the call. (ER# 258103043)

T-Server now retains the OutOfService cause code provided by JTAPI when the CAUSE_DEVICE_UNREGISTERED code is generated. T-Server now sets the Extension Mobility (EM) address to BackInService during EM login and registration. Previously, T-Server may have set the EM DN into an OutOfService state after EM logout and login. (ER# 257592621)

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 8.0.101.01. 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 8.0.1 release of T-Server for Cisco Unified Communications Manager.

• T-Server now supports the ability to independently specify a partition with a DN (number) whether it is unique or not. Starting with release 8.0.1, T-Server supports the configuration of DNs in Configuration Manager in the form of 6002[PART1] or 6002[PART1]@SEP000125675, even if 6002 has only one partition.

• Support for multiple T-Servers per switch configuration. T-server now supports a configuration of multiple T-Servers to a single Cisco Unified Communications Manager switch, allowing proper call type reporting for agents on different T-Servers.

• Support for Call Parking with 3PCC (Third Party Call Control).

• Support for new T-Server HA configuration option. The switchover-on-first-link-failure option has been added to force failover to the backup T-Server for all JTAPI links upon failure of one JTAPI link (or associated CTI Manager).

  switchover-on-first-link-failure
  Default Value: true
  Valid Values: true, false
  Changes Take Effect: Immediately
  
  

  When set to false, T-Server sets DNs from the failed link to out-of-service, and will not trigger switchover if at least one JTAPI link remains active. When set to true, T-Server immediately reports LinkDisconnected to SCI after the first JTAPI link fails; SCS then triggers the switchover.

• Support for the Cisco UCM 7.1 feature Drop Any Party From Conference.

• T-Server 8.0.1 supports all versions of Cisco UCM 8.0.x and all versions of JTAPI supported by these releases of Cisco T-Server, and has been successfully tested against CUCM version 8.0.2.10000-24 with JTAPI version 8.0(2.10000).

• T-Server now supports the T-Library request RequestSingleStepTransfer.

Corrections and Modifications

This release includes the following corrections and modifications:

T-Server now properly accepts subscriptions from two supervisors to monitor AllCalls for the same agent. Previously, the first supervisor was immediately added to the existing call, and T-Server incorrectly added the second supervisor to all subsequent calls for the agent until the second supervisor canceled the subscription. (ER# 227343831)

An attempt to initiate emergency recording no longer fails if regular recording on the call has already started. (ER# 220555373)

T-Server now correctly reports the DNIS attribute for NetworkReached and Established events. Previously, T-Server did not correctly report these attributes in certain scenarios. This resolves a backward compatibility issue from release 7.2. (ER# 233747958)

T-Server now monitors the number of unsuccessful connection attempts to the CUCM CTI Manager, and stops connection retries after 10 consecutive failures. This limits the number of defunct processes generated. T-Server will resume the CUCM connection after the CME link configuration has changed. Previously, T-Server created numerous defunct processes if the ccm-host was configured incorrectly, or when JTAPI could not connect to the CUCM CTI Manager. (ER# 220487613)

T-Server now retrieves the partition name, even if the address is from a different JTAPI link, which provides sufficient information for correct party matching. Previously, the CUCM partitioning feature may not have worked correctly in deployments where multiple JTAPI links were used, and a call was made from an address with multiple partitions to an address on a different JTAPI link. In this scenario, the second link did not retrieve partition information about the other address. (ER# 238444008)

T-Server now catches all exceptions associated with parsing of incoming requests, and does not abort subsequent operations. Previously, T-Server may have stopped sending 3pcc requests to JTAPI if special characters ",',@,[,] were used in request attributes, as it encoded extra information into the DN name. (ER# 228163278)

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# 219869424)

T-Server now retrieves the locality from Released events, and uses the locality for correct party matching. Previously, T-Server did not account for the locality of the DN in the CallCtlConnDisconnected JTAPI event for the Quiet Clear scenario. As a result, this party may not have been released from the call. (ER# 245841371)

T-Server now retrieves the correct RTP IP address from the HELLO message, and replaces the one created during Stream Manager connection. Previously, T-Server ignored the RTP IP address provided by Stream Manager, and used the default IP address of Stream Manager. (ER# 227612855)

T-Server now reads the correct values for the following options during startup, and passes them to JTAPI:

• TServerTraceFileBase
• TServerTraceFileExt
• TServerTraceMaxFiles
• TServerTraceMaxFileSize

Previously, T-Server may have incorrectly reported the following diagnostic (Reason: too slow). This issue has been corrected in the T-Server Common Part. (ER# 233272827)

T-Server now checks the address name and exact terminal name from JTAPI events to ensure the correct party is selected for call merge events. Previously, T-Server may have distributed extra EventPartyAdded, and EventPartyDeleted events to T-Library clients during merge scenarios, as a result of using the wrong terminal name. (ER# 176018972)

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.

Corrections and Modifications

This release includes the following corrections and modifications:

T-Server now uses correct tone values during recording. Previously, T-Server used incorrect recording tone values, which caused Stream Manager to record repeating beeps. (ER# 240383401)

T-Server now uses the correct monitor tones according to Cisco JTAPI specifications. Previously, T-Server used incorrect Supervisor Monitor tones while monitoring an Agent, which caused the Supervisor and Agent to hear constant beeps. (ER# 240935515)

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.11. 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 8.0 release of T-Server for Cisco Unified Communications Manager.

• Support for Call Recording.

• Support for Supervisor Monitoring.

• Support for DNs that have the same number, but are located in different partitions on Cisco Unified Communications Manager.

• T-Server now only supports the socket mode of communication with the JTAPI library. The JNI mode has been discontinued.

• Support for Customer Matters Code (CMC) and Forced Authorization Code (FAC), also known as Account Codes.

• Support for the retrieval and distribution of modified CLID.

• Support for the separate logging of JTAPI failures if a Socket connection is broken, or not established yet.

• The switch name has been changed to Cisco Unified Communications Manager (CUCM).

• T-Server has been tested with CUCM 7.0.1.11000-2 with JTAPI 7.0(1.1000).

• T-Server has been tested with CUCM 7.1.2.20000-2 with JTAPI 7.1(2.10000)-3.

• T-Server now supports the following operating systems:

  • AIX 32/64 bit version 6.1
  • Red Hat Enterprise Linux AS Edition on 32-bit Intel platforms, version 5.0
  • Microsoft Windows Server 2008

Corrections and Modifications

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

T-Server now includes the -Xrs Java option by default to reduce the handling of system signals. (ER# 204461621)

To perform logging in situations where the network connection between JTAPI and T-Server becomes unavailable, T-Server now writes severe error conditions to a set of log files, rotating among them as each becomes filled to a specified capacity. Each log file is named according to a pattern controlled by the properties, TServerTraceFileBase, and TServerTraceFileExt. The TServerTraceFileBase property determines the prefix of each log file name, and the TServerTraceFileExt property determines the suffix (for example, log). The property TServerTraceMaxFiles determines the number of files allowed in a set before the first one is overwritten. The property TServerTraceMaxFileSize determines the maximum file size (in bytes) for each individual file.

The following new options have been added to the jtapi section on the Options tab of the T-Server Application object:

• TServerTraceFileBase (default value: ts_trace)
• TServerTraceFileExt (default value: log)
• TServerTraceMaxFiles (default value: 10)
• TServerTraceMaxFileSize (default value: 100)

A sample fragment of a new log file is as follows:
0: @2009/02/16 10:02:59 IOException in TS input thread. Exiting.

T-Server now checks the DN state rather than the call state when validating TRedirectCall requests. Previously, T-Server was sometimes unable to redirect a call, even if the DN was in the ringing state. (ER# 225206163)

T-Server now verifies the Call State, and returns an error, if a client attempts to issue a TRedirectCall request for a call in an established state. Previously, T-Server would allow the redirection of a call that was in an established state, which is not a valid T-Library request. (ER# 186232188)

T-Server now closes the log subsystem before initiating a Java child process. Previously, T-Server kept the initial log file locked by a child Java process. (ER# 199750537)

T-Server now properly identifies the cause of an OutOfServiceEvents event from JTAPI and correctly processes the startup snapshot of OutofService events. In doing so, the correct agent states are preserved. Previously, when configured for an High Availability environment, T-Servers could have reported an incorrect agent state after a double switchover. (ER# 139550274)

The Java subsystem now only prints essential information and monitors for the maximum data that can be sent over a socket connection to T-Server. Previously, error events during completion of a call that was conferenced or transferred could have resulted in printing JDump debug information that exceeded the incoming socket capacity of T-Server. (ER#  209885098)

T-Server now filters the JTAPI out of service events, and ignores the ones that were caused by a regular link cleanup after a CTI manager failure. (ER# 221085679)

T-Server now sets calls between an UnParking address and a parking device to the Internal call type. Previously, during the unparking of a call, the call type was set incorrectly if the main call was Inbound. (ER# 183965526)

T-Server now properly terminates the IP_PHONE_DISPLAY text on a telephone by using <ExecuteItem URL="Init:Services"/> as recommended by Cisco. (ER# 185592585)

When the keep alive options are set, JTAPI also initiates keep alive messages to verify if T-Server is responding. After a specified timeout and a number of retries, Java will print a message in the JTAPI enhanced log, and will quit. Previously, keep alive messages were initiated only from the T-Server to the JTAPI process. Under some conditions, this may have lead to JTAPI processes not responding. (ER# 211096416)

T-Server now checks the LinkID for incoming events and verifies that the corresponding treatment requests are executed after the events came from the correct link. Previously, a in multi-link configuration, T-Server may have failed to apply a treatment if the network latency for different links was high for JTAPI events. (ER# 210396748)

T-Server now delays the processing of the RequestRouteCall from Universal Routing Server (URS) until a corresponding CiscoTransferStartEv or CiscoConferenceStartEv message from JTAPI is received. This only applies if the completion of a transfer or conference call is done with a T-LIB request rather than manually on the telephone. Previously, if a URS route request was executed between a JTAPI consultation request and a corresponding JTAPI CiscoTransferStartEv or CiscoConferenceStartEv request, the transfer or conference call would fail on the CUCM switch. (ER# 214543118)

A new restricted option called update-calls-after-swover 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.

update-calls-after-swover
Default Value: 0
Valid Values: 0–10000
Changes Take Effect: Immediately

A new primary T-Server will query JTAPI for existing active calls to ensure synchronization with the switch when the number of switchovers exceeds the value set by this option. The default value of 0 (zero) disables the functionality of this option.

(ER# 199169222 )

T-Server now correctly handles both ISCC connect and reconnect operations between T-Servers. (ER# 212907691)

Two new restricted options, call-ended-timeout and use-jtapi-call-deleted, have been added to T-Server.

These options are configured in the globalgroup section on the Options tab for the T-Server Application object in the Configuration Layer.

call-ended-timeout
Default Value: 2000
Valid Values: 0–Maximum Integer
Changes Take Effect: Immediately

Specifies the amount of time, in milliseconds, that T-Server waits to delete the call when a JTAPI CallInvalidEv event is sent to T-Server. If the timeout is set to 0, the call will be deleted immediately. This option should be used in conjunction with the restricted use-jtapi-call-deleted option.

use-jtapi-call-deleted
Default Value: false
Valid Values: true, false
Changes Take Effect: Immediately

When this option is set to true, after receiving the JTAPI message CallEnded (CallInvalidEvent), T-Server will delete the call in the amount of time (in milliseconds) specified by the call-ended-timeout option.

(ER# 215934851)

Java child processes will now explicitly close log fragments after T-Server is started. Previously, this log fragment was kept opened by the Java child process. Under some conditions, T-Server may have modified this log file. (ER# 210085424)

T-Server now correctly processes the removal of DNs with type Routing Point or ACD Queue from Configuration Manager and reports the correct DN numbers in EventQueued and EventRouteRequest events. Previously in some scenarios, T-Server reported an incorrect DN number in EventQueued and EventRouteRequest events if a Routing Point or an ACD Queue DN was deleted from Configuration Manager while T-Server was running. (ER# 216984477)

Support for the originating-timeout option has been added to T-Server. Configure this option in the gctm section on the Options tab for the T-Server Application object in the Configuration Layer. The option description and values for originating-timeout are:

originating-timeout
Default Value: 1800000 (30 minutes)
Valid Value: 0 - Maximum Integer
Changes Take Effect: Immediately

When set, this option will indicate the longest non-established call (in milliseconds) before T-Server deletes the call from memory as abandoned. This option can be used for predictive calls if the treatment duration is longer than 30 minutes.

(ER#  185288991)

Top of Page

Known Issues and Recommendations

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

The RequestAnswerCall request fails in this specific third-party call control (3PCC) shared line scenario:

1. The shared line DN1 invokes RequestMakeCall to DN2 which answers.
2. DN2 initiates a RequestInitiateTransfer request to DN3.
3. DN2 then sends RequestCompleteTransfer.
4. DN3 attempts RequestAnswerCall, but it fails due to an unspecified Cisco JTAPI Exception.

This call flow works correctly when done manually using first party call control.

(ER# 275804615)

Call forwarding can not be applied to DNs that are members of a Hunt Group. A call arriving on a DN via the Call Pilot will ring on the DN despite the previous attempt to set forwarding to another destination. (ER# 260169588)

For scenarios that involve the two-step transfer of an internal call between hunt lists, and depending on the call duration, T-Server may distribute extra EventNetworkReached and EventPartyChanged events immediately before the call is ended. These events can be safely ignored. (ER# 273788144)

When parking a call using a 3PCC park request, T-Server distributes PARK_ADDRESS in the Key Value pair of the Extensions attribute, not PARK_DN as documented in the Framework 8.0 T-Server for Cisco Unified Communications Manager Deployment Guide. (ER# 258461733)

When a call is unparked from a parking DN, T-Server may distribute an unexpected EventNetworkReached event to T-Library clients. (ER# 247424735)

During an inbound call with a MuteTransfer to a Route Point (RP), T-Server may distribute an unexpected duplicated EventPartyChanged event. (ER# 243968326)

Delete Shared Line from conference will lead to an Error (Timeout), if the otherDN attribute points to a shared line party in a bridged state. Delete Shared Line from conference, when the shared line is in a held state, is not supported by T-Server. (ER# 255964272)

In a CUCM cluster distributed environment controlled by T-Server, JTAPI may report the wrong call type for consult calls. This issue has been reported to the vendor. (ER# 252267984)

A Monitoring Session is not started in scenarios where T-Server receives a RequestMonitorNextCall at the moment an agent is placed on hold. (ER# 227371541 )

T-Server incorrectly accepts subscriptions from two supervisors to monitor AllCalls for the same agent. The first supervisor is immediately added to the existing call, and T-Server incorrectly adds the second supervisor to all subsequent calls for the agent until the second supervisor cancels the subscription. In scenarios where T-Server accepts subscriptions from two supervisors before the call is accepted by an agent, only the second supervisor will be connected to all subsequent calls for the agent. (ER# 227343831)

A supervisor in Whisper Coaching mode is unable to hear all call participants. Only an agent can hear the supervisor in Whisper Coaching mode. In order to hear all call participants, the supervisor should switch back to Silent Monitoring mode using the TMuteOn request.

An attempt to initiate emergency recording will fail if regular recording on this call had been already started. (ER# 220555373)

T-Server ignores the value of the queue-music option specified on the ACD DN level, and instead selects the music file specified in the queue-music option on the T-Server application level. As a workaround, to play music as specified on the DN level, configure the music option instead. (ER# 226442331)

A supervisor is inadvertently released from the call when an agent on a monitored consultation call completes a two-step conference. (ER# 226882076)

Because of JTAPI limitations, when using Cisco Unified Communications Manager release 4.x, T-Server for Cisco Unified Communications Manager 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 Unified Communications Manager 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 CUCM 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 Unified Communications Manager. (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 Windows Server 2000 32 bit 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 Customer Care website. The following documentation also contains information about this software. Please consult the Deployment Guide first.

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

• The Framework 8.0 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 Customer Care 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 Customer Care for additional information.

Product documentation is provided on the Customer Care website, the Genesys Documentation website, and the Documentation Library DVD (produced monthly) or the Developer Documentation CD.

Note: For the DVD/CD, the New Documents on this DVD/CD page indicates the production date for that disc. Due to disc production schedules, documentation on the Genesys Documentation website may be more up-to-date than what is available on disc immediately after a product is released or updated. To determine the version of a document, check the version number that is located on the second page in PDFs or on the About This File topic in Help files.

Top of Page