It was using the old default stun location, and I replaced it with stun.voipbuster.com.
Sorry, I don't have the original sipXecs default server address. -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of George Niculae Sent: Wednesday, June 01, 2011 1:18 AM To: Joegen Baclor Cc: sipXecs developer discussions Subject: Re: [sipx-dev] MOH and STUN On Wed, Jun 1, 2011 at 11:07 AM, George Niculae <[email protected]> wrote: > On Tue, May 31, 2011 at 1:40 PM, Joegen Baclor <[email protected]> wrote: >> It seems not STUN related. My guess was that an over zealous firewall was >> in the middle and messing around with SDP >> >> > > Well there is a relation MoH - sipxbridge and between sipxbridge - > STUN so there is a good chance that if STUN server down MoH not to > work as expected... Will investigate further Todd, what STUN server were you using when noticed the problem and what server did you put in for solving it? Thanks, George _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev/ ----- No virus found in this message. Checked by AVG - www.avg.com Version: 10.0.1375 / Virus Database: 1511/3673 - Release Date: 06/01/11 _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev/
