The script is simply forwarding requests and responses in a stateless manner.
I've tried the simple stateful configuration in the opensips site, but I've
like to try it with the stateless configuration. Here's the script I'm using:
####### Global Parameters #########
debug=0log_stderror=no
fork=yeschildren=12
/* uncomment the next line to disable TCP (default on) */disable_tcp=yes
#listen=udp:10.0.0.1:5060port=5060
####### Modules Section ########
#set module pathmpath="/usr/lib/opensips/modules/"
loadmodule "sl.so"loadmodule "tm.so"
modparam("tm", "wt_timer", 2)modparam("tm", "restart_fr_on_each_reply", 0)#
----------------- setting module-specific parameters ---------------
####### Routing Logic ########
# main request routing logic
route{ forward();}
The errors I'm receiving in sipp are like the following:
2011-09-11 19:42:41:161 1315784561.161207: Aborting call on unexpected
message for Call-Id '188-8326@::1': while expecting '200' (index 5), received
'SIP/2.0 180 RingingVia: SIP/2.0/UDP
[::1]:5062;received=127.0.0.1;branch=z9hG4bK-8326-188-0From: sipp
<sip:sipp@[::1]:5062>;tag=8326SIPpTag00188To: sut
<sip:[email protected]:5061>;tag=188Call-ID: 188-8326@::1CSeq: 1 INVITEContact:
<sip:[::1]:5061;transport=UDP>Content-Length: 0
Thanks,
Luis Morales.
From: [email protected]
Date: Mon, 12 Sep 2011 21:19:22 -0500
To: [email protected]
Subject: Re: [OpenSIPS-Users] OpenSIPs Stress test problem
Can't really tell without seeing what the errors are and what your script is
doing. Are you doing any database lookups??
-Brett
On Sep 12, 2011, at 9:18 PM, Luis Morales <[email protected]> wrote:
Hello Brett,
You're right, I forgot to check the logging. I disabled it and it's working
better. I'm still getting some unexpected messages error, but a lot less than I
was getting before. Thanks for your help. Do you know if there's something else
I could do so I could stop getting the errors.?
Thanks,
Luis Morales.
From: [email protected]
Date: Mon, 12 Sep 2011 10:56:13 -0500
To: [email protected]
Subject: Re: [OpenSIPS-Users] OpenSIPs Stress test problem
On Mon, Sep 12, 2011 at 9:15 AM, Luis Alfredo Morales Lora
<[email protected]> wrote:
I'm using version 3.1 and I've also tried version 3.2 and I have the same
problem in both. I used the -trace_err to see what the errors where, and the
problem is that while Sipp is expecting a particular response, it receives
another, for example, while expecting and acknowledge it receives an OK. I used
wireshark to see what was happening, and i saw that the Opensips server
introduces a little delay in sending each response, but what I don't
understand is why with such a small call rate I'm having this problem.
Luis,
You didn't answer my logging questions. I've seen bad logging configurations
totally disable an opensips server. Specifically a registration server that
could handle ONE phone but not TWO. No kidding. Problem was 100% syslog setup.
Disabled logging and back up to being able to handle thousands of phones.
This is pretty well documented and has been reported in the past. That may be
your issue.
-Brett
_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
