From owner-freebsd-questions@FreeBSD.ORG Fri Jun 6 14:49:40 2008 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D8B6C106567F for ; Fri, 6 Jun 2008 14:49:40 +0000 (UTC) (envelope-from mark@summersault.com) Received: from tanagra.summersault.com (tanagra.summersault.com [12.161.105.149]) by mx1.freebsd.org (Postfix) with SMTP id 0FCAE8FC0A for ; Fri, 6 Jun 2008 14:49:39 +0000 (UTC) (envelope-from mark@summersault.com) Received: (qmail 77786 invoked from network); 6 Jun 2008 10:22:57 -0400 Received: from simba.summersault.com (HELO ?192.168.97.182?) (192.168.97.182) by tanagra.summersault.com with SMTP; 6 Jun 2008 10:22:57 -0400 From: Mark Stosberg To: Bob McConnell In-Reply-To: References: <1212760486.29520.22.camel@localhost> Content-Type: text/plain Date: Fri, 06 Jun 2008 10:22:57 -0400 Message-Id: <1212762177.29520.31.camel@localhost> Mime-Version: 1.0 X-Mailer: Evolution 2.22.1.1 Content-Transfer-Encoding: 7bit Cc: freebsd-questions@freebsd.org Subject: RE: outbound serial modem now times out or drops connection X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 Jun 2008 14:49:40 -0000 > > Trying a new modem (US Robotics external 56k serial modem) did help > > slightly. With it, we consistently connnect, but then after a short > > pause the connection is dropped. This is easily reproduced in > > "minicom": (Using the Sprint TAP modem number here). > > > > ATDT18886561727 > > CONNECT 31200/ARQ/V34/LAPM/V42BIS > > > > NO CARRIER > > > > I'm out of ideas here. This phone line is only used for this outbound > > service, although our alarm system also uses it for outbound alerts. > > > > Any suggestions for possible causes or further troubleshooting > > approaches are appreciated. > > Does that modem support Unimodem Diagnostics? What do you get from a > '#UD' command right after the failed connection attempt? Bob, Thanks for the response! I tried that with Minicom, and the prompt just goes back to the hover over the "#" sounds and sits there. From some quick Google searches, I didn't find any mentions of this modem supporting that. I'm also not familiar with the details of the TAP protocol. After the CONNECT, who should speak next? From looking at the qpage source code, it looks like we might be waiting for "ID=" to sent from the remote end, and it is not. That would make me suspect the remote end, except that multiple remote modems are responding the same way. Mark