> We're having problems with features that use the URI > parameter "sipx-userforwards=false". The problem is that > this parameter disables not only user-forwarding, but all > mappings defined in the aliases IMDB table, which are used > when people want to give users alphanumeric names, and then > provide dialable digit-strings as aliases. > > This is a known problem in BLF lists; attempting to monitor > an alias doesn't work. But it is also a problem in call > pick-up after we redefined the search for the call to pick up > to not follow user forwardings. (That change was stimulated > by XX-7668.) > > To what degree do we care about this? > > 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. _______________________________________________ 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/
