[OpenSIPS-Devel] Adding support for 'dialog-rules'
ag at ag-projects.com
Mon Nov 16 19:19:59 CET 2009
One of the IETF goals is to make protocols extensible without having
to go back to the standards body for adding new stuff. In SIP you can
an extra header for instance without breaking anything and without
having to standardize it either.
This is one example for extending the usage of the standard common-
policy. It takes 5 lines of code to use it for other useful purposes.
It means that IETF did something good in the end.
On Nov 15, 2009, at 8:57 PM, Iñaki Baz Castillo wrote:
> El Martes, 10 de Noviembre de 2009, Saul Ibarra Corretge escribió:
>> As it was discussed earlier
>> (http://www.openser.org/pipermail/devel/2009-July/003522.html) we are
>> planning to support access rules for Event: dialog in the same
>> pres-rules do for Event: presence.
> So we'll end with two components supporting this non estandar feature:
> OpenXCAP as XCAP server and OpenSIPS as SIP presence server. And I
> expect that
> Blink (SIP/XCAP softphone) will also implement it.
> Proprietary appplications on top of open source software. Not so
> great IMHO.
> Also, what does it mean "using like pres-rules format"? pres-rules
> format (RFC
> 5025) is more than "uri A => allow", uri B => block". It allows
> filtering the
> notified information (however it's not used at all). But this could
> be useful
> for dialog-info event ("I allow alice to monitor call to me, but not
> call made
> by me" or "I allow bob to also monitor calls made by me, but he
> cannot know
> how I call"). These filetering features are also suggested in RFC
> It would be great if a draft is written with this specification
> instead of
> just coding a propietary feature (IMHO).
> Iñaki Baz Castillo <ibc at aliax.net>
> Devel mailing list
> Devel at lists.opensips.org
More information about the Devel