Hi, Would you mind also telling us what release of Project Clearwater you’re running on?
Thanks, Seb. From: Clearwater [mailto:[email protected]] On Behalf Of Faustinoni Fabrizio Sent: 24 January 2017 14:49 To: [email protected] Subject: [Project Clearwater] Clearwater sip-stress fail due to Unexpected-Msg 183 Hi, I deployed a Clearwater Cluster, everything looks fine. If I start the stress test /usr/share/clearwater/bin/run_stress --sipp-output demo.clearwater 400 10 the test fail: Last Error: Aborting call on unexpected message for Call-Id '10-4484@127... ------------------------------ Scenario Screen -------- [1-9]: Change Screen -- Call-rate(length) Port Total-time Total-calls Remote-host 0.1(5000 ms)/1.000s 5061 141.75 s 10 192.168.3.46:5054(TCP) 0 new calls during 1.004 s period 1 ms scheduler resolution 0 calls (limit 1) Peak was 1 calls, after 13 s 1 Running, 2 Paused, 3 Woken up 0 dead call msg (discarded) 0 out-of-call msg (discarded) 3 open sockets Messages Retrans Timeout Unexpected-Msg INVITE ----------> 10 0 0 100 <---------- 10 0 0 0 183 <---------- 0 0 0 10 There aren’t error messages in the logs file. In sprout nodes I can see this log but I don’t understand if this is an error or just a info: 4-01-2017 14:47:20.227 UTC Status alarm.cpp:62: sprout issued 1004.1 alarm 24-01-2017 14:47:20.227 UTC Status alarm.cpp:62: sprout issued 1001.1 alarm 24-01-2017 14:47:20.227 UTC Status alarm.cpp:62: sprout issued 1002.1 alarm 24-01-2017 14:47:50.227 UTC Status alarm.cpp:62: sprout issued 1004.1 alarm Thank you
_______________________________________________ Clearwater mailing list [email protected] http://lists.projectclearwater.org/mailman/listinfo/clearwater_lists.projectclearwater.org
