Release Note

Contents

Introduction

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

This release note applies to all 8.0 releases of T-Server for Nortel Communication Server 1000 with SCCS/MLS.

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

Use of Third-Party Software

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

Supported Operating Systems

New in This Release

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

This is a hot fix for this product. This section describes new features that were introduced in this release:

• T-Server now supports Emulated Agent States. The soft-login-support configuration option has been introduced to turn on or off the Emulated Agent States (also known as the Soft Agent) feature. The agent-implied-state configuration option has been introduced to specify whether inbound calls will trigger a change in the agent's state.

  soft-login-support
  Default Value: false
  Valid Values: true, false
  Changes Take Effect: After T-Server is restarted

  If this option is set to true, T-Server processes all agent-related requests (TAgentLogin/TAgentLogout/TAgentSetReady/TAgentNotReady) internally, without interacting with the CTI-link. T-Server accepts all client requests, provided that they do not contradict the Agent-State diagram. See the Genesys Events and Models Reference Manual and Voice Platform SDK 8.0 .NET (or Java) API Reference Manual for more information.

  The following conditions must be met:

  • AgentID must be configured in the Configuration Layer.
  • Only one login with any given AgentID is allowed at any time.
  • Only one agent login is allowed on the DN.
  • Only DNs of type Extension should be used for soft agent login.
  • If a password is configured in the Configuration Layer, it must be supplied in a TRequestAgentLogin request; otherwise the request fails.
  • WorkMode is not used in a TAgentSetReady request, but T-Server supports all NotReady substates shown in the Agent-State model.
  • In order for a TAgentLogin request to succeed for a soft agent, the DN must be in an idle state.

  Notes:
  

  • The T-Server Common Part implements the Emulated Agent States feature. When this feature is enabled, T-Server processes agent-related CTI messages, but it does not distribute corresponding agent-related events when an agent uses a phone set to log in or out manually. To avoid loss of synchronization between the PBX and the reporting application, agents should not log in or out manually (a so-called "hard" login) when the soft-login-support option is enabled.
  • When the soft-login-support configuration option is set to true, the timed ACW is active and the value of the soft-wrap-up-time configuration option is taken into account, regardless of the value of the soft-tacw-support configuration option.

  agent-implied-ready
  Default Value: all
  Valid Values: off, all, acd
  Changes Take Effect: Immediately

  This configuration option, which is set in the gctm section, specifies whether inbound calls will trigger a change in the agent's state.

  • If this option is set to off, then there will be no change in the agent's state.
  • If this option is set to all, an inbound call to a DN where agents are allowed to log in (Extensions if the Soft Agent feature is enabled, and ACD Positions if the Soft Agent feature is not enabled) will cause a logged-in agent in a NotReady state to go into a Ready state. If T-Server has no prior knowledge of an agent logged in at a DN, then this change will cause T-Server to send EventAgentLogin, EventAgentNotReady, and EventAgentReady events, in this order.
  • If this option is set to acd, only ACD calls (calls seen by T-server as distributed through an ACD Queue or a Routing Point) will cause this transition to the Ready state.

  Notes:
  

  • Genesys strongly recommends that you set the value of this option to off or acd whenever the Soft Login feature is enabled, and to use the default value (all) when the feature is not enabled.
  • This configuration option must be set in the gctm section.

  (ER# 266587401, ER# 266313871)

Corrections and Modifications

This release includes the following correction and modification:

T-Server now repeatedly attempts to check out SDN licenses after a connection to the License Manager is restored. Previously, after an unsuccessful attempt to check out SDN licenses again, T-Server denied the new DN registration because of a license violation. (ER# 262127850)

Top of Page

Supported Operating Systems

New in This Release

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

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

• The new option no-delay-orig-divert gives clients the option of delaying the distribution of the EventRouteUsed event of the main call.

  no-delay-orig-divert
  Default Value: false
  Valid Values: true, false
  Changes Take Effect: Immediately

  When this option is set to true, T-Server avoids delaying the distribution of EventRouteUsed if the call is in an estabished state and involves a transfer between Routing Points using unknown DNs (for example CallPilot ports). This ensures the correct distribution order of the EventRouteUsed events when unknown DNs are used to transfer calls between Routing Points. When this option is set to false, T-Server delays the distribution of the EventRouteUsed event to conduct precise party matching and create more accurate internal call representation.

  Note: Use this option only when requested by Genesys Technical Support.

  (ER# 246975705)

Corrections and Modifications

This release does not include any corrections and modifications.

Top of Page

Supported Operating Systems

New in This Release

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

There are no restrictions for this release. This section describes new features that were introduced in the initial 8.0.1 release of T-Server for Nortel Communication Server 1000 with SCCS/MLS.

• Flexible call matching has been enhanced to resolve race conditions that previously could interfere with Inter Server Call Control/Call Overflow (ISCC/COF).

• T-Server now supports Contact Center Release 6.0 Standby Server.

Corrections and Modifications

This release includes the following corrections and modifications:

T-Server now shows the correct status in the AttributeExtensions of the EventAddressInfo event for a DN that is abandoned. (ER# 101391756)

The match-ani method of Call Overflow (COF) now works for T-Server. (ER# 226630061)

T-Server no longer includes an empty AttributeDNIS in events. (ER# 238889783)

T-Server preserves the original AttributeDNIS in events after completing a transfer to a Queue with agents that are ready. (ER# 245132111)

Top of Page

Supported Operating Systems

New in This Release

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

Corrections and Modifications

This release includes the following corrections and modifications:

T-Server no longer terminates unexpectedly under very rare time-sensitive scenarios involving unmonitored parties. (ER# 246523904)

T-Server no longer has memory issues in Inter Server Call Control (ISCC) scenarios. (ER# 246406182)

Top of Page

Supported Operating Systems

New in This Release

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

Corrections and Modifications

This release includes the following corrections and modifications:

T-Server no longer displays the message (reason: too slow) when a client disconnects from a session under normal operating conditions. (ER# 233269265)

T-Server no longer has to be restarted when a transfer to a Routing Point or an ACD (Automated Call Distribution) Queue diverts to an agent in the Ready state who then becomes Not Ready and Ready again within 500 milliseconds. Previously, this issue occured on HP-UX operating systems. (ER# 237979656)

T-Server now issues an EventLinkConnected event even if a client disconnects during DN registration. (ER# 236113562)

T-Server no longer terminates unexpectedly when setting certain hidden options with values of null or empty in Configuration Manager. (ER# 239190241)

Top of Page

Supported Operating Systems

New in This Release

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

There are no restrictions for this release. This section describes new features that were introduced in the initial 8.0 release of T-Server for Nortel Communication Server 1000 with SCCS/MLS.

• T-Server now supports additional progress codes. The new options dest-busy-codes and dest-busy-invalid-num-codes allow additional control over how T-Server handles specific progress codes.

  dest-busy-codes
  Default Value: 0 (null)
  Valid Values: Any space-delimited set of hexadecimal progress codes
  Changes Take Effect: Immediately

  Specifies the list of additional space-delimited progress codes (in hexadecimal form) that are translated into an EventDestinationBusy event. These progress codes are in addition to the five hexadecimal codes that T-Server always translates into an EventDestinationBusy event.

  dest-busy-invalid-num-codes
  Default Value: 0C08
  Valid Values: Any space-delimited set of hexadecimal progress codes
  Changes Take Effect: Immediately

  Specifies the list of space-delimited progress codes (in hexadecimal form) that are translated into an EventDestinationBusy event with an AttributeCallState 11 (CallStateSitInvalidnum) attribute.

• T-Server now supports voice-monitoring application password. The new option rtp-info-password specifies the password that must be supplied by voice-monitoring application.

  rtp-info-password
  Default Value: none
  Valid Values: A password string or empty
  Changes Take Effect: Immediately

  Specifies the password that must be supplied by a voice-monitoring application as value for the RTP-PASSWORD key in the Extensions attribute in either RequestRegisterAddress or RequestPrivateService. If this option is not provided, no voice-monitoring application will be allowed to receive RTP stream data.

• T-Server can now send EventError in response to the Error message Set is in target state from the switch for login and logout requests.

  update-login-on-err
  Default Value: true
  Valid Values: true, false
  Changes Take Effect: Immediately

  Determines T-Server�s behavior when T-Server receives the ErrorCode 0x200E (decimal 8206) - Set is in target state message for login and logout requests from the switch. If this option is set to true (default), T-Server updates the agent�s state and distributes events that indicate the change. If this option is set to false, T-Server sends EventError to the client with ErrorCode 186 - Set is in target state.

• The new option vtport-generate-hook-events generates hook events for DNs configured as Voice Treatment Ports.

  vtport-generate-hook-events
  Default Value: true
  Valid Values: true, false
  Changes Take Effect: Immediately

  When set to false, DNs configured in Configuration Manager as Voice Treatment Ports will send EventOffHook and EventOnHook only when the switch sends these events. When set to true, these DNs will behave like regular DNs and T-Server will generate EventOnHook when all parties for the DN have released, and EventOffHook when a party on the DN changes to an active state.

• The new option create-addr-on-register has been introduced to enable clients to register and send requests for DNs that do not have an entry in Configuration Manager. This option can also be used to deny clients the ability to register and send requests for DNs that do not have an entry in Configuration Manager, if necessary.

  create-addr-on-register
  Default Value: true
  Valid Values: true, false
  Changes Take Effect: Immediately

  When set to true, clients can register and send requests for DNs that do not have an entry in Configuration Manager. If set to false, clients registering for DNs not found in Configuration Manager will see the following error message: DN is not configured in CME.

Corrections and Modifications

This release includes the following corrections and modifications:

T-Server now includes the Set Discovery flag in the DirectoryNumberRelease message if the set-discovery option is to a value of true. Previously, T-Server did not include this flag, which resulted in an error from the switch. (ER# 222680365)

T-Server now includes UserData in EventDialing, and subsequent events based on RequestMakeCall requests. (ER# 204232044)

T-Server now re-acquires a DN if a client unregisters and then registers that DN in quick succession. (ER# 234218701)

T-Server now treats the CDN as a regular non-monitored DN after a call is established. As a result, when a new party is added to the call, EventPartyChanged() is sent for the monitored party to show that the otherDN has changed. This is a single-step transfer call model, and is required since EventEstablished(otherDN=CDN) has already been sent. (ER# 230141122)

T-Server now completes a transfer based on the Status Change Disconnect message as long as the Call Type is Complete Transfer, even if there is no Transferred Party Call ID. Previously, the transfer would not be completed if there was no Transferred Party Call ID. (ER# 176025954)

T-Server now correctly matches parties with unknown digits. This corrects scenarios involving external parties with unknown digits, such as, an external party completing a transfer while on a Route Point. (ER# 215502962)

T-Server no longer resets the consult-call-unverified-timeout when a new call to the same address occurs. This eliminates the possibility of a stuck consult call. (ER# 198801056)

T-Server now correctly registers addresses after the link goes down and comes back up. Previously, an internal problem in tracking pending requests could result in T-Server incorrectly throttling registration requests after link up. (ER# 0793181)

T-Server now sends calls routed by the switch software back to the Route Point if Unringing is received for the destination agent position. Previously, these calls were sent back to the Agent's queue. (ER# 82868054)

Top of Page

Known Issues and Recommendations

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

The match-ani Call Overflow (COF) method does not work. As a workaround, any other COF method supported by T-Server may be used. (ER# 226630061)

T-Server now supports Network Skills-Based Routing, with the following exceptions:

1. T-Server supports providing attached data in Network Skills-Based Routing scenarios. Some event attributes reported by T-Server may be inconsistent in such scenarios.
2. T-Server does not support busy treatments on Meridian Mail in Network Skills-Based Routing scenarios.
3. T-Server does not support the use of reporting clients in conjunction with Network Skills-Based Routing.
4. T-Server does not support the Call Forwarded on No Answer feature for Network Skills-Based Routing. Genesys recommends that you configure autoanswer on agent DNs.

The option merged-user-data specifies data that is attached to the resulting call after a call transfer, conference, or merge completion. But when this option is set to its default value (main-only), T-Server may lose user data after Trunk Anti-Tromboning (TAT) if the call was initiated or transferred from an unmonitored DN. See merged-user-data in the Framework 7.6 T-Server for Nortel Communication Server 1000 with SCCS/MLS Deployment Guide for details.

In a T-Server multi-site environment where a call may be routed or transferred several times between different T-Servers, the T-Server where a previous instance of the call is still active may not preserve the Connection ID of the call when it arrives back at that T-Server. The original Connection ID is reported in the FirstTransferConnID attribute and can be used by T-Server instead of the ConnID attribute when backward compatibility mode is enabled. In addition, the LastTransferConnID attribute contains the Connection ID of the call from the previous location.

The installation script on UNIX cannot update configuration data for applications whose host computers contain a dot (".") in their names. Therefore, when configuring a Host object in the Configuration Database, avoid using dots in the value for the Host Name property on the General tab.

If you have to use an IP address (such as 180.170.9.150) or a full host name including the domain name (such as server.genesyslab.com), expect to receive a warning during the installation of any application on this host. The warning message tells you that the installation cannot find the specified object; as a result, the installation script does not update the configuration data for this application. If you see this warning, continue with the installation.

After completing the installation, update the configuration data for an application you installed on this host as follows:

1. Open the Properties window for the Application object in Configuration Manager.
2. Enter the correct values for Working Directory, Command Line, and Command Line Arguments on the Start Info tab.
3. Click Apply and OK to save configuration updates.
4. If using the run.sh file to start the application, verify that the Working Directory, Command Line, and Command Line Arguments are specified correctly in the run.sh file.

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.

HP-UX 11.00 is no longer supported.

Windows 2000 is no longer supported.

Solaris 7 is no longer supported.

Top of Page

Internationalization

Information in this section is included for international customers. There are no known internationalization issues for this product.

Top of Page

Additional Information

Additional information on Genesys Telecommunications Laboratories, Inc. is available on our Technical Support website. The following documentation also contains information about this software.

• Framework 8.0 T-Server for Nortel Communication Server 1000 with SCCS/MLS Deployment Guide contains detailed reference information for the Genesys Framework 8.0 T-Server for Nortel Communication Server 1000 with SCCS/MLS including configuration options and specific functionality.

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

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

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

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

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

Top of Page