Topic: ISP/ISDN Problems

[Danny]

I'm trying to configure e-smith to connect via ISDN. The system works fine with another ISP, but as soon as i try and use Plusnet i get the following error:-

Jan 18 12:11:14 e-smith kernel: lldata_handler unknown primitive 0x232
Jan 18 12:11:16 e-smith kernel: lldata_handler unknown primitive 0x232

Does anyone know what this means or how to fix it?

thanks in advance,

Danny.

Full log bellow:
Jan 18 12:11:10 e-smith chat[866]: abort on (NO CARRIER)
Jan 18 12:11:10 e-smith chat[866]: abort on (NO DIALTONE)
Jan 18 12:11:10 e-smith chat[866]: abort on (Invalid Login)
Jan 18 12:11:10 e-smith chat[866]: abort on (Login incorrect)
Jan 18 12:11:10 e-smith chat[866]: send (ATZ^M)
Jan 18 12:11:11 e-smith chat[866]: expect (OK)
Jan 18 12:11:11 e-smith chat[866]: ATZ^M^M
Jan 18 12:11:11 e-smith chat[866]: OK
Jan 18 12:11:11 e-smith chat[866]: -- got it
Jan 18 12:11:11 e-smith chat[866]: send (ATDT08440404101^M)
Jan 18 12:11:11 e-smith chat[866]: expect (CONNECT)
Jan 18 12:11:11 e-smith chat[866]: ^M
Jan 18 12:11:14 e-smith kernel: lldata_handler unknown primitive 0x232
Jan 18 12:11:16 e-smith kernel: lldata_handler unknown primitive 0x232
Jan 18 12:11:17 e-smith chat[866]: ATDT08440404101^M^M
Jan 18 12:11:17 e-smith chat[866]: NO CARRIER
Jan 18 12:11:17 e-smith chat[866]: -- failed
Jan 18 12:11:17 e-smith chat[866]: Failed (NO CARRIER)
Jan 18 12:11:17 e-smith diald[363]: Connect script failed.
Jan 18 12:11:18 e-smith diald[363]: Delaying 10 seconds before clear to dial.

[Danny]

I changed the AT string to include ATS14=3 which sorted the lldata problem (my ISP needed to use HDLC), but i'm still stuck.

It connects ok, waits, then just hangs up. I've have checked my secrets files and everything else i can find.

Can someone tell me how to get more information, or point me in the right direction.

My log now looks like this:)

Jan 24 07:47:26 iserver diald[363]: Delaying 10 seconds before clear to dial.
Jan 24 07:47:37 iserver diald[363]: Calling site 192.168.1.2
Jan 24 07:47:38 iserver chat[717]: abort on (BUSY)
Jan 24 07:47:38 iserver chat[717]: abort on (ERROR)
Jan 24 07:47:38 iserver chat[717]: abort on (NO CARRIER)
Jan 24 07:47:38 iserver chat[717]: abort on (NO DIALTONE)
Jan 24 07:47:38 iserver chat[717]: abort on (Invalid Login)
Jan 24 07:47:38 iserver chat[717]: abort on (Login incorrect)
Jan 24 07:47:38 iserver chat[717]: send (ATZ&E123456S14=3^M)
Jan 24 07:47:38 iserver chat[717]: expect (OK)
Jan 24 07:47:38 iserver chat[717]: ATZ&E123456S14=3^M^M
Jan 24 07:47:38 iserver chat[717]: OK
Jan 24 07:47:38 iserver chat[717]: -- got it
Jan 24 07:47:38 iserver chat[717]: send (ATDT08451400101^M)
Jan 24 07:47:38 iserver chat[717]: expect (CONNECT)
Jan 24 07:47:38 iserver chat[717]: ^M
Jan 24 07:47:40 iserver chat[717]: ATDT08451400101^M^M
Jan 24 07:47:40 iserver chat[717]: CONNECT
Jan 24 07:47:40 iserver chat[717]: -- got it
Jan 24 07:47:40 iserver diald[363]: Connected to site 192.168.1.2
Jan 24 07:47:40 iserver pppd[718]: pppd 2.3.11 started by root, uid 0
Jan 24 07:47:40 iserver diald[363]: Running pppd (pid = 718).
Jan 24 07:47:40 iserver pppd[718]: Using interface ppp0
Jan 24 07:47:40 iserver pppd[718]: Connect: ppp0 <--> /dev/ttyI0
Jan 24 07:48:04 iserver pppd[718]: Hangup (SIGHUP)
Jan 24 07:48:04 iserver pppd[718]: Modem hangup
Jan 24 07:48:04 iserver pppd[718]: Connection terminated.
Jan 24 07:48:04 iserver pppd[718]: Exit.
Jan 24 07:48:04 iserver diald[363]: start sl0: SIOCSIFMTU: Invalid argument
Jan 24 07:48:04 iserver diald[363]: start sl0: SIOCADDRT: File exists
Jan 24 07:48:04 iserver diald[363]: stop ppp0: SIOCDELRT: No such process
Jan 24 07:48:04 iserver kernel: ppp: ppp0 not active
Jan 24 07:48:04 iserver diald[363]: stop ppp0: SIOCSIFFLAGS: Device not configured
Jan 24 07:48:05 iserver diald[363]: Delaying 10 seconds before clear to dial.

I dont know wether this helps, but i've also tried doing a manual PPP connection via minicom/pppd (which i assume i've done right) and i get the following:-

[root@iserver ppp]# pppd -d -detach /dev/ttyI0 38400
Using interface ppp0
Connect: ppp0 <--> /dev/ttyI0
sent [LCP ConfReq id=0x1 ]
sent [LCP ConfReq id=0x1 ]
sent [LCP ConfReq id=0x1 ]
sent [LCP ConfReq id=0x1 ]
sent [LCP ConfReq id=0x1 ]
sent [LCP ConfReq id=0x1 ]
sent [LCP ConfReq id=0x1 ]
Modem hangup
Connection terminated.
[root@iserver ppp]#

My minicom screen shows:-

AT&E531349 S14=3                                    
OK                                                  
atdt08440404101                                      
CONNECT 64000/HDLC                                  
ÿ..!..ÿ..!.....#.û..I..ô.       .BTMDIPÿ..!.....#.û..I..ô.      .BTMDIPÿ..!....P
NO CARRIER

Can some please help, i've been trying to sort this for 2 days solid now and my eyes are going square from RTFMing and browsing newsgroups/webpages:))

many thanks:)

Danny.

[Danny]

Someone please help, i've been at this all week now:(

[Tudor]

Hi Danny

The answer for my Pace ISDN TA is found under section 3 at http:www.precedence.co.uk/nc/faq/net.html as the problem is with both BT Surftime and BTi.

The init strings are there but I don't how to manipulate them into a useable format.

If you get it to work, let me know

Tudor
www.striatum.org

[Rob]

Hi Danny and Tudor

I use a Hayes Accura ISDN TA for Connection to My ISP Btinternet
on The sutftime Package and all works well for over 1 year now with e-smith

Looking at your Example Log Readout I noted that u Use
ATDT0844????????  IN YOUR DIAL SCRIPT..
tudor actually uses ATD084//////////////

look here
etc/sysconfig/network-scripts and view/edit the file chat-ppp0
mine follows
#------------------------------------------------------------
# DO NOT MODIFY THIS FILE! It is updated automatically by the
# e-smith server and gateway software. Instead, modify the source
# template in the /etc/e-smith/templates directory. For more
# information, see http://www.e-smith.org.
#
# copyright (C) 1999, 2000 e-smith, inc.
#------------------------------------------------------------

'ABORT' 'BUSY'
'ABORT' 'ERROR'
'ABORT' 'NO CARRIER'
'ABORT' 'NO DIALTONE'
'ABORT' 'Invalid Login'
'ABORT' 'Login incorrect'
'' 'ATZ'
'OK' 'ATDI08440404005'  <<<<< Check this Line Here
'CONNECT'

#------------------------------------------------------------
# TEMPLATE END
#------------------------------------------------------------

Note I use ATDI

I being ISDN and Not T for Tone or P for Pulse

Without this I cannot Connect to BT with the standard file created by e-smith
bt ALSO USE cHAT AND not pap E-SMITH DOES SUPPORT tHIS
Dont forget to also alter the Template as well as this file

I also haave a Pace ISDN TA Surpluss to Requirements due to never being able to get it working under linux  its fine with Windows...

Heres hoping this helps you
if not get in touch I will send you all my config files by email if required

Rob
Derby UK

[Charlie Brady]

Rob wrote:

> look here
> etc/sysconfig/network-scripts and view/edit the file chat-ppp0

No, don't do that.

> #------------------------------------------------------------
> # DO NOT MODIFY THIS FILE! It is updated automatically by the
> # e-smith server and gateway software. Instead, modify the
> # template in the /etc/e-smith/templates directory. For more
> # information, see http://www.e-smith.org.

Specifically, see http://www.e-smith.org/custom/.

Regards

Charlie

[guestFF]

Hi,

Besides your specific problem, may I ask you how you configured ISDN with e-smith for I've tryed this many times with no success.....

regards,

H.F. Wang