Release Note

SIP Server

8.1.x

Genesys Telecommunications Laboratories, Inc. © 2011–2019

Contents

Introduction

Release Number AIX Linux Solaris Windows
8.1.103.59 [08/12/19] – Update   X   X
8.1.103.58 [08/02/19] – Update   X   X
8.1.103.56 [07/16/19] – Update   X   X
8.1.103.54 [07/09/19] – Update   X   X
8.1.103.53 [07/02/19] – Hot Fix   X   X
8.1.103.52 [06/25/19] – Update   X   X
8.1.103.48 [06/04/19] – Update   X   X
8.1.103.46 [05/17/19] – Update   X   X
8.1.103.45 [05/09/19] – Update   X   X
8.1.103.43 [04/16/19] – Update   X   X
8.1.103.41 [04/09/19] – Update   X   X
8.1.103.40 [03/22/19] – Update   X   X
8.1.103.38 [03/05/19] – Update   X   X
8.1.103.37 [03/05/19] – General X X X X
8.1.103.35 [02/05/19] – Update   X   X
8.1.103.32 [01/22/19] – Update Unavailable   X   X
8.1.103.29 [12/13/18] – Update Unavailable X X X X
8.1.103.28 [11/20/18] – Update   X   X
8.1.103.26 [11/13/18] – Update   X   X
8.1.103.25 [11/06/18] – Update   X   X
8.1.103.24 [10/30/18] – Update   X   X
8.1.103.23 [10/16/18] – Update   X   X
8.1.103.21 [10/02/18] – Update   X   X
8.1.103.20 [09/18/18] – Update   X   X
8.1.103.18 [09/07/18] – Update   X   X
8.1.103.17 [08/17/18] – Update   X   X
8.1.103.16 [08/14/18] – Update   X   X
8.1.103.15 [07/31/18] – Update   X   X
8.1.103.14 [07/17/18] – Update   X   X
8.1.103.13 [07/10/18] – Update   X   X
8.1.103.12 [06/29/18] – Update   X   X
8.1.103.11 [06/22/18] – Update   X   X
8.1.103.10 [05/25/18] – Update   X   X
8.1.103.08 [05/15/18] – Update   X   X
8.1.103.07 [05/08/18] – Update   X   X
8.1.103.06 [04/27/18] – General X X X X
8.1.103.04 [04/10/18] – Update   X   X
8.1.103.03 [03/19/18] – Update   X   X
8.1.103.02 [03/13/18] – Update   X   X
8.1.103.01 [03/05/18] – Update   X   X
8.1.103.00 [02/21/18] – Update   X   X
8.1.102.99 [02/06/18] – Update   X   X
8.1.102.98 [01/23/18] – Hot Fix   X   X
8.1.102.96 [12/20/17] – Hot Fix   X   X
8.1.102.95 [12/13/17] – Hot Fix X X X X
8.1.102.94 [12/01/17] – Hot Fix   X   X
8.1.102.93 [11/14/17] – Hot Fix   X   X
8.1.102.92 [11/07/17] – Hot Fix   X   X
8.1.102.90 [10/24/17] – Hot Fix   X   X
8.1.102.89 [10/06/17] – Hot Fix   X   X
8.1.102.88 [09/26/17] – Hot Fix   X   X
8.1.102.86 [09/19/17] – Hot Fix   X   X
8.1.102.85 [09/12/17] – Hot Fix   X   X
8.1.102.84 [09/06/17] – Hot Fix   X   X
8.1.102.83 [08/22/17] – Hot Fix   X   X
8.1.102.81 [08/15/17] – Hot Fix   X   X
8.1.102.80 [08/04/17] – Hot Fix   X   X
8.1.102.79 [08/01/17] – Hot Fix   X   X
8.1.102.78 [07/25/17] – Hot Fix   X   X
8.1.102.77 [07/14/17] – Hot Fix   X   X
8.1.102.73 [06/21/17] – General X X X X
8.1.102.72 [06/12/17] – Hot Fix   X   X
8.1.102.71 [06/06/17] – Hot Fix   X   X
8.1.102.70 [05/30/17] – Hot Fix   X   X
8.1.102.69 [05/23/17] – Hot Fix   X   X
8.1.102.68 [05/16/17] – Hot Fix   X   X
8.1.102.67 [05/05/17] – Hot Fix   X   X
8.1.102.65 [04/28/17] – Hot Fix   X   X
8.1.102.64 [04/25/17] – Hot Fix   X   X
8.1.102.62 [04/18/17] – Hot Fix   X   X
8.1.102.61 [04/11/17] – Hot Fix   X   X
8.1.102.60 [03/24/17] – Hot Fix   X   X
8.1.102.59 [03/07/17] – Hot Fix   X   X
8.1.102.58 [02/21/17] – Hot Fix   X   X
8.1.102.57 [02/07/17] – Hot Fix   X   X
8.1.102.56 [01/24/17] – Hot Fix   X   X
8.1.102.55 [12/28/16] – Hot Fix   X   X
8.1.102.54 [12/16/16] – General X X X X
8.1.102.53 [12/02/16] – Hot Fix   X   X
8.1.102.52 [11/18/16] – Hot Fix   X   X
8.1.102.51 [11/15/16] – Hot Fix   X   X
8.1.102.50 [11/09/16] – Hot Fix   X   X
8.1.102.49 [10/31/16] – Hot Fix   X   X
8.1.102.46 [10/14/16] – Hot Fix   X   X
8.1.102.45 [10/11/16] – Hot Fix   X   X
8.1.102.43 [09/27/16] – Hot Fix   X   X
8.1.102.42 [09/20/16] – Hot Fix   X   X
8.1.102.41 [09/14/16] – Hot Fix   X   X
8.1.102.40 [09/06/16] – Hot Fix   X   X
8.1.102.39 [08/29/16] – Hot Fix   X   X
8.1.102.38 [08/23/16] – Hot Fix   X   X
8.1.102.36 [08/12/16] – Hot Fix   X   X
8.1.102.35 [08/08/16] – Hot Fix   X   X
8.1.102.34 [08/02/16] – Hot Fix   X   X
8.1.102.33 [07/26/16] – Hot Fix   X   X
8.1.102.32 [07/19/16] – Hot Fix   X   X
8.1.102.31 [07/08/16] – Hot Fix   X   X
8.1.102.29 [06/28/16] – Hot Fix   X   X
8.1.102.28 [06/22/16] – General X X X X
8.1.102.27 [06/14/16] – Hot Fix   X   X
8.1.102.26 [06/07/16] – Hot Fix   X   X
8.1.102.25 [05/24/16] – Hot Fix   X   X
8.1.102.23 [05/10/16] – Hot Fix   X   X
8.1.102.22 [05/03/16] – Hot Fix   X   X
8.1.102.20 [04/26/16] – Hot Fix   X   X
8.1.102.19 [04/15/16] – Hot Fix   X   X
8.1.102.18 [04/12/16] – Hot Fix   X   X
8.1.102.14 [04/05/16] – Hot Fix   X   X
8.1.102.13 [03/29/16] – Hot Fix   X   X
8.1.102.11 [03/18/16] – Hot Fix   X   X
8.1.102.10 [03/15/16] – Hot Fix   X   X
8.1.102.09 [03/08/16] – Hot Fix   X   X
8.1.102.08 [02/23/16] – Hot Fix   X   X
8.1.102.06 [02/12/16] – Hot Fix   X   X
8.1.102.05 [02/08/16] – Hot Fix   X   X
8.1.102.04 [01/26/16] – Hot Fix   X   X
8.1.102.02 [01/19/16] – Hot Fix   X   X
8.1.102.01 [12/29/15] – Hot Fix   X   X
8.1.102.00 [12/18/15] – Hot Fix   X   X
8.1.101.98 [12/11/15] – General X X X X
8.1.101.97 [12/08/15] – Hot Fix   X   X
8.1.101.95 [11/24/15] – Hot Fix   X   X
8.1.101.94 [11/17/15] – Hot Fix   X   X
8.1.101.93 [11/10/15] – Hot Fix   X   X
8.1.101.92 [11/03/15] – Hot Fix   X   X
8.1.101.91 [10/27/15] – Hot Fix   X   X
8.1.101.90 [10/14/15] – Hot Fix   X   X
8.1.101.88 [10/05/15] – Hot Fix   X   X
8.1.101.87 [09/29/15] – Hot Fix   X   X
8.1.101.86 [09/22/15] – Hot Fix   X   X
8.1.101.85 [09/16/15] – Hot Fix   X   X
8.1.101.83 [09/09/15] – Hot Fix   X   X
8.1.101.81 [09/01/15] – Hot Fix   X X X
8.1.101.79 [08/18/15] – Hot Fix   X   X
8.1.101.78 [08/07/15] – Hot Fix   X   X
8.1.101.76 [08/03/15] – Hot Fix   X   X
8.1.101.75 [07/24/15] – Hot Fix   X   X
8.1.101.74 [07/08/15] – Hot Fix   X   X
8.1.101.73 [06/25/15] – Hot Fix   X   X
8.1.101.69 [06/17/15] – Hot Fix   X   X
8.1.101.68 [06/15/15] – General X X X X
8.1.101.67 [06/02/15] – Hot Fix   X   X
8.1.101.66 [05/21/15] – Hot Fix   X   X
8.1.101.65 [05/13/15] – Hot Fix   X   X
8.1.101.64 [04/27/15] – Hot Fix X X   X
8.1.101.63 [04/14/15] – Hot Fix   X   X
8.1.101.62 [03/30/15] – Hot Fix   X   X
8.1.101.61 [03/17/15] – Hot Fix   X   X
8.1.101.59 [03/06/15] – Hot Fix   X X X
8.1.101.58 [02/17/15] – Hot Fix   X   X
8.1.101.57 [02/12/15] – Hot Fix   X   X
8.1.101.56 [01/30/15] – Hot Fix   X X X
8.1.101.55 [01/23/15] – Hot Fix   X   X
8.1.101.54 [01/16/15] – Hot Fix   X   X
8.1.101.53 [12/23/14] – General X X X X
8.1.101.52 [12/05/14] – Hot Fix   X   X
8.1.101.51 [11/21/14] – Hot Fix   X   X
8.1.101.50 [11/11/14] – Hot Fix   X   X
8.1.101.49 [10/31/14] – Hot Fix   X   X
8.1.101.47 [10/21/14] – Hot Fix   X X X
8.1.101.46 [10/14/14] – Hot Fix   X   X
8.1.101.45 [10/07/14] – Hot Fix   X   X
8.1.101.44 [09/25/14] – Hot Fix   X   X
8.1.101.43 [09/19/14] – Hot Fix   X   X
8.1.101.42 [09/15/14] – Hot Fix   X   X
8.1.101.40 [09/05/14] – Hot Fix   X   X
8.1.101.39 [08/15/14] – Hot Fix   X   X
8.1.101.38 [08/06/14] – Hot Fix   X X X
8.1.101.34 [07/30/14] – General X X X X
8.1.101.33 [07/15/14] – Hot Fix   X   X
8.1.101.30 [07/01/14] – Hot Fix   X   X
8.1.101.29 [06/20/14] – Hot Fix   X   X
8.1.101.28 [06/12/14] – Hot Fix   X   X
8.1.101.27 [06/04/14] – Hot Fix   X   X
8.1.101.25 [05/28/14] – Hot Fix   X   X
8.1.101.23 [05/16/14] – Hot Fix   X   X
8.1.101.22 [05/09/14] – Hot Fix   X   X
8.1.101.20 [04/21/14] – Hot Fix   X   X
8.1.101.19 [03/31/14] – Hot Fix   X   X
8.1.101.18 [03/26/14] – Hot Fix   X   X
8.1.101.17 [03/25/14] – General X X X X
8.1.101.16 [03/04/14] – Hot Fix   X   X
8.1.101.15 [02/21/14] – Hot Fix   X   X
8.1.101.10 [01/31/14] – Hot Fix   X   X
8.1.101.08 [01/21/14] – Hot Fix   X   X
8.1.101.07 [01/14/14] – Hot Fix       X
8.1.101.06 [12/20/13] – Hot Fix   X   X
8.1.101.04 [12/11/13] – Hot Fix       X
8.1.101.03 [11/27/13] – Hot Fix   X   X
8.1.101.01 [11/22/13] – General X X X X
8.1.100.98 [10/30/13] – Hot Fix   X   X
8.1.100.94 [10/21/13] – Hot Fix   X   X
8.1.100.93 [10/11/13] – Hot Fix   X   X
8.1.100.91 [09/27/13] – Hot Fix       X
8.1.100.89 [09/16/13] – Hot Fix   X   X
8.1.100.87 [09/04/13] – Hot Fix       X
8.1.100.86 [08/23/13] – Hot Fix       X
8.1.100.85 [08/16/13] – Hot Fix   X   X
8.1.100.84 [08/09/13] – Hot Fix       X
8.1.100.82 [08/01/13] – Hot Fix       X
8.1.100.81 [07/26/13] – Hot Fix X X   X
8.1.100.80 [07/09/13] – Hot Fix   X   X
8.1.100.78 [06/28/13] – Hot Fix   X   X
8.1.100.77 [06/17/13] – Hot Fix   X   X
8.1.100.75 [06/07/13] – Hot Fix   X   X
8.1.100.74 [05/28/13] – General X X X X
8.1.100.64 [03/15/13] – General X X X X
8.1.001.30 [09/06/13] – Hot Fix   X   X
8.1.001.29 [05/23/13] – Hot Fix   X   X
8.1.001.28 [05/16/13] – Hot Fix     X X
8.1.001.27 [05/08/13] – Hot Fix   X   X
8.1.001.26 [04/26/13] – Hot Fix   X   X
8.1.001.25 [04/11/13] – Hot Fix   X   X
8.1.001.24 [04/09/13] – Hot Fix   X   X
8.1.001.22 [03/14/13] – Hot Fix   X X X
8.1.001.19 [02/14/13] – Hot Fix   X   X
8.1.001.17 [02/01/13] – Hot Fix       X
8.1.001.16 [01/25/13] – Hot Fix   X   X
8.1.001.15 [01/15/13] – General X X X X
8.1.001.12 [12/28/12] – Hot Fix       X
8.1.001.11 [12/12/12] – Hot Fix   X   X
8.1.001.10 [12/06/12] – Hot Fix   X X X
8.1.001.06 [11/19/12] – Hot Fix   X   X
8.1.001.05 [11/09/12] – Hot Fix   X   X
8.1.001.04 [11/02/12] – Hot Fix   X X X
8.1.001.03 [10/22/12] – Hot Fix   X   X
8.1.001.00 [10/12/12] – Hot Fix   X X X
8.1.000.99 [10/05/12] – Hot Fix   X   X
8.1.000.98 [09/28/12] – Hot Fix   X   X
8.1.000.96 [09/20/12] – Hot Fix       X
8.1.000.94 [09/07/12] – Hot Fix   X   X
8.1.000.93 [08/29/12] – Hot Fix X X   X
8.1.000.91 [08/30/12] – General X X X X
8.1.000.90 [08/17/12] – Hot Fix   X X X
8.1.000.89 [08/14/12] – Hot Fix   X   X
8.1.000.88 [08/06/12] – Hot Fix     X X
8.1.000.86 [07/31/12] – Hot Fix     X X
8.1.000.82 [07/17/12] – Hot Fix   X   X
8.1.000.81 [07/03/12] – Hot Fix     X X
8.1.000.80 [06/22/12] – Hot Fix   X X X
8.1.000.79 [06/12/12] – General X X X X
8.1.000.78 [05/31/12] – Hot Fix   X   X
8.1.000.77 [05/18/12] – Hot Fix   X   X
8.1.000.76 [05/04/12] – Hot Fix   X X X
8.1.000.72 [04/19/12] – Hot Fix X     X
8.1.000.70 [04/16/12] – Hot Fix   X   X
8.1.000.68 [04/11/12] – Hot Fix   X X X
8.1.000.65 [03/12/12] – General X X X X
8.1.000.62 [02/29/12] – Hot Fix X X X X
8.1.000.61 [02/24/12] – Hot Fix X X X X
8.1.000.60 [02/17/12] – Hot Fix   X   X
8.1.000.59 [02/10/12] – Hot Fix   X   X
8.1.000.58 [02/03/12] – Hot Fix   X   X
8.1.000.57 [01/30/12] – Hot Fix   X X X
8.1.000.55 [01/13/12] – Hot Fix   X   X
8.1.000.54 [12/30/11] – Hot Fix   X   X
8.1.000.52 [12/16/11] – Hot Fix       X
8.1.000.51 [12/15/11] – General X X X X
8.1.000.49 [12/06/11] – Hot Fix   X   X
8.1.000.47 [11/29/11] – Hot Fix   X   X
8.1.000.46 [11/18/11] – Hot Fix X X   X
8.1.000.45 [10/28/11] – Hot Fix       X
8.1.000.44 [10/24/11] – General X X X X
8.1.000.40 [09/30/11] – Hot Fix X X   X
8.1.000.39 [09/16/11] – Hot Fix   X X X
8.1.000.37 [08/30/11] – General X X X X

Link to 8.0 Product Release Note (Cumulative)
Documentation Corrections
Known Issues and Recommendations
Discontinued Support
Internationalization
Additional Information


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 SIP Server.

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 the Legal Notices for SIP Server. Please contact your Genesys Customer Care representative if you have any questions.


Release Number 8.1.103.59 [08/12/19] – Update

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 release of SIP Server is built with T-Server Common Part (TSCP) release number 8.1.011.13. TSCP is the shared software that all T-Servers and SIP Servers use. Consult the TSCP release note for information about changes to the Common Part that might affect the functionality of SIP Server.

There are no restrictions for this release. This release contains the following new features or functionality:

Corrections and Modifications

This release does not include any corrections.

Top of Page


Release Number 8.1.103.58 [08/02/19] – Update

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 release of SIP Server is built with T-Server Common Part (TSCP) release number 8.1.011.13. TSCP is the shared software that all T-Servers and SIP Servers use. Consult the TSCP release note for information about changes to the Common Part that might affect the functionality of SIP Server.

There are no restrictions for this release. This release contains the following new features or functionality:

Corrections and Modifications

This release does not include any corrections.

Top of Page


Release Number 8.1.103.56 [07/16/19] – Update

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 release of SIP Server is built with T-Server Common Part (TSCP) release number 8.1.011.13. TSCP is the shared software that all T-Servers and SIP Servers use. Consult the TSCP release note for information about changes to the Common Part that might affect the functionality of SIP Server.

There are no restrictions for this release. This release contains the following new features or functionality:

Corrections and Modifications

This release includes the following corrections and modifications:


When a DN located behind the softswitch is placed out of service, SIP Server now correctly sends SIP OPTIONS messages according to the oos-check option to recheck the DN state regardless of the SIP activity. Previously, if there was frequent SIP messaging for this DN, it remained out of service. (SIP-25651)


Top of Page


Release Number 8.1.103.54 [07/09/19] – Update

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 release of SIP Server is built with T-Server Common Part (TSCP) release number 8.1.011.13. TSCP is the shared software that all T-Servers and SIP Servers use. Consult the TSCP release note for information about changes to the Common Part that might affect the functionality of SIP Server.

There are no restrictions for this release. This release contains the following new features or functionality:

Corrections and Modifications

This release includes the following corrections and modifications:


SIP Server in SIP Cluster mode: When a DN is deleted from the configuration environment and then recreated again, SIP Server now correctly processes calls to that DN. Previously, after a DN was recreated, SIP Server considered such a DN as disabled and rejected requests to that DN. (SIP-25231)


Top of Page


Release Number 8.1.103.53 [07/02/19] – Hot Fix

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 release of SIP Server is built with T-Server Common Part (TSCP) release number 8.1.011.13. TSCP is the shared software that all T-Servers and SIP Servers use. Consult the TSCP release note for information about changes to the Common Part that might affect the functionality of SIP Server.

This is a hot fix for this product. This release contains the following new features or functionality:

Corrections and Modifications

This release includes the following corrections and modifications:


When a subscription termination from a phone arrives to SIP Server after the new subscription is already established, SIP Server now correctly sends NOTIFY messages for a new subscription. Previously, SIP Server did not send NOTIFY messages for the SUBSCRIBE request sent for Hotelling events when a phone was restarted. (SIP-25535)


Top of Page


Release Number 8.1.103.52 [06/25/19] – Update

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 release of SIP Server is built with T-Server Common Part (TSCP) release number 8.1.011.13. TSCP is the shared software that all T-Servers and SIP Servers use. Consult the TSCP release note for information about changes to the Common Part that might affect the functionality of SIP Server.

There are no restrictions for this release. This release contains the following new features or functionality:

Corrections and Modifications

This release includes the following corrections and modifications:


After a high-availability (HA) switchover, SIP Server now correctly synchronizes calls in the dialing state with a new primary SIP Server while processing a TMakeCall or TMakePredicitveCall request. Previously, the calls sometimes became stuck in the dialing state after a SIP Server switchover. (SIP-25255, SIP-25254)


SIP Server now correctly waits for a configured value of the predictive-call-timeout configuration option set to greater than 32 seconds during the ringing state of the outbound call and terminates the outbound call when the timeout expires. Previously, SIP Server did not apply the predictive-call-timeout option setting correctly. (SIP-25543)


When an inbound call arrives at an agent DN with a nailed-up connection and the INVITE message contains the X-Genesys header, if userdata-map-all-calls is set to true, SIP Server now maps the SIP header into UserData correctly. Previously, SIP Server did not map call info for calls with nailed-up connections. (SIP-25459)


Top of Page


Release Number 8.1.103.48 [06/04/19] – Update

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 release of SIP Server is built with T-Server Common Part (TSCP) release number 8.1.011.13. TSCP is the shared software that all T-Servers and SIP Servers use. Consult the TSCP release note for information about changes to the Common Part that might affect the functionality of SIP Server.

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

Corrections and Modifications

This release includes the following corrections and modifications:


SIP Server no longer terminates unexpectedly in a scenario with the incorrect configuration in which the Application-level configuration option alternate-route-profile points to a Routing Point containing an empty Default DNs list, and the router-timeout expires at another Routing Point. (SIP-25546)


For DNs located behind the softswitch for 3pcc calls, SIP Server now correctly sends a DN name in the origin section of the request to SIP Feature Server that now includes agent-id in its response. Previously, SIP Server used the Request URI of the origination device instead of the DN name and SIP Feature Server did not include agent-id in the origin section of its response and, as a result, agent-id was missing in the INFO message sent by SIP Server to GVP for recording a 3pcc call initiated by a remote agent. (SIP-25534)


Top of Page


Release Number 8.1.103.46 [05/17/19] – Update

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 release of SIP Server is built with T-Server Common Part (TSCP) release number 8.1.011.13. TSCP is the shared software that all T-Servers and SIP Servers use. Consult the TSCP release note for information about changes to the Common Part that might affect the functionality of SIP Server.

There are no restrictions for this release. This release contains the following new features or functionality:

Corrections and Modifications

This release includes the following corrections and modifications:


In an active-active Resource Manager (RM) environment, if SIP Server receives an MSML error response from one RM to the INFO message for joining all the parties in a two-step conference, SIP Server now selects another RM to recover the conference. Previously, SIP Server did not establish connection with the second RM and failed to recover the conference. (SIP-25361)


When SIP Server tries to resolve any trunk with available gateways, and if an incoming trunk does not match its address with any MSML service, SIP Server no longer attempts to resolve those MSML services. Previously, SIP Server first resolved the MSML service and then tried to match the incoming trunk address with the MSML DN contact, which caused excessive logging. (SIP-25205)


When the session id of the origin header in the SDP becomes greater than a 32-bit integer value, SIP Server can still support that value and pass it correctly in the SDP message "o=" line. Previously, SIP Server increased the session id value from 9 to 20 digits, which became unacceptable for other SIP components. (SIP-25178)


Top of Page


Release Number 8.1.103.45 [05/09/19] – Update

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 release of SIP Server is built with T-Server Common Part (TSCP) release number 8.1.011.13. TSCP is the shared software that all T-Servers and SIP Servers use. Consult the TSCP release note for information about changes to the Common Part that might affect the functionality of SIP Server.

There are no restrictions for this release. This release contains the following new features or functionality:

Corrections and Modifications

This release includes the following corrections and modifications:


To achieve General Data Protection Regulation (GDPR) compliance, agents can now see the reason for the outbound call termination (before a customer answers the call) under the name "GSW_Outbound_Call_Result" on their desktop. If an outbound call is terminated with an error, such as NoAnswer, InvalidNumber, or Busy, SIP Server delivers an appropriate reason to the agent desktop for termination of the outbound call. Previously, SIP Server delivered the Unknown reason in outbound call termination cases. (SIP-25393)


In multisite deployments where SIP Servers are connected via the SBC, SIP Server now sends a NOTIFY message containing the Event header in accordance with RFC 3857. Previously, SIP Server did not include the Event header, causing the SBC to reject the NOTIFY message with an error response. (SIP-25142)


Top of Page


Release Number 8.1.103.43 [04/16/19] – Update

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 release of SIP Server is built with T-Server Common Part (TSCP) release number 8.1.011.13. TSCP is the shared software that all T-Servers and SIP Servers use. Consult the TSCP release note for information about changes to the Common Part that might affect the functionality of SIP Server.

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

Corrections and Modifications

This release includes the following corrections and modifications:


SIP Server now handles the MonitorMode and MonitorScope key values in TMonitorNextCall requests in a case-insensitive manner in both standalone and SIP Cluster modes. Previously, SIP Server handled those keys in a case-insensitive manner only in standalone mode. (SIP-25166)


SIP Server no longer grows in memory when a TMakePredictiveCall request (on a Trunk Group) is timed out or rejected with the 4XX error message. (SIP-25158)


When a subsequent monitored call with AssistMode=mute (after a first call with AssistMode=coach) is released, SIP Server no longer sets the supervisor to the NotReady state with WorkMode=ACW. Previously, when ACW was disabled but LegalGuard Timer was enabled for each call, the supervisor was incorrectly set to the NotReady state with WorkMode=ACW. (SIP-24995)


When the SDP that SIP Server receives contains two media lines—an "m=" line for active audio and an "m=" line for inactive video—SIP Server now correctly generates the hold SDP with the media line for inactive video. Previously, SIP Server incorrectly generated an empty "m=" line. (SIP-24961)


To comply with RFC 3262, SIP Server no longer adds the Contact header to the 200 OK message in response to the PRACK message. (SIP-24891)


Top of Page


Release Number 8.1.103.41 [04/09/19] – Update

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 release of SIP Server is built with T-Server Common Part (TSCP) release number 8.1.011.13. TSCP is the shared software that all T-Servers and SIP Servers use. Consult the TSCP release note for information about changes to the Common Part that might affect the functionality of SIP Server.

There are no restrictions for this release. This release contains the following new features or functionality:

Corrections and Modifications

This release includes the following corrections and modifications:


In the Disable Media Before Greeting feature, SIP Server disables the SDP media for party A and party B before applying a greeting to both and enables the media after the greeting is completed. In this case, before enabling the media for party A, SIP Server now considers if party B has the hold media (intentional hold with the non-active media) and does not enable media for party A. Previously, though party B exchanged with the hold media, SIP Server still enabled the media for party A, which resulted in invalid exchange of SDPs between parties. (SIP-25070)


When SIP Server detects that a Trunk DN for an inbound call is out of service, to enable SIP Server to send a request using the transport associated with the dialog you must set the new configuration option, enable-retransmit-on-oos-transport, to true at either an Application or DN level. Previously, without this option setting, SIP Server sent the timeout and terminated the call.

enable-retransmit-on-oos-transport
Setting: [TServer] section, Application or DN level
Default Value: false (Application level); no default value (DN level)
Valid Values: true, false
Changes Take Effect: For the next call

When this option is set to true, SIP Server continues retransmission of the SIP request using the transport associated with the dialog, even though the DN is detected as out of service. If set to false, SIP Server does not retransmit the request and sends the timeout to the application layer when the DN is detected as out of service.

The DN-level setting takes precedence over the Application-level setting.

(SIP-24999)


When SIP Server detects that there is no active transport available for a destination and a SIP request is received through the transport associated with the dialog, SIP Server now places the transport in service and retransmits the SIP request using the same transaction. Previously, SIP Server created a new transaction for each retransmission request. (SIP-25011)


When a backup SIP Server disconnects from the primary, and fails to synchronize one or more dialogs of a main call, the corresponding main call and any consultation call for that main call will be deleted in the backup SIP Server. Previously, because of the sync failure, even after the main call and consultation call ended in the primary, the consultation call remained active in the backup SIP Server. (SIP-25007)


Top of Page


Release Number 8.1.103.40 [03/22/19] – Update

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 release of SIP Server is built with T-Server Common Part (TSCP) release number 8.1.011.13. TSCP is the shared software that all T-Servers and SIP Servers use. Consult the TSCP release note for information about changes to the Common Part that might affect the functionality of SIP Server.

There are no restrictions for this release. This release contains the following new configuration options:

Corrections and Modifications

This release does not include any corrections.

Top of Page


Release Number 8.1.103.38 [03/05/19] – Update

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 release of SIP Server is built with T-Server Common Part (TSCP) release number 8.1.011.13. TSCP is the shared software that all T-Servers and SIP Servers use. Consult the TSCP release note for information about changes to the Common Part that might affect the functionality of SIP Server.

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

Corrections and Modifications

This release includes the following corrections and modifications:


If, while sending a refresh INVITE message, a TCP connection is lost between SIP Server and a call party, SIP Server now retransmits the INVITE through the new TCP connection. Previously, SIP Server did not retransmit the INVITE, which blocked further session refresh INVITE messages being sent to that party. (SIP-24976)


When trying to establish a third-party recorder connection for an outbound call, SIP Server now ignores unreliable 18x response messages, if the new option, sip-disable-unreliable-sdp, is set to true on the Trunk DN for outbound calls.

sip-disable-unreliable-sdp
Setting: [TServer] section, DN level
Default Value: false
Valid Values: true, false
Changes Take Effect: For the next call

When set to true, SIP Server does not process an unreliable 18x response message containing the SDP received at the DN where this option is configured.

(SIP-24821)


Top of Page


Release Number 8.1.103.37 [03/05/19] – 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

Note: This version was first released as an Update on 02/22/19.

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

There are no restrictions for this release. This release contains the following new features or functionality:

Corrections and Modifications

This release includes the following corrections and modifications:


While using the sips schema for secure SIP signaling, SIP Server now correctly forms the URI in the SIP From header by adding the TLS port. This includes predictive outgoing calls. Previously, SIP Server incorrectly included a non-TLS port in the From URI. (SIP-24962, SIP-24911)


In a multisite call, when the sip-enable-call-info option is set to true and an agent does a single-step conference to a Routing Point followed by a TListenDisconnect request, SIP Server now disconnects the agent from the conference until the agent invokes a TListenReconnect request. Previously, the agent was not disconnected from the conference properly. (SIP-24936)


SIP Server now properly propagates mapped key-value pairs with empty values from UserData to SIP headers of generated INVITE messages. Previously, key-value pairs with empty values were filtered out and not propagated as mapped. (SIP-25115)


Top of Page


Release Number 8.1.103.35 [02/05/19] – Update

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 release of SIP Server is built with T-Server Common Part (TSCP) release number 8.1.011.13. TSCP is the shared software that all T-Servers and SIP Servers use. Consult the TSCP release note for information about changes to the Common Part that might affect the functionality of SIP Server.

There are no restrictions for this release. This release contains the following new features or functionality:

Corrections and Modifications

This release includes the following corrections and modifications:


When SIP Server receives a TApplyTreatment request with the TEXT parameter pointing to an absolute file path, the path string must be appended with the parameter is-absolute-path with a value of true. This way SIP Server does not remove the file:// string when passing the file path to MCP, and MCP is able to access the absolute file path. Previously, SIP Server removed the file:// string for both relative and absolute paths, and MCP was not able to access the absolute file path. (Example of the absolute file path: file://c:\MusicRecourses\GoodBuyGreeting.wav;is-absolute-path=true.) (SIP-24814)


If the SIP Server HA pair fails to synchronize registration of a DN nailed-up connection during network instabilities, agents can now establish a nailed-up connection by logging out and logging in again, once the network becomes stable. Previously, if the ADDP was disabled between primary and backup SIP Server instances, agents were not able to establish a nailed-up connection after re-logging in. (SIP-24763)


In a non-MSML outbound deployment, when TMakePredictiveCall is requested to a trunk that is configured with the replace-prefix option and is not configured with the cpd-capability option, SIP Server properly creates the Request-URI of the INVITE message sent to the trunk. Previously, this Request-URI was formed incorrectly. (SIP-24753)


SIP Server now correctly adds the replaces tag in the Supported header of INVITE, re-INVITE, and 200 OK responses. Previously, SIP Server supported replaces by default, but did not explicitly add the replaces tag in the Supported header. That might cause to some SBCs to filter the Replaces header out, assuming that SIP Server does not support it. (SIP-24676)


When switch partitioning is enabled in SIP Server (the dn-scope option is set to a value other than undefined), SIP Server no longer terminates while generating EventNetworkReached in the scenario where Agent1 conferences a call to Agent2, and Agent2 transfers the call to an external trunk, and then Agent1 releases from the call before the trunk sends confirmation. This fixed issue applied to the single-step conference and single-step transfer scenarios. (SIP-24787)


SIP Server no longer terminates a SIP dialog which provides music when an agent invokes a TListenDisconnect request while he or she is in a conference with a Routing Point. Previously, starting with version 8.1.102.77, SIP Server incorrectly terminated that SIP dialog and corresponding music treatment. (SIP-24774)


When running in SIP Cluster mode and when the http-port option is enabled, SIP Server no longer prints inaccurate messages about the SIP Server HA status in its log. (SIP-23116)


When an agent places a call on hold, but Media Server (to play music on hold) is not responding, then after the agent cancels the hold operation, SIP Server now sends a 487 Request Terminated message, re-invites both call legs, and updates the SDPs. Previously in this scenario, call parties did not hear each other because of the incorrect SDP after canceling the hold operation. (SIP-24187)


When running in SIP Cluster mode, SIP Server now correctly processes the untimed value for the WrapUp time that is set by UserData. Previously, starting with version 8.1.103.20, the agent had not been set to NotReady state after the call release in accordance with the configuration. (SIP-24789)


In a multisite environment, SIP Server now cancels an active ISCC transaction after receiving an error for the call routing attempt. Previously, the transaction was not canceled as expected, which caused external Routing Points to be blocked. (SIP-24784)


Top of Page


Release Number 8.1.103.32 [01/22/19] – Update Unavailable

Supported Operating Systems
New in This Release

Supported Operating Systems

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

New in This Release

As of January 30, 2019, this release is no longer available. A critical issue was discovered. If you downloaded the software, do not install it. The identified issue will be addressed in the next release.

Top of Page


Release Number 8.1.103.29 [12/13/18] – Update Unavailable

Supported Operating Systems
New in This Release

Supported Operating Systems

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

New in This Release

As of January 30, 2019, this release is no longer available. A critical issue was discovered. If you downloaded the software, do not install it. The identified issue will be addressed in the next release.

Top of Page


Release Number 8.1.103.28 [11/20/18] – Update

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 release of SIP Server is built with T-Server Common Part (TSCP) release number 8.1.011.12. TSCP is the shared software that all T-Servers and SIP Servers use. Consult the TSCP release note for information about changes to the Common Part that might affect the functionality of SIP Server.

There are no restrictions for this release. This release contains the following new features or functionality:

Corrections and Modifications

This release includes the following corrections and modifications:


When a TClearCall request is invoked while a call is on a Routing Point during a post-call survey, SIP Server now distributes EventAbandoned with the ReleasingParty key in AttributeExtensions set to a value of 1 Local. Previously, SIP Server distributed EventAbandoned with the ReleasingParty key set to a value of 3 Undefined. (SIP-24733)


In the IP Address Takeover HA configuration, SIP Server runs a Virtual IP address script in accordance with the vip-state-change-timeout option configuration. Previously, if there were network problems and multiple switchovers occurred, SIP Server was not able to run the Virtual IP address scripts successfully. (SIP-24650)


In a SIP Cluster deployment, when an outbound call is done via a Routing Point, SIP Server now correctly adds the X-Genesys-Route header in the ACK message. (SIP-24648)


Top of Page


Release Number 8.1.103.26 [11/13/18] – Update

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 release of SIP Server is built with T-Server Common Part (TSCP) release number 8.1.011.12. TSCP is the shared software that all T-Servers and SIP Servers use. Consult the TSCP release note for information about changes to the Common Part that might affect the functionality of SIP Server.

There are no restrictions for this release. This release contains the following new features or functionality:

Corrections and Modifications

This release includes the following corrections and modifications:


After multiple switchovers, SIP Server now correctly sends CTILINK messages. (SIP-24700)


An inbound call is now connected to an agent, even if SIP Server receives the refresh UPDATE requests in early dialog state. Previously, SIP Server did not connect the call to an agent. (SIP-24639)


SIP Server now correctly retransmits a 200 OK message for transport=tcp when the sip-rel-200-retransmit option is set to true. (SIP-24740)


Top of Page


Release Number 8.1.103.25 [11/06/18] – Update

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 release of SIP Server is built with T-Server Common Part (TSCP) release number 8.1.011.12. TSCP is the shared software that all T-Servers and SIP Servers use. Consult the TSCP release note for information about changes to the Common Part that might affect the functionality of SIP Server.

There are no restrictions for this release. This release contains the following new features or functionality:

Corrections and Modifications

This release includes the following corrections and modifications:


When establishing a nailed-up connection with an agent (connect-nailedup-on-login = gcti::park), and if an MSML VOIP Service DN contains the contact-list option with a list of multiple IP addresses containing the transport=tcp parameters, SIP Server now correctly includes the transport=tcp parameter in the Contact header when sending an INVITE message to the agent. Previously, SIP Server did not include the transport=tcp parameter in the Contact header, defaulting to the UDP transport. (SIP-24590)


When a REFER with the Replaces header request is issued to perform a blind transfer to a Routing Point and a treatment is played, the backup SIP Server deletes the old media service and its associated connection when the call ends. This ensures that the DN is unreserved when a call is terminated, and when a switchover occurs, SIP Server processes the call on this agent DN. Previously, after a switchover, SIP Server did not process the call on the agent DN with the reject-call-incall option set to true, because it remained in the reserved state. (SIP-24392)


Top of Page


Release Number 8.1.103.24 [10/30/18] – Update

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 release of SIP Server is built with T-Server Common Part (TSCP) release number 8.1.011.12. TSCP is the shared software that all T-Servers and SIP Servers use. Consult the TSCP release note for information about changes to the Common Part that might affect the functionality of SIP Server.

There are no restrictions for this release. This release contains the following new features or functionality:

Corrections and Modifications

This release includes no corrections.

Top of Page


Release Number 8.1.103.23 [10/16/18] – Update

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 release of SIP Server is built with T-Server Common Part (TSCP) release number 8.1.011.12. TSCP is the shared software that all T-Servers and SIP Servers use. Consult the TSCP release note for information about changes to the Common Part that might affect the functionality of SIP Server.

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

Corrections and Modifications

This release includes the following corrections and modifications:


Hoteling subscriptions are now synchronized between SIP Servers in the HA pair, and SIP Server now increments a CSeq number for a specified method after each switchover. Previously, hoteling subscriptions were not synchronized, and when a double switchover occurred, the new primary SIP Server sent a hotelling NOTIFY message with the CSeq number less than the previous one, which was rejected by a Polycom phone. (SIP-24601)


Hoteling subscriptions are now synchronized between SIP Servers in the HA pair, and subscription dialogs are now correctly associated after each switchover. Previously, hoteling subscriptions were not synchronized and subsequent requests were rejected by SIP Server. (SIP-24544)


When blind-transfer-enabled is set to true, sip-ring-tone is set to 1, and recording is enabled on all 3 DNs, SIP Server no longer drops a call when a consulted party answers the blind-transferred call. (SIP-24339)


Top of Page


Release Number 8.1.103.21 [10/02/18] – Update

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 release of SIP Server is built with T-Server Common Part (TSCP) release number 8.1.011.12. TSCP is the shared software that all T-Servers and SIP Servers use. Consult the TSCP release note for information about changes to the Common Part that might affect the functionality of SIP Server.

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

Corrections and Modifications

This release includes the following corrections and modifications:


If call recording fails during call redirection to an after-call survey, SIP Server no longer generates an alarm and increments the NCALLRECORDINGFAILED statistic. (SIP-24485)


In a multisite deployment, when a remote observer connects to an observing conference and the observer's device sends several re-INVITE messages, SIP Server no longer disconnects the observer from the call. (SIP-24484)


In a multisite deployment, when an agent and a customer are located at one site, and if an observer that is located at another site places the call on hold, the agent and the customer now correctly hear silence. Ensure that the sip-enable-call-info option is set to true. Previously, the agent and the customer heard music-on-hold instead. (SIP-24465)


In SIP Cluster mode, after a BusinessCall that a supervisor monitored is released, SIP Server now correctly applies the Application-level option call-monitor-acw and the AfterCallWork (ACW) state to the supervisor. Previously, SIP Server placed the supervisor to the ACW state even when the call-monitor-acw option was set to false. (SIP-24450)


SIP Server no longer opens inter-thread TCP ports to external clients. Previously, SIP Server sometimes terminated when a network scanning tool probed internal SIP Server ports. (SIP-24421)


Top of Page


Release Number 8.1.103.20 [09/18/18] – Update

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 release of SIP Server is built with T-Server Common Part (TSCP) release number 8.1.011.12. TSCP is the shared software that all T-Servers and SIP Servers use. Consult the TSCP release note for information about changes to the Common Part that might affect the functionality of SIP Server.

There are no restrictions for this release. This release contains the following new features or functionality:

Corrections and Modifications

This release includes the following corrections and modifications:


In a multisite deployment, after a call is routed to an agent on the second site and when the agent does a single-step transfer using the pullback transaction type while a re-INVITE request is in progress, SIP Server now performs the transfer operation after completion of the re-INVITE operation. Previously, in this race-condition scenario, the call was disconnected when the next TRouteCall was processed. (SIP-24481)


When running in SIP Cluster mode, if SIP Server receives a TRegisterAddress request for an Extension DN that is disabled in the configuration database, SIP Server now correctly responds with EventRegistered (status=OOS). Previously, SIP Server responded with EventError "DN is not configured in CME". (SIP-24166)


Top of Page


Release Number 8.1.103.18 [09/07/18] – Update

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 release of SIP Server is built with T-Server Common Part (TSCP) release number 8.1.011.12. TSCP is the shared software that all T-Servers and SIP Servers use. Consult the TSCP release note for information about changes to the Common Part that might affect the functionality of SIP Server.

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

Corrections and Modifications

This release includes the following corrections and modifications:


When a DN is configured with the force-register option to require registration, SIP Server now correctly processes a 407 Proxy Authentication Required message that it receives in response to a REGISTER request. Previously, SIP Server ignored a 407 response and did not generate a new REGISTER request with authentication information. (SIP-24268)


SIP Server supports a new Application-level configuration option for the Agent Login and State Update on SIP Phones feature:

agent-allow-empty-password
Setting: [TServer] section
Default Value: true
Valid Values: true, false
Change Take Effect: For the next agent login

When set to true, SIP Server allows an agent to log in from a SIP phone without the password. When set to false, SIP Server rejects agent logging from a SIP phone without the password.

(SIP-21805)


When running in SIP Cluster mode, if the external-contact option is set to an SRV record, SIP Server now correctly resolves it and adds the correct Route header for outbound SIP messages. (SIP-24479)


When running in SIP Cluster mode, SIP Server no longer consumes excessive memory while synchronizing its messages in this rare scenario: SCS loses its connection to a primary LCA, SCS instructs the backup SIP Server to switch its role to a primary, and, at the same time, the primary SIP Server remains running in primary mode. (SIP-24016)


Top of Page


Release Number 8.1.103.17 [08/17/18] – Update

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 release of SIP Server is built with T-Server Common Part (TSCP) release number 8.1.011.12. TSCP is the shared software that all T-Servers and SIP Servers use. Consult the TSCP release note for information about changes to the Common Part that might affect the functionality of SIP Server.

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

Corrections and Modifications

This release includes the following corrections and modifications:


In a single-step conference scenario from an agent to a recorder (gcti::record), when the call is released by the agent, SIP Server now correctly includes AttributeCtrlParty in EventCallDeleted. (SIP-24249)


Top of Page


Release Number 8.1.103.16 [08/14/18] – Update

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 release of SIP Server is built with T-Server Common Part (TSCP) release number 8.1.011.10. TSCP is the shared software that all T-Servers and SIP Servers use. Consult the TSCP release note for information about changes to the Common Part that might affect the functionality of SIP Server.

There are no restrictions for this release. This release contains the following new features or functionality:

Corrections and Modifications

This release includes the following corrections and modifications:


In multisite deployments, when a consultation call from Site 1 arrives as a non-business call at Site 2 (the bsns-call-dev-types option was set to -xrp), and after a consultation agent at Site 1 completes the transfer of the consultation call, SIP Server now correctly changes the call type to business if the main call at Site 1 was a business call. Previously, in such deployments, SIP Server did not set the call type to business. (SIP-24189)


In multisite deployments, when reject-call-incall is set to true, SIP Server now correctly handles a postponed scenario for a REFER request that it receives while another call-related operation is in progress. Previously, in this race-condition scenario, SIP Server did not clean up a transaction because of the postponed call operation, resulting in incorrectly rejected calls. (SIP-24008)


Top of Page


Release Number 8.1.103.15 [07/31/18] – Update

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 release of SIP Server is built with T-Server Common Part (TSCP) release number 8.1.011.10. TSCP is the shared software that all T-Servers and SIP Servers use. Consult the TSCP release note for information about changes to the Common Part that might affect the functionality of SIP Server.

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

Corrections and Modifications

This release includes the following corrections and modifications:


In deployments with SIP Proxy, after receiving a TNetworkPrivateService request containing a reboot parameter from SIP Feature Server for a registered device, SIP Server now correctly sends NOTIFY to that device to inform the device about its reboot. Previously, SIP Server did not send NOTIFY to the device. (SIP-24304)


Top of Page


Release Number 8.1.103.14 [07/17/18] – Update

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 release of SIP Server is built with T-Server Common Part (TSCP) release number 8.1.011.10. TSCP is the shared software that all T-Servers and SIP Servers use. Consult the TSCP release note for information about changes to the Common Part that might affect the functionality of SIP Server.

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

Corrections and Modifications

This release includes the following corrections and modifications:


This release contains modifications to support Genesys Cloud implementations only. (SIP-24363)


Top of Page


Release Number 8.1.103.13 [07/10/18] – Update

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 release of SIP Server is built with T-Server Common Part (TSCP) release number 8.1.011.10. TSCP is the shared software that all T-Servers and SIP Servers use. Consult the TSCP release note for information about changes to the Common Part that might affect the functionality of SIP Server.

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

Corrections and Modifications

This release includes the following corrections and modifications:


In a race-condition scenario when the ACK message with SDP Answer is delayed during SDP negotiation between two parties, SIP Server now correctly connects a call. Previously, if the called party sent a re-INVITE without the SDP and did not send the ACK message for the 200 OK with the last known SDP soon enough, the call became stuck. (SIP-24239)


When a REFER request is rejected with a specific error code, SIP Server now forwards that error code in the body of the NOTIFY message. Previously, SIP Server incorrectly sent a default error code "500 Server Internal error" in NOTIFY, instead of the received error code. (SIP-24165)


Top of Page


Release Number 8.1.103.12 [06/29/18] – Update

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 release of SIP Server is built with T-Server Common Part (TSCP) release number 8.1.011.10. TSCP is the shared software that all T-Servers and SIP Servers use. Consult the TSCP release note for information about changes to the Common Part that might affect the functionality of SIP Server.

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

Corrections and Modifications

This release includes the following corrections and modifications:


When sip-signaling-chat is set to none, and an inbound call with AtrributeExtentions chat set to true is made to a Routing Point, and after receiving the TRouteCall request containing RouteTypeReject, SIP Server now correctly releases the call. Previously, SIP Server rejected TRouteCall with the EventError message. (SIP-24213)


When disable-media-before-greeting is set to true, and a call containing invalid greeting extensions in AttributeExtensions of TRouteCall is routed to an agent, SIP Server now correctly connects an agent with a caller. Previously, SIP Server placed the agent on hold. (SIP-24191)


When an inbound call is routed to an agent and then returned to a Routing Point according to the no-answer-overflow option that is set to recall, and a treatment is applied, SIP Server now applies the media stream correctly. Previously, if the SDP was sent in response to the first INVITE in an unreliable 180 Ringing message, SIP Server did not apply the media to a treatment correctly. (SIP-24132)


SIP Server now correctly sends EventAgentLogin and EventAgentReady messages when an endpoint with the enable-agentlogin-presence option starts in the out-of-service state and registers with SIP Server using the SIP REGISTER request. (SIP-24062)


Top of Page


Release Number 8.1.103.11 [06/22/18] – Update

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 release of SIP Server is built with T-Server Common Part (TSCP) release number 8.1.011.10. TSCP is the shared software that all T-Servers and SIP Servers use. Consult the TSCP release note for information about changes to the Common Part that might affect the functionality of SIP Server.

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

Corrections and Modifications

This release includes the following corrections and modifications:


In a multi-site deployment, in a remote supervision scenario with a scope agent, a caller from Site 1 is being transferred to the SIP Server at the remote site (Site 2) and a supervisor from Site 1 starts monitoring Agent 2 on Site 2. Previously, after the TCompleteTransfer request, the caller was added through the INVITE with Replaces message to the SIP Server at Site 2, and the supervisor's desktop was not updated with the caller number. Now, call participants are correctly updated on the supervisor's desktop at Site 1. (SIP-24002)


Top of Page


Release Number 8.1.103.10 [05/25/18] – Update

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 release of SIP Server is built with T-Server Common Part (TSCP) release number 8.1.011.10. TSCP is the shared software that all T-Servers and SIP Servers use. Consult the TSCP release note for information about changes to the Common Part that might affect the functionality of SIP Server.

There are no restrictions for this release. This release contains the following new features or functionality:

Corrections and Modifications

This release includes the following corrections and modifications:


When enable-strict-location-match is set to true and no-answer-timeout expires, SIP Server now correctly connects the caller to the agent's voicemail (no-answer-overflow). Previously in this scenario, SIP Server did not connect the caller to the voicemail. (SIP-23936)


When SIP Server goes out of the signaling path, the custom headers from a REFER message are now filtered and sent in the outgoing REFER according to the sip-pass-refer-headers option setting. Previously in this scenario, SIP Server did not filter custom headers from the REFER. (SIP-23190)


SIP Server now sends EventPartyChanged and EventUserEvent in the correct order when the epp-tout option is set to a non-zero value. Previously, SIP Server sent EventUserEvent with the new ConnID value before sending EventPartyChanged that contained the previous and actual ConnID. (SIP-23136)


Top of Page


Release Number 8.1.103.08 [05/15/18] – Update

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 release of SIP Server is built with T-Server Common Part (TSCP) release number 8.1.011.09. TSCP is the shared software that all T-Servers and SIP Servers use. Consult the TSCP release note for information about changes to the Common Part that might affect the functionality of SIP Server.

There are no restrictions for this release. This section describes new features that were introduced in this release of SIP Server.

Corrections and Modifications

This release does not include any corrections.

Top of Page


Release Number 8.1.103.07 [05/08/18] – Update

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 release of SIP Server is built with T-Server Common Part (TSCP) release number 8.1.011.09. TSCP is the shared software that all T-Servers and SIP Servers use. Consult the TSCP release note for information about changes to the Common Part that might affect the functionality of SIP Server.

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

Corrections and Modifications

This release includes the following corrections and modifications:


SIP Server now correctly starts recording of a predictive outbound call when Agent A transfers the call to a Routing Point and the call is routed to Agent B. Agent DNs are configured with record=true and the ringback. Previously, SIP Server incorrectly started recording during the ringback and did not reconnect the recorder to the call, which resulted in a dropped outbound call. (SIP-23791)


When an external Trunk does not respond to a TMakePredictiveCall request and SIP Server attempts to find an alternative Trunk without success, and the call is released because of the timeout, SIP Server now generates EventReleased containing CallState 7 (CallStateNoAnswer). Previously in this scenario, SIP Server generated EventReleased containing CallState 0 (CallStateOk). (SIP-23513)

Note: This issue was initially fixed in release 8.1.103.00, but now extends to the alternative trunk scenario.


When a TRouteCall request contains customer-greeting and agent-greeting key-value pairs in AttributeExtensions, SIP Server now correctly applies greetings to a call in a scenario where divert-on-ringing is set to false and the call is diverted to another agent DN because after-routing-timeout expires. Previously in this scenario, SIP Server did not apply greetings. (SIP-23347)


Top of Page


Release Number 8.1.103.06 [04/27/18] – 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

Note: This version was first released as an Update on 04/17/18.

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

There are no restrictions for this release. This release contains the following new features or functionality:

Corrections and Modifications

This release does not include any corrections.

Top of Page


Release Number 8.1.103.04 [04/10/18] – Update

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 release of SIP Server is built with T-Server Common Part (TSCP) release number 8.1.011.09. TSCP is the shared software that all T-Servers and SIP Servers use. Consult the TSCP release note for information about changes to the Common Part that might affect the functionality of SIP Server.

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

Corrections and Modifications

This release includes the following corrections and modifications:


When the Masking Sensitive Data in SIP Messages feature is enabled, SIP Server no longer prints received DTMF symbols in the SIP Server log files. Previously, if the log output was set to the Debug level, some DTMF data was printed in the Debug-level messages. (SIP-23669)


Top of Page


Release Number 8.1.103.03 [03/19/18] – Update

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 release of SIP Server is built with T-Server Common Part (TSCP) release number 8.1.011.09. TSCP is the shared software that all T-Servers and SIP Servers use. Consult the TSCP release note for information about changes to the Common Part that might affect the functionality of SIP Server.

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

Corrections and Modifications

This release includes the following corrections and modifications:


When an inbound call is routed to an agent with the nailed-up connection and a preview interaction is enabled, SIP Server now extracts the AttributeExtensions from the TRouteCall request and apply them accordingly to the call after the preview interaction is finished. Previously, SIP Server did not extract the extensions from the TRouteCall request, which resulted in the wrong music-on-hold file being played. (SIP-23712)


When an agent is in a conference call for a call supervision and a consultation call is established at the remote site, and the record-consult-call option is set to true, if the agent completes a transfer, SIP Server no longer sends a SIP INFO message containing the <modifyconference> element to the consultation call recording leg. Previously, SIP Server incorrectly sent the malformed MSML message that was rejected by MCP, which caused the transfer operation to fail. (SIP-23674)


Recording of the GSW_CONNECT_TIME value always occurs after the corresponding 200 OK is received by SIP Server. Now, SIP Server correctly shows the value of GSW_CONNECT_TIME. Previously, the GSW_CONNECT_TIME value was sometimes recorded 1 second earlier than the logged timestamp of the triggering 200 OK message. (SIP-23653)


When a nailed-up connection is configured with the Preview Interaction and reuse-sdp-on-reinvite is set to true, and an agent with the nailed-up connection is connected to an inbound caller through aTRouteCall request for the second time, SIP Server now reports AttributeOtherDN as the inbound caller number in both EventRinging and Event Established messages. Previously, SIP Server incorrectly reported AttributeOtherDN as the Routing Point number in EventEstablished. (SIP-23460)


Top of Page


Release Number 8.1.103.02 [03/13/18] – Update

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 release of SIP Server is built with T-Server Common Part (TSCP) release number 8.1.011.09. TSCP is the shared software that all T-Servers and SIP Servers use. Consult the TSCP release note for information about changes to the Common Part that might affect the functionality of SIP Server.

There are no restrictions for this release. This release contains the following new features or functionality:

Corrections and Modifications

This release includes the following corrections and modifications:


SIP Server now correctly handles error responses from SIP Feature Server that are sent in fragmented messages. Previously in this scenario, SIP Server sometimes terminated unexpectedly. (SIP-23636)


Top of Page


Release Number 8.1.103.01 [03/05/18] – Update

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 release of SIP Server is built with T-Server Common Part (TSCP) release number 8.1.011.09. TSCP is the shared software that all T-Servers and SIP Servers use. Consult the TSCP release note for information about changes to the Common Part that might affect the functionality of SIP Server.

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

Corrections and Modifications

This release includes the following corrections and modifications:


This release contains modifications to support Genesys Cloud implementations only. (SIP-23550)


Top of Page


Release Number 8.1.103.00 [02/21/18] – Update

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 release of SIP Server is built with T-Server Common Part (TSCP) release number 8.1.011.09. TSCP is the shared software that all T-Servers and SIP Servers use. Consult the TSCP release note for information about changes to the Common Part that might affect the functionality of SIP Server.

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

Corrections and Modifications

This release includes the following corrections and modifications:


When an inbound call is established with an agent and a consultation call is going through an outbound Trunk with required authentication, SIP Server now correctly sends an INVITE with authorization parameters and without the SDP. In addition, after the CompleteTransfer the agent leaves the call, both external parties have a proper RTP flow. Previously in this scenario, SIP Server sent the old SDP content that resulted in a one-way audio call. (SIP-23553)


If the DN-level option use-register-for-service-state is set to true and the registration expires, SIP Server now correctly places that DN in out of service. Previously, SIP Server placed the DN back in service when the recovery-timeout option expired, even if the DN contact was empty because of the expired registration. (SIP-23529)


When an external Trunk responds to a TMakePredictiveCall request with only a 100 Trying message (without 180 Ringing) and the call is released because of the timeout, SIP Server now generates EventReleased containing CallState 7 (CallStateNoAnswer). Previously in this scenario, SIP Server generated EventReleased containing CallState 0 (CallStateOk). (SIP-23513)

Note: A new alternative trunk scenario was added in release 8.1.103.07. Use release 8.1.103.07 for your environment.


Top of Page


Release Number 8.1.102.99 [02/06/18] – Update

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 release of SIP Server is built with T-Server Common Part (TSCP) release number 8.1.011.09. TSCP is the shared software that all T-Servers and SIP Servers use. Consult the TSCP release note for information about changes to the Common Part that might affect the functionality of SIP Server.

There are no restrictions for this release. This release contains the following new features or functionality:

Corrections and Modifications

This release includes the following corrections and modifications:


In a multi-thread SIP Server deployment configured with drop-nailedup-on-logout=true, a nailed-up connection to an agent using a non-provisioned external phone number is now correctly terminated by SIP Server when the agent logs out. Previously in this scenario, SIP Server did not terminate that nailed-up connection. (SIP-23388)


An agent is now able to log in from the Polycom phone using a new Agent Login ID after Configuration Server was restarted. Previously in this scenario, SIP Server did not process the SUBSCRIBE message with the x-broadworks-hoteling event from the Polycom phone properly. (SIP-23386)


In scenarios where SIP Server receives EventNetworkPrivateInfo from the other site to start recording, SIP Server no longer starts recording on a Routing Point where a call is still queued. Previously, SIP Server incorrectly started recording of the call that was queued on a Routing Point. (SIP-23339)


If a PlayAnnouncementAndCollectDigits treatment is stopped by GVP with an error response to the PlayAnnouncement dialog, SIP Server now correctly terminates both the associated treatment dialogs. Previously, SIP Server did not terminate the CollectDigits dialog when a PlayAnnouncement dialog was terminated by GVP, which resulted in collection of duplicated digits. (SIP-23325)


SIP Server now correctly connects an observer to a call using a TSingleStepConference request with AssistMode=coach. Previously, if the destination DN in the TSingleStepConference request from the observer was changed to a new DN by applying the dial-plan-rule option, SIP Server rejected further TSingleStepConference requests to the same DN with EventError. (SIP-23262)


Top of Page


Release Number 8.1.102.98 [01/23/18] – Hot Fix

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 release of SIP Server is built with T-Server Common Part (TSCP) release number 8.1.011.09. TSCP is the shared software that all T-Servers and SIP Servers use. Consult the TSCP release note for information about changes to the Common Part that might affect the functionality of SIP Server.

This is a hot fix for this product. This release contains the following new features or functionality:

Corrections and Modifications

This release includes the following corrections and modifications:


SIP Server no longer terminates unexpectedly while trying to reconnect to SIP Feature Server when one of the Feature Server nodes is down. (SIP-23463)


Top of Page


Release Number 8.1.102.96 [12/20/17] – Hot Fix

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 release of SIP Server is built with T-Server Common Part (TSCP) release number 8.1.011.09. TSCP is the shared software that all T-Servers and SIP Servers use. Consult the TSCP release note for information about changes to the Common Part that might affect the functionality of SIP Server.

This is a hot fix for this product. This release does not contain new features or functionality.

Corrections and Modifications

This release includes the following corrections and modifications:


In the scenario where a conditional dial-plan parameter onnotreg, ontimeout, onbusy, or ondnd is applied to forward calls to a trunk configured with sip-enable-diversion=true, SIP Server now correctly adds only one @hostname to the destination DN name in the Diversion header. Previously, SIP Server incorrectly added the @hostname twice to the destination DN name. (SIP-23346)


In a NETANN-based deployment when a race condition occurs between ApplyTreatment and SendDTMF signaling handshakes, calls no longer become stuck. Previously, if reject-call-incall was set to true, calls to the Agent DN from which SendDTMF was sent were rejected. (SIP-23264)


Top of Page


Release Number 8.1.102.95 [12/13/17] – Hot Fix

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 release of SIP Server is built with T-Server Common Part (TSCP) release number 8.1.011.09. TSCP is the shared software that all T-Servers and SIP Servers use. Consult the TSCP release note for information about changes to the Common Part that might affect the functionality of SIP Server.

This is a hot fix for this product. This release contains the following new features or functionality:

Note: This release is not recommended for integration with SIP Feature Server. See known issue SIP-23463.

Corrections and Modifications

This release does not include any corrections.

Top of Page


Release Number 8.1.102.94 [12/01/17] – Hot Fix

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 release of SIP Server is built with T-Server Common Part (TSCP) release number 8.1.011.08. TSCP is the shared software that all T-Servers and SIP Servers use. Consult the TSCP release note for information about changes to the Common Part that might affect the functionality of SIP Server.

This is a hot fix for this product. This release does not contain new features or functionality.

Corrections and Modifications

This release includes the following corrections and modifications:


If both greeting-notification=started and record-agent-greeting=true are configured, when the greeting is finished, SIP Server now generates EventPrivateInfo to notify the agent that the greeting is finished. Previously in this scenario, SIP Server did not generate the greeting completion notification. (SIP-23195)


In the following scenario, if wrap-up-time=<non-zero value (0)> and inbound-bsns-calls=true are configured on both Routing Points (RP1 and RP2), SIP Server no longer terminates unexpectedly while generating EventEstablished:

  1. An inbound call is routed from RP1 to an agent on DN1.
  2. The agent answers the call.
  3. RP1 is deleted in the Genesys configuration.
  4. The agent on DN1 makes a single-step transfer to RP2.
  5. The call is routed from RP2 to the agent on DN2, and the agent on DN2 answers the call.
  6. SIP Server attempts to generate EventEstablished.

(SIP-23015)


Top of Page


Release Number 8.1.102.93 [11/14/17] – Hot Fix

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 release of SIP Server is built with T-Server Common Part (TSCP) release number 8.1.011.08. TSCP is the shared software that all T-Servers and SIP Servers use. Consult the TSCP release note for information about changes to the Common Part that might affect the functionality of SIP Server.

This is a hot fix for this product. This release contains the following new features or functionality:

Corrections and Modifications

This release does not include any corrections.

Top of Page


Release Number 8.1.102.92 [11/07/17] – Hot Fix

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 release of SIP Server is built with T-Server Common Part (TSCP) release number 8.1.011.08. TSCP is the shared software that all T-Servers and SIP Servers use. Consult the TSCP release note for information about changes to the Common Part that might affect the functionality of SIP Server.

This is a hot fix for this product. This release contains the following new features or functionality:

Corrections and Modifications

This release includes the following corrections and modifications:


When the sip-filter-media option is set to video, SIP Server now correctly forms SIP messages with SDP Media m=video lines set to 0 (zero). Previously, SIP Server incorrectly removed the m=video line from the SDP. (SIP-22986)


Top of Page


Release Number 8.1.102.90 [10/24/17] – Hot Fix

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 release of SIP Server is built with T-Server Common Part (TSCP) release number 8.1.011.08. TSCP is the shared software that all T-Servers and SIP Servers use. Consult the TSCP release note for information about changes to the Common Part that might affect the functionality of SIP Server.

This is a hot fix for this product. This release does not contain new features or functionality.

Corrections and Modifications

This release includes the following corrections and modifications:


When the userdata-map-format option is set to sip-headers-encoded, SIP Server now encodes the user data key values of integer type. Previously, only the string data type was encoded correctly. (SIP-23032)


SIP Server now rejects TSingleStepTransfer of the main call if the related consultation call is present. (SIP-22815)


SIP Server now distributes EventError in response to a TRouteCall request when a routing target redirects a call to a DN, which is not available to accept the call, by sending the 302 response. Previously, when the first target sent a 180 response before the 302 response and the divert-on-ringing option was set to false, the call was redirected to an unavailable DN and became stuck. (SIP-22539)


SIP Server no longer incorrectly releases a main call when its related consultation call, after routing to an agent, was redirected by the 302 response to another agent that was not available to accept that call. This issue applied when the dual-dialog-enabled option was set to false. (SIP-22513)


When SIP Server receives the TRouteCall request containing the OtherDN attribute with a value of dn@host:port, it sends the 302 response containing the proper contact as dn@host:port. Previously in this scenario, SIP Server included the invalid contact value (dn@host:port@host:port). (SIP-22154)


Top of Page


Release Number 8.1.102.89 [10/06/17] – Hot Fix

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 release of SIP Server is built with T-Server Common Part (TSCP) release number 8.1.011.08. TSCP is the shared software that all T-Servers and SIP Servers use. Consult the TSCP release note for information about changes to the Common Part that might affect the functionality of SIP Server.

This is a hot fix for this product. This release contains the following new features or functionality:

Corrections and Modifications

This release includes no corrections.

Top of Page


Release Number 8.1.102.88 [09/26/17] – Hot Fix

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 release of SIP Server is built with T-Server Common Part (TSCP) release number 8.1.011.08. TSCP is the shared software that all T-Servers and SIP Servers use. Consult the TSCP release note for information about changes to the Common Part that might affect the functionality of SIP Server.

This is a hot fix for this product. This release does not contain new features or functionality.

Corrections and Modifications

This release includes the following corrections and modifications:


SIP Server now stops the no-answer supervision timer, when an agent answered a call but re-INVITE sent to the caller was failed. Previously, SIP Server reported the agent as NotReady with the reason “no-answer” because the no-answer supervision timer expired. (SIP-22767)


Top of Page


Release Number 8.1.102.86 [09/19/17] – Hot Fix

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 release of SIP Server is built with T-Server Common Part (TSCP) release number 8.1.011.08. TSCP is the shared software that all T-Servers and SIP Servers use. Consult the TSCP release note for information about changes to the Common Part that might affect the functionality of SIP Server.

This is a hot fix for this product. This release does not contain new features or functionality.

Corrections and Modifications

This release includes the following corrections and modifications:


SIP Server no longer terminates unexpectedly while processing session refresh transactions for unresponsive devices. (SIP-22900)


Top of Page


Release Number 8.1.102.85 [09/12/17] – Hot Fix

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 release of SIP Server is built with T-Server Common Part (TSCP) release number 8.1.011.08. TSCP is the shared software that all T-Servers and SIP Servers use. Consult the TSCP release note for information about changes to the Common Part that might affect the functionality of SIP Server.

This is a hot fix for this product. This release does not contain new features or functionality.

Corrections and Modifications

This release includes the following corrections and modifications:


If an incoming trunk DN contains the sip-early-dialog-mode option set to 1 and an incoming INVITE message has no SDP and no Supported: 100rel parameter, SIP Server now sends a 200 OK message. Previously, SIP Server incorrectly sent the 183 Session in Progress message with the SDP and waited for a PRACK that never came because of unsupported 100rel, which resulted in a stuck call. (SIP-22777)


SIP Server no longer terminates unexpectedly when a 1pcc outbound call from the shared line member is placed on hold and then an attempt to seize the line is made by the same shared line member of the shared line group. Now, in this scenario, the first call will be released and the second call will be connected. (SIP-22763)


SIP Server no longer sends a re-INVITE message to a busy destination party. Previously, when a destination party responded with a 486 Busy Here message while SIP Server had not yet received a response to a NOTIFY message, SIP Server sent re-INVITE to the busy party. The problem was that while SIP Server was processing a TSingleStepTransfer by REFER request from DN1 and sending re-INVITE to DN2 (configured with refer-enabled set to false), SIP Server sent NOTIFY to DN1, which did not respond immediately. (SIP-22746)


Top of Page


Release Number 8.1.102.84 [09/06/17] – Hot Fix

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 release of SIP Server is built with T-Server Common Part (TSCP) release number 8.1.011.08. TSCP is the shared software that all T-Servers and SIP Servers use. Consult the TSCP release note for information about changes to the Common Part that might affect the functionality of SIP Server.

This is a hot fix for this product. This release does not contain new features or functionality.

Corrections and Modifications

This release includes the following corrections and modifications:


When recording is enabled and the disable-media-before-greeting option is set to true, SIP Server now correctly handles a TMakeCall request to an external DN, from the parked agent with a nailed-up connection. Previously, a ringback was not played to an agent on the outbound call if the previous inbound call was dropped by a caller before the recording was established. (SIP-22835)


SIP Server now correctly passes a 486 Busy response to the call originator after receiving the 302 Redirect message and if the 486 Busy response was the first response from the new contact to the INVITE request. (SIP-22655)


In a multi-site deployment where the same Agent Login object is configured under Switch1 on SIP Server1 and Switch2 on SIP Server2, when the Agent Login object is deleted from Switch1 explicitly, it is now deleted only in the SIP Server1 application. When a SUBSCRIBE message is received on SIP Server2 from a DN associated with the Agent Login (broadsoft-hoteling event), SIP Server2 will send NOTIFY containing AgentID associated with the DN. Previously in this scenario, this Agent Login was also deleted from the SIP Server2 application, and for the SUBSCRIBE request to this Agent Login on Switch2, SIP Server generated NOTIFY containing no AgentID and terminated the hoteling feature. (SIP-22578)


Top of Page


Release Number 8.1.102.83 [08/22/17] – Hot Fix

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 release of SIP Server is built with T-Server Common Part (TSCP) release number 8.1.011.08. TSCP is the shared software that all T-Servers and SIP Servers use. Consult the TSCP release note for information about changes to the Common Part that might affect the functionality of SIP Server.

This is a hot fix for this product. This release does not contain new features or functionality.

Corrections and Modifications

This release includes the following corrections and modifications:


This release contains modifications to support Genesys Cloud implementations only. (SIP-22748)


Top of Page


Release Number 8.1.102.81 [08/15/17] – Hot Fix

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 release of SIP Server is built with T-Server Common Part (TSCP) release number 8.1.011.07. TSCP is the shared software that all T-Servers and SIP Servers use. Consult the TSCP release note for information about changes to the Common Part that might affect the functionality of SIP Server.

This is a hot fix for this product. This release contains the following new features or functionality:

Corrections and Modifications

This release includes the following corrections and modifications:


When an agent changes the state from Not Ready with a Reason Code to Not Ready with no Reason Code by issuing the TAgentNotReady request, and when SIP Server receives the re-subscription request from an IP phone, SIP Server now properly synchronizes the Not Ready state with no Reason Code between the IP phone and the Agent desktop. Previously, SIP Server added a Reason Code from the previous state in the NOTIFY message for re-subscription. (SIP-22657)


Top of Page


Release Number 8.1.102.80 [08/04/17] – Hot Fix

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 release of SIP Server is built with T-Server Common Part (TSCP) release number 8.1.011.07. TSCP is the shared software that all T-Servers and SIP Servers use. Consult the TSCP release note for information about changes to the Common Part that might affect the functionality of SIP Server.

This is a hot fix for this product. This release does not contain new features or functionality.

Corrections and Modifications

This release includes the following corrections and modifications:


When operating in HA mode, if the TApplyTreatment request for a music treatment is initiated with the duration parameter set to the maximum negative value (-2147483648), SIP Server no longer terminates unexpectedly while synchronizing treatment attributes with the backup server. Now, when the duration parameter contains a negative value, SIP Server returns an EventError message (Invalid attribute). (SIP-22669)


Top of Page


Release Number 8.1.102.79 [08/01/17] – Hot Fix

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 release of SIP Server is built with T-Server Common Part (TSCP) release number 8.1.011.07. TSCP is the shared software that all T-Servers and SIP Servers use. Consult the TSCP release note for information about changes to the Common Part that might affect the functionality of SIP Server.

This is a hot fix for this product. This release contains the following new features or functionality:

Corrections and Modifications

This release includes the following corrections and modifications:


When dn-scope is set to office, SIP Server no longer terminates unexpectedly while clearing the call after tromboning. (SIP-22597)


When sip-enable-moh is set to true and record is set to true, SIP Server now correctly handles a TReleaseCall request issued during TAlternateCall request processing. Previously, SIP Server did not properly process a race-condition scenario, when a TReleaseCall request was issued in the middle of the media services connection. (SIP-22590)


When a call is waiting to be routed, if sip-enable-call-info is set to true, sip-server-inter-trunk is set to true, and ringing-on-route-point is set to false, SIP Server no longer sends NOTIFY with call information. SIP Server continues sending NOTIFY after the call is connected as usual. Previously in this scenario, immediately after the INVITE message for ISCC RouteCall, SIP Server sent NOTIFY with call information, which was rejected by the second SIP Server with the 481 error message that led to the failed call. (SIP-22577)


Top of Page


Release Number 8.1.102.78 [07/25/17] – Hot Fix

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 release of SIP Server is built with T-Server Common Part (TSCP) release number 8.1.011.07. TSCP is the shared software that all T-Servers and SIP Servers use. Consult the TSCP release note for information about changes to the Common Part that might affect the functionality of SIP Server.

This is a hot fix for this product. This release does not contain new features or functionality.

Corrections and Modifications

This release includes the following corrections and modifications:


In a multi-site Complete Transfer scenario with a call recording in progress, SIP Server no longer drops the call at the moment of the transfer completion. Previously in this scenario, because of the race condition between SIP and ISCC messages, SIP Server sometimes dropped the call. This issue occurred when the record-moh option was set to false. (SIP-22546)


Top of Page


Release Number 8.1.102.77 [07/14/17] – Hot Fix

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 release of SIP Server is built with T-Server Common Part (TSCP) release number 8.1.011.07. TSCP is the shared software that all T-Servers and SIP Servers use. Consult the TSCP release note for information about changes to the Common Part that might affect the functionality of SIP Server.

This is a hot fix for this product. This release does not contain new features or functionality.

Corrections and Modifications

This release includes the following corrections and modifications:


When an agent first sends the presence NOTIFY message with status Busy, and then changes the status to Ready, by sending another presence NOTIFY message during the After Call Work (ACW) time period, SIP Server now saves the latest state and updates the state after the ACW timer expires. Previously, SIP Server ignored the agent state update that was requested during ACW. (SIP-22437)


Top of Page


Release Number 8.1.102.73 [06/21/17] – 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 release of SIP Server is built with T-Server Common Part (TSCP) release number 8.1.011.07. TSCP is the shared software that all T-Servers and SIP Servers use. Consult the TSCP release note for information about changes to the Common Part that might affect the functionality of SIP Server.

There are no restrictions for this release. This release contains the following new features or functionality:

Corrections and Modifications

This release does not include other corrections.

Top of Page


Release Number 8.1.102.72 [06/12/17] – Hot Fix

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 release of SIP Server is built with T-Server Common Part (TSCP) release number 8.1.011.06. TSCP is the shared software that all T-Servers and SIP Servers use. Consult the TSCP release note for information about changes to the Common Part that might affect the functionality of SIP Server.

This is a hot fix for this product. This release does not contain new features or functionality.

Corrections and Modifications

This release includes the following corrections and modifications:


SIP Server is built with TSCP version 8.1.011.06 that corrects reporting AttributeCtrlParty in EventCallDeleted. Previously, the order of notifications and sending events was incorrect; as a result, AttributeCtrlParty was not included in EventCallDeleted. (SIP-22365)


Top of Page


Release Number 8.1.102.71 [06/06/17] – Hot Fix

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 release of SIP Server is built with T-Server Common Part (TSCP) release number 8.1.011.04. TSCP is the shared software that all T-Servers and SIP Servers use. Consult the TSCP release note for information about changes to the Common Part that might affect the functionality of SIP Server.

This is a hot fix for this product. This release contains the following new features or functionality:

Corrections and Modifications

This release does not include other corrections.

Top of Page


Release Number 8.1.102.70 [05/30/17] – Hot Fix

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 release of SIP Server is built with T-Server Common Part (TSCP) release number 8.1.011.04. TSCP is the shared software that all T-Servers and SIP Servers use. Consult the TSCP release note for information about changes to the Common Part that might affect the functionality of SIP Server.

This is a hot fix for this product. This release does not contain new features or functionality.

Corrections and Modifications

This release includes the following corrections and modifications:


When running in multi-threaded mode (sip-link-type=3) and if one of the SIP Server threads takes more than 15 seconds to start, SIP Server now correctly loads the DN configuration. Previously in this scenario, SIP Server did not load the DN configuration properly; as a result, calls to those DNs were rejected. (SIP-22027)


Top of Page


Release Number 8.1.102.69 [05/23/17] – Hot Fix

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 release of SIP Server is built with T-Server Common Part (TSCP) release number 8.1.011.04. TSCP is the shared software that all T-Servers and SIP Servers use. Consult the TSCP release note for information about changes to the Common Part that might affect the functionality of SIP Server.

This is a hot fix for this product. This release does not contain new features or functionality.

Corrections and Modifications

This release includes the following corrections and modifications:


SIP Server now specifies a value for the cnonce parameter in the Authorization header that is sent in the REGISTER message, if SIP Server receives the qop directive in the WWW-Authenticate header field. Previously, SIP Server sent the cnonce parameter with an empty string. (SIP-22325)


When SIP Server receives an UPDATE message (with no SDP) after sending a reliable 183 response and before receiving a PRACK message, SIP Server now responds with a 2xx message to the UPDATE message. Previously, SIP Server did not respond to this UPDATE message. (SIP-22242)


When a single-step transfer is initiated and SIP Server receives an XS response from SIP Feature Server, and if the hostname is missing in the URI of the device, SIP Server now adds a host name to the To header in the outgoing INVITE message. (SIP-22156)


SIP Server now properly clears internal storage entries related to a Routing Point when a call is diverted from the Routing Point by issuing a TSingleStepTransfer request to an external number. Previously, when some entries were not cleared, it resulted in a TRouteCall request failure when the same properties were reused in new calls. (SIP-22081)


If the divert-on-ringing option is set to false and a TRouteCall request contains the NO_ANSWER_OVERFLOW AttributeExtension with the location specified in the format <routepoint>@<hostname> and a call is rerouted two times after the no-answer timer expires, when the call is rerouted the third time, the call is now queued in the overflow destination and the call flow continues normally. Previously in this scenario, the call became stuck.

Note: The configuration described in the above scenario is not recommended. To use No-Answer Supervision when the divert-on-ringing configuration option is set to false, the values of any no-answer-overflow options (extn-no-answer-overflow, agent-no-answer-overflow, posn-no-answer-overflow, or no-answer-overflow) or the NO_ANSWER_OVERFLOW AttributeExtension must not be set (they must be empty). (SIP-21998)


Top of Page


Release Number 8.1.102.68 [05/16/17] – Hot Fix

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 release of SIP Server is built with T-Server Common Part (TSCP) release number 8.1.011.04. TSCP is the shared software that all T-Servers and SIP Servers use. Consult the TSCP release note for information about changes to the Common Part that might affect the functionality of SIP Server.

This is a hot fix for this product. This release contains the following new features or functionality:

Corrections and Modifications

This release includes the following corrections and modifications:


SIP Server is built with TSCP version 8.1.011.04 that corrects handling of requests when two different T-Library clients send RequestGetAccessNumber with the same Reference ID for different calls. (TS-11398, SIP-22129)


SIP Server no longer terminates unexpectedly while processing a wrongly-formatted message that is passed to the management port. SIP Server now ignores such management messages that are sent with a wrong format. (SIP-22077)


The silent setup for SIP Server now works correctly on Linux platforms. Previously, the silent setup installation might fail with an error stating that the data entered for the host name was invalid, even though the host name did not contain any invalid characters. (SIP-22331)


Top of Page


Release Number 8.1.102.67 [05/05/17] – Hot Fix

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 release of SIP Server is built with T-Server Common Part (TSCP) release number 8.1.011.02. TSCP is the shared software that all T-Servers and SIP Servers use. Consult the TSCP release note for information about changes to the Common Part that might affect the functionality of SIP Server.

This is a hot fix for this product. This release contains the following new features or functionality:

Corrections and Modifications

This release includes the following corrections and modifications:


SIP Server no longer applies the dial-plan rule parameter onbusy to members of the Hunt Group. Previously, when a call destination was the sequential Hunt Group, the onbusy parameter was set, and a Hunt Group member declined the call, SIP Server incorrectly applied the dial-plan rule, and the call was sent to the onbusy destination instead of the next Hunt Group member. (SIP-22235)


When the sip-enable-two-party-mute option is set to true, SIP Server now correctly reconnects a party to the call that was put on hold by TListenDisconnected by a conference member, who then left the conference, leaving only two conference parties on the call. (SIP-22152)


Top of Page


Release Number 8.1.102.65 [04/28/17] – Hot Fix

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 release of SIP Server is built with T-Server Common Part (TSCP) release number 8.1.011.02. TSCP is the shared software that all T-Servers and SIP Servers use. Consult the TSCP release note for information about changes to the Common Part that might affect the functionality of SIP Server.

This is a hot fix for this product. This release does not contain new features or functionality.

Corrections and Modifications

This release includes the following corrections and modifications:


When the userdata-map-format option is set to sip-headers-encoded on a VOIP Service DN, SIP Server encodes the user data values that are passed in SIP Headers of the SIP INFO request sent to MCP, but not the user data passed in gvp:params. Previously, SIP Server encoded the user data values passed in gvp:params which was not processed by MCP. (SIP-22112)


Top of Page


Release Number 8.1.102.64 [04/25/17] – Hot Fix

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 release of SIP Server is built with T-Server Common Part (TSCP) release number 8.1.011.02. TSCP is the shared software that all T-Servers and SIP Servers use. Consult the TSCP release note for information about changes to the Common Part that might affect the functionality of SIP Server.

This is a hot fix for this product. This release does not contain new features or functionality.

Corrections and Modifications

This release includes the following corrections and modifications:


SIP Server now correctly clears the call on a DN if the DN is set to out of service by the timeout while the initiated call from this DN is not answered yet. Previously, the SIP dialog on the DN was stuck, and if the reject-call-incall option was set to true, no calls were distributed to this DN after it came back in service. (SIP-22065)


SIP Server no longer grows in memory while processing a GVP subscription on a voicemail VoIP Service DN. Previously, SIP Server did not delete the subscription dialog after unsubscribe, which led to accumulating undeleted dialogs and, as result, to memory growth. (SIP-22033)


Top of Page


Release Number 8.1.102.62 [04/18/17] – Hot Fix

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 release of SIP Server is built with T-Server Common Part (TSCP) release number 8.1.011.02. TSCP is the shared software that all T-Servers and SIP Servers use. Consult the TSCP release note for information about changes to the Common Part that might affect the functionality of SIP Server.

This is a hot fix for this product. This release does not contain new features or functionality.

Corrections and Modifications

This release includes the following corrections and modifications:


SIP Server now encodes both the header name and its value when the userdata-map-format option is set to sip-headers-encoded. Previously, SIP Server encoded only the header value when this option was configured. (SIP-22047)


In a multi-site routing scenario with the extended dial plan provided by SIP Feature Server, if the override-to-on-divert option is set to true, SIP Server now correctly sets the username of the To header as the destination DN in the INVITE message sent to the agent. Previously in this scenario, SIP Server set the username to Anonymous. (SIP-21959)


Top of Page


Release Number 8.1.102.61 [04/11/17] – Hot Fix

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 release of SIP Server is built with T-Server Common Part (TSCP) release number 8.1.011.02. TSCP is the shared software that all T-Servers and SIP Servers use. Consult the TSCP release note for information about changes to the Common Part that might affect the functionality of SIP Server.

This is a hot fix for this product. This release contains the following new features or functionality:

Corrections and Modifications

This release does not include other corrections.

Top of Page


Release Number 8.1.102.60 [03/24/17] – Hot Fix

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 release of SIP Server is built with T-Server Common Part (TSCP) release number 8.1.011.02. TSCP is the shared software that all T-Servers and SIP Servers use. Consult the TSCP release note for information about changes to the Common Part that might affect the functionality of SIP Server.

This is a hot fix for this product. This release does not contain new features or functionality.

Corrections and Modifications

This release includes the following corrections and modifications:


SIP Server now correctly handles a 100 Trying response to a re-INVITE request for the nailed-up agent connection if the event-ringing-on-100trying option is set to true on the agent’s DN. Previously, SIP Server did not process the 100 Trying response correctly, which resulted in a 500 Server Internal Error response. (SIP-21909)


SIP Server now correctly starts the OOS check for existing transports after a switchover. Previously, when transports specified by the FQDN in the contact were newly added or re-configured right before a switchover, SIP Server started the OOS check of those transports without the proper delay, which triggered the oos-force timer for those transports not yet started. (SIP-21846)


Top of Page


Release Number 8.1.102.59 [03/07/17] – Hot Fix

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 release of SIP Server is built with T-Server Common Part (TSCP) release number 8.1.010.94. TSCP is the shared software that all T-Servers and SIP Servers use. Consult the TSCP release note for information about changes to the Common Part that might affect the functionality of SIP Server.

This is a hot fix for this product. This release contains the following new features or functionality:

Corrections and Modifications

This release includes no corrections.

Top of Page


Release Number 8.1.102.58 [02/21/17] – Hot Fix

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 release of SIP Server is built with T-Server Common Part (TSCP) release number 8.1.010.94. TSCP is the shared software that all T-Servers and SIP Servers use. Consult the TSCP release note for information about changes to the Common Part that might affect the functionality of SIP Server.

This is a hot fix for this product. This release contains the following new features or functionality:

Corrections and Modifications

This release includes the following corrections and modifications:


When the after-call-divert-destination option is configured and an agent releases the call after a switchover, SIP Server now correctly diverts a call to the configured DN. Previously, SIP Server did not properly synchronize the value of the after-call-divert-destination option with the backup SIP Server, as the result, after the switchover, SIP Server did not divert the call to the configured DN. (SIP-21865)


Top of Page


Release Number 8.1.102.57 [02/07/17] – Hot Fix

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 release of SIP Server is built with T-Server Common Part (TSCP) release number 8.1.010.94. TSCP is the shared software that all T-Servers and SIP Servers use. Consult the TSCP release note for information about changes to the Common Part that might affect the functionality of SIP Server.

This is a hot fix for this product. This release does not contain new features or functionality.

Corrections and Modifications

This release includes the following corrections and modifications:


When the disable-media-before-greeting option is set to true, and an agent makes a consultation call and alternates the call before the consultation call is established, resulting in the main call being retrieved and the consultation call being put in the held state with music-on-hold (MOH) treatment. Now, when the consultation call is established, SIP Server plays the configured greeting and does not retrieve the consultation call. Previously, SIP Server retrieved the consultation call by terminating the MOH treatment, which resulted in two active calls for the agent.

When disable-media-before-greeting is set to true and greeting-call-type-filter is set to consult/internal/outbound, SIP Server now disables the media only if a greeting must be played to the call according to the greeting-call-type-filter option setting. Previously, SIP Server disabled the media even though a greeting was not to be played for the call. (SIP-21506)


Top of Page


Release Number 8.1.102.56 [01/24/17] – Hot Fix

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 release of SIP Server is built with T-Server Common Part (TSCP) release number 8.1.010.94. TSCP is the shared software that all T-Servers and SIP Servers use. Consult the TSCP release note for information about changes to the Common Part that might affect the functionality of SIP Server.

This is a hot fix for this product. This release does not contain new features or functionality.

Corrections and Modifications

This release includes the following corrections and modifications:


When SIP Server receives a NOTIFY request indicating that a Media Server that started recording is out of service and that a call with recording is placed on hold, SIP Server now correctly connects an alternative Media Server to the call to continue recording. Previously in this scenario, no alternative Media Server was connected and recording stopped. (SIP-21683)


In a standalone deployment with more than 10,000 DNs configured with the use-register-for-service-state option set to true or in a Business Continuity deployment with more than 10,000 DNs, SIP Server's transition to the Primary role is optimized to not exceed a few hundred milliseconds. Previously in these configurations, SIP Server's unresponsiveness for five or more seconds during the transition to the Primary role sometimes triggered the reconnection procedure for T-Library clients. (SIP-21558)


Top of Page


Release Number 8.1.102.55 [12/28/16] – Hot Fix

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 release of SIP Server is built with T-Server Common Part (TSCP) release number 8.1.010.94. TSCP is the shared software that all T-Servers and SIP Servers use. Consult the TSCP release note for information about changes to the Common Part that might affect the functionality of SIP Server.

This is a hot fix for this product. This release contains the following new features or functionality:

Corrections and Modifications

This release includes the following corrections and modifications:


If the sip-enable-sdp-codec-filter option is set to true and the audio-codecs option is configured on the inbound Trunk DN, SIP Server now correctly provides codec filtering for inbound calls. Previously, SIP Server filtered only codecs configured at an Application level. (SIP-21624)


If a Voice over IP Service device goes out of service and then back in service, the backup SIP Server no longer attempts to re-activate GVP subscription. Previously, SIP Server, while in backup mode, tried to select an active transport for future subscription, which led to repetitive log messages. (SIP-21492)


Top of Page


Release Number 8.1.102.54 [12/16/16] – 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 release of SIP Server is built with T-Server Common Part (TSCP) release number 8.1.010.94. TSCP is the shared software that all T-Servers and SIP Servers use. Consult the TSCP release note for information about changes to the Common Part that might affect the functionality of SIP Server.

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

Corrections and Modifications

This release includes the following corrections and modifications:


SIP Server no longer terminates unexpectedly while processing TApplyTreatment requests containing Reference ID with more than 9 decimal digits. This issue occurred only on the Solaris operating system. (SIP-21592)


When an agent issues a second TSingleStepConference request to a Routing Point after the first request is routed to an external destination, SIP Server now correctly adds AttributeCallState as 2 (CallStateConferenced) in the EventPartyAdded message. Previously in this scenario, SIP Server added AttributeCallState as 0 (CallStateOk) in the EventPartyAdded message. (SIP-21513)


When the divert-on-ringing option is set to false, and an agent issues a TSingleStepConference request to a Routing Point, SIP Server now correctly terminates an external call leg if a TDeleteFromConference request is issued on that Routing Point. Previously in this scenario, SIP Server did not terminate that call leg if the TDeleteFromConference request was issued before the external number, to which the call was routed, answered the call. (SIP-21484)


Top of Page


Release Number 8.1.102.53 [12/02/16] – Hot Fix

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 release of SIP Server is built with T-Server Common Part (TSCP) release number 8.1.010.94. TSCP is the shared software that all T-Servers and SIP Servers use. Consult the TSCP release note for information about changes to the Common Part that might affect the functionality of SIP Server.

This is a hot fix for this product. This release contains the following new features or functionality:

Corrections and Modifications

This release includes the following corrections and modifications:


SIP Server no longer adds mailbox info to the From header in INVITE messages that it sends in routing scenarios triggered by a TRouteCall request containing the gvm_mailbox extension key. Previously, SIP Server incorrectly added the data to the From header, which led to an incorrect identification of the voice mail originator. (SIP-21502)


If, during a 1pcc single-step transfer, a destination responds with a 407 Proxy Authentication Required message, SIP Server now sends a NOTIFY message only when the authorization negotiation is completed. Previously in this scenario, SIP Server sent a NOTIFY message to the transferee with the 407 response included in the message body, which resulted in a dropped call. (SIP-21481)


When the TCP is configured between SIP Server and SIP Proxy, SIP Server now selects the correct SIP Proxy that is in the service state to send a re-INVITE message. Previously, if one SIP Proxy was out of service, SIP Server sometimes incorrectly selected that out-of-service SIP Proxy. (SIP-21403)


Top of Page


Release Number 8.1.102.52 [11/18/16] – Hot Fix

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 release of SIP Server is built with T-Server Common Part (TSCP) release number 8.1.010.94. TSCP is the shared software that all T-Servers and SIP Servers use. Consult the TSCP release note for information about changes to the Common Part that might affect the functionality of SIP Server.

This is a hot fix for this product. This release does not contain new features or functionality.

Corrections and Modifications

This release includes the following corrections and modifications:


SIP Server now rejects TCompleteTransfer or TCompleteConference requests with EventError when a preview interaction is in progress for any of the consultation call parties. Previously, when SIP Server received TCompleteTransfer, the call was established with the consultation call destination, even though the preview interaction was in progress on the destination, and as a result, SIP Server terminated unexpectedly when the preview interaction timer expired after the transfer was completed. (SIP-21445)


Top of Page


Release Number 8.1.102.51 [11/15/16] – Hot Fix

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 release of SIP Server is built with T-Server Common Part (TSCP) release number 8.1.010.94. TSCP is the shared software that all T-Servers and SIP Servers use. Consult the TSCP release note for information about changes to the Common Part that might affect the functionality of SIP Server.

This is a hot fix for this product. This release contains the following new features or functionality:

Corrections and Modifications

This release includes the following corrections and modifications:


When SIP Server is configured for Active Out-of-Service Detection, and during OPTIONS/200 OK exchange messages the time is shifted backward for some reason, a SIP Server switchover no longer occurs. Previously in this scenario, SIP Server reported the SelfMonitoring: SIP traffic timeout detected message according to timestamp calculations that led to a SIP Server switchover. (SIP-21181)


Top of Page


Release Number 8.1.102.50 [11/09/16] – Hot Fix

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 release of SIP Server is built with T-Server Common Part (TSCP) release number 8.1.010.94. TSCP is the shared software that all T-Servers and SIP Servers use. Consult the TSCP release note for information about changes to the Common Part that might affect the functionality of SIP Server.

This is a hot fix for this product. This release contains the following new features or functionality:

Corrections and Modifications

This release includes the following corrections and modifications:


SIP Server now correctly sends re-SUBSCRIBE messages to DNs located behind the softswitch after the second switchover. Previously, after the second switchover, SIP Server, running again in the Primary mode, sometimes did not send re-SUBSCRIBE messages to DNs located behind the softswitch. (SIP-21279)


If a trunk DN subscribed to presence goes out of service, SIP Server now selects the backup contact specified in the contacts-backup option on that trunk DN and sends a SUBSCRIBE message to the backup contact. Previously, when the subscription expired, SIP Server incorrectly sent the SUBSCRIBE message to the out-of-service trunk DN. (SIP-21271)


SIP Server now parks an agent with the nailed-up connection with Media Server even though it receives an unexpected UPDATE request (without the SDP, and between 18x and 200 OK messages) from an agent leg. Previously in this scenario, the nailed-up connection was not established. (SIP-21120)


Top of Page


Release Number 8.1.102.49 [10/31/16] – Hot Fix

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 release of SIP Server is built with T-Server Common Part (TSCP) release number 8.1.010.94. TSCP is the shared software that all T-Servers and SIP Servers use. Consult the TSCP release note for information about changes to the Common Part that might affect the functionality of SIP Server.

This is a hot fix for this product. This release contains the following new features or functionality:

Corrections and Modifications

This release includes the following corrections and modifications:


When establishing a nailed-up connection with an agent (connect-nailedup-on-login=gcti::park), SIP Server now includes in the Contact header the username part of the From header when sending an INVITE message to the agent. Previously, SIP Server included gcti::park as the username part in the Contact header, which resulted in rejection of the INVITE message. (SIP-21251)


SIP Server can now use the following new option, sip-allow-update-method, to include UPDATE request support in the Allow header of 200 OK and ACK messages in scenarios in which the UPDATE request is used for non-SDP updates. Previously, SIP Server did not include UPDATE request support in 200 OK and ACK messages, which forced some SIP endpoints to use the re-INVITE method for non-SDP updates as well.

sip-allow-update-method
Section: TServer, Application level
Default Value: false
Valid Value: true, false
Changes Take Effect: Immediately

When set to true, SIP Server includes the UPDATE method in the Allow header of 200 OK and ACK messages.

(SIP-21238)


In an early media scenario, SIP Server now ignores the 100 Trying response received on an UPDATE request and waits for a final response to the UPDATE request. Previously, SIP Server considered 100 Trying as the final response and sent an ACK message to the peer party, which resulted in the established dialog instead of remaining in the early media state. (SIP-21285)


SIP Server no longer terminates unexpectedly if the trunk configuration update occurred when Operational Statistics is outlined for the same trunk to the log file or for the HTTP statistics response, or if the in-service status of the trunk was changed when Operational Statistics outlined for this trunk. (SIP-21230)


Top of Page


Release Number 8.1.102.46 [10/14/16] – Hot Fix

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 release of SIP Server is built with T-Server Common Part (TSCP) release number 8.1.010.94. TSCP is the shared software that all T-Servers and SIP Servers use. Consult the TSCP release note for information about changes to the Common Part that might affect the functionality of SIP Server.

This is a hot fix for this product. This release does not contain new features or functionality.

Corrections and Modifications

This release includes the following corrections and modifications:


This release contains modifications to support only Genesys Cloud implementations. (SIP-21261)


Top of Page


Release Number 8.1.102.45 [10/11/16] – Hot Fix

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 release of SIP Server is built with T-Server Common Part (TSCP) release number 8.1.010.94. TSCP is the shared software that all T-Servers and SIP Servers use. Consult the TSCP release note for information about changes to the Common Part that might affect the functionality of SIP Server.

This is a hot fix for this product. This release does not contain new features or functionality.

Corrections and Modifications

This release includes the following corrections and modifications:


This release contains modifications to support only Genesys Cloud implementations. (SIP-21253, SIP-2095)


Top of Page


Release Number 8.1.102.43 [09/27/16] – Hot Fix

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 release of SIP Server is built with T-Server Common Part (TSCP) release number 8.1.010.89. TSCP is the shared software that all T-Servers and SIP Servers use. Consult the TSCP release note for information about changes to the Common Part that might affect the functionality of SIP Server.

This is a hot fix for this product. This release contains the following new features or functionality:

Corrections and Modifications

This release does not include any corrections.

Top of Page


Release Number 8.1.102.42 [09/20/16] – Hot Fix

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 release of SIP Server is built with T-Server Common Part (TSCP) release number 8.1.010.89. TSCP is the shared software that all T-Servers and SIP Servers use. Consult the TSCP release note for information about changes to the Common Part that might affect the functionality of SIP Server.

This is a hot fix for this product. This release contains the following new features or functionality:

Corrections and Modifications

This release includes the following corrections and modifications:


SIP Server no longer initiates unnecessary recording while establishing a nailed-up connection when an agent logs in in accordance with the connect-nailedup-on-login option setting. Previously, if an agent DN was configured with the record option set to true, recording was started when the nailed-up connection was being established. (SIP-21091)


Top of Page


Release Number 8.1.102.41 [09/14/16] – Hot Fix

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 release of SIP Server is built with T-Server Common Part (TSCP) release number 8.1.010.89. TSCP is the shared software that all T-Servers and SIP Servers use. Consult the TSCP release note for information about changes to the Common Part that might affect the functionality of SIP Server.

This is a hot fix for this product. This release contains the following new features or functionality:

Corrections and Modifications

This release includes the following corrections and modifications:


If the after-call-divert-destination option setting instructs SIP Server to divert a call to a Routing Point for a survey after an interaction with an agent ends, SIP Server now properly releases the call when the survey ends. Previously in this scenario, SIP Server did not release the call. (SIP-21122)


SIP Server now correctly plays the ring tone via Media Server when the sip-ring-tone-mode option is set to 1, and the first-received 180 Ringing message from a called party is without the SDP. Previously in this scenario, when SIP Server was establishing a dialog with Media Server, another 180 Ringing message with the SDP arrived from the called party, and SIP Server erroneously started connecting an agent to the second audio dialog, which resulted in no audio for the agent. (SIP-21057)


When an agent with the same login credentials tries to log in from two different phones (each phone sends a SUBSCRIBE message), SIP Server now rejects the second login attempt by sending a NOTIFY message with AgentLoggedOffEvent in the message body. The 3pcc RequestAgentLogin is rejected by the EventError message. Previously in this scenario, SIP Server did not reject the second login with the same agent credentials. (SIP-18710)


Top of Page


Release Number 8.1.102.40 [09/06/16] – Hot Fix

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 release of SIP Server is built with T-Server Common Part (TSCP) release number 8.1.010.89. TSCP is the shared software that all T-Servers and SIP Servers use. Consult the TSCP release note for information about changes to the Common Part that might affect the functionality of SIP Server.

This is a hot fix for this product. This release does not contain new features or functionality.

Corrections and Modifications

This release includes the following corrections and modifications:


In a supervision call with the agent scope, when a monitored agent transfers the call to a Routing Point, followed by a treatment application and routing to a new agent, and when the sip-treatments-continuous option was set to true, SIP Server now correctly connects the caller with the new agent. Previously in this scenario, SIP Server did not connect the caller with the agent, which resulted in no audio between them. (SIP-20890)


SIP Server no longer grows in memory while merging main and consultation calls initiated on different SIP Server sites.

A new Application-level configuration option, stale-call-tout, is introduced in the extrouter section.

stale-call-tout
Section: extrouter
Default Value: 0 (zero)
Valid Values: 0, and from 1 min to 24 hr. See the “Timeout Value Format” in the SIP Server Deployment Guide.
For example: stale-call-tout = 5 min
Changes Take Effect: After SIP Server restart

Specifies the time interval that SIP Server waits for a call to be updated from its last update. After this time elapses, if no new events about the call are received, SIP Server clears this call as a stale transit ISCC call by deleting the call information from memory unconditionally. The default value of 0 disables the stale calls cleanup. (SIP-19620)


Top of Page


Release Number 8.1.102.39 [08/29/16] – Hot Fix

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 release of SIP Server is built with T-Server Common Part (TSCP) release number 8.1.010.89. TSCP is the shared software that all T-Servers and SIP Servers use. Consult the TSCP release note for information about changes to the Common Part that might affect the functionality of SIP Server.

This is a hot fix for this product. This release contains the following new features or functionality:

Corrections and Modifications

This release includes the following corrections and modifications:


SIP Server now correctly processes voicemail messages when both group and personal voicemail boxes are configured in SIP Feature Server. Previously, a group voicemail box message was not played if a personal voicemail box was configured. (SIP-20982)


Top of Page


Release Number 8.1.102.38 [08/23/16] – Hot Fix

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 release of SIP Server is built with T-Server Common Part (TSCP) release number 8.1.010.89. TSCP is the shared software that all T-Servers and SIP Servers use. Consult the TSCP release note for information about changes to the Common Part that might affect the functionality of SIP Server.

This is a hot fix for this product. This release contains the following new features or functionality:

Corrections and Modifications

This release includes the following corrections and modifications:


SIP Server now correctly generates log event 52053 to indicate alternate routing when URS becomes non-operational or unresponsive. Previously in this scenario, SIP Server did not generate that log event. (SIP-20902)


SIP Server now recovers recording correctly in the scenario when INFO for the end of the greeting is received when the recording of the call is in process of starting. Previously, in this race-condition scenario, SIP Server terminated the call. (SIP-20813)


Top of Page


Release Number 8.1.102.36 [08/12/16] – Hot Fix

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 release of SIP Server is built with T-Server Common Part (TSCP) release number 8.1.010.89. TSCP is the shared software that all T-Servers and SIP Servers use. Consult the TSCP release note for information about changes to the Common Part that might affect the functionality of SIP Server.

This is a hot fix for this product. This release contains the following new features or functionality:

Corrections and Modifications

This release includes the following corrections and modifications:


SIP Server now includes the Max-Forwards header with a predefined value set to 70 when sending the SUBSCRIBE message to Resource Manager. Previously, when SIP Server did not include that header, a third-party load balancer located between SIP Server and Resource Manager rejected that SUBSCRIBE with the "400 Missing Max-Forwards header field" error message. (SIP-20930)


The backup SIP Server now shuts down immediately when processing the Graceful Shutdown command and will not forcefully log agents out. Previously, when graceful shutdown was issued to the backup SIP Server, it waited for all calls to complete before shutting down; it also logged agents out. (SIP-20843)


If a caller disconnects from the call while a TCompleteConference request issued by an agent is in progress, SIP Server now terminates the main call and clears all associations between main and consultation calls after the consultation call is released. Previously in this scenario, some call associations became stuck, which resulted in a rejected call to that agent because the reject-call-incall option was set to true. (SIP-20797)


Top of Page


Release Number 8.1.102.35 [08/08/16] – Hot Fix

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 release of SIP Server is built with T-Server Common Part (TSCP) release number 8.1.010.89. TSCP is the shared software that all T-Servers and SIP Servers use. Consult the TSCP release note for information about changes to the Common Part that might affect the functionality of SIP Server.

This is a hot fix for this product. This release does not contain new features or functionality.

Corrections and Modifications

This release includes the following corrections and modifications:


When an agent disconnects from the call and the caller is routed to a post-call survey and then disconnects during the survey, SIP Server now reports AttributeCtrlParty in EventCallPartyDeleted as an agent DN, because the agent disconnected first. Previously, if a caller disconnected during a post-call survey, SIP Server reported AttributeCtrlParty as the caller DN. (SIP-20835)


SIP Server no longer terminates unexpectedly when an agent transfers a call using a MuteTransfer to an external party but the caller disconnects before a provisional response is received from that external party. (SIP-20819)


Top of Page


Release Number 8.1.102.34 [08/02/16] – Hot Fix

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 release of SIP Server is built with T-Server Common Part (TSCP) release number 8.1.010.89. TSCP is the shared software that all T-Servers and SIP Servers use. Consult the TSCP release note for information about changes to the Common Part that might affect the functionality of SIP Server.

This is a hot fix for this product. This release contains the following new features or functionality:

Corrections and Modifications

This release includes the following corrections and modifications:


When an agent logs into a DN located behind the softswitch and recording is enabled (record=true) for the agent in the corresponding Agent Login object, SIP Server starts recording whenever a call is established with that agent. Previously in this scenario, SIP Server did not start recording. (SIP-20877)


When running in multi-threaded mode, in a No-Answer Supervision scenario, when the divert-on-ringing configuration option is set to false, SIP Server now correctly processes the new TRouteCall request after the previous TRouteRequest was responded to with an EventError message because the after-routing-timeout expired. Previously, because of a race condition, SIP Server did not process the second TRouteCall and sent EventError for all consecutive requests. (SIP-20815)


In a No-Answer Supervision scenario, when agent-no-answer-timeout expires, but an agent answers the call while waiting for a SIP Feature Server dial plan response on a redirection request, SIP Server now sends the call to the redirect destination and releases the agent from the call. Previously, SIP Server established the call with the agent, and also sent the call to the redirect destination, which resulted in termination of the call. (SIP-20734)


Top of Page


Release Number 8.1.102.33 [07/26/16] – Hot Fix

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 release of SIP Server is built with T-Server Common Part (TSCP) release number 8.1.010.89. TSCP is the shared software that all T-Servers and SIP Servers use. Consult the TSCP release note for information about changes to the Common Part that might affect the functionality of SIP Server.

This is a hot fix for this product. This release contains the following new features or functionality:

Corrections and Modifications

This release includes the following corrections and modifications:


SIP Server no longer terminates unexpectedly and now sends a 488 Not Acceptable Here message when it receives a REFER with Replaces request while processing the previous INVITE with Replaces request. (SIP-20805)


SIP Server now correctly handles removal of the DN-level sip-cti-control option set to dtmf. Previously, SIP Server incorrectly applied the value of the removed option. (SIP-20707)


Top of Page


Release Number 8.1.102.32 [07/19/16] – Hot Fix

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 release of SIP Server is built with T-Server Common Part (TSCP) release number 8.1.010.87. TSCP is the shared software that all T-Servers and SIP Servers use. Consult the TSCP release note for information about changes to the Common Part that might affect the functionality of SIP Server.

This is a hot fix for this product. This release does not contain new features or functionality.

Corrections and Modifications

This release includes the following corrections and modifications:


Starting with version 8.1.102.32, the modifications SIP-19469, SIP-19718, and SIP-20208 made in previous versions have been removed and are no longer available.


SIP Server can now resolve a DNS SRV record of the Trunk Group DN contact to an IP address, regardless of the number of Trunk Group DNs configured in the Configuration Database. Previously, if there were more than 256 of these DNs configured in the Configuration Database, SIP Server sometimes did not resolve the DN contact correctly. (SIP-20795)


SIP Server now correctly handles re-INVITE messages containing multiple disabled "m=" lines (0 port) in the SDP, which arrived while SIP Server was processing the previous transaction. Previously, during the SDP negotiation, SIP Server sometimes sent a SIP 503 error message instead of the re-INVITE with the SDP. (SIP-20750)


SIP Server no longer adds the ReasonCode, previously set by an agent, in EventAgentNotReady distributed on a TAgentLogin request that is submitted without any ReasonCode in it. Previously, starting with version 8.1.102.22 (correction of SIP-20410), when an agent logged out, SIP Server added the previously used ReasonCode in EventAgentLogout and EventAgentNotReady after the agent re-logged in. (SIP-20718)


Top of Page


Release Number 8.1.102.31 [07/08/16] – Hot Fix

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 release of SIP Server is built with T-Server Common Part (TSCP) release number 8.1.010.87. TSCP is the shared software that all T-Servers and SIP Servers use. Consult the TSCP release note for information about changes to the Common Part that might affect the functionality of SIP Server.

This is a hot fix for this product. This release contains the following new features or functionality:

Corrections and Modifications

This release includes the following corrections and modifications:


In multi-threaded mode, in a monitored call with the agent scope and recording enabled on all parties, when the monitored agent completes the transfer and leaves the call, SIP Server now starts recording the remaining parties of the call. Previously, SIP Server did not start recording after the transfer completion. (SIP-20620)


SIP Server is built with the latest TSCP, which corrects the following issue:

SIP Server now correctly processes suspended events in scenarios where the epp-tout option is set to a non-zero value if other suspended events are present on the same party. SIP Server reports the correct AttributePreviousConnID in EventPartyChanged on multisite transfer completions. (TS-11165, SIP-20546)


SIP Server now correctly processes a call after receiving a 400 Bad Request response to a REFER request. Previously, SIP Server did not process the call correctly when multiple TRouteCall requests were sent and a response to the REFER message was received after the after-routing-timeout timer was started, which resulted in a stuck call. (SIP-20526)


When a single-step transfer to a Routing Point fails, SIP Server now deletes this party. When the same Routing Point is used in the call again, SIP Server now handles it correctly. Previously, when a TRouteCall request was received from URS for the same Routing Point later in the call, SIP Server generated an Invalid Attribute error. (SIP-20517)


Top of Page


Release Number 8.1.102.29 [06/28/16] – Hot Fix

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 release of SIP Server is built with T-Server Common Part (TSCP) release number 8.1.010.85. TSCP is the shared software that all T-Servers and SIP Servers use. Consult the TSCP release note for information about changes to the Common Part that might affect the functionality of SIP Server.

This is a hot fix for this product. This release contains the following new features or functionality:

Corrections and Modifications

This release includes the following corrections and modifications:


When the sip-error-overflow option is configured and an agent rejects the call, SIP Server queues the call back to a Routing Point; and when a treatment is applied on that Routing Point, the caller will be able to hear the treatment. Previously in this scenario, the caller did not hear the treatment if the disable-media-before-greeting option was set to true. (SIP-20616)


SIP Server now starts other scheduled services, such as supervision, when a customer greeting is successfully established, but the agent greeting is failed because of the MSML error response received from Media Server. Previously in this scenario, SIP Server did not start other scheduled services. (SIP-20437)


When conference and recording are serviced by the same MCP and it is detected as out of service, SIP Server tries to recover conference and recording. Even if SIP Server receives an error response from an active (running) Media Server (or the timeout expires, or there is no response to INFO) during a service recovery provided by this Media Server, SIP Server is now able to clear the recorder reservation correctly and route the next call to the same DN. Previously in this scenario, SIP Server did not clear the recording from the DN and new calls were rejected for this DN. (SIP-20122)


Top of Page


Release Number 8.1.102.28 [06/22/16] – 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 release of SIP Server is built with T-Server Common Part (TSCP) release number 8.1.010.85. TSCP is the shared software that all T-Servers and SIP Servers use. Consult the TSCP release note for information about changes to the Common Part that might affect the functionality of SIP Server.

There are no restrictions for this release. This release contains the following new features or functionality:

Corrections and Modifications

This release includes the following corrections and modifications:


When the default-route-point option is set to reject=<SIP ERROR> and the default-route-point-order option is set to after-dial-plan, SIP Server no longer applies the default-route-point option setting for the call if a dial plan fits the original target and the modified target, after the dial plan was applied, matches an internal resource, and SIP Server sends the call to that resource. Previously in this scenario, when SIP Server applied the default-route-point option setting, it resulted in EventError and left the call stuck. (SIP-20672)


Top of Page


Release Number 8.1.102.27 [06/14/16] – Hot Fix

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 release of SIP Server is built with T-Server Common Part (TSCP) release number 8.1.010.85. TSCP is the shared software that all T-Servers and SIP Servers use. Consult the TSCP release note for information about changes to the Common Part that might affect the functionality of SIP Server.

This is a hot fix for this product. This release does not contain new features or functionality.

Corrections and Modifications

This release includes the following corrections and modifications:


When the MCP fails to play a treatment and an RM fails, and a SIP Server switchover occurs during the treatment recovery procedure, the new primary SIP Server now completes the treatment recovery procedure without delay, sending the re-INVITE message to the in-service RM right after the time period, configured in options oos-check and oos-force, expires. Previously in this scenario, SIP Server delayed sending re-INVITE for the treatment after its switchover. (SIP-20589)


After establishing an inbound call to IVR (GVP) and recording for this call is started as configured, if SIP Server receives an INFO message from the IVR while recording is in progress, it will process this INFO message properly. SIP Server updates the party data accordingly and sends the 200 OK in response. Previously, SIP Server rejected this INFO with a 488 error response. (SIP-20579)


SIP Server no longer terminates unexpectedly while processing an INVITE message received with a malformed Request-URI, for example, containing ‘( ‘ brackets in the DN number. (SIP-20527)


While running in backup mode, SIP Server no longer changes the media service to the out-of-service state because of DNS resolution failure. Previously, the backup SIP Server changed the media service to the out-of-service state, which made the SIP Server HA pair out of sync, which in turn resulted in stuck calls in the backup SIP Server. (SIP-20518)


Top of Page


Release Number 8.1.102.26 [06/07/16] – Hot Fix

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 release of SIP Server is built with T-Server Common Part (TSCP) release number 8.1.010.85. TSCP is the shared software that all T-Servers and SIP Servers use. Consult the TSCP release note for information about changes to the Common Part that might affect the functionality of SIP Server.

This is a hot fix for this product. This release contains the following new features or functionality:

Corrections and Modifications

This release includes the following corrections and modifications:


A call is now properly returned to the Routing Point and EventError is issued in the following scenario:

In the case of a TRedirectCall scenario, the call is sent to a new destination without returning to the Routing Point. The following new option is introduced to control the behavior for the continuous treatment.

sip-continue-treatment-on-call-reject
Section: [TServer]
Default Value: false
Valid Values: true, false
Changes Take Effect: Immediately

When the option is set to true (the recommended setting), the continuous treatment that is already applied is not interrupted in both scenarios above. When the option is set to false (the default setting to ensure backward compatibility), the continuous treatment is terminated in the scenarios above as soon as TReleaseCall or TRedirectCall is received.

(SIP-20557)


In cases where a dial plan is created with some invalid rules, SIP Server now ignores invalid dial plan rules and creates a dial plan with valid rules. Previously, if the last dial-plan-rule was invalid, SIP Server did not ignore it, and as a result, did not use the dial plan. (SIP-20519)


When in response to the INFO message generated by the TSendDTMF request, the re-INVITE message comes before 200 OK, SIP Server now schedules the processing of the re-INVITE and processes correctly TSendDTMF. Previously in this scenario, the re-INVITE was lost and was not passed to other leg. (SIP-20428)


Top of Page


Release Number 8.1.102.25 [05/24/16] – Hot Fix

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 release of SIP Server is built with T-Server Common Part (TSCP) release number 8.1.010.85. TSCP is the shared software that all T-Servers and SIP Servers use. Consult the TSCP release note for information about changes to the Common Part that might affect the functionality of SIP Server.

This is a hot fix for this product. This release contains the following new features or functionality:

Corrections and Modifications

This release includes the following corrections and modifications:


SIP Server no longer terminates unexpectedly while processing a Media Server failure for recording in scenarios with single-dialog devices. (SIP-20493)


SIP Server no longer terminates unexpectedly while releasing a call with recording after a 1pcc single-step transfer if a transferred DN was moved to the out-of-service state during the call. (SIP-20426)


Top of Page


Release Number 8.1.102.23 [05/10/16] – Hot Fix

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 release of SIP Server is built with T-Server Common Part (TSCP) release number 8.1.010.85. TSCP is the shared software that all T-Servers and SIP Servers use. Consult the TSCP release note for information about changes to the Common Part that might affect the functionality of SIP Server.

This is a hot fix for this product. This release does not contain new features or functionality.

Corrections and Modifications

This release includes the following corrections and modifications:


This release contains modifications to support Genesys Cloud implementations only. (SIP-20512)


Top of Page


Release Number 8.1.102.22 [05/03/16] – Hot Fix

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 release of SIP Server is built with T-Server Common Part (TSCP) release number 8.1.010.84. TSCP is the shared software that all T-Servers and SIP Servers use. Consult the TSCP release note for information about changes to the Common Part that might affect the functionality of SIP Server.

This is a hot fix for this product. This release contains the following new features or functionality:

Corrections and Modifications

This release includes the following corrections and modifications:


On receiving re-subscription from an IP phone, SIP Server now properly synchronizes the Not Ready Reason code between the IP phone and the agent desktop. Previously, SIP Server did not add the Reason code for re-subscription, which made the IP phone and the desktop out of sync. (SIP-20410)


When an agent is logged out during the preview interaction timeout, SIP Server now keeps the agent in the logged out state. Previously in this scenario, SIP Server sometimes set that agent back into the logged in and NotReady state; after that it was not possible to set the agent into the Ready state. This issue occurred when the Application option forced-notready was set to true (the default). (SIP-20395)


In Business Continuity deployments, SIP Server now sends EventAddressInfo with the correct AttributeReferenceID and the agent state to the SIP Feature Server request TQueryAddress and SIP Feature Server generates dial-plan rules accordingly. Previously, SIP Server did not include AttributeReferenceID in EventAddressInfo when sending it to SIP Feature Server, which led to a timeout exception in SIP Feature Server. (SIP-20367)


When recording and treatment are being applied to a conference call and SIP Server routes the call to an agent who does not answer and the agent that initiated the conference, which was recorded, leaves the call, SIP Server now correctly re-routes the call to deposit a voicemail. Previously in this scenario, the TRouteCall request to the Media Server containing record and gvm_mailbox AtrributeExtentions was rejected with an error, because of the absence of the recorded party. (SIP-20290)


In a deployment with multiple Media Servers and the Active-Active RM pair configuration, when all RMs go down and then come back in service during a SIP Server switchover, SIP Server now correctly sets the RM DN that has oos-error-check set to true in the in-service state after the second switchover. Previously, SIP Server sometimes did not set the DN in the in-service state after it received the positive response for the OPTIONS request. (SIP-20104)


Top of Page


Release Number 8.1.102.20 [04/26/16] – Hot Fix

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 release of SIP Server is built with T-Server Common Part (TSCP) release number 8.1.010.83. TSCP is the shared software that all T-Servers and SIP Servers use. Consult the TSCP release note for information about changes to the Common Part that might affect the functionality of SIP Server.

This is a hot fix for this product. This release contains the following new features or functionality:

Corrections and Modifications

This release includes the following corrections and modifications:


In a multi-site deployment, when a re-INVITE message for the hold contains an SDP with several "m=" lines, and a second re-INVITE for a music-on-hold SDP contains several "m=" lines (one of which is inactive), SIP Server now processes those re-INVITEs correctly and a music-on-hold treatment is played to the call on hold. Previously, in cases when the sip-hold-rfc3264 option was set to false, SIP Server took into account rejected media streams as the hold SDP, which resulted in a failed music-on-hold treatment. (SIP-20208)

Note: Starting with version 8.1.102.32, this modification is no longer available as it did not function as expected.


Top of Page


Release Number 8.1.102.19 [04/15/16] – Hot Fix

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 release of SIP Server is built with T-Server Common Part (TSCP) release number 8.1.010.83. TSCP is the shared software that all T-Servers and SIP Servers use. Consult the TSCP release note for information about changes to the Common Part that might affect the functionality of SIP Server.

This is a hot fix for this product. This release does not contain new features or functionality.

Corrections and Modifications

This release includes the following corrections and modifications:


This release contains corrections to support Genesys Cloud implementations only. (SIP-20419)


Top of Page


Release Number 8.1.102.18 [04/12/16] – Hot Fix

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 release of SIP Server is built with T-Server Common Part (TSCP) release number 8.1.010.82. TSCP is the shared software that all T-Servers and SIP Servers use. Consult the TSCP release note for information about changes to the Common Part that might affect the functionality of SIP Server.

This is a hot fix for this product. This release contains the following new features or functionality:

Corrections and Modifications

This release contains corrections to support Genesys Cloud implementations only. (SIP-20330, SIP-20139)

Top of Page


Release Number 8.1.102.14 [04/05/16] – Hot Fix

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 release of SIP Server is built with T-Server Common Part (TSCP) release number 8.1.010.79. TSCP is the shared software that all T-Servers and SIP Servers use. Consult the TSCP release note for information about changes to the Common Part that might affect the functionality of SIP Server.

This is a hot fix for this product. This release does not contain new features or functionality.

Corrections and Modifications

This release includes the following corrections and modifications:


If the no-answer action is set to notready for an agent, SIP Server can now process or ignore presence SIP messages to change an agent state to Ready, depending on a new ignore-presence-after-nas option setting. Previously, if the no-answer action is set to notready for an agent, SIP Server ignored presence SIP message and did not change the agent state.

If the no-answer action is set to none for an agent, SIP Server can now process presence SIP messages to change an agent state regardless of the ignore-presence-after-nas option value. Previously, if the no-answer action is set to none for an agent, SIP Server ignored presence SIP message and did not change the agent state.

ignore-presence-after-nas
Section: TServer, Application and DN levels
Default Value: true
Valid Values: true, false
Changes Take Effect: At the next call

If set to true, SIP Server ignores presence SIP messages if the no-answer action is set to notready.
If set to false, SIP Server processes presence SIP messages if the no-answer action is set to notready.

(SIP-20238)


SIP Server now correctly clears the call on a DN in scenarios in which a TInitiateTransfer request from a DN is in progress and SIP Server receives another T-Library request for that DN. Previously, a SIP dialog remained stuck and SIP Server rejected a new call to the same DN, in accordance with the reject-call-incall=true setting. (SIP-20153)


In this scenario:

When the call is merged, then the consultation call recording will be stopped at both sites and restarted for only the main call at both sites. Previously in this scenario, SIP Server restarted the recording at the origination site and the recording was not restarted or resumed at the destination site when the call was merged. For this functionality, sip-server-inter-trunk must be set to true on a trunk between SIP Servers. (SIP-20190)


Top of Page


Release Number 8.1.102.13 [03/29/16] – Hot Fix

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 release of SIP Server is built with T-Server Common Part (TSCP) release number 8.1.010.79. TSCP is the shared software that all T-Servers and SIP Servers use. Consult the TSCP release note for information about changes to the Common Part that might affect the functionality of SIP Server.

This is a hot fix for this product. This release contains the following new features or functionality:

Corrections and Modifications

This release includes the following corrections and modifications:


SIP Server now displays the number of logged on agents statistic correctly. Previously, the number of logged on agents statistic sometimes incremented (decremented) multiple times when TAgentLogin (TAgentLogout) were sent for the same DN. As a result, statistics displayed wrong values. (SIP-20269)


Top of Page


Release Number 8.1.102.11 [03/18/16] – Hot Fix

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 release of SIP Server is built with T-Server Common Part (TSCP) release number 8.1.010.79. TSCP is the shared software that all T-Servers and SIP Servers use. Consult the TSCP release note for information about changes to the Common Part that might affect the functionality of SIP Server.

This is a hot fix for this product. This release does not contain new features or functionality.

Corrections and Modifications

This release includes the following corrections and modifications:


In a Business Continuity deployment, when a multi-site call is routed to a DR peer based on external dial-plan rules, SIP Server now correctly forwards the call to a voicemail if no agent is logged in to both sites. Previously, SIP Server dropped the call without forwarding it to a voicemail which resulted in a loop where the call was sent to DR peers repeatedly. (SIP-20178)


Top of Page


Release Number 8.1.102.10 [03/15/16] – Hot Fix

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 release of SIP Server is built with T-Server Common Part (TSCP) release number 8.1.010.77. TSCP is the shared software that all T-Servers and SIP Servers use. Consult the TSCP release note for information about changes to the Common Part that might affect the functionality of SIP Server.

This is a hot fix for this product. This release does not contain new features or functionality.

Corrections and Modifications

This release includes the following corrections and modifications:


When a 3pcc call is established after receiving an unreliable provisional response from an agent, SIP Server now correctly increments the SDP version number in the re-INVITE message sent to the caller. Previously, SIP Server did not increment the version number in the re-INVITE, which resulted in no voice path between the caller and the agent. (SIP-20103)


In a scenario in which:

  1. A main call is established between a caller and an Agent1.
  2. Agent1 makes a consultation call to Agent2.
  3. Recording is enabled for both Agents.
  4. SIP Server processes the conference completion.
If the Complete Conference fails for Agent2, SIP Server now generates EventReleased and BYE for Agent2. Previously, SIP Server generated only EventReleased and did not send BYE to Agent2. (SIP-20060)


When conference, treatment, and recording services are provided by different Media Servers, and if any Media Server is detected as out of service, SIP Server now recovers only media services provided by that failed Media Server. Previously in this scenario, SIP Server did not recover services properly, which led to an error response issued by an active (running) Media Server. See also known issue SIP-20122. (SIP-19968)


SIP Server now correctly synchronizes registration information after its role has been changed from backup to primary. Previously, in a race-condition scenario with two consecutive switchovers, registration information was not synchronized correctly. (SIP-19787)


Top of Page


Release Number 8.1.102.09 [03/08/16] – Hot Fix

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 release of SIP Server is built with T-Server Common Part (TSCP) release number 8.1.010.77. TSCP is the shared software that all T-Servers and SIP Servers use. Consult the TSCP release note for information about changes to the Common Part that might affect the functionality of SIP Server.

This is a hot fix for this product. This release contains the following new features or functionality:

Corrections and Modifications

This release includes the following corrections and modifications:


For configurations in which SIP Feature Server dial plans are applied to destinations, SIP Server now correctly applies the replace-prefix option value, configured on a trunk, and will use the new value when creating the Refer-To header. Previously, SIP Server did not replace the prefix and used the received user part in the Refer-to header. (SIP-20154)


When a consultation call with activated recording and treatment is routed from a Routing Point to an agent who does not answer, and the conference is completed while the call is still on the Routing Point, and the call is re-routed to a voicemail, SIP Server now correctly includes the agent’s mailbox ID for depositing a voicemail. Previously, SIP Server sent the mailbox ID as none in the INVITE message to the voicemail DN. (SIP-20117)


SIP Server no longer terminates unexpectedly while handling SIP responses that were received over reliable protocols. (SIP-20066)


In a multi-site call, when the monitored agent leaves the call and if there is more than one active party identified at another site using the LCTParty list (the Providing Call Participant Info feature is activated), SIP Server now preserves a supervisor (in mute or coach supervision mode) in the call. Previously, SIP Server removed the supervisor from the call when the monitored agent left the call, without considering the two active parties remaining at another site. (SIP-16373)


It is now possible to make a call to an extension DN with the reject-call-incall=true setting after a switchover. Previously, the DN became stuck when TListenDisconnect was issued, causing the call to be rejected because of the reject-call-incall=true setting. (SIP-20023)


Top of Page


Release Number 8.1.102.08 [02/23/16] – Hot Fix

Supported Operating Systems
New in This Release
Corrections and Modifications

This hot fix is no longer available as it did not function as expected. If you downloaded it, do not install it. Hot fix version 8.1.102.09 corrects the identified issue.

Top of Page


Release Number 8.1.102.06 [02/12/16] – Hot Fix

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 release of SIP Server is built with T-Server Common Part (TSCP) release number 8.1.010.70. TSCP is the shared software that all T-Servers and SIP Servers use. Consult the TSCP release note for information about changes to the Common Part that might affect the functionality of SIP Server.

This is a hot fix for this product. This release contains the following new features or functionality:

Corrections and Modifications

This release includes the following corrections and modifications:


SIP Server no longer terminates unexpectedly when a DN, which is already in a conference, issues a single-step conference request to an external party and releases the call before receiving a provisional response from that external party. (SIP-20025)


Top of Page


Release Number 8.1.102.05 [02/08/16] – Hot Fix

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 release of SIP Server is built with T-Server Common Part (TSCP) release number 8.1.010.70. TSCP is the shared software that all T-Servers and SIP Servers use. Consult the TSCP release note for information about changes to the Common Part that might affect the functionality of SIP Server.

This is a hot fix for this product. This release contains the following new features or functionality:

Corrections and Modifications

This release includes the following corrections and modifications:


In a multi-site deployment, when a re-INVITE (for example, for a greeting) is received from another site in the middle of the blind transfer completion, SIP Server now processes the transfer properly and completes it successfully. Previously in this scenario, SIP Server generated EventError in response to that re-INVITE. (SIP-19874)


Top of Page


Release Number 8.1.102.04 [01/26/16] – Hot Fix

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 release of SIP Server is built with T-Server Common Part (TSCP) release number 8.1.010.70. TSCP is the shared software that all T-Servers and SIP Servers use. Consult the TSCP release note for information about changes to the Common Part that might affect the functionality of SIP Server.

This is a hot fix for this product. This release does not contain new features or functionality.

Corrections and Modifications

This release includes the following corrections and modifications:


In a Business Continuity deployment, while operating in DR mode, SIP Server now properly updates the state of the Extension DN as back-in-service (EventDNBackInService) if a contact of that DN is changed back to the correct contact value. Previously in this scenario, SIP Server did not update the DN state that remained in out-of-service state. (SIP-19821)


When a party is removed from the conference call, SIP Server no longer generates EventPartyDeleted with incorrect ThirdPartyDN attributes referring to a party that never joined the call. Previously, SIP Server incorrectly included a supervisor DN (who never joined the call) in attributes ThirdPartyDN and ThirdPartyRole as RoleObserver of EventPartyDeleted. (SIP-19813)


In a deployment with multiple Media Servers and the Active-Active RM pair configuration, when an outbound call is initiated, SIP Server now correctly selects a VOIP service in a round-robin fashion. Previously, SIP Server incorrectly selected only one VOIP service. (SIP-19665)


SIP Server now correctly sends the INVITE to the MSML VOIP DN that matches the call by geo-location. Previously, in deployments with Voice Treatment Ports devices configured with the contact = "::msml", SIP Server sometimes sent it to a MSML VOIP DN that did not match the call by geo-location. (SIP-20245)


Top of Page


Release Number 8.1.102.02 [01/19/16] – Hot Fix

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 release of SIP Server is built with T-Server Common Part (TSCP) release number 8.1.010.70. TSCP is the shared software that all T-Servers and SIP Servers use. Consult the TSCP release note for information about changes to the Common Part that might affect the functionality of SIP Server.

This is a hot fix for this product. This release contains the following new features or functionality:

Corrections and Modifications

This release includes the following corrections and modifications:


Because SIP Server does not support UPDATE requests for established dialogs, the Allow header of 200 OK and ACK messages that are sent in response to an INVITE request no longer includes the UPDATE request in the list of allowed requests. Previously, when SIP Server included the UPDATE request in the Allow header list of those messages, it caused some SIP endpoints to send an unsupported UPDATE for established dialogs. (SIP-19797)


While a recording stop operation is in progress and SIP Server receives any T-Library request for the same call, it will now queue that request and execute it even though an ongoing operation is canceled. Previously, in some race conditions, SIP Server did not execute the queued request when the ongoing operation was canceled which might lead, for example, to a call not being routed. (SIP-19764)


SIP Server now correctly processes an asynchronous INFO message with content-type = application/x-www-form-urlencoded and attaches the UserData received in the message to the call. Previously, SIP Server ignored UserData received in such an asynchronous INFO message. (SIP-19731)


Top of Page


Release Number 8.1.102.01 [12/29/15] – Hot Fix

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 release of SIP Server is built with T-Server Common Part (TSCP) release number 8.1.010.70. TSCP is the shared software that all T-Servers and SIP Servers use. Consult the TSCP release note for information about changes to the Common Part that might affect the functionality of SIP Server.

This is a hot fix for this product. This release contains the following new features or functionality:

Corrections and Modifications

This release does not include any corrections.

Top of Page


Release Number 8.1.102.00 [12/18/15] – Hot Fix

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 release of SIP Server is built with T-Server Common Part (TSCP) release number 8.1.010.70. TSCP is the shared software that all T-Servers and SIP Servers use. Consult the TSCP release note for information about changes to the Common Part that might affect the functionality of SIP Server.

This is a hot fix for this product. This release contains the following new features or functionality:

Corrections and Modifications

This release includes the following corrections and modifications:


SIP Server no longer distributes the second EventAgentLogout following agent's desktop disconnection (the logout-on-disconnect option was set to true) if the first EventAgentLogout was already distributed for the out-of-service DN (the logout-on-out-of-service was set to true). Previously in this scenario, SIP Server distributed two EventAgentLogout messages. (SIP-19675)


SIP Server no longer generates a NOTIFY message with a negative CSeq value as a result of a local counter overflow. (SIP-19652)


Top of Page


Release Number 8.1.101.98 [12/11/15] – 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 release of SIP Server is built with T-Server Common Part (TSCP) release number 8.1.010.70. TSCP is the shared software that all T-Servers and SIP Servers use. Consult the TSCP release note for information about changes to the Common Part that might affect the functionality of SIP Server.

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

Corrections and Modifications

This release includes the following corrections and modifications:


If the Application-level option sip-save-rejected-sdp is set to true, SIP Server does not include the rejected SDP stream from the last known SDP on one endpoint while generating an SDP answer to another endpoint. Previously, SIP Server tried to include the rejected SDP stream, which resulted in an incorrect SDP answer with double "m=" lines. (SIP-19718)

Note: Starting with version 8.1.102.32, this modification is no longer available as it did not function as expected.


Top of Page


Release Number 8.1.101.97 [12/08/15] – Hot Fix

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 release of SIP Server is built with T-Server Common Part (TSCP) release number 8.1.010.70. TSCP is the shared software that all T-Servers and SIP Servers use. Consult the TSCP release note for information about changes to the Common Part that might affect the functionality of SIP Server.

This is a hot fix for this product. This release contains the following new features or functionality:

Corrections and Modifications

This release includes the following corrections and modifications:


When the msml-support configuration option is set to true, SIP Server now correctly generates EventHeld in response to a THoldCall request for a chat call. Previously, SIP Server generated EventError. (SIP-19619)


When dialing the Shared Line or routing, transferring, or conferencing a call to the Shared Line, SIP Server now plays a ringback to a caller, if it is configured. Previously, SIP Server did not connect the caller to the media service, and as a result no ringback was played. (SIP-19526)


SIP Server now properly processes TCancelReqGetAccessNumber requests. Previously, SIP Server rejected those requests with the error: Bad or missing transaction specific data. (SIP-19775)


Top of Page


Release Number 8.1.101.95 [11/24/15] – Hot Fix

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 release of SIP Server is built with T-Server Common Part (TSCP) release number 8.1.010.67. TSCP is the shared software that all T-Servers and SIP Servers use. Consult the TSCP release note for information about changes to the Common Part that might affect the functionality of SIP Server.

This is a hot fix for this product. This release contains the following new features or functionality:

Corrections and Modifications

This release also includes the following corrections and modifications:


In a Business Continuity deployment, where the dr-forward option is set to no-agent, when a call arrives at a DR peer site as a result of the DR forwarding procedure and a destination DN is out of service, SIP Server now correctly applies the onnotreg dial-plan parameter. Previously in this scenario, SIP Server did not apply the onnotreg dial-plan parameter and dropped the call with the 603 Decline error message. (SIP-19613)


SIP Server no longer duplicates the P-Access-Network-Info header in an outgoing SIP message. Previously, in some scenarios, if SIP Server received several messages with P-Access-Network-Info headers during one call, it included several P-Access-Network-Info headers in the outgoing message to the caller. (SIP-19582)


Top of Page


Release Number 8.1.101.94 [11/17/15] – Hot Fix

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 release of SIP Server is built with T-Server Common Part (TSCP) release number 8.1.010.67. TSCP is the shared software that all T-Servers and SIP Servers use. Consult the TSCP release note for information about changes to the Common Part that might affect the functionality of SIP Server.

This is a hot fix for this product. This release contains the following new features or functionality:

Corrections and Modifications

This release does not include other corrections and modifications.

Top of Page


Release Number 8.1.101.93 [11/10/15] – Hot Fix

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 release of SIP Server is built with T-Server Common Part (TSCP) release number 8.1.010.67. TSCP is the shared software that all T-Servers and SIP Servers use. Consult the TSCP release note for information about changes to the Common Part that might affect the functionality of SIP Server.

This is a hot fix for this product. This release contains the following new features or functionality:

Corrections and Modifications

This release includes the following corrections and modifications:


SIP Server no longer terminates unexpectedly while processing a misconfigured dial-plan rule and entering into a loop. (SIP-19496)


SIP Server supports a new Application-level option:

sip-save-rejected-sdp
Section: TServer
Default Value: false
Valid Values: true, false
Changes Take Effect: For the next call

When set to true, if a media stream is rejected in the SDP answer (by setting the corresponding port to zero), SIP Server saves its state and uses it as is (with the zero port) in subsequent modifications of the same SDP session, in accordance with RFC 3264.

The default value of false is required to preserve the original SIP Server behavior and provide backward compatibility. In this case, SIP Server ignores the media stream rejection and tries to find a matching SDP media stream, which might result in duplicated media streams in the SDP. (SIP-19469)

Note: Starting with version 8.1.102.32, this modification is no longer available as it did not function as expected.


SIP Server now executes scheduled re-INVITEs even when a greeting or recording service fails. Previously, in a multi-site deployment, and because of a race condition, SIP Server canceled scheduled re-INVITEs when a greeting or recording failed, which resulted in one way audio. (SIP-19453)


SIP Server now correctly plays a greeting for the agent that is defined in the TRouteCall request if the previous routing failed. Previously, SIP Server did not play a greeting in this scenario, even if it was defined in AttributeExtensions of TRouteCall sent to the agent DN. (SIP-19445)


Top of Page


Release Number 8.1.101.92 [11/03/15] – Hot Fix

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 release of SIP Server is built with T-Server Common Part (TSCP) release number 8.1.010.67. TSCP is the shared software that all T-Servers and SIP Servers use. Consult the TSCP release note for information about changes to the Common Part that might affect the functionality of SIP Server.

This is a hot fix for this product. This release contains the following new features or functionality:

Corrections and Modifications

This release includes the following corrections and modifications:


If a call is made to an incorrectly configured sequential Hunt Group (no Hunt Group members were specified), SIP Server now correctly distributes the call to a default DN if one is configured, or drops the call. Previously in this scenario, SIP Server terminated unexpectedly. (SIP-19556)


When SIP Server receives a re-INVITE in the middle of the Music-On-Hold (MOH) recovery and the MOH recovery fails, SIP Server now re-invites the caller and agent and processes further requests for this call. Previously in this scenario, SIP Server did not process further requests for the call. (SIP-19522)


SIP Server no longer generates an EventNetworkCallStatus message when there is no Network Attended Transfer/Conference in place. Previously in this scenario, SIP Server sometimes generated an EventNetworkCallStatus message. (SIP-19511)


SIP Server running in the HA backup mode now correctly releases the DN reservation while deleting a stuck SIP call. Previously, when resolving a complex scenario with a broken connection to the Media Server, the backup SIP Server did not release the DN reservation. As a result, after the SIP Server switchover, the new primary SIP Server rejected a new call to the same DN. The issue occurred when the DN-level option reject-call-incall was set to true. (SIP-19467)


Top of Page


Release Number 8.1.101.91 [10/27/15] – Hot Fix

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 release of SIP Server is built with T-Server Common Part (TSCP) release number 8.1.010.67. TSCP is the shared software that all T-Servers and SIP Servers use. Consult the TSCP release note for information about changes to the Common Part that might affect the functionality of SIP Server.

This is a hot fix for this product. This release does not contain new features or functionality.

Corrections and Modifications

This release includes the following corrections and modifications:


SIP Server no longer removes capacity and capacity-group configuration options from the DN configuration when a new DN is created in the configuration environment. Previously, after more than 100 modifications (such as enabling, disabling, creating, and deleting DNs), SIP Server sometimes removed capacity and capacity-group from the existing configured DNs when a new DN was created. (SIP-19494)


When the info-pass-through option is configured, SIP Server now correctly passes the INFO message to the inbound call leg. Previously, when SIP Server was waiting for a 200 OK message in response to INFO that was sent to GVP, and received the INFO from GVP before the 200 OK arrived, SIP Server sometimes did not pass the INFO to the inbound call leg. (SIP-19486)


Top of Page


Release Number 8.1.101.90 [10/14/15] – Hot Fix

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 release of SIP Server is built with T-Server Common Part (TSCP) release number 8.1.010.67. TSCP is the shared software that all T-Servers and SIP Servers use. Consult the TSCP release note for information about changes to the Common Part that might affect the functionality of SIP Server.

This is a hot fix for this product. This release does not contain new features or functionality.

Corrections and Modifications

This release includes the following corrections and modifications:


SIP Server can now correctly process called numbers containing special characters. Previously, SIP Server rejected the outbound call request that contained a called number started with an open parenthesis "(". (SIP-19402)


Top of Page


Release Number 8.1.101.88 [10/05/15] – Hot Fix

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 release of SIP Server is built with T-Server Common Part (TSCP) release number 8.1.010.67. TSCP is the shared software that all T-Servers and SIP Servers use. Consult the TSCP release note for information about changes to the Common Part that might affect the functionality of SIP Server.

This is a hot fix for this product. This release contains the following new features or functionality:

Corrections and Modifications

This release does not contain other corrections or modifications.

Top of Page


Release Number 8.1.101.87 [09/29/15] – Hot Fix

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 release of SIP Server is built with T-Server Common Part (TSCP) release number 8.1.010.67. TSCP is the shared software that all T-Servers and SIP Servers use. Consult the TSCP release note for information about changes to the Common Part that might affect the functionality of SIP Server.

This is a hot fix for this product. This release contains the following new features or functionality:

Corrections and Modifications

This release includes the following corrections and modifications:


In Business Continuity deployments, when a call arrives to a SIP endpoint which was not registered and the Dial-Plan Rule with the onnotreg parameter was configured with the destination as a voicemail (onnotreg=gcti::voicemail), SIP Server now correctly delivers the call (with the appropriate SIP headers) to the voicemail server. Previously in this scenario, SIP Server delivered the call without the voicemail parameters, and as a result, the voicemail server did not correctly process the call. (SIP-19392)


In an Active-Active Resource Manager (RM) deployment with SIP Proxy, when an RM goes out of service in the middle of the call, SIP Server now correctly updates the Route header with the active RM contact, so the media service request is processed successfully. Previously, when one of the RMs went out of service, SIP Server did not update the Route header and the media service request was not processed.

The new DN-level configuration option sip-route-active-transport must be set to true on all DNs that are configured to point to the RM pair:

sip-route-active-transport
Section: TServer
Default Value: false
Valid Values: true, false
Changes Take Effect: For the next call

When set to true, SIP Server updates the Route header with the active RM contact. (SIP-18870)


Top of Page


Release Number 8.1.101.86 [09/22/15] – Hot Fix

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 release of SIP Server is built with T-Server Common Part (TSCP) release number 8.1.010.67. TSCP is the shared software that all T-Servers and SIP Servers use. Consult the TSCP release note for information about changes to the Common Part that might affect the functionality of SIP Server.

This is a hot fix for this product. This release includes the following new features or functionality:

Corrections and Modifications

This release includes the following corrections and modifications:


SIP Server now correctly performs active Out Of Service detection of the Trunk DN if its contact is configured as an IPv6 address. Previously, SIP Server did not recognize the IPv6 address in the Trunk DN contact of Resource Manager, and as a result, no connection to Resource Manager was established. (SIP-19350)


SIP Server supports a new Application-level configuration option:

greeting-stops-no-answer-timeout
Section: TServer
Default Value: false
Valid Values: true, false
Changes Take Effect: For the next call

Set this option to true in environments where both No-Answer Supervision and Personal Greeting functionality are configured. In this case, SIP Server stops the no-answer timer as soon as a 200 OK SIP response is received, indicating that the destination party has answered the call. SIP Server does not apply the no-answer action and no-answer overflow to the call even if they are configured in the corresponding options.

The default value of false is required to preserve the original SIP Server behavior and provide backward compatibility. In this case, SIP Server does not stop the no-answer timer until EventEstablished is generated for the destination party. It might cause SIP Server to release the call on an agent DN in the middle of the greeting if greeting-delay-events is set to true. EventEstablished on the agent DN is generated only when the greeting is finished. (SIP-19345)


During TMakePredictiveCall processing, if re-INVITE is received from a called party when Call Progress Analysis (CPA) is in progress, SIP Server now correctly sends re-INVITE messages to the call parties after the CPA timeout expires. Previously in this scenario, SIP Server did not send re-INVITE messages, which resulted in the wrong SDP negotiation. (SIP-19330)


If the conditional dial plan is applied, SIP Server now preserves originally dialed digits (the original-dialplan-digits extension key) in T-Events for the new destination if another dial plan was not applied to the new destination. Previously, SIP Server did not include originally dialed digits in T-Events for the new destination. For backward compatibility, set the restricted Application-level option preserve-original-dialplan-digits to false. (SIP-19327)


Top of Page


Release Number 8.1.101.85 [09/16/15] – Hot Fix

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 release of SIP Server is built with T-Server Common Part (TSCP) release number 8.1.010.67. TSCP is the shared software that all T-Servers and SIP Servers use. Consult the TSCP release note for information about changes to the Common Part that might affect the functionality of SIP Server.

This is a hot fix for this product. This release contains the following new features or functionality:

Corrections and Modifications

This release includes the following corrections and modifications:


SIP Server is built with TSCP version 8.1.010.67 that corrects the excessive memory consumption in SIP Server. The issue occurred in the environment where contact FQDN resolution for multiple trunks was configured in the local hosts file. (SIP-19085)


SIP Server now correctly sets the agent's Not Ready state to After Call Work (ACW) when it receives the corresponding SUBSCRIBE message while the agent was in the Not Ready state. Previously, when the ACW button was pressed on the AudioCodes 420HD phone, SIP Server did not change the agent state to ACW. (SIP-19288)


Top of Page


Release Number 8.1.101.83 [09/09/15] – Hot Fix

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 release of SIP Server is built with T-Server Common Part (TSCP) release number 8.1.010.66. TSCP is the shared software that all T-Servers and SIP Servers use. Consult the TSCP release note for information about changes to the Common Part that might affect the functionality of SIP Server.

This is a hot fix for this product. This release contains the following new features or functionality:

Corrections and Modifications

This release includes the following corrections and modifications:


In scenarios where the main call recording is not started and a consultation call is recorded, invoking Complete Transfer/Conference triggers SIP Server to restart the recording with the correct metadata and recording file name after the transfer/conference is completed. As a result, the new recording associated with the main call is created. Previously, SIP Server did not restart the recording when the main and consultation calls were merged after transfer/conference completion, and the main call was recorded in the same audio file as the consultation call. (SIP-14514)


Top of Page


Release Number 8.1.101.81 [09/01/15] – Hot Fix

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 release of SIP Server is built with T-Server Common Part (TSCP) release number 8.1.010.66. TSCP is the shared software that all T-Servers and SIP Servers use. Consult the TSCP release note for information about changes to the Common Part that might affect the functionality of SIP Server.

This is a hot fix for this product. This release does not contain new features or functionality.

Corrections and Modifications

This release includes the following corrections and modifications:


In a multi-site environment, when a consultation call has two parties on site A, but ISCC signaling is tromboned through site B, an update of UserData no longer causes an unexpected release of the ISCC connection to site B. Previously, this condition prevented distribution of the required EventPartyChanged on the transfer completion. (SIP-19299)


An active VSP call list is no longer corrupted on the backup T-Server when a connection to the primary T-Server is lost and recovered. (SIP-19240)


When the greeting-after-merge option is set to false, SIP Server no longer incorrectly applies a greeting to a call that is established after a blind transfer completion. Previously, SIP Server ignored this option while processing blind transfers. (SIP-19225)


In multi-site environments with three SIP Server sites involved in a call, when the first 302 redirection response is arrived without a provisional 18x response, and while processing a subsequent 302 redirection response, SIP Server no longer generates an incorrect EventPartyAdded message for a transferred call. (SIP-19199)


Top of Page


Release Number 8.1.101.79 [08/18/15] – Hot Fix

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 release of SIP Server is built with T-Server Common Part (TSCP) release number 8.1.010.64. TSCP is the shared software that all T-Servers and SIP Servers use. Consult the TSCP release note for information about changes to the Common Part that might affect the functionality of SIP Server.

This is a hot fix for this product. This release does not contain new features or functionality.

Corrections and Modifications

This release includes the following corrections and modifications:


SIP Server now correctly continues to distribute new calls to the Hunt Group in the following scenario: a call arrives at the Hunt Group in which one or more members are busy with other calls; idle members do not answer the call within the hg-noanswer-timeout interval, and busy members do not free themselves up within the hg-queue-timeout interval; and the call is finally distributed to the default DN. Previously in this scenario, SIP Server stopped distributing new calls to the Hunt Group. (SIP-19270)


SIP Server now correctly distributes the call to Hunt Group 2 in the following scenario: a call is distributed to Hunt Group 1 and, declined by all members of that Hunt Group, it is redirected to the default DN (which was Hunt Group 2, and also contained some members of Hunt Group 1). Previously in this scenario, SIP Server did not distribute the call to Hunt Group 2. (SIP-19136)


When a main call is reconnected after receiving an unreliable provisional response (with the SDP) in the consultation call, SIP Server now increments the version number in the updated SDP sent to the agent. Previously in this scenario, SIP Server did not increment the SDP version number, which resulted in no voice path between the caller and the agent. The issue occurred with the following configuration: dual-dialog-enabled was set to false at the agent DN and reuse-sdp-on-reinvite was set to true at the consultation call destination DN. (SIP-19176)


Top of Page


Release Number 8.1.101.78 [08/07/15] – Hot Fix

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 release of SIP Server is built with T-Server Common Part (TSCP) release number 8.1.010.64. TSCP is the shared software that all T-Servers and SIP Servers use. Consult the TSCP release note for information about changes to the Common Part that might affect the functionality of SIP Server.

This is a hot fix for this product. This release contains the following new functionality:

Corrections and Modifications

This release includes the following corrections and modifications:


A primary SIP Server now correctly synchronizes the CSeq value with a backup SIP Server. Previously, after a switchover, the new primary SIP Server sent an incorrect CSeq value in a NOTIFY request. (SIP-19197)

Top of Page


Release Number 8.1.101.76 [08/03/15] – Hot Fix

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 release of SIP Server is built with T-Server Common Part (TSCP) release number 8.1.010.64. TSCP is the shared software that all T-Servers and SIP Servers use. Consult the TSCP release note for information about changes to the Common Part that might affect the functionality of SIP Server.

This is a hot fix for this product. This release does not contain new features or functionality.

Corrections and Modifications

This release includes the following corrections and modifications:


In multi-site scenarios, where a call is routed from Site A to Site B using the ISCC route transaction type, SIP Server no longer terminates unexpectedly while handling a router-timeout expiration on an External Routing Point. (SIP-19210)


In Business Continuity deployments, SIP Server can now correctly resolve where to send a request when two different sites have a Routing Point configured with the same DN number. A new Application level option manages this functionality:

resolve-internal-rp-by-host
Section: TServer
Default Value: false
Valid Values: false, true
Changes Take Effect: For next call

Set to true to specify that SIP Server will include host information when resolving the internal Routing Point number.
Set to false (the default) to enable the previous behavior in SIP Server. (SIP-19149, SIP-19091)


SIP Server now always sends a PRACK request for a response which contains Require:100rel. Previously, in some race conditions, when SIP Server received a reliable response while processing another scenario during the same call (for example, connecting to Media Server) the PRACK request might not be sent. (SIP-19067)


Top of Page


Release Number 8.1.101.75 [07/24/15] – Hot Fix

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 release of SIP Server is built with T-Server Common Part (TSCP) release number 8.1.010.64. TSCP is the shared software that all T-Servers and SIP Servers use. Consult the TSCP release note for information about changes to the Common Part that might affect the functionality of SIP Server.

This is a hot fix for this product. This release contains the following new features or functionality.

Corrections and Modifications

This release includes the following corrections and modifications:


When SIP Server receives RequestNetworkPrivateService with a special gcti_provisioning DN as destDN, it now correctly sends NOTIFY to the contact specified in this T-Library request. Previously, SIP Server sent NOTIFY to the phone that was last registered to the gcti_provisioning DN. (SIP-19126)


If dynamic recording is enabled for an agent and, after a transfer, SIP Server restarts recording for that agent, SIP Server now passes to GVP the AtributeExtensions dest and dest2, which were received in a TPrivateService request for the correct recorder selection. Previously in this scenario, SIP Server did not pass those extensions to GVP. (SIP-19095)


While working in Business Continuity mode and the dr-forward option is set to no-agent, SIP Server now correctly forwards calls to its DR peer when there is no agent logged into the DN. Previously, when the agent phone (where calls are received) was registered to only one of the two SIP Servers in the BC deployment, the DR call forwarding was not performed. (SIP-19075)


After a successful completion of the out-of-signaling-path (OOSP) transfer, SIP Server no longer sends a re-INVITE to the trunk if it receives the recording failure message during the OOSP transfer. (SIP-19058)


Top of Page


Release Number 8.1.101.74 [07/08/15] – Hot Fix

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 release of SIP Server is built with T-Server Common Part (TSCP) release number 8.1.010.64. TSCP is the shared software that all T-Servers and SIP Servers use. Consult the TSCP release note for information about changes to the Common Part that might affect the functionality of SIP Server.

This is a hot fix for this product. This release contains the following new features or functionality:

Corrections and Modifications

This release includes the following corrections and modifications:


SIP Server can now clear all calls on a DN that was disabled in the configuration environment while in dialing state. Previously, a SIP dialog remained stuck and no calls could be made from that DN when it was re-enabled. Use the new sip-release-call-on-disable-dn configuration option to manage this functionality.

sip-release-call-on-disable-dn
Section: TServer
Default Values: false
Valid Values: true, false
Changes Take Effect: At the next call

This option specifies whether SIP Server releases all calls for a DN that was disabled in the configuration environment. If set to true, SIP Server releases both call's dialogs (T-Library and SIP) for the disabled DN. (SIP-19038)


SIP Server now correctly distinguishes a prompt completion INFO message containing msml.dialog.exit in cases where two treatments are played one after another and msml.dialog.exit is received for a first treatment after the second prompt is started. Previously, in this race-condition scenario, SIP Server incorrectly ended the second treatment while it was in progress. (SIP-19009)


In multi-site scenarios where a call is routed from Site A to Site B using the ISCC direct-uui transaction type, SIP Server now correctly passes the isccid contact URI parameter from a received 302 Moved Temporarily response when sending a SIP message to the destination. Previously, SIP Server did not pass the isccid parameter. (SIP-18977)


When SIP Server tries to recover a treatment after its switchover but the recovery fails because of the MSML error response from a Media Server, SIP Server now generates a TreatmentEnd to the treatment. Previously in this scenario, SIP Server terminated unexpectedly while generating the TreatmentEnd. (SIP-18976)


SIP Server now correctly keeps the call forwarding setting on a DN. Previously, if any DN option was modified in the configuration environment, the TCallForwardSet request set on that DN was incorrectly cleared. (SIP-19044)


Top of Page


Release Number 8.1.101.73 [06/25/15] – Hot Fix

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 release of SIP Server is built with T-Server Common Part (TSCP) release number 8.1.010.64. TSCP is the shared software that all T-Servers and SIP Servers use. Consult the TSCP release note for information about changes to the Common Part that might affect the functionality of SIP Server.

This is a hot fix for this product. This release contains the following new features or functionality:

Corrections and Modifications

This release includes the following corrections and modifications:


SIP Server no longer responds with an EventError message to a TMonitorNextCall request if a previous intrusion attempt was unsuccessful. Previously, while running in the multi-threaded mode, SIP Server incorrectly rejected the new monitoring request. (SIP-18693)


SIP Server now connects a consultation call destination DN to the Music-on-Hold service in this two-step transfer scenario: TAlternateCall was performed before the consultation call answers and the transfer initiator is connected to the ringback treatment. Previously in this scenario, SIP Server dropped the consultation call after it answered. The issue occurred when the dual-dialog-enabled option was set to false on the agent DN that initiated the transfer. (SIP-18713)


Top of Page


Release Number 8.1.101.69 [06/17/15] – Hot Fix

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 release of SIP Server is built with T-Server Common Part (TSCP) release number 8.1.010.58. TSCP is the shared software that all T-Servers and SIP Servers use. Consult the TSCP release note for information about changes to the Common Part that might affect the functionality of SIP Server.

This is a hot fix for this product. This release contains the following new features or functionality:

Corrections and Modifications

This release includes the following corrections and modifications:


An agent can now make calls (using TMakeCall requests) while remaining in the Do Not Disturb state. Previously, in releases 8.1.x, SIP Server did not support this operation. (SIP-18905)


SIP Server no longer terminates if RequestClearCall is executed for a call distributed to a sequential Hunt Group DN but not answered yet. Previously in this scenario, if that Hunt Group had a large number of configured members (more than 100), SIP Server sometimes terminated unexpectedly. (SIP-18903)


SIP Server now properly processes a 302 Moved Temporarily message from a trunk, if that message came at the moment when a ringback transaction triggered by the preceding provisional response was in progress. Previously in this scenario, SIP Server might drop the call, leaving some call properties uncleared, and reject consecutive calls to that DN if the reject-call-incall option set to true. (SIP-18796)


SIP Server no longer terminates unexpectedly while handling call-completion SUBSCRIBE transactions. Previously, SIP Server did not clear SipCallCompletionSubscriberDialog correctly after subscription expired, which led to SIP Server memory corruption. (SIP-18911)


Top of Page


Release Number 8.1.101.68 [06/15/15] – 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 release of SIP Server is built with T-Server Common Part (TSCP) release number 8.1.010.58. TSCP is the shared software that all T-Servers and SIP Servers use. Consult the TSCP release note for information about changes to the Common Part that might affect the functionality of SIP Server.

There are no restrictions for this release. This release contains the following new features or functionality:

Note: This version was first released as a Hot Fix on 06/08/15.

Corrections and Modifications

This release does not include any corrections.

Top of Page


Release Number 8.1.101.67 [06/02/15] – Hot Fix

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 release of SIP Server is built with T-Server Common Part (TSCP) release number 8.1.010.58. TSCP is the shared software that all T-Servers and SIP Servers use. Consult the TSCP release note for information about changes to the Common Part that might affect the functionality of SIP Server.

This is a hot fix for this product. This release contains the following new features or functionality:

Corrections and Modifications

This release includes the following corrections and modifications:


SIP Server no longer drops a call on a Routing Point in the following race-condition scenario:

  1. SIP Server receives a TRouteCall request and sends an INVITE to the routing destination, waiting for a response.
  2. SIP Server receives an UPDATE with a new SDP from the caller, before the response to the INVITE arrives.
Previously in this scenario, SIP Server sometimes dropped the call. (SIP-18828)


Top of Page


Release Number 8.1.101.66 [05/21/15] – Hot Fix

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 release of SIP Server is built with T-Server Common Part (TSCP) release number 8.1.010.58. TSCP is the shared software that all T-Servers and SIP Servers use. Consult the TSCP release note for information about changes to the Common Part that might affect the functionality of SIP Server.

This is a hot fix for this product. This release contains the following new features or functionality:

Corrections and Modifications

This release includes the following corrections and modifications:


In a scenario where a call is routed to a DN with the Preview Interaction feature enabled, but the preview request is rejected with the status "expired," SIP Server now correctly applies a treatment to the call. Previously in this scenario, SIP Server did not apply the treatment. (SIP-18830)


Top of Page


Release Number 8.1.101.65 [05/13/15] – Hot Fix

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 release of SIP Server is built with T-Server Common Part (TSCP) release number 8.1.010.58. TSCP is the shared software that all T-Servers and SIP Servers use. Consult the TSCP release note for information about changes to the Common Part that might affect the functionality of SIP Server.

This is a hot fix for this product. This release does not contain new features or functionality.

Corrections and Modifications

This release includes the following corrections and modifications:


In an Active-Active Resource Manager (RM) deployment with the Trunk Group subscription enabled, if both RMs go down and a SIP Server switchover occurs after which at least one of the RMs comes back in service, SIP Server now sends the SUBSCRIBE message to the Trunk Group. SIP Server resends the subscription for the Trunk Group according to the sip-retry-timeout configuration option. Previously in this scenario, SIP Server did not send the SUBSCRIBE message, in order to receive notifications about the Trunk Group DN. (SIP-18745)


SIP Server no longer terminates unexpectedly if the key sdp-c-host (in AttributeExtensions of the TRouteCall request that was sent to a parked agent with the nailed-up connection) contains an empty value. (SIP-18735)


If the after-routing-timeout option set at the SIP Server Application to a value of less than the no-answer-timeout option set at the DN, the backup SIP Server no longer terminates unexpectedly when after-routing-timeout expires. (SIP-18598)


Top of Page


Release Number 8.1.101.64 [04/27/15] – Hot Fix

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 release of SIP Server is built with T-Server Common Part (TSCP) release number 8.1.010.58. TSCP is the shared software that all T-Servers and SIP Servers use. Consult the TSCP release note for information about changes to the Common Part that might affect the functionality of SIP Server.

This is a hot fix for this product. This release contains the following new features or functionality:

Corrections and Modifications

This release includes the following corrections and modifications:


In a scenario where a call is routed to a DN with the Preview Interaction feature enabled but the DN (agent) rejects the preview request and routing strategy applies new treatment, SIP Server now correctly applies a treatment to the call. Previously in this scenario, SIP Server rejected the treatment request. (SIP-18705)


When running in the multi-threaded mode (sip-link-type=3 or 4), and when two agents on the same site are monitored by two different supervisors, and one agent calls the other agent, SIP Server now correctly includes only one supervisor in the call. Previously, SIP Server included both supervisors in the call. (SIP-18684)


In a remote supervision scenario, when there is no monitor-type extension key present in a TRouteCall request issued to park a remote supervisor, SIP Server no longer incorrectly cancels the remote subscription and now invites the remote supervisor for all calls answered by the monitored agent. Previously, SIP Server sometimes canceled the remote subscription after the release of the first monitored call. (SIP-18627)


In a REFER-based multi-site scenario where an agent who rejoined the conference issues a THoldCall request, SIP Server now processes the request correctly and does not release the call. Previously in this rare scenario, SIP Server released the call unexpectedly. (SIP-18523)


In a multi-site or Business Continuity configuration conference scenario with four agents located on different SIP Servers, all involved parties are now correctly reported in EventUserEvent using the LCTParty extension key. Previously in this scenario, SIP Server included an incorrect list of parties in EventUserEvent. (SIP-16830, SIP-16566)


Top of Page


Release Number 8.1.101.63 [04/14/15] – Hot Fix

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 release of SIP Server is built with T-Server Common Part (TSCP) release number 8.1.010.58. TSCP is the shared software that all T-Servers and SIP Servers use. Consult the TSCP release note for information about changes to the Common Part that might affect the functionality of SIP Server.

This is a hot fix for this product. This release does not contain new features or functionality.

Corrections and Modifications

This release includes the following corrections and modifications:


In a multi-site supervision scenario, if a TMonitorNextCall request from a supervisor to monitor a remote agent is rejected, SIP Server now processes further monitoring requests issued by the same supervisor successfully. Previously in this scenario, SIP Server rejected further monitoring requests from the same supervisor with EventError. (SIP-18594)


For the ASM dialing mode when an outbound call is merged using the bridging method, SIP Server now correctly releases all Media Server parties associated with the call. Previously, SIP Server did not release Media Server parties associated with the call, which led to excessive memory consumption. (SIP-18462)


In an outbound call scenario in the ASM dialing mode, if a called party disconnects during processing of the TMergeCall request, SIP Server now clears the outbound call and generates an EventError response to the TMergeCall request. Previously in this scenario, SIP Server generated EventReleased to the outbound leg and an agent incorrectly remained in the ASM Engaged state. (SIP-18414)


When call recording is established and a recorded party is single-step transferred, SIP Server now correctly applies the sip-ring-tone-mode option value to determine if the ringback tone should be played to the call. Previously, SIP Server ignored the option value configured on the Trunk DN and did not connect the call to a Media Server to play the ringback tone. (SIP-18521)


SIP Server built with TSCP 8.1.010.58 no longer terminates unexpectedly while handling several concurrent configuration change events for adding and deleting connections in the Configuration Layer between server applications—for example, during restoration of the connection between Configuration Server and Configuration Server Proxy. (SIP-18375)


Top of Page


Release Number 8.1.101.62 [03/30/15] – Hot Fix

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 release of SIP Server is built with T-Server Common Part (TSCP) release number 8.1.010.56. TSCP is the shared software that all T-Servers and SIP Servers use. Consult the TSCP release note for information about changes to the Common Part that might affect the functionality of SIP Server.

This is a hot fix for this product. This release contains the following new features or functionality:

Corrections and Modifications

This release includes the following corrections and modifications:


When the disable-media-before-greeting configuration option is set to true at the Application level, SIP Server now correctly connects the caller to the voicemail if a greeting is present in the call and a destination DN does not answer the call. Previously in this scenario, SIP Server connected the caller in hold mode to the voicemail, so that caller could not hear the prompts of the voicemail. (SIP-18393)


In a scenario where a call from an external device is forwarded on no-answer to a Routing Point specified in the ontimeout dial-plan parameter, SIP Server now correctly reports CallStateOK in EventQueued. Previously in this scenario, SIP Server reported CallStateForwarded. (SIP-18398)


SIP Server no longer terminates unexpectedly while reading erroneously configured Voice over IP service DN with service-type=cos. (SIP-18481)


Top of Page


Release Number 8.1.101.61 [03/17/15] – Hot Fix

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 release of SIP Server is built with T-Server Common Part (TSCP) release number 8.1.010.56. TSCP is the shared software that all T-Servers and SIP Servers use. Consult the TSCP release note for information about changes to the Common Part that might affect the functionality of SIP Server.

This is a hot fix for this product. This release contains the following new features or functionality:

Corrections and Modifications

This release includes the following corrections and modifications:


In multi-site environments, in a remote supervision scenario where calls from a monitored Routing Point are routed to an agent on another site by means of the route transaction type, SIP Server now invites the correct supervisor to the call. Previously, SIP Server invited incorrect supervisors to the call. (SIP-18346)


When the divert-on-ringing option is set to false, SIP Server now correctly generates a new EventRouteRequest message if the call was rejected by an agent with the TRedirectCall request redirecting to the same Routing Point. Previously in this scenario, SIP Server did not process the new routing request, which resulted in a stuck call. (SIP-18356)


In a scenario where TSingleStepConference, TInitiateTransfer, or TInitiateConference requests to a Routing Point are progress, and a TSingleStepTransfer request is issued from the same DN to the same Routing Point, SIP Server now rejects the TSingleStepTransfer request with EventError. Previously in this scenario, SIP Server did not process those requests correctly. (SIP-18296, SIP-19568)


Top of Page


Release Number 8.1.101.59 [03/06/15] – Hot Fix

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 release of SIP Server is built with T-Server Common Part (TSCP) release number 8.1.010.56. TSCP is the shared software that all T-Servers and SIP Servers use. Consult the TSCP release note for information about changes to the Common Part that might affect the functionality of SIP Server.

This is a hot fix for this product. This release does not contain new features or functionality.

Corrections and Modifications

This release includes the following corrections and modifications:


SIP Server now properly connects remaining parties to the call when a party that is added to the conference releases the call while the two-step conference completion was in progress. Previously in this scenario, SIP Server did not connect the remaining parties of the call. (SIP-18337)


SIP Server no longer terminates unexpectedly while processing SUBSCRIBE messages for the Call Completion feature. Previously, when a new SUBSCRIBE message was received while the previous SUBSCRIBE was in the initiated state, SIP Server tried to clear the previous transaction, which caused SIP Server to terminate unexpectedly. (SIP-18289)


SIP Server now forwards the 180 Ringing provisional response to a caller in addition to the 181 Call is Being Forwarded response forwarded earlier. Previously in this scenario, SIP Server was not forwarding the 180 Ringing without the SDP to the caller. As a result, the caller did not see the redirection information when the destination phone was ringing. (SIP-18206)


SIP Server can be upgraded from any pre-8.1.101.56 version of 8.1.1 release to version 8.1.101.59 or later without service interruption. Previously, if a pre-8.1.101.56 version was upgraded to version 8.1.101.56, .57, or .58 and SIP Servers of two different versions were running as an HA pair, agent states were synchronized incorrectly. (SIP-18399)


The restricted sip-strict-cseq-match configuration option has been added. Set this option to false for backward compatibility with SIP devices that are not following RFC 3261 for CSeq implementation.

sip-strict-cseq-match
Section: TServer
Default Value: true
Valid Values: true, false
Changes Take Effect: After restart

When set to true, this option enables strict matching of the CSeq header.

Warning! Use this option only when requested by Genesys Customer Care.

(SIP-18386)


Top of Page


Release Number 8.1.101.58 [02/17/15] – Hot Fix

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 release of SIP Server is built with T-Server Common Part (TSCP) release number 8.1.010.56. TSCP is the shared software that all T-Servers and SIP Servers use. Consult the TSCP release note for information about changes to the Common Part that might affect the functionality of SIP Server.

This is a hot fix for this product. This release contains the following new features or functionality:

Corrections and Modifications

This release includes the following corrections and modifications:


SIP Server now correctly routes a call to an external destination specified in the default-dn option when the out-of-signaling-path (OOSP) is configured on the destination trunk. Previously in this scenario, SIP Server incorrectly terminated the call. (SIP-18248)


In a scenario where the disable-media-before-greeting option is set to true and the destination DN rejects or does not respond to the call and the call is returned to a Routing Point, SIP Server now correctly connects the caller with the Media Server (the active SDP) to play the treatment. Previously in this scenario, SIP Server incorrectly connected the caller with an inactive SDP and, as a result, the caller could not hear the treatment. (SIP-18238)


In IP Address Takeover HA configurations where the sip-iptakeover-monitoring option is set to false, the backup SIP Server now runs the VIP (Virtual IP address) down script only after the script is fully initialized. Previously, the backup SIP Server failed to run the VIP down script during its startup when the primary SIP Server was up but the VIP down script was not fully initialized. (SIP-18133)


When running in the multi-threaded mode, the backup SIP Server no longer grows in memory if it is started when the primary SIP Server was already running for a long time with active calls and nailed-up connections in progress. Previously, under rare circumstances, the backup SIP Server sometimes grew in memory. (SIP-18031)


Top of Page


Release Number 8.1.101.57 [02/12/15] – Hot Fix

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 release of SIP Server is built with T-Server Common Part (TSCP) release number 8.1.010.56. TSCP is the shared software that all T-Servers and SIP Servers use. Consult the TSCP release note for information about changes to the Common Part that might affect the functionality of SIP Server.

This is a hot fix for this product. This release contains the following new features or functionality:

Corrections and Modifications

This release includes the following corrections and modifications:


When an agent is logged in to the phone and the phone subscription expires, SIP Server now correctly logs the agent out. (SIP-18246)


Top of Page


Release Number 8.1.101.56 [01/30/15] – Hot Fix

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 release of SIP Server is built with T-Server Common Part (TSCP) release number 8.1.010.55. TSCP is the shared software that all T-Servers and SIP Servers use. Consult the TSCP release note for information about changes to the Common Part that might affect the functionality of SIP Server.

This is a hot fix for this product. This release contains the following new feature or functionality:

Corrections and Modifications

This release includes the following corrections and modifications:


When the enable-agentlogin-subscribe option is configured on an agent DN, SIP Server now correctly compares the password entered by the agent on the agent phone with the password configured in the Agent Login configuration object (Advanced tab) to allow the agent to log in if the passwords match. Previously, if the password was configured on the Advanced tab of the Agent Login object, SIP Server incorrectly denied access to the agent logging in to the phone. (SIP-18163)


SIP Server no longer applies the dial plan to the gcti::record number. Previously, SIP Server incorrectly applied the dial plan to the gcti::record number and placed the call to a Routing Point. (SIP-18021)


SIP Server now operates properly in a high-availability deployment even if the sip-link-type option is set to 0 in the primary SIP Server and to 3 in the backup SIP Server. Previously, after a switchover, SIP Server failed to process T-Library requests with this misconfiguration. (SIP-16635)


Top of Page


Release Number 8.1.101.55 [01/23/15] – Hot Fix

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 release of SIP Server is built with T-Server Common Part (TSCP) release number 8.1.010.55. TSCP is the shared software that all T-Servers and SIP Servers use. Consult the TSCP release note for information about changes to the Common Part that might affect the functionality of SIP Server.

This is a hot fix for this product. This release contains the following new features or functionality:

Corrections and Modifications

This release does not include any corrections.

Top of Page


Release Number 8.1.101.54 [01/16/15] – Hot Fix

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 release of SIP Server is built with T-Server Common Part (TSCP) release number 8.1.010.55. TSCP is the shared software that all T-Servers and SIP Servers use. Consult the TSCP release note for information about changes to the Common Part that might affect the functionality of SIP Server.

This is a hot fix for this product. This release does not contain new features or functionality.

Corrections and Modifications

This release includes the following corrections and modifications:


SIP Server now correctly adds the Max-Forwards header in the ACK request of the session refresh transaction. Previously, SIP Server did not add the Max-Forwards header in the ACK request sent for the session refresh transaction. (SIP-18071)


SIP Server no longer grows in memory if there is an invalid fully-qualified domain name (FQDN) configured in the contact option of the Trunk Group DN object. (SIP-18030)


SIP Server no longer terminates the call in a scenario in which a 183 (Session in Progress) early media provisional reliable response is received while the UPDATE in early dialog was sent by SIP Server. Previously in this scenario, if option reuse-sdp-on-reinvite is set to true on the trunk, SIP Server terminated the call. (SIP-17965)


When the call-observer-with-hold option is set to true, SIP Server can now send either an inactive SDP (a=inactive) or black hole SDP (c=IN IP4 0.0.0.0) in the initial INVITE to a supervisor, depending on the setting of the sip-hold-rfc3264 option. Previously, SIP Server sent only a black hole SDP in the initial INVITE to the supervisor. (SIP-17929)


If, while establishing a TCP connection to a SIP Endpoint, SIP Server switches to the backup mode, it now correctly handles the closure of that TCP connection. Previously in this scenario, these TCP connections sometimes became stale and SIP Server was not able to re-open them when switching back to the primary role. (SIP-17821)


SIP Server introduces the DN-level option enforce-rfc3455 to enable blocking the P-Called-Party-ID header in INVITE messages for environments where SIP Server acts as a User Agent Client (UAC) and RFC 3455 is strictly enforced. Previously, SIP Server always propagated the P-Called-Party-ID header in INVITE messages that caused the request rejection in those environments.

enforce-rfc3455
Section: TServer
Default Value: false
Valid Values: true, false
Changes Take Effect: Immediately

If set to true, SIP Server does not propagate the P-Called-Party-ID header in outgoing INVITE messages in SIP environments where RFC 3455 is strictly enforced. If set to false, SIP Server propagates the P-Called-Party-ID header in outgoing INVITE messages.

(SIP-17786)


Top of Page


Release Number 8.1.101.53 [12/23/14] – 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 release of SIP Server is built with T-Server Common Part (TSCP) release number 8.1.010.55. TSCP is the shared software that all T-Servers and SIP Servers use. Consult the TSCP release note for information about changes to the Common Part that might affect the functionality of SIP Server.

There are no restrictions for this release. This release contains the following new features or functionality:

Corrections and Modifications

This release includes the following corrections and modifications:


SIP Server no longer incorrectly generates error messages 06080 Mandatory configuration option not found or 06082 Mandatory configuration option has invalid value while processing a Switch Access Code configuration change from a non-empty value to an empty one, and vice versa. (SIP-16806)


SIP Server now releases a consultation call correctly in the following scenario:

  1. The reject-call-incall option is set to true on an agent DN.
  2. The agent makes a consultation call from that DN.
  3. The agent requests to alternate calls.
  4. The consultation call is established but the DN does not respond to SIP Server's NOTIFY and INVITE requests for the alternate operation.
Previously in this scenario, SIP Server did not clear the consultation call and reported the DN as busy. (SIP-17907)


In the scenario where a treatment is applied to a call at one Routing Point, and then the call is routed to another Routing Point where a treatment is also applied, SIP Server now properly synchronizes the call state with the backup instance. Previously in this scenario, SIP Server sometimes did not synchronize the call state, which resulted in a treatment failure if a switchover happened while the treatment was in progress. (SIP-17889)


While operating in Business Continuity mode, SIP Server now correctly applies the onnotreg dial-plan parameter to DNs that have no SIP registration and no contact configured. (SIP-17871)


SIP Server now disables the ability to perform a call pickup (in the ringing state) by a Hunt Group member in sequential ringing Hunt Group scenarios. SIP Server now rejects call pickup requests with a 403 Forbidden SIP response. Previously, Hunt Group scenarios were processed incorrectly, causing SIP Server to terminate unexpectedly. (SIP-17863)


SIP Server now correctly processes an outbound stranded call (a call that arrives at a queue with no remaining logged-in agents) and when the stranded-on-arrival-calls-overflow option is set to release. Previously in this scenario, SIP Server entered into a loop, printing aTmParty::SetCause: QueueCleared messages, while processing a stranded call routed to an ACD queue (the default destination). (SIP-17838)


SIP Server now ignores a mismatch value of the sequence number in the CSeq header field in NOTIFY messages within the SUBSCRIBE dialog with Resource Manager. Previously in this scenario, SIP Server rejected requests with an incorrect CSeq header value, which it received after a Resource Manager switchover. (SIP-17834)


Top of Page


Release Number 8.1.101.52 [12/05/14] – Hot Fix

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 release of SIP Server is built with T-Server Common Part (TSCP) release number 8.1.010.54. TSCP is the shared software that all T-Servers and SIP Servers use. Consult the TSCP release note for information about changes to the Common Part that might affect the functionality of SIP Server.

This is a hot fix for this product. This release contains the following new features or functionality:

Corrections and Modifications

This release includes the following corrections and modifications:


SIP Server now cancels an initial client INVITE transaction after detecting a transport error in the initial server INVITE transaction. Previously in this scenario, SIP Server did not cancel an initial client INVITE transaction but only destroyed a SIP dialog upon receiving CALLED_TRANSPORT_ERROR, which sometimes led to a stuck client INVITE transaction. (SIP-17760)


SIP Server built with TSCP 8.1.010.54 no longer grows in memory while processing multi-site (ISCC) trunk optimization scenarios in which multi-site calls are routed back to the origination site. (SIP-16775)


Top of Page


Release Number 8.1.101.51 [11/21/14] – Hot Fix

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 release of SIP Server is built with T-Server Common Part (TSCP) release number 8.1.010.53. TSCP is the shared software that all T-Servers and SIP Servers use. Consult the TSCP release note for information about changes to the Common Part that might affect the functionality of SIP Server.

This is a hot fix for this product. This release contains the following new features or functionality:

Corrections and Modifications

This release includes the following corrections and modifications:


When running in multi-threaded mode, SIP Server now correctly passes the message-file (.lms) information to the Log library for all threads. Previously, SIP Server logged the Std 04107 Unable to load Log Messages file 'TServer.lms', error code 30 message in all thread logs during its startup. (SIP-17651)


The restricted sip-wait-ack-timeout configuration option has been modified. It can now be configured in milliseconds. Previously, it could be only configured in seconds.

sip-wait-ack-timeout
Section: TServer
Default Value: 2 sec
Valid Value: Any positive integer, sec/msec (example: 3 sec, 250 msec)
Changes Take Effect: Immediately

When SIP Server processes an incoming re-INVITE request, it starts a timer to wait for the ACK message to be received for this transaction. Once the ACK arrives, SIP Server sends the re-INVITE to perform the requested operation (greeting, treatment, and so on). If the option is set to 0 (zero), the current SIP Server behavior applies.

Warning! Use this option only when requested by Genesys Customer Care.

(SIP-17411)


Top of Page


Release Number 8.1.101.50 [11/11/14] – Hot Fix

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 release of SIP Server is built with T-Server Common Part (TSCP) release number 8.1.010.53. TSCP is the shared software that all T-Servers and SIP Servers use. Consult the TSCP release note for information about changes to the Common Part that might affect the functionality of SIP Server.

This is a hot fix for this product. This release contains the following new features or functionality:

Corrections and Modifications

This release includes the following corrections and modifications:


The primary SIP Server now correctly synchronizes released call data with the backup SIP Server if a call was released because of the errors in call-control operations. Previously in this scenario, the released call was stuck in the new primary (formerly backup) SIP Server after a switchover. (SIP-17475)


If force-register, oos-check, and oos-force options are set on a Trunk DN, SIP Server now sends one REGISTER message at a time to the trunk. Previously, SIP Server sent an additional REGISTER message, before the first REGISTER was canceled, to the unresponsive trunk when it detected that the trunk was back in-service. (SIP-17409)


SIP Server no longer overwrites the UserData set by URS when routing a call from a Routing Point to another Routing Point on the same SIP Server. Previously in this scenario, SIP Server incorrectly repeated the mapping of the custom header from INVITE into AttributeUserData of the second EventRouteRequest. (SIP-17263)


Top of Page


Release Number 8.1.101.49 [10/31/14] – Hot Fix

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 release of SIP Server is built with T-Server Common Part (TSCP) release number 8.1.010.53. TSCP is the shared software that all T-Servers and SIP Servers use. Consult the TSCP release note for information about changes to the Common Part that might affect the functionality of SIP Server.

This is a hot fix for this product. This release contains the following new features or functionality:

Corrections and Modifications

This release includes the following corrections and modifications:


When either the display-name option is configured at the DN level option or the DisplayName key extension is specified in a T-Library request, and if the encoding is enabled, SIP Server now correctly encodes the display name in UTF-8 format before including it in a SIP message. Previously in this scenario, SIP Server did not encode the display name. (SIP-17208)


When processing HTTP Digest authentication for outbound calls and when a server (SBC) indicates multiple supported quality of protection (qop) options (for example, Qop="auth,auth-int") in the www-authenticate header of the Digest challenge, SIP Server now generates the Digest Response using the selected qop option value. Previously, SIP Server included an incorrect Digest Response, which resulted in failed authentication of outbound calls. (SIP-17155)


Top of Page


Release Number 8.1.101.47 [10/21/14] – Hot Fix

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 release of SIP Server is built with T-Server Common Part (TSCP) release number 8.1.010.52. TSCP is the shared software that all T-Servers and SIP Servers use. Consult the TSCP release note for information about changes to the Common Part that might affect the functionality of SIP Server.

This is a hot fix for this product. This release contains the following new features or functionality.

Corrections and Modifications

This release includes the following corrections and modifications:


SIP Server now correctly retransmits scheduled re-INVITE messages for session refresh purposes. Previously, in cases where the session-refresh timeout was expired while another transaction was in progress, SIP Server sometimes did not send scheduled re-INVITE messages. (SIP-17390)


SIP Server is now able to handle malformed SUBSCRIBE messages. (SIP-17308)


Top of Page


Release Number 8.1.101.46 [10/14/14] – Hot Fix

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 release of SIP Server is built with T-Server Common Part (TSCP) release number 8.1.010.52. TSCP is the shared software that all T-Servers and SIP Servers use. Consult the TSCP release note for information about changes to the Common Part that might affect the functionality of SIP Server.

This is a hot fix for this product. This release contains the following new features or functionality.

Corrections and Modifications

This release includes the following corrections and modifications:


If an UPDATE message arrives on an initial INVITE transaction that is in the early dialog state, SIP Server now includes the P-Asserted-Identity header present in the UPDATE message when generating an INVITE message to a destination. Previously, SIP Server ignored the P-Asserted-Identity header present in the UPDATE message. (SIP-17311)


When msml-support is set to true, and when a treatment is requested on a Routing Point, SIP Server establishes a connection with Genesys Media Server and sends an INFO message with the msml dialog to start the treatment. If SIP Server receives the INFO message with msml.dialog.exit in the TCP connection in response to its INFO message before 200 OK arrives, SIP Server now generates EventTreatmentApplied and EventTreatmentEnd messages. Previously, SIP Server ignored this INFO and did not generate EventTreatmentEnd. (SIP-17386)


Top of Page


Release Number 8.1.101.45 [10/07/14] – Hot Fix

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 release of SIP Server is built with T-Server Common Part (TSCP) release number 8.1.010.52. TSCP is the shared software that all T-Servers and SIP Servers use. Consult the TSCP release note for information about changes to the Common Part that might affect the functionality of SIP Server.

This is a hot fix for this product. This release does not contain new features or functionality.

Corrections and Modifications

This release includes the following corrections and modifications:


SIP Server executes SIP-to-TLib mapping from the SIP INVITE message received in response to a REFER request that SIP Server sent to an endpoint to transfer the call to a Routing Point. Previously, in a scenario where an unattended transfer was issued to a Routing Point, SIP Server did not map user data from the received INVITE.

A new Application-level option, userdata-map-invite-after-refer, is added.

userdata-map-invite-after-refer
Section: TServer
Default Value: false
Valid Values: true, false
Changes Take Effect: Immediately

If the option is set to true, SIP Server executes SIP-to-TLib mapping from the SIP INVITE message received in response to a REFER request that SIP Server sent to an endpoint to transfer the request to a Routing Point. If the option is set to false, no mapping is performed from that INVITE.

Note: If SIP-to-TLib mapping is configured for both INVITE and REFER requests and the userdata-map-invite-after-refer option is set to true, then in cases where an unattended transfer is triggered by a 1pcc REFER, SIP Server maps data twice. The first time SIP Server maps data from the received REFER and then it maps data from the INVITE. If the same keys must be mapped from both REFER and INVITE (for example, Call-ID), the keys from the INVITE take precedence.

(SIP-17088)


Top of Page


Release Number 8.1.101.44 [09/25/14] – Hot Fix

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 release of SIP Server is built with T-Server Common Part (TSCP) release number 8.1.010.52. TSCP is the shared software that all T-Servers and SIP Servers use. Consult the TSCP release note for information about changes to the Common Part that might affect the functionality of SIP Server.

This is a hot fix for this product. This release does not contain new features or functionality.

Corrections and Modifications

This release includes the following corrections and modifications:


SIP Server no longer terminates unexpectedly in a scenario in which an inbound call arrives at a Routing Point, but no URS clients are connected to SIP Server, and the default-dn Application-level option is set to a nonexistent DN. (SIP-17285)


SIP Server now correctly converts the gvp:param name multi-byte characters to UTF-8 format in the msml body of the INFO message that is sent to MCP. Previously, SIP Server encoded characters twice and, as a result, attached the incorrect User Data to the call. (SIP-17205)


SIP Server now processes the expires parameter in the Contact header of the 200 OK response to the REGISTER request when the Expires header in the 200 OK is absent. Previously in this scenario, SIP Server ignored this parameter. (SIP-17136)


Top of Page


Release Number 8.1.101.43 [09/19/14] – Hot Fix

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 release of SIP Server is built with T-Server Common Part (TSCP) release number 8.1.010.52. TSCP is the shared software that all T-Servers and SIP Servers use. Consult the TSCP release note for information about changes to the Common Part that might affect the functionality of SIP Server.

This is a hot fix for this product. This release contains the following new features or functionality:

Corrections and Modifications

This release includes the following corrections and modifications:


When receiving an UPDATE message with the P-Asserted-Identity header after the initial INVITE, SIP Server now correctly includes the updated P-Asserted-Identity header in the INVITE message sent to a destination. Previously in this scenario, SIP Server did not include the P-Asserted-Identity header that was present in the UPDATE message while generating the INVITE. See known limitation SIP-17311. (SIP-17192)


On the Linux operating system, if sip-nic-monitoring or tlib-nic-monitoring is set to true, SIP Server reports the NIC status as failed only if two consecutive monitoring requests have detected the NIC to be in failed status. All unsuccessful attempts to obtain status are ignored. Previously, SIP Server reported the NIC status as failed when the status was not detected on a second attempt (the error code was returned instead of the NIC status).

Note: A similar issue is also fixed for Virtual IP address monitoring when the sip-iptakeover-monitoring option is set to true. Previously in this scenario, SIP Server reported the Virtual IP address as not present. (SIP-17186)


Top of Page


Release Number 8.1.101.42 [09/15/14] – Hot Fix

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 release of SIP Server is built with T-Server Common Part (TSCP) release number 8.1.010.52. TSCP is the shared software that all T-Servers and SIP Servers use. Consult the TSCP release note for information about changes to the Common Part that might affect the functionality of SIP Server.

This is a hot fix for this product. This release contains the following new features or functionality:

Corrections and Modifications

This release includes the following corrections and modifications:


SIP Server now sends the correct Request-URI for the mid-dialog request when processing strict routing in accordance with RFC 3261 requirements. Previously, when processing strict routing, SIP Server incorrectly updated the Request-URI for the mid-dialog request with a value from the Contact header. (SIP-17051)


SIP Server supports the new configuration option session-refresh-enforced. This option controls whether SIP Server sends the re-INVITE message when the session refresh mechanism is activated. Previously, SIP Server sent a refresh re-INVITE to all devices including those that did not support the session refresh.

session-refresh-enforced
Section: TServer
Default Value: true
Valid Values: true, false
Changes Take Effect: Immediately

Controls whether SIP Server activates the SIP Session timer within a SIP dialog. If set to false, SIP Server activates the SIP Session timer only if both an initial INVITE and 200 OK response to that INVITE contains the Session-Expires header. If set to true, SIP Server, while activating that timer, ignores the absence of the Session-Expires header in the response and starts the timer based on the header presence in the request. If an endpoint does not support the session refresh mechanism, set this option to false. The option has an affect only when the session-refresh-interval option is set to a non-zero value. You can define this option at both the Application and the DN level. The DN-level setting takes precedence over the Application-level setting.

(SIP-16741)


When the sip-from-pass-through option is set to true on an inbound trunk, SIP Server now correctly passes through the SIP URI parameters in the From header of the incoming INVITE message to the outgoing INVITE. Previously, SIP Server did not pass through SIP URI parameters. (SIP-15783)


In multi-site scenarios, SIP Server processes a TDeleteFromConference request successfully and removes the requested party from the conference. Previously, SIP Server rejected a TDeleteFromConference request with EventError if the request was submitted to remove the conference initiator, or the conferenced party present at the other site, if this party was not added by the party that submitted the request. (SIP-16797)


Top of Page


Release Number 8.1.101.40 [09/05/14] – Hot Fix

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 release of SIP Server is built with T-Server Common Part (TSCP) release number 8.1.010.52. TSCP is the shared software that all T-Servers and SIP Servers use. Consult the TSCP release note for information about changes to the Common Part that might affect the functionality of SIP Server.

This is a hot fix for this product. This release contains the following new features or functionality:

Corrections and Modifications

This release includes the following corrections and modifications:


SIP Server now adds MsmlResponseCode and ResponseDescription keys in AttributeExtensions only in EventTreatmentNotApplied messages. Previously, SIP Server incorrectly also added these keys in EventTreatmentApplied. (SIP-17078)


SIP Server no longer processes the Transfer-Type=oosp key in AttributeExtensions of TRouteCall when an incoming multi-site call arrives via an external Routing Point. Previously, SIP Server processed Transfer-Type=oosp and sent 302 Moved Temporarily to the routing destination. (SIP-17027)


SIP Server now correctly drops an inbound leg of a call after receiving, in response to INVITEs, 180 Ringing, 401 Unauthorized, and then 481 Call/Transaction Does Not Exist messages from the destination. Previously in this scenario, SIP Server did not drop the inbound leg of the call. (SIP-16931)


SIP Server no longer grows in memory if the overload control module rejects a request. Previously in this scenario, SIP Server experienced a memory leak when it was built with TSCP version 8.1.010.25 through 8.1.010.51. (TS-10777, SIP-16896)


When running in warm standby mode, SIP Server now properly registers Access Resources after a switchover. Previously in this scenario, SIP Server did not register Access Resources, which led to failed routing transactions with the Access_Resource_Not_Registered error message. (TS-10771, SIP-16805)


Top of Page


Release Number 8.1.101.39 [08/15/14] – Hot Fix

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 release of SIP Server is built with T-Server Common Part (TSCP) release number 8.1.010.51. TSCP is the shared software that all T-Servers and SIP Servers use. Consult the TSCP release note for information about changes to the Common Part that might affect the functionality of SIP Server.

This is a hot fix for this product. This release contains no new features or functionality.

Corrections and Modifications

This release includes the following corrections and modifications:


When both greeting-delay-events and greeting-after-merge options are set to true and a two-step attended transfer is performed, SIP Server now correctly generates EventEstablished when a greeting after a call merge is completed. Previously in this scenario, if a call was merged while the greeting was in progress, SIP Server did not generate EventEstablished. (SIP-16928)


The sip-error-conversion configuration option now works correctly in HoldCall scenarios. Previously, when the sip-error-conversion option was configured on a DN, on a softswitch DN (Voice over IP Service DN with service-type=softswitch), or on an Application level, and a call was placed on hold, SIP Server did not convert the error code which was received in response to the hold INVITE message. (SIP-16871)


Default values of the following configuration options are now set to 0 to disable corresponding overload control functionality:

(SIP-16930)


Top of Page


Release Number 8.1.101.38 [08/06/14] – Hot Fix

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 release of SIP Server is built with T-Server Common Part (TSCP) release number 8.1.010.51. TSCP is the shared software that all T-Servers and SIP Servers use. Consult the TSCP release note for information about changes to the Common Part that might affect the functionality of SIP Server.

This is a hot fix for this product. This release contains the following new features or functionality:

Corrections and Modifications

This release includes the following corrections and modifications:


SIP Server no longer terminates unexpectedly after receiving a re-INVITE message from the caller during a session refresh. Previously, SIP Server terminated unexpectedly while executing the re-INVITE. (SIP-16841)


For the IP Address Takeover configuration (the Application option sip-iptakeover-monitoring is set to true), when SIP Server is not able to open a SIP port for listening, it reports the SERVICE_UNAVAILABLE status to LCA/SCS and, as result, is promoted to a backup role, after which it correctly reports the SERVICE_RUNNING status. Previously in this scenario, the backup SIP Server remained in status SERVICE_UNAVAILABLE. (SIP-16833)


If the charge-type option is set to 2 in the Voice Over IP Service DN, when the agent makes an outbound call and the called destination provides an early media, the agent and destination can now hear each other correctly. Previously in this scenario, SIP Server incorrectly placed the agent on hold, which resulted in one-way audio. (SIP-16813)


If the Application option logout-on-disconnect is set to true, SIP Server no longer logs Agent A out of the DN when Agent B tries to log in on the same DN from a different T-Library client and then disconnects. Previously in this scenario, SIP Server incorrectly logged Agent A out of the DN. (SIP-16790)


If the version of the primary SIP Server is 8.1.0.x or 8.1.1.x and the version of the backup SIP Server is 8.1.101.38, the synchronization between servers after the switchover is now processed correctly. Previously, different versions of SIP Servers were not synchronized correctly, which caused the Hot Upgrade procedure to fail.

Note: The Hot Rollback procedure, from the primary newer SIP Server version to the backup older SIP Server version, is not supported.

(SIP-16645)


If enabled, SIP Server now correctly applies Unicode support to instant messages. Previously, SIP Server did not encode instant messages and passed them through without any changes.

To enable instant messages encoding received in SIP messages from UTF-8 to a local character set in T-Library messages and vice versa, set the following options:

A new Application-level option has been added to support this feature:

encoding-area
Section: TServer
Default Value: No default value
Valid Values: A list of areas separated by a comma (,) where encoding will be applied. Supported areas:

Changes Take Effect: Immediately

Specifies the list of areas where encoding applies.

(SIP-16600)


The x-sip-log configuration option has been modified as follows:

Previously, if this option was not configured, SIP Server generated the log file for the Main thread only. Now, if this option is not configured, SIP Server generates log files for all running threads by default. In this case, the names for the log files will be taken from the log option all. If the x-sip-log option is configured as an empty string, SIP Server generates the log file for the Main thread only. (SIP-16577)


Top of Page


Release Number 8.1.101.34 [07/30/14] – 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 release of SIP Server is built with T-Server Common Part (TSCP) release number 8.1.010.51. TSCP is the shared software that all T-Servers and SIP Servers use. Consult the TSCP release note for information about changes to the Common Part that might affect the functionality of SIP Server.

There are no restrictions for this release. This release contains the following new features or functionality:

Corrections and Modifications

This release includes the following corrections and modifications:


In a scenario where the subscription-id option is configured on both the Voice over IP Service DN with service-type=msml that represents an Active-Active Resource Manager (RM) pair and Trunk Group DN with contact=::msml, when both RMs go down, the Voice over IP Service DN goes out of service and then comes back in service, SIP Server now subscribes (using the SUBSCRIBE message) for notifications about Voice over IP Service and Trunk Group DNs. Previously in this scenario, SIP Server did not send the SUBSCRIBE message to receive notifications about the Trunk Group DN. (SIP-16756)


SIP Server now correctly restores nailed-up connections after a switchover, if the backup SIP Server was restarted before the switchover. Previously, SIP Server did not restore nailed-up connections that were established before the switchover occurred. (SIP-16595)


Top of Page


Release Number 8.1.101.33 [07/15/14] – Hot Fix

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 release of SIP Server is built with T-Server Common Part (TSCP) release number 8.1.010.51. TSCP is the shared software that all T-Servers and SIP Servers use. Consult the TSCP release note for information about changes to the Common Part that might affect the functionality of SIP Server.

This is a hot fix for this product. This release contains the following new features or functionality:

Corrections and Modifications

This release includes the following corrections and modifications:


SIP Server now correctly plays a greeting in the following scenario:

  1. An inbound call arrives at a Routing Point.
  2. When a routing timer expires, the call is routed to a default-dn.
  3. The default-dn routes the call to another Routing Point.
  4. The call is routed to an agent with the configured agent and customer greetings.
Previously in this scenario, SIP Server did not play greetings correctly. (SIP-16647)


If a routing attempt fails on a Routing Point and the timeout specified by after-routing-timeout expires, SIP Server correctly generates the EventError message, as before. However, it no longer repeats the attempt to route the call by selecting an alternate trunk for it. (SIP-16468)


SIP Server now correctly generates the Min-SE header in accordance with RFC 4028, as follows:

Previously, SIP Server did not generate the Min-SE header in accordance with the RFC requirements. In the case of direct calls, SIP Server now converts the 422 response to 603 by default. (SIP-15099)


SIP Server no longer incorrectly adds the P-Asserted-Identity header in an outbound INVITE message if an outbound Trunk DN configured with the enforce-privacy option set to id and the enforce-trusted option set to false. (SIP-16653)


SIP Server supports a new key in AttributeExtensions:

Key: busy-on-reject
Values: true, false

If SIP Server receives TRouteCall with busy-on-reject=true in AttributeExtensions and if the destination responds with the 486 Busy Here message, it generates EventDestinationBusy for the origination party. (SIP-15900)


When an agent transfers a call to an external destination and if that destination responds with a 180 Ringing response, SIP Server initiates a ring back to the agent. Before the media session is established for playing a ring back, if the destination sends back a 302 Moved Temporarily response with the alternate destination, SIP Server now successfully redirects the call to the alternate destination. Previously, when the 302 response was received before the media session was established, SIP Server dropped the call.
The issue occurred with the following configuration: divert-on-ringing=false was set on the Application level and sip-ring-tone-mode=1 was set on the agent DN. (SIP-16734)


SIP Server no longer reports license errors in the log while shutting down. (SIP-16512)


Top of Page


Release Number 8.1.101.30 [07/01/14] – Hot Fix

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 release of SIP Server is built with T-Server Common Part (TSCP) release number 8.1.010.50. TSCP is the shared software that all T-Servers and SIP Servers use. Consult the TSCP release note for information about changes to the Common Part that might affect the functionality of SIP Server.

This is a hot fix for this product. This release contains the following new features or functionality:

Corrections and Modifications

This release does not include any corrections or modifications.

Top of Page


Release Number 8.1.101.29 [06/20/14] – Hot Fix

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 release of SIP Server is built with T-Server Common Part (TSCP) release number 8.1.010.50. TSCP is the shared software that all T-Servers and SIP Servers use. Consult the TSCP release note for information about changes to the Common Part that might affect the functionality of SIP Server.

This is a hot fix for this product. This release contains the following new features or functionality:

Corrections and Modifications

This release includes the following corrections or modifications:


SIP Server now correctly parks an agent with a nailed-up connection after processing a two-step transfer to a Routing Point. Previously in this scenario, SIP Server did not park the agent with the nailed-up connection. (SIP-16479)


Top of Page


Release Number 8.1.101.28 [06/12/14] – Hot Fix

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 release of SIP Server is built with T-Server Common Part (TSCP) release number 8.1.010.50. TSCP is the shared software that all T-Servers and SIP Servers use. Consult the TSCP release note for information about changes to the Common Part that might affect the functionality of SIP Server.

This is a hot fix for this product. This release contains no new features or functionality.

Corrections and Modifications

This release includes the following corrections and modifications:


This release introduces a new SIP Server Application-level option:

sip-tls-sec-protocol
Section: TServer
Default Value: SSLv23
Valid Values: SSLv23, SSLv3, TLSv1, TLSv11
Changes Take Effect: After restart

This option specifies which handshake protocol SIP Server will use on the SIP TLS listening port and when connecting to a SIP TLS-enabled device as a client. This option can be used only on UNIX operating systems with Genesys Security Pack on 8.1.300.03 or later. The option has no effect on Windows. Protocols are specified by the option values as follows:

(SIP-16335)


Top of Page


Release Number 8.1.101.27 [06/04/14] – Hot Fix

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 release of SIP Server is built with T-Server Common Part (TSCP) release number 8.1.010.49. TSCP is the shared software that all T-Servers and SIP Servers use. Consult the TSCP release note for information about changes to the Common Part that might affect the functionality of SIP Server.

This is a hot fix for this product. This release contains the following features or functionality:

Corrections and Modifications

This release includes the following corrections and modifications:


SIP Server now correctly schedules a re-INVITE in the following inbound-call scenarios:

  1. Early media is established between a called party and an agent, and
  2. Conversion to the full media is finished on one side while the conversion is still in progress on the other side, waiting for ACK for 200 OK.
  3. Re-INVITE with the new SDP is received at this point.
Previously, SIP Server ignored the re-INVITE, which resulted in a one-way audio call. (SIP-16094)


In IP Address Takeover HA scenarios, SIP Server now correctly transmits a 200 OK message to a destination after a switchover if the TCP connection is used between SIP Server and an endpoint. Previously, SIP Server attempted to restore the TCP connection after the switchover and did not transmit 200 OK properly. (SIP-16375)


Top of Page


Release Number 8.1.101.25 [05/28/14] – Hot Fix

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 release of SIP Server is built with T-Server Common Part (TSCP) release number 8.1.010.48. TSCP is the shared software that all T-Servers and SIP Servers use. Consult the TSCP release note for information about changes to the Common Part that might affect the functionality of SIP Server.

This is a hot fix for this product. This release contains no new features or functionality.

Corrections and Modifications

This release includes the following corrections and modifications:


SIP Server now accepts and properly processes a TSendDTMF request if a destination party has not answered yet, but has been connected to the caller through the early media provisional reliable response. Previously, SIP Server rejected such a request. (SIP-16290)


SIP Server now correctly parks an agent with a nailed-up connection when the second switchover occurs. Previously, SIP Server correctly parked the agent with the nailed-up connection after the first switchover but failed to park the agent with the nailed-up connection when the second switchover occurred. (SIP-16317)


SIP Server now correctly performs SIP-to-TLib data mapping when a SIP REFER request is received during the execution of the TSendDTMF request. Previously in this scenario, SIP Server did not map SIP-to-TLib data even though it processed the SIP REFER request properly. (SIP-16299)


Top of Page


Release Number 8.1.101.23 [05/16/14] – Hot Fix

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 release of SIP Server is built with T-Server Common Part (TSCP) release number 8.1.010.48. TSCP is the shared software that all T-Servers and SIP Servers use. Consult the TSCP release note for information about changes to the Common Part that might affect the functionality of SIP Server.

This is a hot fix for this product. This release contains no new features or functionality.

Corrections and Modifications

This release includes the following corrections and modifications:


When operating in Business Continuity (BC) deployments, SIP Server now correctly forwards the multi-site MWI notification request TNetworkPrivateService (AttributePrivateMsgID - 6002) to its BC peer. (SIP-16228)


When both contact and contacts-backup options are configured on the Trunk and a single-step transfer is initiated using the OOSP method (oosp-transfer-enabled=true), SIP Server now correctly uses the active contact in the Refer-to header of the REFER message. Previously, SIP Server incorrectly used only the primary contact and did not use the contacts-backup. As a result, when the primary contact went down, the single-step transfer could not be completed. (SIP-16047)


If the SIP URI in the From header of an INVITE request contains a comma, semicolon, or question mark, SIP Server now encloses the SIP URI in angle brackets (< >) when passing the INVITE. Previously, SIP Server removed the angle brackets from the From header. (SIP-16201)


Top of Page


Release Number 8.1.101.22 [05/09/14] – Hot Fix

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 release of SIP Server is built with T-Server Common Part (TSCP) release number 8.1.010.48. TSCP is the shared software that all T-Servers and SIP Servers use. Consult the TSCP release note for information about changes to the Common Part that might affect the functionality of SIP Server.

This is a hot fix for this product. This release contains no new features or functionality.

Corrections and Modifications

This release includes the following corrections and modifications:


SIP Server now provides the ability to control AttributeReasons to be populated in unsolicited EventAgentReady messages generated by the After Call Work (ACW) feature, by using the Application-level acw-persistent-reasons configuration option in the TServer section. Previously, SIP Server always populated AttributeReasons in EventAgentReady messages.

acw-persistent-reasons
Section: TServer
Default Value: true
Valid Values: true, false
Changes Take Effect: Immediately

If set to true, SIP Server populates AttributeReasons in unsolicited EventAgentReady messages generated by the After Call Work (ACW) feature. If set to false, SIP Server does not populate AttributeReasons in EventAgentReady messages.

(SIP-1952, ER# 277433536)


When running on the Linux/UNIX operating system with TLS enabled, the TLS connection between SIP Server and its clients might be unstable, and SIP Server might terminate unexpectedly if the sip-tls-cipher-list configuration option was specified. To solve this issue, install Genesys Security Pack on UNIX version 8.1.300.01. (SIP-16071)


SIP Server no longer compares host names in a security certificate with the actual host name on a case-sensitive basis. Previously, a case-sensitive comparison was made, resulting in incorrect failures in authentication. To solve this issue, install Genesys Security Pack on UNIX version 8.1.300.01. (SIP-16182)


Top of Page


Release Number 8.1.101.20 [04/21/14] – Hot Fix

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 release of SIP Server is built with T-Server Common Part (TSCP) release number 8.1.010.47. TSCP is the shared software that all T-Servers and SIP Servers use. Consult the TSCP release note for information about changes to the Common Part that might affect the functionality of SIP Server.

This is a hot fix for this product. This release contains the following new feature or functionality:

Corrections and Modifications

This release does not include any corrections.

Top of Page


Release Number 8.1.101.19 [03/31/14] – Hot Fix

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 release of SIP Server is built with T-Server Common Part (TSCP) release number 8.1.010.47. TSCP is the shared software that all T-Servers and SIP Servers use. Consult the TSCP release note for information about changes to the Common Part that might affect the functionality of SIP Server.

This is a hot fix for this product. This release contains no new features or functionality.

Corrections and Modifications

This release includes the following corrections and modifications:


SIP Server now correctly parks an agent with a nailed-up connection in a race condition scenario where the BYE message is received from the external caller and the call is terminated during routing to the agent with the nailed-up connection. Previously in this scenario, SIP Server did not park the agent. (SIP-15906)


After a switchover, SIP Server now correctly generates an EventUserEvent message when it receives the MWI NOTIFY from a voicemail SIP Server. Previously in this scenario, when NOTIFY was received after the switchover, SIP Server did not generate EventUserEvent. (SIP-15812)


If a graceful shutdown command is issued while calls are in progress, a SIP Server instance running in a backup mode now correctly shuts down as soon as all calls in progress are over. Previously in this scenario, the backup SIP Server did not shut down if some calls were in progress. (SIP-15929)


Top of Page


Release Number 8.1.101.18 [03/26/14] – Hot Fix

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 release of SIP Server is built with T-Server Common Part (TSCP) release number 8.1.010.47. TSCP is the shared software that all T-Servers and SIP Servers use. Consult the TSCP release note for information about changes to the Common Part that might affect the functionality of SIP Server.

This is a hot fix for this product. This release contains no new features or functionality.

Corrections and Modifications

This release includes the following corrections and modifications:


In nailed-up connection scenarios, SIP Server now correctly establishes a new parking SIP dialog, after a switchover, if a backup SIP Server was started later than the primary, after the SIP dialog was already established. Previously, SIP Server did not preserve the nailed-up connection if a dialog to the nailed-up agent had been established on the primary SIP Server before the backup SIP Server had been started. (SIP-15815)


SIP Server now rejects a TSingleStepTransfer request if the request initiator is in the dialing state. Previously in this scenario, SIP Server did not report respective events correctly to the transfer initiator and the agent DN became stuck. (SIP-15688)


When a single-step transfer is in progress, SIP Server now acknowledges the dynamic recording request for a transferred party, immediately, but starts recording only after a destination party answers the call. Previously in this scenario, SIP Server tried to start recording before the destination party answered the call that resulted in a failed recording attempt. (SIP-15693)


When a single-step transfer initiated using the re-INVITE method fails, SIP Server now correctly retrieves the call and restores its original state. For example, if a caller is put on hold before a single-step transfer is initiated, the call is restored back to its hold state. Previously in this scenario, SIP Server did not retrieve the call properly. (SIP-15503)


Top of Page


Release Number 8.1.101.17 [03/25/14] – 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 release of SIP Server is built with T-Server Common Part (TSCP) release number 8.1.010.47. TSCP is the shared software that all T-Servers and SIP Servers use. Consult the TSCP release note for information about changes to the Common Part that might affect the functionality of SIP Server.

There are no restrictions for this release. This release contains no new features or functionality.

Corrections and Modifications

This release includes the following corrections and modifications:


When an agent initiates a consultation call by using a TInitiateTransfer or TInitiateConference request and then, when there is no response, releases it, SIP Server now allows a second attempt to initiate the consultation call to the same destination. Previously in this scenario, SIP Server rejected the second attempt with the Request already in progress error message. (SIP-15795)


When running in multi-threaded mode on the Solaris operating system, SIP Server no longer becomes unresponsive if one of the threads consumes 100% of its memory allocation. (SIP-15727)


When the monitor-consult-calls option is set to true and if a supervisor initiates intrusion monitoring when the consultation call is in the ringing phase and the main call is on hold, then SIP Server starts monitoring of the consultation call when it is established. Previously, SIP Server started monitoring of the main call on intrusion when a consultation call was in ringing state, which sometimes negatively impacted processing of a TCompleteTransfer request. (SIP-15636)


When running in multi-threaded mode, SIP Server no longer terminates unexpectedly when a connection to a USB flash drive or SAN storage on which logging occurs is broken. To avoid this issue, set the no-memory-mapping log option to true.

no-memory-mapping
Section: TServer
Default Value: false
Valid Values: true, false
Changes Take Effect: At restart

Specifies if memory-mapped files, including memory log output (with file extension .memory.log) and snapshot files (with file extension .snapshot.log), are disabled for file outputs. (SIP-15499)


Top of Page


Release Number 8.1.101.16 [03/04/14] – Hot Fix

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 release of SIP Server is built with T-Server Common Part (TSCP) release number 8.1.010.47. TSCP is the shared software that all T-Servers and SIP Servers use. Consult the TSCP release note for information about changes to the Common Part that might affect the functionality of SIP Server.

This is a hot fix for this product. This release contains no new features or functionality.

Corrections and Modifications

This release includes the following corrections and modifications:


SIP Server no longer includes the value of the display-name option configured on a Trunk DN in the To header of the INVITE message that it sends to the destination DN through this trunk. Previously, SIP Server always included the value of this option in the To header. (SIP-15293)


Top of Page


Release Number 8.1.101.15 [02/21/14] – Hot Fix

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 release of SIP Server is built with T-Server Common Part (TSCP) release number 8.1.010.46. TSCP is the shared software that all T-Servers and SIP Servers use. Consult the TSCP release note for information about changes to the Common Part that might affect the functionality of SIP Server.

This is a hot fix for this product. This release contains the following new features or functionality:

Corrections and Modifications

This release includes the following corrections and modifications:


SIP Server no longer generates EventError when processing a TSendDTMF request in a race condition. Previously, SIP Server generated EventError instead of EventDTMFSent, when an agent interrupted the announcement by sending DTMF digits from Interaction Workspace, and Media Server reached the end of announcement and sent a SIP BYE message for the announcement leg at the same time SIP Server was attempting to re-INVITE the announcement leg after the DTMF digits were collected. (SIP-15120)


SIP Server now sets off all the timers related to a treatment (START_TIMEOUT,TOTAL_TIMEOUT,DIGIT_TIMEOUT) when the treatment PlayAnnouncement and CollectDigits is completed (that is, EventTreatmentEnd is generated or the routing destination responds with 200 OK). Previously, SIP Server did not set off the DIGIT_TIMEOUT timer and the call was dropped after receiving 200 OK from the routing destination when the timer expired. This issue applied when sip-treatments-continuous=true and msml-support=true. (SIP-15481)


Top of Page


Release Number 8.1.101.10 [01/31/14] – Hot Fix

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 release of SIP Server is built with T-Server Common Part (TSCP) release number 8.1.010.46. TSCP is the shared software that all T-Servers and SIP Servers use. Consult the TSCP release note for information about changes to the Common Part that might affect the functionality of SIP Server.

This is a hot fix for this product. This release contains the following new features or functionality:

Corrections and Modifications

This release includes the following corrections and modifications:


SIP Server now correctly distributes calls to Hunt Group members after their busy state has ended, that is, as soon as they become available to accept new calls from queue. Previously, those Hunt Group members sometimes remained incorrectly in the busy state if SIP Server stayed active for at least 24 days after it started. (SIP-15436)


SIP Server now supports HTTP Digest authentication for re-INVITE messages. SIP Server generates a new re-INVITE with the authentication header in response to 401 Unauthorized or 407 Proxy Authentication challenges to the re-INVITE. Previously, SIP Server supported the authentication procedure for only initial INVITE or REFER messages. (SIP-15171)


Top of Page


Release Number 8.1.101.08 [01/21/14] – Hot Fix

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 release of SIP Server is built with T-Server Common Part (TSCP) release number 8.1.010.46. TSCP is the shared software that all T-Servers and SIP Servers use. Consult the TSCP release note for information about changes to the Common Part that might affect the functionality of SIP Server.

This is a hot fix for this product. This release contains no new features or functionality.

Corrections and Modifications

This release includes the following corrections and modifications:


SIP Server, when working in single-thread mode, no longer terminates unexpectedly while processing a two-step transfer or two-step conference request from an agent who was immediately released after submitting the TInitiateTransfer or TInitiateConference requests. (SIP-15407, SIP-15302)


SIP Server now correctly encodes the filename for a treatment to UTF-8 format in the msml body of the INFO message that is sent to MCP. Previously, SIP Server did not encode the filename to UTF-8 format, which resulted in a treatment error. (SIP-15359)


Top of Page


Release Number 8.1.101.07 [01/14/14] – Hot Fix

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 release of SIP Server is built with T-Server Common Part (TSCP) release number 8.1.010.46. TSCP is the shared software that all T-Servers and SIP Servers use. Consult the TSCP release note for information about changes to the Common Part that might affect the functionality of SIP Server.

This is a hot fix for this product. This release contains no new features or functionality.

Corrections and Modifications

This release includes the following corrections and modifications:


When msml-support is set to true, and when a treatment is requested on a Routing Point, SIP Server establishes a connection with Genesys Media Server and sends an INFO message with the msml dialog to start the treatment. If SIP Server receives the INFO message with msml.dialog.exit in response to its INFO message before 200 OK arrives, SIP Server now generates EventTreatmentApplied and EventTreatmentEnd messages. Previously, SIP Server ignored this INFO and did not generate EventTreatmentEnd. (SIP-14759)


SIP Server now correctly puts the value of the Expires header and expires parameter in the Contact header in the 200 OK response to the REGISTER Refresh request—the value is the lesser of the expires parameter present in the REGISTER request and the registrar-default-timeout configuration option. Previously, SIP Server included the incorrect expires value when generating the 200 OK response to the REGISTER Refresh request. (SIP-15348)


Top of Page


Release Number 8.1.101.06 [12/20/13] – Hot Fix

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 release of SIP Server is built with T-Server Common Part (TSCP) release number 8.1.010.46. TSCP is the shared software that all T-Servers and SIP Servers use. Consult the TSCP release note for information about changes to the Common Part that might affect the functionality of SIP Server.

This is a hot fix for this product. This release contains no new features or functionality.

Corrections and Modifications

This release includes the following corrections and modifications:


In IMS deployments where divert-on-ringing is set to false, when a call is routed to an external number, SIP Server no longer diverts the call from the Routing Point if it receives a SIP 183 Session Progress message with an SDP offer in response to the SIP INVITE sent to the external number. Now SIP Server diverts the call only after receiving a SIP 200 OK response to the INVITE sent to the external number. (SIP-13766)


SIP Server no longer forwards INFO messages containing Content-Type: application/dtmf-relay if the info-pass-through configuration option is not configured. Previously, SIP Server incorrectly forwarded these INFO messages in case of Music or PlayApplication treatments. (SIP-15093)


SIP Server now attaches the correct User Data to the call for both MSML- and NETANN-based services if the header in the INFO message contains the data in UTF-8 format. Previously, for a NETANN-based service, SIP Server encoded data characters twice and, as a result, attached the incorrect User Data to the call. (SIP-15003)


For Instant Messaging (IM) calls, a PlayAnnouncement treatment can now be requested more than five times without the call being dropped. Previously, SIP Server dropped a chat call if this treatment was requested more than five times. (SIP-15021)


Top of Page


Release Number 8.1.101.04 [12/11/13] – Hot Fix

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 release of SIP Server is built with T-Server Common Part (TSCP) release number 8.1.010.46. TSCP is the shared software that all T-Servers and SIP Servers use. Consult the TSCP release note for information about changes to the Common Part that might affect the functionality of SIP Server.

This is a hot fix for this product. This release contains no new features or functionality.

Corrections and Modifications

This release also includes the following corrections and modifications:


In MSML configurations, SIP Server now properly updates AttributeUserData and AttributeReferenceId in the EventTreatmentEnd message that is generated after a switchover of SIP Servers that happened while a treatment was in progress. Previously in this scenario, AttributeUserData and AttributeReferenceId were missing from the EventTreatmentEnd message. (SIP-14958)


If the sip-error-conversion option is configured on both Application and DN levels, SIP Server now correctly applies the DN-level value because it takes precedence. Previously, SIP Server ignored the DN-level value. (SIP-14967)


Top of Page


Release Number 8.1.101.03 [11/27/13] – Hot Fix

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 release of SIP Server is built with T-Server Common Part (TSCP) release number 8.1.010.46. TSCP is the shared software that all T-Servers and SIP Servers use. Consult the TSCP release note for information about changes to the Common Part that might affect the functionality of SIP Server.

This is a hot fix for this product. This release contains the following new features or functionality:

Corrections and Modifications

This release also includes the following corrections and modifications:


For configurations with reliable transports, SIP Server now properly retransmits 200 OK responses to an INVITE message if ACK is not received for 200 OK. To enable this functionality, use the new option sip-rel-200-retransmit.

sip-rel-200-retransmit
Section: TServer
Default Value: false
Valid Values: false, true
Changes Take Effect: For next call

Specifies if SIP Server retransmits 200 OK in response to an INVITE message on reliable transports. This option can be set at the Application and/or the DN level, with the DN-level setting overriding the value set at the Application level.

The default value of this option (false) enables the old behavior in SIP Server.

(SIP-14953)


SIP Server now properly handles T-Library requests that have been issued in quick succession while another call operation is in progress. Previously, these requests were sometimes not handled properly. For example, TCompleteTransfer was sometimes not executed while two consecutive requests for recording were being processed. (SIP-14909)


In MSML configurations for multi-site calls using the direct-uui transaction type, the supervisor can now change the supervision mode for initiated Intrusion using MuteOn/MuteOff. Previously in this scenario, changing the supervision mode for initiated Intrusion did not work properly. (SIP-14833)


In HA environments, memory allocations of a certain size (512 bytes) no longer cause unlimited memory consumption in a backup SIP Server. (SIP-5652)


Top of Page


Release Number 8.1.101.01 [11/22/13] – 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 release of SIP Server is built with T-Server Common Part (TSCP) release number 8.1.010.46. TSCP is the shared software that all T-Servers and SIP Servers use. Consult the TSCP release note for information about changes to the Common Part that might affect the functionality of SIP Server.

There are no restrictions for this release. This release contains the following new features or functionality:

Corrections and Modifications

This release also includes the following corrections and modifications:


For MSML-based recording, SIP Server now only sends additional metadata in a SIP INFO message (create conference and record) when the msml-record-metadata-support option is set to true in the TServer section at the Application level. Previously, metadata was distributed when MSML-based recording was initiated.

msml-record-metadata-support
Section: TServer
Default Value: false
Valid Values: true, false
Changes Take Effect: Immediately

Specifies whether SIP Server, while starting call recording, sends additional metadata in the INFO message to Genesys Media Server. If set to false (the default), SIP Server does not include additional metadata in the INFO message. If set to true, SIP Server sends additional metadata to the Genesys Media Server for use in Genesys Media Server file-based call recording. (SIP-14839)


SIP Server now correctly handles a re-INVITE message containing an SDP offer with the inactive attribute during a pending REFER transaction by responding with a 200 OK message containing an SDP answer with the inactive attribute. Previously, SIP Server responded with a 200 OK message containing the last-known SDP answer. (SIP-14827)


SIP Server now properly generates EventTreatmentNotApplied for the Routing Point (RP) when an ACD Queue is associated with that RP. Previously, SIP Server generated EventTreatmentNotApplied for the ACD Queue. (SIP-14652)


SIP Server now correctly parks an agent with a nailed-up connection after a consultation call is released, in the scenario where an agent initiates a consultation call to an external destination using a TInitiateConference request, and after SIP Server sends an INVITE, the agent releases the call by issuing a TReleaseCall request. Previously in this scenario, the agent connection became stuck. (SIP-14651)


In an Active-Active RM deployment, when both RMs are out-of-service and the sip-error-conversion option is configured at the Application level, if an inbound call arrives to the GVP trunk, SIP Server now correctly converts and sends the error code to the caller as configured. Previously in this scenario, SIP Server did not convert and sent the original error code, ignoring the option setting. (SIP-14596)


Top of Page


Release Number 8.1.100.98 [10/30/13] – Hot Fix

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 release of SIP Server is built with T-Server Common Part (TSCP) release number 8.1.010.45. TSCP is the shared software that all T-Servers and SIP Servers use. Consult the TSCP release note for information about changes to the Common Part that might affect the functionality of SIP Server.

This is a hot fix for this product. This release contains the following new features or functionality:

Corrections and Modifications

This release also includes the following corrections and modifications:


SIP Server now properly sends a call that has been rejected by all members of the Hunt Group to the default DN, removing that call from the ACD Queue and enabling new calls to be distributed to the members immediately after the timeout specified by the hg-busy-timeout expires. Previously, SIP Server did not send these rejected calls to the default DN, and they remained in the ACD queue, blocking all new calls from being distributed. The calls were removed from the queue only after the original call was disconnected. (SIP-14739)


SIP Server now correctly plays agent and customer greetings after dynamic recording for the call starts. Previously, greetings sometimes were not started because of a race condition between requests for greeting and dynamic recording. (SIP-14620)


SIP Server now correctly provides the same value in the Expires header and expires parameter of the Contact header in 200 OK responses to REGISTER requests. (SIP-14409)


SIP Server now releases the transferring party in the single-step transfer scenario when the REFER is Accepted, in the double-dip IMS environment where the server-role configuration option is set to 3 and the divert-on-ringing option is set to false. Previously in this scenario, SIP Server did not release the transferring party until the transfer destination answered the call. (SIP-14646)


SIP Server no longer returns an EventError "Unknown cause" message when the Authentication procedure for a REFER request fails. SIP Server will now pass a SIP response code in EventError in accordance with the map-sip-errors option setting. (SIP-4876, ER# 312768969)


SIP Server no longer starts distributing a new hunt group call until the previous call is answered by a hunt group member and gets diverted from the hunt group. Previously, SIP Server could incorrectly start distributing a new call when the previous one was still not answered. This could lead to a hunt group member having two calls ringing on his/her phone simultaneously. (SIP-16306)


Top of Page


Release Number 8.1.100.94 [10/21/13] – Hot Fix

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 release of SIP Server is built with T-Server Common Part (TSCP) release number 8.1.010.45. TSCP is the shared software that all T-Servers and SIP Servers use. Consult the TSCP release note for information about changes to the Common Part that might affect the functionality of SIP Server.

This is a hot fix for this product. This release contains the following new features or functionality:

Corrections and Modifications

This release also includes the following corrections and modifications:


SIP Server now correctly handles the situation in which Hunt Group call distribution fails if a single member DN does not have the proper SIP contact, and is therefore not registered. In this case, the call is readied for distribution to any of those member DNs that are registered; if no DNs are available within a specified timeout, the call is distributed to the DN specified by the default-dn option.
Previously, if one of more DNs in a Hunt Group were not registered with SIP Server, a call directed to that Hunt Group was stuck; it was not distributed to any members of the Hunt Group or to the default-dn. (SIP-14603)


SIP Server no longer experiences a memory leak when the timeout specified in extension AttributeTimeout of TMakePredictiveCall expires and a call is released at a Routing Point. Previously in this scenario, call objects were not released properly resulting in a memory leak. (SIP-14499)


SIP Server no longer consumes 100% CPU when processing TCP exceptions that occurred if there is only one transport for a trunk and if there are two active SIP transactions for that transport. (SIP-14678)


For Delta-Proxy IMS deployments only: SIP Server now correctly inserts the orig parameter in the Route header of INVITE messages going to a customer and does not insert it in the messages going to an agent in predictive-call scenarios. Previously, SIP Server was omitting the orig parameter in the Route header of INVITE messages going to both a customer and an agent if the ims-3pcc-prefix configuration option was defined. (SIP-14512)


SIP Server now correctly reports CPU usage for operational information on MS Windows in the SIP Server Operational Information log. It requires LCA version 8.1.300.13 and later for this log thread to be reported. (SIP-14547)


Top of Page


Release Number 8.1.100.93 [10/11/13] – Hot Fix

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 release of SIP Server is built with T-Server Common Part (TSCP) release number 8.1.010.44. TSCP is the shared software that all T-Servers and SIP Servers use. Consult the TSCP release note for information about changes to the Common Part that might affect the functionality of SIP Server.

This is a hot fix for this product. This release contains the following new features or functionality:

Corrections and Modifications

This release includes the following corrections and modifications:


SIP Server no longer terminates unexpectedly in an MSML configuration when handling TCP socket exceptions that are generated for a transport associated with multiple active transactions. (SIP-14408)


SIP Server now properly maps the AlertInfo header from a TRouteCall request to an INVITE request that it sends to members of the Hunt Group. Previously, SIP Server did not include the AlertInfo header in these requests. (SIP-14548)


SIP Server now includes the CPNDigits extension key in the INVITE request sent to Hunt Group members after a TRouteCall request (with the CPNDigits extension key) issued by URS. Previously, SIP Server did not add CPNDigits to the INVITE request sent to Hunt Group members; it only added CPNDigits to the INVITE request sent to Media Server. (SIP-14513)


SIP Server now correctly includes the dialed number in the From header of an INVITE request sent to an agent DN that issues a TMakeCall request with the CPNDigits extension key. Previously in this scenario, SIP Server replaced the destination information in the From header with CPNDigits. (SIP-14374)


SIP Server now correctly includes the dialed number in the From header of an INVITE request sent to an agent DN after an outbound call using a TMakePredictiveCall request that contains the CPNDigits extension key. Previously in this scenario, SIP Server replaced the destination information in the From header with CPNDigits. (SIP-14058)


Top of Page


Release Number 8.1.100.91 [09/27/13] – Hot Fix

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 release of SIP Server is built with T-Server Common Part (TSCP) release number 8.1.010.44. TSCP is the shared software that all T-Servers and SIP Servers use. Consult the TSCP release note for information about changes to the Common Part that might affect the functionality of SIP Server.

This is a hot fix for this product. This release contains the following new features or functionality:

Corrections and Modifications

This release includes the following corrections and modifications:


This version of SIP Server is built with TSCP 8.1.010.44, which corrects the following issue:

SIP Server can now control the scope of the requests transmitted to a Virtual Service Provider (VSP) by setting the new Application-level restricted vsp-process-udata option to true. Previously (starting in version 8.1.1), SIP Server unexpectedly started to transmit User Data requests addressed to Virtual Queues to its VSP even though it had not done so in earlier versions. This new option has been added to provide backward compatibility.

(SIP-14039)


When both the agent-greeting and customer-greeting options are configured for an Agent Login object, and the greeting-delay-events option is set to true, SIP Server now generates EventEstablished if greetings are not played. Previously, if greetings were not played because, for example, the Media Server was out-of-service, SIP Server did not generates EventEstablished and the call eventually timed out. (SIP-14305)


When MSML-based silent monitoring is in use and the Media Control Platform (MCP) on which the conference was created goes out of service, SIP Server now recovers the monitoring session using an alternate instance of MCP when it receives NOTIFY from Resource Manager about MCP failure. Previously in this scenario, SIP Server did not recover the session, even when it received NOTIFY. (SIP-14250)


SIP Server now correctly applies continuous treatments when the Media for a call has changed. Previously in this scenario, and when the sip-treatments-continuous option was set to true and the divert-on-ringing was set to false, SIP Server did not send the proper notifications, so the caller sometimes heard silence until the called party answered. (SIP-14264)


In a multi-site supervision scenario, SIP Server now generates EventMonitoringNextCall with the proper AttributeExtensions for an Agent DN that is configured in both the local and remote sites and is monitored by a supervisor in the remote site. Previously, SIP Server removed the AttributeExtensions and used the default-monitor-mode and default-monitor-scope key values in the AttributeExtensions for the EventMonitoringNextCall. (SIP-14136)


A nailed-up session is now correctly synchronized between primary and backup SIP Servers. Previously, after a switchover, SIP Server set up a new nailed-up connection to a gcti::park device. (SIP-2632, ER# 285305941)


Top of Page


Release Number 8.1.100.89 [09/16/13] – Hot Fix

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 release of SIP Server is built with T-Server Common Part (TSCP) release number 8.1.010.42. TSCP is the shared software that all T-Servers and SIP Servers use. Consult the TSCP release note for information about changes to the Common Part that might affect the functionality of SIP Server.

This is a hot fix for this product. This release contains no new features or functionality.

Corrections and Modifications

This release includes the following corrections and modifications:


SIP Server no longer terminates because of call deletion after an unsuccessful TSingleStepConference that was requested by an agent who is involved in two consultation calls with recording. Previously, the call deletion was not handled properly in memory, and SIP Server sometimes terminated unexpectedly. (SIP-14083)


SIP Server now properly handles the scenario in which a Routing Point is disabled or deleted from the Genesys configuration while it is involved in a conference call. Previously in this scenario, SIP Server became unstable and terminated unexpectedly. (SIP-14248)


In an ASM outbound call scenario, when switchover occurs immediately after Merge Call (Bridging method), SIP Server now correctly processes the re-INVITE request, received from the agent, for putting the call on hold. Previously in this scenario, SIP Server did not process the request properly. (SIP-13721)


SIP Server performance no longer decreases when the convert-otherdn option is set to +agentid. Previously, if SIP Server had a significant number of configured DNs, setting this option to +agentid caused SIP Server performance degradation. (SIP-14262)


SIP Server no longer terminates unexpectedly after receiving a T-Library message that contains a corrupted/malformed TKVList pair in AttributeUserData, and now, in this case, will reply with EventError. (SIP-14187)


SIP Server no longer terminates unexpectedly if the destination SIP Server in an ISCC transaction receives two or more events propagated by ISCC followed by ISCCEventCallDeleted while the transaction is still in progress. Previously, SIP Server sometimes entered into a loop, consuming 100% of the CPU and triggering an Out of Memory error. (SIP-14172)


Top of Page


Release Number 8.1.100.87 [09/04/13] – Hot Fix

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 release of SIP Server is built with T-Server Common Part (TSCP) release number 8.1.010.40. TSCP is the shared software that all T-Servers and SIP Servers use. Consult the TSCP release note for information about changes to the Common Part that might affect the functionality of SIP Server.

This is a hot fix for this product. This release contains no new features or functionality.

Corrections and Modifications

This release includes the following corrections and modifications:


In an IP Address Takeover high-availability configuration, where a Voice over IP Service DN is configured with the transport TCP and the oos-check option is set to a small value (that is, Active OOS is enabled), if SIP Server attempts to open a TCP connection before the VIP address is present on the host, it now tries to open the TCP connection again. Previously in this scenario, SIP Server did not retry to open the TCP connection and considered the DN as out of service. (SIP-14093)


SIP Server no longer sends EventRouteRequest to a Routing Point DN that is disabled in the configuration environment. Previously, it erroneously did. (SIP-13725)


SIP Server no longer terminates abnormally after a switchover from backup to primary mode if a call is diverted from a Routing Point to another DN when the after-routing-timeout expires. Previously, the call was not properly diverted from the Routing Point, causing SIP Server to terminate after the switchover. (SIP-13815)


SIP Server now correctly generates EventEstablished for a new call to a parked agent with a nailed-up connection when the agent is on hold. Previously in this scenario, the call was distributed to the agent but SIP Server did not generate EventEstablished. (SIP-14191)


Top of Page


Release Number 8.1.100.86 [08/23/13] – Hot Fix

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 release of SIP Server is built with T-Server Common Part (TSCP) release number 8.1.010.40. TSCP is the shared software that all T-Servers and SIP Servers use. Consult the TSCP release note for information about changes to the Common Part that might affect the functionality of SIP Server.

This is a hot fix for this product. This release contains the following new features or functionality:

Corrections and Modifications

This release includes the following corrections and modifications:


When SIP Server sends a message longer than 1024 bytes to an unreachable host that is in the same IP network sub-net, and no static ARP is configured, there will be no delay in sending the next message to the reachable destination.

In this case, you must configure the following registry on the Windows OS:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\AFD\Parameters\FastSendDatagramThreshold = (DWORD) 4096

Refer to Microsoft Windows documentation for further information: http://support.microsoft.com/kb/235257/en-us.

(SIP-2814)


If a two-step transfer is completed successfully and SIP Server receives a TReleaseCall request containing the Connection ID of the consultation call, SIP Server now rejects the request with the Event Error (Invalid Connection ID) message. Previously, SIP Server incorrectly released the main call. (SIP-6636)


Top of Page


Release Number 8.1.100.85 [08/16/13] – Hot Fix

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 release of SIP Server is built with T-Server Common Part (TSCP) release number 8.1.010.40. TSCP is the shared software that all T-Servers and SIP Servers use. Consult the TSCP release note for information about changes to the Common Part that might affect the functionality of SIP Server.

This is a hot fix for this product. This release contains no new features or functionality.

Corrections and Modifications

This release includes the following corrections and modifications:


In multi-site supervision scenarios with MSML configuration, where a supervisor at the remote site monitors an agent located at a local site, SIP Server now correctly sets the gvp:confrole for the supervisor in the INFO message: monitor (for Mute mode) or coach (for Coach mode). Previously, SIP Server did not update the gvp:confrole for the supervisor. (SIP-13724)


In the SIP Server with Active-Active RM pair deployment, SIP Server now correctly applies the oos-check when sending the OPTIONS messages to the RM pair, in cases where an MSML Voice over IP service DN is configured with the contact-list option. Previously, SIP Server did not send OPTIONS messages to the second RM in the list, if the first RM was in the active call. (SIP-13742)


In some scenarios with the softswitch configuration, where oos-force and oos-check configuration options are set to valid values, SIP Server now correctly uses the new contact information specified in the 18x early media reliable response when sending the PRACK message. Previously, SIP Server used the original contact information to send the PRACK. (SIP-13764)


If an agent with a nailed-up connection is involved in main and consultation calls that are placed on hold, and the 2nd party releases the consultation call when there is an attempt to retrieve it, SIP Server now correctly releases the consultation call and places the agent back on the main call, which remains on hold. Previously in this scenario, the agent was not re-invited to the main call. (SIP-6610)


Top of Page


Release Number 8.1.100.84 [08/09/13] – Hot Fix

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 release of SIP Server is built with T-Server Common Part (TSCP) release number 8.1.010.40. TSCP is the shared software that all T-Servers and SIP Servers use. Consult the TSCP release note for information about changes to the Common Part that might affect the functionality of SIP Server.

This is a hot fix for this product. This release contains no new features or functionality.

Corrections and Modifications

This release includes the following corrections and modifications:


If the value of the logout-on-disconnect option is set to false, SIP Server no longer terminates when an agent DN with the logged-in agent is deleted from the configuration environment. (SIP-13827)


SIP Server now responds with EventAgentLogin to consecutive TAgentLogin requests from T-Library clients, if those TAgentLogin requests contain values for the AgentID, ThisQueue, and ThisDN attributes matching those in the first TAgentLogin request. EventAgentReady and EventAgentNotReady are populated with the current agent state. Previously, SIP Server distributed EventError in response to consecutive TAgentLogin requests. (SIP-6083)


Top of Page


Release Number 8.1.100.82 [08/01/13] – Hot Fix

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 release of SIP Server is built with T-Server Common Part (TSCP) release number 8.1.010.40. TSCP is the shared software that all T-Servers and SIP Servers use. Consult the TSCP release note for information about changes to the Common Part that might affect the functionality of SIP Server.

This is a hot fix for this product. This release contains no new features or functionality.

Corrections and Modifications

This release includes the following corrections and modifications:


In multi-site scenarios, SIP Server that is located in a signaling path between other SIP Servers can now pass 183 Session in Progress messages with Advice of Charge (AoC) information. (SIP-6019)


Starting with version 8.1.100.74, SIP Server supports sending the Advice of Charge (AoC) information using 183 Session in Progress reliable provisional responses for non-established dialogs of inbound calls. This feature is enabled by setting the sip-enable-100rel option to true either at an Application level or at a DN level where setting at the DN level takes precedence. Previously, SIP Server did not enable the feature if the DN-level sip-enable-100rel option was set to true, but the Application-level sip-enable-100rel option was set to false. (SIP-6049, ER# 321260142)


SIP Server now correctly removes the capacity value from its memory when the capacity configuration option is removed from the Trunk on which it was set. Previously, SIP Server did not remove the capacity value from its memory though it was removed from the Trunk. (SIP-13626)


In a multi-site scenario using the direct-uui transaction type, SIP Server now correctly passes the X-ISCC-Id header received in a REFER request to a corresponding INVITE request, if the sip-pass-refer-headers option is set to X-ISCC-Id. Previously, SIP Server did not pass the X-ISCC-Id header, which resulted in a mismatched call. (SIP-13810)


Top of Page


Release Number 8.1.100.81 [07/26/13] – Hot Fix

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 release of SIP Server is built with T-Server Common Part (TSCP) release number 8.1.010.40. TSCP is the shared software that all T-Servers and SIP Servers use. Consult the TSCP release note for information about changes to the Common Part that might affect the functionality of SIP Server.

This is a hot fix for this product. This release contains the following new feature:

Corrections and Modifications

This release includes the following corrections and modifications:


After a switchover, SIP Server now correctly uses the Expires header provided in a REGISTER request. Previously, SIP Server did not apply the Expires header content after its switchover. (SIP-6649)


SIP Server now correctly processes incoming concurrent re-INVITE requests when the session refresh is in progress. Previously, SIP Server sometimes did not process the concurrent re-INVITEs correctly, which resulted in a dropped call. (SIP-6277)


SIP Server no longer drops an original call and correctly processes 4xx, 5xx, or 6xx SIP responses from an external destination resulting from a single-step transfer to that destination made through a Trunk configured with reuse-sdp-on-reinvite=true. Previously in this scenario, SIP Server dropped the original call after the unsuccessful transfer. (SIP-5969)


In outbound-call scenarios initiated by an agent with early media established, SIP Server now correctly handles race conditions involving 2xx successful responses between parties when the agent places the call on hold and then retrieves it. Previously in this scenario, SIP Server dropped the call. (SIP-5743, SIP-6411)


SIP Server is now able to apply an MSML-based treatment (greeting) to a call when NETANN-based recording of the established call fails because of the recorder being out-of-service. Previously in this scenario, SIP did not start other available services. (SIP-5688)


If SIP Server receives REFER with Replaces while establishing a call treatment with Media Server and a switchover occurs, the call is now correctly synchronized after the switchover. (SIP-5143)


SIP Server now correctly maps User Data containing multi-line characters (including carriage returns and line breaks) to an RFC-compliant SIP message when the userdata-map-format option is set to sip-headers-encoded on the Voice over IP Service DN. Previously, SIP Server did not map those characters correctly. (SIP-6401)


In a multi-site configuration with the route ISCC transaction type and the divert-on-ringing option set to false at an Application level, when a call arrives through an External Routing Point and is routed to an agent, and then the call is redirected to an internal Routing Point because of the no-answer timeout, SIP Server now correctly reports EventRouteUsed and EventDiverted. Previously, SIP Server did not report those events. (SIP-13645)


Top of Page


Release Number 8.1.100.80 [07/09/13] – Hot Fix

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 release of SIP Server is built with T-Server Common Part (TSCP) release number 8.1.010.40. TSCP is the shared software that all T-Servers and SIP Servers use. Consult the TSCP release note for information about changes to the Common Part that might affect the functionality of SIP Server.

This is a hot fix for this product. This release contains no new features or functionality.

Corrections and Modifications

This release includes the following corrections and modifications:


SIP Server now correctly processes geo-location information in certain msml scenarios. Previously, when SIP Server received a TApplyTreatment request that did not include geo-location in the AttributeExtensions, followed by a second TApplyTreatment request that did include the geo-location, SIP Server used only the existing (first) connection to process the treatment, making the geo-location from the second request unavailable for resource selection. Now, based on the second request, SIP Server establishes a new connection with the Resource Manager, adding the geo-location info in the X-Genesys-geo-location header, so that SIP Server is able to use geo-location when selecting Resource Manager and MCP. (SIP-6640, ER# 324893166)


SIP Server is now able to successfully recover music-on-hold (MOH) service after a high-availability (HA) switchover when it is working with an active-active Resource Manager pair configured in the contact-list mode. Previously, when a switchover occurred while MOH was playing, and the MCP used for MOH became unavailable (Resource Manager notifying SIP Server of the outage), SIP Server was unable to recover the service. Now, on getting notification from Resource Manager that the MCP is down in this scenario, SIP Server is able to successfully recover the service. (SIP-6524, ER# 323837272)


SIP Server now correctly handles call path optimization scenarios. Previously, SIP Server could experience performance degradation and memory growth in complex Inter Service Call Control (ISCC) call scenarios that involved call path optimization (out-of-service-path transfers) and ISCC loop detection (if the value of the match-call-once option was set to false). (SIP-6641, ER# 324893117)


SIP Server now correctly sends subsequent INFO messages when applying a second treatment to an available Resource Manager (RM). Previously, in active-active Resource Manager scenarios (deployed in contact-list mode), if an RM instance failed after the first treatment was applied to a call on a Routing Point, SIP Server sometimes tried to send INFO messages to the failed RM instance (even though the RM was detected as Out of Service (OOS)), causing a subsequent second treatment to fail. Now, when processing the second treatment, SIP Server sends the subsequent INFO message to the available RM instance. (SIP-6529, ER# 323895621)


SIP Server no longer incorrectly attempts to resolve the special contact ::msml setting, in cases where oos-check and oos-force options are configured on the Trunk DN. Previously, when OOS detection was enabled, SIP Server inadvertently tried to resolve the DNS name msml, resulting in failure.(SIP-6414, ER# 322798651)


Top of Page


Release Number 8.1.100.78 [06/28/13] – Hot Fix

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 release of SIP Server is built with T-Server Common Part (TSCP) release number 8.1.010.38. TSCP is the shared software that all T-Servers and SIP Servers use. Consult the TSCP release note for information about changes to the Common Part that might affect the functionality of SIP Server.

This is a hot fix for this product. This release contains the following new functionality:

Corrections and Modifications

This release includes no following corrections or modifications.

Top of Page


Release Number 8.1.100.77 [06/17/13] – Hot Fix

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 release of SIP Server is built with T-Server Common Part (TSCP) release number 8.1.010.38. TSCP is the shared software that all T-Servers and SIP Servers use. Consult the TSCP release note for information about changes to the Common Part that might affect the functionality of SIP Server.

This is a hot fix for this product. This release contains the following new functionality:

Corrections and Modifications

This release also contains the following correction or modification.


SIP Server no longer terminates unexpectedly in a multi-site scenario in which a call is routed from Site A to Site B and back to Site A, if the oosp-transfer-enabled or sip-server-inter-trunk option is set to true for the Trunks pointing to the peer SIP Servers. Previously in this scenario, SIP Server at Site A terminated unexpectedly when it received the 302 message for the second routing. (ER# 324789161)


Top of Page


Release Number 8.1.100.75 [06/07/13] – Hot Fix

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 release of SIP Server is built with T-Server Common Part (TSCP) release number 8.1.010.37. TSCP is the shared software that all T-Servers and SIP Servers use. Consult the TSCP release note for information about changes to the Common Part that might affect the functionality of SIP Server.

This is a hot fix for this product. This release contains no new features or functionality.

Corrections and Modifications

This release includes the following corrections and modifications:


In early media scenarios, SIP Server no longer starts call monitoring until a call is established between a caller and an agent. Previously, SIP Server started call monitoring immediately after Hold and Retrieve operations and before the call was established. (ER# 323631867)


SIP Server no longer drops the call in the following scenario:

  1. An agent transfers a call from a DN at SIP Server A to a Routing Point at another SIP Server B.
  2. A routing strategy at SIP Server B immediately routes the call to another destination.
  3. As a result, SIP Server A receives a 180 Ringing message followed by a 302 Moved Temporary message containing the X-Genesys-CallInfo: routed header.
Previously in this scenario, while processing the 302 Moved Temporary message, SIP Server dropped the call. (ER# 321004991, 324075882)


In blind-transfer scenarios in which an early media dialog is established with a transfer destination, and if the transfer destination rejects the call with a 603 Decline message during the transfer completion, SIP Server now correctly generates proper events after the transferring party has left the call. Previously in this scenario, SIP Server did not generate an EventAbandoned message for the transfer destination. (ER# 319948398)


SIP Server no longer terminates when receiving SIP messages without the Contact header parameters in response to the INVITE with the transport=udp parameter in the Request-URI. Previously in this scenario, SIP Server sometimes terminated. (ER# 321586860)


If, while in a conference, an agent issues TReleaseCall and TDeleteFromConference requests simultaneously, SIP Server now releases the agent from the call. Previously in this scenario, when running in the multi-threaded mode, SIP Server terminated unexpectedly. (ER# 323294813)


In predictive-call scenarios, when Call Progress Analysis (CPA) is in progress and SIP Server receives a BYE message from the outbound Trunk, SIP Server now generates an EventReleased message with the CallState attribute set to 5 (remote release) and GSW_CONNECT_TIME in the AttributeExtension. Previously, SIP Server generated EventReleased with CallState set to 0. (ER# 322871385)


For Delta-Proxy IMS deployments only: SIP Server no longer sets the orig parameter in the Route header of INVITE messages going to an agent in predictive-call scenarios. Previously in these scenarios, the orig parameter was set in the INVITE messages going to both a customer and an agent. (ER# 322871393)


In the SIP Server with Active-Active RM pair deployment using the IP-based model (using the contact-list option), when a conference is established and switchover occurs, SIP Server is now able to add or modify parties in the conference. Previously, SIP Server was not able to add or modify parties in the conference. (ER# 321932663)


Top of Page


Release Number 8.1.100.74 [05/28/13] – 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 release of SIP Server is built with T-Server Common Part (TSCP) release number 8.1.010.36. TSCP is the shared software that all T-Servers and SIP Servers use. Consult the TSCP release note for information about changes to the Common Part that might affect the functionality of SIP Server.

There are no restrictions for this release. This section describes new features that were introduced in this release of SIP Server.

Corrections and Modifications

This release also includes the following corrections and modifications:


SIP Server no longer grows in memory in the ISCC Call Overflow scenarios. Previously, when a call was routed by ISCC using the route transaction type and the Call Overflow feature was activated, SIP Server grew in memory. (ER# 322871400)


When running on the Linux, Solaris, or AIX platform, SIP Server no longer terminates unexpectedly if a TRequest is rejected because of overload conditions. (ER# 322708670)


SIP Server now successfully routes a call to default-dn if an external destination is configured as default-dn and the call is routed to the default-dn immediately after arriving on a Routing Point because of URS unavailability. Previously in this scenario, SIP Server released the call. (ER# 323036948)


SIP Server no longer terminates unexpectedly while parsing the userdata list in the header of an INFO message when the last key-value pair in the list contains only a key but no value after the "=" sign. Previously in this scenario, SIP Server terminated unexpectedly. (ER# 322461234)


SIP Server can now generate a SUBSCRIBE request if the option contact on the softswitch Voice over IP Service DN does not contain a port number. Previously in this scenario, SIP Server was unable to send the SUBSCRIBE request. (ER# 322383104)


Now, only one configuration section called log is created in the SIP Server application when the application is created using Genesys Administrator and the SIP Server XML template file. Previously in this scenario, duplicate log sections were created, one called log and one called Log. (ER# 322174205)


SIP Server no longer sends empty MWI (Message Waiting Indicator) notifications within NOTIFY messages to SIP clients, and inside EventUserEvent messages to T-Library clients, when an agent logs in or logs out. (ER# 321583241)


SIP Server is now able to retry a subscription on another Media Server in 30 seconds after SIP Server considers the TCP transport as failed. This issue applied to a single-threaded SIP Server configured with sip-link-type=0 (zero). Previously, SIP Server was unable to retry a subscription on another Media Server. (ER# 321530580)


SIP Server in high-availability mode, when integrated with Cisco Unified Communications Manager 7.1, now correctly synchronizes the agent state after a switchover occurs. Previously, if an agent was set to the Logout or NotReady state, after a switchover SIP Server erroneously set the agent back to the Login/Ready state. (ER# 321459088)


In addition to the current supported Advice of Charge (AoC) feature where SIP Server uses the INFO method to send the AoC information, SIP Server can now send the AoC information using 183 Session in Progress reliable provisional responses for non-established dialogs of inbound calls.

To enable this feature, the sip-enable-100rel option must be set to true at the origination device (Trunk) or at the SIP Server Application level. Setting this option on the device (Trunk), if configured explicitly, takes precedence over the Application-level option. SIP Server receives the AoC information in a TPrivateService message sent from a T-Library client for a non-established dialog. SIP Server maps the AoC information from TPrivateService to a 183 message instead of the INFO message. If AoC is successfully delivered, then SIP Server responds with EventACK. Otherwise, it responds with EventError.

Note: SIP Server does not enable the feature if the DN-level sip-enable-100rel option is set to true, but the Application-level sip-enable-100rel option is set to false. This issue was fixed in version 8.1.100.82.

(ER# 321260142)


SIP Server now supports the BroadWorks SIP Trunking solution by using the Network Asserted Identity mechanism for controlling the presentation of personal information (caller details) in SIP messages within a trusted network. The following SIP headers are included when SIP Server generates outgoing SIP INVITE messages:

To configure this feature, set the following configuration options:

enable-preserve-privacy
Section: TServer
Default Value: false
Valid Values: true, false
Changes Take Effect: At the next call

When set to true, the privacy service requested by an initial call is preserved during routing, transfer, consultation, and conference operations. When set to false, those operations reset the call privacy state, unless it is explicitly requested by the origination DN.

network-provided-privacy
Section: TServer
Default Value: An empty string
Valid Values: A comma-separated list of privacy type tags, such as user,id
Changes Take Effect: At the next call

DN-level option for Trunk DNs. If configured, all outgoing INVITE messages sent through the trunk are altered in the following way:

Feature Limitations:

(ER# 321260135)


The backup SIP Server no longer terminates during the creation of the 16,777,215th call if the sip-link-type option is set to 0 (zero). (ER# 321259958)


Outgoing in-dialog requests via inter-site connections (sip-server-inter-trunk must be set to true for the Trunk DN to the other SIP Server) are now routed to an active SIP Proxy that belongs to the local pool of SIP Proxies. Previously, the requests were routed to the SIP Proxy instance that was a proxy for the SIP Server that initiated the dialog. (ER# 321102491)


SIP Server now processes a SIP or T-Library NIC failure properly. By converting FQDNs to the correct IPv4 or IPv6 addresses, SIP Server can now query SIP NIC or T-Library NIC status correctly and respond appropriately. Previously, SIP Server was unable to process either failure in an IPv6 network. (ER# 321064951)


SIP Server now uses the updated value of the contact-list option of the msml VOIP Service DN and sends OPTIONS messages to the new IP address. Previously, SIP Server would not recognize the updated value, and continue to send OPTIONS messages to the previous IP address. (ER# 321060371)


For deployments in which SIP Server is integrated with SIP Proxy, SIP Server now accepts SIP requests from non-local pools of SIP Proxies. Previously, SIP requests from non-local pools of SIP Proxies were rejected. (ER# 321009721)


If the value of the logout-on-out-of-service configuration option is set to true, SIP Server now logs out an agent if the agent's DN is deleted from the configuration environment. Previously in this scenario, SIP Server became unstable. (ER# 320915874)


SIP Server now drops a call queued on a Routing Point immediately after the Routing Point is deleted from the configuration environment. Previously, SIP Server did not drop the call. (ER# 320864957)


SIP Server now drops a call queued on an ACD Queue immediately after the ACD Queue is deleted from the configuration environment. Previously, SIP Server did not drop the call. (ER# 320864800)


When SIP Server is integrated with Media Server in Active-Active RM IP mode (using the contact-list option) and contact of the Trunk object is configured as ::msml, the request URI of the INVITE sent to the Trunk now correctly contains the userpart received in the incoming INVITE. Previously, it contained the value of the msml VOIP Service DN.

In addition, if using TCP transport when the OPTIONS to one RM fails, that RM is now re-tried when it comes back into service. Previously, that RM was not re-tried.

(ER# 320082880)


SIP Server now correctly deletes old log files according to the value set in the expire option setting. Previously, logs were not removed when the value of the expire option was set to <number> of days. (ER# 319982219)


SIP Server now correctly sets AttributeReferenceID in the EventRouteUsed message in the following multi-site scenario (the route ISCC transaction type):

  1. Inbound call to SIP Server is established with an agent on the first site.
  2. The agent initiates a two-step transfer to an External Routing Point (ERP) on the second site.
  3. Treatment is applied on the ERP and the consultation call is established.
  4. The TRouteCall request is issued, and before the call is answered the TCompleteTransfer request is sent.

Previously in this scenario, the EventRouteUsed message was generated, but did not contain AttributeReferenceID.

(ER# 319982212)


In case of Active-Active RM deployment, SIP Server now sends requests to GVP using the TCP transport configured in the Trunk Group. Previously, SIP Server sent requests using UDP transport even if the Trunk Group was configured with TCP. (ER# 319329841)


SIP Server now support the values 0 and max for the num-of-licenses and num-sdn-licenses configuration options. Previously, you had to explicitly specify the number of licenses of a certain type allocated for a particular SIP Server. (ER# 319120151)


On the Linux platform, when a connection to a remote Local Control Agent (LCA) is not established, the connection on LINUX is now closed properly. Previously, the connection was not closed properly, causing SIP Server to consume 100% of the CPU.(ER# 318986320)


When SIP Server is integrated with Media Server in Active-Active RM IP mode (using the contact-list option), SIP Server no longer updates the request-uri field of the mid-dialog request when sending the request using alternate transport. Previously in this scenario, SIP Server updated the request-uri field with the contact of the new transport being used. This resulted in the request being rejected by the RM with the message 482 Loop detected. (ER# 318906020)


SIP Server now includes a correct contact header in the implicit MWI Notify message sent to the phone. Previously, the message contained an incorrect header, and a 400 Bad request error was generated on the phone. (ER# 318616855)


SIP Server now considers the recording failure INFO message received from a Media Server and retries recording with another Media Server in the following scenario:

  1. Recording is enabled in the agent.
  2. A call is established between a caller and the agent, and call recording is started.
  3. While the agent puts the caller on Hold, the Media Server sends a recording failure INFO message.

Previously in this scenario, SIP Server ignored the recording failure INFO message.

(ER# 317759174)


SIP Server is now able to deliver voicemail to the logged-in agent to the voicemail box number configured in the Extension object. SIP Server now attaches a VoiceMailbox number in the INVITE message (as the userpart of the To header) that is sent to RM. Previously, SIP Server did not use a correct VoiceMailbox number, and failed to deliver the voicemail. (ER# 317672571)


If the dial plan fails and the dial plan is set to reject, SIP Server now plays a busy tone and releases the call. Previously, for backward compatibility purposes, if the dial plan was set to reject, the sip-busy-type option had to be set to 2 for SIP Server to reject a call. This requirement no longer applies. (ER# 317237570)


SIP Server is now able to add a remote supervisor to the call. This issue occurred only if SIP Server was integrated with Media Server working by NETANN. Previously, SIP Server failed to add a remote supervisor to a call. (ER# 317204063)


Now, in a HA configuration, with sip-iptakeover-monitoring set to true, if the backup SIP Server detects that the IP address specified by the sip-address option is a duplicate of a Virtual IP address present on the backup host, the Virtual IP address down control script is executed to remove that IP address on the backup host. In that case, the Virtual IP address up control script on the primary host is executed.

Note: On the Solaris platform, if you experience duplicate Virtual IP addresses, some remote hosts may be unable to communicate with SIP Server using that Virtual IP address.

(ER# 316666221)


Top of Page


Release Number 8.1.100.64 [03/15/13] – 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 release of SIP Server is built with T-Server Common Part (TSCP) release number 8.1.010.25. TSCP is the shared software that all T-Servers and SIP Servers use. Consult the TSCP release note for information about changes to the Common Part that might affect the functionality of SIP Server.

There are no restrictions for this release. This section describes new features that were introduced in the 8.1.1 release of SIP Server.

Corrections and Modifications

This release includes the following corrections and modifications:


In No-Answer-Supervision scenarios where the NO_ANSWER_ACTION parameter is set to notready, SIP Server now correctly applies the agent status and ignores the Agent Presence notification until the agent takes an action. (ER# 261657915)


The new Application-level option, call-monitor-acw, enables the application of emulated After Call Work status to a service observer (supervisor).

call-monitor-acw
Default: false
Valid Values: true, false
Changes Take Effect: For the next call

When set to true, SIP Server applies emulated After Call Work (ACW) to a service observer (supervisor) after a call is released.

(ER# 262519207)


SIP Server now correctly processes a TPlayAnnouncementAndDigits request with a list of interruptible announcements, and controls playing the second prompt in the list by using Media Server (MSML-based services), if the first prompt is completed and no DTMF digit is received. (ER# 273090851)


SIP Server now correctly handles the following scenario where a call is placed on hold by a THoldCall request and refresh re-INVITE messages with a hold SDP arrives. Previously, if the value of the sip-cti-control option was set to talk, SIP Server misinterpreted refresh re-INVITE messages with the hold SDP as 1pcc hold operation messages. (ER# 274818145)


SIP Server now correctly releases the transferring party before sending a REFER message when performing a single-step transfer by using the pullback transaction type. Previously, if the value of the refer-enabled option was set to true, SIP Server released the transferring party after the REFER message was sent. (ER# 275904559)


SIP Server no longer disconnects a call if it is placed on hold during an agent or customer greeting. Now, when the call is placed on hold during the greeting, the greeting stream is disconnected, and the call remains on hold. (ER# 276010650)


SIP Server no longer plays a ringback tone if a treatment is already applied to the call. Previously, SIP Server incorrectly played a busy treatment and a ringback tone to the transferring party simultaneously. (ER# 276662249)


In a scenario where a Routing Point is associated with an ACD Queue, a call is routed to a busy destination DN (a 486 Busy Here message is received), SIP Server now routes the call back to the Routing Point, so the strategy on the Routing Point performs the next action for the call. Previously in this scenario, SIP Server incorrectly routed a call to both the Routing Point and the ACD Queue, which resulted in two strategies being applied to the same call. (ER# 277219813)


If a Voice over IP Service DN that is configured with the value of the use-register-for-service-state option set to true, and it is placed out-of-service, SIP Server now keeps the DN in this state until a REGISTER request for it arrives. (ER# 278526987)


If a hold re-INVITE request is issued by a media gateway, to which SIP Server replies with a 200 OK message, and if SIP Server receives a REFER request before it sends an ACK message in response to the 200 OK, SIP Server now postpones processing the REFER request until the ACK message is received. Previously in this scenario, if SIP Server received the REFER request before the ACK message, SIP Server dropped the call. (ER# 278579261)


SIP Server is now able to perform SIP-to-TLib mapping properly when the value of the mapped SIP header contains a comma. Previously, SIP Server mapped only the characters that followed the comma into the TLib UserData KVP. Now SIP Server is able to map the entire SIP header value. To activate this functionality, a device to or from which the SIP message is sent or received must be configured with the userdata-map-format option set to the value of sip-headers-encoded. (ER# 282373421)


SIP Server now continuously plays a URS busy treatment (in continuous mode) until the routing destination is answered the call. Previously in this scenario, SIP Server started to play a ringback tone when it received a 180 Ringing message from a destination DN. (ER# 284258386)


If the make-call-rfc3725-flow=2 and sip-ring-tone-mode=1 options are configured for a caller's DN, SIP Server now correctly plays a ringback tone to that caller. (ER# 285219974)


If the value of the predictive-call-router-timeout option is explicitly set to the default value of 0 (zero), SIP Server no longer incorrectly prints the Configuration option has invalid value error message in the log. (ER# 285315841)


While processing a TApplyTreatment request, SIP Server now correctly processes a 491 Request Pending from Media Server in response to an INVITE request and also correctly responds to a TRouteCall request from URS for the same call. Previously, SIP Server responded to TRouteCall with EventError. (ER# 285697658)


SIP Server now properly generates an EventPartyDeleted message, if a party, which was created by substituting the existing party while processing the INVITE with Replaces, is released. Previously in this scenario, SIP Server did not generate EventPartyDeleted. (ER# 285845167)


SIP Server no longer drops a call if during a ringback tone treatment, it receives a 302 Moved Temporarily message from a transferred destination. SIP Server now continues to process the call. (ER# 286319633)


In a scenario where a call comes through a Trunk DN that has the value of the refer-enable option set to false and the call is routed to a Trunk Group DN, after the switchover the new primary SIP Server no longer sends a REFER request, while processing the REFER request that was issued by the Trunk Group DN. (ER# 286392900)


If SIP Server does not receive an answer SDP for the offer SDP in a re-INVITE message, SIP Server now resets the SDP state to let other operations continue within the same SIP dialog. Previously in this scenario, SIP Server incorrectly left the call in the invalid state, so no operation with the SIP dialog of the call was possible. (ER# 287014753)


In multi-site call-monitoring scenarios, SIP Server now correctly generates an EventPartyDeleted message when a caller is disconnected after the conference completion with an agent at the remote site. Previously in this scenario, SIP Server did not generate EventPartyDeleted even though it generated EventPartyAdded. (ER# 289293243)


SIP Server no longer prints a duplicate total_timeout timer set message into the log. (ER# 290416312)


SIP Server now correctly applies the start_timeout timer if the USER_ANN_ID and USER_ID parameters are included in a PlayAnnouncementAndDigits treatment request. Previously in this scenario, SIP Server did not apply the start_timeout. (ER# 290509215) [Fixed Known Issue]


SIP Server now successfully applies the dial plan to a call during processing of a TRedirectCall request. Previously, SIP Server did not apply the dial plan to a call and failed to redirect the call to an external destination. (ER# 291105539)


When the graceful shutdown command is issued, SIP Server now performs graceful shut down by transiting to the suspended state, and releasing the calls. Previously, instead of graceful shutdown, SIP Server restarted as it was defined (Auto-restart) on the Start Info tab in the SIP Server Application. (ER# 291663084)


SIP Server now correctly recovers recording and conference sessions if MCP goes down. Previously, SIP Server was not able to recover the service on a second Media Server. (ER# 292439093)


When the overload control feature is enabled while SIP Server is running, the dialog rate is now calculated from the time when the overload control feature is enabled. Previously in this scenario, the dialog rate was calculated from the start of SIP Server, which led to calls being rejected because of the high dialog rate. (ER# 293054179)


When processing a TMakePredictiveCall request, SIP Server now sends the Expires header containing appropriate values in the INVITE message sent via an alternate trunk while the first selected trunk was unresponsive. Previously, SIP Server included incorrect values in the Expires header. (ER# 294647484)


SIP Server now correctly sends an ACK message in response to a 200 OK message from Media Server when the inbound leg of the call is re-INVITEd and then terminated during the MSML-based treatment. Previously in this scenario, SIP Server did not send the ACK message and attempted to initiate a new treatment to the call. (ER# 295442946)


If a DN is disabled and then deleted from the configuration environment, and SIP Server receives a TRegisterAddress request for this DN, it now generates an EventError message. Previously, SIP Server incorrectly processed registration for the deleted DN. (ER# 295771299)


SIP Server now correctly handles a scenario where a transfer destination is released from a call when a 3pcc Complete Transfer operation is in a progress. SIP Server now keeps the main call active. The problem occurred when the transfer controller DN was configured with the dual-dialog-enabled option set to false. Previously in this scenario, the main call became non-operable, and SIP Server responded to any T-Library request with EventError. (ER# 296043909)


In a multi-site scenario, SIP Server now plays greetings after completing TCompleteTransfer/TCompleteConference requests when the greetings-after-merge parameter is enabled. Previously in this scenario, SIP Server did not play greetings. (ER# 296342146)


In a call-monitoring scenario with MonitorScope set to agent, where a supervisor issues a TCancelMonitoring request and an agent performs a single-step transfer, SIP Server now correctly removes the supervisor from the call. Previously, when the supervisor canceled the monitoring session, SIP Server did not remove the supervisor from the call. (ER# 296566076)


The SIP Server Application TServer_SIPPremise_810.xml file no longer contains duplicate entries of wrap-up-time and untimed-wrap-up-value configuration options. Previously, duplicate entries caused conflict in Genesys Administrator. (ER# 296586439)


When playing a ringback tone, SIP Server now correctly selects a Voice over IP Service DN with the geo-location of the agent who initiated the TMakeCall request. Previously, when playing a ringback tone, SIP Server incorrectly selected the Voice over IP Service DN with the geo-location of the destination DN. (ER# 297747182)


In a call-monitoring scenario, if greeting and monitoring are enabled for an agent but the greeting fails, SIP Server correctly starts monitoring. Previously, in this scenario, SIP Server did not start monitoring. (ER# 298322594)


After a session refresh, SIP Server now correctly processes consecutive 3pcc requests. Previously, after a session refresh, if SIP Server received a re-INVITE request from a caller, SIP Server did not process it and responded with a 491 Request Pending message. (ER# 298519034)


SIP Server is now able to play customer or agent greetings that are requested in the TRouteCalll request sent to the remote site. Previously, these greetings were sometimes not played if the access resource number provided by the remote site was resolved to one of the available trunks, and, at the same time, the access resource name matched exactly the name of the configured but disabled trunk on the SIP Server switch. (ER# 298860730)


When handling event distribution, SIP Server no longer becomes unstable when a device with an active call, but without registered T-Library clients, was deleted from the configuration environment. (ER# 298943328)


SIP Server no longer becomes unstable in a scenario where the time specified in the agent-no-answer-timeout option expires and SIP Server redirects a call from the agent’s DN (configured with reuse-sdp-on-reinvite=true) to overflow destinations sending a REFER message only to the dialog which is fully completed. Previously, SIP Server sometimes sent a REFER message to the dialog that had an non-acknowledged re-INVITE transaction. (ER# 299261303)


If, when applying a treatment to a call, SIP Server gets a 488 error response from a gateway, SIP Server now parks the call once and does not attempt to re-apply the treatment. Previously, SIP Server attempted to park the call each time it received the 488 error message, which led to an infinite loop of the message exchange between SIP Server and the gateway. (ER# 299843510)


When SIP Server functions as an application server behind a softswitch and the softswitch responds with a 408 Request Timeout message, SIP Server now correctly places a DN in out-of-service state. After the recovery-timeout (configured on the Voice over IP Service DN with service-type=softswitch) setting expires, SIP Server places the DN back in service. Previously in this scenario, SIP Server did not place the DN back in service. (ER# 300521299, 300606487)


In a multi-site scenario where a call is routed from Site A to Site B using the ISCC route transaction type, and the greeting parameters are specified in the TRouteCall request, the agent greeting is only played by SIP Server at Site B. Previously in this scenario, SIP Server at Site A and SIP Server at Site B simultaneously engaged Stream Managers to play the greeting. (ER# 300633942, 303202526)


SIP Server now correctly prints the total Trunk capacity in the log. Previously, SIP Server printed the incorrect value of the total capacity of the Trunk, which had the capacity-group option configured but not the capacity option. (ER# 300638934)


SIP Server no longer treats inbound calls as business calls in multi-site scenarios when the option propagated-call-type is set to true and the option internal-bsns-calls is set to false. This means that the agent does not go into the AgentNotReady state after the call is released. The issue occurred when the Switch Partitioning functionality was enabled (the dn-scope option was set to tenant).

Limitations

(ER# 301478945)


When processing a TRouteCall (RouteTypeDefault) request that requires delivering a call to a default destination, SIP Server checks for the default-dn configuration option that might be specified in the following locations, in order of priority:

  1. Routing Point DN
  2. SIP Server Application level
Previously, SIP Server did not check the Routing Point configuration and routed the call to the default-dn destination specified at the Application level. (ER# 301789073)


SIP Server now properly handles a User-Agent Extension attribute in TRouteCall requests. Previously, SIP Server incorrectly added duplicated User-Agent headers when sending INVITE messages. (ER# 301864233)


SIP Server no longer cancels the dialog with MSML-based services to apply a treatment when it receives a PRACK message for an inbound leg of the call after the msml dialog is initiated in response to a TApplyTreatment request. (ER# 302221846)


If the value of the sip-ring-tone-mode configuration option is set to 1, SIP Server no longer simultaneously plays a ringtone and a treatment that was already applied to a call. (ER# 302446624)


For NETANN-based services with Genesys Media Server, SIP Server passes received digits in the INFO message without any conversion to the code (as it does with Stream Manager). Now SIP Server does not convert the non-digit characters * and # to DTMF(0). (ER# 303202549)


In a multi-site scenario, SIP Server now correctly sets the CallState attribute to OK (0) in EventQueued messages if it receives a 302 Moved Temporarily message from another SIP Server after a multi-site route. Previously in this scenario, SIP Server incorrectly set the CallState to Forwarded (23). (ER# 304149137)


In a multi-site call-monitoring scenario where:

  1. Intrusion is enabled and MonitorMode is set to mute,
  2. An agent is on a call, which is monitored by a supervisor located at another site,
  3. The supervisor cancels the monitoring, and then issues the TMonitorNextCall request with MonitorMode set to coach for the same agent.
SIP Server now accepts the TMonitorNextCall request from the supervisor. Previously in this scenario, SIP Server rejected the TMonitorNextCall request. (ER# 304510594)


SIP Server no longer rejects 3pcc requests containing blank spaces in destination DN names.It executes the 3pcc requests by truncating the blank spaces. (ER# 307294336)


When, after a single-step conference of a call to a Routing Point while the treatment is in progress, a caller is disconnected from the call, SIP Server correctly processes an incoming TRouteCall request with RejectRouteType and disconnects parties from the call. Previously, SIP Server generated an EventError message. (ER# 308070301)


If the value of the sip-enable-sdp-codec-filter configuration option is set to true and SIP Server processes multi-part content SDPs, SIP Server now correctly filters SDPs based on the specified codecs. Previously in this scenario, SIP Server did not filter the codecs correctly, which resulted in dropped calls. (ER# 308232199)


SIP Server now correctly exchanges session re-INIVTE messages while processing a call with a treatment. Previously, because of network issues, SIP Server did not process the call correctly, which resulted in a stuck call. (ER# 308509325)


SIP Server no longer rejects a call containing the Content-Type=multipart/mixed in an INVITE request. Previously, SIP Server generated an EventError message. (ER# 309203586)


In a predictive-call scenario involving a treatment by NETANN-based services, SIP Server no longer rejects the second TApplyTreatment request if the NETANN-based service replies to the first TApplyTreatment request with the BYE message. (ER# 310815935)


A primary SIP Server now correctly synchronizes RTP monitoring information with the backup SIP Server, even if the backup SIP Server was not running when the primary SIP Server received a subscription (TPrivateService request) for RTP monitoring information. As a result, after the backup SIP Server becomes the new primary, it is able to distribute RTP monitoring information in the EventUserEvent message. Previously, SIP Server synchronized the RTP monitoring information only if the backup SIP Server was running. (ER# 311006592)


SIP Server no longer drops a consultation call to an external destination if the external destination responds with a 302 Moved Temporarily message while playing a ringback tone to a transfer control party. (ER# 311629789)


SIP Server now correctly generates an EventError message if a single-step conference is made to an unresponsive DN. Previously, SIP Server correctly terminated conference dialogs and reconnected the caller with an agent, but it did not generate EventError. (ER# 311878826)


SIP Server no longer terminates a call in a scenario involving a ringback tone on an endpoint and early media on a destination. (ER# 312023908)


SIP Server now attaches the correct UserData if the Content-Type is application/vnd.radisys.msml+xml and the header in the INFO message contains the data in non-UTF-8 format. Previously, SIP Server converted the data to the UTF-8 format twice, and as a result, attached the incorrect UserData to the call. (ER# 313635841)


SIP Server now correctly forwards an INVITE message with the UserData to a Media Server when it completes a transfer while the treatment (NETTANN-based) is in progress by processing the INVITE message with the Replaces header. Previously in this scenario, SIP Server did not attach the UserData when sent the request to Media Server. (ER# 314294955)


In an Outbound VOIP environment, when processing TMergeCalls with the Extension attribute method set to bridging, SIP Server now correctly bridges the call legs. Previously, SIP Server after the bridging immediately disconnected the call legs and sent the re-INVITEs to both call participants to restore the call, causing the delay in connection of the call participants. (ER# 314972576)


SIP Server now, when sending a 200 OK response for the established dialog, includes all supported request methods (INVITE, ACK, PRACK, CANCEL, BYE, REFER, INFO, UPDATE, MESSAGE, NOTIFY, OPTIONS) in the Allow header to a media gateway. Previously, SIP Server included only a limited set of request methods as in the previous 18x provisional response. (ER# 315060681)


SIP Server now escapes the reserved character = in the URI parameters of an INVITE message that is received in the form dn=msml= for call recording. Previously, SIP Server did not escape the reserved character that caused incorrect call handling by GVP. (ER# 315202909)


SIP Server now terminates a call leg established with Media Server (for playing a ringback tone) after the call is established with the agent using a dummy SDP. Previously in this scenario, SIP Server dropped the call. (ER# 315951629)


SIP Server now correctly processes a scenario in which the ringback tone (sip-ring-tone-mode=1) to be played to a caller fails. SIP Server now keeps the call until the agent answers. Previously, when a Media Server responded with an error, SIP Server sent a BYE message to the caller and a CANCEL message to the agent leg. (ER# 283915697, 316899513)


When a two-step conference is successfully completed and SIP Server sends an INFO message to the MCP but receives an error response instead, SIP Server now correctly reports the DN of the agent who initiated the conference, as the value of the ThirdPartyDN attribute in the EventPartyAdded message. Previously, SIP Server incorrectly reported a caller DN as the ThirdPartyDN attribute value. (ER# 317241516)


SIP Server now updates the contact of the SIP endpoint in the configuration environment only if it is different from the contact received in the previous REGISTER message. Previously, SIP Server updated the contact each time the endpoint sent the refresh REGISTER message, which led to minor usability issues. (ER# 317779268)


If a DN subscribes to a message-summary event, but the DN has no mailbox configured (option gvm_mailbox), SIP Server accepts the subscription and no longer sends a NOTIFY message. (ER# 299401974)


When sending an outbound INVITE request, SIP Server will generate a P-Asserted-Identity header from the P-Asserted-Identity header that was included in the incoming INVITE if the enforce-privacy option is not configured on the outbound Trunk DN. Previously in this scenario, SIP Server sometimes did not generate a P-Asserted-Identity header. (SIP-14559)

Top of Page


Release Number 8.1.001.30 [09/06/13] – Hot Fix

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 release of SIP Server is built with T-Server Common Part (TSCP) release number 8.1.001.68. TSCP is the shared software that all T-Servers and SIP Servers use. Consult the TSCP release note for information about changes to the Common Part that might affect the functionality of SIP Server.

This is a hot fix for this product. This release contains no new features or functionality.

Corrections and Modifications

This release includes the following corrections and modifications:


SIP Server no longer terminates unexpectedly after receiving a T-Library message that contains a corrupted/malformed TKVList pair in AttributeUserData, and now, in this case, will reply with EventError. (SIP-13670)


SIP Server no longer terminates unexpectedly after a switchover from backup to primary mode if a call is diverted from a Routing Point to another DN when the after-routing-timeout expires. Previously, the call was not properly diverted from the Routing Point, causing SIP Server to terminate after the switchover. (SIP-6622)


SIP Server no longer terminates unexpectedly if the destination SIP Server in an ISCC transaction receives two or more events propagated by ISCC followed by ISCCEventCallDeleted while the transaction is still in progress. Previously, SIP Server sometimes entered into a loop, consuming 100% of the CPU and triggering an Out of Memory error. (SIP-6621)


If an agent with a nailed-up connection is involved in main and consultation calls that are placed on hold, and if during an attempt to retrieve a consultation call the second party releases the consultation call, SIP Server now correctly releases the consultation call and places the agent back on the main call, which remains on hold. Previously in this scenario, the agent was not re-invited to the main call. (SIP-6611)


Top of Page


Release Number 8.1.001.29 [05/23/13] – Hot Fix

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 release of SIP Server is built with T-Server Common Part (TSCP) release number 8.1.001.61. TSCP is the shared software that all T-Servers and SIP Servers use. Consult the TSCP release note for information about changes to the Common Part that might affect the functionality of SIP Server.

This is a hot fix for this product. This release contains no new features or functionality.

Corrections and Modifications

This release includes the following corrections and modifications:


In early media scenarios, SIP Server no longer starts call monitoring until a call is established between a caller and an agent. Previously, SIP Server started call monitoring immediately after Hold and Retrieve operations and before the call was established. (ER# 320474711)


Top of Page


Release Number 8.1.001.28 [05/16/13] – Hot Fix

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 release of SIP Server is built with T-Server Common Part (TSCP) release number 8.1.001.61. TSCP is the shared software that all T-Servers and SIP Servers use. Consult the TSCP release note for information about changes to the Common Part that might affect the functionality of SIP Server.

This is a hot fix for this product. This release contains no new features or functionality.

Corrections and Modifications

This release includes the following corrections and modifications:


SIP Server no longer grows in memory in the ISCC Call Overflow scenarios. Previously, when a call was routed by ISCC using the route transaction type and the Call Overflow feature was activated, SIP Server grew in memory. (ER# 321694858)


Top of Page


Release Number 8.1.001.27 [05/08/13] – Hot Fix

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 release of SIP Server is built with T-Server Common Part (TSCP) release number 8.1.001.61. TSCP is the shared software that all T-Servers and SIP Servers use. Consult the TSCP release note for information about changes to the Common Part that might affect the functionality of SIP Server.

This is a hot fix for this product. This release contains no new features or functionality.

Corrections and Modifications

This release includes the following corrections and modifications:


For Delta-Proxy IMS deployments only: SIP Server no longer sets the orig parameter in the Route header of INVITE messages going to an agent in predictive-call scenarios. Previously in these scenarios, the orig parameter was set in the INVITE messages going to both a customer and an agent. (ER# 314313212)


In predictive-call scenarios, when Call Progress Analysis (CPA) is in progress and SIP Server receives a BYE message from the outbound Trunk, SIP Server now generates an EventReleased message with the CallState attribute set to 5 (remote release) and GSW_CONNECT_TIME in the AttributeExtension. Previously, SIP Server generated EventReleased with CallState set to 0. (ER# 320063213)


Top of Page


Release Number 8.1.001.26 [04/26/13] – Hot Fix

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 release of SIP Server is built with T-Server Common Part (TSCP) release number 8.1.001.61. TSCP is the shared software that all T-Servers and SIP Servers use. Consult the TSCP release note for information about changes to the Common Part that might affect the functionality of SIP Server.

This is a hot fix for this product. This release contains no new features or functionality.

Corrections and Modifications

This release includes the following corrections and modifications:


If, while in a conference, an agent issues TReleaseCall and TDeleteFromConference requests simultaneously, SIP Server now releases the agent from the call. Previously in this scenario, when running in the multi-threaded mode, SIP Server terminated unexpectedly. (ER# 320766840)


SIP Server now supports version 11.9 of the FLEXlm client library, which is fully compatible with the previous version 9.5 of the FLEXlm license manager. Previously, this incompatibility sometimes caused SIP Server to terminate unexpectedly. (ER# 315850077)


Top of Page


Release Number 8.1.001.25 [04/11/13] – Hot Fix

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 release of SIP Server is built with T-Server Common Part (TSCP) release number 8.1.001.57. TSCP is the shared software that all T-Servers and SIP Servers use. Consult the TSCP release note for information about changes to the Common Part that might affect the functionality of SIP Server.

This is a hot fix for this product. This release contains no new features or functionality.

Corrections and Modifications

This release includes the following corrections and modifications:


SIP Server in high-availability mode, when integrated with Cisco Unified Communications Manager 7.1, now correctly synchronizes the agent state after a switchover occurs. Previously, if an agent was set to the Logout or NotReady state, after a switchover SIP Server erroneously set the agent back to the Login/Ready state. (ER# 320478391)


Top of Page


Release Number 8.1.001.24 [04/09/13] – Hot Fix

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 release of SIP Server is built with T-Server Common Part (TSCP) release number 8.1.001.57. TSCP is the shared software that all T-Servers and SIP Servers use. Consult the TSCP release note for information about changes to the Common Part that might affect the functionality of SIP Server.

This is a hot fix for this product. This release contains the following new features or functionality:

Corrections and Modifications

This release includes the following corrections and modifications:


The backup SIP Server no longer terminates during the creation of 16777215th call if the sip-link-type option is set to 0. (ER# 319151591)


Top of Page


Release Number 8.1.001.22 [03/14/13] – Hot Fix

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 release of SIP Server is built with T-Server Common Part (TSCP) release number 8.1.001.57. TSCP is the shared software that all T-Servers and SIP Servers use. Consult the TSCP release note for information about changes to the Common Part that might affect the functionality of SIP Server.

This is a hot fix for this product. This release contains no new features or functionality.

Corrections and Modifications

This release includes the following corrections and modifications:


SIP Server now correctly sets the AttributeReferenceID to the EventRouteUsed in the following multi-site scenario (the route ISCC transaction type):

  1. Inbound call to SIP Server is established with an agent on the first site.
  2. The agent initiates a two-step transfer to an External Routing Point (ERP) on the second site.
  3. Treatment is applied on the ERP and the consultation call is established.
  4. The TRouteCall request is issued, and before the call is answered the TCompleteTransfer request is sent.

Previously in this scenario, the EventRouteUsed message was generated, but did not contain the AttributeReferenceID. (ER# 315293468)


SIP Server now correctly deletes old log files according to the value set in the expire option setting. Previously, logs were not removed when the value of the expire option was set to <number> of days. (ER# 318288685)


SIP Server no longer terminates a TRouteCall operation when a DTMF event is sent during a multi-prompt, interruptible treatment. Previously in this scenario, SIP Server could incorrectly start to execute a new prompt and terminate routing. (ER# 304489007)


Top of Page


Release Number 8.1.001.19 [02/14/13] – Hot Fix

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 release of SIP Server is built with T-Server Common Part (TSCP) release number 8.1.001.47. TSCP is the shared software that all T-Servers and SIP Servers use. Consult the TSCP release note for information about changes to the Common Part that might affect the functionality of SIP Server.

This is a hot fix for this product. This release contains no new features or functionality.

Corrections and Modifications

This release includes the following corrections and modifications:


SIP Server now correctly releases the nailed-up connection if the registration expires or if the device is unregistered, placing a corresponding DN in out-of-service status. Previously, SIP Server did not release the nailed-up connection for an out-of-service DN. (ER# 316589773)


Top of Page


Release Number 8.1.001.17 [02/01/13] – Hot Fix

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 release of SIP Server is built with T-Server Common Part (TSCP) release number 8.1.001.47. TSCP is the shared software that all T-Servers and SIP Servers use. Consult the TSCP release note for information about changes to the Common Part that might affect the functionality of SIP Server.

This is a hot fix for this product. This release contains no new features or functionality.

Corrections and Modifications

This release includes the following corrections and modifications:


SIP Server now correctly terminates a recording session of main and consultation calls if the parties that are left on the call after the call transfer do not have recording enabled. Previously in this scenario, SIP Server erroneously continued a recording session after the recording-enabled party disconnected from the transferred call. (ER# 316425852)


Top of Page


Release Number 8.1.001.16 [01/25/13] – Hot Fix

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 release of SIP Server is built with T-Server Common Part (TSCP) release number 8.1.001.47. TSCP is the shared software that all T-Servers and SIP Servers use. Consult the TSCP release note for information about changes to the Common Part that might affect the functionality of SIP Server.

This is a hot fix for this product. This release contains no new features or functionality.

Corrections and Modifications

This release includes the following corrections and modifications:


SIP Server no longer incorrectly includes the supervisor in the call when:

Previously in this scenario, SIP Server incorrectly included the supervisor in the call. (ER# 315288019)


SIP Server now deletes the START_TIMEOUT when the TOTAL_TIMEOUT expires before the START_TIMEOUT during PlayAndCollectDigit treatments when sip-treatment-continuous mode is enabled. (ER# 314146737)


SIP Server now correctly generates an EventTreatmentEnd message when digits are received for TreatmentPlayAnnouncementAndDigits, even if the TreatmentPlayAnnouncementAndDigits is restarted because an INVITE with replaces for the original call is received (in other words, a consultation call transforms to a main call, 1pcc two-step transfer). Previously, SIP Server did not generate the EventTreatmentEnd message in this scenario. (ER# 315938599)


Top of Page


Release Number 8.1.001.15 [01/15/13] – 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 release of SIP Server is built with T-Server Common Part (TSCP) release number 8.1.001.47. TSCP is the shared software that all T-Servers and SIP Servers use. Consult the TSCP release note for information about changes to the Common Part that might affect the functionality of SIP Server.

There are no restrictions for this release. This release contains the following new features or functionality:

Corrections and Modifications

This release includes the following corrections and modifications:


In outbound-call s