 |
| |||||||||||||
|
|
| |||||||||||||
|
|
Tenor (tm) Survivable SIP Gateway (SSG) - S107-09-00 Release NotesThis document lists features and enhancements, as well as resolved and open inconsistencies, for Tenor Survivable SIP Gateway (SSG or SIP Survivable Gateway) running software version S107-09-00. For Response Point only: All features/enhancements/inconsistencies noted for Response Point are applicable only to those units listed here: http://www.quintum.com/responsepoint/rp_products.html. The following sections are included:
Products AffectedThe following products run software version S107-09-00: Analog Gateways
Digital Gateways
Note: This document only addresses these products running survivability software (prefixed with an "S"), not standard gateway software (prefixed with a "P"). Upgrading to Tenor S Software from Standard Gateway SoftwareAlthough the Tenor S (survivability) software runs on many of the same hardware platforms, it is a separate product with slightly different defaults for some parameters, and some new parameters that do not exist in the standard gateway software. With that in mind, it is best to restore factory defaults after upgrading to S107 software from P10x software. This will ensure proper defaults, good security and best operating behavior. Also, note that a license upgrade is required to use survivable software. Survivable software (prefixed with an "S", such as S106) must not be run on a system without the proper license. It will not behave as expected if the proper license is not installed. Contact your distributor to obtain a license upgrade. It is highly recommended that the Tenor S Application Guide be read and fully understood to ensure a seamless introduction to this product line. Interoperability
See http://www.quintum.com/support for the latest changes in product interoperability or to download the latest code. Major FeaturesThis sections includes major features introduced in S107-09-00, as well as any new major features introduced in Maintenance Releases S106-12-01 through S106-12-14. You now have the option to acquire certain features via a license upgrade. Contact your sales representative and/or price list for more information. 4299 ACD feature addedThe ACD enables calls to be distributed to endpoints that have registered to the SSG. In the branch office, IP phones will register through the SSG to a softswitch or service provider. While the service is available, all calls will be routed to the softswitch for termination. In the event of a softswitch failure or network outage the SSG will take on that routing role. The ACD enables the SSG to route a number to a group of endpoints. Other EnhancementsThis sections includes other enhancements introduced in S107-09-00, as well as any other enhancements introduced in Maintenance Releases S106-12-01 through S106-12-14. 3805 Prack supportPrack method is now supported for Microsoft early media. 4131/4376 New SSG commandsThere are a few new SIP configuration commands available through the CLI, including a new configuration for reading the ssg.cfg file. Previously, the Tenor would need to be reset in order to read the file. This also includes support for the ACD command (see 4299). The following commands have been added. cmd sip displaysg. Displays a print out of the ssg.cfg file, if available. cmd sip displayroutes. Displays all routes being used, including the registered routes. cmd sip readssg. Reads the ssg.cfg file and adds each route to the route list. Reboot is not required. cmd sip addssgroute <source> <expression> <replacement> [tcp | udp] [priority] Adds the route to ssg.cfg files. If it does not exist, the file will be created. cmd sip delssgroute <source> <expression> <replacement> [tcp | udp] [priority] Deletes the route from the ssg.cfg file. cmd sip delssgroute. Deletes the ssg.cfg file. 4184 NoConnectTimeout parameter now configurableA new parameter, SSGNoConnectTimeout, has been added as a configuration parameter in the var_config.cfg file. This configurable timer addresses the situation where an incoming or outgoing call has not connected, despite the messages exchanged. If a Connect message is not received within the configured time set in the SSGNoConnectTimeout, the call is cleared. A valid entry is 31 to 2147483 seconds. See the Command Reference for additional information about the var_config.cfg file. 4215 User Agent made Quintum SpecificA new feature enables you to configure how the SSG handles the User Agent Header (i.e., configure the User Header so that it is local to the Tenor). A new parameter, SSGuahQ, configurable through the var_config.cfg file, regulates how the SSG sends the User Agent Header. Configure as follows: SSGuahQ 1. Default entry. This configuration changes the User Agent Header that it sends to be local to the Tenor (i.e., Quintum/1.0.0). SSGuahQ 0 Passes the User Agent Header through as it is received (this is the original behavior of the User Agent Header). 4437 Survivable Mode Invite Timeout ConfigurableA new parameter, SurvivableModeInviteTimeout is now supported. This new option controls the duration of the Invite time out. Valid values are between 1 and 30 seconds. Any value outside this range will default to 4 seconds. This new parameters is configured through the var_config.cfg file. See the Command
Reference for additional information about the var_config.cfg
file. Resolved InconsistenciesThis sections includes inconsistencies resolved in S107-09-00, as well as inconsistencies resolved in Maintenance Releases S106-12-01 through S106-12-14. 4119 No ACK after 487/Cancelsends an OK (in response to a Cancel and a 487 to the Invite), the SSG did not respond with an ACK. This has been resolved. 4123 When NoConnectTimer Expired, Cancel not sentFor an incoming call, when the NoConnectTimer expires, no indication is sent to the Origination side (Cancel) or the Termination side (Failure response). This has been resolved. 4130 SecureSSG did not work when external NAT IP address was in useThe Secure SSG feature did not work when external NAT IP address was in use. This has been resolved. 4209 Support REGISTER Contact Header URI's with ParametersURI parameters were not supported in the REGISTER Contact Header for an Invite message. The SSG now uses the Contact URI, including the parameters, when sending INVITE requests. 4360 SSG registration problemWhen an endpoint was being registered in the SSG, the call failed because the SSG was not processing the URI name properly. This has been resolved. 4393 Before connected, SSG did not pass Notify messages.For an incoming Invite, the SSG was not passing the Notify message through to the other end. This has been resolved. 4403 SSG stripped the Contact from the Ringing headerWhen a call goes through the SSG as outbound proxy, it receives a Ringing and Progress, which has a Contact header. But when the SSG sent the corresponding Ringing/Progress, there was no Contact header As a fix, the outgoing Ringing/Progress from the SSG will have a Contact header (contact specifying the SSG's address). 4432 Multipart Mime decoding problemsFor incoming SIP messages, the Tenor was not fully encoding the MIME messages correctly. The Tenor was expecting a CR/LF to delimit the MIME sections, but this message appeared in the middle of a payload. As a reuslt, a call would fail because only part of the MIME was decoded properly. Open InconsistenciesThis section includes open inconsistencies in Release S107-09-00. Specific details are included for each open issue. If a work around is available, it is listed. 4520 Filter IP does not workFilter IP feature does not work on Tenor CMS or Tenor DX.
|
