Forum Home
Press F1
Thread ID: 23788	2002-08-25 14:19:00	slow modem disconnection	Chris Wilson (431)	Press F1

Post ID	Timestamp	Content	User
73842	2002-08-26 05:22:00	I wonder what the actual problem is. Is it an excessive delay in "disconnecting" from the phone line, or is it the process of logging out of the ISP?	Graham L (2)
73843	2002-08-26 05:25:00	Nothing to do with the ISP, and as far as I'm aware you've actually disconnected enough to get a dial-tone back, just the constant bzzzzzzzzzzzzzzzzzzzzzzzz noise you get if you pick up the phone keeps going, so I'm not too sure where to look next with this one. The bzzzzzzzzzzzz is there at the same time as the dial-tone, so I think it's a matter of the computer not fully disconnecting the modem... Mike.	Mike (15)
73844	2002-08-26 05:31:00	Probably best to point out that it isn't my machine that has the problem, but my better½s machine in Greymouth.. I beleive that she can pick up the phone, and there is dead air, her modem connected to what seems like nothing, she has to wait for the computer to "click off" and then can use the phone line for speech	Chris Wilson (431)
73845	2002-08-26 05:46:00	OK, this is two different problems. CH (the better half of Chris)'s modem has actually not gone "onhook". This is what happens when only one party to a phone call has hung up. The phone line is still held, but there is no dial tone. So the ISP has cleared its end. I'm not sure if this still holds the other end (the ISP's line) busy --- it used to in the old switchgear. Mike's case: dial tone plus "something" That means that both ends have actually released the line. That's the only way you can get dialtone. So what is the other noise/signal? Is it the carrier signal? That would be a fairly high frequency. Anyway, the modem must be disconnecting then connecting again. But it shouldn't put carrier tone on the line ... it should be silent until it sends the DTMF dialling signals. Isn't technology marvellous? Never a dull moment. If only the bloody stuff would work.	Graham L (2)
73846	2002-08-26 06:11:00	Chris, In Win98, Modem Advanced Settings gives a check box for "Keep a Log File" I don't know where to find it in ME, but in win98 it's NOT available from Start - control Panel - Modems, but from (deep breath) My Computer - Properties - Device Mangler - Modem - [Your Modem's Name Here] - Properties - Connection - Advanced - Append to Log (gasp) you can ask for a log file to be kept. It will be found in the Windows Directory under [Your Modem's Name].log Mine lives in C:\Windows\HSP56 MicroModem.log Look for this sort of information. 08-26-2002 00:24:31.70 - Hanging up the modem. 08-26-2002 00:24:31.70 - Hardware hangup by lowering DTR. 08-26-2002 00:24:32.90 - WARNING: The modem did not respond to lowering DTR. Trying software hangup... 08-26-2002 00:24:32.90 - Send: +++ 08-26-2002 00:24:32.91 - Recv: <cr><lf>NO CARRIER<cr><lf> 08-26-2002 00:24:32.91 - Interpreted response: No Carrier 08-26-2002 00:24:32.91 - Send: ATH<cr> 08-26-2002 00:24:33.03 - Recv: <cr><lf>OK<cr><lf> 08-26-2002 00:24:33.03 - Interpreted response: Ok As you can see from the 100ths of a second column, It shouldn't take too long even when there IS a problem. On a very quick look through my log for the last 100 or so connections, it's failed twice on lowering Data Terminal Ready, and each time succeeded with the Hayes "+++" "get lost" command, followed by the "Ahoy there, Sling your Hook, matey!" request. I hope Win ME can do the same for your friend - I'm sure someone else on the forum will know. Cheers, Alan (Freezing my butt off in Christchurch)	Alan Carpenter (540)
73847	2002-08-26 06:18:00	Just a note on interpreting that: "+++" sent to the modem switches it from data to control mode, so it will respond to "AT" commands, such as "ATH" -- the AT is the command prefix, the "H" is hook condition . The default is 0, which could appear as ATH0 which means "onhook" =( not connected . ATH1 means "offhook" = connected .	Graham L (2)
73848	2002-08-26 07:17:00	Thanks, Graham. For others, here's a quite friendly listing of the Hayes Modem Command Set (docs.kde.org) . I'm quite a fan of the ATI (that's "eye", not "one" - for Inquiry, Information, or Interrogation, you choose) followed by the digit of your choice. Start at ATI0 and move up from ATI1 until you get "error" or similar. You might learn something interesting about your modem. Cheers, Alan (still freezing) Carpenter	Alan Carpenter (540)
73849	2002-08-26 07:30:00	I recall (several years ago when on the Xtra helpdesk) there being an AT command to fix this, but do you think I can remember it now ?? Grrrrr.	antmannz (28)
73850	2002-08-27 03:56:00	Well here's the hangup portion from my log file for anyone to see if they can spot what the problem could be - although this example might be a bad one, cause I didn't have to wait for disconnect this time: 08-27-2002 14:50:51.169 - Read: Total: 1280810, Per/Sec: 269, Written: Total: 246046, Per/Sec: 93 08-27-2002 14:51:05.019 - Hanging up the modem. 08-27-2002 14:51:05.019 - Hardware hangup by lowering DTR. 08-27-2002 14:51:05.820 - Detected CD dropped from lowering DTR 08-27-2002 14:51:05.820 - Recv: <cr><lf>OK<cr><lf> 08-27-2002 14:51:05.820 - Interpreted response: OK 08-27-2002 14:51:05.830 - Send: ATH<cr> 08-27-2002 14:51:05.850 - Recv: <cr><lf>OK<cr><lf> 08-27-2002 14:51:05.850 - Interpreted response: OK 08-27-2002 14:51:05.870 - Send: at#ud<cr> 08-27-2002 14:51:05.900 - Recv: <cr><lf>DIAG <2A4D3263 0=10><cr><lf>DIAG <2A4D3263 1=7><cr><lf>DIAG <2A4D3263 2=0><cr><lf>DIAG <2A4D3263 3=0><cr><lf>DIAG <2A4D3263 4=""><cr><lf>DIAG <2A4D3263 5=""><cr><lf>DIAG <2A4D3263 10=13 11=F 12=26><cr><lf>DIAG <2A4D3263 18=40222220><cr><lf>DIAG <2A4D3263 20=E 22=C80 24=725><cr><lf>DIAG < 08-27-2002 14:51:05.900 - Unknown Response 08-27-2002 14:51:05.900 - 115200,8,N,1, ctsfl=1, rtsctl=2 08-27-2002 14:51:05.900 - Initializing modem. 08-27-2002 14:51:06.100 - Send: AT<cr> 08-27-2002 14:51:06.120 - Recv: <cr><lf>OK<cr><lf> 08-27-2002 14:51:06.120 - Interpreted response: OK 08-27-2002 14:51:06.130 - Send: AT&FE0V1S0=0&C1&D2+MR=2;+DR=1;+ER=1;W2<cr> 08-27-2002 14:51:06.150 - Recv: <cr><lf>OK<cr><lf> 08-27-2002 14:51:06.150 - Interpreted response: OK 08-27-2002 14:51:06.160 - Send: ATS7=60M1+ES=3,0,2;+DS=3;+IFC=2,2;X4<cr> 08-27-2002 14:51:06.180 - Recv: <cr><lf>OK<cr><lf> 08-27-2002 14:51:06.180 - Interpreted response: OK 08-27-2002 14:51:06.190 - Waiting for a call. 08-27-2002 14:51:06.200 - Send: ATS0=0<cr> 08-27-2002 14:51:06.220 - Recv: <cr><lf>OK<cr><lf> 08-27-2002 14:51:06.220 - Interpreted response: OK 08-27-2002 14:51:06.230 - Session Statistics: 08-27-2002 14:51:06.230 - Reads : 24 bytes 08-27-2002 14:51:06.230 - Writes: 86 bytes HTH :) Mike.	Mike (15)
73851	2002-08-27 05:14:00	Mmmm . I was about to remark "What problem Mike?" but I had to scroll all the way across to get to the Reply button . ;-) That diagnostic output is all in one line . . . That's about what I would expect to see . A 13 second delay after disconnecting from the ISP, to start the physical disconnect . The DTR one may turn off the "CD" (carrier detect signal --- which ideally come from the other end . . . but might be locally faked) then about a second to hang up the phone line, and reset the modem ready to answer any incoming call . I wonder why the driver sends the diagnostic request . . . I was about to say that the driver doesn't recognise the response, but that log is probably from something else . Is it? If the log is produced by the driver, it ought to handle it . The DIAG stuff looks like a series of lines containing a series of register contents (e . g . 1=0) preceded by a long hexadecimal number which is probably a model and software revision ID number . I wonder if the values differ when you have the long delay .	Graham L (2)
1 2 3