Eskimo North


          [Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

          Busy signals and "Your call did not go through" recordings.


          • To: dave@megapop.net, tsupport@megapop.net, outages-list@eskimo.com, billing@megapop.net
          • Subject: Busy signals and "Your call did not go through" recordings.
          • From: Robert Dinse <nanook@eskimo.com>
          • Date: Fri, 3 Mar 2000 00:00:37 -0800 (PST)
          • Newsgroups: lobby, announcements
          • Resent-Date: Fri, 3 Mar 2000 00:00:56 -0800
          • Resent-From: outages-list@eskimo.com
          • Resent-Message-ID: <"3qj3-.0.Hr.r4tlu"@mx1>
          • Resent-Sender: outages-list-request@eskimo.com

          
          
               Dave & Co...
          
               A while back I wrote to you regarding our customers getting busy signals
          and "Your call did not go through" recordings when dialing the Seattle access
          number, 206-812-1399. 
          
               You told me you would talk with engineers and get back to me that day.
          
               I have not heard from you since.  I have e-mailed you and tsupport
          specific numbers that calls are originating from, and basically they are coming
          from Seattle proper, south of Seattle, north of Seattle and Eastside
          Bellevue/Redmond/Issaquah, from both GTE and US West serviced areas which
          pretty much places the problem either in ELI or your equipment since there
          isn't anything common on the originating end. 
          
               I got an auto-reply saying that you were out and would be back on March
          1st.  I still haven't heard from you and I've got a lot of customers who are
          less than happy about not being able to connect without multiple re-dials. 
          
               My customers would very much like to know what is happening and what is
          being done to rectify this situation and I would very much appreciate it if you
          could provide this information to me so that I can relay it to them. 
          
               Despite the fact that this has been a problem for a couple of weeks now,
          primarily it would seem in the 8pm-10pm timeframe, I still see no information
          on your website regarding this condition and steps being taken to rectify it. 
          
               Please provide some status with respect to this problem.  Thank you.
          
          
          
          

          • Prev by Date: More Ports with bad DNS in Detroit, MI:
          • Next by Date: 56k/ISDN Authentication problems again
          • Prev by thread: 56k/ISDN Authentication problems again
          • Next by thread: More Ports with bad DNS in Detroit, MI:
          • Index(es):
            • Date
            • Thread