Release Note

Contents

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 7.5 releases of Network SIP Server.

• Links in the Contents section enable you to access information regarding a specific release. Releases are listed by version number rather than in date order. For this reason, a recent release may be listed after earlier releases, if the version number is lower. Except when otherwise noted in the information for a specific release, each release includes all of the features and corrections that were introduced for the applicable operating system at earlier dates, regardless of the version numbering.
• The Release Number table lists the supported operating systems for each release at a high level. For more detailed information, see the Genesys Supported Operating Environment Reference Guide.
• The Known Issues and Recommendations section is a cumulative list. It includes information on when individual items were found and, if applicable, corrected.
• The Corrections and Modifications section for each release may list additional issues that were corrected without first being documented as Known Issues.
• The Discontinued Support section is cumulative. It lists functionality that is no longer supported and the release number of the version in which support was discontinued.
• You can find information about changes and corrections to functionality common to all T-Servers in the release note for T-Server Common Part release 7.5.x and T-Server Common Part release 8.0.x.

Use of Third-Party Software

Genesys follows applicable third-party redistribution policies to the extent that Genesys solutions utilize third-party functionality. Please contact your Genesys Customer Care representative if you have any questions.

Supported Operating Systems

New in This Release

Note: This version was first released as a Hot Fix on 11/13/14.

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

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

To migrate your environment from Network SIP Server to use 8.1.1 SIP Server, refer to the Migrating from Network SIP Server to SIP Server article for details. This article describes differences between the two components (Network SIP Server and SIP Server), and describes migration use cases, with migration steps, that might apply to your environment.

Corrections and Modifications

This release includes the following corrections and modifications:

If during call routing Network SIP Server receives an ISCCEventPartyChanged message from the T-Server originating a call, Network SIP Server now correctly generates EventPartyChanged and properly routes the call. After successfully routing the call, Network SIP Server then generates EventRouteUsed containing the same ConnectionID as EventPartyChanged. Previously in this scenario, Network SIP Server sometimes rejected a TRouteCall request containing a non-empty AttributeLocation. (NWSIPSVR-149 )

Top of Page

Supported Operating Systems

New in This Release

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:

Network SIP Server no longer terminates while processing the URS register attempt for a Routing Point that is deleted from the configuration environment. Previously, in rare cases, Network SIP Server terminated. (ER# 302629058)

Top of Page

Supported Operating Systems

New in This Release

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

• Network SIP Server now supports the new configuration option, enable-sip-port-on-backup.
  
  enable-sip-port-on-backup
  Default Value: true
  Valid Values: true, false
  Changes Take Effect: After restart
  
  This option specifies whether Network SIP Server closes its SIP port when it runs in the backup mode. When set to true (the default), Network SIP Server opens the SIP port (the backward compatibility mode). When set to false, Network SIP Server closes the SIP port if it runs in the backup mode. (ER# 296586598)

• Network SIP Server now supports two additional values of the parameter-n option in the Extensions section: Diversion and X-Genesys-Custom.
  
  If the parameter-n option is set to Diversion and/or X-Genesys-Custom, Network SIP Server passes the content of headers Diversion and/or X-Genesys-Custom, respectively, from the SIP message to the AttributeExtensions of EventRouteRequest. (ER# 298071781)

Corrections and Modifications

This release includes the following corrections and modifications:

If Network SIP Server is configured on the default SIP port (5060) and receives an incorrect packet from the network, it no longer consumes about 100 percent CPU. Previously in this scenario, Network SIP Server fell in a request-response loop (to itself), which resulted in increased memory utilization. (ER# 293951126)

Top of Page

Supported Operating Systems

New in This Release

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 version of SIP Server is built with TSCP 8.0.101.19, which corrects the following issue:

SIP Server no longer becomes unstable if a new connection to it is configured in a client application and then immediately removed (in the Configuration Layer), while SIP Server is still processing data related to the added connection. (ER# 288576838)

Top of Page

Supported Operating Systems

New in This Release

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

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

Corrections and Modifications

This release contains the following corrections or modifications:

Network SIP Server no longer rejects INVITE requests that contains a Max-Forwards header value 0 with the 503 (Service Unavailable) error response. Network SIP Server will now always reject such a request with the 483 (Too Many Hoops) error response. (ER# 286077568)

The Component Name (Network SIP Server) is now correctly printed in the log file. (ER# 279525831)

URS strategy can now control how Network SIP Server generates SIP response codes by sending a TRouteCall request with the RouteTypeReject parameter. If the AttributeOtherDN of such a request contains a string of digits in the range of 400 to 699, Network SIP Server responds to an incoming INVITE message with a SIP response code equal to the AttributeOtherDN. Otherwise, Network SIP Server responds with a 603 Decline SIP response code. (ER# 292550331)

Top of Page

Supported Operating Systems

New in This Release

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

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

Corrections and Modifications

This release contains the following corrections or modifications:

This version of Network SIP Server is built with TSCP 8.0.101.17, which corrects the following issue:

In rare scenarios, involving dynamic update of Host objects in the configuration environment, Network SIP Server no longer becomes unstable. (ER# 278120314, 281482191)

Top of Page

Supported Operating Systems

New in This Release

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

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

• Network SIP Server is built with TSCP release number 8.0.101.12 to incorporate the Transaction Monitoring feature. (ER# 272322411)

• Network SIP Server can now add a custom SIP header in 302 Moved Temporarily messages by using the SIP_HEADERS key in AttributeExtensions.

  No changes are required to the configuration of the Network SIP Server Application object. All mapping information is provided in the TRouteCall request that is created by the URS routing strategy and sent to Network SIP Server.

  The TRouteCall request must contain the SIP_HEADERS key to trigger T-Library-to-SIP mapping in Network SIP Server. The SIP_HEADERS key contains a list of extension names of TRouteCall to be mapped to the outgoing SIP message as headers. Header values must be also specified in the TRouteCall request.

  Example

  This example demonstrates how mapping works in Network SIP Server when it receives the following TRouteCall request:

  message RequestRouteCall
AttributeThisDN '5000'
AttributeConnID 006e01886c3d7001
AttributeOtherDN 'sip:21101@sip1@genesyslab.com'
AttributeExtensions[371] 00 0B 00 00..
'SIP_HEADERS' 'Header-1,Header-2'
'Header-1' 'Value-1'
'Header-2’ 'Value-2'
AttributeDNIS '5000'
AttributeRouteType 1 (RouteTypeDefault)
AttributeReferenceID 9

  This message contains the SIP_HEADERS key, which forces Network SIP Server to look for pairs Header-1 and Header-1 and to add them as additional headers inside the redirect response:

  SIP/2.0 302 Moved Temporarily
From: ;tag=6DC234B3-826E-4333-94F3-FA24F0286E90-1
To: sip:47000@192.168.14.116:5080;tag=263687D4
Call-ID: F0C994F4-9D4D-40F0-875E-1BC99996005C-1@192.168.14.116
CSeq: 1 INVITE
Via: SIP/2.0/UDP 192.168.14.116:6001;branch=z9hG4bKECC4F4E9-CA3E-45E9-B90E-24721C971102-1
Contact: sip:21101@sip1@genesyslab.com
Header-1: Value-1
Header-2: Value-2
Content-Length: 0

  (ER# 272322318)

Corrections and Modifications

This release does not contain any corrections or modifications.

Top of Page

Supported Operating Systems

New in This Release

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

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

• Name resolution through DNS. To support hostname resolution through DNS, a new Application-level option resolve-sip-address has been introduced.

  resolve-sip-address
  Default Value: false
  Valid Values: true, false
  Changes Take Effect: After restart
  
  If set to true, Network SIP Server will resolve the hostname in the OtherDN URI of the RequestRouteCall to its corresponding IPv4 address, which it then uses in the 302 Contact message. Resolution through DNS is only done once, and will be stored in the internal server table. The corresponding IPv4 address will be extracted from this table for any similar subsequent RequestRouteCall. SIP Server must be restarted for a new IP address to be assigned to an FQDN. (ER# 269673782)

Corrections and Modifications

This release includes no corrections or modifications.

Top of Page

Supported Operating Systems

New in This Release

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

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

Corrections and Modifications

This release contains the following corrections and modifications:

Network SIP Server can now be installed properly, using build 2, on Linux 4 and 5 platforms. (ER# 247512871)

Network SIP Server now correctly reports status of registered devices in the Extensions attribute in EventRegistered messages. Previously, Network SIP Server reported devices registered other than RouteDN as out-of-service (with a value set to 128). This issue applied to Network SIP Server version 7.5.000.05 and later. (ER# 209866628)

Top of Page

Supported Operating Systems

New in This Release

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

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

• Network SIP Server now supports the default-route-destinations configuration option at the Switch/DN level, in the TServer section:

  default-route-destinations
  Default Value: Empty string
  Valid Values: List of valid SIP URIs (Uniform Resource Identifier) separated by commas, spaces, or semicolons
  Changes Take Effect: Immediately

  Specifies a list of valid SIP URIs for destinations to which calls are routed when Universal Routing Server (URS) is not operational, or when the timeout specified in the Application-level option, router-timeout, expires. The destinations are selected from the list in a cyclic manner. In scenarios when URS is not operational or all the clients that are registered are in Monitor mode, the router-timeout option value will be ignored and default routing will be performed immediately.

  Note: The option settings at the Switch/DN level take precedence over the Application level setting.

  (ER# 1197181305)

Corrections and Modifications

No corrections or modifications were made in this release.

Top of Page

Supported Operating Systems

New in This Release

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

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

• This version of Network SIP Server introduces the following new Application-level option to set a default routing destination.

  default-route-destinations
  Default Value: Empty string
  Valid Values: List of valid SIP URIs (Uniform Resource Identifier)
  Changes Take Effect: Immediately

  Specifies a list of valid SIP URIs (Uniform Resource Identifier) for destinations to which calls are routed when Universal Routing Server (URS) is not operational, or when the timeout specified in the router-timeout option expires. The destinations are selected from the list in a cyclic manner. In scenarios when URS is not operational or all the clients that are registered are in Monitor mode, the router-timeout option value will be ignored and default routing will be performed immediately.

  Note: Valid delimiters in the list are commas, spaces, and semicolons.

  (ER# 173109811)

• Network SIP Server now performs Call Monitoring in a compatible manner for ICON. (ER# 160445255)

Corrections and Modifications

No corrections or modifications were made in this release.

Top of Page

Supported Operating Systems

New in This Release

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

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

• Network SIP Server supports the OPTIONS SIP request. Network SIP Server will return a 200 OK SIP message as a response to that request.

Corrections and Modifications

No corrections or modifications were made between Release 7.2 or earlier releases and the initial 7.5 release.

Top of Page

Known Issues and Recommendations

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

Network SIP Server may not be installed properly on Linux 4 and 5 platforms. (ER# 247512871)

In the Framework 7.5 Network SIP Server Deployment Guide, on page 128, the Note is incorrectly documented. Use the following description instead:

Note: Hot-standby HA is not currently supported for Network SIP Server.

(ER# 275704946)

The Framework 7.5 Network SIP Server Deployment Guide omits the following information:

final-timeout
Default Value: 0
Valid Values: 0, or any positive integer
Changes Take Effect: Immediately

Specifies the maximum time interval, in milliseconds, during which Network SIP Server does not delete a call after processing it. This timeout allows Network SIP Server to wait for call rerouting attempts from SIP gateways.

num-of-rerouting
Default Value: 11
Valid Values: Any positive integer
Changes Take Effect: Immediately

Specifies the maximum number of attempts to reroute a call. If Network SIP Server receives an INVITE message that belongs to an existing call (based on the CallID attribute) from a SIP gateway, it initiates an attempt to reroute the call. When the number of rerouting attempts specified by this configuration option is reached, Network SIP Server responds with a 480 (Temporarily Unavailable response) message. The time interval, during which a reroute attempt could be applied to a call, is specified by the final-timeout configuration option.

load-balancing
Default Value: yes
Valid Values: yes, no
Changes Take Effect: At the next incoming INVITE

If this option is set to yes, T-Server ignores the UserName part of the Request URI from incoming SIP messages and uses a Routing Point from the pool of registered Routing Point DNs. If the pool of registered Routing Point DNs is empty, T-Server uses a Routing Point from the pool of configured and not disabled Routing Points DNs and sets default routing for it (the destination is specified by the default-route-destinations configuration option). In previous releases, this was the only possible way to choose a Routing Point. If this option is set to no, T-Server generates EventRouteRequest on behalf of the Routing Point, the value of which is equal to the UserName part of the Request URI.

Note: Genesys recommends that you set this option to no if you intend to use the ISCC feature.

(ER# 187276314, 238336351)

Top of Page

Discontinued Support

This section documents features that are no longer supported in this software. This cumulative list is in release-number order with the most recently discontinued features at the top of the list. For more information on discontinued support for operating environments and databases, see Discontinued Support in the Genesys Supported Operating Environment Reference Guide.

Windows Server 2003 operating system

Solaris 7 operating system

Top of Page

Internationalization

Information in this section is included for international customers.

There are no internationalization issues for this product.

Top of Page

Additional Information

Additional information on Genesys Telecommunications Laboratories, Inc. is available on our Customer Care website. The following documentation also contains information about this software. Please consult the Framework 7.5 Network SIP Server Deployment Guide first.

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

• Genesys Events and Models Reference Manual contains the T-Library API, information on TEvents, and an extensive collection of call models.

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

Product documentation is provided on the Customer Care website, the Genesys Documentation website, and the Documentation Library DVD.

Note: For the DVD, the New Documents on this DVD page indicates the production date for that disc. Due to disc production schedules, documentation on the Genesys Documentation website may be more up-to-date than what is available on disc immediately after a product is released or updated.

Top of Page