It's me again. Alarms sent out this tidbit after reconfiguration: Alarm Text: The STUN Server 'stun.ezuce.com' is dysfunctional.
Guess it is dead at the moment. On Mon, Dec 19, 2011 at 10:12 PM, Philippe Laurent <[email protected]> wrote: > So, perhaps the stun.ezuce.com server is/was down? I changed the NAT > settings to IP, and set me IP address in that field, and it registered. > Changed it back to stun with stun.ezuce.com, and it worked. I'll test the > others tomorrow. > > Strange. > > Sorry for the noise. > > > On Mon, Dec 19, 2011 at 9:51 PM, Philippe Laurent <[email protected]> wrote: > >> I have two locations, both running sipX and registering with different >> voip.ms accounts, that have both stopped registering with voip.ms, with >> no changes to sipX or Voip.ms account settings. Anyone else experiencing >> the same? If so, have you resolve it, and what did you do to do so? > > >
_______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users/
