On Thu, 2010-03-04 at 09:04 -0500, Robert Joly wrote: > > If we care, we will probably have to start tagging entries in > > the aliases table so that "sipx-userforwards=false" can > > distinguish user forwardings from other types of alias. > > > > > My vote is to have a marker that will differentiate aliases vs. call > forward and only suppress that call forward contacts when > "sipx-userforwards=false" is seen.
I suspect that what we really want is to improve the registrar processing of aliases to better follow the rules for matching URL values. For example, currently, if I send a request URI sip:[email protected];foo=bar then it should not match an identity sip:[email protected];abc=xyz so any alias that translates the either of these would not be returned when the other was received. I think that right now we strip any URL parameters before looking up the identity, so they would match each other. _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev sipXecs IP PBX -- http://www.sipfoundry.org/
