[Blink] digest md5

Adrian Georgescu ag at ag-projects.com
Mon Apr 12 11:42:14 CEST 2010


As a note, if you want to contribute with such functionality yourself,  
you can look at the developer guide hosted at:

http://sipsimpleclient.com/

And at the how to contribute page:

http://sipsimpleclient.com/wiki/SipSupport

Adrian

On Apr 12, 2010, at 10:13 AM, Peter Darvasi wrote:

> First of all, thanks for the answer.
>
> If I get it right, your client does not aim to be compatible with  
> IMS providers.
>
> Is this the situation?
>
> Peter
>
> On Mon, Apr 12, 2010 at 9:31 AM, Adrian Georgescu <ag at ag- 
> projects.com> wrote:
> IMPI, NAI, PAI, TS is stuff we do not serve here.
>
> You ask the wrong question.
>
> Adrian
>
>
> On Apr 12, 2010, at 9:21 AM, Peter Darvasi wrote:
>
>> Could anybody please look at this issue?
>>
>> The problem is, that IMPI is not in NAI format according to 3GPP TS  
>> 23.228 and IETF RFC 2486.
>> Therefore the IMS could not accept the REGISTER.
>>
>> Thanks,
>>
>> Regards,
>>
>> Peter
>>
>>
>> On Wed, Apr 7, 2010 at 10:32 AM, Peter Darvasi <darvasi.peter at gmail.com 
>> > wrote:
>> Hello all!
>>
>> These are the server logs, not too much:
>> DEBUG de.fhg.fokus.hss.main.Task- execute - Processing UAR!
>> DEBUG de.fhg.fokus.hss.main.Task- execute - Processing MAR!
>> DEBUG de.fhg.fokus.hss.cx.op.MAR- generateAuthVector - Auth-Scheme  
>> is Digest-MD5
>>
>> But..
>>
>> In the second Register, the Private User Identity is set to  
>> 'darvasipeter'.
>> I assume it is not possible according to TS 23.228 §4.3.3.1.
>> It says:
>> 'The private identity is assigned by the
>> home network operator, and used, for example, for Registration,  
>> Authorization, Administration, and Accounting
>> purposes. This identity shall take the form of a Network Access  
>> Identifier (NAI) as defined in  IETF RFC 2486 [14].'
>> 'darvasipeter' is not in NAI format.
>> But I could not modify it, as it is processed automatically as IMPU  
>> minus realm.
>>
>> REGISTER sip:open-ims.test SIP/2.0
>> Via: SIP/2.0/UDP 192.168.10.196:51134;rport;branch=z9hG4bKPjc. 
>> 8a6B1vFXXszxY4zN3sRCqRg2dojfum
>> Max-Forwards: 70
>> From: "Peter Darvasi" <sip:darvasipeter at open- 
>> ims.test>;tag=4GSE4f8S2qtYVJeVA.SNMyzPDOhtc0m2
>> To: "Peter Darvasi" <sip:darvasipeter at open-ims.test>
>> .....
>> Authorization: Digest username="darvasipeter", realm="open- 
>> ims.test", nonce="d7ee0154792a31d238a1817f777c1a1d", uri="sip:open-ims.test 
>> ", response="67dd7a8a51a8eeda4452cb7c0497cb5e", algorithm=MD5,  
>> cnonce="iwl3Hf129jcVhR8LRF3zlOau73k2pj5m", qop=auth, nc=00000001
>> Content-Length:  0
>>
>> Is there a way to manually configure IMPI?
>>
>> Thanks,
>>
>> BR,
>>
>> Peter
>>
>>
>> On Tue, Apr 6, 2010 at 3:39 PM, Iñaki Baz Castillo <ibc at aliax.net>  
>> wrote:
>> 2010/4/6 Peter Darvasi <darvasi.peter at gmail.com>:
>> > Thanks, great!
>> > Then could you please tell me, if the password is correct, and  
>> the IMPU and
>> > IMPI are set in server side, how can the following trace occur?
>>
>>
>> Your server should log somewhere why the credentials are being  
>> rejected.
>>
>>
>>
>> --
>> Iñaki Baz Castillo
>> <ibc at aliax.net>
>> _______________________________________________
>> Blink mailing list
>> Blink at lists.ag-projects.com
>> http://lists.ag-projects.com/mailman/listinfo/blink
>>
>>
>> _______________________________________________
>> Blink mailing list
>> Blink at lists.ag-projects.com
>> http://lists.ag-projects.com/mailman/listinfo/blink
>
>
> _______________________________________________
> Blink mailing list
> Blink at lists.ag-projects.com
> http://lists.ag-projects.com/mailman/listinfo/blink
>
>
> _______________________________________________
> Blink mailing list
> Blink at lists.ag-projects.com
> http://lists.ag-projects.com/mailman/listinfo/blink

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ag-projects.com/pipermail/blink/attachments/20100412/2bb3b098/attachment.html>


More information about the Blink mailing list