Tilghman Lesher wrote: > Given that this is the case, we may want to do one of the following: > a) document that qualify=yes is incompatible with realtime, unless > rtcachefriends is turned on, b) automatically disallow qualify=yes if the > peer is realtime and caching is not turned on, or c) automatically cache > realtime peers whose qualify field is set to yes. > > I am open to discussion and suggestions. Option a is certainly the least > invasive, which doesn't change any behavior, so it's the default, but I think > that enough people would consider this behavior a bug that we might change > it. The only question that I have is, change it to what?
My vote is option (c) with a note clearly documenting this. The other option, of course is only to cache the required fields for qualify to be set to yes - IP address and port? _______________________________________________ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- AstriCon 2008 - September 22 - 25 Phoenix, Arizona Register Now: http://www.astricon.net asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
