AutoPPP fails to establish a connection during long distance calls - PPP

This is a discussion on AutoPPP fails to establish a connection during long distance calls - PPP ; Hi This is Saradhi. I am using mgetty to provide a PPP (AutoPPP) solution for one of our product. I am facing some weired problems when the call is received. The following are the problems that i have faced 1) ...

+ Reply to Thread
Results 1 to 5 of 5

Thread: AutoPPP fails to establish a connection during long distance calls

  1. AutoPPP fails to establish a connection during long distance calls

    Hi

    This is Saradhi. I am using mgetty to provide a PPP (AutoPPP) solution
    for one of our product. I am facing some weired problems when the call
    is received.

    The following are the problems that i have faced

    1) timeout in chat script, waiting for `'
    2) failed in mg_init_data, dev=ttyS6, pid=640 or failed dev=ttyS6,
    pid=641, got signal 15, exiting

    In both the cases, the problem was seen only during a long distance
    call[isdn](Never observed in all other cases).

    And this is inconsistent also(some times connection do get
    establishes).

    I have added the logs for both these problems below.

    I am using minimal configuration on the mgetty side. The Setup is as
    follows

    1) mgetty.config

    debug 4
    speed 9600

    2) login.config
    /AutoPPP/ - a_ppp /usr/sbin/pppd ttyS

    Init chat, fource init chat and answer chat sequences are the default
    ones provided by mgetty (release is 1.0.0).

    Linux kernel version is 2.4.20

    Am i missing some settings?

    Thanks in advance.

    Regards
    Saradhi

    ================================================== ============
    Problem 1:
    ================================================== ============
    09/15 00:53:51 yS6 mgetty: official release 1.0.0
    09/15 00:53:51 yS6 check for lockfiles
    09/15 00:53:51 yS6 locking the line
    09/15 00:53:52 yS6 lowering DTR to reset Modem
    09/15 00:53:52 yS6 send: \dATQ0V1H0[0d]
    09/15 00:53:53 yS6 waiting for ``OK'' ** found **
    09/15 00:53:53 yS6 send: ATS0=0Q0&D0[0d]
    09/15 00:53:53 yS6 waiting for ``OK'' ** found **
    09/15 00:53:53 yS6 waiting...
    09/15 10:32:17 yS6 waiting for ``RING'' ** found **
    09/15 10:32:17 yS6 send: ATA[0d]
    09/15 10:32:17 yS6 waiting for ``CONNECT'' ** found **
    09/15 10:32:33 yS6 send:
    09/15 10:32:33 yS6 waiting for ``
    '' ** found **
    09/15 10:32:54 yS6 getlogname: timeout

    09/15 10:33:23 ##### failed dev=ttyS6, pid=557, got signal 1, exiting

    --
    09/15 10:33:23 yS6 mgetty: official release 1.0.0
    09/15 10:33:23 yS6 check for lockfiles
    09/15 10:33:23 yS6 locking the line
    09/15 10:33:24 yS6 lowering DTR to reset Modem
    09/15 10:33:24 yS6 send: \dATQ0V1H0[0d]
    09/15 10:33:25 yS6 waiting for ``OK'' ** found **
    09/15 10:33:25 yS6 send: ATS0=0Q0&D0[0d]
    09/15 10:33:25 yS6 waiting for ``OK'' ** found **
    09/15 10:33:25 yS6 waiting...
    09/15 10:34:48 yS6 waiting for ``RING'' ** found **
    09/15 10:34:48 yS6 send: ATA[0d]
    09/15 10:34:48 yS6 waiting for ``CONNECT'' ** found **
    09/15 10:35:09 yS6 send:
    09/15 10:35:09 yS6 waiting for ``
    ''
    09/15 10:36:33 yS6 timeout in chat script, waiting for `
    '
    09/15 10:36:33 ##### failed timeout dev=ttyS6, pid=646, caller=none,
    conn='21600/ARQ', name=''

    --
    09/15 10:36:33 yS6 mgetty: official release 1.0.0
    09/15 10:36:33 yS6 check for lockfiles
    09/15 10:36:33 yS6 locking the line
    09/15 10:36:34 yS6 lowering DTR to reset Modem
    09/15 10:36:34 yS6 send: \dATQ0V1H0[0d]
    09/15 10:36:35 yS6 waiting for ``OK'' ** found **
    09/15 10:36:35 yS6 send: ATS0=0Q0&D0[0d]
    09/15 10:36:35 yS6 waiting for ``OK'' ** found **
    09/15 10:36:36 yS6 waiting...
    09/15 10:36:56 yS6 waiting for ``RING'' ** found **
    09/15 10:36:56 yS6 send: ATA[0d]
    09/15 10:36:56 yS6 waiting for ``CONNECT'' ** found **
    09/15 10:37:15 yS6 send:
    09/15 10:37:15 yS6 waiting for ``
    ''
    09/15 19:23:18 yS6 timeout in chat script, waiting for `
    '
    09/15 19:23:18 ##### failed timeout dev=ttyS6, pid=647, caller=none,
    conn='16800/ARQ', name=''

    --
    09/15 19:23:18 yS6 mgetty: official release 1.0.0
    09/15 19:23:18 yS6 check for lockfiles
    09/15 19:23:18 yS6 locking the line
    09/15 19:23:18 yS6 WARNING: DCD line still active, check modem
    settings (AT&Dx)
    09/15 19:23:18 yS6 lowering DTR to reset Modem
    09/15 19:23:19 yS6 send: \dATQ0V1H0[0d]
    09/15 19:23:20 yS6 waiting for ``OK''
    09/15 19:24:17 ##### failed dev=ttyS6, pid=648, got signal 15, exiting

    --
    09/15 19:24:26 yS6 mgetty: official release 1.0.0
    09/15 19:24:26 yS6 check for lockfiles
    09/15 19:24:26 yS6 locking the line
    09/15 19:24:27 yS6 lowering DTR to reset Modem
    09/15 19:24:27 yS6 send: \dATQ0V1H0[0d]
    09/15 19:24:28 yS6 waiting for ``OK'' ** found **
    09/15 19:24:28 yS6 send: ATS0=0Q0&D0[0d]
    09/15 19:24:28 yS6 waiting for ``OK'' ** found **
    09/15 19:24:29 yS6 waiting...
    09/15 20:24:29 yS6 checking if modem is still alive
    09/15 20:24:29 yS6 mdm_send: 'AT' -> OK
    09/15 20:24:29 yS6 waiting...
    09/15 20:47:46 yS6 waiting for ``RING'' ** found **
    09/15 20:47:47 yS6 send: ATA[0d]
    09/15 20:47:47 yS6 waiting for ``CONNECT'' ** found **
    09/15 20:48:02 yS6 send:
    09/15 20:48:02 yS6 waiting for ``
    ''

    ================================================== ============
    PROBLEM 2:
    ================================================== ============
    05/27 23:18:26 yS6 mgetty: official release 1.0.0
    05/27 23:18:26 yS6 check for lockfiles
    05/27 23:18:26 yS6 locking the line
    05/27 23:18:27 yS6 WARNING: DSR is off - modem turned off or bad
    cable?
    05/27 23:18:27 yS6 lowering DTR to reset Modem
    05/27 23:18:27 yS6 send: \dATQ0V1H0[0d]
    05/27 23:18:28 yS6 waiting for ``OK'' ** found **
    05/27 23:18:28 yS6 send: ATS0=0Q0&D0[0d]
    05/27 23:18:28 yS6 waiting for ``OK'' ** found **
    05/27 23:18:28 yS6 waiting...
    05/27 23:24:58 yS6 waiting for ``RING'' ** found **
    05/27 23:24:58 yS6 send: ATA[0d]
    05/27 23:24:58 yS6 waiting for ``CONNECT''
    05/27 23:26:02 yS6 found action string: ``NO CARRIER''
    05/27 23:26:02 ##### failed A_FAIL dev=ttyS6, pid=528, caller=none,
    conn='', name=''

    --
    05/27 23:26:02 yS6 mgetty: official release 1.0.0
    05/27 23:26:02 yS6 check for lockfiles
    05/27 23:26:02 yS6 locking the line
    05/27 23:26:02 yS6 WARNING: DSR is off - modem turned off or bad
    cable?
    05/27 23:26:02 yS6 lowering DTR to reset Modem
    05/27 23:26:03 yS6 send: \dATQ0V1H0[0d]
    05/27 23:26:04 yS6 waiting for ``OK'' ** found **
    05/27 23:26:04 yS6 send: ATS0=0Q0&D0[0d]
    05/27 23:26:04 yS6 waiting for ``OK'' ** found **
    05/27 23:26:04 yS6 waiting...
    05/27 23:26:18 yS6 waiting for ``RING'' ** found **
    05/27 23:26:18 yS6 send: ATA[0d]
    05/27 23:26:18 yS6 waiting for ``CONNECT''
    05/27 23:27:21 yS6 found action string: ``NO CARRIER''
    05/27 23:27:21 ##### failed A_FAIL dev=ttyS6, pid=631, caller=none,
    conn='', name=''

    --
    05/27 23:27:21 yS6 mgetty: official release 1.0.0
    05/27 23:27:21 yS6 check for lockfiles
    05/27 23:27:21 yS6 locking the line
    05/27 23:27:21 yS6 WARNING: DSR is off - modem turned off or bad
    cable?
    05/27 23:27:21 yS6 lowering DTR to reset Modem
    05/27 23:27:22 yS6 send: \dATQ0V1H0[0d]
    05/27 23:27:23 yS6 waiting for ``OK'' ** found **
    05/27 23:27:23 yS6 send: ATS0=0Q0&D0[0d]
    05/27 23:27:23 yS6 waiting for ``OK'' ** found **
    05/27 23:27:23 yS6 waiting...
    05/27 23:28:58 yS6 waiting for ``RING'' ** found **
    05/27 23:28:58 yS6 send: ATA[0d]
    05/27 23:28:58 yS6 waiting for ``CONNECT''
    05/27 23:30:01 yS6 found action string: ``NO CARRIER''
    05/27 23:30:01 ##### failed A_FAIL dev=ttyS6, pid=632, caller=none,
    conn='', name=''

    --
    05/27 23:30:01 yS6 mgetty: official release 1.0.0
    05/27 23:30:01 yS6 check for lockfiles
    05/27 23:30:01 yS6 locking the line
    05/27 23:30:01 yS6 WARNING: DSR is off - modem turned off or bad
    cable?
    05/27 23:30:01 yS6 lowering DTR to reset Modem
    05/27 23:30:02 yS6 send: \dATQ0V1H0[0d]
    05/27 23:30:03 yS6 waiting for ``OK'' ** found **
    05/27 23:30:03 yS6 send: ATS0=0Q0&D0[0d]
    05/27 23:30:03 yS6 waiting for ``OK'' ** found **
    05/27 23:30:03 yS6 waiting...
    05/27 23:30:37 yS6 waiting for ``RING'' ** found **
    05/27 23:30:37 yS6 send: ATA[0d]
    05/27 23:30:37 yS6 waiting for ``CONNECT''
    05/27 23:31:41 yS6 found action string: ``NO CARRIER''
    05/27 23:31:41 ##### failed A_FAIL dev=ttyS6, pid=633, caller=none,
    conn='', name=''

    --
    05/27 23:31:41 yS6 mgetty: official release 1.0.0
    05/27 23:31:41 yS6 check for lockfiles
    05/27 23:31:41 yS6 locking the line
    05/27 23:31:41 yS6 WARNING: DSR is off - modem turned off or bad
    cable?
    05/27 23:31:41 yS6 lowering DTR to reset Modem
    05/27 23:31:42 yS6 send: \dATQ0V1H0[0d]
    05/27 23:31:43 yS6 waiting for ``OK'' ** found **
    05/27 23:31:43 yS6 send: ATS0=0Q0&D0[0d]
    05/27 23:31:43 yS6 waiting for ``OK'' ** found **
    05/27 23:31:43 yS6 waiting...
    05/27 23:36:25 yS6 waiting for ``RING'' ** found **
    05/27 23:36:25 yS6 send: ATA[0d]
    05/27 23:36:25 yS6 waiting for ``CONNECT''
    05/27 23:37:29 yS6 found action string: ``NO CARRIER''
    05/27 23:37:29 ##### failed A_FAIL dev=ttyS6, pid=636, caller=none,
    conn='', name=''

    --
    05/27 23:37:29 yS6 mgetty: official release 1.0.0
    05/27 23:37:29 yS6 check for lockfiles
    05/27 23:37:29 yS6 locking the line
    05/27 23:37:29 yS6 WARNING: DSR is off - modem turned off or bad
    cable?
    05/27 23:37:29 yS6 lowering DTR to reset Modem
    05/27 23:37:30 yS6 send: \dATQ0V1H0[0d]
    05/27 23:37:31 yS6 waiting for ``OK'' ** found **
    05/27 23:37:31 yS6 send: ATS0=0Q0&D0[0d]
    05/27 23:37:31 yS6 waiting for ``OK'' ** found **
    05/27 23:37:31 yS6 waiting...
    05/27 23:39:28 yS6 waiting for ``RING'' ** found **
    05/27 23:39:28 yS6 send: ATA[0d]
    05/27 23:39:28 yS6 waiting for ``CONNECT'' ** found **
    05/27 23:39:48 yS6 send:
    05/27 23:39:48 yS6 waiting for ``
    '' ** found **
    05/27 23:39:50 ##### data dev=ttyS6, pid=639, caller=none,
    conn='9600/REL - LAPM', name='', cmd='/usr/sbin/pppd', user='/AutoPPP/'

    --
    05/27 23:40:20 yS6 mgetty: official release 1.0.0
    05/27 23:40:20 yS6 check for lockfiles
    05/27 23:40:20 yS6 locking the line
    05/27 23:40:21 yS6 WARNING: DCD line still active, check modem
    settings (AT&Dx)
    05/27 23:40:21 yS6 WARNING: DSR is off - modem turned off or bad
    cable?
    05/27 23:40:21 yS6 lowering DTR to reset Modem
    05/27 23:40:22 yS6 send: \dATQ0V1H0[0d]
    05/27 23:40:22 yS6 waiting for ``OK''
    05/27 23:40:25 yS6 found action string: ``NO CARRIER''
    05/27 23:40:25 yS6 init chat failed, exiting...: Invalid argument
    05/27 23:40:25 ##### failed in mg_init_data, dev=ttyS6, pid=640

    --
    05/27 23:40:25 yS6 mgetty: official release 1.0.0
    05/27 23:40:25 yS6 check for lockfiles
    05/27 23:40:25 yS6 locking the line
    05/27 23:40:26 yS6 WARNING: DSR is off - modem turned off or bad
    cable?
    05/27 23:40:26 yS6 lowering DTR to reset Modem
    05/27 23:40:27 yS6 send: \dATQ0V1H0[0d]
    05/27 23:40:27 yS6 waiting for ``OK'' ** found **
    05/27 23:40:27 yS6 send: ATS0=0Q0&D0[0d]
    05/27 23:40:27 yS6 waiting for ``OK'' ** found **
    05/27 23:40:28 yS6 waiting...
    05/28 00:01:36 ##### failed dev=ttyS6, pid=641, got signal 15, exiting

    --
    05/28 01:04:20 yS6 mgetty: official release 1.0.0
    05/28 01:04:20 yS6 check for lockfiles
    05/28 01:04:20 yS6 locking the line
    05/28 01:04:21 yS6 WARNING: DSR is off - modem turned off or bad
    cable?
    05/28 01:04:21 yS6 lowering DTR to reset Modem
    05/28 01:04:21 yS6 send: \dATQ0V1H0[0d]
    05/28 01:04:22 yS6 waiting for ``OK'' ** found **
    05/28 01:04:22 yS6 send: ATS0=0Q0&D0[0d]
    05/28 01:04:22 yS6 waiting for ``OK'' ** found **
    05/28 01:04:22 yS6 waiting...
    05/28 01:04:34 yS6 waiting for ``RING'' ** found **
    05/28 01:04:34 yS6 send: ATA[0d]
    05/28 01:04:34 yS6 waiting for ``CONNECT'' ** found **
    05/28 01:05:05 yS6 send:
    05/28 01:05:05 yS6 waiting for ``
    '' ** found **
    05/28 01:05:09 yS6 clean_line: only 500 of 2780 bytes logged
    05/28 01:05:29 yS6 getlogname: timeout

    05/28 01:05:51 ##### failed dev=ttyS6, pid=651, got signal 1, exiting

    --
    05/28 01:05:51 yS6 mgetty: official release 1.0.0
    05/28 01:05:51 yS6 check for lockfiles
    05/28 01:05:51 yS6 locking the line
    05/28 01:05:51 yS6 WARNING: DSR is off - modem turned off or bad
    cable?
    05/28 01:05:51 yS6 lowering DTR to reset Modem
    05/28 01:05:52 yS6 send: \dATQ0V1H0[0d]
    05/28 01:05:52 yS6 waiting for ``OK'' ** found **
    05/28 01:05:52 yS6 send: ATS0=0Q0&D0[0d]
    05/28 01:05:52 yS6 waiting for ``OK'' ** found **
    05/28 01:05:53 yS6 waiting...
    05/28 01:07:46 yS6 waiting for ``RING'' ** found **
    05/28 01:07:46 yS6 send: ATA[0d]
    05/28 01:07:46 yS6 waiting for ``CONNECT'' ** found **
    05/28 01:08:16 yS6 send:
    05/28 01:08:16 yS6 waiting for ``
    '' ** found **
    05/28 01:08:22 yS6 clean_line: only 500 of 5922 bytes logged
    05/28 01:08:43 yS6 getlogname: timeout

    05/28 01:08:47 yS6 login name all uppercase, set IUCLC OLCUC
    05/28 01:08:47 ##### data dev=ttyS6, pid=652, caller=none, conn='9600',
    name='', cmd='/bin/login', user='` l'

    --
    05/28 01:08:47 yS6 mgetty: official release 1.0.0
    05/28 01:08:47 yS6 check for lockfiles
    05/28 01:08:47 yS6 locking the line
    05/28 01:08:48 yS6 WARNING: DCD line still active, check modem
    settings (AT&Dx)
    05/28 01:08:48 yS6 WARNING: DSR is off - modem turned off or bad
    cable?
    05/28 01:08:48 yS6 lowering DTR to reset Modem
    05/28 01:08:54 yS6 clean_line: only 500 of 5365 bytes logged
    05/28 01:08:54 yS6 send: \dATQ0V1H0[0d]
    05/28 01:08:54 yS6 waiting for ``OK''
    05/28 01:09:48 yS6 timeout in chat script, waiting for `OK'
    05/28 01:09:48 yS6 init chat timed out, trying force-init-chat
    05/28 01:09:48 yS6 send: \d[10][03]\d\d\d+++\d\d\d[0d]\dATQ0V1H0[0d]
    05/28 01:09:52 yS6 waiting for ``OK''
    05/28 01:09:52 yS6 found action string: ``NO CARRIER''
    05/28 01:09:52 yS6 send: \dATQ0V1H0[0d]
    05/28 01:09:53 yS6 waiting for ``OK'' ** found **
    05/28 01:09:53 yS6 send: ATS0=0Q0&D0[0d]
    05/28 01:09:53 yS6 waiting for ``OK'' ** found **
    05/28 01:09:53 yS6 waiting...
    05/28 01:10:16 yS6 waiting for ``RING'' ** found **
    05/28 01:10:16 yS6 send: ATA[0d]
    05/28 01:10:16 yS6 waiting for ``CONNECT''
    05/28 01:11:19 yS6 found action string: ``NO CARRIER''
    05/28 01:11:19 ##### failed A_FAIL dev=ttyS6, pid=653, caller=none,
    conn='', name=''

    --
    05/28 01:11:19 yS6 mgetty: official release 1.0.0
    05/28 01:11:19 yS6 check for lockfiles
    05/28 01:11:19 yS6 locking the line
    05/28 01:11:20 yS6 WARNING: DSR is off - modem turned off or bad
    cable?
    05/28 01:11:20 yS6 lowering DTR to reset Modem
    05/28 01:11:20 yS6 send: \dATQ0V1H0[0d]
    05/28 01:11:21 yS6 waiting for ``OK'' ** found **
    05/28 01:11:21 yS6 send: ATS0=0Q0&D0[0d]
    05/28 01:11:21 yS6 waiting for ``OK'' ** found **
    05/28 01:11:21 yS6 waiting...
    05/28 01:11:29 ##### failed dev=ttyS6, pid=655, got signal 15, exiting

    --
    05/28 01:11:36 yS6 mgetty: official release 1.0.0
    05/28 01:11:36 yS6 check for lockfiles
    05/28 01:11:36 yS6 locking the line
    05/28 01:11:36 yS6 WARNING: DSR is off - modem turned off or bad
    cable?
    05/28 01:11:36 yS6 lowering DTR to reset Modem
    05/28 01:11:37 yS6 send: \dATQ0V1H0[0d]
    05/28 01:11:38 yS6 waiting for ``OK'' ** found **
    05/28 01:11:38 yS6 send: ATS0=0Q0&D0[0d]
    05/28 01:11:38 yS6 waiting for ``OK'' ** found **
    05/28 01:11:38 yS6 waiting...
    05/28 01:12:58 yS6 waiting for ``RING'' ** found **
    05/28 01:12:58 yS6 send: ATA[0d]
    05/28 01:12:58 yS6 waiting for ``CONNECT'' ** found **
    05/28 01:13:20 yS6 send:
    05/28 01:13:20 yS6 waiting for ``
    '' ** found **
    05/28 01:13:38 ##### data dev=ttyS6, pid=658, caller=none,
    conn='9600/REL - LAPM', name='', cmd='/usr/sbin/pppd', user='/AutoPPP/'

    --
    05/28 01:14:08 yS6 mgetty: official release 1.0.0
    05/28 01:14:08 yS6 check for lockfiles
    05/28 01:14:08 yS6 locking the line
    05/28 01:14:09 yS6 WARNING: DSR is off - modem turned off or bad
    cable?
    05/28 01:14:09 yS6 lowering DTR to reset Modem
    05/28 01:14:10 yS6 send: \dATQ0V1H0[0d]
    05/28 01:14:10 yS6 waiting for ``OK'' ** found **
    05/28 01:14:10 yS6 send: ATS0=0Q0&D0[0d]
    05/28 01:14:10 yS6 waiting for ``OK'' ** found **
    05/28 01:14:11 yS6 waiting...
    05/28 01:14:25 yS6 waiting for ``RING'' ** found **
    05/28 01:14:25 yS6 send: ATA[0d]
    05/28 01:14:25 yS6 waiting for ``CONNECT''
    05/28 01:15:28 yS6 found action string: ``NO CARRIER''
    05/28 01:15:28 ##### failed A_FAIL dev=ttyS6, pid=659, caller=none,
    conn='', name=''


  2. Re: AutoPPP fails to establish a connection during long distance calls

    "Saradhi" writes:
    > In both the cases, the problem was seen only during a long distance
    > call[isdn](Never observed in all other cases).


    The failures you're seeing all look to me like problems with the TA or
    the ISDN service itself. Your best bet is probably to look into the
    debug and event recording facilities available in the TAs you're
    using. Though I don't use ISDN these days, most ones I've seen in the
    past provided quite a bit of debug; you'll need the programmer's
    reference manual.

    A second suggestion is to try a different brand or model of TA (at one
    or both ends of the connection). It's possible that it's just a bug
    in that device.

    Next, if you're using an integrated ISDN device (with a Linux kernel
    driver), you might want to experiment with an external serial-
    attached device.

    Finally, although there are a lot of variables here, none of this
    appears to be related to PPP in any particular way. It doesn't look
    like PPP is even running. You might want to look around for a Linux
    telecom or ISDN newsgroup.

    > speed 9600


    Really?

    --
    James Carlson, KISS Network
    Sun Microsystems / 1 Network Drive 71.232W Vox +1 781 442 2084
    MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677

  3. Re: AutoPPP fails to establish a connection during long distance calls

    "Saradhi" writes:

    >Hi


    >This is Saradhi. I am using mgetty to provide a PPP (AutoPPP) solution
    >for one of our product. I am facing some weired problems when the call
    >is received.


    >The following are the problems that i have faced


    >1) timeout in chat script, waiting for `'


    The remote machine sent a carriage return. Thus mgetty then asked for and
    waited for a login. The machine on the far side is badly configured. It
    should not be sending a carriage return before starting ppp.


    >2) failed in mg_init_data, dev=3DttyS6, pid=3D640 or failed dev=3DttyS6,
    >pid=3D641, got signal 15, exiting


    NO. the problem was that mgetty was waiting for the modem to send the
    message "CONNECT" and instead it got "NO CARRIER" Ie, the modems were
    unable to establish a connection with each other. It has nothing to do with
    software, it is hardware (modem and phone lines. Probably bad phone lines
    making it impossible for the modems to connect to each other.)


    >In both the cases, the problem was seen only during a long distance
    >call[isdn](Never observed in all other cases).


    >And this is inconsistent also(some times connection do get
    >establishes).


    >I have added the logs for both these problems below.


    >I am using minimal configuration on the mgetty side. The Setup is as
    >follows


    >1) mgetty.config


    >debug 4
    >speed 9600


    >2) login.config
    >/AutoPPP/ - a_ppp /usr/sbin/pppd ttyS


    >Init chat, fource init chat and answer chat sequences are the default
    >ones provided by mgetty (release is 1.0.0).


    That is silly. those scripts are there for you to adapt for your particular
    modem. All modems are different. What works for some does not work for
    others. Read your modem manual and set up the strings to set the state of
    the modem.


    >Linux kernel version is 2.4.20


    >Am i missing some settings?


    >Thanks in advance.


    >Regards
    >Saradhi


    >=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3 D=3D=3D=3D=3D=3D=3D=3D=3D=
    >=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3 D=3D=3D=3D=3D=3D=3D=3D=3D=
    >=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
    >Problem 1:
    >=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3 D=3D=3D=3D=3D=3D=3D=3D=3D=
    >=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3 D=3D=3D=3D=3D=3D=3D=3D=3D=
    >=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
    >09/15 00:53:51 yS6 mgetty: official release 1.0.0
    >09/15 00:53:51 yS6 check for lockfiles
    >09/15 00:53:51 yS6 locking the line
    >09/15 00:53:52 yS6 lowering DTR to reset Modem
    >09/15 00:53:52 yS6 send: \dATQ0V1H0[0d]
    >09/15 00:53:53 yS6 waiting for ``OK'' ** found **
    >09/15 00:53:53 yS6 send: ATS0=3D0Q0&D0[0d]
    >09/15 00:53:53 yS6 waiting for ``OK'' ** found **
    >09/15 00:53:53 yS6 waiting...
    >09/15 10:32:17 yS6 waiting for ``RING'' ** found **
    >09/15 10:32:17 yS6 send: ATA[0d]
    >09/15 10:32:17 yS6 waiting for ``CONNECT'' ** found **
    >09/15 10:32:33 yS6 send:
    >09/15 10:32:33 yS6 waiting for ``
    >'' ** found **
    >09/15 10:32:54 yS6 getlogname: timeout


    >09/15 10:33:23 ##### failed dev=3DttyS6, pid=3D557, got signal 1, exiting


    >--
    >09/15 10:33:23 yS6 mgetty: official release 1.0.0
    >09/15 10:33:23 yS6 check for lockfiles
    >09/15 10:33:23 yS6 locking the line
    >09/15 10:33:24 yS6 lowering DTR to reset Modem
    >09/15 10:33:24 yS6 send: \dATQ0V1H0[0d]
    >09/15 10:33:25 yS6 waiting for ``OK'' ** found **
    >09/15 10:33:25 yS6 send: ATS0=3D0Q0&D0[0d]
    >09/15 10:33:25 yS6 waiting for ``OK'' ** found **
    >09/15 10:33:25 yS6 waiting...
    >09/15 10:34:48 yS6 waiting for ``RING'' ** found **
    >09/15 10:34:48 yS6 send: ATA[0d]
    >09/15 10:34:48 yS6 waiting for ``CONNECT'' ** found **
    >09/15 10:35:09 yS6 send:
    >09/15 10:35:09 yS6 waiting for ``
    >''
    >09/15 10:36:33 yS6 timeout in chat script, waiting for `
    >'
    >09/15 10:36:33 ##### failed timeout dev=3DttyS6, pid=3D646, caller=3Dnone,
    >conn=3D'21600/ARQ', name=3D''


    >--
    >09/15 10:36:33 yS6 mgetty: official release 1.0.0
    >09/15 10:36:33 yS6 check for lockfiles
    >09/15 10:36:33 yS6 locking the line
    >09/15 10:36:34 yS6 lowering DTR to reset Modem
    >09/15 10:36:34 yS6 send: \dATQ0V1H0[0d]
    >09/15 10:36:35 yS6 waiting for ``OK'' ** found **
    >09/15 10:36:35 yS6 send: ATS0=3D0Q0&D0[0d]
    >09/15 10:36:35 yS6 waiting for ``OK'' ** found **
    >09/15 10:36:36 yS6 waiting...
    >09/15 10:36:56 yS6 waiting for ``RING'' ** found **
    >09/15 10:36:56 yS6 send: ATA[0d]
    >09/15 10:36:56 yS6 waiting for ``CONNECT'' ** found **
    >09/15 10:37:15 yS6 send:
    >09/15 10:37:15 yS6 waiting for ``
    >''
    >09/15 19:23:18 yS6 timeout in chat script, waiting for `
    >'
    >09/15 19:23:18 ##### failed timeout dev=3DttyS6, pid=3D647, caller=3Dnone,
    >conn=3D'16800/ARQ', name=3D''


    >--
    >09/15 19:23:18 yS6 mgetty: official release 1.0.0
    >09/15 19:23:18 yS6 check for lockfiles
    >09/15 19:23:18 yS6 locking the line
    >09/15 19:23:18 yS6 WARNING: DCD line still active, check modem
    >settings (AT&Dx)
    >09/15 19:23:18 yS6 lowering DTR to reset Modem
    >09/15 19:23:19 yS6 send: \dATQ0V1H0[0d]
    >09/15 19:23:20 yS6 waiting for ``OK''
    >09/15 19:24:17 ##### failed dev=3DttyS6, pid=3D648, got signal 15, exiting


    >--
    >09/15 19:24:26 yS6 mgetty: official release 1.0.0
    >09/15 19:24:26 yS6 check for lockfiles
    >09/15 19:24:26 yS6 locking the line
    >09/15 19:24:27 yS6 lowering DTR to reset Modem
    >09/15 19:24:27 yS6 send: \dATQ0V1H0[0d]
    >09/15 19:24:28 yS6 waiting for ``OK'' ** found **
    >09/15 19:24:28 yS6 send: ATS0=3D0Q0&D0[0d]
    >09/15 19:24:28 yS6 waiting for ``OK'' ** found **
    >09/15 19:24:29 yS6 waiting...
    >09/15 20:24:29 yS6 checking if modem is still alive
    >09/15 20:24:29 yS6 mdm_send: 'AT' -> OK
    >09/15 20:24:29 yS6 waiting...
    >09/15 20:47:46 yS6 waiting for ``RING'' ** found **
    >09/15 20:47:47 yS6 send: ATA[0d]
    >09/15 20:47:47 yS6 waiting for ``CONNECT'' ** found **
    >09/15 20:48:02 yS6 send:
    >09/15 20:48:02 yS6 waiting for ``
    >''


    >=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3 D=3D=3D=3D=3D=3D=3D=3D=3D=
    >=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3 D=3D=3D=3D=3D=3D=3D=3D=3D=
    >=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
    >PROBLEM 2:
    >=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3 D=3D=3D=3D=3D=3D=3D=3D=3D=
    >=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3 D=3D=3D=3D=3D=3D=3D=3D=3D=
    >=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
    >05/27 23:18:26 yS6 mgetty: official release 1.0.0
    >05/27 23:18:26 yS6 check for lockfiles
    >05/27 23:18:26 yS6 locking the line
    >05/27 23:18:27 yS6 WARNING: DSR is off - modem turned off or bad
    >cable?
    >05/27 23:18:27 yS6 lowering DTR to reset Modem
    >05/27 23:18:27 yS6 send: \dATQ0V1H0[0d]
    >05/27 23:18:28 yS6 waiting for ``OK'' ** found **
    >05/27 23:18:28 yS6 send: ATS0=3D0Q0&D0[0d]
    >05/27 23:18:28 yS6 waiting for ``OK'' ** found **
    >05/27 23:18:28 yS6 waiting...
    >05/27 23:24:58 yS6 waiting for ``RING'' ** found **
    >05/27 23:24:58 yS6 send: ATA[0d]
    >05/27 23:24:58 yS6 waiting for ``CONNECT''
    >05/27 23:26:02 yS6 found action string: ``NO CARRIER''
    >05/27 23:26:02 ##### failed A_FAIL dev=3DttyS6, pid=3D528, caller=3Dnone,
    >conn=3D'', name=3D''


    >--
    >05/27 23:26:02 yS6 mgetty: official release 1.0.0
    >05/27 23:26:02 yS6 check for lockfiles
    >05/27 23:26:02 yS6 locking the line
    >05/27 23:26:02 yS6 WARNING: DSR is off - modem turned off or bad
    >cable?
    >05/27 23:26:02 yS6 lowering DTR to reset Modem
    >05/27 23:26:03 yS6 send: \dATQ0V1H0[0d]
    >05/27 23:26:04 yS6 waiting for ``OK'' ** found **
    >05/27 23:26:04 yS6 send: ATS0=3D0Q0&D0[0d]
    >05/27 23:26:04 yS6 waiting for ``OK'' ** found **
    >05/27 23:26:04 yS6 waiting...
    >05/27 23:26:18 yS6 waiting for ``RING'' ** found **
    >05/27 23:26:18 yS6 send: ATA[0d]
    >05/27 23:26:18 yS6 waiting for ``CONNECT''
    >05/27 23:27:21 yS6 found action string: ``NO CARRIER''
    >05/27 23:27:21 ##### failed A_FAIL dev=3DttyS6, pid=3D631, caller=3Dnone,
    >conn=3D'', name=3D''


    >--
    >05/27 23:27:21 yS6 mgetty: official release 1.0.0
    >05/27 23:27:21 yS6 check for lockfiles
    >05/27 23:27:21 yS6 locking the line
    >05/27 23:27:21 yS6 WARNING: DSR is off - modem turned off or bad
    >cable?
    >05/27 23:27:21 yS6 lowering DTR to reset Modem
    >05/27 23:27:22 yS6 send: \dATQ0V1H0[0d]
    >05/27 23:27:23 yS6 waiting for ``OK'' ** found **
    >05/27 23:27:23 yS6 send: ATS0=3D0Q0&D0[0d]
    >05/27 23:27:23 yS6 waiting for ``OK'' ** found **
    >05/27 23:27:23 yS6 waiting...
    >05/27 23:28:58 yS6 waiting for ``RING'' ** found **
    >05/27 23:28:58 yS6 send: ATA[0d]
    >05/27 23:28:58 yS6 waiting for ``CONNECT''
    >05/27 23:30:01 yS6 found action string: ``NO CARRIER''
    >05/27 23:30:01 ##### failed A_FAIL dev=3DttyS6, pid=3D632, caller=3Dnone,
    >conn=3D'', name=3D''


    >--
    >05/27 23:30:01 yS6 mgetty: official release 1.0.0
    >05/27 23:30:01 yS6 check for lockfiles
    >05/27 23:30:01 yS6 locking the line
    >05/27 23:30:01 yS6 WARNING: DSR is off - modem turned off or bad
    >cable?
    >05/27 23:30:01 yS6 lowering DTR to reset Modem
    >05/27 23:30:02 yS6 send: \dATQ0V1H0[0d]
    >05/27 23:30:03 yS6 waiting for ``OK'' ** found **
    >05/27 23:30:03 yS6 send: ATS0=3D0Q0&D0[0d]
    >05/27 23:30:03 yS6 waiting for ``OK'' ** found **
    >05/27 23:30:03 yS6 waiting...
    >05/27 23:30:37 yS6 waiting for ``RING'' ** found **
    >05/27 23:30:37 yS6 send: ATA[0d]
    >05/27 23:30:37 yS6 waiting for ``CONNECT''
    >05/27 23:31:41 yS6 found action string: ``NO CARRIER''
    >05/27 23:31:41 ##### failed A_FAIL dev=3DttyS6, pid=3D633, caller=3Dnone,
    >conn=3D'', name=3D''


    >--
    >05/27 23:31:41 yS6 mgetty: official release 1.0.0
    >05/27 23:31:41 yS6 check for lockfiles
    >05/27 23:31:41 yS6 locking the line
    >05/27 23:31:41 yS6 WARNING: DSR is off - modem turned off or bad
    >cable?
    >05/27 23:31:41 yS6 lowering DTR to reset Modem
    >05/27 23:31:42 yS6 send: \dATQ0V1H0[0d]
    >05/27 23:31:43 yS6 waiting for ``OK'' ** found **
    >05/27 23:31:43 yS6 send: ATS0=3D0Q0&D0[0d]
    >05/27 23:31:43 yS6 waiting for ``OK'' ** found **
    >05/27 23:31:43 yS6 waiting...
    >05/27 23:36:25 yS6 waiting for ``RING'' ** found **
    >05/27 23:36:25 yS6 send: ATA[0d]
    >05/27 23:36:25 yS6 waiting for ``CONNECT''
    >05/27 23:37:29 yS6 found action string: ``NO CARRIER''
    >05/27 23:37:29 ##### failed A_FAIL dev=3DttyS6, pid=3D636, caller=3Dnone,
    >conn=3D'', name=3D''


    >--
    >05/27 23:37:29 yS6 mgetty: official release 1.0.0
    >05/27 23:37:29 yS6 check for lockfiles
    >05/27 23:37:29 yS6 locking the line
    >05/27 23:37:29 yS6 WARNING: DSR is off - modem turned off or bad
    >cable?
    >05/27 23:37:29 yS6 lowering DTR to reset Modem
    >05/27 23:37:30 yS6 send: \dATQ0V1H0[0d]
    >05/27 23:37:31 yS6 waiting for ``OK'' ** found **
    >05/27 23:37:31 yS6 send: ATS0=3D0Q0&D0[0d]
    >05/27 23:37:31 yS6 waiting for ``OK'' ** found **
    >05/27 23:37:31 yS6 waiting...
    >05/27 23:39:28 yS6 waiting for ``RING'' ** found **
    >05/27 23:39:28 yS6 send: ATA[0d]
    >05/27 23:39:28 yS6 waiting for ``CONNECT'' ** found **
    >05/27 23:39:48 yS6 send:
    >05/27 23:39:48 yS6 waiting for ``
    >'' ** found **
    >05/27 23:39:50 ##### data dev=3DttyS6, pid=3D639, caller=3Dnone,
    >conn=3D'9600/REL - LAPM', name=3D'', cmd=3D'/usr/sbin/pppd', user=3D'/AutoP=
    >PP/'


    >--
    >05/27 23:40:20 yS6 mgetty: official release 1.0.0
    >05/27 23:40:20 yS6 check for lockfiles
    >05/27 23:40:20 yS6 locking the line
    >05/27 23:40:21 yS6 WARNING: DCD line still active, check modem
    >settings (AT&Dx)
    >05/27 23:40:21 yS6 WARNING: DSR is off - modem turned off or bad
    >cable?
    >05/27 23:40:21 yS6 lowering DTR to reset Modem
    >05/27 23:40:22 yS6 send: \dATQ0V1H0[0d]
    >05/27 23:40:22 yS6 waiting for ``OK''
    >05/27 23:40:25 yS6 found action string: ``NO CARRIER''
    >05/27 23:40:25 yS6 init chat failed, exiting...: Invalid argument
    >05/27 23:40:25 ##### failed in mg_init_data, dev=3DttyS6, pid=3D640


    >--
    >05/27 23:40:25 yS6 mgetty: official release 1.0.0
    >05/27 23:40:25 yS6 check for lockfiles
    >05/27 23:40:25 yS6 locking the line
    >05/27 23:40:26 yS6 WARNING: DSR is off - modem turned off or bad
    >cable?
    >05/27 23:40:26 yS6 lowering DTR to reset Modem
    >05/27 23:40:27 yS6 send: \dATQ0V1H0[0d]
    >05/27 23:40:27 yS6 waiting for ``OK'' ** found **
    >05/27 23:40:27 yS6 send: ATS0=3D0Q0&D0[0d]
    >05/27 23:40:27 yS6 waiting for ``OK'' ** found **
    >05/27 23:40:28 yS6 waiting...
    >05/28 00:01:36 ##### failed dev=3DttyS6, pid=3D641, got signal 15, exiting


    >--
    >05/28 01:04:20 yS6 mgetty: official release 1.0.0
    >05/28 01:04:20 yS6 check for lockfiles
    >05/28 01:04:20 yS6 locking the line
    >05/28 01:04:21 yS6 WARNING: DSR is off - modem turned off or bad
    >cable?
    >05/28 01:04:21 yS6 lowering DTR to reset Modem
    >05/28 01:04:21 yS6 send: \dATQ0V1H0[0d]
    >05/28 01:04:22 yS6 waiting for ``OK'' ** found **
    >05/28 01:04:22 yS6 send: ATS0=3D0Q0&D0[0d]
    >05/28 01:04:22 yS6 waiting for ``OK'' ** found **
    >05/28 01:04:22 yS6 waiting...
    >05/28 01:04:34 yS6 waiting for ``RING'' ** found **
    >05/28 01:04:34 yS6 send: ATA[0d]
    >05/28 01:04:34 yS6 waiting for ``CONNECT'' ** found **
    >05/28 01:05:05 yS6 send:
    >05/28 01:05:05 yS6 waiting for ``
    >'' ** found **
    >05/28 01:05:09 yS6 clean_line: only 500 of 2780 bytes logged
    >05/28 01:05:29 yS6 getlogname: timeout


    >05/28 01:05:51 ##### failed dev=3DttyS6, pid=3D651, got signal 1, exiting


    >--
    >05/28 01:05:51 yS6 mgetty: official release 1.0.0
    >05/28 01:05:51 yS6 check for lockfiles
    >05/28 01:05:51 yS6 locking the line
    >05/28 01:05:51 yS6 WARNING: DSR is off - modem turned off or bad
    >cable?
    >05/28 01:05:51 yS6 lowering DTR to reset Modem
    >05/28 01:05:52 yS6 send: \dATQ0V1H0[0d]
    >05/28 01:05:52 yS6 waiting for ``OK'' ** found **
    >05/28 01:05:52 yS6 send: ATS0=3D0Q0&D0[0d]
    >05/28 01:05:52 yS6 waiting for ``OK'' ** found **
    >05/28 01:05:53 yS6 waiting...
    >05/28 01:07:46 yS6 waiting for ``RING'' ** found **
    >05/28 01:07:46 yS6 send: ATA[0d]
    >05/28 01:07:46 yS6 waiting for ``CONNECT'' ** found **
    >05/28 01:08:16 yS6 send:
    >05/28 01:08:16 yS6 waiting for ``
    >'' ** found **
    >05/28 01:08:22 yS6 clean_line: only 500 of 5922 bytes logged
    >05/28 01:08:43 yS6 getlogname: timeout


    >05/28 01:08:47 yS6 login name all uppercase, set IUCLC OLCUC
    >05/28 01:08:47 ##### data dev=3DttyS6, pid=3D652, caller=3Dnone, conn=3D'96=
    >00',
    >name=3D'', cmd=3D'/bin/login', user=3D'` l'


    >--
    >05/28 01:08:47 yS6 mgetty: official release 1.0.0
    >05/28 01:08:47 yS6 check for lockfiles
    >05/28 01:08:47 yS6 locking the line
    >05/28 01:08:48 yS6 WARNING: DCD line still active, check modem
    >settings (AT&Dx)
    >05/28 01:08:48 yS6 WARNING: DSR is off - modem turned off or bad
    >cable?
    >05/28 01:08:48 yS6 lowering DTR to reset Modem
    >05/28 01:08:54 yS6 clean_line: only 500 of 5365 bytes logged
    >05/28 01:08:54 yS6 send: \dATQ0V1H0[0d]
    >05/28 01:08:54 yS6 waiting for ``OK''
    >05/28 01:09:48 yS6 timeout in chat script, waiting for `OK'
    >05/28 01:09:48 yS6 init chat timed out, trying force-init-chat
    >05/28 01:09:48 yS6 send: \d[10][03]\d\d\d+++\d\d\d[0d]\dATQ0V1H0[0d]
    >05/28 01:09:52 yS6 waiting for ``OK''
    >05/28 01:09:52 yS6 found action string: ``NO CARRIER''
    >05/28 01:09:52 yS6 send: \dATQ0V1H0[0d]
    >05/28 01:09:53 yS6 waiting for ``OK'' ** found **
    >05/28 01:09:53 yS6 send: ATS0=3D0Q0&D0[0d]
    >05/28 01:09:53 yS6 waiting for ``OK'' ** found **
    >05/28 01:09:53 yS6 waiting...
    >05/28 01:10:16 yS6 waiting for ``RING'' ** found **
    >05/28 01:10:16 yS6 send: ATA[0d]
    >05/28 01:10:16 yS6 waiting for ``CONNECT''
    >05/28 01:11:19 yS6 found action string: ``NO CARRIER''
    >05/28 01:11:19 ##### failed A_FAIL dev=3DttyS6, pid=3D653, caller=3Dnone,
    >conn=3D'', name=3D''


    >--
    >05/28 01:11:19 yS6 mgetty: official release 1.0.0
    >05/28 01:11:19 yS6 check for lockfiles
    >05/28 01:11:19 yS6 locking the line
    >05/28 01:11:20 yS6 WARNING: DSR is off - modem turned off or bad
    >cable?
    >05/28 01:11:20 yS6 lowering DTR to reset Modem
    >05/28 01:11:20 yS6 send: \dATQ0V1H0[0d]
    >05/28 01:11:21 yS6 waiting for ``OK'' ** found **
    >05/28 01:11:21 yS6 send: ATS0=3D0Q0&D0[0d]
    >05/28 01:11:21 yS6 waiting for ``OK'' ** found **
    >05/28 01:11:21 yS6 waiting...
    >05/28 01:11:29 ##### failed dev=3DttyS6, pid=3D655, got signal 15, exiting


    >--
    >05/28 01:11:36 yS6 mgetty: official release 1.0.0
    >05/28 01:11:36 yS6 check for lockfiles
    >05/28 01:11:36 yS6 locking the line
    >05/28 01:11:36 yS6 WARNING: DSR is off - modem turned off or bad
    >cable?
    >05/28 01:11:36 yS6 lowering DTR to reset Modem
    >05/28 01:11:37 yS6 send: \dATQ0V1H0[0d]
    >05/28 01:11:38 yS6 waiting for ``OK'' ** found **
    >05/28 01:11:38 yS6 send: ATS0=3D0Q0&D0[0d]
    >05/28 01:11:38 yS6 waiting for ``OK'' ** found **
    >05/28 01:11:38 yS6 waiting...
    >05/28 01:12:58 yS6 waiting for ``RING'' ** found **
    >05/28 01:12:58 yS6 send: ATA[0d]
    >05/28 01:12:58 yS6 waiting for ``CONNECT'' ** found **
    >05/28 01:13:20 yS6 send:
    >05/28 01:13:20 yS6 waiting for ``
    >'' ** found **
    >05/28 01:13:38 ##### data dev=3DttyS6, pid=3D658, caller=3Dnone,
    >conn=3D'9600/REL - LAPM', name=3D'', cmd=3D'/usr/sbin/pppd', user=3D'/AutoP=
    >PP/'


    >--
    >05/28 01:14:08 yS6 mgetty: official release 1.0.0
    >05/28 01:14:08 yS6 check for lockfiles
    >05/28 01:14:08 yS6 locking the line
    >05/28 01:14:09 yS6 WARNING: DSR is off - modem turned off or bad
    >cable?
    >05/28 01:14:09 yS6 lowering DTR to reset Modem
    >05/28 01:14:10 yS6 send: \dATQ0V1H0[0d]
    >05/28 01:14:10 yS6 waiting for ``OK'' ** found **
    >05/28 01:14:10 yS6 send: ATS0=3D0Q0&D0[0d]
    >05/28 01:14:10 yS6 waiting for ``OK'' ** found **
    >05/28 01:14:11 yS6 waiting...
    >05/28 01:14:25 yS6 waiting for ``RING'' ** found **
    >05/28 01:14:25 yS6 send: ATA[0d]
    >05/28 01:14:25 yS6 waiting for ``CONNECT''
    >05/28 01:15:28 yS6 found action string: ``NO CARRIER''
    >05/28 01:15:28 ##### failed A_FAIL dev=3DttyS6, pid=3D659, caller=3Dnone,
    >conn=3D'', name=3D''



  4. Re: AutoPPP fails to establish a connection during long distance calls

    Saradhi wrote:

    Up front: I've only used mgetty on a regular landline for defending
    against telemarketers and for login, not PPP. It's now been years since
    I've used it (unused since my NO-CALL listings became active .

    > Hi


    > This is Saradhi. I am using mgetty to provide a PPP (AutoPPP) solution
    > for one of our product. I am facing some weired problems when the call
    > is received.


    > The following are the problems that i have faced


    > 1) timeout in chat script, waiting for `'
    > 2) failed in mg_init_data, dev=ttyS6, pid=640 or failed dev=ttyS6,
    > pid=641, got signal 15, exiting


    > In both the cases, the problem was seen only during a long distance
    > call[isdn](Never observed in all other cases).


    > And this is inconsistent also(some times connection do get
    > establishes).


    > I have added the logs for both these problems below.


    > I am using minimal configuration on the mgetty side. The Setup is as
    > follows


    > 1) mgetty.config


    > debug 4
    > speed 9600


    > 2) login.config
    > /AutoPPP/ - a_ppp /usr/sbin/pppd ttyS


    > Init chat, fource init chat and answer chat sequences are the default
    > ones provided by mgetty (release is 1.0.0).


    That's an awfully old release. The one I used years ago was 1.1.21.

    > Linux kernel version is 2.4.20


    > Am i missing some settings?


    > Thanks in advance.


    > Regards
    > Saradhi


    > ================================================== ============
    > Problem 1:
    > ================================================== ============
    > 09/15 00:53:51 yS6 mgetty: official release 1.0.0
    > 09/15 00:53:51 yS6 check for lockfiles
    > 09/15 00:53:51 yS6 locking the line
    > 09/15 00:53:52 yS6 lowering DTR to reset Modem
    > 09/15 00:53:52 yS6 send: \dATQ0V1H0[0d]
    > 09/15 00:53:53 yS6 waiting for ``OK'' ** found **
    > 09/15 00:53:53 yS6 send: ATS0=0Q0&D0[0d]
    > 09/15 00:53:53 yS6 waiting for ``OK'' ** found **
    > 09/15 00:53:53 yS6 waiting...
    > 09/15 10:32:17 yS6 waiting for ``RING'' ** found **
    > 09/15 10:32:17 yS6 send: ATA[0d]
    > 09/15 10:32:17 yS6 waiting for ``CONNECT'' ** found **
    > 09/15 10:32:33 yS6 send:
    > 09/15 10:32:33 yS6 waiting for ``
    > '' ** found **


    You are waiting for a carriage-return and the other side sent one.
    You shouldn't be waiting for one. I suspect you use

    CONNECT \c \r

    which is *wrongly* used in many "info mgetty" examples. If so then
    get rid of the \r. It apparently means the same thing to mgetty chat
    as it does to pppd chat (and to bash), namely a carriage-return.
    Also from "info mgetty" here:

    This is the command sequence that is used to answer a phone call.
    Usually you can leave it at the default ` "" ATA CONNECT \c \r ',
    but for some modems you need `ATS0=1' in place of `ATA' (ATA not
    allowed). The extra `\r' expect string is needed that the code can
    grab the full CONNECT XYZ\R string. It will work without the \r,
    but then the logging information will be less detailed. *Right now,
    \r won't work at all, it's not implemented yet. Don't use it.*

    Note: Info mgetty gives examples with \c but "info mgetty" never
    says what it means to it's internal chat. To the pppd chat it means
    "send nothing" and I used it with mgetty as meaning the same thing
    with no problem. The "send:" line above provides evidence that the
    meaning is same for chat and mgetty.

    > 09/15 10:32:54 yS6 getlogname: timeout


    As Bill Unruh observed, a carriage-return was received from the other
    side and found by mgetty, causing mgetty to expect a login, not PPP.

    > 09/15 10:33:23 ##### failed dev=ttyS6, pid=557, got signal 1, exiting


    > --
    > 09/15 10:33:23 yS6 mgetty: official release 1.0.0
    > 09/15 10:33:23 yS6 check for lockfiles
    > 09/15 10:33:23 yS6 locking the line
    > 09/15 10:33:24 yS6 lowering DTR to reset Modem
    > 09/15 10:33:24 yS6 send: \dATQ0V1H0[0d]
    > 09/15 10:33:25 yS6 waiting for ``OK'' ** found **
    > 09/15 10:33:25 yS6 send: ATS0=0Q0&D0[0d]
    > 09/15 10:33:25 yS6 waiting for ``OK'' ** found **
    > 09/15 10:33:25 yS6 waiting...
    > 09/15 10:34:48 yS6 waiting for ``RING'' ** found **
    > 09/15 10:34:48 yS6 send: ATA[0d]
    > 09/15 10:34:48 yS6 waiting for ``CONNECT'' ** found **
    > 09/15 10:35:09 yS6 send:
    > 09/15 10:35:09 yS6 waiting for ``
    > ''
    > 09/15 10:36:33 yS6 timeout in chat script, waiting for `
    > '
    > 09/15 10:36:33 ##### failed timeout dev=ttyS6, pid=646, caller=none,
    > conn='21600/ARQ', name=''


    Here the other side doesn't send a carriage-return (which is the correct
    thing to do - again, as Bill Unruh observed) and chat times out waiting
    for one to arrive.

    > --
    > 09/15 10:36:33 yS6 mgetty: official release 1.0.0
    > 09/15 10:36:33 yS6 check for lockfiles
    > 09/15 10:36:33 yS6 locking the line
    > 09/15 10:36:34 yS6 lowering DTR to reset Modem
    > 09/15 10:36:34 yS6 send: \dATQ0V1H0[0d]
    > 09/15 10:36:35 yS6 waiting for ``OK'' ** found **
    > 09/15 10:36:35 yS6 send: ATS0=0Q0&D0[0d]
    > 09/15 10:36:35 yS6 waiting for ``OK'' ** found **
    > 09/15 10:36:36 yS6 waiting...
    > 09/15 10:36:56 yS6 waiting for ``RING'' ** found **
    > 09/15 10:36:56 yS6 send: ATA[0d]
    > 09/15 10:36:56 yS6 waiting for ``CONNECT'' ** found **
    > 09/15 10:37:15 yS6 send:
    > 09/15 10:37:15 yS6 waiting for ``
    > ''
    > 09/15 19:23:18 yS6 timeout in chat script, waiting for `
    > '
    > 09/15 19:23:18 ##### failed timeout dev=ttyS6, pid=647, caller=none,
    > conn='16800/ARQ', name=''


    Here chat again times out waiting for a carriage-return. What _is_
    strange is the 8 hour 46 minute 3 second delay between the beginning
    of the wait and the timeout.

    > --
    > 09/15 19:23:18 yS6 mgetty: official release 1.0.0
    > 09/15 19:23:18 yS6 check for lockfiles
    > 09/15 19:23:18 yS6 locking the line
    > 09/15 19:23:18 yS6 WARNING: DCD line still active, check modem
    > settings (AT&Dx)
    > 09/15 19:23:18 yS6 lowering DTR to reset Modem
    > 09/15 19:23:19 yS6 send: \dATQ0V1H0[0d]
    > 09/15 19:23:20 yS6 waiting for ``OK''
    > 09/15 19:24:17 ##### failed dev=ttyS6, pid=648, got signal 15, exiting


    The DCD (carrier detect) line was not reset and mgetty exits after
    waiting 57 seconds for an OK from the modem. This suggests the
    modem might still have been connected when mgetty resumes above.
    Mgetty restarts from scratch below without a problem.

    > --
    > 09/15 19:24:26 yS6 mgetty: official release 1.0.0
    > 09/15 19:24:26 yS6 check for lockfiles
    > 09/15 19:24:26 yS6 locking the line
    > 09/15 19:24:27 yS6 lowering DTR to reset Modem
    > 09/15 19:24:27 yS6 send: \dATQ0V1H0[0d]
    > 09/15 19:24:28 yS6 waiting for ``OK'' ** found **
    > 09/15 19:24:28 yS6 send: ATS0=0Q0&D0[0d]
    > 09/15 19:24:28 yS6 waiting for ``OK'' ** found **
    > 09/15 19:24:29 yS6 waiting...
    > 09/15 20:24:29 yS6 checking if modem is still alive
    > 09/15 20:24:29 yS6 mdm_send: 'AT' -> OK
    > 09/15 20:24:29 yS6 waiting...
    > 09/15 20:47:46 yS6 waiting for ``RING'' ** found **
    > 09/15 20:47:47 yS6 send: ATA[0d]
    > 09/15 20:47:47 yS6 waiting for ``CONNECT'' ** found **
    > 09/15 20:48:02 yS6 send:
    > 09/15 20:48:02 yS6 waiting for ``
    > ''


    > ================================================== ============
    > PROBLEM 2:
    > ================================================== ============
    > 05/27 23:18:26 yS6 mgetty: official release 1.0.0
    > 05/27 23:18:26 yS6 check for lockfiles
    > 05/27 23:18:26 yS6 locking the line
    > 05/27 23:18:27 yS6 WARNING: DSR is off - modem turned off or bad
    > cable?


    The modem most likely got buggered somehow and needs a hard reset.

    > 05/27 23:18:27 yS6 lowering DTR to reset Modem
    > 05/27 23:18:27 yS6 send: \dATQ0V1H0[0d]
    > 05/27 23:18:28 yS6 waiting for ``OK'' ** found **
    > 05/27 23:18:28 yS6 send: ATS0=0Q0&D0[0d]
    > 05/27 23:18:28 yS6 waiting for ``OK'' ** found **
    > 05/27 23:18:28 yS6 waiting...
    > 05/27 23:24:58 yS6 waiting for ``RING'' ** found **
    > 05/27 23:24:58 yS6 send: ATA[0d]
    > 05/27 23:24:58 yS6 waiting for ``CONNECT''
    > 05/27 23:26:02 yS6 found action string: ``NO CARRIER''
    > 05/27 23:26:02 ##### failed A_FAIL dev=ttyS6, pid=528, caller=none,
    > conn='', name=''


    The "NO CARRIER" may have been left over in a serial port buffer from
    a previous connection that was not cleanly terminated.

    > --
    > 05/27 23:26:02 yS6 mgetty: official release 1.0.0
    > 05/27 23:26:02 yS6 check for lockfiles
    > 05/27 23:26:02 yS6 locking the line
    > 05/27 23:26:02 yS6 WARNING: DSR is off - modem turned off or bad
    > cable?
    > 05/27 23:26:02 yS6 lowering DTR to reset Modem
    > 05/27 23:26:03 yS6 send: \dATQ0V1H0[0d]
    > 05/27 23:26:04 yS6 waiting for ``OK'' ** found **
    > 05/27 23:26:04 yS6 send: ATS0=0Q0&D0[0d]
    > 05/27 23:26:04 yS6 waiting for ``OK'' ** found **
    > 05/27 23:26:04 yS6 waiting...
    > 05/27 23:26:18 yS6 waiting for ``RING'' ** found **
    > 05/27 23:26:18 yS6 send: ATA[0d]
    > 05/27 23:26:18 yS6 waiting for ``CONNECT''
    > 05/27 23:27:21 yS6 found action string: ``NO CARRIER''
    > 05/27 23:27:21 ##### failed A_FAIL dev=ttyS6, pid=631, caller=none,
    > conn='', name=''


    > --
    > 05/27 23:27:21 yS6 mgetty: official release 1.0.0
    > 05/27 23:27:21 yS6 check for lockfiles
    > 05/27 23:27:21 yS6 locking the line
    > 05/27 23:27:21 yS6 WARNING: DSR is off - modem turned off or bad
    > cable?
    > 05/27 23:27:21 yS6 lowering DTR to reset Modem
    > 05/27 23:27:22 yS6 send: \dATQ0V1H0[0d]
    > 05/27 23:27:23 yS6 waiting for ``OK'' ** found **
    > 05/27 23:27:23 yS6 send: ATS0=0Q0&D0[0d]
    > 05/27 23:27:23 yS6 waiting for ``OK'' ** found **
    > 05/27 23:27:23 yS6 waiting...
    > 05/27 23:28:58 yS6 waiting for ``RING'' ** found **
    > 05/27 23:28:58 yS6 send: ATA[0d]
    > 05/27 23:28:58 yS6 waiting for ``CONNECT''
    > 05/27 23:30:01 yS6 found action string: ``NO CARRIER''
    > 05/27 23:30:01 ##### failed A_FAIL dev=ttyS6, pid=632, caller=none,
    > conn='', name=''


    > --
    > 05/27 23:30:01 yS6 mgetty: official release 1.0.0
    > 05/27 23:30:01 yS6 check for lockfiles
    > 05/27 23:30:01 yS6 locking the line
    > 05/27 23:30:01 yS6 WARNING: DSR is off - modem turned off or bad
    > cable?
    > 05/27 23:30:01 yS6 lowering DTR to reset Modem
    > 05/27 23:30:02 yS6 send: \dATQ0V1H0[0d]
    > 05/27 23:30:03 yS6 waiting for ``OK'' ** found **
    > 05/27 23:30:03 yS6 send: ATS0=0Q0&D0[0d]
    > 05/27 23:30:03 yS6 waiting for ``OK'' ** found **
    > 05/27 23:30:03 yS6 waiting...
    > 05/27 23:30:37 yS6 waiting for ``RING'' ** found **
    > 05/27 23:30:37 yS6 send: ATA[0d]
    > 05/27 23:30:37 yS6 waiting for ``CONNECT''
    > 05/27 23:31:41 yS6 found action string: ``NO CARRIER''
    > 05/27 23:31:41 ##### failed A_FAIL dev=ttyS6, pid=633, caller=none,
    > conn='', name=''


    > --
    > 05/27 23:31:41 yS6 mgetty: official release 1.0.0
    > 05/27 23:31:41 yS6 check for lockfiles
    > 05/27 23:31:41 yS6 locking the line
    > 05/27 23:31:41 yS6 WARNING: DSR is off - modem turned off or bad
    > cable?
    > 05/27 23:31:41 yS6 lowering DTR to reset Modem
    > 05/27 23:31:42 yS6 send: \dATQ0V1H0[0d]
    > 05/27 23:31:43 yS6 waiting for ``OK'' ** found **
    > 05/27 23:31:43 yS6 send: ATS0=0Q0&D0[0d]
    > 05/27 23:31:43 yS6 waiting for ``OK'' ** found **
    > 05/27 23:31:43 yS6 waiting...
    > 05/27 23:36:25 yS6 waiting for ``RING'' ** found **
    > 05/27 23:36:25 yS6 send: ATA[0d]
    > 05/27 23:36:25 yS6 waiting for ``CONNECT''
    > 05/27 23:37:29 yS6 found action string: ``NO CARRIER''
    > 05/27 23:37:29 ##### failed A_FAIL dev=ttyS6, pid=636, caller=none,
    > conn='', name=''


    > --
    > 05/27 23:37:29 yS6 mgetty: official release 1.0.0
    > 05/27 23:37:29 yS6 check for lockfiles
    > 05/27 23:37:29 yS6 locking the line
    > 05/27 23:37:29 yS6 WARNING: DSR is off - modem turned off or bad
    > cable?
    > 05/27 23:37:29 yS6 lowering DTR to reset Modem
    > 05/27 23:37:30 yS6 send: \dATQ0V1H0[0d]
    > 05/27 23:37:31 yS6 waiting for ``OK'' ** found **
    > 05/27 23:37:31 yS6 send: ATS0=0Q0&D0[0d]
    > 05/27 23:37:31 yS6 waiting for ``OK'' ** found **
    > 05/27 23:37:31 yS6 waiting...
    > 05/27 23:39:28 yS6 waiting for ``RING'' ** found **
    > 05/27 23:39:28 yS6 send: ATA[0d]
    > 05/27 23:39:28 yS6 waiting for ``CONNECT'' ** found **
    > 05/27 23:39:48 yS6 send:
    > 05/27 23:39:48 yS6 waiting for ``
    > '' ** found **
    > 05/27 23:39:50 ##### data dev=ttyS6, pid=639, caller=none,
    > conn='9600/REL - LAPM', name='', cmd='/usr/sbin/pppd', user='/AutoPPP/'


    Note that "waiting for ``CONNECT'' ** found **" (as opposed to just
    "waiting for ``CONNECT''") appears less than 1 second after "send :
    ATA[0d]" and my guess is that in doing so it preempts "NO CARRIER"
    detection.

    Note also that the carriage-return arrived less than 1 second after
    the "send:" so there wasn't any timeout. The small time difference
    between the two events may also have caused mgetty to ignore or miss
    the carriage-return enabling mgetty to use AutoPPP - but that's just
    wild speculation on my part.

    > --
    > 05/27 23:40:20 yS6 mgetty: official release 1.0.0
    > 05/27 23:40:20 yS6 check for lockfiles
    > 05/27 23:40:20 yS6 locking the line
    > 05/27 23:40:21 yS6 WARNING: DCD line still active, check modem
    > settings (AT&Dx)
    > 05/27 23:40:21 yS6 WARNING: DSR is off - modem turned off or bad
    > cable?
    > 05/27 23:40:21 yS6 lowering DTR to reset Modem
    > 05/27 23:40:22 yS6 send: \dATQ0V1H0[0d]
    > 05/27 23:40:22 yS6 waiting for ``OK''
    > 05/27 23:40:25 yS6 found action string: ``NO CARRIER''
    > 05/27 23:40:25 yS6 init chat failed, exiting...: Invalid argument
    > 05/27 23:40:25 ##### failed in mg_init_data, dev=ttyS6, pid=640


    Modem initialization appears to be invalid when DCD is active and DSR
    is off. DCD is likely active because the previous modem connection is
    still up. Action on detection of "NO CARRIER" appears to be preempted.

    > --
    > 05/27 23:40:25 yS6 mgetty: official release 1.0.0
    > 05/27 23:40:25 yS6 check for lockfiles
    > 05/27 23:40:25 yS6 locking the line
    > 05/27 23:40:26 yS6 WARNING: DSR is off - modem turned off or bad
    > cable?
    > 05/27 23:40:26 yS6 lowering DTR to reset Modem
    > 05/27 23:40:27 yS6 send: \dATQ0V1H0[0d]
    > 05/27 23:40:27 yS6 waiting for ``OK'' ** found **
    > 05/27 23:40:27 yS6 send: ATS0=0Q0&D0[0d]
    > 05/27 23:40:27 yS6 waiting for ``OK'' ** found **
    > 05/27 23:40:28 yS6 waiting...
    > 05/28 00:01:36 ##### failed dev=ttyS6, pid=641, got signal 15, exiting


    No waiting for RING, no "send: ATA[0d]," no "NO CARRIER", ect., which
    were previously seen after successful modem initializations??

    A kill -SIGTERM mgetty?

    > --
    > 05/28 01:04:20 yS6 mgetty: official release 1.0.0
    > 05/28 01:04:20 yS6 check for lockfiles
    > 05/28 01:04:20 yS6 locking the line
    > 05/28 01:04:21 yS6 WARNING: DSR is off - modem turned off or bad
    > cable?
    > 05/28 01:04:21 yS6 lowering DTR to reset Modem
    > 05/28 01:04:21 yS6 send: \dATQ0V1H0[0d]
    > 05/28 01:04:22 yS6 waiting for ``OK'' ** found **
    > 05/28 01:04:22 yS6 send: ATS0=0Q0&D0[0d]
    > 05/28 01:04:22 yS6 waiting for ``OK'' ** found **
    > 05/28 01:04:22 yS6 waiting...
    > 05/28 01:04:34 yS6 waiting for ``RING'' ** found **
    > 05/28 01:04:34 yS6 send: ATA[0d]
    > 05/28 01:04:34 yS6 waiting for ``CONNECT'' ** found **
    > 05/28 01:05:05 yS6 send:
    > 05/28 01:05:05 yS6 waiting for ``
    > '' ** found **
    > 05/28 01:05:09 yS6 clean_line: only 500 of 2780 bytes logged
    > 05/28 01:05:29 yS6 getlogname: timeout


    > 05/28 01:05:51 ##### failed dev=ttyS6, pid=651, got signal 1, exiting


    Looks like a mgetty restart, but now with the "clean_line: ..." message??

    > --
    > 05/28 01:05:51 yS6 mgetty: official release 1.0.0
    > 05/28 01:05:51 yS6 check for lockfiles
    > 05/28 01:05:51 yS6 locking the line
    > 05/28 01:05:51 yS6 WARNING: DSR is off - modem turned off or bad
    > cable?
    > 05/28 01:05:51 yS6 lowering DTR to reset Modem
    > 05/28 01:05:52 yS6 send: \dATQ0V1H0[0d]
    > 05/28 01:05:52 yS6 waiting for ``OK'' ** found **
    > 05/28 01:05:52 yS6 send: ATS0=0Q0&D0[0d]
    > 05/28 01:05:52 yS6 waiting for ``OK'' ** found **
    > 05/28 01:05:53 yS6 waiting...
    > 05/28 01:07:46 yS6 waiting for ``RING'' ** found **
    > 05/28 01:07:46 yS6 send: ATA[0d]
    > 05/28 01:07:46 yS6 waiting for ``CONNECT'' ** found **
    > 05/28 01:08:16 yS6 send:
    > 05/28 01:08:16 yS6 waiting for ``
    > '' ** found **
    > 05/28 01:08:22 yS6 clean_line: only 500 of 5922 bytes logged
    > 05/28 01:08:43 yS6 getlogname: timeout


    > 05/28 01:08:47 yS6 login name all uppercase, set IUCLC OLCUC
    > 05/28 01:08:47 ##### data dev=ttyS6, pid=652, caller=none, conn='9600',
    > name='', cmd='/bin/login', user='` l'


    Timeout and an apparent login? Race condition?

    > --
    > 05/28 01:08:47 yS6 mgetty: official release 1.0.0
    > 05/28 01:08:47 yS6 check for lockfiles
    > 05/28 01:08:47 yS6 locking the line
    > 05/28 01:08:48 yS6 WARNING: DCD line still active, check modem
    > settings (AT&Dx)
    > 05/28 01:08:48 yS6 WARNING: DSR is off - modem turned off or bad
    > cable?
    > 05/28 01:08:48 yS6 lowering DTR to reset Modem
    > 05/28 01:08:54 yS6 clean_line: only 500 of 5365 bytes logged
    > 05/28 01:08:54 yS6 send: \dATQ0V1H0[0d]
    > 05/28 01:08:54 yS6 waiting for ``OK''
    > 05/28 01:09:48 yS6 timeout in chat script, waiting for `OK'
    > 05/28 01:09:48 yS6 init chat timed out, trying force-init-chat


    Timeout waiting for modem response to first initialization string
    with DCD active and DSR off apparently triggers force-init-chat.

    > 05/28 01:09:48 yS6 send: \d[10][03]\d\d\d+++\d\d\d[0d]\dATQ0V1H0[0d]
    > 05/28 01:09:52 yS6 waiting for ``OK''
    > 05/28 01:09:52 yS6 found action string: ``NO CARRIER''
    > 05/28 01:09:52 yS6 send: \dATQ0V1H0[0d]
    > 05/28 01:09:53 yS6 waiting for ``OK'' ** found **
    > 05/28 01:09:53 yS6 send: ATS0=0Q0&D0[0d]
    > 05/28 01:09:53 yS6 waiting for ``OK'' ** found **
    > 05/28 01:09:53 yS6 waiting...
    > 05/28 01:10:16 yS6 waiting for ``RING'' ** found **
    > 05/28 01:10:16 yS6 send: ATA[0d]
    > 05/28 01:10:16 yS6 waiting for ``CONNECT''
    > 05/28 01:11:19 yS6 found action string: ``NO CARRIER''
    > 05/28 01:11:19 ##### failed A_FAIL dev=ttyS6, pid=653, caller=none,
    > conn='', name=''


    > --
    > 05/28 01:11:19 yS6 mgetty: official release 1.0.0
    > 05/28 01:11:19 yS6 check for lockfiles
    > 05/28 01:11:19 yS6 locking the line
    > 05/28 01:11:20 yS6 WARNING: DSR is off - modem turned off or bad
    > cable?
    > 05/28 01:11:20 yS6 lowering DTR to reset Modem
    > 05/28 01:11:20 yS6 send: \dATQ0V1H0[0d]
    > 05/28 01:11:21 yS6 waiting for ``OK'' ** found **
    > 05/28 01:11:21 yS6 send: ATS0=0Q0&D0[0d]
    > 05/28 01:11:21 yS6 waiting for ``OK'' ** found **
    > 05/28 01:11:21 yS6 waiting...
    > 05/28 01:11:29 ##### failed dev=ttyS6, pid=655, got signal 15, exiting


    Again, no waiting for RING, no "NO CARRIER", ect. ...

    > --
    > 05/28 01:11:36 yS6 mgetty: official release 1.0.0
    > 05/28 01:11:36 yS6 check for lockfiles
    > 05/28 01:11:36 yS6 locking the line
    > 05/28 01:11:36 yS6 WARNING: DSR is off - modem turned off or bad
    > cable?
    > 05/28 01:11:36 yS6 lowering DTR to reset Modem
    > 05/28 01:11:37 yS6 send: \dATQ0V1H0[0d]
    > 05/28 01:11:38 yS6 waiting for ``OK'' ** found **
    > 05/28 01:11:38 yS6 send: ATS0=0Q0&D0[0d]
    > 05/28 01:11:38 yS6 waiting for ``OK'' ** found **
    > 05/28 01:11:38 yS6 waiting...
    > 05/28 01:12:58 yS6 waiting for ``RING'' ** found **
    > 05/28 01:12:58 yS6 send: ATA[0d]
    > 05/28 01:12:58 yS6 waiting for ``CONNECT'' ** found **
    > 05/28 01:13:20 yS6 send:
    > 05/28 01:13:20 yS6 waiting for ``
    > '' ** found **
    > 05/28 01:13:38 ##### data dev=ttyS6, pid=658, caller=none,
    > conn='9600/REL - LAPM', name='', cmd='/usr/sbin/pppd', user='/AutoPPP/'


    > --
    > 05/28 01:14:08 yS6 mgetty: official release 1.0.0
    > 05/28 01:14:08 yS6 check for lockfiles
    > 05/28 01:14:08 yS6 locking the line
    > 05/28 01:14:09 yS6 WARNING: DSR is off - modem turned off or bad
    > cable?
    > 05/28 01:14:09 yS6 lowering DTR to reset Modem
    > 05/28 01:14:10 yS6 send: \dATQ0V1H0[0d]
    > 05/28 01:14:10 yS6 waiting for ``OK'' ** found **
    > 05/28 01:14:10 yS6 send: ATS0=0Q0&D0[0d]
    > 05/28 01:14:10 yS6 waiting for ``OK'' ** found **
    > 05/28 01:14:11 yS6 waiting...
    > 05/28 01:14:25 yS6 waiting for ``RING'' ** found **
    > 05/28 01:14:25 yS6 send: ATA[0d]
    > 05/28 01:14:25 yS6 waiting for ``CONNECT''
    > 05/28 01:15:28 yS6 found action string: ``NO CARRIER''
    > 05/28 01:15:28 ##### failed A_FAIL dev=ttyS6, pid=659, caller=none,
    > conn='', name=''



    FWIW, my bottom line suggestions:

    1) Hard reset the modem.

    2) Get rid of \r, period.

    3) Update mgetty.

    4) Add "ATZ OK" immediately followed by "AT&F OK", or "AT&F1 OK" for
    USR modems, at the *beginning* of the modem initializations. Hopefully
    this should flush the serial port buffers (may be controversial) and
    reset the modem profile to default, or appropriate, factory settings
    before the other initializations are applied.

    As always, constructive criticism is welcome.

    --
    Clifford Kite Email: "echo xvgr_yvahk-ccc@ri1.arg|rot13"
    PPP-Q&A links, downloads: http://ckite.no-ip.net/
    /* The generation of random numbers is too important to be left
    to chance. */

  5. Re: AutoPPP fails to establish a connection during long distance calls

    Thanks for the comments. But i still wonder why these failures occuring
    only incase of long
    distance calls. If i connect locally this is seen not even once.


+ Reply to Thread