Hi,
I copy the post I wrote about 'qop' param in auth.c, which it is necessary
for REGISTER with the latest version of OpenImsCore.
-----
Hi,
I had a problem with the QOP parameter. I found that patch (
https://sourceforge.net/tracker/?func=detail&atid=637566&aid=2776238&group_id=104305)
and It is not working. The solution is the following:
$ diff sipp.svn/auth.c sipp.patch/auth.c
231a232,237
>
>* // if supplied qop="auth,auth-int",*
>* // then choose qop=auth*
>* if (strstr(authtype, "auth") && strstr(authtype, "auth-int"))*
{
>* strcpy(authtype, "auth");*
>* }
*
You nedd to add this code in 232 line. Then go to sipp directoriy and
execute the commands:
:: make clean
:: make ossl (in my case)
And that's all. I could register my clients successfully.
Regards,*
---
*I hope it helps :)*
*
On Fri, Nov 20, 2009 at 9:24 AM, Yao-Min Chen <yaomin.c...@sun.com> wrote:
> Could you help pointing to these couple of bugs related to auth.c that you
> referred to?
>
> In the SPECsip benchmark that we are developing, every transaction is
> authenticated so we use the auth feature extensively. It will be good to
> know the current issues are. We can also help testing while running the
> SPECsip benchmark.
>
> Thanks,
> Yaomin
>
>
> On 11/19/09 03:33, Vanesa Tejada wrote:
>
> I agree with you.
>
> auth.c have several bugs, and it should be solved early, because people
> have got problems with INVITE and REGISTER messges.
> There are more emails like yours, fixing these bugs.
>
> Thanks for your help :)
>
>
>
> On Wed, Nov 11, 2009 at 10:36 PM, Madhava Dass <madhav.d...@oracle.com>wrote:
>
>> Hi:
>>
>> I encountered a problem while running a test with a sample application.
>> The application was configured to support "DIGEST" authentication. I
>> observed that the server was returning a opaque with 76 chars long, and the
>> "sipp" was generating re-send message containing the header with the opaque
>> value of "64" chars long.
>>
>> Hence made the change to the file "auth.c" file by increasing the "opaque"
>> declaration from 64 to 128 and re-run the test to verify the change. This
>> change has fixed the issue.
>>
>> I thought that it would be good to fix this in the next release of the
>> "SIPp" source and binaries.
>>
>> FYI - The version of the 'sipp' that I used is 3.1.
>>
>> Please let me know if there are any question(s).
>>
>> I have attached the *.zip" file containing the changed file (with the
>> original, update, and diff).
>>
>> Thanks,
>> Madhava
>>
>> ------------------------------------------------------------------------------
>> Let Crystal Reports handle the reporting - Free Crystal Reports 2008
>> 30-Day
>> trial. Simplify your report design, integration and deployment - and focus
>> on
>> what you do best, core application coding. Discover what's new with
>> Crystal Reports now. http://p.sf.net/sfu/bobj-july
>> _______________________________________________
>> Sipp-users mailing list
>> Sipp-users@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/sipp-users
>>
>>
>
>
> --
> Vanessa Tejada
>
>
>
>
--
Vanessa Tejada
------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Sipp-users mailing list
Sipp-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sipp-users
