Hola buenas tardes,
Estoy tratando de realizar una prueba de stress a mi centralita con la herramienta sipp pero no consigo que funcione de manera adecuada.
Tras haberla instalado haciendo un $ yum install sipp y habiendo ojeado algunos ejemplos básicos:
http://phillipcooper.co.uk/2011/11/stress-testing-asterisk-with-sipp/http://www.loho.co.uk/blog/2011/08/sip-load-testing-with-sipp/https://hasnainali.wordpress.com/2009/03/12/using-sipp-for-stress-testing-asterisk/http://irockasterisk.blogspot.com.es/2012/03/asterisk-stress-testing-using-sipp.htmlno consigo realizar un test de stress de forma adecuada.
Esta es mi configuración:
sip.conf:
[sipp]
type=friend
context=sipp
host=dynamic
port=5060
user=sipp
canreinvite=no
disallow=all
allow=alaw
extensions.conf:
[sipp]
exten => 2005,1,Answer()
same => n,MusicOnHold(default,20)
same => n,Hangup()
Si ejecuto desde la consola de Centos:
$ sipp -sn uac -d 20000 -s 2005 192.168.7.226 -l 30
Aparece algo de este estilo:
Last Reset Time | 2014-12-10 11:41:42:238 1418233302.238643
Current Time | 2014-12-10 11:41:42:832 1418233302.832350
-------------------------+---------------------------+--------------------------
Counter Name | Periodic value | Cumulative value
-------------------------+---------------------------+--------------------------
Elapsed Time | 00:00:00:593 | 00:09:47:766
Call Rate | 10.118 cps | 9.999 cps
-------------------------+---------------------------+--------------------------
Incoming call created | 0 | 0
OutGoing call created | 6 | 5877
Total Call created | | 5877
Current Call | 0 |
-------------------------+---------------------------+--------------------------
Successful call | 0 | 0
Failed call | 6 | 5877
-------------------------+---------------------------+--------------------------
Response Time 1 | 00:00:00:000 | 00:00:00:000
Call Length | 00:00:00:000 | 00:00:00:000
------------------------------ Test Terminated --------------------------------
2014-12-10 11:41:42:766 1418233302.766914: Aborting call on unexpected message for Call-Id '5877-10014@::1': while expecting '100' (index 1), received 'SIP/2.0 488 Not acceptable here
Via: SIP/2.0/UDP [::1]:5061;branch=z9hG4bK-10014-5877-0;received=192.168.7.226;rport=5061
From: sipp <sip:sipp@[::1]:5061>;tag=10014SIPpTag005877
To: 2005 <
sip:20...@192.168.7.226:5060>;tag=as04fbae16
Call-ID: 5877-10014@::1
CSeq: 1 INVITE
Server: Asterisk 11
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH, MESSAGE
Supported: replaces
Content-Length: 0
A su vez desde el CLI de Asterisk aparece algo de este otro estilo:
== Using SIP RTP CoS mark 5
[2014-12-10 11:41:42] NOTICE[9928][C-0000392e]: chan_sip.c:10449 process_sdp: No compatible codecs, not accepting this offer!
[2014-12-10 11:41:42] ERROR[9928]: netsock2.c:269 ast_sockaddr_resolve: getaddrinfo("::1", "5061", ...): Address family for hostname not supported
[2014-12-10 11:41:42] WARNING[9928]: chan_sip.c:18040 check_via: Could not resolve socket address for '[::1]:5061'trar
[2014-12-10 11:41:42] ERROR[9928][C-0000392f]: netsock2.c:269 ast_sockaddr_resolve: getaddrinfo("::1", "5061", ...): Address family for hostname not supported
[2014-12-10 11:41:42] WARNING[9928][C-0000392f]: chan_sip.c:18040 check_via: Could not resolve socket address for '[::1]:5061'
En estos momentos tengo que irme del trabajo, pero cuando pueda haré una captura con sngrep o algo por el estilo. Mientras tanto, si vieseis el por qué del fallo a través de los logs que os acabo de mostrar os agradecería que me echarais una mano.
un saludo
Miguel Sanz