[OpenSIPS-Devel] Adding support for 'dialog-rules'

Iñaki Baz Castillo ibc at aliax.net
Mon Nov 16 00:30:20 CET 2009

El Lunes, 16 de Noviembre de 2009, Saul Ibarra Corretge escribió:
> > Proprietary appplications on top of open source software. Not so great
> > IMHO.
> Every piece of software involved is Open Source, so no 'propietary'
>  application is being developed.

With "propietary" I mean "non standard". It's not required to be "privative" 
in order to be "propietary".
For example, Asterisk Manager Interface (AMI) is a propietary protocol even if 
it's implemented as open source.

> > 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 4235.
> >
> > It would be great if a draft is written with this specification instead
> > of just coding a propietary feature (IMHO).
> There is a lack of a standard in dealing this way with dialog-info, so
>  we'll use the same schema as pre-rules to achieve same functionality:
>  permissions for the dialog-info presence events.

I fully agree.

> If this feature get's standardized or covered on an RFC, we'll modify it so
>  if fits.

As a suggestion, you could elaborate a draft with such specifications as it 
seems there is no IETF people interested in this feature.


Iñaki Baz Castillo <ibc at aliax.net>

More information about the Devel mailing list