Jump to: navigation, search

8.5.001.47

Genesys T-Server and UCMA Connector for Skype for Business Release Notes


9.0
Genesys T-Server and UCMA Connector for Skype for Business is part of 9.0 starting in 8.5.001.44.
Release Date Release Type Restrictions AIX Linux Solaris Windows
09/18/17 Hot Fix X

Helpful Links

What's New

This release includes only resolved issues.



Resolved Issues

This release contains the following resolved issues:


If the Skype for Business T-Server application-level option sip-treatments-continuous is set to false, and a ringtone is configured and the ringtone file is present, T-Server now handles the scenario with no-answer on routing properly and the subsequent RequestApplyTreatment is executed correctly. Previously, this configuration made it impossible to apply a treatment—T-Server sent EventError in response to RequestApplyTreatment. (LYNC-3226)


During a single-step transfer, when the transfer destination starts ringing, the transfer originator agent is disconnected from the audio routes and the customer and the agent no longer can hear each other. In addition, in a two-way call, a ringtone (if configured) is connected to the call to play to the customer. Previously, during a single-step transfer performed by an agent, the customer and the agent could still talk while the call was ringing on the transfer destination. (LYNC-3207)


If the SIP Server application used for Remote Recording is configured with ANI or DNIS in the SIP Server option recording-filename, recording does not start. To resolve this, a new Skype for Business T-Server option recording-filename has been introduced in the [remote-recording] section.

recording-filename
Default Value: An empty string
Valid Values: Any valid file name using the variables specified in the description
Changes Take Effect: For the next recording session

Specifies a pattern that is used to generate a filename for call recording when remote call recording is initiated by T-Server for Skype for Business. When this option contains a value, the generated file name is added to the call as UserData with the GSIP_REC_FN key. When this option does not contain a value, the file name is the UUID of the call. The value of this option overrides any value configured in the SIP Server option recording-filename.

Predefined values can be specified in the pattern definition. The following substrings will be replaced with corresponding actual values when creating a filename:

  • $ANI$: The calling number.
  • $DNIS$: The called number.
  • $DATE$: The current date (GMT) in the Y-M-D format.
  • $TIME$: The current time (GMT) in the H-M-S format.
  • $CONNID$: The Connection ID of the call.
  • $UUID$: The UUID of the call.
  • $AGENTID$: The Agent Login ID, if the agent is logged in on the device where the call recording is initiated.
  • $AGENTDN$: The DN where the call recording is initiated.

(LYNC-3202)


If the application-level or DN-level option handle-direct-calls is changed dynamically during a live Workspace Desktop Edition (WDE) agent session, WDE now correctly receives notification about the changed direct-call-processing mode for the DN. (LYNC-3144)



Upgrade Notes

No special procedure is required to upgrade to release 8.5.001.47.


Dependencies

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

Feedback

Comment on this article:

blog comments powered by Disqus
This page was last modified on April 5, 2018, at 13:52.