[OpenSIPS-Users] Rebooting a Linksys through OpenSIPS

Chris Maciejewski chris at wima.co.uk
Thu May 14 09:15:15 CEST 2009


Hi Bogdan,

Yes, sure. No problem at all.

Best regards,
Chris


2009/5/14 Bogdan-Andrei Iancu <bogdan at voice-system.ro>:
> Hi Chris,
>
> Can I link your tool from the opensips tools web page -
> http://www.opensips.org/Resources/DocsTools   ?
>
> Thanks and regards,
> Bogdan
>
> Chris Maciejewski wrote:
>>
>> Hi,
>>
>> You can find a PhpSIP UA I wrote some time ago, which can be used to
>> send a NOTIFY to resync/reboot Linksys phone. It is far from being a
>> complete SIP UA (no transactions matching etc.), but I am using it all
>> the time to send NOTIFY, or INVITE, REFER for Click 2 Call from my web
>> application (PHP based) and it works well.
>>
>> http://wima.co.uk/PhpSIP/
>>
>> Also you will find two functions auth() and authWWW() which calculate
>> Digest and WWW responses.
>>
>> Regards,
>> Chris
>>
>>
>> 2009/5/13 Bogdan-Andrei Iancu <bogdan at voice-system.ro>:
>>
>>>
>>> Matti,
>>>
>>> you should read more about digest auth in the RFC -
>>> http://www.ietf.org/rfc/rfc2617.txt
>>>
>>> Regards,
>>> Bogdan
>>>
>>> Matti Zemack wrote:
>>>
>>>>
>>>> Hi,
>>>>
>>>> Thanks again Bogdan. Tried that. Still no go. Suppose I'll try to get
>>>> some help from Linksys people.
>>>>
>>>> /Matti
>>>>
>>>> -----Original Message-----
>>>> From: Bogdan-Andrei Iancu [mailto:bogdan at voice-system.ro]
>>>> Sent: den 13 maj 2009 17:46
>>>> To: Matti Zemack
>>>> Cc: Sergio Gutierrez; users at lists.opensips.org
>>>> Subject: Re: [OpenSIPS-Users] Rebooting a Linksys through OpenSIPS
>>>>
>>>> With qop, do :
>>>>
>>>> response=MD5( HA1 ":" nonce ":" nc ":" cnonce ":" qop ":" HA2)
>>>>
>>>> Regards,
>>>> Bogdan
>>>>
>>>> Matti Zemack wrote:
>>>>
>>>>
>>>>>
>>>>> Hi again,
>>>>>
>>>>> Yes, we tried almost that (as we don't receive a cnonce nor
>>>>> nonce-count in the 401 from Linksys, we only get the qop="auth" which
>>>>> actually by the RFC forces us to use your suggested longer response
>>>>> code.).
>>>>>
>>>>> We did try with an empty cnonce and nonce count= "nc=00000001" (or
>>>>> empty).
>>>>>
>>>>> Without success.
>>>>>
>>>>> /Matti
>>>>>
>>>>> *From:* Sergio Gutierrez [mailto:saguti at gmail.com]
>>>>> *Sent:* den 13 maj 2009 17:16
>>>>> *To:* Bogdan-Andrei Iancu
>>>>> *Cc:* Matti Zemack; users at lists.opensips.org
>>>>> *Subject:* Re: [OpenSIPS-Users] Rebooting a Linksys through OpenSIPS
>>>>>
>>>>> Hi Bogdan.
>>>>>
>>>>> For our particular need, it looks like we need to send the response in
>>>>> a more complex way:
>>>>>
>>>>> response = md5(HA1:nonce:nonceCount:clientNonce:qop:ha2)
>>>>>
>>>>> Could you give us any hint about nonceCount and clientNonce
>>>>> parameters? Documentation is not very clear.
>>>>>
>>>>> Thanks and regards.
>>>>>
>>>>> Sergio.
>>>>>
>>>>> On Wed, May 13, 2009 at 9:38 AM, Bogdan-Andrei Iancu
>>>>> <bogdan at voice-system.ro <mailto:bogdan at voice-system.ro>> wrote:
>>>>>
>>>>> Hi Matti,
>>>>>
>>>>> Actually it is SIP auth, so digest auth (RFC 2617)
>>>>> Shortly:
>>>>> HA1=MD5( auth_usernam ":" realm ":" passwd )
>>>>>
>>>>> HA2=MD5( method ":" ruri )
>>>>>
>>>>> response=MD5( HA1 ":" nonce ":" HA2)
>>>>>
>>>>>
>>>>> Regards,
>>>>> Bogdan
>>>>>
>>>>> Matti Zemack wrote:
>>>>>
>>>>>
>>>>>>
>>>>>> Hi again,
>>>>>>
>>>>>> First of all; Thanks Bogdan!
>>>>>> Your tip works (theoretically) fine.
>>>>>> But, I just can't find a way of calculating the PAP2s authentication.
>>>>>> Not much seems to be documented.
>>>>>> Does anyone have any hints regarding Linksys authentication (for a
>>>>>> reboot at least).
>>>>>>
>>>>>> I've tried calculating using
>>>>>> http://en.wikipedia.org/wiki/Digest_access_authentication , and
>>>>>> basically sticking to RFC2069, as I don't believe I have have
>>>>>> nonceCount
>>>>>> & clientNonce.
>>>>>> By the way; how should the digestURI look? (I've tried the
>>>>>> combinations
>>>>>> that came to my mind...)
>>>>>>
>>>>>> Best regards,
>>>>>> Matti Zemack, Stockholm, Sweden
>>>>>>
>>>>>> -----Original Message-----
>>>>>> From: Bogdan-Andrei Iancu [mailto:bogdan at voice-system.ro
>>>>>>
>>>>>>
>>>>>
>>>>> <mailto:bogdan at voice-system.ro>]
>>>>>
>>>>>
>>>>>>
>>>>>> Sent: den 12 maj 2009 10:33
>>>>>> To: Matti Zemack
>>>>>> Cc: users at lists.opensips.org <mailto:users at lists.opensips.org>
>>>>>> Subject: Re: [OpenSIPS-Users] Rebooting a Linksys through OpenSIPS
>>>>>>
>>>>>> Hi Matti,
>>>>>>
>>>>>> Well, it should be possible - you do a 2 steps interaction with the
>>>>>> Linkys :
>>>>>> - first send the NOTIFY via the t_uac_dlg MI command and get from the
>>>>>> result the auth challenge (in the MI command response you do have
>>>>>> access
>>>>>>
>>>>>> to the SIP reply)
>>>>>> - generate a new NOTIFY request including the Authorize header
>>>>>> calculated based on the received challenge.
>>>>>>
>>>>>> Regards,
>>>>>> Bogdan
>>>>>>
>>>>>> Matti Zemack wrote:
>>>>>>
>>>>>>
>>>>>>
>>>>>>>
>>>>>>> Hi all,
>>>>>>>
>>>>>>> I'm still dipping my toes in deep waters with OpenSips 1.5...
>>>>>>>
>>>>>>> And I've come across a small problem. I would like to reboot Linksys
>>>>>>> ATA (PAP2 etc...) using OpenSIPS.
>>>>>>>
>>>>>>> Can this maybe be done?
>>>>>>>
>>>>>>> Basically I use XML-RPC FIFO to send the SIP command. The problem is
>>>>>>> that Linksys replies with 401 challenge. Can I, or is it at all
>>>>>>> possible to reply to this challenge using OpenSIPS?
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> Users mailing list
>>>>> Users at lists.opensips.org <mailto:Users at lists.opensips.org>
>>>>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Sergio Gutiérrez
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>
>>> _______________________________________________
>>> Users mailing list
>>> Users at lists.opensips.org
>>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>>
>>>
>>
>> _______________________________________________
>> Users mailing list
>> Users at lists.opensips.org
>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>
>>
>
>



More information about the Users mailing list