2009/3/30 Alfred Campbell <[email protected]>: > 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
3. Will start with alarm - provided you are able to resolve the stun server address. So this case is really the same as #1 in behavior -- i.e. the address cannot be resolved. > > 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 . > > Al > > _______________________________________________ > sipx-dev mailing list > [email protected] > List Archive: http://list.sipfoundry.org/archive/sipx-dev > Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev > -- M. Ranganathan _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
