On 3/19/08, Damien Herraud <d.herraud at gmail.com> wrote: > I got it finally working ! > When I was reporting you my problems, I was using AKAv1-MD5 digest (default > for open-IMS). I changed the open-IMS configuration (I am hosting the server > on a other computer) to use SIP MD5 digest and it worked flawlessly. > AKAv1-MD5 digest works with UCT IMS client, but not with X-lite (which > also needs SIP MD5 digest). Hmm.. that's not right, pjsip should support AKAv1-MD5 (and AKAv2-MD5) fine. Which pjsip version do you have? AKA was only added at version 0.8 if I recall correctly. Also it is disabled by default, you need to declare this in your config_site.h to enable AKA: #define PJSIP_HAS_DIGEST_AKA_AUTH 1 > Maybe there is a problem with AKAv1-MD5 calculation. I don't need this but > if you want I can help you debugging (remember I am new to SIP, how do I > capture SIP messages ? with wireshark ?) Since you can register fine with MD5 I think your configuration is fine, so we don't need the SIP trace. But yes you'd use Wireshark to capture traffic. Cheers, -benny > Cheers, > > Damien > > > > Date: Wed, 19 Mar 2008 14:52:16 +0000 > > From: "Benny Prijono" <bennylp@xxxxxxxxx> > > Subject: Re: Problem registering with pjsua on an Open-IMS > > network > > To: pjsip at lists.pjsip.org > > Message-ID: > > > <1879720d0803190752x683c6e3ds45124ffffa7bde69 at mail.gmail.com> > > Content-Type: text/plain; charset=ISO-8859-1 > > > > > > On 3/19/08, Damien Herraud <d.herraud at gmail.com> wrote: > > > Hi Benny, > > > > > > Thanks for the quick answer ! I tried this : > > > > > > > --use-ims > > > > --proxy sip:pcscf.open-ims.test:4060;lr > > > > --id sip:alice at open-ims.test > > > > --registrar sip:open-ims.test > > > > --realm open-ims.test > > > > --username alice at open-ims.test > > > > --password alice > > > > > > > > > Unfortunately it resulted in the same error : > > > > Can you register with other IMS user agent? (and make sure it uses > > AKAv1-MD5 digest authentication rather than SIP MD5 digest) If so, can > > you capture the SIP messages? I'd like to know if there are things > > that we need to do differently. > > > > Are you hosting the IMS servers yourself? If so, can you find anything > > peculiar in the server log? > > > > There are few possibilities on why this could happen. Configuration > > setting is one. Or maybe it's just wrong username/password. The worst > > case for me is if the AKAv1-MD5 calculation is wrong, since I don't > > fancy debugging this. But it worked fine before, also others have > > tested this, and I don't recall doing anything on this area, so I > > don't expect this to be the case, hopefully. > > > > Cheers, > > -benny >
