This is particularly ugly. Under the worse assumptions, the interface name of a physical interface can change when the kernel is upgraded or new interfaces added. And the IP addresses can change if they're handed out by DHCP or reconfigured. So we have to determine this address on every startup, and there is no long-term-fixed identifier for the address, or the interface, or anything.
A conservative strategy would be at install/reconfigure time to record the chosen interface name and IP address, and check at each startup that the association was still correct. That would ensure that we could kick the problem back to the user at any time that our previous configuration might have gone invalid. At configuration time, we could probably develop some heuristics that would guess the right interface 95% of the time. (E.g., if there's only one interface that is "up", that's almost certainly the correct one.) I think there might be two different use cases: If sipX is managing DNS, use strategies like those above. But if DNS is externally managed, look up the server addresses for our SIP domain and pick any that matches an interface on this host; that delegates the problem to whoever is managing DNS, which has to be correct for sipX to work anyway. We probably need some sort of manual override for development situations. Dale _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
