I agree that caching in SipX is not only a good idea, but the norm for most software. You don't see Exchange or IIS making constant queries to look something up. Even the DNS client in Windows caches lookups. Going out to the network instead of doing an in memory lookup hurts performance AND makes a system less reliable. If the DNS goes down for a few minutes most likely SipX will stay up if it caches. If not it will not work.
Given that scenario I would recommend that "the cache" does a new lookup and then delete its cached record only if it gets a new one. That way it can survive DNS failure. I also want to touch on the fact making SipX easier to use is something that needs to be done. Especially for initial setup. As I stated before we should: - Get rid of the NUI prompts for everything other than IP config. Information should only be what is necessary to reach the Web GUI. - There should be a Wizard that runs on setup that helps you to configure (or reconfigure) a SipX system. The wizard should walk you through setting up a regular or HA system. It should also provide specific guidance on setting up remote DNS servers and the records they will need etc. Or it should provide the option on using a sub-domain with local DNS server(s) and how to set that up on remote DNS servers etc. This step also gets around the problems people have in changing IP addresses for example. I don't know if that was ever fixed in the GUI. Geoff Van Brunt _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev/
