The release for Project Clearwater sprint "Articuno" has been cut. The code for this release is tagged as release-94 in github.
In this release, we have: * Added nonce-count support. Previously Clearwater issued a new authentication challenge whenever a device re-registered (unless the re-registration was integrity protected by the P-CSCF). Many devices are able to pre-calculate authentication responses based on the previous challenge they received, by incrementing the "nonce count" used to calculate the response. Clearwater now supports nonce counts, and will accept such re-registrations - assuming the authentication response is correct of course! This increases re-registration performance, and reduces the chance of encountering interop problems with different devices. The feature is off by default but can be enabled by putting nonce_count_supported=Y in your /etc/clearwater/shared_config. Note that there are some restrictions on nonce count support - we recommend taking a look at the documentation for nonce_count_supported in http://clearwater.readthedocs.org/en/latest/Clearwater_Configuration_Options_Reference.html before you enable the option on your deployment. * Added some new Alarms for when Clearwater is unable to successfully communicate with Application Servers. If an Application Server stops responding to requests or Clearwater cannot contact it, an alarm will be raised. There are two alarms depending on what default handling is configured for the AS - a major alarm covering ASs that use "session terminated" default handling (alarm index 1009), and a minor alarm for those that use "session continued" default handling (1010). * Improved the reliability and robustness of our alarms. * Changed how the Clearwater sproutlets (S-CSCF/I-CSCF/BGCF) and application servers (Gemini/Memento/MMTel/CDiv/Mangelwurzel) are configured. We've done this to improve performance - we can now route between different sproutlets/application servers more efficiently. It also makes the sproutlets/application servers easier to configure. This release also includes the following bug fixes: * The BGCF fails to route tel URIs that don't include a routing number. (https://github.com/Metaswitch/sprout/issues/1316) * Bono doesn't reject REGISTERs correctly during quiescence (https://github.com/Metaswitch/sprout/issues/1296) * Sprout does not generate EVENT ACRs for some failed REGISTERs. (https://github.com/Metaswitch/sprout/issues/1193) * It's odd that almost all sproutlets are bound to the `scscf` port (https://github.com/Metaswitch/sprout/issues/957) * Mass confusion on I-CSCF if `scscf_uri` isn't `sip:sprout.<home domain>` (https://github.com/Metaswitch/sprout/issues/929) * Can't change the logging level in Homestead (https://github.com/Metaswitch/homestead/issues/320) * Tests are very slow under Valgrind (https://github.com/Metaswitch/chronos/issues/232) * clearwater-cassandra messes with /etc/init.d/cassandra (https://github.com/Metaswitch/clearwater-cassandra/issues/16) * check-uptime giving spurious errors (https://github.com/Metaswitch/clearwater-infrastructure/issues/293) * All alarms are cleared on alarm re-sync, even if their state is not known. (https://github.com/Metaswitch/clearwater-snmp-handlers/issues/134) * In-page-links are broken (https://github.com/Metaswitch/clearwater-readthedocs/issues/155) * NOT_YET_CLUSTERED alarm flickers on restart (https://github.com/Metaswitch/clearwater-etcd/issues/234) To upgrade to this release, follow the instructions at http://clearwater.readthedocs.org/en/latest/Upgrading_a_Clearwater_deployment.html. If you are deploying an all-in-one node, the standard image (http://vm-images.cw-ngv.com/cw-aio.ova) has been updated for this release. Once you've upgraded, you may also need to change your sproutlet configuration, and add a DNS record for your S-CSCF cluster. Previously most Sproutlets/Application servers (AS) either used the value of the 'scscf_uri' parameter for their configuration or had other hard-coded configuration. Now you have the finer control over the configuration - each Sproutlet/AS has three configuration options. The options have the same format for each Sproutlet/AS, as listed here, with <sproutlet> replaced by the appropriate Sproutlet or AS name: * <sproutlet>: The port that the Sproutlet/AS listens on. The default value is 5054 for some Sproutlets/ASs (those enabled by default) and 0 for others (those disabled by default) * <sproutlet>_prefix: The identifier prefix for this Sproutlet/AS, used to build the uri, as described below. The default value is simply the Sproutlet/AS name: <sproutlet> * <sproutlet>_uri: The full identifier for this Sproutlet/AS, used for routing and receiving requests between nodes. The default value is created using the prefix and the hostname of the parent Sprout node, i.e. "sip:<sproutlet_prefix>.<sprout_hostname>;transport=tcp<sip:%3csproutlet_prefix%3e.%3csprout_hostname%3e;transport=tcp>". We recommend that you don't set this yourself anymore, and use the defaults provided. As a concrete example, below are the S-CSCF options and the default values. * scscf=5054 * scscf_prefix=scscf * scscf_uri=sip:scscf.<sprout_hostname>;transport=tcp As we've split out the S-CSCF configuration, you'll also now need to set up DNS records for the S-CSCF cluster specifically (rather than just using the sprout cluster). Thanks, Ellie
_______________________________________________ Clearwater mailing list [email protected] http://lists.projectclearwater.org/mailman/listinfo/clearwater_lists.projectclearwater.org
