Here is an alarm I just received from the server: Message from scs Alarm: SPX00013 Reported on: scs-sipserver.xxxxxx.ca Reported at: 2011-05-05T15:32:55.416652Z Severity: CRIT Alarm Text: The STUN Server 'stun.ezuce.com' is dysfunctional. Suggested Resolution: The STUN Server did not return any information that can be used to determine the public address of the internal SBC. Reconfigure your STUN server settings in the System > Servers > NAT page to point at a functioning STUN server.
From: Joegen Baclor <[email protected]> To: Discussion list for users of sipXecs software <[email protected]> Date: 05/04/2011 05:34 PM Subject: Re: [sipx-users] "Process 'SipXbridge' stopped unexpectedly. Attempting to restart the process." Sent by: [email protected] On 05/04/2011 10:28 PM, Douglas Hubler wrote: > On Wed, May 4, 2011 at 9:38 AM, Solomon Mohamed<[email protected]> wrote: >> I changed the STUN server as suggested by Todd to 'stun.ezuce.com' > I don't think Joegen's stun service is up > [dhubler@swift sipxecs]$ telnet stun.ezuce.com 3478 > Trying 174.142.82.79... > telnet: connect to address 174.142.82.79: Connection refused > _______________________________________________ STUN server is running just fine. You can't use telnet to check for connectivity. STUN is UDP. I double checked using twinkle and STUN service works for stun.ezuce.com _______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users/
_______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users/
