Eskimo North


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

          Everett/Seattle 56k


          • To: outages-list@eskimo.com
          • Subject: Everett/Seattle 56k
          • From: Robert Dinse <nanook@eskimo.com>
          • Date: Tue, 11 May 1999 05:02:41 -0700 (PDT)
          • Resent-Date: Tue, 11 May 1999 05:02:46 -0700
          • Resent-From: outages-list@eskimo.com
          • Resent-Message-ID: <"LSYg11.0.YA3.bn1Et"@mx1>
          • Resent-Sender: outages-list-request@eskimo.com

          
               56K / ISDN  Seattle/Everett Problems               
           
               The 56k problem is still not completely properly resolved, however,
          there is a work-around in place.
          
               The problem with the software marking a modem busy and leaving it
          that way still exists.  However, there is a ten minute idle timeout that
          will eventually release any given modem.
          
               As a work-around, the changed the hunt group to the type that I have
          here for our hunt group where it hunts for the most-idle modem which means
          that unless it's nearly full, the chances of trying to connect to a modem
          that is still hung and hasn't been released by the idle timeout is
          minimal. 
          
               This should greatly reduce the dead-air/re-order/cutoff problems.  To
          further reduce the problem while the vendor is working on a fix to the
          software, they are going to install additional modems such that there are
          more modems than ports so that even with the modems that hang it will
          always have enough to service the calls. 
          
               The engineer I talked to today was hopeful that they'd have a fix for
          the software within the week. 
          
               We however received no more complaints monday night after they made
          the change to the hunt groups so hopefully this work around will prevent
          it form being service impacting while the correct fix is being worked
          upon.
          
               Additionally, here are some other numbers into the Seattle group in
          case the problems reoccur, these may allow you to bypass the problem span
          or modems: 
          
          	206-812-4571    Seattle 
          	206-812-4572    Seattle
          	206-812-4573    Seattle
          	206-812-4574    Seattle
          	206-812-4575    Seattle
          
               If you do encounter ring-no-answer, re-order, cut-offs,
          failure-to-authenticate, or other problems on the Seattle or Everett 56k
          POP, please let us know right away as we need to get this information to
          the MegaPOP people.  There may be seperate unrelated trunking issues
          causing some re-orders from certain areas and to determine that we need
          both the number you called, the number you originated the call on, and the
          time and date of the call, and the nature of the failure. 
          
               Thank you for your patience in this matter.
          
          
          

          • Prev by Date: Tia1
          • Next by Date: www / ftp
          • Prev by thread: www / ftp
          • Next by thread: Tia1
          • Index(es):
            • Date
            • Thread