[OpenSER-Users] about openSER and SIPp

Hi there, I'm doing sipp performance measurements with openser 1.2. I run OpenSER on machine A, then run one SIPp on machine B, one SIPp on machine C. For the SIPp on machine C, I start it using UAS mode, ie., ./sipp -sn uas For the SIPp on machine B, if I start is using the following command: ./sipp -sn uac C -rsa A -m 1 -r 1 Everything is correct. The OpenSER can relay messages correctly. But if I start SIPp on machine B using the following command: ./sipp -sn uac -rsa A -m 1 -r 1 -d 5000 Then the SIPp client on machine B will crash because of receiving unexpected "ringing 180" message. Note: the only difference is I add a pause 5 seconds using "-d 5000" option. What I found is: the OpenSER server will keep sending "INVITE" to C during the '5 second pause', so C will keep reponding with "180 Ringing" to B. Does anybody know why OpenSER keeps sending "INVITE" to C while B only issues one "INVITE" request? BTW, the configuration file for OpenSER is very simple: # # $Id: openser.cfg 1676 2007-02-21 13:16:34Z bogdan_iancu $ # # simple quick-start config script # Please refer to the Core CookBook at http://www.openser.org/dokuwiki/doku.php # for a explanation of possible statements, functions and parameters. # # ----------- global configuration parameters ------------------------ debug=3 # debug level (cmd line: -dddddddddd) fork=yes log_stderror=no # (cmd line: -E) children=32 log_facility=LOG_LOCAL0 disable_tcp=yes disable_dns_blacklist=yes disable_dns_failover=yes # Uncomment these lines to enter debugging mode #fork=no #log_stderror=yes # listen=udp:192.168.2.102:5060 # ------------------ module loading ---------------------------------- loadmodule "modules/tm/tm.so" modparam("tm", "wt_timer", 2) # ------------------------- request routing logic ------------------- # main routing logic route{ t_relay(); } Thanks a lot! -Bo Zhang