Hi Bogdan.<br><br>For our particular need, it looks like we need to send the response in a more complex way:<br><br>response = md5(HA1:nonce:nonceCount:clientNonce:qop:ha2)<br><br>Could you give us any hint about nonceCount and clientNonce parameters? Documentation is not very clear.<br>
<br>Thanks and regards.<br><br>Sergio.<br><br><div class="gmail_quote">On Wed, May 13, 2009 at 9:38 AM, Bogdan-Andrei Iancu <span dir="ltr"><<a href="mailto:bogdan@voice-system.ro">bogdan@voice-system.ro</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Hi Matti,<br>
<br>
Actually it is SIP auth, so digest auth (RFC 2617)<br>
Shortly:<br>
HA1=MD5( auth_usernam ":" realm ":" passwd )<br>
<br>
HA2=MD5( method ":" ruri )<br>
<br>
response=MD5( HA1 ":" nonce ":" HA2)<br>
<div><div></div><div class="h5"><br>
Regards,<br>
Bogdan<br>
<br>
Matti Zemack wrote:<br>
> Hi again,<br>
><br>
> First of all; Thanks Bogdan!<br>
> Your tip works (theoretically) fine.<br>
> But, I just can't find a way of calculating the PAP2s authentication.<br>
> Not much seems to be documented.<br>
> Does anyone have any hints regarding Linksys authentication (for a<br>
> reboot at least).<br>
><br>
> I've tried calculating using<br>
> <a href="http://en.wikipedia.org/wiki/Digest_access_authentication" target="_blank">http://en.wikipedia.org/wiki/Digest_access_authentication</a> , and<br>
> basically sticking to RFC2069, as I don't believe I have have nonceCount<br>
> & clientNonce.<br>
> By the way; how should the digestURI look? (I've tried the combinations<br>
> that came to my mind...)<br>
><br>
> Best regards,<br>
> Matti Zemack, Stockholm, Sweden<br>
><br>
> -----Original Message-----<br>
> From: Bogdan-Andrei Iancu [mailto:<a href="mailto:bogdan@voice-system.ro">bogdan@voice-system.ro</a>]<br>
> Sent: den 12 maj 2009 10:33<br>
> To: Matti Zemack<br>
> Cc: <a href="mailto:users@lists.opensips.org">users@lists.opensips.org</a><br>
> Subject: Re: [OpenSIPS-Users] Rebooting a Linksys through OpenSIPS<br>
><br>
> Hi Matti,<br>
><br>
> Well, it should be possible - you do a 2 steps interaction with the<br>
> Linkys :<br>
> - first send the NOTIFY via the t_uac_dlg MI command and get from the<br>
> result the auth challenge (in the MI command response you do have access<br>
><br>
> to the SIP reply)<br>
> - generate a new NOTIFY request including the Authorize header<br>
> calculated based on the received challenge.<br>
><br>
> Regards,<br>
> Bogdan<br>
><br>
> Matti Zemack wrote:<br>
><br>
>> Hi all,<br>
>><br>
>> I'm still dipping my toes in deep waters with OpenSips 1.5...<br>
>><br>
>> And I've come across a small problem. I would like to reboot Linksys<br>
>> ATA (PAP2 etc...) using OpenSIPS.<br>
>><br>
>> Can this maybe be done?<br>
>><br>
>> Basically I use XML-RPC FIFO to send the SIP command. The problem is<br>
>> that Linksys replies with 401 challenge. Can I, or is it at all<br>
>> possible to reply to this challenge using OpenSIPS?<br>
>><br>
>><br>
><br>
><br>
><br>
<br>
<br>
_______________________________________________<br>
Users mailing list<br>
<a href="mailto:Users@lists.opensips.org">Users@lists.opensips.org</a><br>
<a href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users" target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a><br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>Sergio Gutiérrez<br>