+1 can we at least make the proxy stay active?
From: [email protected] [mailto:[email protected]] On Behalf Of Chris Parfitt Sent: Wednesday, March 25, 2009 4:27 PM To: [email protected] Subject: [sipX-dev] Consequences seen when sipXbridge cannot find its PublicIP address using STUN Would it be possible/practicable to make SIP Proxy more forgiving in a situation when sipXbridge cannot find its Public IP address via the default STUN server? Why? Here are some scenarios: If the Border Controller/internal sipXbridge is added and then "Enable Server Behind NAT" is enabled while one of the following is true the result is detailed below: * The Stun server specified is incorrect/typo * The Stun server specified is down/off the air * The Sipxecs is not connected/has access to the Internet to contact STUN server Result: In the above three scenarios NAT traversal service and the SIP Proxy service both fail to restart when the user is prompted to restart them. SIP Proxy not restarting due to Missing resource: process 'SipXrelay causes all incoming/outgoing calls to fail via PSTN Gateways, Internal User calls fail, AA, Voicemail & Conferences fail, Registration fails basically the box becomes unusable. This effect seems a bit extreme just for the fact that sipXbridge cannot find its STUN server.
_______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
