Genesys T-Server and UCMA Connector for Skype for Business

This PDF is generated from authoritative online content, andis provided for convenience only. This PDF cannot be usedfor legal purposes. For authoritative understanding of whatis and is not supported, always use the online content. Tocopy code samples, always use the online content.

Release Notes 8.5.x

Genesys T-Server and UCMAConnector for Skype for Business

12/31/2021

www.princexml.com

Prince - Non-commercial License

This document was created with Prince, a great way of getting web content onto paper.

Table of ContentsGenesys T-Server and UCMA Connector for Skype for Business 8.5.x Release Note 3

Known Issues and Recommendations 7Release 8.5.0 14

8.5.001.67 158.5.001.65 178.5.001.63 198.5.001.54 218.5.001.50 238.5.001.49 268.5.001.47 288.5.001.44 318.5.001.41 348.5.001.37 368.5.001.36 388.5.001.32 408.5.001.29 428.5.001.24 448.5.001.23 468.5.001.20 488.5.001.18 508.5.001.17 528.5.001.14 548.5.001.12 568.5.001.11 588.5.001.10 608.5.001.09 628.5.001.07 648.5.001.02 678.5.000.94 698.5.000.87 728.5.000.69 748.5.000.51 76

9.x

Genesys T-Server and UCMA Connector forSkype for Business 8.5.x Release Note

Genesys T-Server and UCMA Connector for Skype for Business ispart of 9.x starting in 8.5.001.44.

This Release Note applies to all 8.5.x releases of Genesys T-Server and UCMA Connector for Skype forBusiness. Links in the Available Releases section enable you to access information regarding aspecific release.

ImportantThis release note applies to T-Server and both UCMA Connector for Skype for Business(which supports UCMA 5.0 with Skype for Business) and UCMA Connector for MicrosoftLync (which supports UCMA 4.0 with Microsoft Lync 2013). The two UCMA Connectorsare installed from separate installation packages.

Available Releases[+] Note about release orderReleases are listed by version number rather than in date order. For this reason, a recent release maybe listed after earlier releases, if the version number is lower. Except when otherwise noted in theinformation for a specific release, each release includes all of the features and corrections that wereintroduced for the applicable operating system at earlier dates, regardless of the version numbering.

Release 8.5.0:

Release ReleaseDate

ReleaseType Restrictions AIX Linux Solaris Windows

8.5.001.67 10/01/18 GeneralUnderShippingControl

X


X


X

Genesys T-Server and UCMA Connector for Skype for Business 8.5.x Release Note

Genesys T-Server and UCMA Connector for Skype for Business 3

Release ReleaseDate


8.5.001.54 11/09/17 Hot Fix X8.5.001.50 10/10/17 Hot Fix X


X

8.5.001.47 09/18/17 Hot Fix X


X

8.5.001.41 07/28/17 Hot Fix X


X

8.5.001.36 06/01/17 Hot Fix X


X


X

8.5.001.24 03/14/17 Hot Fix X


X

8.5.001.20 02/03/17 Hot Fix X8.5.001.18 01/20/17 Hot Fix X


X

8.5.001.14 12/08/16 Hot Fix X8.5.001.12 11/23/16 Hot Fix X8.5.001.11 11/17/16 Hot Fix X8.5.001.10 11/10/16 Hot Fix X8.5.001.09 11/03/16 Hot Fix X8.5.001.07 10/26/16 Hot Fix X


X


X

8.5.000.87 05/27/16 General UnderShipping X



Release ReleaseDate


Control


X


X

This Release Note lists the supported operating systems for each release at a high level. For moredetailed information about the supported versions for each operating system, see the MultimediaConnector for Skype for Business page in the Genesys Supported Operating Environment ReferenceGuide.

Discontinued Support[+] Note about discontinued itemsThis section documents features that are no longer supported in this software. This cumulative list isin release-number order with the most recently discontinued features at the top of the list. For moreinformation on discontinued support for operating environments and databases, see DiscontinuedSupport in the Genesys Supported Operating Environment Reference Guide.

There are no discontinued items for this product.

Known Issues

You can find a cumulative list of the Known Issues and Recommendations for all 8.5.x releases ofGenesys T-Server and UCMA Connector for Skype for Business, including the issues that are specificto Localized (International) releases, at the following links:

• Known Issues and Recommendations• Internationalization Issues

Related Resources

For additional information about Genesys T-Server and UCMA Connector for Skype for Business, seethe following documentation:

• The documentation related to this software is available from the Multimedia Connector for Skype for



https://docs.genesys.com/Documentation:System:SOE:MultimediaConnectorForSkypeForBusiness:Current


https://docs.genesys.com/Documentation/System/latest/SOE/Welcome


https://docs.genesys.com/Documentation/System/latest/SOE/DiscontSupSOE

https://docs.genesys.com/Documentation/System/latest/SOE/DiscontSupSOE


https://docs.genesys.com/Documentation/Skype

Business page.

• The Genesys T-Server and UCMA Connector for Skype for Business Deployment Guide provides detailsabout installing and configuring T-Server and UCMA Connector for Skype for Business.

• The Multimedia Connector for Skype for Business page in the Genesys Supported OperatingEnvironment Reference Guide provides detailed information about product support for operatingsystems.

Release Notes for other Genesys components are available here.



https://docs.genesys.com/Documentation/Skype

https://docs.genesys.com/Documentation/Skype/latest/Dep/Welcome




Known Issues and Recommendations

Genesys T-Server and UCMA Connector for Skype for Business

The Known Issues and Recommendations section is a cumulative list for all 8.5.x releases of GenesysT-Server and UCMA Connector for Skype for Business. This section provides the latest information onknown issues and recommendations associated with this product. It includes information on whenindividual items were found and, if applicable, corrected. The Resolved Issues section for eachrelease describes the corrections and may list additional issues that were corrected without firstbeing documented as Known Issues.

If CPN Digits are used for a B2BUA call to a Response Group that contains Skype for Business usersnot handled by Genesys components, the CPN Digits are displayed in the ringing toast, but the CPNDigits are replaced in the Skype for Business conversation window with the conference service portalname after the call is answered.

ID: LYNC-3484 Found In: 8.5.001.63 Fixed In:

If CPN Digits are used for a B2BUA call to a Response Group that contains DNs handled by Genesyscomponents, the call cannot be answered by a Response Group member agent.


If an agent monitored by a supervisor dials a TEL URI, the supervisor will not be included in the calland will no longer be able to monitor calls on any agent.

ID: LYNC-3308 Found In: 8.5.001.50 Fixed In: 8.5.001.54

If the SIP Server application used for Remote Recording is configured with ANI or DNIS in therecording file name, recording does not start. Here is an example of the problematic recordingfilename template:

recording-filename="$UUID$_$ANI$_$DNIS$_$DATE$_$TIME$_"

Workaround: Configure the application-level option recording-filename without using of ANI orDNIS in the recording file name template. For example:

recording-filename="$UUID$_$DATE$_$TIME$_"


Genesys T-Server and UCMA Connector for Skype for Business 8.5.xRelease Note

Known Issues andRecommendations


If the application-level or DN-level option handle-direct-calls is changed dynamically during a liveWorkspace Desktop Edition (WDE) agent session, WDE receives no notification about the changeddirect-call-processing mode for the DN.

Workaround: Restart Workspace Desktop Edition to receive the correct work mode.


If a customer is on an IM or audio call with a federated agent and the federated agent performs anescalation to audio or to IM, the escalation might fail because of an error on the Skype for BusinessEdge Server.


In a rare race-condition scenario, when remote recording is started and a switchover occurs, T-Servermight lose control of the remote recording.


Currently, a federated agent cannot perform supervision because of a limitation in Skype forBusiness. Only a premise agent can be a supervisor.


During a recording session establishment, if a race condition occurs in which the MTLP event arrivesfrom the Connector before T-Library events arrive from SIP Server, T-Server terminates unexpectedlywhen it receives the next T-Library request related to remote recording.


T-Server might not provide event reporting for the main call when a consultation call is notestablished at the destination.


The default value for options uri-pattern for Remote Treatment and Remote Recording is incorrectlyset tosip:{+1999{DDDDDDD}}@example.net, instead of an empty string.


When the Connector is restarted during an active multimedia call (an IM call escalated to audio/videoor vice versa), the multimedia call is not recovered properly and the participants cannot exchangeinstant messages.





T-Server does not generate EventHeld for a call in the dialing state if it is reported by the Connector.


In agent monitoring scenarios, if a supervisor rejects the previously requested call monitoring, anagent still sees the monitoring icon on the Workspace Desktop Edition.


A supervisor can listen to a participant that is placed on hold.


If T-Server transfers a call from an agent with configured recording to another agent with configuredrecording, T-Server closes the current recording session and does not open a new one. As a result,the second agent will not be recorded.


In supervision scenarios where an observing supervisor executes a single-step transfer, T-Serversends EventPartyDeleted for the observer to the new destination after sending EventEstablished. Theroot cause of the limitation is the lack of a ringing notification from Skype for Business to T-Server.


When an agent makes a 3pcc call to a Skype for Business user, the call might fail if the user has callforwarding configured. This issue applies to direct call forwarding or forwarding on busy.


When the Connector is restarted while video calls are active, the video calls are converted to audiocalls during the recovery procedure.


A sequential escalation by an agent from IM to Audio and then to Video is not possible. The Videoconnection fails because of a Skype for Business issue.

ID: LYNC-2394 Found In:Fixed In: Skype for BusinessCU 6.0.9319.510 (December2017)

T-Server does not process properly the required-link-number option and reportsEventLinkConnected when the first link (Connector) becomes available.

Workaround: Genesys recommends setting the required-link-number option to 1.





If a user executes SingleStepConference from a Skype for Business client in regular (non-suppression)mode to a Routing Point, T-Server incorrectly reports the new leg as a new call.


If a UCMA Connector is configured with the caching-enabled option set to true, the UCMAConnector cannot fully recover from the FrontEnd Pool restart if the conference cache is not empty.After the FrontEnd Pool restarts, new calls that were created in the UCMA Connector might fail.

Workaround: Restart the UCMA Connector after the FrontEnd Pool is restarted to avoid failure ofnew calls.


When an inbound IM call to a supervised agent is escalated to voice and a consequent consultationcall is placed, T-Server misses information about the IM in T-Library messaging.


During an escalation of an IM call to an audio call, rare race conditions no longer occur on the Skypefor Business Server. Previously, such conditions could cause T-Server to confuse call origination anddestination in T-Library messaging for the audio call.


Because of a vendor hardware limitation, a video call from a Skype for Business Client without acamera fails to recognize video from an agent with a camera.


During a T-Server switchover, an unfinished single-step transfer of an escalated IM-to-audio call canlose information about a transfer controller in T-Library messaging.


A supervisor might not be released correctly in the following scenario:

1. A supervisor starts agent monitoring with following configuration: scope = 'agent', type = 'one call',mode = 'mute', and the T-Server option monitor-consult-calls = 'all'.

2. The supervisor joins the conference with a caller and Agent1.3. Agent1 performs a two-step transfer to Agent2 that is not monitored by the supervisor.4. The supervisor remains in the conference after Agent1 completes the transfer and leaves the

conference.





If two people are connected in an IM interaction and then the originator escalates it to voice, theoriginator will be immediately displayed as connected, although the second party has not yetaccepted the voice call and can decline it.


If, during a multimedia conference, an agent leaves the audio/video call, but still remains in the IMcall, this agent cannot be added back to the audio/video call using a TSingleStepConference request.


T-Server now processes inbound calls if Skype for Business Server rejects them with a 500 internalserver error.


T-Server does not support the dialing of Skype for Business users by TEL URI.


T-Server for Skype for Business supports only the configured DN number of Agent DNs and RoutePoints as internal dialing destinations. Agent DNs must correspond to endpoints controlled by thesoftware Skype for Business client. Hard phones are not supported.


In a conference escalation scenario, the EventPartyAdded does not include the ThirdPartyDNRoleattribute. As result, Workspace Desktop does not display the third-party user information correctly.


To avoid sending duplicate IM messages, install Lync client 15.0.4763.1001 or later. Otherwise, youcan ignore these duplicate messages.


If both the primary and backup T-Servers unexpectedly exit at the same time, a call that was intreatment at the time of the exit might not continue correctly after the T-Servers restart.


When a supervisor is engaged in an IM conversation with the agent, for which supervisor monitoringis requested, escalation of the IM to voice might produce unexpected results. Results will differ,




depending on the number of IM participants in the conversation and the party that requested IM tovoice escalation, but generally, incorrect call flows might be reported.

To work around this, the supervisor should cancel monitoring of the next call on the agent if thatagent is established in an IM conversation with a supervisor.


If an agent establishes a call with a supervisor who is already in a monitoring session, the monitoringsession becomes inactive and the supervisor cannot monitor the agent, or initiate new monitoringsessions.


If the backup T-Server starts when the primary T-Server is already running, there is nosynchronization of agent states between the T-Servers potentially causing incorrect agent stateswhen the backup is promoted to primary.


T-Server does not support DND state synchronization between primary and backup T-Server.Previously, after T-Server switchover or failover, the DND state could become desynchronized fromthe Skype for Business presence state. The DND state now synchronizes when the newly appointedprimary T-Server receives the first presence update from Skype for Business.


In HA scenarios, the supervisor might lose control of monitoring the next call.


T-Server now correctly handles subscription information when multiple switchovers and failoversoccur.


Connector rejects TAlternateCall, TCompleteConference, TCompleteTransfer requests as UnsupportedOperation when a consultation call is in alerted state.


If T-Server is configured to publish the agent states to the user presence, the Skype for Business(Microsoft Lync) Server might override the presence information.





T-Server might lose third-party call control if a ringing party is answered and released in quicksuccession. The issue is fixed in Skype for Business Server 2015 February 2017 cumulative update6.0.9319.277. Lync Server 2013 still has the issue.


During a reconnect procedure between T-Server and the Connector, T-Server no longer loses controlof some route points if the subscription fails once.


Internationalization Issues

Information in this section is included for international customers.

There are no internationalization issues for this product.




Release 8.5.0

Genesys T-Server and UCMA Connector for Skype for BusinessRelease Notes

You can find links to Release Notes for particular 8.5.0 releases of Genesys T-Server and UCMAConnector for Skype for Business, if available, in the tree menu on the left or in the list of AvailableReleases.

Genesys T-Server and UCMA Connector for Skype for Business 8.5.x Release Note Release 8.5.0


9.x

Helpful LinksReleases Info

• List of 8.5.x Releases• 8.5.x Known Issues

Product Documentation

Genesys T-Server and UCMAConnector for Skype forBusiness

Genesys Products

List of Release Notes

8.5.001.67

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


ReleaseDate


10/01/18 GeneralUnderShippingControl

X

What's New

This release contains the following new features andenhancements:

• Genesys T-Server and UCMA Connector for Skype for Businessprovides the ability to configure access for telephony users tojoin private meetings through a virtual lobby or directly,bypassing the virtual lobby. A new configuration option—lobby-bypass-enabled—set in the [conference-services] section onthe Annex tab of the Switch object enables or disables thisfunctionality. When configured, the option setting applies to allconnectors that are connected to the current default pool.(LYNC-3577)

Resolved Issues

This release contains no resolved issues.



Upgrade Notes

No special procedure is required to upgrade to release 8.5.001.67.

Dependencies

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



9.x




Genesys T-Server and UCMAConnector for Skype forBusiness

Genesys Products


8.5.001.65



ReleaseDate



X

What's New


• A new configuration option—im-reporting—allows the suppressionof all events relating to IM calls and thus prevents T-Server forSkype for Business from interfering with the eServicesmultimedia chat solution.MORE DETAILS

• Direct Call Handling has been enhanced with the implementationof a new configuration option, handle-direct-calls-media. MOREDETAILS

• Support for Windows Server 2016 and Hyper-V for WindowsServer 2016. See the Multimedia Connector for Skype forBusiness page in the Genesys Supported Operating EnvironmentReference Guide for more detailed information and a list of allsupported operating systems.

Resolved Issues

This release contains the following resolved issues:



https://docs.genesys.com/Documentation/Skype/latest/Dep/IMSuppression

https://docs.genesys.com/Documentation/Skype/latest/Dep/DirectCalls


https://docs.genesys.com/Documentation/System/latest/SOE/MultimediaConnectorForSkypeForBusiness

https://docs.genesys.com/Documentation/System/latest/SOE/MultimediaConnectorForSkypeForBusiness



T-Server now reactivates the default routing feature, if configured, when an error response is receivedfrom the Connector while either the option sip-treatments-continuous is set to false or there isno remote treatment in progress. Previously, T-Server did not reactivate such a configured defaultrouting timer when a routing failure had occurred and default routing was not performed after theconfigured timer expired without T-Server receiving RequestRouteCall. (LYNC-3527)

T-Server now prevents the distribution of EventAddressInfo for devices when either the Annex tabconfiguration values or the global option handle-direct-calls have been changed, if such changesdo not result in modification of the relevant extension keys. Previously, T-Server generatedEventAddressInfo for all devices of type Extension regardless of whether any related extension keyschanged. (LYNC-3227)

A sequential escalation by an Agent from IM to audio and then to video is now possible. Previously,the video connection failed due to a Skype for Business issue. (LYNC-2394)

Upgrade Notes


Dependencies




9.x




Multimedia Connector for Skypefor Business

Genesys Products


8.5.001.63



ReleaseDate



X

What's New


• T-Server for Skype for Business can now dial a new destinationusing the Back-to-Back User Agent (B2BUA) method, where callswitching and control is performed by Genesys. This featureallows the provisioning of a configured Caller ID and the correctreporting of the origination party of ISCC calls. It further permitscalls to be made to TEL URI destinations, Response Groups, anddestinations with forwarded calls, none of which can be dialeddirectly by T-Server. See Calling using Back-to-Back User Agentfor details. (LYNC-3076, LYNC-987)

• T-Server for Skype for Business supports ISCC connections withSIP Server and other T-Servers, but does not support ISCCconnections with other instances of T-Server for Skype forBusiness.

Resolved Issues




https://docs.genesys.com/Documentation/Skype/8.5.0/Dep/CallB2BUA

T-Server can now start when the value of the rq-expire-tout option is set to 0 (zero) and a treatmentor recording is configured. Previously, such settings sometimes put T-Server into an endless loop.(LYNC-3387)

When an agent makes a 3pcc call to a Skype for Business user, the call no longer fails if the user hascall forwarding configured. This issue applied to direct call forwarding or forwarding on busy.(LYNC-2524)

T-Server now supports the dialing of Skype for Business users by TEL URI. (LYNC-1682)

Upgrade Notes


Dependencies




9.x





Genesys Products


8.5.001.54



ReleaseDate


11/09/17 Hot Fix X

What's New

This release includes only resolved issues.

Resolved Issues


Previously, when a call undergoing remote treatment was routedto an agent, T-Server reported EventRinging for the agent, startedto disconnect treatments and then started to connect the agentafter the end of the treatment. If treatment disconnection tooklong, it caused a long delay on Workspace Desktop Edition (WDE)between EventRinging and the incoming Skype for Business call. Now when such a call is routed, T-Server immediately disconnects the treatment, reports EventRinging, and connects the agent onlyafter the treatment is disconnected. (LYNC-3348)

If the handle-direct-calls option is set to on-login and an agent logs in on a device that is in DoNot Disturb On state, the device will now be set to Do Not Disturb Off state after the agent logs in. T-Server will continue to monitor any presence state changes that occur while the agent is logged in,and will set the agent's device into the appropriate Do Not Disturb state when the agent logs out.



Previously, T-Server did not perform these actions, which resulted in the agent device being stuck inDND On state after the agent logged in. (LYNC-3347)

Previously, in case of a race condition, a dial-out request destination DN could join into the call afterthe failure of the request. Now the request destination DN is restricted from joining for 10 secondsafter the failure of the request. A new request to the same destination will be performed withoutrestrictions. (LYNC-3313)

Previously, when an agent called a Tel URI, a failed supervision session was created and thesupervisor could no longer monitor agents. Now, if an agent monitored by a supervisor dials a Tel URI,the supervisor will not be included in the call. (LYNC-3308)

Previously, if a call to Skype for Business was made from numbers with a leading + character(+NNNNN), the ANI of such calls was reported as sip:[email protected] and it was impossible tocall back using this ANI. Now T-Server reports the ANI of such calls as +NNNNN, and the agent is ableto call back the customer. (LYNC-3285)

Previously, when the Connector was uninstalled, its configuration file was deleted. The installationprocedure also did not check for an existing connector.config file and overwrote it with defaultcontents. Now the installation procedure checks for the presence of this file and asks whether itshould be overwritten. Uninstallation does not remove this file. (LYNC-2424)

Upgrade Notes


Dependencies




9.x





Genesys Products


8.5.001.50



ReleaseDate


10/12/17 Hot Fix X

What's New


• T-Server now generates new alarms for connection ordisconnection to configured connectors. These alarms can beconfigured for interception and an action can be applied inSolution Control Interface. The following alarms are nowavailable:• GCTI_MSLYNC_CONN_DISCONNECTED

ID: 35198Level: STANDARDText: Link %d to [%s]:%d is disconnected; %d connectors remain connectedDescription: This alarm is generated by T-Server when connection to aconnector is lost.

T-Server generates a message with ID=35198 and context "Link {linkId} to[{hostname}]:{port} is disconnected; {number_of_connected_links}]connectors remain connected".

• GCTI_MSLYNC_CONN_CONNECTEDID: 35199 <br Level: STANDARD<br Text: Link %d to [%s]:%d is opened; %dconnectors are now connected<br Description: This alarm is generated byTServer when connection to connector is opened.

T-Server generates a message with ID=35199 and context "Link {linkId} to [{hostname}]:{port} is opened;{number_of_connected_links}] connectors are now connected".

(LYNC-3300)

• Connector is now able to print the version of the loaded Microsoft Collaboration DLL in its log file. In addition, Connector is able toprovide information regarding the Microsoft DLL that will be loaded when the mslync_connector -V command is issued.(LYNC-3269)



Resolved Issues


Previously, using a ringtone sound file or a music-on-hold sound file caused a memory leak in UCMA.Now this UCMA memory leak is fixed and using a ringtone file or a music-on-hold file no longercauses memory leaks. (LYNC-3299)

T-Server now has a mechanism to clear any stuck calls or sessions on a DN.

A new DN level option force-call-cleanup is available and can be configured in the T-Server sectionof the Annex tab of a DN. The valid values are true and false. The default value is false.

If this option is set to true and the DN is disabled in the Configuration Database, T-Server will cleanup any calls on the DN, and all of the calls on the DN will be dropped.

After the cleanup process has been completed and all calls on the DN are dropped, Genesysrecommends that you remove the option from the DN Annex tab or set it to false. (LYNC-3289)

Now T-Server no longer applies ACW for IM calls and does not take active IM calls into account indetermining when ACW starts; if an AV call is released during active IM calls, ACW will be applied(LYNC-3277)

Previously, if a participant asked to join a call, for example, using RequestRouteCall,RequestMakeCall, or a similar request, but was not connected for some reason, the call became stuckwaiting for the new participant. Now, the im-joining-timeout and av-joining-timeout options areused for this case, as follows:

• For IM calls—If the destination of the request is answered but not joined during the time intervalspecified by im-joining-timeout, the request will be failed.

• For AV calls—If the destination of the request is answered but not joined during the time intervalspecified by av-joining-timeout, the request will be failed.

In both of these cases, the call is established, but is disconnected when the timer expires.

(LYNC-3265)



Upgrade Notes


Dependencies




9.x





Genesys Products


8.5.001.49



ReleaseDate



X

What's New

Note: This version was first released as a Hot Fix on 09/22/17.


• T-Server for Skype for Business now supports user endpointsregistered on a Survivable Branch Appliance (SBA) or aSurvivable Branch Server (SBS) front-end server. When the SBAor SBS is disconnected from the main Skype for Business server,T-Server cannot control calls on such users until connection isrestored. (LYNC-3078)

• T-Server now supports Secure Real-time Transport Protocol (SRTP)traffic between Genesys Media Server (used for treatments andrecording) and Skype for Business Mediation Server. For this,secure connections must be configured between T-Server and SIPServer, and SIP Server and GVP. The contact option in the SIPServer Trunk DNs must make use of SRV records for theMediation Server pool as described here: Configuring SIP Serverand DNs. The PSTN Gateway to SIP Server must be configured on Skype for Business with the entireFQDN of SIP Server to insure correct certificate exchange. (LYNC-3077)



https://docs.genesys.com/Documentation/Skype/8.5.0/Dep/RemoteRecording

https://docs.genesys.com/Documentation/Skype/8.5.0/Dep/RemoteRecording

Resolved Issues


T-Server now correctly processes scenarios in which a call is disconnected from the origination devicewhile a call treatment is playing. Previously, T-Server deleted internal structures on the release of thecall and incorrectly updated other calls with User Data updates sent by SIP Server for the deleted call.(LYNC-3251)

Upgrade Notes


Dependencies




9.x





Genesys Products


8.5.001.47



ReleaseDate


09/18/17 Hot Fix X

What's New


Resolved Issues


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

During a single-step transfer, when the transfer destination starts ringing, the transfer originatoragent is disconnected from the audio routes and the customer and the agent no longer can hear eachother. In addition, in a two-way call, a ringtone (if configured) is connected to the call to play to thecustomer. Previously, during a single-step transfer performed by an agent, the customer and theagent 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 SIPServer option recording-filename, recording does not start. To resolve this, a new Skype forBusiness T-Server option recording-filename has been introduced in the [remote-recording]section.

recording-filenameDefault Value: An empty stringValid Values: Any valid file name using the variables specified in the descriptionChanges Take Effect: For the next recording session

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

Predefined values can be specified in the pattern definition. The following substrings will be replacedwith 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 liveWorkspace Desktop Edition (WDE) agent session, WDE now correctly receives notification about thechanged direct-call-processing mode for the DN. (LYNC-3144)

Upgrade Notes




Dependencies




9.x





Genesys Products


8.5.001.44


This is the first 9.x release of Genesys T-Server and UCMAConnector for Skype for Business.

ReleaseDate



X

What's New


• Support for Skype for Business federated users where Genesys T-Server and the UCMA Connectors for Skype for Business arehosted in the premise environment, but agents are partially orfully hosted in the Office 365 cloud. See Federation Platform withMicrosoft Office 365 Cloud in the Multimedia Connector for Skypefor Business Deployment Guide for details. This support requiresWorkspace Desktop Edition version 8.5.119.05 or later.(LYNC-2676)

Resolved Issues


If a Routing Point is deleted from Skype for Business and reported as out of service (OOS), and a callis delivered to that Routing Point, T-Server now generates ErrorCode (93) "Destination Invalid State".



https://docs.genesys.com/Documentation/Skype/latest/Dep/Federation

https://docs.genesys.com/Documentation/Skype/latest/Dep/Federation

Previously, an attempt to deliver a call failed only on the Connector and Skype for Business sidebecause of an unknown destination. (LYNC-3131)

Previously, if one of the call participants escalated a multimedia (audio/video) call to an IM call butother participants declined or ignored the joining invitation, the originator of the escalation remainedin Dialing state on a new IM call forever.

Now, the new application-level option im-joining-timeout can be used for this scenario:

im-joining-timeoutSection: [TServer]Default Value: 30Valid Values: Integer in the range 5-600Changes Take Effect: Immediately

Specifies the time interval, in seconds, that the Connector waits for a participant in a multimedia callto join an Instant Messaging conference before considering the party for that participant released.(LYNC-3015)

T-Server now provides event reporting for the main call when a consultation call is not established atthe destination. Previously, event reporting for the main call was postponed until a consultation callwas established. (LYNC-2939)

Previously, if a multimedia call was transferred to a destination that does not support IM, the IM callwas stuck in dialing state. Now, the new application-level option im-joining-timeout can be used forthis scenario. (LYNC-2788)

Previously, if a call participant attempted to escalate an IM call to an audio/video call, but the otherparticipants declined the invitation, the originator of the escalation remained in dialing state on thenew audio call indefinitely.

Now, the new application-level option av-joining-timeout can be used for this scenario:

av-joining-timeoutSection: [TServer]Default Value: 30Valid Values: Integer in the range 5-600Changes Take Effect: Immediately

Specifies the time interval, in seconds, that the Connector waits for a participant in a multimedia callto join the audio/video conference before considering the party for that participant released.(LYNC-2457)



Upgrade Notes


Dependencies








Genesys Products


8.5.001.41


ReleaseDate


07/28/17 Hot Fix X

What's New


Resolved Issues


T-Server now attempts to connect to the backup SIP Serverrunning in primary mode if the former primary SIP Server is down.Previously, if the primary SIP Server was down and the SIP Serverswitchover occurred, T-Server attempted to reconnect to theformer primary SIP Server instead of the new primary SIP Server.(LYNC-3035)

Upgrade Notes




Dependencies








Genesys Products


8.5.001.37


ReleaseDate



X

What's New


Resolved Issues


The Connector no longer disconnects established calls if T-Serverdisconnects and is not reconnected before the timeout specifiedin the graceful-period-timeout option expires. Previously, theConnector disconnected calls after this timeout expired.(LYNC-3004)

Upgrade Notes




Dependencies








Genesys Products


8.5.001.36


ReleaseDate


06/01/17 Hot Fix X

What's New

This release includes the following resolved issues.

• Connector has been modified to take advantage of the resolvedMicrosoft issue (16110914914988). Now it is possible to cancelthe dial-out operation to an internal or an external destination.Cancelling dial-out will stop alerting on a destination endpoint.Notes:• Skype for Business CU 6.0.9319.281 or later must be installed.

There are no appropriate updates for Microsoft Lync.• For internal calls, the feature works as described for Skype for

Busines and Lync environments. Call alerting on an externaldestination in the Microsoft Lync environment will continueafter dial-out is cancelled. No calls remain in T-Server afterdial-out has been cancelled; however, the externaldestination should reject (or answer and release) the call tostop the alerting signal. (LYNC-2921)

Resolved Issues


T-Server now correctly handles remote recording after a switchover. Previously, in a rare race-condition scenario, when remote recording was started and a switchover occurred, T-Server lostcontrol of the remote recording. (LYNC-3005)



During a recording session establishment, if a race condition occurs in which the MTLP event arrivesfrom the Connector before T-Library events arrive from SIP Server, T-Server no longer terminatesunexpectedly when it receives the next T-Library request related to remote recording. (LYNC-2966)

The default value for options uri-pattern for Remote Treatment and Remote Recording is now setcorrectly to an empty string. Previously, the default value was set tosip:{+1999{DDDDDDD}}@example.net. (LYNC-2882)

T-Server now properly generates EventHeld for a call in the dialing state if it is reported by theConnector. Previously,T-Server did not generate EventHeld in this scenario. (LYNC-2847)

A supervisor can no longer listen to a participant that is placed on hold. (LYNC-2795)

Upgrade Notes


Dependencies








Genesys Products


8.5.001.32


ReleaseDate



X

What's New


• Support for pass-through calls. See Handling Pass-Through Calls inthe Multimedia Connector for Skype for Business DeploymentGuide for details. (LYNC-2707)

Resolved Issues


T-Server now properly reports an observer party as abandoned when the observer rejects an offeredmonitoring session. Previously, in agent monitoring scenarios, if a supervisor rejected the previouslyrequested call monitoring, the monitoring icon was still displayed on the Workspace Desktop.(LYNC-2841)



https://docs.genesys.com/Documentation/Skype/latest/Dep/ConfRelease

Upgrade Notes


Dependencies








Genesys Products


8.5.001.29


ReleaseDate



X

What's New


• T-Server can now record a call without recording a music-on-holdtreatment when a call is placed on hold. See Remote Recording inthe Multimedia Connector for Skype for Business DeploymentGuide for details. This feature requires SIP Server version8.1.102.55 or later. (LYNC-2624)

• T-Server now supports a configuration in which both the Skype forBusiness client and Workspace Desktop are used alternately onthe same desktop. (LYNC-2315)

• T-Server now supports a deployment with a single application andpaired user Front End pools. See Paired Front End Pools in theMultimedia Connector for Skype for Business Deployment Guidefor details. (LYNC-2085)

• T-Server now supports Workspace Plugin in regular (non-suppression) mode. See Handling Direct Calls in the MultimediaConnector for Skype for Business Deployment Guide for details.

Resolved Issues


If T-Server transfers a call from an agent with configured recording to another agent with configured



https://docs.genesys.com/Documentation/Skype/latest/Dep/RemoteRecording

https://docs.genesys.com/Documentation/Skype/latest/Dep/PairedPools


recording, T-Server closes the current recording session and does not open a new one. As a result,the second agent will not be recorded. (LYNC-2686)

If, during a multimedia conference, an agent leaves the audio/video call, but still remains in the IMcall, this agent cannot be added back to the audio/video call using a TSingleStepConference request(LYNC-1727)

T-Server might lose third-party call control if a ringing party is answered and released in quicksuccession. The issue is fixed in Skype for Business Server 2015 February 2017 cumulative update6.0.9319.277. Lync Server 2013 still has the issue. (LYNC-667)

Upgrade Notes


Dependencies








Genesys Products


8.5.001.24


ReleaseDate


03/14/17 Hot Fix X

What's New


Resolved Issues


T-Server now handles 1pcc hold and 1pcc retrieve operationscorrectly during consultation calls. Previously, in the case of 1pcchold call during a consultation call and 1pcc retrieve, the callingparty was able to hear the agent that used 1pcc operations.(LYNC-2717)

Upgrade Notes




Dependencies








Genesys Products


8.5.001.23


ReleaseDate



X

What's New


• T-Server provides the ability to configure how direct internal orinbound calls are handled. See Handling Direct Calls in theMultimedia Connector for Skype for Business Deployment Guidefor details. (LYNC-2569, LYNC-2023)

Resolved Issues


Upgrade Notes




https://docs.genesys.com/Documentation/Skype/8.5.0/Dep/DirectCalls

Dependencies








Genesys Products


8.5.001.20


ReleaseDate


02/03/17 Hot Fix X

What's New


Resolved Issues


When T-Server receives EventAttachedDataChanged from SIPServer during remote treatments, it now correctly attaches UserData to the call. Previously, T-Server did not attach that User Datato the call. (LYNC-2640)

A calling party can no longer hear a ringtone and an audible treatment when a call is routed to anagent. Now, only one audio source is connected to the calling party. The following T-Serverconfiguration option sip-treatments-continuous is introduced:

sip-treatments-continuousSetting: TServer section, Application levelDefault Value: falseValid Values: true, falseChanges Take Effect: Immediately for all new calls

Enables or disables a routing strategy treatment to be continuously played until the routingdestination has answered the call:

• true: A routing strategy treatment is played continuously until the routing destination has answered thecall.



• false: As soon as routing is requested, a ringtone is played until the routing destination has answeredthe call.

(LYNC-2632)

Upgrade Notes


Dependencies








Genesys Products


8.5.001.18


ReleaseDate


01/20/17 Hot Fix X

What's New


Resolved Issues


Connector now properly processes hold scenarios. Previously,Connector added back a held participant to an audio conversationin 30 seconds; the returned participant was able to listen and talkin active conversation while being on hold. (LYNC-2626)

Upgrade Notes




Dependencies








Genesys Products


8.5.001.17


ReleaseDate



X

What's New


• Support for audio recording of Skype for Business calls. SeeRemote Recording in the Multimedia Connector for Skype forBusiness Deployment Guide for details. This support requires SIPServer version 8.1.102.55 or later. (LYNC-2333)

Resolved Issues


Upgrade Notes




https://docs.genesys.com/Documentation/Skype/latest/Dep/RemoteRecording

Dependencies

• This release requires SIP Server version 8.1.102.55 or later.• 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 tothe Common Part that may affect the functionality of your particular type of T-Server.







Genesys Products


8.5.001.14


ReleaseDate


12/08/16 Hot Fix X

What's New


• T-Server now unregisters devices on the Connector, andconsequently on Skype for Business Server, when a DN is deletedor disabled in the Configuration Layer.T-Server immediately reports EventDNOutOfService for thatdevice and sends an unregistration request to the Connectorwhen the device becomes idle. Previously, T-Server did notunsubscribe deleted or disabled devices from the Connector.

To simplify troubleshooting, T-Server now alsoprovides an extension key cause inEventDNOutOfService. The new extension keyspecifies the cause in text form. For example,the cause "dn disabled in CME" means that theevent is generated as a result of a disableddevice in the Configuration Layer. The cause"terminated" means that the Connector receives a notification from Skype forBusiness Server about the disabling of a user account.

There is no predetermined list of possible causes. (LYNC-2503)



Resolved Issues


Upgrade Notes


Dependencies








Genesys Products


8.5.001.12


ReleaseDate


11/23/16 Hot Fix X

What's New


Resolved Issues


The Connector now correctly attempts to restore services and callcontrol when one of the Front End servers in the Microsoft Lync/Skype for Business environment is stopped and restarted.Previously in this scenario, the Connector sometimes failed ifthere were established calls present, and/or loose control over theexisting calls.

Limitations:

• The Connector will work properly in scenarios involving stopping and starting one of the Front Endservers only if the restart of the previously stopped Front End server is performed after synchronizationof the Microsoft Lync/Skype for Business servers is completed (approximately after 5 minutes). Thebehavior of the Connector might be unpredictable if the Front End server restart is performed in alesser time.

• The Connector might report the release of the calls or parties in scenarios involving starting andstopping one of the Front End servers if a User Endpoint, participating in the call, has been served bythe stopped Front End server. Reporting is based on reporting from Microsoft Lync/Skype for Business.

• The Connector will reject call-related requests for the calls for which conference and serving portals arenot available.



• When using Skype for Business, if the Invoke-CsComputerFailOver command is issued while theConnector is running and configured to use the conference scheduling feature, it can take 20 minutesor longer for the failover to successfully complete.

(LYNC-2447)

Upgrade Notes


Dependencies








Genesys Products


8.5.001.11


ReleaseDate


11/17/16 Hot Fix X

What's New


Resolved Issues


A T-Server switchover in a multi-connector environment no longercauses duplicate windows to appear in Workspace DesktopEdition (WDE) if a call is released immediately after a switchover.Previously, a T-Server switchover sometimes caused creation ofduplicate windows in WDE.

The Connector supports the following new configuration option:

conf-session-shutdownSetting: connector sectionDefault Value: falseValid Values: true, falseChanges Take Effect: Immediately

If set to true, the Connector monitors the Conference Session state and will end the call if aConference Session of this call goes to the Disconnected state. If set to false, the Connector doesnothing in this situation.

(LYNC-2429)



Upgrade Notes


Dependencies








Genesys Products


8.5.001.10


ReleaseDate


11/10/16 Hot Fix X

What's New


Resolved Issues


T-Server can now add a supervisor to a call even if Skype forBusiness Server skips sending provisional responses duringscenario execution. (LYNC-2420)

Upgrade Notes


Dependencies

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







Genesys Products


8.5.001.09


ReleaseDate


11/03/16 Hot Fix X

What's New


• In routing scenarios involving no-answer supervision, T-Servernow instructs the Connector to modify a value of the no-answer-timeout option on a routing destination if the destination is amonitored Lync/Skype for Business user. After that, T-Serverinstructs the Connector to reset that value at the end of theexecution of the routing scenario.

The Connector now supports the following newconfiguration option:

default-agent-no-answer-time

Setting: connector section

Default Value: 20

Valid Values: Integer greater than 0

Changes Take Effect: Immediately

Specifies the default no-answer timeout for the monitored agent that T-Server sets for the Lync/Skype for Business user after a routing scenariocompletion that involves no-answer supervision.(LYNC-2367)



Resolved Issues


A supervised call no longer becomes stuck in the Connector if a supervisor does not connect to thecall because of a missing notification from UCMA. (LYNC-2420)

T-Server now rejects a TMakeCall request to a Virtual Routing Point with EventError (Invaliddestination). Previously, T-Server terminated unexpectedly after receiving TMakeCall from a DN to aVirtual Routing Point. (LYNC-2402)

Upgrade Notes


Dependencies








Genesys Products


8.5.001.07


ReleaseDate


10/26/16 Hot Fix X

What's New


• The maximum value for the no-answer-timeout option hasincreased from 20 sec to 600 sec. (LYNC-2380)

Resolved Issues


T-Server/Connector now correctly plays a ringback tone to a callerwhen the call is placed to an agent in the following scenarios:

• routing to an agent• initiating a direct call to an agent (1pcc and 3pcc)• consultation call to an agent

Use the new Connector configuration option ringtone-file-path to specify the audio file path.

ringtone-file-pathSetting: connector sectionDefault Value: No default valueValid Values: A stringChanges Take Effect: Immediately



Specifies the path (full path, relative path or network path are supported) to the audio file that isplayed as a ringback tone to a caller while a call is alerting the receiving party. T-Server/Connectorsupports the audio file .wma type. (LYNC-2396)

T-Server/Connector now properly restores calls in an environment with two or more Connectors whena link to one of the Connectors is disconnected. Previously in this scenario, T-Server sometimes:

• restored calls only when the Connector with the calls was disconnected and reconnected later;• incorrectly restored calls, so escalation to another media for those calls did not work;• did not restore calls properly when the Connector with the restored calls was disconnected again.

Note: The voice path in some restored calls might be temporarily unavailable or of a bad quality.(LYNC-2354)

T-Server running in Backup mode now correctly reports the link availability state depending on theavailability of connections to Connectors. Previously, T-Server running in Backup mode incorrectlyreported EventLinkConnected in the following scenarios:

• when the HA role has been changed to Primary and no links to Connectors were available• when the synchronization update from the Primary T-Server reported EventLinkConnected, while the

Backup T-Server did not have any available links to Connector(s).

(LYNC-2368)

T-Server now correctly reports the required AttributeExtensions in EventTreatmentEnd if the eventwas generated as a result of remote treatment execution. Previously, T-Server did not propagate therequired extension with key USER_ANN_ID, if it was present in events received from the remotetreatment server.

T-Server now correctly reports empty AttributeCollectedDigits in EventTreatmentEnd if no informationwas available from the remote treatment server. Previously, T-Server did not report emptyAttributeCollectedDigits in this scenario. (LYNC-2362)

In a configuration with multiple Connectors, when a new Connector starts, T-Server does not performthe resubscription of a User Endpoint to the newly available Connector until the Endpoint no longerhas active calls. Previously, T-Server performed resubscription immediately after the Connectorstarted, which sometimes broke normal call control operations. (LYNC-2353)

T-Server now correctly processes the required-link-number option and reports EventLinkConnectedaccordingly. (LYNC-2385)



Upgrade Notes


Dependencies








Genesys Products


8.5.001.02


ReleaseDate



X

What's New


Resolved Issues


When an inbound IM call to a supervised agent is escalated tovoice and a consequent consultation call is placed, T-Server nowcorrectly includes the IM information in T-Library messaging.(LYNC-2087)

Beginning with version 15.0.4763.1001, Lync client no longer sends duplicate IM messages.(LYNC-1410)



Upgrade Notes


Dependencies








Genesys Products


8.5.000.94


ReleaseDate



X

What's New


Resolved Issues


When the connector is running where the option caching-enabled option is set to true and the conference cache is notempty, the connector now fully recovers from a FrontEnd Poolrestart. After a restart, new calls created in the connector nolonger fail. (LYNC-2131)

T-Server now correctly releases the supervisor in the followingscenario:

1. A supervisor starts agent monitoring with the following configuration: scope = 'agent', type = 'one call',mode = 'mute', and the T-Server option monitor-consult-calls = 'all'.

2. The supervisor joins the conference with a caller and Agent1.3. Agent1 performs a two-step transfer to Agent2 that is not monitored by the supervisor.4. The supervisor no longer remains in the conference after Agent1 completes the transfer and leaves the

conference.

(LYNC-1758)

If two people are connected in an IM interaction and then the originator escalates it to voice, the



originator is no longer immediately displayed as connected when the second party has not yetaccepted the voice call and can decline it. (LYNC-1739)

When the primary and backup T-Servers unexpectedly exit at the same time, a call that was in atreatment at the time of the exit now continues correctly after the servers restart. (LYNC-1405)

When a supervisor is engaged in an IM conversation with the agent, whose voice calls he monitors,IM-to-voice escalation no longer reports incorrect call flows. (LYNC-1403)

When a supervisor is busy, a monitoring session no longer starts. Previously, if a monitored agentreceived a call while the supervisor was busy, T-Server tried to start a monitoring session, whichfailed with an error, made the monitoring session inactive, and prevented the supervisor frommonitoring the agent or initiating new monitoring sessions. (LYNC-1388)

If the backup T-Server starts when the primary T-Server is already running, agent states are nowsynchronized between the T-Servers. (LYNC-1202)

T-Server does not support DND state synchronization between primary and backup T-Server.Previously, after T-Server switchover or failover, the DND state could become desynchronized fromthe Skype for Business presence state. The DND state now synchronizes when the newly appointedprimary T-Server receives the first presence update from Skype for Business. (LYNC-1108)

T-Server now correctly handles subscription information when multiple switchovers and failoversoccur. (LYNC-1013)

During a reconnect procedure between T-Server and the Connector, T-Server no longer loses controlof some route points if the subscription fails once. (LYNC-588)

Upgrade Notes


Dependencies

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







Genesys Products


8.5.000.87


ReleaseDate



X

What's New


• The Multimedia Connector for Skype for Business now supportscontact centers of up to 1000 agents, by enabling conferencepooling and Audio/Video call reuse. See the new Performancetopic in the Deployment Guide.

Resolved Issues


T-Server now processes inbound calls if Skype for Business Serverrejects them with a 500 internal server error. (LYNC-1699)

Upgrade Notes




https://docs.genesys.com/Documentation/Skype/latest/Dep/Perf

Dependencies








Genesys Products


8.5.000.69


ReleaseDate



X

What's New


• Support for Skype for Business Server, which is the new version ofMicrosoft Lync Server.

• Support for video calls from customers.• Support for escalation from other media to video. For example, an

interaction can start as an IM session that then gets escalated tovoice, and then gets escalated to video. Or, what starts as avoice session can get escalated to video.

Resolved Issues


In a conference escalation scenario, the EventPartyAdded now includes the ThirdPartyDNRoleattribute. (LYNC-1425)



Upgrade Notes


Dependencies

This release of T-Server is built with T-Server Common Part (TSCP) release number 8.1.010.68. TSCPis the shared software that all T-Servers and SIP Servers use. Consult the TSCP release notes forinformation about changes to the Common Part that might affect the functionality of T-Server/SIPServer.






Skype for Business

Genesys Products


8.5.000.51


ReleaseDate


07/31/15 GeneralUndershippingcontrol

X

What's New


• Support for Windows 2012 64-bit native operating system. Seethe Supported Operating Environment: Multimedia Connector forSkype for Business.

• Support for Inter-Server call control communication with SIPServer.

• Support for Outbound Campaigns.• Support for remote treatments.• Support for presence propagation.• Support for media escalations.• Support for voice and instant messaging.• Support for Microsoft Lync 2013.

Resolved Issues




Upgrade Notes


Dependencies

This release of T-Server is built with T-Server Common Part (TSCP) release number 8.1.010.64. TSCPis the shared software that all T-Servers and SIP Servers use. Consult the TSCP release note forinformation about changes to the Common Part that might affect the functionality of T-Server/SIPServer.



Documents

Genesys T-Server and UCMA Connector for Skype for Business