On Fri, 09 Jul 2004 11:46:18 +0100, John Richard Smith <[EMAIL PROTECTED]> wrote:

Raffaele BELARDI wrote:

John Richard Smith wrote:

How to decypher dialupscript

Where can I get a list of explanation of the messages the dial up
window gives you in kppp ?

John


Not sure of what kppp prints since I don't use it, but V90 and older
modems use the Hayes command set (i.e. AT commands), you can find
explanation for example here:

http://docs.kde.org/en/3.1/kdenetwork/kppp/appendix-hayes-commands.html

raffaele

Much obliged Raffaele,that was what I'm looking for, though I still have a few lines unexplained, this is what I'm getting after a particular recurrence like this, kppp logs on and emails download, then halfway through the process my ISP seems to cut me off,

I doubt if it's your ISP that's cutting you off, it's more than likely that your modem's timing out.


this causes kppp to redial with this error message,

It's not actually an error message, it's a report generated by the "&V1" command.


What modem is it?

ATZ
OK
AT &F1 &V1

Try either "&F" or "&F2" instead of "&F1".

Drop the "&V1" altogether.
The "&V1" command isn't designed to be included in an init string, it's designed to be used after the connection has terminated to generate a report such as you have below:


TERMINATION REASON.......... NONE
LAST TX rate................ N/A
HIGHEST TX rate............. 300 BPS
LAST RX rate................ N/A
HIGHEST RX rate............. 300 BPS
PROTOCOL.................... N/A
COMPRESSION................. N/A
Line QUALITY................ 255
Rx LEVEL.................... 214
Highest Rx State............ 00
Highest TX State............ 00
EQM Sum..................... FFFF
RBS Pattern................. FF
Rate Drop................... FF
Digital Loss................ FFFF
Local Rtrn Count............ 00
Remote Rtrn Count........... 00
V90

Hetre's a report I've just generated by typing "AT&V1" in a dumb terminal following my last call to my ISP:


---------- 8< ----------
at&v1
TERMINATION REASON.......... LOCAL REQUEST
LAST TX rate................ 26400 BPS
HIGHEST TX rate............. 26400 BPS
LAST RX rate................ 44000 BPS
HIGHEST RX rate............. 45333 BPS
PROTOCOL.................... LAPM
COMPRESSION................. V42Bis
Line QUALITY................ 023
Rx LEVEL.................... 015
Highest Rx State............ 67
Highest TX State............ 87
EQM Sum..................... 00D6
Min Distance................ 0000
RBS Pattern................. 00
Rate Drop................... 00
Digital Loss................ 2000
Local Rtrn Count............ 00
Remote Rtrn Count........... 00
Flex fail

OK
---------- 8< ----------

OK
ATM1L1
OK
ATDT147008089916080

Why are you using "1470" in front of your ISP's phone number?

Judging by your email address, your ISP is FreeServe. When I had an account with them, it was unnecessary to use "1470".

NO CARRIER

Question is why no carrier ?

At this point in time, sorry, dunno. See my suggestions at the end.

Immediately I redial she logs on as usual.

This has now become a pattern.

I don't understand the scale of report in the "F's" and the numbers,
like Line QUALITY...... 255, is that good bad or indifferent.

Ignore 'em :-)

All my searches in google have come up with no detailed explanation, and
although your suggestion is very helpful it isn't complete, as far as I
can see.

The basic questions I need answering are,

Am I being cut off because my ISP is overloaded and needs to make room
for others,

I wouldn't have thought so. It's more than likely a modem init/config problem.

Am I being cut off because of line quality or modem config.

Am I being cut off because of software like guarddog(don't think so, but
I'm not sure) etc.


Or what ?

I suspect you have a Rockwell chipped modem, similar to mine.
If so, fire up KPPP, click the "Configure" button and then click the "Device" tab.
Things to look for here are:
Flow control should be set at "Hardware(CRTSCTS)"
Line termination should be set at "CR"
Connection speed should be "115200"
Modem timeout should be set at "60" seconds or greater.


Now click on the "Modem" tab.
"Wait for dialtone before dialing" should be X'd.

Now click on the "Modem commands" button.
For starters, try "ATZ" in the "Initialisation 1" box.
Leave the "Initialisation 2" box empty.
"No dialtone detection" should be "ATX3"

Now try it again and see what happens.
Best of luck :-)

Hope this helps.

--
Martin

Using Opera's revolutionary e-mail client: http://www.opera.com/m2/

____________________________________________________
Want to buy your Pack or Services from MandrakeSoft? 
Go to http://www.mandrakestore.com
Join the Club : http://www.mandrakeclub.com
____________________________________________________

Reply via email to