Dear Simon, Unfortunately, SIPp does always use the same auth values, when no explicit auth-infos are send by the core. Do you (or anyone else) have any ideas how to calculate new values with an increasing counce counter?
Best, Bjoern -----Ursprüngliche Nachricht----- Von: Simon Flannery [mailto:[EMAIL PROTECTED] Gesendet: Mittwoch, 22. August 2007 19:52 An: Björn Korall Cc: [email protected] Betreff: Re: [Sipp-users] SIP Re-Registration with AUTH information Hej Bjorn, Your IMS core should generate the nounce for each and every challenge. This assumes that you are you are using deist mode (or even Single Sign On) in your IMS core. This is just a guess, but I would change the following line: <pause milliseconds="60000" auth="true" next ="2"/> to <pause milliseconds="60000" next ="2"/> I am thinking that this will stop SIPp from using the OLD auth nounce value. HTH, Simon On 8/22/07, Björn Korall <[EMAIL PROTECTED]> wrote: > Hi, > > I have the following problem. I want to do a registration and continuous > re-registrations of a user after a specific time. The Re-Registrations should > contain the correct authentication information. However, the nounce count is > not incremented and thus, I receive 401s, when re-registering :-( Is there a > way in incrementing the nounce counter in SIPp? I am using latest stable > release 2.0.1. > Thanks a lot in advance! > > Best, > Bjoern > > PS.: Below, you find the scenario I am using. I am injecting all the > information needed from an external file with field2 containing the > Auth-Information (MD5). After first (successfull) registration, it pauses for > some time and sends the Registration with Auth-Information again (implemented > as a loop, jumping to label 2). > > > > <?xml version="1.0" encoding="ISO-88519-1" ?> <!DOCTYPE scenario > SYSTEM "sipp.dtd"> > > <scenario name="Register_Reregister"> > > > <send retrans="500"> > <![CDATA[ > > REGISTER sip:mydomain.org SIP/2.0 > Via: SIP/2.0/[transport] [local_ip]:[local_port];branch=[branch] > Max-Forwards: 70 > Contact: <sip:[EMAIL PROTECTED]:[local_port]> > To: [field0] <sip:[EMAIL PROTECTED]> > From: [field0] <sip:[EMAIL PROTECTED]>;tag=[call_number] > Call-ID: [call_id] > CSeq: [cseq] REGISTER > Expires: 600 > User-Agent: SIPp/Linux > Content-Length: 0 > > ]]> > </send> > > <recv response="200" optional="true" next="1"> </recv> <recv > response="401" auth="true"> </recv> > > <label id="2"/> > > <send retrans="500"> > <![CDATA[ > > REGISTER sip:mydomain.org SIP/2.0 > Via: SIP/2.0/[transport] [local_ip]:[local_port];branch=[branch] > Max-Forwards: 70 > To: [field0] <sip:[EMAIL PROTECTED]> > From: [field0] <sip:[EMAIL PROTECTED]>;tag=[call_number] > Call-ID: [call_id] > CSeq: [cseq] REGISTER > Contact: <sip:[EMAIL PROTECTED]:[local_port]> > [field2] > Expires: 600 > User-Agent: SIPp/Linux > Content-Length: 0 > > ]]> > </send> > > <recv response="200" > > </recv> > > > > > <label id="1"/> > > > <pause milliseconds="60000" auth="true" next ="2"/> > > <!-- Definition of the response time values --> > <ResponseTimeRepartition value="10, 20, 30, 40, 50, 100, 150, 200"/> > > ---------------------------------------------------------------------- > --- This SF.net email is sponsored by: Splunk Inc. > Still grepping through log files to find problems? Stop. > Now Search log events and configuration files using AJAX and a browser. > Download your FREE copy of Splunk now >> http://get.splunk.com/ > _______________________________________________ > Sipp-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/sipp-users > ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Sipp-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/sipp-users
