hello Henning, <br><br>i would like to thank you very much. you save alot of work because i decided to change my database from LDAP to MySQL. just to make it clear to anyone who may face this problem. <br><br>the solution to keep you passwords hashed in the LDAP server is to save it as HA1 = MD5(username:realm:password). after you build the HA1 save as clear in the LDAP server (i am using openLADP). if you save it as MD5 you will retrieve it as {MD5} blablabla which may cause a problem. so hash it then save it as clear. <br>
<br>thanks for every one helps me in this issue <br><br>regards,<br>Ahmed Huraimel ALALI<br><br><div class="gmail_quote">On Fri, May 23, 2008 at 12:00 PM, <<a href="mailto:users-request@lists.openser.org">users-request@lists.openser.org</a>> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Send Users mailing list submissions to<br>
<a href="mailto:users@lists.openser.org">users@lists.openser.org</a><br>
<br>
To subscribe or unsubscribe via the World Wide Web, visit<br>
<a href="http://lists.openser.org/cgi-bin/mailman/listinfo/users" target="_blank">http://lists.openser.org/cgi-bin/mailman/listinfo/users</a><br>
or, via email, send a message with subject or body 'help' to<br>
<a href="mailto:users-request@lists.openser.org">users-request@lists.openser.org</a><br>
<br>
You can reach the person managing the list at<br>
<a href="mailto:users-owner@lists.openser.org">users-owner@lists.openser.org</a><br>
<br>
When replying, please edit your Subject line so it is more specific<br>
than "Re: Contents of Users digest..."<br>
<br>
<br>
Today's Topics:<br>
<br>
1. Re: [OT] NGREP showing \r and \n symbols (Andreas Heise)<br>
2. Re: [OT] NGREP showing \r and \n symbols (I?aki Baz Castillo)<br>
3. Re: Problem with audio when either or both UAs are not behind<br>
NAT (I?aki Baz Castillo)<br>
4. Re: Authentication problem in openSER (Henning Westerholt)<br>
<br>
<br>
----------------------------------------------------------------------<br>
<br>
Message: 1<br>
Date: Thu, 22 May 2008 23:55:56 +0200<br>
From: Andreas Heise <<a href="mailto:aheise@gmx.de">aheise@gmx.de</a>><br>
Subject: Re: [OpenSER-Users] [OT] NGREP showing \r and \n symbols<br>
To: Ovidiu Sas <<a href="mailto:osas@voipembedded.com">osas@voipembedded.com</a>><br>
Cc: <a href="mailto:users@lists.openser.org">users@lists.openser.org</a><br>
Message-ID: <<a href="mailto:4835EBEC.7070800@gmx.de">4835EBEC.7070800@gmx.de</a>><br>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed<br>
<br>
Hi I?aki,<br>
<br>
I had the same issue with a Nortel CS1k switch, the easiest way to check this<br>
problem is to use the Wireshark feature "Display raw text for SIP message"<br>
which can be enabled under preferences / protocols / SIP<br>
<br>
regards,<br>
Andreas<br>
<br>
<br>
Ovidiu Sas schrieb:<br>
> Hello Inaki,<br>
><br>
> Perform a raw capture using tcpdump and open the file with wireshark.<br>
> Check the lower window in wireshark where you have the message<br>
> displayed in hex format.<br>
> There you will be able to spot '\n' and '\r'. To find the hex codes,<br>
> perform a 'man ascii' on your linux box.<br>
><br>
><br>
> Regards,<br>
> Ovidiu Sas<br>
><br>
> On Tue, May 20, 2008 at 10:53 AM, I?aki Baz Castillo <<a href="mailto:ibc@in.ilimit.es">ibc@in.ilimit.es</a>> wrote:<br>
><br>
>> El Tuesday 20 May 2008 16:37:03 Bogdan-Andrei Iancu escribi?:<br>
>><br>
>>> Hi I?aki,<br>
>>><br>
>>> have you tried the "-W byline" ? - it will format you the lines.<br>
>>><br>
>> Hi Bogdan. Yes, in fact I use this option "-W byline", but this option just<br>
>> splits the trace into lines (macthing "\n"). This is not enough for me since<br>
>> \r is not showed.<br>
>><br>
>> I need it since I send and receive traffic from a carrier using a painful<br>
>> Nortel CS2K softswitch that separes SDP lines with \r instead of the<br>
>> mandatory \r\n adn they are applying dirty and not working patches during<br>
>> production state so I need a way to monitorize it.<br>
>><br>
>> Thanks a lot.<br>
>><br>
>><br>
>><br>
>> --<br>
>> I?aki Baz Castillo<br>
>> <a href="mailto:ibc@in.ilimit.es">ibc@in.ilimit.es</a><br>
>><br>
>> _______________________________________________<br>
>> Users mailing list<br>
>> <a href="mailto:Users@lists.openser.org">Users@lists.openser.org</a><br>
>> <a href="http://lists.openser.org/cgi-bin/mailman/listinfo/users" target="_blank">http://lists.openser.org/cgi-bin/mailman/listinfo/users</a><br>
>><br>
>><br>
><br>
> _______________________________________________<br>
> Users mailing list<br>
> <a href="mailto:Users@lists.openser.org">Users@lists.openser.org</a><br>
> <a href="http://lists.openser.org/cgi-bin/mailman/listinfo/users" target="_blank">http://lists.openser.org/cgi-bin/mailman/listinfo/users</a><br>
><br>
><br>
<br>
<br>
<br>
<br>
------------------------------<br>
<br>
Message: 2<br>
Date: Fri, 23 May 2008 09:31:31 +0200<br>
From: I?aki Baz Castillo <<a href="mailto:ibc@in.ilimit.es">ibc@in.ilimit.es</a>><br>
Subject: Re: [OpenSER-Users] [OT] NGREP showing \r and \n symbols<br>
To: <a href="mailto:users@lists.openser.org">users@lists.openser.org</a><br>
Message-ID: <<a href="mailto:200805230931.31959.ibc@in.ilimit.es">200805230931.31959.ibc@in.ilimit.es</a>><br>
Content-Type: text/plain; charset="iso-8859-1"<br>
<br>
El Thursday 22 May 2008 23:55:56 Andreas Heise escribi?:<br>
> Hi I?aki,<br>
><br>
> I had the same issue with a Nortel CS1k switch<br>
<br>
It's nice to know that I'm not theonly sending/receiving traffic from a Nortel<br>
CS[12]K. ;)<br>
<br>
--<br>
I?aki Baz Castillo<br>
<a href="mailto:ibc@in.ilimit.es">ibc@in.ilimit.es</a><br>
<br>
<br>
<br>
------------------------------<br>
<br>
Message: 3<br>
Date: Fri, 23 May 2008 09:32:21 +0200<br>
From: I?aki Baz Castillo <<a href="mailto:ibc@in.ilimit.es">ibc@in.ilimit.es</a>><br>
Subject: Re: [OpenSER-Users] Problem with audio when either or both<br>
UAs are not behind NAT<br>
To: <a href="mailto:users@lists.openser.org">users@lists.openser.org</a><br>
Message-ID: <<a href="mailto:200805230932.21444.ibc@in.ilimit.es">200805230932.21444.ibc@in.ilimit.es</a>><br>
Content-Type: text/plain; charset="ISO-8859-1"<br>
<br>
El Thursday 22 May 2008 18:54:53 Krunal Patel escribi?:<br>
> Hi,<br>
><br>
> I have registered an UA 12345 , which is public.<br>
> In location table, I found NULL value for received.<br>
> I dial any UA , irrespective to their NAT status.<br>
> Call has been established but can't get audio both side.<br>
> It does not use mediaproxy for audio signaling.<br>
><br>
> How to resolve this problem?<br>
<br>
Do a full sip flow capture and analyze trhe address and port of media in SDP<br>
of INVITE and 200 OK.<br>
<br>
<br>
--<br>
I?aki Baz Castillo<br>
<a href="mailto:ibc@in.ilimit.es">ibc@in.ilimit.es</a><br>
<br>
<br>
<br>
------------------------------<br>
<br>
Message: 4<br>
Date: Fri, 23 May 2008 10:57:56 +0200<br>
From: Henning Westerholt <<a href="mailto:henning.westerholt@1und1.de">henning.westerholt@1und1.de</a>><br>
Subject: Re: [OpenSER-Users] Authentication problem in openSER<br>
To: <a href="mailto:users@lists.openser.org">users@lists.openser.org</a><br>
Cc: Ahmed Huraimel <<a href="mailto:huraimel@gmail.com">huraimel@gmail.com</a>><br>
Message-ID: <<a href="mailto:200805231057.56974.henning.westerholt@1und1.de">200805231057.56974.henning.westerholt@1und1.de</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
On Thursday 22 May 2008, Ahmed Huraimel wrote:<br>
> i am investigating the authentication on openSER. I search for a proper<br>
> explanations but unfortunately i did not find how it is exactly done so i<br>
> did some experiments. i assumed that the response is generated as the<br>
> following: note that i set the username and password with the same string<br>
> "alali"<br>
><br>
> Response = MD5( username + MD5(password) + realm + nonce)<br>
> [..]<br>
> could anyone tell me how exactly the authentication is done in openSER? is<br>
> the response generated is like the one i assumed? what + means in the<br>
> response? does is mean concatenation or exoring?<br>
<br>
Hi Ahmed,<br>
<br>
the authentification in OpenSER/ SIP is based on HTTP auth. You find a<br>
detailed explanation for the construction of the response for example at:<br>
<a href="http://en.wikipedia.org/wiki/Digest_access_authentication" target="_blank">http://en.wikipedia.org/wiki/Digest_access_authentication</a> , some further<br>
informations at: <a href="http://www.voip-info.org/wiki/view/SIP+Authentication" target="_blank">http://www.voip-info.org/wiki/view/SIP+Authentication</a><br>
<br>
For the exact logic inside OpenSER just take a look at the auth module source<br>
code, it should be not that hard to understand. ;-)<br>
<br>
Cheers,<br>
<br>
Henning<br>
<br>
<br>
<br>
------------------------------<br>
<br>
_______________________________________________<br>
Users mailing list<br>
<a href="mailto:Users@lists.openser.org">Users@lists.openser.org</a><br>
<a href="http://lists.openser.org/cgi-bin/mailman/listinfo/users" target="_blank">http://lists.openser.org/cgi-bin/mailman/listinfo/users</a><br>
<br>
<br>
End of Users Digest, Vol 36, Issue 48<br>
*************************************<br>
</blockquote></div><br>