Hi Rashid,

Looking into the logs, I see that most of the errors are 401s/403s.

The 401s are expected. In a successful registration, we expect the client to do 
a REGISTER with no authentication credentials. This then gets rejected with a 
401 (which contains a WWW-authenticate header). The client will then resend the 
REGISTER, with the appropriate authorization (which uses the contents of the 
WWW-authenticate header).

This should then be accepted, returning a 200 OK. In your case it’s returning a 
403 though. This is returned when the subscriber can’t be found, its password 
is wrong, or the public identity that’s being registered doesn’t belong to the 
private identity that’s authenticating.

To work out which case it is we need the logs from Sprout. You’ve said that you 
can register/make calls manually, so we’ll have to use the stress testing setup 
to get logs. Can you please:

·         Change the number of users down to 10. You can do this by only 
running stress on one of your SIPp nodes, and on that node:

o   Add count=10 in /etc/clearwater/shared_config

o   Run sudo /usr/share/clearwater/infrastructure/scripts/sip-stress

o   Run sudo service clearwater-sip-stress restart

·         Turn on debug logs in Sprout. You can do this by:

o   Write log_level=5 to /etc/clearwater/user_settings (creating it if it 
doesn’t exist already)

o   Restart Sprout (sudo service sprout stop - it will be restarted by monit).

Can you then send across the Sprout debug logs (once they’ve got a few 403s in 
them)?

Ellie

From: Clearwater [mailto:[email protected]] On 
Behalf Of Rashid Mijumbi
Sent: 05 May 2016 07:24
To: [email protected]
Subject: [Project Clearwater] Clearwater SIPp Node Errors 401, 403 and 503

Hi all,

I am trying to stress test a manually installed clearwater system using the 
SIPp node.

I have created numbers in bulk, and created the SIPp node following the 
instructions at

http://clearwater.readthedocs.io/en/latest/Clearwater_stress_testing.html

However, when I start the SIPp node, all requests are rejected by Bono with 
either 401, 403 or 503 error code.

I have 5 SIPp nodes all running against the same Bono. I registered 100,000 
users.

Graphs in Cacti initially showed that Bono Client count increased only up to 7, 
before falling back to 0.

I am able to register and make calls with anyone of the bulk-created numbers 
using zoiper.

I am providing some logs from SIPp and Bono nodes at the links below:


sip-stress_33889_.csv: https://owncloud.tssg.org/index.php/s/npkUrx6z2JvzUfh

sip-stress_3389_counts.csv: 
https://owncloud.tssg.org/index.php/s/B5uwIH66KpAhrMQ

sip-stress.xml: https://owncloud.tssg.org/index.php/s/epF3YznsBuGl0g3

sip-stress_3389_errors.log: 
https://owncloud.tssg.org/index.php/s/zVTu8Kx3p1GxqLA

sip-stress.1.out: https://owncloud.tssg.org/index.php/s/BZQJP51FpIPOHUb

bono_current.txt: https://owncloud.tssg.org/index.php/s/deRQ0BGWF5MK7Q7

/var/log/bono/log_current.txt: 
https://owncloud.tssg.org/index.php/s/wb21OA7mF10Gqr7

Cacti Graphs: https://owncloud.tssg.org/index.php/s/D2L2Z50cJDpzX5w

I would appreciate if anyone could please point me to what is going wrong.

Regards,

Rashid
_______________________________________________
Clearwater mailing list
[email protected]
http://lists.projectclearwater.org/mailman/listinfo/clearwater_lists.projectclearwater.org

Reply via email to