On Mon, 2009-03-30 at 14:55 -0400, Alfred Campbell wrote: > Did we get consensus on this one? > > http://track.sipfoundry.org/browse/XECS-2413 > > Issue is asking for this: > > 1. The Stun server specified is incorrect/typo > > 2. The Stun server specified is down/off the air > > 3. The Sipxecs is not connected/has access to the Internet to > contact STUN server > > Right now the fix doesn’t address 1 or 3. > > > Should we just remove the dependency all together? Meaning start the > process regardless and flag alarms if needed .
No - the dependency is a good thing. What's important is that no process fail due to anything that _could_ be a temporary error, even if it means that it can't do anything (or some things). Since we cannot distinguish mis-configuration from a network or remote server error, we should bring up the process, alarm, and keep trying. If it's a misconfiguration, the user will figure that out and fix it; if not, they can fix the net or whatever. _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
