Release Note

Top of Page

Supported Operating Systems

New in This Release

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

• Support for new switch version: This release supports switch version Aastra NeXspan R4.2.

Corrections and Modifications

This release includes the following corrections and modifications:

T-Server has been modified to handle unexpected switch reporting for calls transferred between DNs that are monitored by different T-Servers connected to the same switch. Now, T-Server will not fail in this scenario and will attempt to correct the reporting. (ER# 193496670)

T-Server has been modified to ensure that agent states remain correctly synchronized between T-Server and the switch after the release of a business call. (ER# 194154065)

A workaround has been implemented in T-Server to ensure correct release of a held connection irrespective of the completeness of switch reporting. (ER# 193524128)

Monitor Stop functionality has been implemented in T-Server. (ER# 190522551)

Top of Page

Supported Operating Systems

New in This Release

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

Corrections and Modifications

This release includes the following corrections and modifications:

T-Server has been modified to correct a problem with inbound calls being seen as outbound when they come from an IVR. Now, when a call is transferred from an unmonitored device, T-Server will create a new call with type Unknown (if required) and will keep the type until the call is disconnected. Also, if, during a transfer to a monitored device, the origination party of the primary call is changed (for example, due to unexpected PBX reporting) T-Server will not change the reported digits of the external party. (ER# 170748179)

Top of Page

Supported Operating Systems

New in This Release

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

• New configuration option clid-withheld-name has been introduced. This enables T-Server to define a string to replace the caller's DN in the events for other parties when a caller has requested that CLID be withheld.

  clid-withheld-name
  Default Value: PRIVATE
  Valid Values: Any string
  Changes Take Effect: Immediately
  Defines a name that replaces a withheld CLID. If no value is entered (empty string) the withheld CLID will be displayed.

Corrections and Modifications

This release includes the following corrections and modifications:

T-Server has been modified to correct a problem with incorrect call types after TCompleteTransfer when a call is transferred via ISCC. Previously, the call arriving at the remote destination was being reported with call type Unknown, and has now been corrected to show call type Inbound. (ER# 166707395)

A problem with an incorrect call state in call release scenarios has been corrected. Previously, when a party resided on a VTO-type device in established state and the call was released remotely, T-Server reported CallStateRemoteRelease in EventReleased. Now, in such scenarios, EventReleased is reported with CallStateOk. (ER# 150481157)

Support for private data has been implemented in order to enable UUI data to be provided in events. If an event reported by the PBX contains a private data field, T-Server will attach the key GCTI_MATRA_PRIVATE_DATA to the call related to the event. Due to a limitation in the CSTA protocol, the maximum size of the key value is 32 characters. Additional characters will be cut. T-Server trims the string from the private data field, removing trailing blanks, then adds the key to User Data. (ER# 165683007)

A problem with failure of THoldCall has been corrected. Now, T-Server makes additional checks on party states in processing Hold requests. (ER# 165730728)

Top of Page

Supported Operating Systems

New in This Release

This release of T-Server is built with the T-Server Common Part (TSCP) release number 7.5.009.00. 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 section describes new features that were introduced in the initial 7.5 release of T-Server for EADS Telecom M6500 Succession:

• Emulated Agent support: Genesys Emulated Agent functionality has been implemented.
  
  
• Emulated Predictive Dialing support: Support for Genesys Emulated Predictive Dialing functionality has been implemented.
  
  
• Emulated Supervised Routing support: Support for Genesys Emulated Supervised Routing has been implemented.
  
  
• Enhanced No-Answer Supervision: No-Answer Supervision has been enhanced to include private calls. Additionally, No-Answer Supervision can now be applied to recall scenarios.
  
  
• Smart OtherDN Handling support: For T-Server clients that provide the agent ID value as the OtherDN in requests to T-Server, T-Server can convert this OtherDN value, using its knowledge of the association between the agent ID and the DN, in order to ensure correct execution of the request by the switch. For switches expecting an agent ID in the place of a DN for a particular operation, T-Server can convert the OtherDN value supplied by the client, to the agent ID that the switch expects.
  
  
• Additional operating system and platform support: T-Server supports:
  
  
  • AIX 5.3
  • Red Hat Linux 3.0
  • Red Hat Enterprise Linux AS version 4 on Intel platforms
  • Microsoft Windows 2003 32 and 64-bit
  • Microsoft Windows Server 2003 64-bit
  • HP Compaq TRU/64/Alfa version 5.1B
  • Solaris/Sparc 32/64-bit version 10
  • HP-UX/PA 32 and 64-bit v 11i v2
  • VMWare GSX 3.0
    
    
• New switch release: T-Server supports the switch release version 3.2.
  
  
• VoIP Soft Phone support: T-Server now supports VoIP soft phones.
  
  
• Unification of OtherDN content: When the destination or origination party is unknown, T-Server reports the party with DN Txxxxx, where xxxxx is numeric and corresponds to a dynamic ID.
  

• Support for rolling upgrades: In release 7.5, support for rolling upgrades has been implemented.
  

• Support for switch Send DTMF feature: T-Server now supports the switch Send DTMF feature for established external and internal calls.
  

• Support for all types of Hunt Groups: All cyclic and parallel types of Hunt Groups are supported in this release.
  

• Configuration option auto-xfer-dly: New configuration option auto-xfer-dly has been implemented to provide a configurable delay between events applicable to transfer requests after a connection is established.
  
  
• Support in T-Server for business-type classification of calls: In release 7.5, T-Server now identifies calls as either private, business, or work-related, using the new BusinessCall extension key. Valid values are:
  • 0—Private call
  • 1—Business call
  • 2—Work-related call
  
  
• Improved call cleanup: In release 7.5, improvements have been made to the way T-Server performs call cleanup.
  
  
• Support for virtual agent groups: In release 7.5, support for virtual agent groups has been implemented. T-Server now provides consistent reporting of agent group information at login. As soon as T-Server is able to determine the agent group for a particular agent (whether the agent group is provided by the switch or from the value specified in agent-group ), that value is reported in events throughout that agent login session. The switch value, if provided, takes precedence.
  
  
• Extended query capabilities: TQueryServer is able to provide information about which agent work modes are supported by T-Server. These extended capabilities are defined for agent-related events and requests and for TRouteCall,TApplyTreatment,TCallForwardSet,TQueryAddress,TQueryCall, and TMonitorNextCall.
  
  
• Improved link-disconnect scenarios: Link-disconnect and reconnect scenarios have been enhanced. You can now configure T-Server to retain calls across the connection failure, to prevent loss of user data and to reduce traffic when the link is restored. Feature states are also now preserved across the failure. See new configuration options:
  
  
  • restart-period
  • restart-cleanup-limit
  • quiet-cleanup
  • quiet-startup
  • restart-cleanup-dly
  
  
• Additional log link-trace information: T-Server generates additional link-trace information in decodable format in log files. T-Server now provides more detail about logged events, including distinguishing in link-trace information between events from and requests to the switch.
  
  
• Agent-state transitions: T-Server has been enhanced to enable client applications to invoke and receive agent state transitions without provoking superfluous switch reporting.
  
  
• Support for Event Party Propagation (EPP): Support for Event Party Propagation (EPP) has been implemented.
  
  
• Support for unmonitored call scenarios: Additional support for unmonitored scenarios is introduced. Previously T-Server could not determine whether unmonitored calls progressed by distribution or not, irrespective of the call type. You can now configure unmonitored calls to have the new type unknown . When this is the case, moving the monitored party to the unknown call during the transfer engages the current handling of emulated business-call operations.
  
  
• Enhanced Hot HA synchronization handling: When the primary T-Server receives a Backup Ready message from the backup, it now waits until all calls that were created during the backup T-Server’s switch synchronization phase have gone. This means that all remaining calls have the same connection ID in both T-Servers. When no further synchronization is required, the primary T-Server sends a message to the backup indicating that full synchronization has taken place.
  
  
• Smart ConnectionID/RequestID Handling: Smart Connection ID handling has been improved. T-Server can intelligently correct invalid Connection IDs or Request IDs (where there are invalid or absent attributes, or invalid semantics for the call state). Two new configuration options enable backward compatibility:
  
  

  • correct-connid
  • correct-rqid

• Support for distinction between single-step and two-step transfers in event causation: T-Server distinguishes between the AttributeCause reported in EventReleased for single-step and two-step transfers in complex scenarios.
  
  
• Support for reporting of external party states has been implemented.
  
  
• Extended Redirect scenario reporting: T-Server reports AttributeThirdPartyDN in scenarios involving Divert/Overflow from extensions/agents where the PBX provides that information.
  
  
• Support for DNs not configured in Configuration Layer: T-Server supports the handling of TRegisterAddress from its clients for DNs that are not configured in Configuration Layer, and provides extended handling of removal/addition of DNs in Configuration Layer. See configuration options:
  
  
  • extension
  • routing-point
  • accept-dn-type
  • default-dn-type
  • dn-del-mode
  
  
• Processing of Ring Back for held calls: Ring Back has been modified. In transitions from Held to Ringing state, T-Server now translates Request Reconnect from the client into Answer towards the switch.
  
  
• Clearing of initiated calls: In cases when there is an initiated call that has not yet been originated, T-Server now sends only EventOffHook for that device. T-Server also allows RequestReleaseCall (ConnID = 0) in this scenario and sends a Clear Connection request (or equivalent) to the PBX. The response to the requesting client is EventError with the RefID of the ReleaseCall request.
  
  
• Handling of call states Forwarded and Redirected:Handling of call states has been improved. If a call is moved by the switch to another telephony device because the original destination did not answer the call, the Call State is now always reported as Forwarded.
  

• Completion of transfers and conferences: In transfer or conference completion, the remaining call is now always the primary call, regardless of which call (primary or consult) is active at the time of completion.
  

• Conference scenario enhancement: Processing of conference scenarios has been enhanced to enable retrieval of the first conference party. EventPartyChanged is now sent with additional extensions containing a list of all conference parties, as shown below:
  
  
  • NumOfOrigDNs
  • OrigDN-1..
  • OrigDN-N

Corrections and Modifications

This release includes no corrections or modifications.

Top of Page

Known Issues and Recommendations

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

The PBX does not allow a chained consult call to be answered. (ER# 176600493)

An unexpected EventError (Internal T-Server timeout) is generated when a correct EventReleased event arrives after a consult call is released. This is caused by T-Server requesting Release Call when the PBX has already released the call.

Because there is no mechanism to distinguish between the release of a call due to request and the release of a call by the PBX, T-Server clears the request using EventError. (ER# 141446967)

T-Server generates an extra EventRouteRequest when moving a call between Hunt Group members. (ER# 136383048)

You cannot send a parked call to other devices. (ER# 128861814)

The switch Secret Identity feature is only applicable at the switch level, and is not applicable via the CTI link. (ER# 123331822)

CallForward does not report call state Forward in EventRinging on the destination DN. (ER# 88098999)

No events are generated over the link to indicate a CallBack in Progress scenario. (ER# 94388683)

Call control is lost if the call is created before the backup T-Server is started, then switchover takes place. (ER# 119670378)

It is not possible to snapshot devices on the PBX. Therefore if there is a call on a device at monitor start, T-Server is unable to report it. (ER# 85298668)

When an analog phone is left off hook for 3 minutes, the switch generates a Connection Cleared event, triggering an OnHook message from T-Server. However the DN is still off hook and cannot receive calls. (ER# 124682008)

ConnID is not maintained on a remote T-Server:

• After emulated single-step transfer. (ER# 123327382)
• During supervised routing when ANI matching. (ER# 123331849)

IP hard phones are not supported. (ER# 84489)

The switch does not report any event when a phoneset is unplugged or plugged in. Hence, T-Server cannot provide events such as EventDNBackInService and EventDNOutOfService. (ER# 59151)