Hi Bogdan,
I think the dialog would be a good place to handle cseq. I raised
this issue again after I saw your changes in the dialog module :)
We could store the outgoing cseq in the dialog and for every outgoing
request, replace the cseq from the request with the one stored on the
dialog and vi
Hi Ovidiu,
well, the things are a bit more complicated than they seam. If in case
of FROM URI it is just information that does not change across the
dialog, for CSEQ, its value may change - and I'm not talking about the
increasing value for each sequential request, but about the fact you can
Hi all,
Are there any news with respect to increasing CSeq feature?
I search the bug list but I could not find one related to to this issue.
Regards,
Ovidiu Sas
On 1/10/07, Andreas Heise <[EMAIL PROTECTED]> wrote:
Hi Bogdan,
yes with the "fix" suggested by Thomas works with some proxies
maybe the source (auth.c) of sipsak is a good example how qop could be
implemented easy.
It looks not so complicated, what do you think?
ciao,
Andreas
Bogdan-Andrei Iancu schrieb:
Hi Andreas,
yes, that is true - is a bit of complicated to calculate the response
when qop is on. Have you tr
Hi Bogdan,
yes with the "fix" suggested by Thomas works with some proxies
I hope that real qop support and CSeq feature will be define as todo for
the next roadmap instead of nice to have, because uac_auth is really needed
often.
greetings from Berlin,
Andreas
Bogdan-Andrei Iancu schrieb:
Hi Thomas,
what you patch does is ignoring the qop and responding as if no qop was
received. This implies some flexibility from the auth server ;) - what
you are auth against?
maybe we can do config option to ignore the qop for the moment.
regards,
bogdan
Thomas Gelf wrote:
My previous m
Hi Andreas,
yes, that is true - is a bit of complicated to calculate the response
when qop is on. Have you tried the approach suggested by Thomas? to
completely ignore the qop from challenge and to send the response as if
no qop was received..
regards,
bogdan
Andreas Heise wrote:
I'v
I've make some tests to deeper understand qop, for this I've modify the
auth_hdr.c to
ignore the qop and add a static qop=auth to the outgoing authorization
header, but this
way wasn't successful.
After review of RFC 2617 I found that in case of qop cnonce and
nonce-count (nc) MUST
send by t
Hi!
Please open a ticket at the bugtracker - to avoid that this problem
gets forgotten.
regards
klaus
Thomas Gelf wrote:
Hi Bodgan, Klaus, Stefano, ... :o)
I make intensive use of uac_auth() and temporarily "solved" this problem
for my personal needs as described in
> http://openser.org/
