Hi Andrew, I've got the same problem with the lastest stable release (124). The initial registrations are successful, so I don't think it is a problem with the number provisioning. Moreover, excluding the re-registration part from the scenario, the call-setup/teardown are also working. The only problem is with the re-registration. The server replies with a 401 Unauthorized on subsequent REGISTER messages instead of 200 OK.
No problems with the release 123. It is possible that this problem with the sip_stress.xml scenario is due to these changes ? - It is now possible to configure Clearwater to authenticate initial non-REGISTER requests (such as call setup requests) from these endpoints. If the request does not contain authentication information, the request is challenged with a 407 response, prompting the endpoint to re-submit its request with a proper authentication response.To enable this behaviour, set the ` non_register_authentication` config option to ` initial_req_from_req_digest_endpoint` (see http://clearwater.readthe docs.io/en/latest/Clearwater_Configuration_Options_Reference.html <http://clearwater.readthedocs.io/en/latest/Clearwater_Configuration_Options_Reference.html> for more details). - The S-CSCF now authenticates all REGISTER messages from these endpoints (including challenging them if necessary). Thanks Stefano On Thu, Jun 15, 2017 at 12:07 PM, Andrew Edmonds < [email protected]> wrote: > Hi Eric, > > > > Thank you for your question. > > > > Since we have updated our node types the bulk-provisioning commands > <https://github.com/Metaswitch/crest/blob/dev/docs/Bulk-Provisioning%20Numbers.md> > should be run on the vellum nodes. Can you check that you get a successful > output when you run the stress_provision.sh script. > > > > You should also have your deployment configured to use homestead-prov. > This will mean that subscriber details are looked up in the Cassandra > database (which is where the stress_provision.sh provisions subscribers to) > rather than an external HSS. To verify this can you check your > /etc/clearwater/shared_config file contains the following config options: > > > > *# HSS configuration* > > *hss*_hostname*=*0.0*.*0.0 > > *hss*_port*=*3868 > > > > There doesn’t appear to be any errors in the Bono log you have sent me. If > you try the above and still get failures could you please send me the most > recent /var/log/sprout/sprout_XX log from the Sprout node? > > > > Thanks, > > > > Andrew > > > > *From:* Clearwater [mailto:[email protected]] > *On Behalf Of *??? > *Sent:* Monday, June 12, 2017 5:55 AM > *To:* [email protected] > *Subject:* [Project Clearwater] Sipp stress test problem - 400 Bad Request > > > > Hi, > > > > I had installed new version of clearwater. When I finished Sipp > intallation, I start stress test in Clearwater. > > > > > > When I user boghe or zoiper, the clearwater system can process > registration and call setup, it running normaly. > > I had checked my clearwater all process is status ok or running, but > stress test is error. > > The all error message which stress node got is 400 Bad Request. > > > > The message is like as following : > > 2017-06-11 21:37:18:327 1497242238.327900: Aborting call on > unexpected message for Call-Id '[email protected]': while > expecting '200' (index 5), received 'SIP/2.0 400 Bad Request > > > > I'm sure is not the stress node error, because I use it to test the old > version of clearwater, which is not include vellum and dime nodes, and it > works. > > > > Until recently, I had installed new version of clearwater, and creat new > accounts following other use > > > https://github.com/Metaswitch/crest/blob/dev/docs/Bulk-Provi > sioning%20Numbers.md > > > > steps, as I was did, the stress node always recieve 400 bad reqeust. > > > > > > These is bono log : > > > > > > 12-06-2017 04:35:25.531 UTC Status load_monitor.cpp:260: Maximum incoming > request rate/second unchanged - only handled 20 requests in last 202058ms, > minimum threshold for a change is 60461.304688 > > 12-06-2017 04:35:26.309 UTC Warning (Net-SNMP): Warning: Failed to connect > to the agentx master agent ([NIL]): > > 12-06-2017 04:35:41.314 UTC Warning (Net-SNMP): Warning: Failed to connect > to the agentx master agent ([NIL]): > > 12-06-2017 04:35:53.098 UTC Status alarm.cpp:244: Reraising all alarms > with a known state > > 12-06-2017 04:35:53.099 UTC Status alarm.cpp:37: sprout issued 1005.1 alarm > > 12-06-2017 04:35:53.099 UTC Status alarm.cpp:37: sprout issued 1012.3 alarm > > 12-06-2017 04:35:56.329 UTC Warning (Net-SNMP): Warning: Failed to connect > to the agentx master agent ([NIL]): > > 12-06-2017 04:36:11.345 UTC Warning (Net-SNMP): Warning: Failed to connect > to the agentx master agent ([NIL]): > > 12-06-2017 04:36:15.186 UTC Status sip_connection_pool.cpp:422: Recycle > TCP connection slot 23 > > 12-06-2017 04:36:20.187 UTC Status sip_connection_pool.cpp:422: Recycle > TCP connection slot 41 > > 12-06-2017 04:36:23.099 UTC Status alarm.cpp:244: Reraising all alarms > with a known state > > 12-06-2017 04:36:23.099 UTC Status alarm.cpp:37: sprout issued 1005.1 alarm > > 12-06-2017 04:36:23.099 UTC Status alarm.cpp:37: sprout issued 1012.3 alarm > > 12-06-2017 04:36:26.360 UTC Warning (Net-SNMP): Warning: Failed to connect > to the agentx master agent ([NIL]): > > 12-06-2017 04:36:34.189 UTC Status sip_connection_pool.cpp:422: Recycle > TCP connection slot 28 > > 12-06-2017 04:36:41.363 UTC Warning (Net-SNMP): Warning: Failed to connect > to the agentx master agent ([NIL]): > > 12-06-2017 04:36:53.099 UTC Status alarm.cpp:244: Reraising all alarms > with a known state > > 12-06-2017 04:36:53.099 UTC Status alarm.cpp:37: sprout issued 1005.1 alarm > > 12-06-2017 04:36:53.099 UTC Status alarm.cpp:37: sprout issued 1012.3 alarm > > 12-06-2017 04:36:56.376 UTC Warning (Net-SNMP): Warning: Failed to connect > to the agentx master agent ([NIL]): > > 12-06-2017 04:37:08.195 UTC Status sip_connection_pool.cpp:422: Recycle > TCP connection slot 42 > > 12-06-2017 04:37:11.376 UTC Warning (Net-SNMP): Warning: Failed to connect > to the agentx master agent ([NIL]): > > 12-06-2017 04:37:14.483 UTC Status load_monitor.cpp:260: Maximum incoming > request rate/second unchanged - only handled 20 requests in last 108948ms, > minimum threshold for a change is 32600.236328 > > 12-06-2017 04:37:16.535 UTC Status load_monitor.cpp:260: Maximum incoming > request rate/second unchanged - only handled 195 requests in last 2052ms, > minimum threshold for a change is 614.014832 > > 12-06-2017 04:37:23.099 UTC Status alarm.cpp:244: Reraising all alarms > with a known state > > 12-06-2017 04:37:23.099 UTC Status alarm.cpp:37: sprout issued 1005.1 alarm > > 12-06-2017 04:37:23.099 UTC Status alarm.cpp:37: sprout issued 1012.3 alarm > > 12-06-2017 04:37:23.197 UTC Status sip_connection_pool.cpp:422: Recycle > TCP connection slot 4 > > 12-06-2017 04:37:26.382 UTC Warning (Net-SNMP): Warning: Failed to connect > to the agentx master agent ([NIL]): > > 2-06-2017 04:37:26.671 UTC Status load_monitor.cpp:260: Maximum incoming > request rate/second unchanged - only handled 197 requests in last 10135ms, > minimum threshold for a change is 3032.670410 > > > > Futherly, I use sipp to test new version clearwater that is work. But > recently I install new clearwater system, its not working anymore. > > > > How to solve the problem, > > Any help is appreciated. > > > > Grades, > > Eric > > > > > > > > > > > > > > _______________________________________________ > Clearwater mailing list > [email protected] > http://lists.projectclearwater.org/mailman/listinfo/ > clearwater_lists.projectclearwater.org > >
_______________________________________________ Clearwater mailing list [email protected] http://lists.projectclearwater.org/mailman/listinfo/clearwater_lists.projectclearwater.org
