Re: [Sipp-users] registration with digest auth: how to send right authorization header?

SourceForge Headquarters 1320 Columbia Street Suite 310 San Diego, CA 92101 +1 (858) 422-6466

Dmitry,

Thanks for the reply.

As far as I understand from the manual, including [field2] is the same as
including [authentication username=3853 password=3853].. Is that true?

I also tried including [authentication username=3853 password=3853]
directly, instead of including it from a csv file.

But alas, the second Register still contains incomplete Authorization
header:

Authorization:
,nonce="0769acd81e2821f41cf5103c0668da82496dbc54",response="bff0efb69c5d26b0
d18516e50288c705",algorithm=MD5

This syntax does not work for me...

Could it be something wrong with my sipp installation? I installed sipp
using yum from a standard repository.

Is there an error in my scenario below? 

Could somebody give me a working example of registration scenario or try my
scenario?

Thanks and regards,

Nikolay.

  _____  

From: Dmitry Goncharov [mailto:dgo...@un...] 
Sent: Wednesday, January 14, 2009 1:09 PM
To: Nikolay Kondratyev
Cc: sip...@li...
Subject: Re: [Sipp-users] registration with digest auth: how to send right
authorization header?

You could try including
[authentication username=<your_username> password=<your_password>]
in your second REGISTER.

Have a look at the enclosed file. This scenario does not register, but sets
up a call through a proxy that requires digest authorization.

Br, Dmitry

Nikolay Kondratyev wrote: 

Hi all,

I'm new to sipp and trying to create a scenario for registration with digest
authorization.

Looks like I need some help with it.

I'm using sipx 3.10 as proxy/registrar.

Sipp version:

[kond@localhost sipp]$ sipp -v

 SIPp v3.1-TLS-PCAP, version unknown, built Jul  6 2008, 09:56:05.

I created the following scenario:

<?xml version="1.0" encoding="ISO-8859-1" ?>

<scenario name="register_client">

  <send retrans="500">

    <![CDATA[

      REGISTER sip:[remote_ip] SIP/2.0

      Via: SIP/2.0/[transport] [local_ip]:[local_port];branch=[branch]

      From:  <sip:%5bfield0%5d@%5bfield1%5d>
<sip:[field0]@[field1]>;tag=[call_number]

      To:  <sip:%5bfield0%5d@%5bfield1%5d> <sip:[field0]@[field1]>

      Call-ID: [call_id]

      CSeq: 1 REGISTER

      Contact: sip:[field0]@[local_ip]:[local_port]

      Max-Forwards: 5

      Expires: 1800

      User-Agent: SIPp/Linux

      Content-Length: 0

    ]]>

  </send>

  <recv response="401" auth="true">

  </recv>

  <send retrans="500">

    <![CDATA[

      REGISTER sip:[remote_ip] SIP/2.0

      Via: SIP/2.0/[transport] [local_ip]:[local_port];branch=[branch]

      From:  <sip:%5bfield0%5d@%5bfield1%5d>
<sip:[field0]@[field1]>;tag=[call_number]

      To:  <sip:%5bfield0%5d@%5bfield1%5d> <sip:[field0]@[field1]>

      Call-ID: [call_id]

      CSeq: 2 REGISTER

      Contact: sip:[field0]@[local_ip]:[local_port]

      [field2]

      Max-Forwards: 5

      Expires: 1800

      User-Agent: SIPp/Linux

      Content-Length: 0

    ]]>

  </send>

  <recv response="200">

  </recv>

</scenario>

The following csv file:

SEQUENTIAL

3853;sipx4.lab.nstel.ru;[authentication username=3853 password=3853];

3808;sipx4.lab.nstel.ru;[authentication username=3808 password=3808];

And when I start this scenario :

sipp -sf register_client.xml  -inf register_client.csv -i 172.23.11.94
sipx4.lab.nstel.ru

I got the following message flow:

|Time     | 172.23.11.94      | 172.23.12.104     |

|1,995    |         Request: REGISTER s           |SIP: Request: REGISTER
sip:172.23.12.104

|         |(5060)   ------------------>  (5060)   |

|2,000    |         Status: 401 Unautho           |SIP: Status: 401
Unauthorized    (0 bindings)

|         |(5060)   <------------------  (5060)   |

|2,000    |         Request: REGISTER s           |SIP: Request: REGISTER
sip:172.23.12.104

|         |(5060)   ------------------>  (5060)   |

|2,005    |         Status: 401 Unautho           |SIP: Status: 401
Unauthorized    (0 bindings)

|         |(5060)   <------------------  (5060)   |

|2,005    |         Request: BYE sip:38           |SIP: Request: BYE
sip:38...@si...

|         |(5060)   ------------------>  (5060)   |

|2,034    |         Status: 481 Transac           |SIP: Status: 481
Transaction Does Not Exist

|         |(5060)   <------------------  (5060)   |

The trace in text format is attached.

I think that the problem is in Authorization header of the second Register
message, which looks to be wrong:

Authorization:
,nonce="7c955a589d291cd3b430e4dcdbf1612c496d9ce9",response="deec89ad22272700
a0d17ac62b50101b",algorithm=MD5

I believe, correct authorization header should look like

Authorization: Digest
username="3853",realm="pbxnsip.lab.nstel.ru",nonce="3d675a0e579d994f0fa1f1a9
68be6869",uri= <sip:pbxnsip.lab.nstel.ru>
"sip:pbxnsip.lab.nstel.ru",response="7b38eb913257dd809a8e64bda03990c6",algor
ithm=MD5

So, can anybody please help me with sending correct authorization header?

Thanks in advance,

Nikolay.

  _____  

----------------------------------------------------------------------------
--
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword

  _____  

_______________________________________________
Sipp-users mailing list
Sip...@li...
https://lists.sourceforge.net/lists/listinfo/sipp-users