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/pipermail/users/2007-January/008538.html
Would it be an option to add such a "patch" to OpenSER 1.2? At least it
would make uac_auth() usable in real-world scenarios without the need of
manually patching OpenSER.
If you are going to use uac_auth() "as it is" you aren't even able to
authenticate against an "out-of-the-box" OpenSER installation with
simple digest authentication...
Kind regards,
Thomas Gelf
NB: Sorry for "crossposting" ;)
Bogdan-Andrei Iancu schrieb:
Hi Klaus, Hi Stefano,
fixes to these limitations are scheduled to be done, but I'm afraid they
will not be ready for the next release - more time consuming things are
on the roll and I personally prefer to finish them before attacking
something new...
Regards,
Bogdan
Klaus Darilion wrote:
Stefano Capitanio wrote:
Hi,
i would like to ask if the two known limitations of UAC Module
(authentication does not support qop; CSeq not increased during
authentication) will be resolved in future releases and if anyone has
developed a patch or is working on it.
I wonder if the dialog module can be used to keep track of the CSeq
difference between the SIPclient-->openser and
openser--->upstreamSIPcomponent and modify all messages on the fly?
Or another idea - would i be possible to store the Cseq difference in
the record route parameter of uac module too?
regards
klaus
_______________________________________________
Devel mailing list
Devel@openser.org
http://openser.org/cgi-bin/mailman/listinfo/devel
