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 Aastra MXONE CSTA I (formerly T-Server for Ericsson MD110).

• 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 Aastra MX-ONE 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.1.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 Guide.

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 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.1.001.79. 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 or modifications:

T-Server no longer sends an EventReleased and an EventError with the same reference ID to the T-Server client when the agent and customer release a call simultaneously. (UKTS-17672)

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.79. 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 Windows Server 2016 running in native (64-bit) mode. See the T-Server Aastra MX-ONE page in the Genesys Supported Operating Environment Reference Guide page for more detailed information and a list of all supported operating systems. (UKTS-17617)

• DTMF data in T-Lib messages is now hidden in the T-Server log when the configuration option log-filter\hide-tlib-sensitive-data is set to true. (UKTS-17580)

Corrections and Modifications

This release includes the following corrections or modifications:

T-Server now correctly includes a ReferenceID in an EventDialing event after a RequestMakeCall request. Previously, the missing ReferenceID could result in a failed call. (UKTS-17610)

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

• Support for Red Hat Enterprise Linux (RHEL) 6.x and 7.x.

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.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 release does not contain any new features or functionality.

Corrections and Modifications

This release includes the following corrections or modifications:

T-Server no longer becomes unstable after receiving the CSTA event ConnectionCleared with a valid dialingNumber in the CSTA Connection structure and a releasingDevice of notKnown : NULL. (UKTS-17512)

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

• Support for Windows Server 2012.

• T-Server now enables you to specify different rules for internal and external call forwarding. T-Server matches the forwarding destination number against a set of rules and forwards calls accordingly.

  Configure any number of rules in a configuration section called fwd-type-rules, using the following format:

  rule-1 as pattern=AAA;type=external
  ...
  rule-N as pattern=AAAA;type=internal

  For pattern definition, use Augmented Backus-Naur Form (ABNF) notation. See RFC-2234 and the "Number Translation Rules" chapter in the T-Server Deployment Guide for more information.

  If the pattern specified in the rule matches the forwarding destination, then T-Server applies the specified forwarding type, "external" or "internal".

  If no rules are configured or the forwarding destination number does not match any configured rule, then T-Server determines the forwarding type using the maximum length of the monitored number (which is the old behavior).

  (UKTS-17255)

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

• AttributeCallId now stores any changes to CallId made at the switch during the entire life of a call. (UKTS-17188)

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

Corrections and Modifications

This release includes the following corrections or modifications:

T-Server now supports backwards compatibility for the 7.6 version of T-Server for Ericsson MD110 in emulated After-Call Work (ACW) scenarios for real agents. Previously, T-Server sometimes did not apply the emulated ACW for an agent in such scenarios.

Note: The name of T-Server for Ericsson MD110 changed to T-Server for Aastra MXONE CSTA I in version 8.1.

(ER# 316553663)

If a call is transferred from a CAS port to a monitored extension by default (the analog-transfer configuration option is set to 1), T-Server no longer keeps the CAS port in off-hook state.

Note: This issue was corrected for Solaris.

(ER# 297294252)

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.

There are no restrictions for this release. This release does not contain any new features or functionality.

Corrections and Modifications

This release includes the following correction or modification:

T-Server now supports the sip-trunk-id configuration option, which allows T-Server to make a difference between calls that have the SIP trunk ID as the value that is specified in the sip-trunk-id option. This option is set in the TServer section of the T-Server Application object.

sip-trunk-id
Default Value: An empty string
Valid Values: A comma-separated list of SIP trunks (as reported by the PBX), or use "*" to indicate that all trunks are SIP trunks.
Changes Take Effect: Immediately

Specifies that T-Server should treat calls that have the same SIP trunk ID as the value specified in the sip-trunk-id option as separate calls. The PBX generates the SIP trunk ID by using the following format: a three digit routing number, a three digit server number, and a three digit trunk number.

Previously, T-Server might have reported multiple calls from the SIP trunk as one call. (ER# 306754470)

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

Corrections and Modifications

This release includes the following corrections or modifications:

If a call is transferred from a CAS port to a monitored extension by default (the analog-transfer configuration option is set to 1), T-Server no longer keeps the CAS port in off-hook state. (ER# 297294252)

Note: This issue was corrected for Windows.

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

Corrections and Modifications

This release includes the following corrections or modifications:

T-Server now restores party information using the CSTA Conferenced event. Previously, issues could happen when the PBX reported an external party release for the party that actually remained on the call. (ER# 289953954)

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.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 a hot fix for this product. This release does not contain any new features or functionality.

Corrections and Modifications

This release includes the following corrections and modifications:

T-Server no longer occasionally becomes unstable when the PBX reports a CSTA Transferred event with an incomplete list of new connections (such as, the device identifier in the connection list is missing). (ER# 287221753)

The following Known Issues have been also corrected: ER# 243487529, 243723721, 243487697, and 243516834.

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.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 section describes new features that were introduced in the initial 8.1 release of T-Server for Aastra MXONE CSTA I.

• T-Server no longer connects to applications that have disabled status in the configuration environment.
• The default value of the background-processing configuration option has been changed to true.
• T-Server now supports the Unresponsive Process Detection feature. The following configuration options enable this feature:

  • heartbeat-period
  • hangup-restart

  See option descriptions in your T-Server Deployment Guide. For more information, refer to the Framework 8.0 Management Layer User’s Guide.
• T-Server now supports IPv6. For more information, refer to the Framework 8.1 Deployment Guide.
• T-Server now supports vSphere 4 Hypervisor.
• T-Server now supports Acresso FLEXNet Publisher 11.9 license manager.
• T-Server is now supported on the following platforms:

  • AIX 7.1 64-bit
  • HP-UX Itanium (version 11i v3)
  • Red Hat Enterprise Linux 5 64-bit

• T-Server now supports Aastra MXONE Release 4.1 with SP3.
• Error handling in T-Server has been enhanced to distribute the following LMS messages:

  • 35404 - "DN %s: association %s invalid" (incorrect ADN configuration)
  • 36405 - "Client %x(%s): device (%s) already involved in a call" (request to the device already in the same call - eg Routing)
  • 36403 - "Client %x(%s): no held call on device (%s)" (Request Reconnect call without held call)
  • 36404 - "Client %x(%s): no active call on device (%s)" (Request Alternate call & Request Mute Transfer)

  (ER# 214052846)

Corrections and Modifications

This release also includes the following corrections and modifications:

T-Server now correctly reports events in the scenario where an incoming call has the same originator (ANI) as a DN monitored on the switch. (ER# 277149838)

T-Server now operates correctly when DNs are disabled and enabled in Configuration Manager in quick succession. Previously, T-Server might have entered a continuous processing loop in such a scenario. (ER# 281536991)

T-Server no longer becomes unstable after transfer is completed to an emulated Routing Point with supervised routing in progress. (ER# 278712725)

The option kpl-loss-rate has been removed from T-Server. (ER# 275364174)

Top of Page

Known Issues and Recommendations

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

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.

PBX limitation: outbound calls made through an ISDN trunk cannot be routed through the same trunk. (UKTS-17220)

When agents makes multiple (chained) consultation calls during inbound or outbound calls, the switch may fail to report events for Reconnect or Retrieve call. PBX failure to report such events may affect Emulated Predictive Call and Agent No Answer supervision functionality in T-Server. (UKTS-17221)

Switches do not support blind transfer completion if the other party in a transferring call is On Hold. (UKTS-17222)

When a consultation call is mute transferred or blind transferred to a routing point, consecutive routing to the new destination produces a new call in the switch. This incorrect reporting causes the loss of Genesys-specific data attached to the call prior the routing. (UKTS-17223)

PBX limitation (MX-ONE 4.1 SP3). The PBX does not send a CSTA ConnectionCleared event for releasing a call on the origination DN in the following scenario:

1. An extension on Site 1 makes a call to an external extension on Site 2 through an ISDN Trunk.
2. The external extension on Site 2 answers the call, then initiates a transfer to an ACD Queue using the ISCC transaction type Route (at the same site as the first extension through an ISDN Trunk). The call diverts to an agent. The initiator completes the transfer before the agent answers.
3. The agent answers and the origination extension releases the call. The PBX does not send a CSTA ConnectionCleared event on releasing the call.

As a result, the call becomes stuck. This behavior does not affect the primary T-Server, which is able to clear stuck calls using the snapshot. However, it may cause the backup T-Server to become unstable. To avoid this, the T-Server call-cleanup mechanism needs to be set to stop stuck calls from accumulating in memory. (ER# 296278209)

PBX limitation (MX-ONE 4.1 SP 3). T-Server does not report an EventReleased message in the following scenario:

1. An extension on Site 1 makes a call to an extension on Site 2.
2. The extension on Site 2 initiates and completes the transfer to the ACD Queue on Site 1 through an ISDN Trunk.
3. The call is distributed to an agent who answers and releases the call.

After the agent releases the call, T-Server does not report EventReleased, because the PBX does not report ConnectionCleared on the agent. (ER# 287562523)

PBX limitation (MX-ONE 4.1 SP 3). T-Server incorrectly reports an EventAbandoned message in the following scenario:

1. An extension on Site 1 makes a call to an extension on Site 2.
2. The extension on Site 2 answers the call, then initiates and completes a transfer to the Hunt Group (CTI Group with the Hunt Group member) on Site 1.
3. The Hunt Group (by using the TRouteCall request) routes the call to another extension on Site 2.

PBX limitation (MX-ONE 4.1 SP 3, AL7 SP2). T-Server is not able to set or cancel call forwarding to an external device via CTI. (ER# 284960631)

PBX limitation (MX-ONE 4.1 SP 3, AL7 SP2). T-Server incorrectly reports an EventAbandoned message in the following scenario:

1. One extension makes a call to another extension on another site through an ISDN Trunk.
2. The second extension initiates a transfer back to the ACD Group and the call is distributed to an agent (at the same site as the first extension).
3. The second extension completes the transfer before the agent answers.
4. The agent doesn't answer and the switch timeout expires (call has been redirected back to the ACD Group).

After the call redirects back to the ACD Group, T-Server reports EventAbandoned to the agent instead of EventReleased, because the switch reports trunk optimization after the transfer, but fails to report that the call was returned back to the ACD Group. (ER# 284960640)

PBX limitation (MX-ONE 4.1 SP 3, AL7 SP2). T-Server does not report an EventPartyChanged message in the following scenario:

1. A call is established between a monitored extension and an unmonitored extension.
2. The unmonitored extension initiates a transfer to an external extension (extension on another site) via ISDN Trunk.
3. The transfer completes before the external extension answers.

There is no EventPartyChanged reported on the monitored extension, because the switch does not report unmonitored transfer completion to T-Server of monitored extensions. The switch reports that the call was released and established with a new connection ID instead of a transfer event. T-Server is unable to use this report. (ER# 284960647)

When a group of T-Server DNs is disabled and enabled in configuration multiple times, multiple monitors on the same DN may be requested on the switch. T-Server functionality is not affected, but this scenario may result in a resource leak on the switch. (ER# 284960678)

An Agent No Answer action may not be executed when a request for No Answer supervision on that Agent is in progress. Use the option agent-emu-login-on-call = true when a workaround is required. (ER# 284960684)

PBX limitation (AL7). When an agent has immediate call forward set to a CTI Group, and a call is made to the agent, T-Server reports an incorrect CallState of Ok on the CTI Group. The reason for this is that for the CTI Group, the PBX incorrectly reports a cause of redirected instead of a cause of CallForwardAlways, which is reported on the originator.

The cause that is reported on a CTI Group should be the same as the cause on the originator (CallForwardAlways). In the scenario above, T-Server cannot use the cause for Reporting since the cause on the originator and on the CTI Group are different. (ER# 267335717)

PBX limitation (MX-ONE 3.2 SP2). An incorrect ConnID is generated on EventRinging for a destination DN on an internal call, and the switch reuses the Call ID from an outbound call for an inbound call in the following scenario:

The cast-type option is set to route.
The event-propagation option is set to list.
The consult-user-data option is set to separate.
The use-data-from option is set to consult-user-data.

1. A call is made from an agent on ODN1 on an MX-ONE switch, to ODN2 on a MD110 switch.
2. A RequestInitiateTransfer is made from the agent on ODN2 to a native Routing Point (divert from the Queue) through ISCC.
3. A RequestCompleteTransfer is performed by the agent on ODN2.
4. The call is routed by the native Routing Point to the agent on DN1.

T-Server generates an incorrect ConnID for EventRinging on DN1, and T-Server generates a call state of Redirected on DN1 instead of Ok because the switch reuses the Call ID from the outbound call (made through the outbound Trunk) for the inbound call (from the incoming Trunk). (ER# 229341751)

PBX limitation (MX-ONE 4.0, AL4 SP21). When setting an Absence code on an IP Phone (via RequestDNDOn), the request times out because there is no reporting from the switch. (ER# 243481471)

PBX limitation (MX-ONE 3.2 SP2). Supervised routing of a call to a DN does not work if the call is made from a SIP DN in the following scenario:

The supervised-route-timeout option is set to 5.

1. An agent on SIP DN1 calls the Hunt Group (Emulated Routing Point).
2. The Hunt Group (Emulated Routing Point) performs a supervised route of the call to ODN1.

The CSTA error: systemResourceErrors : generic is received.

(ER# 234796352)

MX-ONE: T-Server generates an incorrect EventAbandoned instead of an EventReleased on an ADN in the following scenario:

1. An agent on ODN1 makes an outbound call to external DN1.
2. External DN1 answers the call.
3. The agent on ODN1 does an initiate transfer of the call to ACD Queue2 (ADN2)
4. The agent on ODN1 does a complete transfer of the call.
5. The agent on ADN2 answers the call
6. The agent on ADN2 does a mute transfer to emulated Routing Point1
7. Emulated Routing Point1 routes the call to emulated Routing Point2
8. Emulated Routing Point2 routes the call to ACD Queue3 (ADN3)
9. External DN1 releases the call

T-Server generates an incorrect EventAbandoned instead of EventReleased on ADN3 with a call state of Forwarded. (ER# 243487529)

MX-ONE: T-Server generates an incorrect releasing party in the following scenario:

1. An agent on ODN1 calls ACD Queue1.
2. The agent on ADN1 answers the call.
3. The agent on ADN1 does a consultation call to the agent on ODN2.
4. The agent on ODN2 answers the call.
5. The agent on ODN1 completes the call transfer.
6. The agent on ODN2 releases from the call.

T-Server generates ReleasingParty:1 Local instead of 2 Remote on ODN1. (ER# 243723721)

MX-ONE: T-Server generates incorrect call state of Forwarded instead of Ok in the EventAbandoned on the Emulated Routing Point in the following scenario:

1. An agent on DN1 makes an internal call to an emulated Routing Point.
2. The emulated Routing Point does a supervised route to an ACD Queue.
3. The supervised route timeout expires.
4. The agent on DN1 releases the call.

(ER# 243487697)

MX-ONE: The release call on ADN1 is not reported in the following scenario:

1. An agent on ODN1 makes a call to the ACD Queue (ADN1).
2. The agent on ADN1 answers the call.
3. The agent on ADN1 does a mute transfer to an external DN.

(ER# 243516834)

PBX limitation. The MX-ONE PBX only supports one distribution method to Hunt Group members:

Sequential Searching - Linear Hunt Group, where a new call always goes to member Number1, if free. If Number1 is busy, then it goes to Number2, if Number1 and Number2 are busy, then it goes to Number3. (ER# 230165672)

The following is a statement from Aastra (previously Ericsson):

In order to maintain the same call ID during a whole Call Deflect scenario, every involved device, including logical devices such as ACD groups, must be monitored. For example, if a PBX group is involved in the deflect scenario, the Call ID may change because PBX groups cannot be monitored.

Regarding Genesys:

In Genesys, this will cause problems in some Emulated Routing scenarios, as Hunt Groups cannot be monitored. Therefore, T-Server may not be able to maintain the Call ID and, as a result, attached data will be lost. (ER# 71793929)

PBX limitation (MX-ONE 3.1 SP3, AL4 SP20). An unexpected extra transfer event from the Application Link/switch causes an unexpected EventPartyChanged on the transfer destination in the following scenario:

1. An outbound call from MX-ONE is made to an external device which answers.
2. The outbound originator makes an emulated single-step transfer to an internal queue.
3. The call is delivered to an ADN.

(ER# 195627900)

PBX limitation (MX-ONE 3.1 SP3, AL4 SP20). The switch does not support treatments. (ER# 211241912)

PBX limitation (MX-ONE 3.1 SP3, AL4 SP20). The switch does not support call parking. Hold call functionality is used instead. (ER# 211241748)

PBX limitation (MX-ONE 3.1 SP3, AL4 SP20). The switch does not provide the relevant CTI events across the link to support the Intrude feature. (ER# 211241776)

PBX limitation (MX-ONE 3.1 SP3, AL4 SP20). Four-party conferences are not supported via CTI, but can be created manually via the handset. (ER# 211241969)

PBX limitation (MX-ONE 3.1 SP3, AL4 SP20). The lock/unlock status of ODN-only devices is not reported by the Application Link at monitor start. Therefore, T-Server reports the status of these devices as unknown. (ER# 211241884)

PBX limitation (MX-ONE 3.1 SP3, AL4 SP20). Consultation calls are always made from the ODN. If the primary call is on ODN, then the consultation call is made from the same ODN.

If the primary call is on an ADN, then the consultation call is made from the associated ODN. (ER# 211242017)

PBX limitation (MX-ONE 3.1 SP3, AL4 SP20). Reporting of conference events from the Application Link is incomplete when a conference party is unmonitored. When devices are released, they have different Call IDs. (ER# 211241411)

PBX limitation (MX-ONE 3.1 SP3, AL4 SP20). Application Link reports In/Out of Service events when VoIP agents log in manually. Only emulated agents are supported by T-Server with these devices.  (ER# 211242119)

PBX limitation (MX-ONE 3.1 SP3, AL4 SP20). The destination for Forward On Busy and Forward On No Answer cannot be dynamically set via CTI. (ER# 211242054, 211242081)

PBX limitation (MX-ONE 3.1 SP3, AL4 SP20). It is not possible to redirect or route a call to a DN which has Immediate Forwarding set. (ER# 211242156)

PBX limitation (MX-ONE 3.1 SP3, AL4 SP20).  When there is a call on an ADN and another call on the ODN, the request TAlternate has to be made from the active call leg, because this is the only way to populate a Reference ID on the correct event. (ER# 211242203)

PBX limitation (MX-ONE 3.1 SP3, AL4 SP20). To complete a conference, when the conference initiator is an ADN, it is necessary to alternate the primary and consultation call, so that the primary call becomes the active call (primary call on ADN), and then complete the conference. The one exception to this rule is when the primary call is Outbound. In this situation it is possible to complete the conference without alternating the call. However, the call that remains after conference completion is the consultation call that was on the ODN - the primary call on the ADN will be released. (ER# 211242285)

PBX limitation (MX-ONE 3.1 SP3, AL4 SP20). The Application Link does not report conference calls when queried after the switch link disconnects and then reconnects. (ER# 211076244)

Emulated Redirect from an ADN or an analog device is not supported. T-Server will attempt to use a native redirect with these devices. (ER# 60333842, 60333836)

A call's position in queue is cleared when one party places the call on Hold. In addition, an Initiate Transfer also clears the position. See the Maintain Position in Queue section of the Deployment Guide for more details. (ER# 45841606, 50549339)

An incompatibility exists between T-Server and URS when T-Server option call-retain-in-queue is set to keep and the Maintain Position in Queue feature is enabled (see the Deployment Guide).

Any time an attempt is made to transfer a call back to the Routing Point, the request fails. This prevents the keep value being useful for the following scenarios:

• transfer-to-agent = false
• Multiple treatments when the call has to be returned by URS back to the Routing Point
• IVR making a transfer back to a Routing Point

(ER# 49581107)

The MD110 switch does not support a native RequestClearCall. It is only supported within T-Server when used in conjunction with the Maintain Position in Queue feature to drop a call completely. (ER# 50549313)

Conference reporting is unreliable when used in conjunction with the Maintain Position in Queue feature. (ER# 45841618)

The Application Link does not report conference calls when queried after the switch link disconnects and then reconnects. (ER# 40142095)

OCS does not have separate Ready/NotReady states for DNs on a place. It has OffHook/OnHook states for DNs only. After receiving EventAgentReady OCS considers that the agent is ready to take an outbound call. OCS does not know which DN is responsible for receiving an outbound call. If the Position DN works with outbound calls, use only this DN to change agent status (Ready/NotReady). (ER# 72251)

PBX limitation (BC12 SP5, AL 4 SP 9). If an analog or CAS port is left in an off-hook state without a call, after a switch timeout, the switch will issue a Connection Cleared followed by OutOfService. T-Server then issues EventOnHook and EventDNOutOfService. To get the device back in service, you must place the analog or CAS port back on-hook. (ER# 89117)

PBX limitation (BC12 SP5, AL 4 SP 10 HF 03). In the following scenario, the switch does not report devices as held, but reports them as established. Switch reporting is correct if only one of the devices is held.

1. Create internal call between 2 ODNs.
2. Put both on Hold.
3. Restart T-Server.

(ER# 97473, 97474)

PBX limitation (BC12 SP5, AL 4 SP 10 HF 06). In the following scenario, the switch does not report the dialing party on startup, and reports the alerting party with call ID=1.

1. Alerting on an internal call from another monitored DN.
2. Start T-Server.
3. After link is, connected start a T-Server client and register for the alerting DN.
4. The client requests TQueryInfoDNStatus.
5. The call is answered.

After the call is answered, the switch assigns a new call ID=2 to the call, and stops reporting for call ID=1. (ER# 99612, 99611)

PBX limitation (BC12 SP5, AL 4 SP 10 HF 03). Because of switch reporting, T-Server cannot report Call State Redirected on Diverted and Ringing after a call arrives from a Queue. (ER# 92193, 92194)

PBX limitation (BC12 SP5, AL 4 SP 10 HF 03). In the following scenario, the switch does not report transfer events on ADN B.

1. ADN A establishes a call to ADN B.
2. ADN B establishes the consultation to ADN C.
3. ADN C establishes the consultation to ADN D.
4. Attempt to complete the transfer on ADN B.

(ER# 93262, 91361)

PBX limitation (BC 11, AL 4 SP 8 HF 02). In the following scenario, the switch only issues Connection Cleared for the consultation destination. No Connection Cleared is issued for consultation call on the CAS port. Eventually the switch places the CAS port in and out of service to clear the device.

1. Internal call to CAS port.
2. Answer the call.
3. From the CAS port initiate an internal transfer.
4. Answer the consultation call.
5. Release the consultation call at the consultation destination.

(ER# 83171, 83170)

PBX limitation (BC 11, AL 4 SP 8). When T-Server performs login using option use-makecall-login set to true, Application Link indicates that the device is on hook. However the line where login is requested remains in an off-hook state. It remains in this state until the switch times out or another CTI request (for example, Ready or NotReady) is made. (ER# 77661, 75195)

PBX limitation (BC 11, AL 4 SP 8 HF 02).The Genesys call model requires that if a call is forwarded to a device, then the first event on that device should have call state Forwarded. The Ericsson MD110 does not always report the call as Forwarded, so T-Server cannot reliably report this. In such cases T-Server reports forward state as OK. (ER# 77143, 77144)

PBX limitation (BC 11, AL 4). Genesys cannot guarantee the following at T-Server start/restart:

• Before Application Link 4, Service Pack 4: the initial state for device and agent work modes.
• With Application Link 4, Service Pack 4: Ready/NotReady status for ODNs/ADNs.
• With Application Link 4, Service Pack 7+:Ready/NotReady status for ODNs only.
• With Application Link 4, Service Pack 13: NotReady state for ADNs when ODN Ready and ADN NotReady. All other ODN/ADN combinations for Ready can be synchronized. In an ODN-only place, T-Server cannot synchronize if the ODN is logged in when T-Server is started. You must manually logout the ODN in order to be able to use CTI functionality.

(ER# 77779, 77780)

PBX limitation (BC 11, AL 4, SP 7). Application Link does not report conference completion correctly when all parties are internal and the conference controller is an unmonitored device. (ER# 66300, 77666)

OCS two-step transfer causes problems when a call is established on emulated Routing Points. When the call is routed with either supervised routing or RouteTypeReject, upon the call being established, OCS tries to complete the transfer. (ER# 14896377)

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 Red Hat Enterprise Linux 3.0 operating system is no longer supported.

The Solaris 8 operating system is no longer supported.

The Tru64 UNIX operating system is no longer supported.

The AIX 5.1 and 5.2 operating systems are no longer supported.

Top of Page

Internationalization

Information in this section is included for international customers.

There are no known internationalization issues for this product.

Top of Page

Additional Information

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

• The Framework 8.1 T-Server for Aastra MXONE CSTA I Deployment Guide contains detailed reference information for the Genesys Framework 8.1 T-Server for Aastra MXONE CSTA I 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 contain the T-Library API, information on TEvents, and an extensive collection of call models.

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

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

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

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. To determine the version of a document, check the version number that is located on the second page in PDFs or on the About This File topic in Help files.

Top of Page