Hi, I'm trying out the new path module, and I've got a couple of questions..
In my current configuration I'm replicating the register between two OpenSER. (To have each registrar have all contacts for all users + redundancy)
However, now I get ERROR: t_newtran: EoH not parsed when I replicate the REGISTER...
br hw
Helge Waastad wrote:
Hi, I'm trying out the new path module, and I've got a couple of questions..
In my current configuration I'm replicating the register between two OpenSER. (To have each registrar have all contacts for all users + redundancy)
However, now I get ERROR: t_newtran: EoH not parsed when I replicate the REGISTER...
I'm able to reproduce it, but it does not seem to be a path-related problem, since it also occurs when I disable all the path-stuff...
Looking at parser/hf.h, there are these lines:
/* type to flag conversion * WARNING: HDR_ERROR_T has no corresponding FLAG ! */ #define HDR_T2F(type) \
(((type)!=HDR_EOH_T)?((hdr_flags_t)1<<(type)):(~(hdr_flags_t)0))
Bogdan, maybe there's a problem with the new header chaining? Sure, that it's HDR_EOH_T and not HDR_ERROR_T in the macro?
Andy
Hi Helge, Hi Andreas,
can you detail a little bit your scenario - I made a small REGISTER replication cfg but still not able to reproduce the error. are you sure you do not have an parsing errors related to that REGISTER?
also be sure you did a complete update from the CVS.
regards, bogdan
Andreas Granig wrote:
Helge Waastad wrote:
Hi, I'm trying out the new path module, and I've got a couple of questions..
In my current configuration I'm replicating the register between two OpenSER. (To have each registrar have all contacts for all users + redundancy)
However, now I get ERROR: t_newtran: EoH not parsed when I replicate the REGISTER...
I'm able to reproduce it, but it does not seem to be a path-related problem, since it also occurs when I disable all the path-stuff...
Looking at parser/hf.h, there are these lines:
/* type to flag conversion
- WARNING: HDR_ERROR_T has no corresponding FLAG ! */
#define HDR_T2F(type) \
(((type)!=HDR_EOH_T)?((hdr_flags_t)1<<(type)):(~(hdr_flags_t)0))
Bogdan, maybe there's a problem with the new header chaining? Sure, that it's HDR_EOH_T and not HDR_ERROR_T in the macro?
Andy
Bogdan-Andrei Iancu wrote:
can you detail a little bit your scenario - I made a small REGISTER replication cfg but still not able to reproduce the error. are you sure you do not have an parsing errors related to that REGISTER?
You're right, if not only path is disabled in registrar, but if there is generally NO path header in the message, it works. Still investigating...
Andy
Hi guys, I sure will.....
I'll get back to you.
br hw
man, 06,.03.2006 kl. 16.42 +0100, skrev Andreas Granig:
Andreas Granig wrote:
You're right, if not only path is disabled in registrar, but if there is generally NO path header in the message, it works. Still investigating...
Ok, found it. Helge, can you please check that again (after CVS has synched)?
Andy
Hi, as far as I can see it works just fine now.
Thanks a lot.
br hw
man, 06,.03.2006 kl. 16.42 +0100, skrev Andreas Granig:
Andreas Granig wrote:
You're right, if not only path is disabled in registrar, but if there is generally NO path header in the message, it works. Still investigating...
Ok, found it. Helge, can you please check that again (after CVS has synched)?
Andy
Hi,
I did more searching on the error cause. It may appear in only one case ,when the message is malformed - the CRLF between the hdrs and body is missing - in this case the parser will not parse any more hdrs, but HDR_EOH_F will not be set since end of headers was not found.
check if it's not your case.
regards, bogdan
Andreas Granig wrote:
Helge Waastad wrote:
Hi, I'm trying out the new path module, and I've got a couple of questions..
In my current configuration I'm replicating the register between two OpenSER. (To have each registrar have all contacts for all users + redundancy)
However, now I get ERROR: t_newtran: EoH not parsed when I replicate the REGISTER...
I'm able to reproduce it, but it does not seem to be a path-related problem, since it also occurs when I disable all the path-stuff...
Looking at parser/hf.h, there are these lines:
/* type to flag conversion
- WARNING: HDR_ERROR_T has no corresponding FLAG ! */
#define HDR_T2F(type) \
(((type)!=HDR_EOH_T)?((hdr_flags_t)1<<(type)):(~(hdr_flags_t)0))
Bogdan, maybe there's a problem with the new header chaining? Sure, that it's HDR_EOH_T and not HDR_ERROR_T in the macro?
Andy
Bogdan-Andrei Iancu wrote:
I did more searching on the error cause. It may appear in only one case ,when the message is malformed - the CRLF between the hdrs and body is missing - in this case the parser will not parse any more hdrs, but HDR_EOH_F will not be set since end of headers was not found.
There was a problem with the path module inserting the Path header, where the Header wasn't terminated properly (yes, a CRLF problem). I've fixed that about a week ago. Or are there still issues with that? It worked for me as well as for Helge, as far as I've seen.
Andy
Andreas Granig wrote:
Bogdan-Andrei Iancu wrote:
I did more searching on the error cause. It may appear in only one case ,when the message is malformed - the CRLF between the hdrs and body is missing - in this case the parser will not parse any more hdrs, but HDR_EOH_F will not be set since end of headers was not found.
There was a problem with the path module inserting the Path header, where the Header wasn't terminated properly (yes, a CRLF problem). I've fixed that about a week ago. Or are there still issues with that? It worked for me as well as for Helge, as far as I've seen.
no, no issue; just I found an explanation for that error message.
regards, bogdan
-
Andreas Granig -
Bogdan-Andrei Iancu -
Helge Waastad