[OpenSIPS-Devel] SF.net SVN: opensips:[6345] trunk/modules/drouting
Revision: 6345 http://opensips.svn.sourceforge.net/opensips/?rev=6345view=rev Author: anca_vamanu Date: 2009-11-18 12:17:36 + (Wed, 18 Nov 2009) Log Message: --- - fixed small typing error in documentation Modified Paths: -- trunk/modules/drouting/README trunk/modules/drouting/doc/drouting_admin.xml This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site. ___ Devel mailing list Devel@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/devel
[OpenSIPS-Devel] Adding support for 'dialog-rules'
I would like to know what happens if Eyebeam or SipSimpleClient gets, via XCAP, a pres-rules document with lots of rule sections and many (not just one) in condition sections. Some transformation would be also cool... Inaki, You can make a patch to make it work and we will add it. -- Adrian ___ Devel mailing list Devel@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/devel
Re: [OpenSIPS-Devel] Adding support for 'dialog-rules'
El Miércoles, 18 de Noviembre de 2009, Adrian Georgescu escribió: Inaki, So what are you gonna do about it? Code :) -- Iñaki Baz Castillo i...@aliax.net ___ Devel mailing list Devel@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/devel
Re: [OpenSIPS-Devel] Adding support for 'dialog-rules'
That's the spirit! Adrian On Nov 18, 2009, at 10:06 PM, Iñaki Baz Castillo wrote: El Miércoles, 18 de Noviembre de 2009, Adrian Georgescu escribió: Inaki, So what are you gonna do about it? Code :) -- Iñaki Baz Castillo i...@aliax.net ___ Devel mailing list Devel@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/devel ___ Devel mailing list Devel@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/devel
Re: [OpenSIPS-Devel] Add X-XCAP-Preferred-Identity header to XCAP clients
El Jueves, 19 de Noviembre de 2009, Iñaki Baz Castillo escribió: This header can be: X-XCAP-Preferred-Identity and/or X-3GPP-Preferred-Identity References: - OMA-TS-XDM_Core-V1_1-20080627-A (6.3.2 XDM Client identity assertion) - 3GPP TS 24.109 (7.2 Authentication) However there is other approach: 1) The client doesn't include a identity header. 2) The XCAP proxy/server requires autentication, but it *doesn't* set the realm based on the XUI domain. Instead it sets the realm with a constant value (i.e.: provider.com) even if it's a multidomain environment. 3) The client creates the credentials and sets as username the *full* SPI URI (sip:al...@domain.org). 4) The servers checks the credentials and parses the credentials username so it already knows the identity of the client and can check authorization based on the identity, the xui and the requested document. But it's important to understand that Digest credentials username should contain a SIP URI (or TEL URI) rather than just the SIP username or a pseudo- uri (al...@domain.org). In fact, I would like that OpenSIPS itself adds a new field ha1c in subscriber table so: ha1 = credentials username = alice ha1b = credentials username = al...@domain.org ha1c = credentials username = sip:al...@domain.org Also, OMA specs mandate it: -- OMA-TS-XDM_Core_V2 5.1 Security Procedures 3. The “username” parameter SHALL have the value of the XUI (i.e. the SIP URI or Tel URI) identifying the user (the public user identity); -- Regards. -- Iñaki Baz Castillo i...@aliax.net ___ Devel mailing list Devel@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/devel
