[Freeswitch-dev] Why does Freeswitch send Bye to sipp(uac and uas) when doing performance test?
Hi, I use sipp to performance test on freeswitch. The test environment is as following, sipp(uac 10.51.50.5 ) <->(10.51.50.4) freeswitch(10.51.51.4) <-> sipp(uas10.51.51.5 ) But when the new call rate reaches 150 new call per second, after a little while the sipp uas shows the following error. Is there something wrong with my test case? In what environment the freeswitch will send Bye to sipp(uac and uas) ? Thanks -Congxin =============================================================================================================== [czhao@congxin trunk]$ sudo sipp -sn uac -i 10.51.50.5 10.51.50.4 -trace_err -d 100000 -r 200 Resolving remote host '10.51.50.4'... Done. ------------------------------ Scenario Screen -------- [1-9]: Change Screen -- Call-rate(length) Port Total-time Total-calls Remote-host 200.0(100000 ms)/1.000s 5060 51.40 s 10281 10.51.50.4:5060 (UDP) 75 new calls during 0.375 s period 1 ms scheduler resolution 9769 calls (limit 60000) Peak was 9769 calls, after 51 s 0 Running, 9769 Paused, 49 Woken up 0 dead call msg (discarded) 3227 out-of-call msg (discarded) 3 open sockets Messages Retrans Timeout Unexpected-Msg INVITE ----------> 10281 655 0 100 <---------- 10167 214 0 0 180 <---------- 169 0 0 0 183 <---------- 0 0 0 0 200 <---------- E-RTD1 1668 68 0 0 ACK ----------> 1668 0 Pause [ 1:40] 1668 512 BYE ----------> 0 0 0 200 <---------- 0 0 0 0 ------------------------------ Test Terminated -------------------------------- ----------------------------- Statistics Screen ------- [1-9]: Change Screen -- Start Time | 2009-03-09 13:13:49:196 1236575629.196965 Last Reset Time | 2009-03-09 13:14:40:234 1236575680.234329 Current Time | 2009-03-09 13:14:40:609 1236575680.609605 -------------------------+---------------------------+-------------------------- Counter Name | Periodic value | Cumulative value -------------------------+---------------------------+-------------------------- Elapsed Time | 00:00:00:375 | 00:00:51:412 Call Rate | 200.000 cps | 199.973 cps -------------------------+---------------------------+-------------------------- Incoming call created | 0 | 0 OutGoing call created | 75 | 10281 Total Call created | | 10281 Current Call | 9769 | -------------------------+---------------------------+-------------------------- Successful call | 0 | 0 Failed call | 11 | 512 -------------------------+---------------------------+-------------------------- Response Time 1 | 00:00:42:741 | 00:00:18:963 Call Length | 00:00:45:415 | 00:00:31:336 ------------------------------ Test Terminated -------------------------------- 2009-03-09 13:14:40:331 1236575680.331543: Discarding message which can't be mapped to a known SIPp call: INVITE sip:sipp@10.51.50.5:5060 SIP/2.0 Via: SIP/2.0/UDP 10.51.50.4;rport;branch=z9hG4bKa4g2UNXNrty8N Max-Forwards: 70 From: sut <sip:service@10.51.50.4:5060>;tag=Ktmc91a3N33rQ To: sipp <sip:sipp@10.51.50.5:5060>;tag=7557SIPpTag00106 Call-ID: 106-7557@10.51.50.5 CSeq: 112169493 INVITE Contact: <sip:mod_sofia@10.51.50.4:5060;transport=udp> User-Agent: FreeSWITCH-mod_sofia/1.0.trunk-11580M Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, PRACK, MESSAGE, SUBSCRIBE, NOTIFY, REFER, UPDATE, REGISTER, INFO Supported: timer, precondition, path, replaces Session-Expires: 120 Min-SE: 120 Content-Type: application/sdp Content-Disposition: session Content-Length: 153 v=0 o=user1 6853881552441804661 3123293097102204886 IN IP4 10.67.7.177 s=- c=IN IP4 10.51.50.4 t=0 0 m=audio 18182 RTP/AVP 0 a=rtpmap:0 PCMU/8000 -------------------------------------------------------------------------------------------------------------------------------------------------- [czhao@congxin trunk]$ sudo sipp -sn uac -i 10.51.50.5 10.51.50.4 -trace_err -d 100000 -r 200 [sudo] password for czhao: Resolving remote host '10.51.50.4'... Done. ------------------------------ Scenario Screen -------- [1-9]: Change Screen -- Call-rate(length) Port Total-time Total-calls Remote-host 200.0(100000 ms)/1.000s 5060 36.35 s 7270 10.51.50.4:5060 (UDP) 66 new calls during 0.326 s period 1 ms scheduler resolution 6915 calls (limit 60000) Peak was 6915 calls, after 36 s 0 Running, 6915 Paused, 0 Woken up 0 dead call msg (discarded) 553 out-of-call msg (discarded) 3 open sockets Messages Retrans Timeout Unexpected-Msg INVITE ----------> 7270 364 0 100 <---------- 7270 123 0 0 180 <---------- 153 0 0 0 183 <---------- 0 0 0 0 200 <---------- E-RTD1 1227 56 0 0 ACK ----------> 1227 0 Pause [ 1:40] 1227 355 BYE ----------> 0 0 0 200 <---------- 0 0 0 0 ------------------------------ Test Terminated -------------------------------- ----------------------------- Statistics Screen ------- [1-9]: Change Screen -- Start Time | 2009-03-09 13:29:10:948 1236576550.948498 Last Reset Time | 2009-03-09 13:29:46:977 1236576586.977287 Current Time | 2009-03-09 13:29:47:307 1236576587.307007 -------------------------+---------------------------+-------------------------- Counter Name | Periodic value | Cumulative value -------------------------+---------------------------+-------------------------- Elapsed Time | 00:00:00:329 | 00:00:36:358 Call Rate | 200.608 cps | 199.956 cps -------------------------+---------------------------+-------------------------- Incoming call created | 0 | 0 OutGoing call created | 66 | 7270 Total Call created | | 7270 Current Call | 6915 | -------------------------+---------------------------+-------------------------- Successful call | 0 | 0 Failed call | 1 | 355 -------------------------+---------------------------+-------------------------- Response Time 1 | 00:00:30:102 | 00:00:13:578 Call Length | 00:00:32:687 | 00:00:23:473 ------------------------------ Test Terminated -------------------------------- 2009-03-09 13:29:47:004 1236576587.004757: Aborting call on an unexpected BYE for call: 673-21803@10.51.50.5. sipp: There were more errors, see 'uac_21803_errors.log' file
On Mar 9, 2009, at 5:20 AM, congxin zhao wrote:
Hi,
I use sipp to performance test on freeswitch. The test environment is as following,
sipp(uac 10.51.50.5 ) <->(10.51.50.4) freeswitch(10.51.51.4) <-> sipp(uas10.51.51.5 )
But when the new call rate reaches 150 new call per second, after a little while the sipp uas shows the following error. Is there something wrong with my test case?
Maybe, what is your test case? Call limits?
In what environment the freeswitch will send Bye to sipp(uac and uas) ?
End of call? The other side hung up?? Mike p.s. There is a little more info at: http://wiki.freeswitch.org/wiki/Load_testing
Thanks Make's response. The test case is that, set up new calls from sipp uac with high call rate(200 Call Attempts per Second). After the call has been set up successfully, sipp uac pauses about 1:40 minute and then sends bye to sipp uas. When running the test case, after a little while, the sipp uas runs normally, but the sipp uac shows the types of errors as the following, 2009-03-09 13:14:40:331 1236575680.331543: Discarding message which can't be mapped to a known SIPp call: 2009-03-09 13:29:47:004 1236576587.004757: Aborting call on an unexpected BYE for call: 673-21803@10.51.50.5. It looks that when the new call rate is high, the freeswitch will send some sipp uac unknown INVITE message and bye message. Should I forward this email to freeswitch user? -Congxin 2009/3/9 Michael Jerris <mike@jerris.com>
On Mar 9, 2009, at 5:20 AM, congxin zhao wrote:
Hi,
I use sipp to performance test on freeswitch. The test environment is as following,
sipp(uac 10.51.50.5 ) <->(10.51.50.4) freeswitch(10.51.51.4) <-> sipp(uas10.51.51.5 )
But when the new call rate reaches 150 new call per second, after a little while the sipp uas shows the following error. Is there something wrong with my test case?
Maybe, what is your test case? Call limits?
In what environment the freeswitch will send Bye to sipp(uac and uas) ?
End of call? The other side hung up??
Mike
p.s. There is a little more info at: http://wiki.freeswitch.org/wiki/Load_testing
_______________________________________________ Freeswitch-dev mailing list Freeswitch-dev@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-dev UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-dev http://www.freeswitch.org
This is normal depending on which side hung up the call and if the scenario file accounts for it... sipp is a tool that takes time to master and understand fully and isn't something I would consider EASY. :P /b On Mar 9, 2009, at 10:42 PM, congxin zhao wrote:
Thanks Make's response.
The test case is that, set up new calls from sipp uac with high call rate(200 Call Attempts per Second). After the call has been set up successfully, sipp uac pauses about 1:40 minute and then sends bye to sipp uas. When running the test case, after a little while, the sipp uas runs normally, but the sipp uac shows the types of errors as the following, 2009-03-09 13:14:40:331 1236575680.331543: Discarding message which can't be mapped to a known SIPp call: 2009-03-09 13:29:47:004 1236576587.004757: Aborting call on an unexpected BYE for call: 673-21803@10.51.50.5.
It looks that when the new call rate is high, the freeswitch will send some sipp uac unknown INVITE message and bye message.
Should I forward this email to freeswitch user?
-Congxin
participants (3)
-
Brian West
-
congxin zhao
-
Michael Jerris