1. disable software compression

2. slow down the modem

Both could probably do with a firmware/driver update to the most recent
version.

Also, check out www.modemsite.com for lots of great tips and tricks.

--
  Troy Settle
  Pulaski Networks
  540.994.4254 - 866.477.5638
  http://www.psknet.com
 

> -----Original Message-----
> From: owner-ascend-users at max.bungi.com 
> [mailto:owner-ascend-users at max.bungi.com] On Behalf Of 
> niblettda at gru.com
> Sent: Monday, November 25, 2002 11:25 AM
> To: b.weeber at viastore.de; ascend-users at bungi.com
> Subject: RE: (ASCEND) Disconnect code 185, Progress 30 problem
> 
> 
> Burkhard,
> 
> Actually, I know it's hanging up at the LCP negotiation.
> I'm still confused why it works on my old number, but
> not my new number.  The hardware is the same, the TAOS
> version is the same.  People seem to negotiate the same
> connect speed as before, and can't connect, but if they
> force the modem to connect at a lower speed (like 33.6)
> they connect just fine to the new number.
> 
> Here is a log from a machine calling my new number:
> 
> 10/25/02	5:12 PM	Dialing 5821111
> 10/25/02	5:12 PM	CCL write: "ATDT5821111\13"
> 10/25/02	5:13 PM	CCL match: "CARRIER"
> 10/25/02	5:13 PM	CCL match: "CONNECT "
> 10/25/02	5:13 PM	CCL match: "49333"
> 10/25/02	5:13 PM	CCL match: "\10"
> 10/25/02	5:13 PM	PPP connection started.
> 10/25/02	5:13 PM	LCP: Sending Configuration Request.
> 10/25/02	5:13 PM	LCP: >> Async Map = 0x00000000.
> 10/25/02	5:13 PM	LCP: >> Magic Number = 0xB4EA711E.
> 10/25/02	5:13 PM	LCP: >> Protocol Compression On
> 10/25/02	5:13 PM	LCP: >> Address/Control Compression On
> 10/25/02	5:13 PM	LCP: Sending Configuration Request.
> 10/25/02	5:13 PM	LCP: >> Async Map = 0x00000000.
> 10/25/02	5:13 PM	LCP: >> Magic Number = 0xB4EA711E.
> 10/25/02	5:13 PM	LCP: >> Protocol Compression On
> 10/25/02	5:13 PM	LCP: >> Address/Control Compression On
> ... Repeated 6 more times ...
> 10/25/02	5:13 PM	No response from the remote side.
> 10/25/02	5:13 PM	CCL write: "+++ATH\13"
> 10/25/02	5:13 PM	CCL match: "OK\13\10"
> 10/25/02	5:13 PM	CCL write: "AT&F\13"
> 10/25/02	5:13 PM	CCL match: "OK\13\10"
> 10/25/02	5:13 PM	The remote side is not responding correctly.  
> 10/25/02	5:13 PM	Connection terminated.
> 
> 
> On the same machine, dialing my old number, I get this:
> 
> 10/25/02	5:20 PM	Dialing 3777997
> 10/25/02	5:20 PM	CCL write: "ATDT3777997\13"
> 10/25/02	5:21 PM	CCL match: "CARRIER"
> 10/25/02	5:21 PM	CCL match: "PROTOCOL: LAP"
> 10/25/02	5:21 PM	CCL match: "CONNECT "
> 10/25/02	5:21 PM	CCL match: "49333"
> 10/25/02	5:21 PM	CCL match: "\10"
> 10/25/02	5:21 PM	PPP connection started.
> 10/25/02	5:21 PM	LCP: Sending Configuration Request.
> 10/25/02	5:21 PM	LCP: >> Async Map = 0x00000000.
> 10/25/02	5:21 PM	LCP: >> Magic Number = 0xD1BB17CD.
> 10/25/02	5:21 PM	LCP: >> Protocol Compression On
> 10/25/02	5:21 PM	LCP: >> Address/Control Compression On
> 10/25/02	5:21 PM	LCP: Received Configuration Request.
> 10/25/02	5:21 PM	LCP: >> MRU = 1524.
> ... All the normal PPP negotiation ...
> 10/25/02	5:21 PM	PPP ready for TCP/IP with IP address 
> 64.238.160.252.
> 10/25/02	5:21 PM	Connection established at 49333 bps.
> 10/25/02	5:21 PM	CCL write: "+++ATH\13"
> 10/25/02	5:22 PM	CCL match: "OK\13\10"
> 10/25/02	5:22 PM	CCL write: "AT&F\13"
> 10/25/02	5:22 PM	CCL match: "OK\13\10"
> 10/25/02	5:22 PM	Connection terminated.
> 
> Thanks again.
> 
> --
> David A. Niblett               | eMail: niblettda at gru.net
> Network Administrator          | Phone: (352) 334-3400
> Gainesville Regional Utilities | Web: http://www.gru.net/
> 
> 
> 
> > -----Original Message-----
> > From: Burkhard Weeber [mailto:b.weeber at viastore.de]
> > Sent: Monday, November 25, 2002 9:53 AM
> > To: niblettda at gru.com; Ascend User List (E-Mail)
> > Subject: RE: (ASCEND) Disconnect code 185, Progress 30 problem
> > 
> > 
> > Looks like the PPP handshake fails.
> > I would use a telnet client which can capture to file, go 
> > into diagnostics
> > mode and do a "wannext 1500".
> > Feed that file to "ethereal" and you will get a quite good 
> > understanding
> > what happens.
> > 
> > For a quick analysis of the snipplet you gave I would say 
> > that the giving
> > away of the IP address fails or is late  since the host is 
> > still "0.0.0.0".
> > 
> > Burkhard Weeber
> > viastore systems GmbH
> > P/O Box 300668
> > D-70446 Stuttgart
> > Tel: +49-711-9818-0
> > Email: B.Weeber at viastore.de
> > 
> > Disclaimer:
> > The opinions expressed herein are my personal points of view 
> > and do not
> > represent those of my employer.
> > 
> > Windows95: <win-doz-nin-te-fiv> n.
> > 32 bit extensions and a graphical shell for a 16 bit patch 
> to an 8 bit
> > operating system originally coded for a 4 bit microprocessor, 
> > written by
> > a 2 bit company, that can't stand 1 bit of competition.
> > 
> > 
> > 
> > > -----Original Message-----
> > > From: niblettda at gru.com [mailto:niblettda at gru.com]
> > > Sent: Monday, November 25, 2002 3:15 PM
> > > To: b.weeber at viastore.de
> > > Subject: RE: (ASCEND) Disconnect code 185, Progress 30 problem
> > >
> > >
> > > Burkhard,
> > >
> > > It takes 20 seconds from the time the call starts to when
> > > the TNT hangs up.  I suppose that is could be too short, but
> > > that doesn't seem to be to me.  Here is a chunk of syslog
> > > that I have on one of these calls.
> > >
> > > Nov 25 08:56:53 tnt2 1/17: [1/1/1/14] Incoming Call,
> > > 3523795987 [MBID 2214;
> > > 3523795987->3525821111]
> > > Nov 25 08:56:53 tnt2 1/17: [1/5/72/0] Assigned to port,
> > > 3523795987 [MBID
> > > 2214; 3523795987->3525821111]
> > > Nov 25 08:56:55 tnt2 1/17: [1/1/1/14] Call Connected,
> > > 3523795987 [MBID 2214;
> > > 3523795987->3525821111]
> > > Nov 25 08:57:16 tnt2 1/17: [1/1/1/14] Call Disconnected 
> [MBID 2214;
> > > 3523795987->3525821111]
> > > Nov 25 08:57:16 tnt2 1/17: [1/5/72/0] Call Terminated [MBID 2214;
> > > 3523795987->3525821111]
> > > Nov 25 08:57:16 tnt2 1/5: [1/5/72/0] STOP: 'Answer'; cause
> > > 185.; progress
> > > 30.; host 0.0.0.0 [MBID 2214; 3523795987->3525821111] [Answer]
> > >
> > > Thanks!
> > >
> > > --
> > > David A. Niblett               | eMail: niblettda at gru.net
> > > Network Administrator          | Phone: (352) 334-3400
> > > Gainesville Regional Utilities | Web: http://www.gru.net/
> > >
> > >
> > >
> > > > -----Original Message-----
> > > > From: Burkhard Weeber [mailto:b.weeber at viastore.de]
> > > > Sent: Monday, November 25, 2002 8:42 AM
> > > > To: niblettda at gru.com
> > > > Subject: RE: (ASCEND) Disconnect code 185, Progress 30 problem
> > > >
> > > >
> > > > See the RADIUS documentation:
> > > >
> > > > Disconnect code 185 -> remote end hung up
> > > > Progress code 30 -> virtual connection has ended.
> > > >
> > > > Looks like there is a very tight timeout on the connection
> > > > program on your
> > > > clients.
> > > >
> > > > Burkhard Weeber
> > > > viastore systems GmbH
> > > > P/O Box 300668
> > > > D-70446 Stuttgart
> > > > Tel: +49-711-9818-0
> > > > Email: B.Weeber at viastore.de
> > > >
> > > > Disclaimer:
> > > > The opinions expressed herein are my personal points of view
> > > > and do not
> > > > represent those of my employer.
> > > >
> > > > Windows95: <win-doz-nin-te-fiv> n.
> > > > 32 bit extensions and a graphical shell for a 16 bit patch
> > > to an 8 bit
> > > > operating system originally coded for a 4 bit microprocessor,
> > > > written by
> > > > a 2 bit company, that can't stand 1 bit of competition.
> > > >
> > > >
> > > >
> > > > > -----Original Message-----
> > > > > From: owner-ascend-users at max.bungi.com
> > > > > [mailto:owner-ascend-users at max.bungi.com]On Behalf Of
> > > > > niblettda at gru.com
> > > > > Sent: Monday, November 25, 2002 1:58 PM
> > > > > To: ascend-users at bungi.com
> > > > > Subject: FW: (ASCEND) Disconnect code 185, Progress 30 problem
> > > > >
> > > > >
> > > > > Anyone have any thoughts on below?  No on responded so I
> > > > > wanted to repost my plea for help.
> > > > >
> > > > > Thanks.
> > > > >
> > > > > --
> > > > > David A. Niblett               | eMail: niblettda at gru.net
> > > > > Network Administrator          | Phone: (352) 334-3400
> > > > > Gainesville Regional Utilities | Web: http://www.gru.net/
> > > > >
> > > > >
> > > > >
> > > > > -----Original Message-----
> > > > > From: niblettda at gru.com [mailto:niblettda at gru.com]
> > > > > Sent: Wednesday, November 20, 2002 2:25 PM
> > > > > To: ascend-users at bungi.com
> > > > > Subject: (ASCEND) Disconnect code 185, Progress 30 problem
> > > > >
> > > > >
> > > > > Hi all,
> > > > >
> > > > > I'm hoping that some still read this list out there.  I've
> > > > > got a very strange issue with a group of users.  Let me
> > > > > first start with what I had.
> > > > >
> > > > > 2 MaxTNT's with 96 port modem cards and 2 8 port T1 cards.
> > > > > We received all of our PRI's from the local telco.
> > > > >
> > > > > We then purchased our own telco switch to handle our PRI's
> > > > > and stop paying the local telco.  So now we get trunks from
> > > > > the LEC, which I then turn into PRI's to service our TNT's.
> > > > >
> > > > > At the same time I switched from using the 8 port T1 cards
> > > > > to using a channelized DS3 card.
> > > > >
> > > > >
> > > > > My problem is with the new set up, 99% of my customers work
> > > > > just fine.  However, it would appear that almost all of my
> > > > > Mac clients can't connect, they get a 185/30 for the
> > > > > disconnect/progress code.  According to Ascend 185/30 =
> > > > >
> > > > >  The TAOS unit received the user's modem call and allocated a
> > > > >  modem to answer the call. Before completing modem
> > > > >  negotiation, the TAOS unit could not detect any signal from
> > > > >  the user's computer modem, probably because the modems
> > > > >  had marginal line quality. Because the TAOS unit's modem
> > > > >  has a digital connection to its local CO, the poor 
> line quality
> > > > >  occurred between the user's modem and its local CO. The
> > > > >  problem might also have been caused by an incompatibility
> > > > >  between the modems.
> > > > >
> > > > > These customers can connect at speeds slower than ~40k, but
> > > > > never connect at higher.  The weird part is that a Windows
> > > > > laptop works just fine at 49k on their phone line.
> > > > >
> > > > > To add to the weirdness, I now have one ISDN customer (using
> > > > > a windows PC) that can connect at 56K, but not at 64K.  They
> > > > > get the exact same 185/30 as the Mac people.
> > > > >
> > > > > So I don't see how it can be phone line related since the
> > > > > ISDN user has digital lines, and we have digital PRI's.
> > > > >
> > > > > Please help me before I loose all my hair and have a flat spot
> > > > > on my head from banging it on the wall.
> > > > >
> > > > > Thanks.
> > > > >
> > > > > --
> > > > > David A. Niblett               | eMail: niblettda at gru.net
> > > > > Network Administrator          | Phone: (352) 334-3400
> > > > > Gainesville Regional Utilities | Web: http://www.gru.net/
> > > > >
> > > > > ++ Ascend Users Mailing List ++
> > > > > To unsubscribe:	send unsubscribe to
> > > > > ascend-users-request at bungi.com
> > > > > Archives: http://www.nexial.com/mailinglists/
> > > > > ++ Ascend Users Mailing List ++
> > > > > To unsubscribe:	send unsubscribe to
> > > > > ascend-users-request at bungi.com
> > > > > Archives: http://www.nexial.com/mailinglists/
> > > > >
> > > >
> > >
> > 
> ++ Ascend Users Mailing List ++
> To unsubscribe:	send unsubscribe to 
> ascend-users-request at bungi.com
> Archives: http://www.nexial.com/mailinglists/
> 
> 

++ Ascend Users Mailing List ++
To unsubscribe:	send unsubscribe to ascend-users-request at bungi.com
Archives: http://www.nexial.com/mailinglists/