| < Previous by Date | Date Index | Next by Date > |
| < Previous in Thread | Thread Index |
|
Hi John
OK, I will try to be clear.
1. You asked how to set SIP message header's value The answer is: Using reSIProcate.txt document explain how use reSIProcate parser. You can get/set any header component very easy.
See inline comments for answer about registration.
Alex
-----Original Message-----
Alexander Altshuler wrote:
>Hi John > >Did you ever read using.txt document distributed with reSIProcate sources? >I hope it will help. > > > Are you referring to the PDF document called "userguide.pdf" which opens up with the big words VOCAL on the first page? Yes - I read it, observed it's grossly outdated and old, and I just don't know what is deprecated and what is still valid...
Then, there is a text file dated January 26. 2004
Using reSIProcate.
I found either from the site, or somewhere, and it was useful, it appears to list a lot of the different "accessing" methods, which I presume would be useful once one can get an understanding of the overall use (which is not yet explained anywhere).
I read it, understand MOST of it... there is NOTHING in that document that explains anything at all about the Handlers, and a specification of what resip handles vs what WE are responsible for handling.
If none of these documents I described is NOT the one you are talking about, then I sure would want to know where it is so I can read it.
Again, I'll re-iterate the big deep questions I have...
on REGISTERING, X-Lite does the following... Upon "first time" a 401 error occurs while registering, X-Lite takes this returned information, and adds this to the message returned.
RECEIVE TIME: 11277225 RECEIVE << xxx.xxx.xxx.xxx:5060 SIP/2.0 401 Unauthorized
< other stuff >
WWW-Authenticate: Digest algorithm=MD5, realm="whitephone.com", nonce="43151c9242d68c90", opaque="01c3900243d79c92" Content-Length: 0
Then it re-issues the REGISTER message, but this time adds...
Authorization: Digest username="u354",realm="whitephone.com",nonce="43151c9242d68c90",response="e97163ae2810dd4e701938834ed3bc13",uri="sip:whitephone.com",algorithm=MD5,opaque="01c3900243d79c92"
to the message...
Ok, my question is this..... Does resip automatically add this "Authorization:" field in a 2nd attempt to register, or am I supposed to ADD this field to my message before re-trying my register, and in what handler would I want to do this in?
======================================================================= Yes, reSIProcate will automatically add Authorization header if : 1. You previously set up ClientAuthManager for DUM 2. You previously set up digest credential for realm within given 401 or 407 response.
Is it clear answer? =======================================================================
Did I make myself clear here, or am I such a BAD explainer of things, as to totaly confuse everyone.
I had to use X-Lite ( A cheezy SIP phone) to see whats actually transpired, but I have NO clue what I'M supposed to do, Vs what the SIP stack does, and the ONLY people who can answer this is the developers.
I can imagine the hundreds of hours of debugging, trial and error, more trial and error I would have to go through trying to "guess" what resip does, or assume it does something and it really doesn't or on the OTOH assume I have to do something when resip already is doing it.... you can see the frustration and confusion I have....
Doesn't ANYONE have some simple example code (I won't try and build it), I can just refer to, so I can be lead down the right path... and I'm sure other users are going to want to know this as well.
John
|