I recompiled without openssl and tested, working fine for me. Best regards, Sakharam Thorat
--- Original Message --- From: "Sakharam Thorat" <sakharam.tho...@outlook.com> Sent: July 13, 2014 11:11 AM To: "Paul Miller" <idkpmil...@sip2serve.com> Cc: "sipp-users" <sipp-users@lists.sourceforge.net> Subject: Re: [Sipp-users] verifyauth consistently reporting false Hi Paul, URL-ยป https://github.com/SIPp/sipp/archive/3.4.0.tar.gz Extract and run this to install ./configure --with-pcap --with-openssl; make To use veryfiauth in SIPP, i think SIPP should be compiled with opelssl. Best regards, Sakharam Thorat --- Original Message --- From: "Paul Miller" <idkpmil...@sip2serve.com> Sent: July 13, 2014 9:40 AM To: "Sakharam Thorat" <sakharam.tho...@outlook.com> Cc: "sipp-users" <sipp-users@lists.sourceforge.net> Subject: Re: [Sipp-users] verifyauth consistently reporting false Hi Sakharam, I appreciate the time you took to give this a shot for me. I have copied your scenario and inf file verbatim and still I have a problem, I then decided it must be a version thing and I have tried to get the same version you indicated and I cannot find it, can you provide the RURL to the source tar.gz file that you have successfully used here so I can compile and try that specific version? The sipp -v from the last version I used is this: SIPp v3.4.0-RTPSTREAM built Jul 13 2014, 15:07:02. And in case there is something I am not seeing here is my message output. ----------------------------------------------- 2014-07-13 15:52:03.825450 UDP message received [313] bytes : REGISTER sip:test.example.com SIP/2.0 Via: SIP/2.0/UDP 192.168.0.65:5060;branch=z9hG4bK90 From: <sip:1...@test.example.com>;tag=24de4a5dbe4ef To: <sip:1...@test.example.com> Call-ID: 8@192.168.0.65 CSeq: 1 REGISTER Max-Forwards: 70 Contact: <sip:1000@192.168.0.65:5060;transport=UDP> Content-Length: 0 ----------------------------------------------- 2014-07-13 15:52:03.826879 UDP message sent (412 bytes): SIP/2.0 401 Authorization Required Via: SIP/2.0/UDP 192.168.0.65:5060;branch=z9hG4bK90 From: <sip:1...@test.example.com>;tag=24de4a5dbe4ef To: <sip:1...@test.example.com>;tag=4692SIPpTag011 Call-ID: 8@192.168.0.65 CSeq: 1 REGISTER Contact: <sip:192.168.0.220:5060;transport=UDP> WWW-Authenticate: Digest realm="test.example.com", nonce="47ebe028cda119c35d4877b383027d28da013815" Content-Length: 0 ----------------------------------------------- 2014-07-13 15:52:03.834364 UDP message received [511] bytes : REGISTER sip:test.example.com SIP/2.0 Via: SIP/2.0/UDP 192.168.0.65:5060;branch=z9hG4bK93 From: <sip:1...@test.example.com>;tag=24de4a5dbe4ef To: <sip:1...@test.example.com> Call-ID: 8@192.168.0.65 CSeq: 2 REGISTER Max-Forwards: 70 Contact: <sip:1000@192.168.0.65:5060;transport=UDP> Authorization: Digest username="1000",realm="test.example.com ",nonce="47ebe028cda119c35d4877b383027d28da013815",uri="sip:test.example.com ",response="8bb23fa285671ad103a1725d7034f72d",algorithm=MD5 Content-Length: 0 --------------------------------------------------------------------------------------------------------------------------------------------- Thanks once again Paul On Sat, Jul 12, 2014 at 10:34 PM, Sakharam Thorat < sakharam.tho...@outlook.com> wrote: > > Hi Paul, > > You getting false becuase of this issue " > https://github.com/SIPp/sipp/issues/62";, I think this is now fixed. > > I tried following with SIPP 3.4.0, and worked for me . > > *SIPP version-* SIPp v3.4.0-TLS-PCAP-RTPSTREAM built Jul 12 2014, > 03:14:38. > *SIPP Command -*/home/test/Desktop/sipp/sipp-3.4.0/sipp -sn uas -sf > reg_auth.xml -inf reg.inf -m 1 -p 5060 -trace_msg -trace_err > *reg_auth.xml-* > > > <?xml version="1.0" encoding="ISO-8859-1" ?> > <!DOCTYPE scenario SYSTEM "sipp.dtd"> > > <scenario name="Basic UAS registrar with authentication"> > > <label id="badauth"/> > <recv request="REGISTER" /> > <send><![CDATA[ > > SIP/2.0 401 Authorization Required > [last_Via:] > [last_From:] > [last_To:];tag=[pid]SIPpTag01[call_number] > [last_Call-ID:] > [last_CSeq:] > Contact: <sip:[local_ip]:[local_port];transport=[transport]> > WWW-Authenticate: Digest realm="test.example.com", > nonce="47ebe028cda119c35d4877b383027d28da013815" > Content-Length: [len] > > ]]> > </send> > <recv request="REGISTER" > > <action> > > <verifyauth assign_to="authvalid" username="[field0]" > password="[field1]" /> > <log message="authvalid=[$authvalid]"/> > </action> > </recv> > > <nop hide="true" test="authvalid" next="goodauth" /> > <nop hide="true" next="badauth" /> > > <label id="goodauth"/> > <send> > <![CDATA[ > > SIP/2.0 200 OK > [last_Via:] > [last_From:] > [last_To:];tag=[call_number] > [last_Call-ID:] > [last_CSeq:] > Contact: <sip:[local_ip]:[local_port];transport=[transport]> > Content-Length: 0 > Expires: 3600 > > ]]> > </send> > > > <!-- definition of the response time repartition table (unit is ms) --> > <ResponseTimeRepartition value="10, 20, 30, 40, 50, 100, 150, 200"/> > > <!-- definition of the call length repartition table (unit is ms) --> > <CallLengthRepartition value="10, 50, 100, 500, 1000, 5000, 10000"/> > > </scenario> > > *reg.inf-* > > SEQUENTIAL > 1000;1000; > > trace_msg- > > ----------------------------------------------- 2014-07-12 03:20:04.761503 > UDP message received [511] bytes : > > REGISTER sip:192.168.43.2 SIP/2.0 > > Via: SIP/2.0/UDP 192.168.43.8:5060 > ;rport;branch=z9hG4bKPj51ee5d73f3134729bf793c267be1429b > > Max-Forwards: 70 > > From: <sip:1000@192.168.43.2>;tag=c951e08fa39747a6acd4211c07d931b8 > > To: <sip:1000@192.168.43.2> > > Call-ID: c687ec6c8df3448cb3611419bb28a239 > > CSeq: 30665 REGISTER > > User-Agent: MicroSIP/3.3.27 > > Contact: <sip:1000@192.168.43.8:5060;ob> > > Expires: 300 > > Allow: PRACK, INVITE, ACK, BYE, CANCEL, UPDATE, INFO, SUBSCRIBE, NOTIFY, > REFER, MESSAGE, OPTIONS > > Content-Length: 0 > > > > > ----------------------------------------------- 2014-07-12 03:20:04.761954 > UDP message sent (479 bytes): > > SIP/2.0 401 Authorization Required > > Via: SIP/2.0/UDP 192.168.43.8:5060 > ;rport;branch=z9hG4bKPj51ee5d73f3134729bf793c267be1429b > > From: <sip:1000@192.168.43.2>;tag=c951e08fa39747a6acd4211c07d931b8 > > To: <sip:1000@192.168.43.2>;tag=1777SIPpTag011 > > Call-ID: c687ec6c8df3448cb3611419bb28a239 > > CSeq: 30665 REGISTER > > Contact: <sip:127.0.1.1:5060;transport=UDP> > > WWW-Authenticate: Digest realm="test.example.com", > nonce="47ebe028cda119c35d4877b383027d28da013815" > > Content-Length: 0 > > > > > ----------------------------------------------- 2014-07-12 03:20:04.762536 > UDP message received [695] bytes : > > REGISTER sip:192.168.43.2 SIP/2.0 > > Via: SIP/2.0/UDP 192.168.43.8:5060 > ;rport;branch=z9hG4bKPjf8efd01a32a64ddfbbec63aca7a7de13 > > Max-Forwards: 70 > > From: <sip:1000@192.168.43.2>;tag=c951e08fa39747a6acd4211c07d931b8 > > To: <sip:1000@192.168.43.2> > > Call-ID: c687ec6c8df3448cb3611419bb28a239 > > CSeq: 30666 REGISTER > > User-Agent: MicroSIP/3.3.27 > > Contact: <sip:1000@192.168.43.8:5060;ob> > > Expires: 300 > > Allow: PRACK, INVITE, ACK, BYE, CANCEL, UPDATE, INFO, SUBSCRIBE, NOTIFY, > REFER, MESSAGE, OPTIONS > > Authorization: Digest username="1000", realm="test.example.com", > nonce="47ebe028cda119c35d4877b383027d28da013815", uri="sip:192.168.43.2", > response="27e1e2e510251e2278c5747972cc00e5" > > Content-Length: 0 > > > > > ----------------------------------------------- 2014-07-12 03:20:04.762834 > UDP message sent (356 bytes): > > SIP/2.0 200 OK > > Via: SIP/2.0/UDP 192.168.43.8:5060 > ;rport;branch=z9hG4bKPjf8efd01a32a64ddfbbec63aca7a7de13 > > From: <sip:1000@192.168.43.2>;tag=c951e08fa39747a6acd4211c07d931b8 > > To: <sip:1000@192.168.43.2>;tag=1 > > Call-ID: c687ec6c8df3448cb3611419bb28a239 > > CSeq: 30666 REGISTER > > Contact: <sip:127.0.1.1:5060;transport=UDP> > > Content-Length: 0 > > Expires: 3600 > > > > > Best Regards, > Sakharam Thorat. > > > ------------------------------ > Date: Fri, 11 Jul 2014 16:47:07 +1200 > Subject: Re: [Sipp-users] verifyauth consistently reporting false > From: idkpmil...@sip2serve.com > To: sakharam.tho...@outlook.com > CC: sipp-users@lists.sourceforge.net > > > Thanks Sakharam, > I checked out the links, I am well familiar with the site but could not > see anything to assist me further on this occasion > > Thanks > > Paul > > > > On Thu, Jul 10, 2014 at 12:42 AM, Sakharam Thorat < > sakharam.tho...@outlook.com> wrote: > > Following links may be helpful > > tomeko.net/other/sipp/scenarios/REGISTER_client.xml > > tomeko.net/other/sipp/sipp_cheatsheet.php?lang=pl > > > Best regards, > Sakharam Thorat > > --- Original Message --- > > From: "Paul Miller" <idkpmil...@sip2serve.com> > Sent: July 9, 2014 2:54 PM > To: sipp-users@lists.sourceforge.net > Subject: [Sipp-users] verifyauth consistently reporting false > > Hi all, > To try and find a successful baseline that shows me that verifyauth is > working correctly I gave the instructions at > http://www.bertera.it/index.php/2013/05/30/uas-authenticating-registrar-sipp-scenario/ > a shot. The outcome was it too always show false. > so has anyone got a sipp scenario that is known to work that I can use to > troubleshoot why it does not work for me? > > Thanks > > Paul > > >
------------------------------------------------------------------------------
_______________________________________________ Sipp-users mailing list Sipp-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sipp-users
------------------------------------------------------------------------------
_______________________________________________ Sipp-users mailing list Sipp-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sipp-users
