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.genesys.com for more details.

This release note applies to all 8.1 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 operating systems available for use with each component release are listed in the table at a high level only. For more detailed information about the supported operating environments, including requirements, supported versions, and any conditions or limitations, see the T-Server Cisco Unified Communications Manager page in 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.5.x. or T-Server Common Part release 8.1.x.

Use of Third-Party Software

Genesys follows applicable third-party redistribution policies to the extent that Genesys solutions utilize third-party functionality. For additional information on third-party software used in this product, see More Release Information/Legal Notices for T-Servers. Please contact your 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.5.000.37. 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 an update for this product. This release contains the following new features or functionality:

• Support for Cisco Unified Communications Manager (CUCM) switch version 15.0.1.11901-2.

Corrections and Modifications

This release includes the following corrections or modifications:

CUCM 14 introduced new requirements for FIPS enabled connections which previously caused T-Server�s JTAPI interface client to fail to properly start, when FIPS is enabled on the switch. The failure during start is corrected in this version of T-Server by adding support for configuration of additional jar files, required by JTAPI FIPS, with additional support for enforcement of FIPS on the client side.

FIPS enabled secure connection requirements

To download the files,

1. Log in to CUCM Administration as an administrator.
2. Navigate to the path: Application/Plugins.
3. Search for the installation where "Name" "Contains" "JTAPI".
4. Download the required files.

New options in the 'link-tls' Section

New options in the 'TServer' Section

• [path1], [path2], etc. are paths to the jar files you want to add to the class path.


• The path separator is ';' (semicolon), this separator can be used for either Windows or Linux systems. Users can specify paths using either POSIX-style forward slashes (/), check_mark, or Windows-style backslashes (\). The application will convert the path separators to the appropriate style based on the operating system where T-Server is running.

For example, ./cryptoLibs/jcmFIPS.jar;./cryptoLibs/sslj.jar;./cryptoLibs/cryptojcommon.jar;./cryptoLibs/cryptojce.jar

updater-java-class-path
Section: TServer
Changes Take Effect: Immediately
Value: [path1][;path2]...
Where:
[path1], [path2], etc. are paths to the jar files you want to add to the class path.
Allows user to add additional jar files to the Java class path, which will be used when launching T-Server's JTAPI updater application. (TCISCOUCM-2641)

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.5.000.35. 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 no new features or functionality.

Corrections and Modifications

This release includes the following corrections or modifications:

This version of T-Server addresses an issue which might cause T-Server to become unresponsive when it receives either the EventRtpStarted or EventRtpEnded events on a DN before the call is constructed, followed by an event (call create type of event) for the same call, but for a different DN. (TCISCOUCM-2629)

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.5.000.32. 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 an update for this product. This release contains the following new features or functionality:

• A new semi-hidden Boolean configuration option x-iscc-msg-log-improved in the Log section is now introduced which can prevent splitting ISCC messages between the two log files.

  [Log].x-iscc-msg-log-improved
  Default Value: false
  Valid Values: true, false
  Changes Take Effect: After restart

  If option set to false, the default behavior is preserved. If the option set to true, T-Server Common Part will prevent ISCC messages from being split between the two log files.
  

  (TS-12129)

• A new semi-hidden Boolean configuration option reasons-purge-improved is now introduced in the TServer section.

  [TServer].reasons-purge-improved
  Default Value: false
  Valid Values: true, false
  Changes Take Effect: Immediately

  If this option is set to false, then current T-Server behavior is preserved. T-Server will clear persistent reasons only if it receives a request with an empty AttributeReasons. If this option is set to true, T-Server will clear persistent reasons even if next request contains no AttributeReasons.
  

  (TS-12130)

Corrections and Modifications

This release includes the following corrections and modifications:

This version of T-Server addresses an issue which can prevent the distribution of RTP EventUserEvent. The issue relates to an ordering problem in messages received by T-Server. It occurs when T-Server receives the RTP_STARTED message before T-Server is notified that the corresponding party exists (is created). To address this issue, T-Server will now redistribute RTP_STARTED or RTP_ENDED with a slight delay, in cases where the party is not found to exist in T-Server, during the processing of these messages.

A new option controls the delay on processing when T-Server detects an out of order condition in RTP events:

unhandled-distribution-delay
Default Value: 250
Range: 0 - 60000 (0 disables the delay)
Visibility: semi-hidden

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.5.000.25. 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 an update for this product. This release contains no new features or functionality.

Corrections and Modifications

This release includes the following corrections and modifications:

This version of T-Server corrects stability issues-related problem in T-Server. Previously, if a client registered and logged on to a DN that is not listed in CME and the registration type used for this DN during registration by the client was not AddressTypeDN, T-Server may experience stability issues including a potential crash. This problem was found and fixed inside GCTM starting with version 8.5.002.11. (TCISCOUCM-2616, TS-12162)

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.5.000.25. 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 an update for this product. This release contains no new features or functionality.

Corrections and Modifications

This release includes the following corrections and modifications:

T-Server now updates the JTAPI.jar file before starting the links. This avoids permission-related issues while starting the Java processes that connect to the switch. (TCISCOUCM-2607)

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.5.000.25. 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 an update for this product. This release contains no new features or functionality.

Corrections and Modifications

This release includes the following corrections and modifications:

In specific looped call scenarios, T-Server can now release the external originating party on the original call when a release event is received from the switch on the looped call. This behavior occurs if the original call contains only unmonitored parties.

A new option controls this behavior:

clear-orig-ext-looped
Section: globalgroup
Valid Values: true, false
Default Value: true
Changes Take Effect: immediately

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.5.000.25. 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 an update for this product. This release contains the following new features or functionality:

• A new restricted option, globalgroup/term-reg-events, is added to allow T-Server to enable terminal register and unregister JTAPI events from the switch.

  term-reg-events
  Section: globalgroup
  Default: false
  Valid Values: true, false
  Changes Take Effect: Next time a DN goes out-of-service/back-in-service

  Turns on or off terminal register and unregister JTAPI events from the switch. This ensures that T-Server is informed of DNs coming in service when agents move from Jabber phones to regular phones.

  (TCISCOUCM-2571)

Corrections and Modifications

This release does not include any corrections.

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.5.000.25. 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 an update for this product. This release contains no new features or functionality.

Corrections and Modifications

This release includes the following corrections and modifications:

In the rare case where a TMakeCall request occurs at the same time a call arrives at the same DN, T-Server no longer copies UserData from the TMakeCall request to the inbound call. (TCISCOUCM-2581)

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.5.000.25. 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 an update for this product. This release contains the following new features and functionality:

• T-Server now provides a way to configure the keep-alive ping for media connections using the new options in the globalgroup section. In addition, T-Server now logs each ping attempt, similar to:

  @17:11:05.4050 [cm] SM 1 StreamMan ping 1 of 15 failed. Try again in 10000 ms...

  SM-ping-timeout
  Default Value: 10000
  Valid Values: Any integer
  Changes Take Effect: After next timeout
  Specifies the time period, in milliseconds, during which T-Server pings the media connection.

  SM-ping-timeout-count
  Default Value: 3
  Valid Values: Any integer
  Changes Take Effect: After next timeout
  Specifies the number of unsuccessful pings after which T-Server disconnects the media connection.

  (TCISCOUCM-2573)

Corrections and Modifications

This release includes the following corrections and modifications:

T-Server now waits for in-service notification from the switch before distributing EventDNBackInService after an out-of-service DN goes back in service on the same terminal. Previously, when the switch responded with destination invalid messages for a DN that was out of service, T-Server incorrectly continued sending calls to that DN. (TCISCOUCM-2572)

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.5.000.25. 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 release contains the following new functionality:

• Starting with this release, T-Server requires FlexNet Publisher License Manager version 11.16 or later.

Corrections and Modifications

This release includes the following corrections or modifications.

T-Server now distributes EventTreatmentApplied if the treatment is successful during a race condition caused by a treatment request immediately followed by a transfer completion. (TCISCOUCM-2559)

T-Server now correctly distributes EventNetworkReached and EventEstablished for outbound extend-and-connect calls. (TCISCOUCM-2557)

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

There are no restrictions for this release. This release contains the following new features or functionality:

• Support for Oracle and OpenJDK 1.8 and higher. See the Supported Operating Environment: T-Server Cisco Unified Communications Manager page for more detailed information and a list of all supported operating systems. (TCISCOUCM-2552)

• Support for Red Hat Enterprise Linux 8, 64-bit. See the Supported Operating Environment: T-Server Cisco Unified Communications Manager page for more detailed information and a list of all supported operating systems.

Corrections and Modifications

This release includes the following corrections or modifications.

T-Server now distributes the correct events for a single-step transfer even when the switch message for the destination does not include the transfer controller. (TCISCOUCM-2549)

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

There are no restrictions for this release. This release contains the following new features or functionality:

• Support for Extension Mobility (EM) with shared lines configured using the @MAC prefix. Added January 2021. (TCISCOUCM-2521)

Corrections and Modifications

This release includes the following corrections or modifications.

T-Server no longer blocks the main provider Java thread when starting address registrations. This change avoids addresses being flagged as out of service in T-Server when they are actually in service on the switch. (TCISCOUCM-2547)

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

There are no restrictions for this release. This release contains the following new features or functionality:

• A new configuration option, override-call-type, specifies a call type for internal calls that land on a routing point and have not been yet assigned a call type. This option addresses the need to assign a call type of outbound to calls initiated during predictive campaigns.

  override-call-type

  Setting: DN object [of the dialed routing point], Annex tab, [TServer] section
  Default: 0 [no override]
  Valid values:

  • 0 [no override]
  • 3 [sets call type to outbound]
  Changes take effect: on the next call
  

  Sets the call type of internal calls arriving at the specified routing point.

  (TS-11950)

Corrections and Modifications

This release includes the following corrections or modifications.

In complex multisite scenarios involving more than two sites, where a call returns to the original site, T-Server no longer duplicates AttributeFirstTransfer and AttributeLastTransfer attributes in corresponding events. (TCISCOUCM-2539)

When acw-trigger=ring, the agent making a consultation call now receives an EventAgentNotReady (ACW) event regardless of the order in which the consultation and originating calls are released. Previously, the agent would not go into ACW if the originating call was released first. (TCISCOUCM-2529)

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

There are no restrictions for this release. This release contains the following new features or functionality:

• A new option, ignore-external-established-looped, prevents an external party from being established or created in a specific looped call flow, enabling ISCC to determine OtherDN in EventPartyDeleted.
  
  ignore-external-established-looped
  Values: true, false
  Default: false
  Effective: immediately
  When true, prevents an external party from being established or created in a specific looped call flow. This allows ISCC to determine OtherDN in EventPartyDeleted. (TCISCOUCM-2522)

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

There are no restrictions for this release. This release contains no new features or functionality.

Corrections and Modifications

This release includes the following corrections or modifications:

T-Server now specifies CallStateSitNocircuit in EventReleased when a call fails with Cisco cause code CAUSE_RESOURCES_NOT_AVAILABLE (107). (TCISCOUCM-2523)

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

There are no restrictions for this release. This release contains no new features or functionality.

Corrections and Modifications

This release includes the following corrections or modifications:

In a multisite scenario, if call routing from a local site to a destination site fails, T-Server now reports an ISCC (multisite) transaction as terminated. Previously, T-Server incorrectly reported this transaction as completed. (TCISCOUCM-2514)

T-Server now attempts to send a queued call to a ready agent even if an invalid state exception occurs during the setup of the queue. This can occur if there is a problem with the queue configuration on the switch. EventHardwareError may also be distributed when this invalid state exception occurs, to notify clients of a problem with the treatment. This change does not solve the switch issue, so music or treatment may not occur, but the call should still be sent to a ready agent. (TCISCOUCM-2503)

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.5.000.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 contains no new features or functionality.

Corrections and Modifications

This release includes the following corrections or modifications:

T-Server now enables the transfer controller to be re-added to the call in the rare event of a failed transfer completion. To enable this behavior, set the option recreate-failed-transfer-controller to true.

recreate-failed-transfer-controller
Values: true, false
Default: false
Effective: immediately
In the rare case that a transfer completion fails, T-Server may have already removed the controller from the caller. Setting this option to true causes T-Server to recreate the controller in the call in an attempt to correct the call model. (TCISCOUCM-2501)

A new globalgroup option, switch-query-port, specifies the HTTP port number used to query the switch for version information. T-Server logs this in the following format:

@09:05:35.3520 [**1] 1 82 S 137 'Querying cti-host �135.17.64.10:8080� for installed version of jtapi.jar.'

T-Server now includes AttributeThisDN in EventHardwareError for conference and transfer error codes 96 and 98. This addition enables the error to be distributed to clients, which can in turn inform the agents and/or take corrective action. (TCISCOUCM-2499)

For Cisco UCM switches v.12.0 or 12.5, when a call involving SIP telephones is transferred to an external destination by a TSingleStepTransfer request, the messaging may be incorrect. TServer now correctly handles these cases. (TCISCOUCM-2494)

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

There are no restrictions for this release. This release contains no new features or functionality.

Corrections and Modifications

This release includes the following corrections or modifications:

Supervisor monitoring now works for a dialing agent when the supervisor is registered on a different link than the agent. (TCISCOUCM-2488)

When a call drops during routing, T-Server now distributes EventAbandoned in addition to EventError. Previously, the error prevented the call from being properly released. (TCISCOUCM-2472)

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

There are no restrictions for this release. This release contains the following new features or functionality:

• Support for the Windows Server 2019 operating system and Windows 2019 Hyper-V virtualization. See the Supported Operating Environment: T-Server Cisco Unified Communications Manager page for more detailed information and a list of all supported operating systems. (TCISCOUCM-2460)

• Support for Cisco Unified Communications Manager Versions 12.0 and 12.5. (TCISCOUCM-2301, TCISCOUCM-2436)

• A new option, ignore-tc-events, enables T-Server to better handle the release of an external party while a transfer or conference is being completed. Previously, in some cases T-Server ignored the release if the events for it were received during the transfer/conference completion phase. To enable the new behavior, you must set ignore-tc-events to false.

  ignore-tc-events
  Values: true, false
  Default: true
  Effective: immediately
  If set to true, T-Server ignores specific JTAPI events that are received during the transfer/conference completion phase of calls. This is the old way of handing such calls. If set to false, T-Server uses a more intelligent buffering mechanism to ensure that the end state of the call is correct.
  

  (TCISCOUCM-2474)

Corrections and Modifications

This release includes the following corrections or modifications:

T-Server no longer prevents link connection if remote port 80 is blocked. (TCISCOUCM-2495)

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

There are no restrictions for this release. This release contains the following new features or functionality:

• Jabber v. 12.x, including the new multi-line feature, is now supported. (TCISCOUCM-2394)

• Several new options improve business call handling and ACW behavior:

  acw-trigger
  Values: any, ring
  Default: any
  Effective: immediately
  If "any", ACW occurs for any agent after call release.
  If "ring", ACW occurs only for agents that were rung.
  
  inbound-bsns-calls
  Values: true, false
  Default: false
  Effective: immediately
  When true, T-Server considers all established inbound calls on an agent as business calls.
  
  outbound-bsns-calls
  Values: true, false
  Default: false
  Effective: immediately
  When true, T-Server considers all established outbound calls on an agent as business calls.
  
  internal-bsns-calls
  Values: true, false
  Default: false
  Effective: immediately
  When true, T-Server considers all established internal calls on an agent as business calls.
  
  unknown-bsns-calls
  Values: true, false
  Default: false
  Effective: immediately
  When true, T-Server considers all established calls of an unknown type on an agent as business calls.
  
  inherit-bsns-type
  Values: true, false
  Default: true
  Effective: immediately
  When true, T-Server inherits the business call behavior between main and consult calls.
  

  (TCISCOUCM-2424)

Corrections and Modifications

This release includes the following corrections or modifications:

T-Server no longer times out on RequestRouteCall in a very specific race condition scenario, where a consult call is routed at the same time the transfer is completed. (TCISCOUCM-2439)

When Stream Manager or UCMC Connector connections fail, the backup T-Server no longer attempts to route calls. This modification avoids unexpected side effects such as dropped calls. (TCISCOUCM-2430)

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

• T-Server now distributes EventReleased events before EventRouteRequest events during a single-step transfer to a routing point, even if switch messages are received in reverse order. (TCISCOUCM-2382)

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

• This initial release of T-Server 8.1.5 adds support for Microsoft Visual Studio 2013 and withdraws support for Microsoft Visual Studio 2008 and earlier. (TCISCOUCM-2384)

  Important: This release is not available on the AIX and Solaris platforms.

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

• Several new options improve business call handling and ACW behavior:

  acw-trigger
  Values: any, ring
  Default: any
  Effective: immediately
  If "any", ACW occurs for any agent after call release.
  If "ring", ACW occurs only for agents that were rung.
  
  inbound-bsns-calls
  Values: true, false
  Default: false
  Effective: immediately
  When true, T-Server considers all established inbound calls on an agent as business calls.
  
  outbound-bsns-calls
  Values: true, false
  Default: false
  Effective: immediately
  When true, T-Server considers all established outbound calls on an agent as business calls.
  
  internal-bsns-calls
  Values: true, false
  Default: false
  Effective: immediately
  When true, T-Server considers all established internal calls on an agent as business calls.
  
  unknown-bsns-calls
  Values: true, false
  Default: false
  Effective: immediately
  When true, T-Server considers all established calls of an unknown type on an agent as business calls.
  
  inherit-bsns-type
  Values: true, false
  Default: true
  Effective: immediately
  When true, T-Server inherits the business call behavior between main and consult calls.
  

  (TCISCOUCM-2424)

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.1.011.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 contains no new features or functionality.

Corrections and Modifications

This release includes the following corrections or modifications:

In some 2-step transfer scenarios, if the option outbound-transfer-missing is true, T-Server no longer quits unexpectedly when receiving JTAPI disconnected events. (TCISCOUCM-2391)

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.1.011.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 contains no new features or functionality.

Corrections and Modifications

This release includes the following corrections or modifications:

T-Server now properly handles third-party ISCC transfers to a hunt group on a different T-Server. Previously, such transfers may not have been processed correctly, resulting in an incorrect AttributeCallType at the destination T-Server. This is controlled by a new option:

Recommended: Set this option to true only when problems occur in transferring to external hunt groups.

(TCISCOUCM-2345)

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

There are no restrictions for this release. This release contains the following new features or functionality:

• To avoid repeated attempts to route calls to unexpectedly unavailable agents, T-Server can now set agents to Not Ready (or equivalent) when their DN is unavailable. See Agent state change on unavailable DN in the Deployment Guide Supplement for details. (TCISCOUCM-2360)

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

There are no restrictions for this release. This release contains the following new features or functionality:

• As of 09/26/18, T-Server for Cisco UCM supports Red Hat Enterprise Linux 7, 64-bit. See the Supported Operating Environment: T-Server Cisco Unified Communications Manager page for more detailed information and a list of all supported operating systems.

• T-Server now enables supervisor monitoring across a Cisco cluster. See Cross-cluster supervisor monitoring in the Deployment Guide Supplement for details. (TCISCOUCM-2277)

Corrections and Modifications

This release includes the following corrections or modifications:

Before clearing calls, T-Server now ensures that all QueryCalls are fully completed. Previously, depending on the timing of the query responses, T-Server could incorrectly clean up calls that were still active. (TCISCOUCM-2296)

T-Server now correctly processes the release of a monitor call that occurs during conference completion. After completion, the supervisor can successfully request to monitor the same agent again. Previously, that request would fail with an "already monitored" error. (TCISCOUCM-2280)

When a consult call loops back very quickly, T-Server no longer prematurely establishes a call on a ringing DN before it is answered. (TCISCOUCM-2268)

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.1.011.08. 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:

• A new option enables T-Server to delay an EventTreatmentEnd event, to avoid its distribution if a call is being abandoned.

  Warning: Use this option only when requested by Genesys Customer Care.

  delay-treatment-end
  Values: 0 to 10000 [milliseconds]
  Default: 0
  Effective: immediately
  Delays the distribution of an EventTreatmentEnd event if it is caused by RTP_STOPPED. If the call is released during this delay, the event is not sent.

  (TCISCOUCM-2270)

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.1.011.08. 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 release was updated to General on October 16, 2017.

There are no restrictions for this release. This release contains the following new features or functionality:

• Support for the Windows 2016 operating system (added October 16, 2017). See the Supported Operating Environment: T-Server Cisco Unified Communications Manager page for more detailed information and a list of all supported operating systems.

• T-Server now masks DTMF digits in T-Server logs when hide-tlib-sensitive-data is set to true in the log-filter section. However, this setting does not prevent DTMF digits from appearing in the corresponding JTAPI logs. To do so, set JTAPI_DEBUGGING, CTI_DEBUGGING, and PROTOCOL_DEBUGGING to false in the jtapi section, although this will affect more than DTMF events. (TCISCOUCM-2267)

Corrections and Modifications

This release includes the following corrections and modifications:

In the unusual case that a switch resolves the completion of a conference call to the consult branch, T-Server now correctly resolves it to the main branch. (TCISCOUCM-2265)

T-Server now correctly handles an AllCalls supervised call when the agent completes a conference. Previously, T-Server wrongly indicated that the supervisor was released after the conference was completed. (TCISCOUCM-2252)

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.1.011.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 new features or functionality.

Corrections and Modifications

This release includes the following corrections and modifications:

T-Server now correctly applies the logout-on-agent-disconnect option setting. Previously, starting with version 8.1.202.15, if the option was set to true, T-Server did not distribute EventAgentLogout. (TCISCOUCM-2262)

T-Server now correctly cancels call monitoring when the monitoring supervisor goes out of service. (TCISCOUCM-2253)

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.1.011.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 new features or functionality.

Corrections and Modifications

This release includes the following corrections and modifications:

T-Server now ensures that an EventEstabished event is distributed for a transfer destination even if the destination answers at exactly the same time that the transfer completes. This is a rare race condition. (TCISCOUCM-2240)

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.1.011.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 new features or functionality.

Corrections and Modifications

This release includes the following corrections and modifications:

T-Server now correctly responds with an EventError if a RequestAttachUserData is sent without a ConnID. (TCISCOUCM-2203)

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.1.011.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 new features or functionality.

Corrections and Modifications

This release includes the following corrections and modifications:

T-Server now reroutes a call on a route point back to itself if the treatment server disconnects, even if this occurs while not in a treatment. Previously, if the treatment server disconnected after EventtreatmentEnd, the call was not rerouted. (TCISCOUCM-2239)

T-Server no longer uses CPNDigits in a RequestRouteCall from ISCC on an external routing point since ISCC should never specify such digits. Rather, any such digits would be left over from an earlier route request on the other T-Server. Previously, T-Server would include any specified CPNDigits in the route request, resulting in an EventError if the external routing point did not support CPNDigits.

You can change this behavior with the semi-hidden global group option:

ignore-cpndigits-on-erp
Section: globalgroup
Default Value: true
Valid Values: true, false
Changes Take Effect: immediately

When true, the route request uses no CPNDigits even if it is ISCC on an XRP.

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.1.011.03. 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 new features or functionality.

Corrections and Modifications

This release includes the following corrections and modifications:

When processing Redirect On No Answer scenarios, T-Server no longer triggers no-answer-redirection on a consultation call made directly to an agent without going through a queue or routing point. Previously, if the original call went through a queue or routing point, T-Server applied no-answer-redirection to direct consultation calls. (TCISCOUCM-2226)

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.1.011.03. 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 release contains no new features or functionality.

This release was updated to General on May 4, 2017.

Corrections and Modifications

This release includes the following corrections and modifications:

T-Server no longer times out RequestReconnectCall if the originating party releases at the same time as the request is made. Previously, the timeout prevented any further requests on the DN for 15 seconds. (TCISCOUCM-2219)

T-Server now uses the monitored CallID when attempting to record a supervisor monitoring calls. (TCISCOUCM-2218)

In some ISCC looped call flows between T-Server for Cisco UCM and SIP Server, T-Server now correctly updates CallType from inbound to consult. (TCISCOUCM-2110)

Top of Page

Supported Operating Systems

The operating systems supported by this release are listed in the Contents, above.

New in This Release

This release of T-Server is built with the T-Server Common Part (TSCP) release number 8.1.011.03. 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 no new features or functionality.

Corrections and Modifications

This release includes the following corrections and modifications:

T-Server now functions in environments running supported versions of JTAPI previous to 9.0. T-Server 8.1.202.15 and later added support for extend and connect, which requires JTAPI 9.0 or later. Pre-9.0 JTAPI versions could prevent those T-Server versions from connecting to the switch. (TCISCOUCM-2213)

When T-Server returns to primary mode in a failover scenario, the agent state is now correct. (TCISCOUCM-2189)

T-Server now generates an EventPartyDeleted event when a party drops out of a conference call. (TCISCOUCM-1665)

Top of Page

Supported Operating Systems

The operating systems supported by this release are listed in the Contents, above.

New in This Release

This release of T-Server is built with the T-Server Common Part (TSCP) release number 8.1.011.02. 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 no new features or functionality.

Corrections and Modifications

This release includes the following corrections and modifications:

In multi-site mute transfer, two-step transfer, or two-step conference scenarios with joint userdata mode, attached user data is no longer reset. (TCISCOUCM-2211)

T-Server now responds with an EventError event if a RequestAttachUserData request is sent without a ConnID. (TCISCOUCM-2203)

Top of Page

Supported Operating Systems

The operating systems supported by this release are listed in the Contents, above.

New in This Release

This release of T-Server is built with the T-Server Common Part (TSCP) release number 8.1.010.97. 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 no new features or functionality.

Corrections and Modifications

This release includes the following corrections and modifications:

T-Server no longer distributes an EventReleased event for an internal party when another internal party is dropped from a conference. Previously, this problem could occur when the switch indicated a slight change in the external digits (for example, from xxxxxx to 91xxxxxx) during this process. (TCISCOUCM-2190)

T-Server now fully supports transfer and conference to non-broadcast hunt groups. Previously, T-Server did not correctly handle the release and ringing of a call from one DN in the hunt group to another. (TCISCOUCM-2178)

T-Server no longer creates a leg connection to a media server for external routing points. Since leg connections are needed only for treatments, and external routing points are never used for treatments, this connection is unnecessary. (TCISCOUCM-2177)

T-Server now correctly handles an inbound transfer or conference to a route point when it is completed before a treatment is requested. Previously, an unexpected switch event would incorrectly cause T-Server to create an extra call. (TCISCOUCM-2138)

T-Server closes a small security hole that could allow a connection to the Java part of T-Server from another host. The Java part now allows connection only from localhost. (TCISCOUCM-2137)

T-Server now maintains the initial link-address mapping even if in-service events are subsequently (and incorrectly) received from the switch. This persistence ensures that an EventDNOutOfService is distributed if this address later goes out of service. (TCISCOUCM-2133)

Top of Page

Supported Operating Systems

The operating systems supported by this release are listed in the Contents, above.

New in This Release

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

• T-Server now supports the Cisco UCM extend and connect feature, which enables an agent to use a remote phone, such as a mobile phone, to connect to the CUCM. Note, however, that the following features are not supported with extend and connect: supervision, call parking, call pickup, and hunt groups. See Extend and connect in the Deployment Guide Supplement for details. (TCISCOUCM-2078)

Corrections and Modifications

This release includes no corrections or modifications.

Top of Page

Supported Operating Systems

The operating systems supported by this release are listed in the Contents, above.

Note: Support for the Linux operating system was added to this release on 9/02/16.

New in This Release

This release of T-Server is built with the T-Server Common Part (TSCP) release number 8.1.010.81. 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 (added on 9/30/16):

• T-Server was successfully tested with the Cisco Jabber application version 11.6.0 on voice capabilities as a single line DN. When integrated with the Cisco Jabber application, T-Server supports basic telephony operations initiated from a T-Library application, through T-Library requests, and basic telephony operations initiated from the Cisco Jabber application.

  Notes:

  • Shared line functionality is supported only on a single line DN on a Jabber device.
  • The following features are not supported: Extension mobility, supervision, call parking, call pickup, and hunt groups.

  (TCISCOUCM-2148)

Corrections and Modifications

This release includes the following corrections and modifications:

T-Server no longer terminates when it receives an unexpected released event for a nonexistent external party from the switch. (TCISCOUCM-2153)

Top of Page

Supported Operating Systems

The operating systems supported by this release are listed in the Contents, above.

Note: Support for the Linux operating system was added to this release on 7/15/16.

New in This Release

This release of T-Server is built with the T-Server Common Part (TSCP) release number 8.1.010.81. 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:

• T-Server now supports version 11.5 of Cisco Unified Communications Manager (CUCM), and has been successfully tested against CUCM version 11.5.1.10000-6 with JTAPI 11.5(1.10000)-1 Release.
  Additionally, SIP Server version 8.1.1, In-Front deployment (SIP Server as a parking platform), has been successfully tested with CUCM 11.5 and T-Server for Cisco Unified Communications Manager. (TCISCOUCM-2141)

Corrections and Modifications

This release includes the following corrections and modifications:

T-Server is now able to report EventTreatmentNotApplied as soon as it identifies that it has lost its connection to Stream Manager, while executing a TApplyTreatment request. Previously, T- Server did not report this event until the pending TApplyTreatment expired. (TCISCOUCM-2095)

T-Server can now properly handle call scenarios performed in an environment with SIP trunks where a path optimization is enabled in the PBX configuration. Previously, T-Server sometimes provided incorrect reporting for calls in those environments. (TCISCOUCM-2085)

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.1.010.81. 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:

• T-Server no longer distributes EventHardwareError when an Extension Mobility agent logs in or out. (TCISCOUCM-2115)

• T-Server now allows the location of the Java Runtime Environment to be specified in the new option java-home in the globalgroup section. If specified, this option takes precedence over the environment variable JAVA_HOME.

  java-home
  Section: globalgroup
  Default Value: No default value
  Valid Values: Any string
  Changes Takes Effect: After link restart

  Specifies the Windows Java Runtime Environment location in the same format as the JAVA_HOME environment variable. For example: "C:\Program Files\Java\jdk1.8.0_60". T-Server automatically appends "\bin\java". This option takes precedence over the environment variable JAVA_HOME. (TCISCOUCM-2086)

Corrections and Modifications

This release includes the following corrections and modifications:

While running in backup mode, T-Server no longer attempts to release an unanswered predictive call. (TCISCOUCM-2119)

T-Server now better handles a change in external originating digits that is indicated by JTAPI NetworkReached events, distributing EventPartyChanged to indicate the change. Previously, T-Server distributed EventPartyAdded and EventPartyDeleted in response to the TDeleteFromConference request. (TCISCOUCM-2109)

T-Server can now recognize the change in external party originator digits by distributing EventPartyChanged if the restricted party-changed-from-external-release configuration option, introduced in release 8.1.202.07, is set to true in the globalgroup section. (TCISCOUCM-2098, TCISCOUCM-2082)

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.1.010.81. 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:

• T-Server now handles a manual transfer to a Routing Point using a method other than the Transfer key, such as the DirTrfr key. (TCISCOUCM-2056)

Corrections and Modifications

This release includes the following corrections and modifications:

T-Server no longer terminates unexpectedly when processing a simple call from a DN that is wrongly configured on multiple CUCM links. In addition, T-Server logs the following warning message during DN registration if it senses that a DN may be configured on multiple links:

@13:00:32.6180 [cm] WARNING: Possible misconfiguration of 650230 on multiple links 1 and 2

(TCISCOUCM-2099)

If a T-Server client registers a DN with the Unknown or unspecified AddressType, T-Server now changes it to TypeDN and registers that DN with the switch. Previously, T-Server did not register the DN with the switch. (TCISCOUCM-2093)

T-Server now correctly handles the stripping of external digits in the external destination number that is indicated by CallCtlConnNetworkAlertingEv (for ISCC calls). Previously, T-Server did not update external digits that were stripped in the external destination number, and, as a result, the call was abandoned. (TCISCOUCM-2092)

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.1.010.72. 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:

• T-Server now includes the list of conference parties in AttributeExtensions of EventPartyChanged, EventPartyAdded, and EventEstablished, using the following keys:

  • OrigDN-n—String value type. The origination DN number specified by n.
  • NumOfOrigDNs—Integer value type. The number of DNs on an original call (excluding the party already reported as ThisDN) and all other DNs.
  • Consult-DN-n—String value type. The consultation DN number specified by n.
  • NumOfConsultDNs—Integer value type. The number of DNs on a consultation call and all other DNs (present only in the EventPartyAdded event).

  (TCISCOUCM-1962)

• T-Server can now include AttributeDNIS in EventDialing for most call flows by setting the restricted option, delay-dialing, to true. This causes EventDialing to be delayed until DNIS info is available.

  delay-dialing
  Default Value: false
  Valid Values: true, false
  Changes Take Effect: Immediately

  If set to true, T-Server includes AttributeDNIS in EventDialing for most call flows by delaying EventDialing until DNIS information is available.

  A few call flows do not use this option and, therefore, do not include DNIS in EventDialing:

  • Predictive calling
  • Unparking a parked call
  • Calls between intercomDNs, such as during supervisor call monitoring

  Warning: Use this option only when requested by Genesys Customer Care.

  (TCISCOUCM-1947)

Corrections and Modifications

This release includes the following corrections and modifications:

T-Server no longer logs Java stack dumps incorrectly. Previously, multi-threading logging sometimes caused stack dump logging to be mixed with other Java logging, resulting in corrupted messages. This eventually caused the message buffer to fill to capacity, which in turn caused T-Server to restart the link. (TCISCOUCM-2091)

T-Server can now recognize the change in external party originator digits by distributing EventPartyChanged if the restricted party-changed-from-external-release configuration option is set to true in the globalgroup section.

party-changed-from-external-release
Default Value: false
Valid Values: true, false
Changes Take Effect: Immediately

If set to true, T-Server uses the JTAPI CallCtlConnDisconnectedEv to trigger the change in external originator digits if the cause is REDIRECTED. T-Server distributes EventPartyChanged with the new originating digits in AttributeOtherDN. (TCISCOUCM-2082)

Warning: Use this option only when requested by Genesys Customer Care.

T-Server now specifies the correct CallType of an outbound call if the external party digits are the same as an internal party. Previously in this scenario, T-Server sometimes specified the CallType as internal. (TCISCOUCM-2055)

T-Server now logs error message 51109 "Unable to register DN" only when a DN fails to register. Previously, T-Server incorrectly logged this error in other situations, such as when an Extension Mobility DN went out of service. (TCISCOUCM-2048)

Top of Page

Supported Operating Systems

New in This Release

Important: This hot fix is no longer available as it did not function as expected. Hot fix version 8.1.202.07 corrects the identified issue.

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

• T-Server now includes the list of conference parties in AttributeExtensions of EventPartyChanged, EventPartyAdded, and EventEstablished, using the following keys:

  • OrigDN-n—String value type. The origination DN number specified by n.
  • NumOfOrigDNs—Integer value type. The number of DNs on an original call (excluding the party already reported as ThisDN) and all other DNs.
  • Consult-DN-n—String value type. The consultation DN number specified by n.
  • NumOfConsultDNs—Integer value type. The number of DNs on a consultation call and all other DNs (present only in the EventPartyAdded event).

  (TCISCOUCM-1962)

• T-Server can now include AttributeDNIS in EventDialing for most call flows by setting the restricted option, delay-dialing, to true. This causes EventDialing to be delayed until DNIS info is available.

  delay-dialing
  Default Value: false
  Valid Values: true, false
  Changes Take Effect: Immediately

  If set to true, T-Server includes AttributeDNIS in EventDialing for most call flows by delaying EventDialing until DNIS information is available.

  A few call flows do not use this option and, therefore, do not include DNIS in EventDialing:

  • Predictive calling
  • Unparking a parked call
  • Calls between intercomDNs, such as during supervisor call monitoring

  Warning: Use this option only when requested by Genesys Customer Care.

  (TCISCOUCM-1947)

• Warning! This release contains Known Issue TCISCOUCM-2091 which might affect T-Server performance in your environment.

Corrections and Modifications

This release includes the following corrections and modifications:

T-Server now specifies the correct CallType of an outbound call if the external party digits are the same as an internal party. Previously in this scenario, T-Server sometimes specified the CallType as internal. (TCISCOUCM-2055)

T-Server now logs error message 51109 "Unable to register DN" only when a DN fails to register. Previously, T-Server incorrectly logged this error in other situations, such as when an Extension Mobility DN went out of service. (TCISCOUCM-2048)

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.1.010.68. 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:

• T-Server supports a new configuration option:

  clean-calls-on-all-links-up
  Default Value: false
  Valid Values: true, false
  Changes Take Effect: Immediately

  When set to true, T-Server queries calls, once all links become active in order to clean up any old calls that may have been released since links were disconnected (EventLinkDisconnected generated). This occurs for both primary and backup T-Servers to avoid stuck calls. (TCISCOUCM-1903)

• T-Server now supports version 11.0 of Cisco Unified Communications Manager (CUCM), and has been successfully tested against CUCM version 11.0.1.20000-2 with JTAPI 11.0(1.10000)-2 Release.
  Additionally, SIP Server version 8.1.1, In-Front deployment (SIP Server as a parking platform), has been successfully tested with CUCM 11.0 and T-Server for Cisco Unified Communications Manager. (TCISCOUCM-2032)

• Note: Support for the AIX operating system is added to this release on 01/25/16.

Corrections and Modifications

This release includes the following corrections and modifications:

T-Server no longer distributes EventPartyDeleted for an external party during conference completion in some time-sensitive scenarios. (TCISCOUCM-2043)

T-Server now always distributes EventDNOutOfService upon receiving CiscoAddrRemovedEv. Previously, a Java race condition may have prevented this. (TCISCOUCM-2018)

T-Server now correctly distributes EventPartyDeleted when an external party is dropped from a conference even if it has the same digits as an internal party. Previously in this scenario, T-Server did not distribute EventPartyDeleted. (TCISCOUCM-1983)

T-Server now includes the correct ThirdPartyDN in EventReleased and correct CallState in EventRinging in auto call pickup scenarios. (TCISCOUCM-1959)

If T-Server receives from Java the RELEASED message on the Routing Point before RINGING on the destination, it now includes the correct TCauseRoute in EventRinging. (TCISCOUCM-1974)

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.1.010.67. 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 new features or functionality.

Corrections and Modifications

This release contains modifications to improve T-Server performance.

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.1.001.78. 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:

• T-Server now allows the specification of $UUID$ in the recording-filename option.

  recording-filename
  Default Value: CUCM/call-$REFCI$-at-$AGENTDN$-on-$DATE$
  Valid Values: Any valid file name using the variables specified below
  Changes Take Effect: When the next call recording is initiated

  Specifies the file name for call recording when call recording is initiated automatically, according to T-Server configuration. When this option contains a value, the generated file name is added as UserData to the call with the GSIP_REC_FN key.

  The following variables are used when creating the file:

  • $AGENTDN$�The DN where the call recording is initiated.
  • $REFCI$�The CUCM callId of the call.
  • $DATE$�The current date (GMT) in the Y-M-D format.
  • $TIME$�The current time (GMT) in the H-M-S format.
  • $UUID$�The call UUID.

• T-Server now restricts the population of the UserData key GSIP_REC_FN using the new option, recording-filename-pop.

  recording-filename-pop
  Default Value: always
  Valid Values: never, always, empty
  Changes Take Effect: Immediately

  Specifies how T-Server populates and clears the UserData key GSIP_REC_FN with recording-filename.

  • never�Never populates or clears the key.
  • always�Always populates the key with recording-filename and clears it upon receiving stop recording from the switch.
  • empty�Populates the key with recording-filename and clears it upon receiving stop recording from the switch only if the key is originally empty.

  (TCISCOUCM-1971)

• T-Server now updates AttributeCallState based on the cause sent by JTAPI. In this specific scenario, the JTAPI CAUSE_DEST_NOT_OBTAINABLE (103) message results in AttributeCallState CallStateSitInvalidnum (11) of EventDestinationBusy. (TCISCOUCM-1968)

Corrections and Modifications

This release includes the following corrections and modifications:

T-Server now successfully registers a DN address on the CUCM, when the DN address belongs to the phone that does not support Do Not Disturb (DND) functionality. (TCISCOUCM-1967)

T-Server can now distribute EventPartyDeleted when the external destination party releases from a blind conference, by setting the restricted Application-level configuration option use-ringing-for-net-alerting, introduced in this version 8.1.201.26, to true in the TServer section.

use-ringing-for-net-alerting
Default Value: false
Valid Values: true, false
Changes Take Effect: Immediately

When this option is set to true, on receiving the JTAPI event CallCtlConnNetworkAlertingEv, T-Server generates EventRinging for external parties. This helps T-Server maintain correct external party representation on outbound calls. (TCISCOUCM-1970)

Warning: Use this option only when requested by Genesys Customer Care.

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.1.001.77. 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 new features or functionality.

Corrections and Modifications

This release includes the following corrections and modifications:

T-Server no longer terminates unexpectedly if it receives JTAPI_ADDR_REMOVED without the MAC address. (TCISCOUCM-1929)

T-Server now distributes EventReleased for the consultation call in the race condition that occurs when the external consultation destination releases just before the transfer or conference is completed. Previously, T-Server incorrectly distributed EventReleased for the main call. (TCISCOUCM-1925)

T-Server can now retry registration if registration fails (after it originally succeeded) with TermRegistrationFailedEv by using the two new restricted configuration options reg-failed-delay and reg-failed-retries. If registration fails after the maximum number of retries specified by reg-failed-retries, log event 51109 is generated and EventDNOutOfService is distributed.

Specifies the time interval, in milliseconds, that T-Server waits after receiving TermRegistrationFailedEv before trying to reregister.

Specifies the number of times T-Server tries to reregister after receiving TermRegistrationFailedEv, after which it generates log event 51109 and distributes EventDNOutOfService. A value of 0 (zero) means that T-Server does not try to reregister.

Warning: Use these options only when requested by Genesys Customer Care.

(TCISCOUCM-1921)

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

• Whisper Coaching enhancement. Intercom DNs no longer require extra licenses. This enhancement changes the way they are configured in the Genesys configuration environment. See the T-Server Deployment Guide for more information. (TCISCOUCM-1907)

• T-Server supports a new restricted option, use-external-establish-from-other-link, that causes T-Server to generate EventEstablished for the originating party of an outbound consultation call if the consultation call arrives back at an internal DN that is flagged as "external" by JTAPI. Normally, T-Server ignores such JTAPI events.

  use-external-establish-from-other-link
  Default Value: false
  Valid Values: true, false
  Changes Take Effect: Immediately

  When the value is true, T-Server generates EventEstablished for the originating party of an outbound consultation call if the consultation call arrives back at an internal DN that is flagged as "external" by JTAPI.

  Warning: Use this option only when requested by Genesys Customer Care.

  (TCISCOUCM-1744)

Corrections and Modifications

This release includes the following corrections and modifications:

This version of T-Server corrects a problem which can result in EventHardwareErrors appearing in the log at startup when soft agent states are enabled. (TCISCOUCM-1891)

The blind conference operation to a pilot number is now supported by Hunt Groups configured for Broadcast hunting. (TCISCOUCM-1893)

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.1.001.76. 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:

• Support of E.164 numbering plan. (TCISCOUCM-1905)

Corrections and Modifications

This release includes the following corrections and modifications:

T-Server now correctly applies the send-backinservice-after-switchover option setting. Previously, starting with version 8.1.201.00, if the option was set to true, T-Server did not distribute EventDNBackInService after its role was changed to the primary. (TCISCOUCM-1901)

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

• If a DN rings with the routing point as a called number, and a ReqRouteCall is pending on that RP, T-Server now assumes that the call has been routed, and distributes EvRouteUsed before EvRinging. This behavior is controlled by a boolean semi-hidden option, route-used-on-ringing. The default value is true. This option may help eliminate the need for the observer-latency-timeout, at least for RPs. (TCISCOUCM-1872)
• Music and Announcements enhancement:

  • T-Server now provides the ability to turn off the default MOH (Music On Hold) treatment provided by the CUCM MOH Server when T-Server does not have an active Media Server connection. This feature is controlled by the force-moh-on-ms-down configuration option. The default value of this option preserves the existing T-Server behavior.

    force-moh-on-ms-down
    Default Value: true
    Valid Values: true, false
    Changes Take Effect: Immediately
    

    This option applies when there is no active Genesys Media Server connection. When set to true, T-Server uses MOH treatments provided by the CUCM MOH Server for client treatment requests resulting in EventTreatmentApplied. When set to false, T-Server responds to treatment requests with EventTreatmentNotApplied (no default treatment provided by the CUCM MOH Server is used).

  • T-Server corrects EventTreatmentApplied for all selected treatments of type TreatmentMusic to include the proper treatment type of TreatmentMusic and also includes a new Extensions attribute key MOH to distinguish between music treatment via Media Server and CUCM MOH Server.

    Extensions attribute
    Key Name: MOH
    Type: Integer
    Possible Values: 0, 1
    

    When the AttributeTreatmentType in EventTreatmentApplied or EventTreatmentEnd is of value TreatmentMusic, the MOH key is used to describe the specific music type 1 for the CUCM MOH Server treatment and 0 for Media Server treatment music.

  (TCISCOUCM-1833)

• Hunt Groups enhancement. T-Server now supports Hunt Groups in Broadcast mode (parallel ringing) where an incoming call rings at all available extensions in the group. (TCISCOUCM-1866)

  Note: See known limitation TCISCOUCM-1893.

Corrections and Modifications

This release includes the following corrections and modifications:

T-Server now correctly handles Extension Mobility scenarios if Java messages DN_OUT_OF_SERVICE and JTAPI_ADDR_REMOVED arrive in reverse order. Previously, if T-Server received these Java messages in reverse order, it prevented T-Server from properly processing an out of service condition, which then led to incorrect processing of the corresponding in-service condition for the same DN. (TCISCOUCM-1750)

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.1.001.76. 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:

• Enhanced support for changing an agent state and applying a delay to an agent state when a corresponding agent DN goes out of service. Previous support was limited to the logout state only. The following new configuration options enable this functionality:

  out-of-service-action
  Default Value: logout
  Valid Values: none, logout, notready, acw, walkaway
  Changes Take Effect: Immediately

  T-Server automatically changes the agent state to the specified state (and work mode) when the corresponding agent DN goes out of service (OOS). The agent state change may be delayed by specifying a delay in the related option out-of-service-action-delay. After T-Server changes the state, the agent cannot log in until the corresponding DN goes back in service. Valid option values are:

  • none—No agent state change is performed.
  • logout—The agent is automatically logged out. This is equivalent to setting the existing option logout-on-out-of-service to true.
  • notready—The agent is automatically made not ready.
  • acw—The agent is automatically made not ready with work mode AgentAfterCallWork.
  • walkaway—The agent is automatically made not ready with work mode AgentWalkAway.

  If both out-of-service-action and logout-on-out-of-service options are configured, the logout-on-out-of-service option takes precedence unless the out-of-service-action option is set to new functionality (anything other than logout).

  out-of-service-action-delay
  Default Value: 0
  Valid Values: Integer from 0 to 3600000
  Changes Take Effect: Immediately

  This delays, in milliseconds, the agent state change specified by the out-of-service-action option. If the corresponding agent DN comes back in service before the delay is completed, T-Server does not change the agent state. This avoids the automatic agent state changes if a DN goes OOS for only a short time. Note that this option will delay the effect of either out-of-service-action or logout-on-out-of-service option.

  (TCISCOUCM-1856)

Corrections and Modifications

This release includes the following corrections and modifications:

In blind transfer to Routing Point call scenarios, when routing of a consultation call occurs immediately after the transfer is complete, T-Server now distributes EventError immediately if a TRouteCall request results in error 470 (Party is not currently on call). Previously in this scenario, the request timed out with EventError (Timeout) some time later. (TCISCOUCM-1858)

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.1.001.76. 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 new features or functionality.

Corrections and Modifications

This release includes the following corrections and modifications:

T-Server no longer indicates the supervisor is released as the result of completing a transfer. Previously, T-Server incorrectly indicated the supervisor was released from the call. (TCISCOUCM-1769)

T-Server now correctly handles route requests received during a Stream Manager disconnection. Previously, those calls sometimes became stuck on Routing Points. (TCISCOUCM-1787)

Top of Page

Supported Operating Systems

New in This Release

This release of T-Server is built with T-Server Common Part (TSCP) release number 8.1.001.76. 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 new features or functionality.

Corrections and Modifications

This release includes the following corrections and modifications:

T-Server now correctly handles supervisor monitoring when a call is in the process of being transferred to an agent. Previously, in this time-sensitive scenario, T-Server sometimes did not report call monitoring events properly. (TCISCOUCM-1807)

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.1.001.76. 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 new features or functionality.

Corrections and Modifications

This release includes the following corrections and modifications:

T-Server now applies a treatment while a Routing Point is being conferenced. Previously, T-Server did not apply the treatment if the JTAPI MediaOpen and RTP events for the Routing Point were received on the consultation call instead of the main call. (TCISCOUCM-1795)

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.1.001.74. 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 in this release. This release contains the following new features or functionality:

• T-Server now supports Red Hat Enterprise Linux 6.0 32-bit and 64-bit native. (TCISCOUCM-1773, TCISCOUCM-1774)
• T-Server now supports version 10.5 of Cisco Unified Communications Manager (CUCM), and has been successfully tested against CUCM version 10.5.1.10000-7 with JTAPI version 10.5(1.10000)-1. (TCISCOUCM-1802)

Corrections and Modifications

There are no corrections or modifications in this release.

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.1.001.74. 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:

• This version of T-Server improves handling of music treatments (TApplyTreatment with TreatmentType=TreatmentMusic) provided by Cisco Unified Communications Manager Music On Hold Server on a Routing Point by ensuring that T-Server does not delay media OLC (Open Logical Channel) response, in case of any outstanding media connection request. (TCISCOUCM-1740)

Corrections and Modifications

There are no corrections or modifications in this release.

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.1.001.74. 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 in this release. This release contains the following new features or functionality:

• T-Server now correctly handles a switchover that occurs during supervisor monitoring. (TCISCOUCM-1749)
• Support of Windows 2012 64-bit. (TCISCOUCM-1772)

Corrections and Modifications

There are no corrections or modifications in this release.

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.1.001.74. 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 ignores DND errors for pre-7.0 versions of JTAPI that do not support DND. Previously, these errors would cause the DNs to remain out of service. (TCISCOUCM-1737)

Corrections and Modifications

This release includes the following corrections and modifications:

T-Server now provides the correct AttributeThisDNRole (RoleObserver) in EventReleased when a supervisor has been released from a call after he or she had already canceled the supervision subscription. (TCISCOUCM-1732)

T-Server now correctly handles the use of Shift-JIS and other multi-byte character encodings in the display name fields. Previously, such encodings sometimes caused message parsing problems eventually resulting in the link being dropped. (TCISCOUCM-1753)

This release is built with TSCP 8.1.001.74 that contains the correction of issues fixed in 8.1.3 Framework libraries. (TCISCOUCM-1765)

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.1.001.71. 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 improves its handling of changes in external party digits that may occur in outbound consultation calls. If JTAPI informs of such changes via redirected digits in either the CallCtlConnNetworkReachedEv or CallCtlConnNetworkAlertingEv events, T-Server will distribute EventPartyChanged with the ThirdPartyDN attribute containing the previous external party and the OtherDN attribute containing the new external party. (TCISCOUCM-1738)

Corrections and Modifications

This release does not include any corrections.

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.1.001.71. 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 distributes EventTreatmentNotApplied for a pending treatment request on a consultation call if the consultation call is merged to the main call. This avoids T-Server delaying the response to the treatment request until it times out. This behavior can be changed using the new restricted configuration option error-treatment-on-tc-complete, which defaults to true.

  error-treatment-on-tc-complete
  Default Value: true
  Valid Values: true, false
  Changes Take Effect: Immediately
  
  When set to true (the default), T-Server distributes EventTreatmentNotApplied for a pending treatment request on a consultation call if the consultation call is merged to the main call.

  Warning: Use this option only when requested by Genesys Customer Care.

  (TCISCOUCM-1715)

Corrections and Modifications

This release includes the following corrections and modifications:

T-Server now distributes EventAbandoned for a call on a Routing Point after a failed treatment request. Previously, if the caller abandoned the call exactly when the treatment was requested on a Routing Point, the call became stuck in T-Server memory. (TCISCOUCM-1689)

T-Server now indicates that RTP has stopped by sending EventUserEvent (and EventTreatmentEnd for Routing Points) to all relevant parties on the consultation call. Previously in this scenario, T-Server did not send these events for all relevant parties when a two-step transfer was completed, which negatively impacted the call recording process. (TCISCOUCM-1730)

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.1.001.71. 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 this release of T-Server for Cisco Unified Communications Manager. See the Framework 8.1 T-Server for Cisco Unified Communications Manager Deployment Guide for detailed information about new features.

• T-Server now supports Do Not Disturb (DND) Call Reject that can be activated from an agent�s phone or by a T-Library request. (TCISCOUCM-223)
• T-Server now provides the ability to change the Automatic Number Identification/Calling Line Identification (ANI/CLI) that is displayed on a destination party�s phone during call routing. (TCISCOUCM-248)
• T-Server now supports a free format for a terminal ID in JTAPI events, using the new option free-form-terminal-id. (TCISCOUCM-247)
• T-Server now ignores the CAUSE_CTIDROPCONFEREE(458752) and CAUSE_NORMALCALLCLEARING(16) attributes in JTAPI messages when an agent uses a hardphone to release one party from a 3-way conference call. Previously in this scenario, T-Server distributed incorrect EventPartyDeleted T-Library messages. (TCISCOUCM-1709)
• T-Server now correctly handles route and treatment requests that occur immediately following the completion of transfers and conferences. Previously, these requests sometimes failed because the transfer or conference was not completed entirely on the switch. This was a time-sensitive problem that did not always occur. (TCISCOUCM-1685)

• T-Server version 8.1.2 requires that the Java 2 Standard Edition (J2SE) Runtime Environment (or J2SE SDK) version 1.7.0 or later be installed on the T-Server host.

• TLS encryption is now supported between the Genesys Java Telephony API (JTAPI) process and the Cisco CTIManager. See TLS Support in the Deployment Guide Supplement for details. (TCISCOUCM-165)

• T-Server now supports version 10.0 of Cisco Unified Communications Manager (CUCM), and has been successfully tested against CUCM version ES 10.0(1.12008-3) with JTAPI version 10.0(1.10000)-2.

Corrections and Modifications

This release includes the following corrections and modifications:

T-Server no longer generates duplicate logs at startup on any UNIX operating system. (TCISCOUCM-113, TCISCOUCM-174)

T-Server no longer sets Routing Points to out-of-service state when they are reconfigured on the switch (moved from one partition to another). (TCISCOUCM-1482)

When a Routing Point is moved from one partition to another, a JTAPI Exception no longer results in the Routing Point being left out of service. (ER# 263021954)

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.1.001.68. 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 no new features or functionality.

Corrections and Modifications

This release includes the following corrections and modifications:

T-Server now correctly handles the use of Shift-JIS and other multi-byte character encodings in the display name fields. Previously, such encodings sometimes caused message parsing problems eventually resulting in the link being dropped. (TCISCOUCM-1747)

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.1.001.68. 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:

• T-Server now ignores the CAUSE_CTIDROPCONFEREE(458752) and CAUSE_NORMALCALLCLEARING(16) attributes in JTAPI messages when an agent uses a hardphone to release one party from a 3-way conference call. Previously in this scenario, T-Server distributed incorrect EventPartyDeleted T-Library messages. (TCISCOUCM-1692)
• T-Server now correctly handles route and treatment requests that occur immediately following the completion of transfers and conferences. Previously, these requests sometimes failed because the transfer or conference was not completed entirely on the switch. This was a time-sensitive problem that did not always occur. (TCISCOUCM-1674)

Corrections and Modifications

There are no corrections or modifications for this release.

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.1.001.68. 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 no 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 default value of true and the value change takes effect immediately. (TCISCOUCM-1636)

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.1.001.67. 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 no new features or functionality.

Corrections and Modifications

This release includes the following corrections and modifications:

In predictive-call scenarios, T-Server translates call results provided by Cisco UCM and distributes them in the CallState Attribute of EventReleased as follows—if T-Server receives CAUSE_USERBUSY(17), it translates to CallStateBusy(6); and if T-Server receives CAUSE_NOUSERRESPONDING(18), it translates to CallStateNoAnswer(7). (TCISCOUCM-1637)

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.1.001.61. 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 this release of T-Server for Cisco Unified Communications Manager:

• This release of T-Server enhances the functionality of the switchover-on-first-link-failure option as follows:

  When set to true, T-Server reports LinkConnected only when all configured links are up. If any link fails, T-Server immediately reports LinkDisconnected, causing Solution Control Server to trigger a switchover. When set to false, T-Server reports LinkConnected as soon as any one link is up. After startup completion, T-Server sets DNs for any link that failed to out-of-service, and does not trigger a switchover as long as at least one JTAPI link remains active. (ER# 307704821)

• T-Server now supports version 9.1 of Cisco Unified Communications Manager (CUCM), and has been successfully tested against:

  • CUCM version 9.1.1.20000-5 and with JTAPI version 9.1(1.10000)-2
  • CUCM version ES 9.1(2.12041-1). with JTAPI version 9.1(2.12040)-1

• This version was first released as a Hot Fix on 05/21/13.

Corrections and Modifications

This release includes the following corrections and modifications:

T-Server now includes AttributeConnID, and AttributeTransferConnID in EventAddressInfo in response to a RequestQueryAddress of type AddressInfoCallsQuery. (ER# 321012828)

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.1.001.57. 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:

• T-Server has been tested with Java 7 Standard Edition (J7SE) Runtime Environment version 1.7.17.

Corrections and Modifications

This release includes the following corrections and modifications:

T-Server now correctly reads a non-null terminated application name in the HELLO message from UCM Connector or Stream Manager. (ER# 317933567)

T-Server corrects a problem with the processing of multi-link messages. Previously, this may have caused switch-based treatments to have been incorrectly handled. (ER# 308232081)

T-Server now correctly processes the expire option when its value is set to <number> days by removing the logs when they expire in <number> days. Previously, T-Server did not remove the logs. (ER# 318288793)

T-Server now correctly populates the AttributePreviousConnectionID attribute value in the EventPartyChanged event after the multi-site two step conference completion. Previously in this scenario, T-Server generated an EventPartyChanged event with the AttributePreviousConnectionID attribute value incorrectly set to ffffffffffffffff. (ER# 316976779)

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.1.001.55. 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 distributes EventUserEvent with OPER = Started/Stopped for the consultation call destination party when a conference call is initiated. Previously, T-Server may have not distributed these events. (ER# 316807048)

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.1.001.55. 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:

• T-Server now supports the new option call-forward-action which can be used to replace the existing option logout-on-fwd. This new option (call-forward-action) provides a new range of agent state change possibilities which can be performed by T-Server when forwarding is detected.

  call-forward-action
  Default Value: logout
  Valid Values:

  none	No agent state change is performed.
  logout	Agent is automatically logged out and prevented from logging back in while the DN is forwarded.
  notready	Agent is automatically put into the not ready state (workmode 0) and prevented from going ready (or potentially logging back in) while the DN is forwarded.
  acw	Agent is automatically put into the not ready state (workmode AgentAfterCallWork) and prevented from going ready (or potentially logging back in) while the DN is forwarded.
  walkaway	Agent is automatically put into the not ready state (workmode AgentWalkAway) and prevented from going ready (or potentially logging back in) while the DN is forwarded.

  Changes Take Effect: Immediately.
  

  The old option (logout-on-fwd) will continue to be supported in T-Server and will continue to cover the supported functionality of logout on forward. However, when the old option and the new option conflict on the functionality (the functionality of logout on forward), the old option will take precedence. The new functionality is covered by the values: none, notready, acw and walkaway and will take precedence over any setting of the old option.

  (ER# 313157941)

Corrections and Modifications

This release includes the following corrections and modifications:

T-Server now distributes EventDialing for a party in the dialing state at startup. Previously, EventEstablished could have been incorrectly distributed in some cases. (ER# 276766112)

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.1.001.54. 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 moves an Extension Mobility user from one terminal to another without logging out of the first terminal. Previously, if the user logged into the second terminal without first logging out of the other terminal, requests such as RequestMakeCall would fail and T-Server sent an EventError InvalidArgumentException message due to the address not being assigned to the correct terminal. (ER# 301772070)

In blind conference call scenarios, when the call is answered after a complete conference operation, T-Server now correctly distributes EventUserEvent(Started) to all parties of the conference. Previously in these scenarios, T-Server did not distribute EventUserEvent(Started) to the conference controller party. (ER# 310961341)

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.1.001.50. 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:

• This version of T-Server extends the configuration of the Redirect On No Answer (RONA) feature to agent login objects in Configuration Manager.

  The following new options (same as existing global options) are now supported for the Agent Login objects under the Annex tab in the TServer section:

  agent-no-answer-timeout
  Default Value: 0
  Valid Values: 0 to 600
  Changes Take Effect: Immediately.
  

  Calls ringing on an agent's phone that were distributed from an ACD Queue or a Routing Point will wait for the telephone to ring for this timeout period (in seconds) before performing the actions described by the agent-no-answer-action option and redirect the call to the destination described in the agent-no-answer-overflow option. The default value of 0 (zero) disables the functionality of this option.

  agent-no-answer-action
  Default Value: none
  Valid Values: none, notready, walkaway, logout
  Changes Take Effect: Immediately.

  Specifies the agent state to which T-Server will be set after the time period for the agent-no-answer-timeout option has expired. A value of none means that the agent will remain in its current state.

  agent-no-answer-overflow
  Default Value: none
  Valid Values:
  none - The call will remain ringing on the agent phone.
  recall - The call will be redirected back to the Routing Point or the ACD Queue that delivered the call to the agent.
  Any destination digits - A valid destination DN must be provided (a Queue or Routing Point on the local switch is recommended).
  Changes Take Effect: Immediately.

  After the time period for the agent-no-answer-timeout option has expired, T-Server will redirect the ringing call to the destination described by this option.

  The agent login ID configuration options now apply to any ringing business call which is queued to an agent through the agent queue, and the corresponding agent login ID.

  However, since multiple sources of these options can be configured (T-Server application, AgentLogin object, and Extensions attribute in TRouteCall), T-Server applies the options in the following priority (from highest to lowest): Extensions attribute in TRouteCall, AgentLogin object, T-Server application.

  (ER# 310773291)

Corrections and Modifications

This release also includes the following corrections and modifications:

T-Server now correctly handles changes in external DN digits with the addition or deletion of prefix digits when the new restricted option external-dn-length is set appropriately.

external-dn-length
Default Value: 0
Valid Values: 0 to 60
Changes Take Effect: Immediately.

This option determines the length of the right most digits to compare between two external DNs on the same conference call. This is to assist T-Server in determining whether or not the DNs are the same (differ only by prefix digits). A value of 0 (zero) turns this comparison off.

Warning: If this option is used, its value must be set high enough to avoid false matches between external DNs.

(ER# 298498834)

T-Server now uses a newer version of the Flex licensing library which corrects stability issues. (ER# 305391884)

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.1.001.50. 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 handles partial messages sent between the Java and the C++ parts. Previously, T-Server attempted to log these partial messages, which caused incorrect information to appear in the log. This also introduced the possibility of T-Server becoming unstable. (ER# 310022868)

T-Server can now be installed on Windows Server 2008 through Genesys Administrator with TServer_CCM_811.xml. (ER# 308476740)

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.1.001.47. 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 associates the correct park address to the releasing party that parked the call. Previously, the incorrect park address could be associated, which caused T-Server to propagate the EventReleased message with the incorrect Extensions attribute key-value pair Data (PARK_ADDRESS). (ER# 268006582)

T-Server now distributes an EventPartyInfo event in response to TQueryCall CallInfoPartiesQuery CallInfoType. (ER# 294751371)

When integrated with Stream Manager, T-Server now correctly handles treatments requested on Routing Points when they are received before, during, and after a call is held and then retrieved. (ER# 303714693)

T-Server now correctly processes a TRouteCall request with a NO_ANSWER_ACTION key value of logout by logging the agent out, if the call is not answered. Previously, T-Server kept the agent logged in. (ER# 303877029)

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.1.001.45. 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:

This version of T-Server is built with multithreaded libraries which prevent T-Server from becoming unstable. Previously, this could occur when the number of licenses was set to the maximum value in the T-Server application. (ER# 302600760)

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

• Media Server is now supported through a new software component which is distributed with the Media Server CD. Support for Media Server is on par with support for Stream Manager and both these media components are distributed in every product of which the IP Media Enterprise Edition CD is part.

• T-Server for Cisco Unified Communications Manager now supports:

  • Red Hat Enterprise Linux 5 64-bit Native
  • Windows 2008 R2 64-bit Native
  • IBM AIX 7.1 64-bit

• T-Server now supports version 9.0 of Cisco Unified Communications Manager (CUCM), and has been successfully tested against CUCM version 9.0.1.10000-37 with JTAPI version 9.0(1.10000)-1.

Corrections and Modifications

This release also includes the following corrections and modifications:

T-Server now corrects a problem which can cause T-Server to miscount the number of active call legs when performing a single-step transfer from a shared line to another shared line. Previously, this problem would have led to incorrect DNRole on the resulting T-Events. (ER# 271426066)

T-Server now allows subsequent treatments if a previous treatment request times out. Previously, it responded with an invalid state error. (ER# 286014012)

T-Server now restarts the link after the specified number of jtapi-keep-alive-retries. Previously, it restarted after one less than specified. (ER# 276759223)

T-Server no longer distributes erroneous EventHardwareError messages to unmonitored parties. Previously, in some call flows, it was potentially possible for T-Server to consider external parties/unmonitored internal parties, when applying the timer for the Agent No Answer Supervision feature. (ER# 273681944)

When the route type parameter of TRouteCall is set to RouteTypeOverwriteDNIS, the value of AttributeDNIS is set as preferredOriginalCalledParty.

The new restricted Application-level option set-preferred-original-called-party is introduced for backward compatibility to enable to set a preferred original called party after TRouteCall regardless of route type when AttributeDNIS is specified.

set-preferred-original-called-party
Default Value: false
Valid Values: true, false
Changes Take Effect: Immediately

When routing a call, T-Server sets AttributeDNIS in subsequent events based on the AttributeDNIS specified in the corresponding RequestRouteCall if the AttributeRouteTypeRouteType is RouteTypeOverwriteDNIS. Setting this option to true causes T-Server to set AttributeDNIS regardless of the AttributeRouteTypeRouteType. This option value supports backward compatibility for pre-8.0.1 T-Server.

Warning: If this option is used, its value must be set high enough to avoid false matches between external DNs.

(ER# 280414039)

T-Server distributes EventTreatmentNotApplied if the call is abandoned from the Routing Point while there is an outstanding treatment request. (ER# 277729998)

T-Server, in hot standby mode, no longer generates an 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-uptimer. (ER# 284979527)

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

When the RouteType attribute of a TRouteCall request is set to RouteTypeOverwriteDNIS, T-Server now sets the value of the DNIS attribute to the value of preferredOriginalCalledParty. (ER# 284951499)

T-Server no longer distributes EventAbandoned in cases where a Routing Point is released and the call is default routed instead of released with cause BUSY. (ER# 276825438)

T-Server now includes the display name information within the CALLING_PARTY_DISPLAY_NAME and/or CALLED_PARTY_DISPLAY_NAME key-value pairs in the Extensions attribute of the EventEstablished call event for the originating address of an internal call. (ER# 284280682)

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.1.001.25. 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 includes calling and called display names in the Extensions attribute of the Ringing, Queued, RouteRequest, Established, and NetworkReached call events, if the names are available from the corresponding switch message.

The following two new configuration options have been introduced to control this functionality:

use-calling-party-display-name
Default Value: false
Valid Values: true, false
Changes Take Effect: Immediately

If set to true, the calling party display name appears in the CALLING_PARTY_DISPLAY_NAME key-value pair in the Extensions attribute of the specific call events.

use-called-party-display-name
Default Value: false
Valid Values: true, false
Changes Take Effect: Immediately

If set to true, the called party display name appears in the CALLED_PARTY_DISPLAY_NAME key-value pair in the Extensions attribute of the specific call events.

Note: These new options are independent of the use-party-display-name option.

(ER# 283506103)

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.1.001.24. 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:

Call Supervision now works correctly when the agent and the supervisor DNs are located on different CTI Links. Previously, the monitoring failed due to a JTAPI Exception (InvalidArgumentException). (ER# 278848651)

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

• T-Server can now provide display name information for DNs involved in calls if the information is available from Cisco Unified Communications Manager. This functionality is controlled by the new configuration option use-party-display-name.

• T-Server now fully supports the deletion of a shared line party from a conference call without the client having to know which shared party is active. T-Server internally adjusts the party to be deleted to correspond to the active shared party to ensure that the request is successful.

• Whisper Intercom Feature, third-party call control (3PCC) support for the Cisco Talk-back Intercom Feature. This feature allows the monitored Agent to use CTI requests from T-Server to talk back to the Supervisor without being overheard by the customer.

• Support for Called Address Redirect Destination in RouteCall messages. RequestRouteCall messages can be customized by sending the request to T-Server in special keys within AttributeExtensions.

• Support for monitoring DNs in Hunt Groups. T-Server now supports Hunt Groups on Cisco Unified Communications Manager.
  Note: this is a restricted feature as it requires the specific release version 8.0.(3)SU2 of Cisco UCM.

• Support for Querying JTAPI on Call States / Active Call On DN. This feature provides an enhanced capability to detect and clean up stuck calls after a link disconnection/reconnection.

• T-Server now supports version 8.5(1) of Cisco Unified Communications Manager (CUCM) and has been successfully tested against CUCM version 8.5.1.10000-26 with JTAPI version 8.5(1.10000)-1

• T-Server now supports version 8.6 of Cisco Unified Communications Manager (CUCM) and has been successfully tested against CUCM version 8.6.1.20000-1 with JTAPI version 8.6(1.10000)-1 . Some limitations apply, see the Known Issues and Recommendations section for more details.

Corrections and Modifications

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

T-Server no longer terminates operation during processing of EndTreatment for treatments of type TreatmentPlayAnnouncementAndDigits. Previously, this could occur under some rare, time-sensitive scenarios. (ER# 278148413)

T-Server now applies subsequent treatments correctly when the second one is started at the exact moment the first one ends. Previously, T-Server may not have applied the second treatment correctly. (ER# 268351293)

T-Server now reports a call as Internal if DNs participating in the call are associated with the Switching office (the Application-level option dn-scope is set to office.) Previously, the call was reported as Outbound in some call scenarios. (ER# 262037923)

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

T-Server now supports Delete Shared Line from conference when the shared line is in a held state. Previously, Delete Shared Line from conference would lead to an Error (Timeout), if the otherDN attribute pointed to a shared line party in a bridged state. (ER# 255964272, 253492628)

T-Server no longer distributes EventPartyDeleted when the last monitored party leaves the conference. Previously, T-Server mistakenly distributed EventPartyDeleted in this scenario. (ER# 252391268)

Top of Page

Documentation Corrections

This section provides corrections and updates for issues found in currently released documentation for this product. The changes described here will be included in future published versions of the document.

The Framework 8.1 T-Server for Cisco Unified Communications Manager Deployment Guide currently contains an incomplete description of the num-sdn-licenses configuration option. The following must be added to the option description:

A value of 0 (zero) does not allow a T-Server client to register seat-related DNs, which causes issues in a client's attempt to acquire seat-related licenses from T-Server. In this case, T-Server prints the following log message: All 0 seat licenses are in use already, registration rejected.

(TCISCOUCM-1963)

The Framework 8.1 T-Server for Cisco Unified Communications Manager Deployment Guide currently contains incorrect description of the recording-filename configuration option. This is the correct option description:

recording-filename
Default Value: CUCM/call-$REFCI$-at-$AGENTDN$-on-$DATE$
Valid Values: Any valid file name using the variables specified below
Changes Take Effect: When the next call recording is initiated

Specifies the file name for call recording when call recording is initiated automatically, according to T-Server configuration. When this option contains a value, the generated file name is added as UserData to the call with the GSIP_REC_FN key.

The following variables are used when creating the file:

• $AGENTDN$�The DN where the call recording is initiated.
• $REFCI$�The CUCM callId of the call.
• $DATE$�The current date (GMT) in the Y-M-D format.
• $TIME$�The current time (GMT) in the H-M-S format.
• $UUID$�The call UUID.

(TCISCOUCM-1949)

Top of Page

Known Issues and Recommendations

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

T-Server currently supports the supervision of only one agent on a call at a time. (TCISCOUCM-2584)

T-Server may distribute duplicate EventForwardSet messages for DNs configured as shared lines. (TCISCOUCM-2553)

The user-friendly method of configuring Extension Mobility (EM) with shared lines does not work correctly. T-Server does, however, support their configuration using the @MAC prefix instead. (TCISCOUCM-2521)

T-Server for UCM 8.1.5xx requires FlexNet Publisher License Manager version 11.13+. (TCISCOUCM-2504)

When a call involving SIP telephones is transferred to an external destination by a TSingleStepTransfer request, the Cisco UCM switches of versions 12.0 and 12.5 sometimes send incorrect messages that cause T-Server to report events improper to that call flow. Genesys strongly recommends that only two-step outbound transfers be used from call centers where SIP telephones are deployed on a version 12.0 or 12.5 switch. (TCISCOUCM-2494)

A rare race condition may occur when the originating party drops from a call during a transfer/conference completion. For example, an inbound call from the customer arrives at agent A which initiates a conference to agent B, and during the transfer the customer drops. If the drop occurs at just the wrong time T-Server may not handle the call correctly. There are two possible problems:

1. The transfer/conference succeeds but T-Server fails to process the disconnect of the originator. T-Server incorrectly considers the originator still on the call.

   Important: This first problem is fixed in T-Server for Cisco UCM release 8.1.501.33, when the ignore-tc-events option is set to false.

2. The transfer/conference fails later in the process. Since T-Server processes the completion earlier it will incorrectly consider the completion to have succeeded.

To ensure backward compatibility, T-Server provides two options that define how many licenses T-Server can check out:

• num-of-licenses defines the max number of licenses that T-Server can check out.
• num-sdn-licenses defines the actual number of licenses that T-Server does check out, up to the maximum value specified by option num-of-licenses.

When the values of the two options are different, then T-Server applies the lower one, so Genesys recommends that you leave the option num-sdn-licenses at the default value max and set the option num-of-licenses to the actual number of licenses that you want T-Server to check out. Alternatively, you can set both options to the same value.

• num-of-licenses
  Default Value: max (equivalent to 9999 licenses)
  Valid Values: max (equivalent to 9999) or any integer
  Changes Take Effect: Immediately
  Specifies the maximum number of DN licenses T-Server can check out. The values max or 0 (zero) is equal to exactly 9999 licenses. To check out any other number of licenses, specify the value as an integer, up to the number of seats supportable in your environment. The sum of all num-of-licenses values for all concurrently deployed T-Servers must not exceed the number of seat-related DN licenses (tserver_sdn) in the corresponding license file. The primary and backup T-Servers share the same licenses, and therefore they need to be counted only once. T-Server checks out the number of licenses indicated by the value for this option, regardless of the number actually in use.

• num-sdn-licenses
  Default Value: max (all DN licenses are seat-related)
  Valid Values: String max (equal to the value of num-of-licenses) or any integer.
  Changes Take Effect: Immediately
  Specifies how many seat-related licenses T-Server checks out. A value of 0 (zero) means that T-Server does not grant control of seat-related DNs to any client, and it does not look for seat-related DN licenses at all. A value of "max" means that T-Server checks out the number of licenses defined in option num-of-licenses. The sum of all num-sdn-licenses values for all concurrently deployed T-Servers must not exceed the number of seat-related DN licenses (tserver_sdn) in the corresponding license file. The primary and backup T-Servers share the same licenses, and therefore they need to be counted only once. T-Server checks out the number of licenses indicated by the value for this option, regardless of the number actually in use.

Cisco JTAPI may timeout connecting to the link when there is insufficient entropy in Linux. To encrypt the username and password, the Cisco JTAPI library requires random data (entropy) that is provided by the underlying Linux OS. If there is insufficient entropy available within the OS within 5 seconds after connecting to the switch, the CUCM will disconnect the JTAPI client. This may be more noticeable when running within a VM. Currently the only workaround is to configure the OS to generate entropy using an alternate method. (TCISCOUCM-2285)

T-Server does not currently support DTMF collection treatment in High Availability (HA) scenarios. (TCISCOUCM-2271)

T-Server neglects to distribute EventPartyDeleted in the following scenario:

1. A calls shared B
2. B conferences in C
3. C deletes B from the conference

T-Server might log Java stack dumps incorrectly. Multi-threading logging could cause stack dump logging to be mixed with other Java logging, resulting in corrupted messages. This would eventually cause the message buffer to fill capacity, which in turn caused T-Server to restart the link. (TCISCOUCM-2091)

The blind conference operation to a pilot number is not supported by Hunt Groups configured for Broadcast hunting. (TCISCOUCM-1893)

DND Reject is supported for shared lines only if all lines are in the same DND state. (TCISCOUCM-1718)

T-Server may not connect to the link if the jtapi.jar file must be downloaded from the switch by T-Server. Restarting T-Server will resolve the issue. (ER# 283933005)

A TApplyTreatment request will timeout within the normal request timeout period with EventTreatmentnotApplied if the specified codec is not configured in T-Server-CUCM to Media Server Connector. Correcting the T-Server-CUCM to Media Server Connector configuration will rectify the problem. (ER# 293561091)

When running on the AIX platform, sections of the T-Server log file may be duplicated if T-Server, configured with multi-links. This does not affect functionality, and should rectify itself within a few seconds or less. (ER# 291988302)

Media Server will record using codecs even if they are not configured in T-Server. To avoid this, ensure that Media Server and T-Server are configured with the same codecs. (ER# 294504047)

T-Server does not include the display name information within the CALLING_PARTY_DISPLAY_NAME and/or CALLED_PARTY_DISPLAY_NAME key-value pairs in the Extensions attribute of the EventEstablished call event for the originating address of an internal call. (ER# 284280682)

T-Server does not distribute EventUserEvent(Started) to the conference controller party for blind conference call scenarios when the call is answered after the complete conference operation. (ER# 310961341)

During link connection time, T-Server may incorrectly distribute EventEstablished for a call that is still ringing. (ER# 276766112)

T-Server does not currently support the monitoring of one agent from two supervisors with different types of Monitor NextCall (MonitorOneCall and MonitorAllCalls). (ER# 276539033)

When a Routing Point is moved from one partition to another, a JTAPI Exception may result in the Routing Point being left out of service. (ER# 263021954)

With release 8.5 and 8.6 of CUCM, 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, 283932964)

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)

In some call scenarios, the switch may send messages indicating that an external DN has the same digits as an internal DN. In such cases, T-server will treat these as shared/bridged parties. This will negatively affect subsequent events for these DNs; in particular causing EventReleased to be distributed for both parties when only one is actually released. (ER# 277433935)

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)

A Monitoring Session is not immediately started in scenarios where T-Server receives a RequestMonitorNextCall at the moment an agent is placed on hold. However, monitoring will be started for a subsequent established call to that agent if monitoring is not cancelled in the meantime. (ER# 227371541 )

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.

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)

In cases where there is only one monitored party on a conference, T-Server may distribute EventPartyDeleted instead of EventReleased when that party releases from the call. This is caused when messages from the switch are slightly out of order. (ER# 252391268)

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. (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. For more information on discontinued support for operating environments and databases, see Discontinued Support in the Genesys Supported Operating Environment Reference Guide.

The following operating systems:

• Red Hat Enterprise Linux 6
• AIX (all versions)
• Solaris (all versions)
• Windows Server 2008

Red Hat Enterprise Linux 3.0 operating system

Solaris 8 operating system

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 Cloud Services, Inc. is available on our Customer Care website. The following documentation also contains information about this software. Please consult the Framework 8.1 T-Server for Cisco Unified Communications Manager Deployment Guide first.

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

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

• The Platform SDK 8.x .NET (or Java) API Reference and the Genesys 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.

Product documentation is provided on the Genesys Customer Care website, the Genesys Documentation website, and the Documentation Library DVD.

Note: For the DVD, the New Documents on this DVD 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.

Top of Page