isdn dial-up - PPP

This is a discussion on isdn dial-up - PPP ; Hi, I used to dial into my ISP thru ISDN using pppd with the following: ************************************************** ***************** /etc/ppp/options: lock asyncmap 0 crtscts noauth idle 120 demand debug persist defaultroute usepeerdns user ksmasai /dev/ttyS1 115200 connect '/usr/sbin/chat -V -v -t 60 ...

+ Reply to Thread
Results 1 to 4 of 4

Thread: isdn dial-up

  1. isdn dial-up

    Hi,

    I used to dial into my ISP thru ISDN using pppd with the following:




    ************************************************** *****************
    /etc/ppp/options:
    lock
    asyncmap 0
    crtscts
    noauth
    idle 120
    demand
    debug
    persist
    defaultroute
    usepeerdns
    user ksmasai
    /dev/ttyS1 115200
    connect '/usr/sbin/chat -V -v -t 60 -f /etc/ppp/chatscript'
    ************************************************** *****************




    ************************************************** *****************
    /etc/ppp/chatscript:
    ABORT BUSY
    ABORT 'NO CARRIER'
    ECHO OFF
    '' "ATZ"
    OK "ATD1525"
    TIMEOUT 60
    CONNECT '\c'
    ************************************************** *****************


    but recently when i tried to dial it says:



    ************************************************** *****************
    Feb 1 08:49:21 intra pppd[28217]: Starting link
    Feb 1 08:49:22 intra chat[29564]: abort on (BUSY)
    Feb 1 08:49:22 intra chat[29564]: abort on (NO CARRIER)
    Feb 1 08:49:22 intra chat[29564]: send (ATZ^M)
    Feb 1 08:49:22 intra chat[29564]: expect (OK)
    Feb 1 08:49:23 intra chat[29564]: ATZ^M
    Feb 1 08:49:23 intra chat[29564]: OK
    Feb 1 08:49:23 intra chat[29564]: -- got it
    Feb 1 08:49:23 intra chat[29564]: send (ATD1525^M)
    Feb 1 08:49:23 intra chat[29564]: timeout set to 60 seconds
    Feb 1 08:49:23 intra chat[29564]: expect (CONNECT)
    Feb 1 08:49:23 intra chat[29564]: ^M
    Feb 1 08:49:24 intra chat[29564]: ATD1525^M^M
    Feb 1 08:49:24 intra chat[29564]: CARRIER 64000^M
    Feb 1 08:49:24 intra chat[29564]: ^M
    Feb 1 08:49:24 intra chat[29564]: PROTOCOL: HDLC^M
    Feb 1 08:49:24 intra chat[29564]: ^M
    Feb 1 08:49:24 intra chat[29564]: COMPRESSION: NONE^M
    Feb 1 08:49:24 intra chat[29564]: ^M
    Feb 1 08:49:24 intra chat[29564]: CONNECT
    Feb 1 08:49:24 intra chat[29564]: -- got it
    Feb 1 08:49:24 intra chat[29564]: send ()
    Feb 1 08:49:24 intra pppd[28217]: Serial connection established.
    Feb 1 08:49:24 intra pppd[28217]: Connect: ppp0 <--> /dev/ttyS1
    Feb 1 08:49:55 intra pppd[28217]: LCP: timeout sending
    Config-Requests
    Feb 1 08:49:55 intra pppd[28217]: Connection terminated.
    Feb 1 08:49:55 intra pppd[28217]: Receive serial link is not 8-bit
    clean:
    Feb 1 08:49:55 intra pppd[28217]: Problem: all had bit 7 set to 0
    Feb 1 08:49:55 intra pppd[28217]: Hangup (SIGHUP)
    ************************************************** *****************




    i tried for about 20 times "killall -HUP pppd" again and again with no
    luck. Finally what i did is plug the diva TA into a windows XP box and
    install the driver that comes with it, it connects in about 3 seconds
    and here is the log file:




    ************************************************** *****************
    02-03-2004 15:39:27.939 - File: C:\WINDOWS\System32\tapisrv.dll,
    Version 5.1.2600
    02-03-2004 15:39:27.949 - File: C:\WINDOWS\System32\unimdm.tsp,
    Version 5.1.2600
    02-03-2004 15:39:27.949 - File: C:\WINDOWS\System32\unimdmat.dll,
    Version 5.1.2600
    02-03-2004 15:39:27.949 - File: C:\WINDOWS\System32\uniplat.dll,
    Version 5.1.2600
    02-03-2004 15:39:28.019 - File: C:\WINDOWS\System32\drivers\modem.sys,
    Version 5.1.2600
    02-03-2004 15:39:28.080 - File: C:\WINDOWS\System32\modemui.dll,
    Version 5.1.2600
    02-03-2004 15:39:28.290 - File: C:\WINDOWS\System32\mdminst.dll,
    Version 5.1.2600
    02-03-2004 15:39:28.290 - Modem type: Diva 852 ISDN TA PnP
    02-03-2004 15:39:28.290 - Modem inf path: oem11.inf
    02-03-2004 15:39:28.290 - Modem inf section: TASER
    02-03-2004 15:39:28.290 - Matching hardware ID: serenum\eic4905
    02-03-2004 15:39:28.310 - Opening Modem
    02-03-2004 15:39:28.310 - 115200,8,N,1, ctsfl=1, rtsctl=2
    02-03-2004 15:39:28.310 - Initializing modem.
    02-03-2004 15:39:28.320 - Send: AT
    02-03-2004 15:39:28.330 - Recv: OK
    02-03-2004 15:39:28.330 - Interpreted response: OK
    02-03-2004 15:39:28.340 - Send: AT&FES95=13W2&B2%B0\P1
    02-03-2004 15:39:28.360 - Recv: OK
    02-03-2004 15:39:28.360 - Interpreted response: OK
    02-03-2004 15:39:28.370 - Send: AT&B2%B0\P0
    02-03-2004 15:39:28.380 - Recv: OK
    02-03-2004 15:39:28.380 - Interpreted response: OK
    02-03-2004 15:39:28.400 - Send: ATS7=60&K3
    02-03-2004 15:39:28.410 - Recv: OK
    02-03-2004 15:39:28.410 - Interpreted response: OK
    02-03-2004 15:39:28.420 - Waiting for a call.
    02-03-2004 15:39:28.430 - Send: ATS0=0
    02-03-2004 15:39:28.440 - Recv: OK
    02-03-2004 15:39:28.440 - Interpreted response: OK
    02-03-2004 15:39:28.580 - TSP(0000): Making Call
    02-03-2004 15:39:28.580 - 115200,8,N,1, ctsfl=1, rtsctl=2
    02-03-2004 15:39:28.580 - Initializing modem.
    02-03-2004 15:39:28.590 - Send: AT
    02-03-2004 15:39:28.600 - Recv: OK
    02-03-2004 15:39:28.600 - Interpreted response: OK
    02-03-2004 15:39:28.610 - Send: AT&FES95=13W2&B2%B0\P1
    02-03-2004 15:39:28.630 - Recv: OK
    02-03-2004 15:39:28.630 - Interpreted response: OK
    02-03-2004 15:39:28.640 - Send: AT&B2%B0\P0
    02-03-2004 15:39:28.650 - Recv: OK
    02-03-2004 15:39:28.650 - Interpreted response: OK
    02-03-2004 15:39:28.660 - Send: ATS7=60&K3
    02-03-2004 15:39:28.670 - Recv: OK
    02-03-2004 15:39:28.670 - Interpreted response: OK
    02-03-2004 15:39:28.680 - Dialing.
    02-03-2004 15:39:28.680 - TSP Completing Async Operation(0x00010100)
    Status 0x00000000
    02-03-2004 15:39:28.680 - TSP(0000): LINEEVENT: LINECALLSTATE_DIALING
    02-03-2004 15:39:28.690 - Send: ATD####
    02-03-2004 15:39:28.700 - TSP(0000): LINEEVENT:
    LINECALLSTATE_PROCEEDING
    02-03-2004 15:39:28.801 - Recv:
    02-03-2004 15:39:28.801 - Interpreted response: Informative
    02-03-2004 15:39:30.743 - Recv:
    02-03-2004 15:39:30.743 - Interpreted response: Informative
    02-03-2004 15:39:30.743 - Recv:
    02-03-2004 15:39:30.743 - Interpreted response: Informative
    02-03-2004 15:39:30.753 - Recv: CARRIER 64000
    02-03-2004 15:39:30.753 - Interpreted response: Informative
    02-03-2004 15:39:30.753 - Recv:
    02-03-2004 15:39:30.753 - Interpreted response: Informative
    02-03-2004 15:39:30.753 - Recv:
    02-03-2004 15:39:30.753 - Interpreted response: Informative
    02-03-2004 15:39:30.753 - Recv: PROTOCOL: PPP
    02-03-2004 15:39:30.753 - Interpreted response: Informative
    02-03-2004 15:39:30.753 - Recv:
    02-03-2004 15:39:30.753 - Interpreted response: Informative
    02-03-2004 15:39:30.753 - Recv:
    02-03-2004 15:39:30.753 - Interpreted response: Informative
    02-03-2004 15:39:30.753 - Recv: CONNECT 64000
    02-03-2004 15:39:30.753 - Interpreted response: Connect
    02-03-2004 15:39:30.753 - Connection established at 64000bps.
    02-03-2004 15:39:30.753 - Error-control on.
    02-03-2004 15:39:30.753 - Data compression off or unknown.
    02-03-2004 15:39:30.753 - TSP(0000): LINEEVENT:
    LINECALLSTATE_CONNECTED
    02-03-2004 15:40:00.757 - Read: Total: 80341, Per/Sec: 2675, Written:
    Total: 14460, Per/Sec: 480
    02-03-2004 15:41:22.374 - TSP(0000): Dropping Call
    02-03-2004 15:41:22.374 - Hanging up the modem.
    02-03-2004 15:41:22.374 - Hardware hangup by lowering DTR.
    02-03-2004 15:41:22.524 - Detected CD dropped from lowering DTR
    02-03-2004 15:41:22.524 - Recv:
    02-03-2004 15:41:22.524 - Interpreted response: Informative
    02-03-2004 15:41:22.524 - Recv:
    02-03-2004 15:41:22.524 - Interpreted response: Informative
    02-03-2004 15:41:22.524 - Recv: NO CARRIER
    02-03-2004 15:41:22.524 - Interpreted response: No Carrier
    02-03-2004 15:41:22.534 - Send: ATH
    02-03-2004 15:41:22.544 - Recv: OK
    02-03-2004 15:41:22.544 - Interpreted response: OK
    02-03-2004 15:41:22.544 - 115200,8,N,1, ctsfl=1, rtsctl=2
    02-03-2004 15:41:22.544 - Initializing modem.
    02-03-2004 15:41:22.554 - Send: AT
    02-03-2004 15:41:22.564 - Recv: OK
    02-03-2004 15:41:22.564 - Interpreted response: OK
    02-03-2004 15:41:22.574 - Send: AT&FES95=13W2&B2%B0\P1
    02-03-2004 15:41:22.594 - Recv: OK
    02-03-2004 15:41:22.594 - Interpreted response: OK
    02-03-2004 15:41:22.604 - Send: AT&B2%B0\P0
    02-03-2004 15:41:22.614 - Recv: OK
    02-03-2004 15:41:22.614 - Interpreted response: OK
    02-03-2004 15:41:22.624 - Send: ATS7=60&K3
    02-03-2004 15:41:22.634 - Recv: OK
    02-03-2004 15:41:22.634 - Interpreted response: OK
    02-03-2004 15:41:22.634 - Waiting for a call.
    02-03-2004 15:41:22.644 - Send: ATS0=0
    02-03-2004 15:41:22.654 - Recv: OK
    02-03-2004 15:41:22.654 - Interpreted response: OK
    02-03-2004 15:41:22.654 - TSP(0000): LINEEVENT:
    LINECALLSTATE_DISCONNECTED(0x1)
    02-03-2004 15:41:22.654 - TSP(0000): LINEEVENT: LINECALLSTATE_IDLE
    02-03-2004 15:41:22.654 - TSP Completing Async Operation(0x000100bb)
    Status 0x00000000
    02-03-2004 15:41:22.654 - TSP(0000): Dropping Call
    02-03-2004 15:41:22.654 - TSP Completing Async Operation(0x000100aa)
    Status 0x00000000
    02-03-2004 15:41:22.654 - TSP(0000): Closing Call
    02-03-2004 15:41:22.654 - Session Statistics:
    02-03-2004 15:41:22.654 - Reads : 30 bytes
    02-03-2004 15:41:22.654 - Writes: 56 bytes
    ************************************************** *****************


    I'm sorry if this seems a bit long but any idea please?

  2. Re: isdn dial-up

    arnold7979@hotmail.com (Junior Arnold) writes:
    > '' "ATZ"
    > OK "ATD1525"


    This is very likely to be the problem. First of all, ATZ is unlikely
    to produce the configuration desired. It means "restore to last saved
    [&W] configuration values."

    What should appear here are configuration bits necessary for the
    Terminal Adapter (mis-named "ISDN modem") to connect and do async PPP
    translation. See the reference manual for your TA for details, or try
    to get ahold of an ".INI" file from a Windows diskette for the TA.

    > Feb 1 08:49:55 intra pppd[28217]: Receive serial link is not 8-bit
    > clean:
    > Feb 1 08:49:55 intra pppd[28217]: Problem: all had bit 7 set to 0


    This means that the peer isn't running PPP at all. Instead, it's at
    some sort of command line prompt. To find out what really happened,
    use a terminal program (such as "cu" or "miniterm") to connect to the
    TA, and issue the dialing sequence that your chat script does.

    > 02-03-2004 15:39:28.340 - Send: AT&FES95=13W2&B2%B0\P1
    > 02-03-2004 15:39:28.370 - Send: AT&B2%B0\P0
    > 02-03-2004 15:39:28.400 - Send: ATS7=60&K3


    Ah ha! There's the initialization sequence you need. Just toss some
    variation on that into the chat script:

    '' 'AT&FES95=13W2&B2%B0\P1'
    OK 'AT&B2%B0\P0'
    OK 'ATS7=60&K3'
    OK 'ATD1525'

    For extra points, you could reduce the number of lines in the chat
    script and make it a little faster by reading the manual for the TA
    carefully, but that's not necessary.

    --
    James Carlson, IP Systems Group
    Sun Microsystems / 1 Network Drive 71.234W Vox +1 781 442 2084
    MS UBUR02-212 / Burlington MA 01803-2757 42.497N Fax +1 781 442 1677

  3. Re: isdn dial-up

    James Carlson wrote in message news:...
    > arnold7979@hotmail.com (Junior Arnold) writes:
    > > '' "ATZ"
    > > OK "ATD1525"

    >
    > This is very likely to be the problem. First of all, ATZ is unlikely
    > to produce the configuration desired. It means "restore to last saved
    > [&W] configuration values."
    >


    Yeah, first step i removed the ATZ.

    > What should appear here are configuration bits necessary for the
    > Terminal Adapter (mis-named "ISDN modem") to connect and do async PPP
    > translation. See the reference manual for your TA for details, or try
    > to get ahold of an ".INI" file from a Windows diskette for the TA.
    >
    > > Feb 1 08:49:55 intra pppd[28217]: Receive serial link is not 8-bit
    > > clean:
    > > Feb 1 08:49:55 intra pppd[28217]: Problem: all had bit 7 set to 0

    >
    > This means that the peer isn't running PPP at all. Instead, it's at
    > some sort of command line prompt. To find out what really happened,
    > use a terminal program (such as "cu" or "miniterm") to connect to the
    > TA, and issue the dialing sequence that your chat script does.
    >


    You're right, i tried minicom and
    ->AT
    OK
    ->ATD1525
    (somethin)
    ->(just hit enter)

    and it presents me with a "node-i34-prompt>" with very few commands
    available, i tried all of them, nothing useful


    > > 02-03-2004 15:39:28.340 - Send: AT&FES95=13W2&B2%B0\P1
    > > 02-03-2004 15:39:28.370 - Send: AT&B2%B0\P0
    > > 02-03-2004 15:39:28.400 - Send: ATS7=60&K3

    >
    > Ah ha! There's the initialization sequence you need. Just toss some
    > variation on that into the chat script:
    >
    > '' 'AT&FES95=13W2&B2%B0\P1'
    > OK 'AT&B2%B0\P0'
    > OK 'ATS7=60&K3'
    > OK 'ATD1525'
    >


    initially i tried with some pretty error instead of "OK" in return, i
    thought the ^M is making trouble so i typed them again, char by char
    and, no luck.

    So what i did after my dinner is using the ancient escape trick:
    "...%B0\P1" became "...%B0\\P1'

    and TADA!!!!


    > For extra points, you could reduce the number of lines in the chat
    > script and make it a little faster by reading the manual for the TA
    > carefully, but that's not necessary.


    yeah, thanks for the advice. I figured out what is the string doing
    now, will try to do "bandwidth on demand" next, with "RAW" AT
    COMMANDS!! =D

    Thanks!!


    Regards,
    Jr. Arnold

  4. Re: isdn dial-up

    arnold7979@hotmail.com (Junior Arnold) writes:
    > initially i tried with some pretty error instead of "OK" in return, i
    > thought the ^M is making trouble so i typed them again, char by char
    > and, no luck.
    >
    > So what i did after my dinner is using the ancient escape trick:
    > "...%B0\P1" became "...%B0\\P1'


    Ah, nuts. I should have caught that. Yes, you need to escape special
    characters.

    > yeah, thanks for the advice. I figured out what is the string doing
    > now, will try to do "bandwidth on demand" next, with "RAW" AT
    > COMMANDS!! =D


    Good luck ...

    --
    James Carlson, IP Systems Group
    Sun Microsystems / 1 Network Drive 71.234W Vox +1 781 442 2084
    MS UBUR02-212 / Burlington MA 01803-2757 42.497N Fax +1 781 442 1677

+ Reply to Thread