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:[email protected]>;tag=c951e08fa39747a6acd4211c07d931b8
To: <sip:[email protected]>
Call-ID: c687ec6c8df3448cb3611419bb28a239
CSeq: 30665 REGISTER
User-Agent: MicroSIP/3.3.27
Contact: <sip:[email protected]: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:[email protected]>;tag=c951e08fa39747a6acd4211c07d931b8
To: <sip:[email protected]>;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:[email protected]>;tag=c951e08fa39747a6acd4211c07d931b8
To: <sip:[email protected]>
Call-ID: c687ec6c8df3448cb3611419bb28a239
CSeq: 30666 REGISTER
User-Agent: MicroSIP/3.3.27
Contact: <sip:[email protected]: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:[email protected]>;tag=c951e08fa39747a6acd4211c07d931b8
To: <sip:[email protected]>;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: [email protected]
To: [email protected]
CC: [email protected]
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 <[email protected]>
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" <[email protected]>
Sent: July 9, 2014 2:54 PM
To: [email protected]
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
[email protected]
https://lists.sourceforge.net/lists/listinfo/sipp-users
