Release Note

T-Server for Alcatel A4200/OXO 


Genesys Telecommunications Laboratories, Inc. © 2008



Release Number AIX HP-UX Linux Solaris Tru64 UNIX Windows [11/07/08] – General X X X X X X

Link to 7.0 Product Release Note (Cumulative)
Known Issues and Recommendations
Discontinued Support
Additional Information


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

This release note applies to all 7.6 releases of T-Server for Alcatel A4200/OXO.

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.

Release Number [11/07/08] – General

Supported Operating Systems
New in This Release
Corrections and Modifications

Supported Operating Systems

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

New in This Release

This section describes new features that were introduced in this initial 7.6 release of T-Server for Alcatel A4200/OXO:

Corrections and Modifications

This release includes the following corrections and modifications that were made between release 7.0 and the initial 7.6 release:

T-Server reporting of has been modified to resolve a mismatching problem between OtherDN and AttributeANI. The following scenarios are impacted: 

(ER# 178959712)

Top of Page

Known Issues and Recommendations

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

When an invalid number is dialed, T-Server reports a misleading EventDestinationBusy message rather than any messaging indicating that the number is invalid. (ER# 213368791)

Found In: 7.6 Fixed In:

There is a 9-second delay between TAnswerCall and EventEstablished when a call ringing on a DN with forwarding set is answered. (ER# 212693588)

Found In: 7.6 Fixed In:

When the CallForwardCancel status of a DN in T-Server is not synchronized with the DN status on the switch, the only way to resynchronize the statuses is to stop and restart T-Server. (ER# 211902631)

Found In: 7.6 Fixed In:

When an outbound call from an unmonitored device is blind-transferred to a Routing Point, the routed call cannot be answered, and the call becomes stuck. (ER# 210451085)

Found In: 7.6 Fixed In:

After call intrusion, the call state received from the switch for the primary call is incorrect. (ER# 210451087)

Found In: 7.6 Fixed In:

T-Server may generate an incorrect EventError Call has disconnected on the Routing Point in the following scenario:

  1. TMakePredictiveCall with prd-dist-call-ans-time configured.
  2. The customer answers and then releases the call before it is routed to an agent.

The rest of the call flow is correct. (ER# 123787509)

Found In: 7.0.204 Fixed In: 7.6

T-Server does not populate ThisQueue on all events after the call is routed to DN2 in the following scenario:

  1. Inbound call to Routing Point.
  2. Supervised route to DN1.
  3. Do not answer.
  4. Supervised routing expires and the call is recalled to the Routing Point.
  5. Re-route to DN2.

(ER# 123787523)

Found In: 7.0.204 Fixed In: 7.6

When a customer releases a predictively dialed call while it is still ringing, the EventReleased on the Routing Point receives an incorrect call state of No Answer. (ER# 123787517)

Found In: 7.0.204 Fixed In: 7.6

A consult call is routed from an emulated Routing Point (which has at least 2 members) to an external device without supervision. This is repeated four times. After this, when a call is made to the Hunt Group, a Delivered event for one Hunt Group member is received, followed by an Alerting event on both Hunt Group members (with the same CallID), and finally a ConnectionCleared on both Hunt Group Members, so the consult call is dropped. This continues happening on all calls to the Routing Point for a few minutes. Eventually the problem clears itself,  at which point it is possible to continue making calls to this Routing Point. (ER# 123091669)

Found In: 7.0.204 Fixed In: 7.6

The PBX might reject a request to route an Outbound call to an external destination if the Outbound call is transferred to a Routing Point. The scenario is as follows:

  1. DN1 establishes a call to an external destination.
  2. DN1 initiates transfer to an emulated Routing Point.
  3. DN1 completes the transfer.
  4. The call is routed to the external destination.
  5. RouteCall is rejected with Incorrect Object State.

(ER# 122852657)

Found In: 7.0.204 Fixed In: 

DN1 has call forwarding set to an external device. DN2 redirects a call to DN1. In this scenario, EventReleased is generated for DN2 but no more reporting is received from the PBX for the redirected side of the call. However, it is still possible to control DN1 via CTI. (ER# 123091649)

Found In: 7.0.204 Fixed In: 

A non-supervised Predictive Call is made and then, without supervision, is routed to an agent. At this stage, before the agent answers the call, if the customer or agent releases the call, the PBX does not generate an EventReleased for the other side of the call. (ER# 123091659)

Found In: 7.0.204 Fixed In: 

After a supervised call is recalled to a Routing Point because the destination did not answer, if the call originator then abandons the call, there is a delay of about 30 seconds before the switch issues Connection Cleared. (ER# 9405036)

Found In: Fixed In: 

T-Server gets no notification from the switch when an IP phoneset is unplugged from the network or plugged back into the network. (ER 89780, 89781)

Found In: R3.10/20.004 and T-Server Fixed In: 

The CTI link might reset in the following scenario: 

  1. DN1 calls DN2.
  2. DN2 males a consult call to DN3.
  3. DN3 makes a consult call to an external number.
  4. DN3 completes conference.
  5. DN3 releases, then DN2 quickly completes conference. (ER 90247, 89777)
Found In: Switch R3.10/20.004 Fixed In:

OmniPCX Office R3.1 sometimes drops an inbound call routed to a forwarded extension. (ER 89852, 89736)

Found In: Fixed In:

When a DN is conferenced into a call, then that DN releases from the conference, the conference controller is wrongly placed into Held state. (ER 87023, 87029)

Found In: Fixed In:

When a conference controller requests ReleaseCall in a three-party conference, all three parties are released. (ER 86260, 86265)

Found In: Fixed In:

After a transfer to an invalid external DN, the VTO port goes off-hook and stays off-hook. This is caused by the PBX generating a Service Initiated event for the VTO Port which is why it goes off-hook. The switch then returns a Failed event for this new call, but no Connection Cleared event is sent, leaving the port off-hook.

A workaround is available by setting the following options in VT server: 

OverloadScript= -1

DetectRing= 1
DetectRelease= 1
DetectRingCount= 0
NoTEventRingingTimeoutSec= 1

With these options set, VTO detects the OffHook, picks up the line, waits for EventRinging for 1 second, will not receive it, plays back the System Error Script and hangs up. The port is then free for use. (ERs 80129, 79873)

Found In: 7.0.2, switch R 2.1 Fixed In:

The switch distributes incorrect CSTA messages when an inbound call is routed to a busy Routing Point. (ER 78279, 50484)

Found In: Switch R 1.1 Fixed In:

In the following scenario the CTI link is broken by the switch:

  1. Consultation call to internal busy device (On Call)
  2. Complete conference

(ER 78280, 50434)

Found In: 6.5.3 Fixed In:

When a manual internal call is made to a to DND device the call fails as expected, but the switch does not distribute to the CTI client a failure reason. (ER 78283, 42991)

Found In: R1.0-56.005 Fixed In:

The switch generates an incorrect object state when an inbound call is redirected to an invalid internal destination. (ER 79186, 34252)

Found In: R1.0-56.005 Fixed In:

In the case of an ISDN trunk between an A4400 and an A4200 Office, the A4200 Office (not the OmniPCX Office) releases the call if it is an inbound call diverted to an extension. This problem does not occur for real ISDN trunks.

As a consequence, where an ISDN trunk connects an A4400 and and A4200 office, you must use supervised routing (Consult Transfer instead of Redirect request).(ER 58183, 79002)

Found In: 6.5.3 Fixed In:

When ISCC option cast-type has the value direct-ani , call matching based on ANI cannot be performed on a remote location when:

  • Case 1 - A call (inbound, internal, consultation) is routed using URS to a remote location 
  • Case 2 - An emulated single-step transfer is performed from a party that did not intiate the primary call (A calls B, B performs single-step transfer to a remote location).

This is because the ANI value changes when the call leaves the emulated Routing Point (case 1 above) or leaves party B (case 2 above). Therefore, neither ConnID nor user data can be maintained at the remote location. (ER 51114, 51039)

Found In: 6.5.300 Fixed In:

Transfer to a Routing Point cannot be completed or reconnected when a call is routed and either route supervision or answer supervision is enabled, because the PBX does not allow completion or reconnection of the first consult call. (ER 50543, 80148)

Found In: Switch R 2.1 Fixed In: 7.6

In a scenario where a call is parked and retrieved, if the call is retrieved during the retain timeout then the connection ID of the call is maintained. However if the call is retrieved after the retain timeout expires, T-Server creates a new connection ID.  (ER 33034, 80181)

Found In: 6.1.002 Fixed In:

Top of Page

Discontinued Support

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

The Solaris 2.6 operating system is no longer supported.

Discontinued As Of: 7.6

The Windows NT operating system is no longer supported.

Discontinued As Of: 7.6

Top of Page


Information in this section is included for international customers. There are no known restrictions specific to international customers.

Top of Page

Additional Information

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

  • The Framework 7.6 T-Server for Alcatel A4200/OXO Deployment Guide provides detailed reference information for the Genesys Framework T-Server for the Alcatel A4200/OXO switch including configuration options, known limitations, and switch functionality.

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

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

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

Top of Page