did you add an entry in hosts file to overcome it? (i.e. 74.63.41.218 newyork.voip.ms)
On Mon, Feb 6, 2012 at 4:51 PM, Sébastien QUESSON <[email protected]> wrote: > Found one solution few days ago. > Error was not recovered and I began to check system log files. I noticed > that ITSP address could not be resolved... Not because of my local DNS, but > because of my ITSP DNS server (unreachable). > Hope it helps > ________________________________ > > From: "Michael Picher" <[email protected]> > To: "Discussion list for users of sipXecs software" > <[email protected]> > Sent: Monday, February 6, 2012 10:16:26 PM > Subject: Re: [sipx-users] FW: Alarm SPX00016: The ITSP Account could not > be reached > > > Ditto here guys... I tried tracking this down with them and got nowhere... > > It doesn't seem to be affecting anything. I also have a second account > connecting through chicago.voip.ms and it's not doing it. > > Mike > > On Mon, Feb 6, 2012 at 3:46 PM, Todd Hodgen <[email protected]> wrote: >> >> This is precisely why I don't use VOIP.ms as a primary route with >> customers. >> I experience the same thing out of their Seattle server, and I used to >> experience the same out of Dallas and Los Angeles. In my opinion, they >> are >> not ready to be a recommended service for customers that use them as their >> primary service. I restrict their use to prepaid services for >> International calling, so as to restrict the liability to the customer, >> and >> for conference services since they have a high number of CCS's with their >> service. >> >> If a customer is wanting SIP trunks for their primary service, I generally >> recommend Broadvox. As low as $12.75 a month for unlimited local >> calling. >> $.02 cents for long distance. >> >> I've used VOIP.ms for over three years now. They have improved >> considerably, but still are not what I would consider a reliable career >> for >> primary service. >> >> -----Original Message----- >> From: [email protected] >> [mailto:[email protected]] On Behalf Of Nathaniel >> Watkins >> Sent: Monday, February 06, 2012 12:11 PM >> To: Discussion list for users of sipXecs software >> Subject: [sipx-users] FW: Alarm SPX00016: The ITSP Account could not be >> reached >> >> Has anyone else seen the below behavor? I seem to get this about once a >> day >> - one minute later I get a message that the ITSP account has recovered. >> >> I was quick on the draw today - so as soon as the first email came in - I >> dialed my cell phone as a long distance call - sure enough, it was routed >> thru the PRI (which is my secondary gateway in sipXecs). A minute later >> when the email came thru that everything was working - I called it again >> and >> it went thru voip.ms >> >> I'm guessing that calls are dropped when this happens - although, I've not >> gotten any calls about it... >> >> I suppose I can constantly ping newyork.voip.ms and see if I'm losing >> connectivity from my pc (although, it uses a different router). >> >> Thoughts? >> >> >> -----Original Message----- >> From: sipXecs Alarm Notification Service >> [mailto:[email protected]] >> Sent: Monday, February 06, 2012 3:04 PM >> To: ITStaff >> Subject: Alarm SPX00016: The ITSP Account could not be reached >> >> Message from sipXecs >> Alarm: SPX00016 >> Reported on: sipx.garrettcounty.org >> Reported at: 2012-02-06T20:03:39.760207Z >> Severity: CRIT >> Alarm Text: An attempt to signal the ITSP 'newyork.voip.ms' timed out. >> Suggested Resolution: Check your ITSP Account Domain, Proxy and Registrar >> settings and restart the SIP Trunking service. >> >> This message and any files transmitted with it are intended only for the >> individual(s) or entity named. If you are not the intended individual(s) >> or >> entity named you are hereby notified that any disclosure, copying, >> distribution or reliance upon its contents is strictly prohibited. If you >> have received this in error, please notify the sender, delete the >> original, >> and destroy all copies. Email transmissions cannot be guaranteed to be >> secure or error-free as information could be intercepted, corrupted, lost, >> destroyed, arrive late or incomplete, or contain viruses. Garrett County >> Government therefore does not accept any liability for any errors or >> omissions in the contents of this message, which arise as a result of >> email >> transmission. >> >> >> Garrett County Government, >> 203 South Fourth Street, Courthouse, Oakland, Maryland 21550 >> www.garrettcounty.org _______________________________________________ >> 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/ > > > > > -- > Michael Picher, Director of Technical Services > eZuce, Inc. > > 300 Brickstone Square > > Suite 201 > > Andover, MA. 01810 > > O.978-296-1005 X2015 > M.207-956-0262 > @mpicher <http://twitter.com/mpicher> > www.ezuce.com > > ------------------------------------------------------------------------------------------------------------ > Hope to see you at the sipX CoLab! http://www.sipfoundry.org/sipx-colab > A gathering for - open source users, eZuce customers & eZuce partners > Get the inside track on 4.6 and a glimpse at the future of sipXecs! > > > _______________________________________________ > 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/ -- ~~~~~~~~~~~~~~~~~~ Tony Graziano, Manager Telephone: 434.984.8430 sip: [email protected] Fax: 434.465.6833 ~~~~~~~~~~~~~~~~~~ LAN/Telephony/Security and Control Systems Helpdesk: Telephone: 434.984.8426 sip: [email protected] Helpdesk Customers: http://myhelp.myitdepartment.net Blog: http://blog.myitdepartment.net Linked-In Profile: http://www.linkedin.com/pub/tony-graziano/14/4a6/7a4 Ask about our Internet Fax services! -- LAN/Telephony/Security and Control Systems Helpdesk: Telephone: 434.984.8426 sip: [email protected] Helpdesk Customers: http://myhelp.myitdepartment.net Blog: http://blog.myitdepartment.net _______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users/
