Topic: Revisited (ISDN how-to for 4.1.1:here is it!) - A Query

[Ian Martin]

Hi all,

Thanks for passing on all your knowledge, but I have hit a snag.

I have followed the tutorial word for word, and even used the original from Klause Mueller updated by Ronald Tanis.

Tweaked it for the UK British Telecom system ('ATZ&E0 in the 20reset file) and everthing seems fine, the line connects dials out
gives an OK then stops with a NO CARRIER error ?

Any idea's I'm stumped, I have waded through the internet-sicherheit.net web site and others and couldnt find the answer.

Your help is required please

Ian Martin a UK discoverer of e-smith

[Ian Martin]

As requested by Engelmann the chat-ppp0 file, and for good measure my messages log file and the text from isdn4linux help where I found the setting for the MSN in the UK, my ISDN Card is the AVM Fritz PCI (BT Speedway in the UK) and my ISDN connection is the BTHH in the text, hence my entering the AT&E0 in the script.

Many thanks in advance for your help in this matter.

Ian Martin

#------------------------------------------------------------
# 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'
REPORT CONNECT
'' 'ATZ&E0''OK' 'AT''OK' 'ATDT08089933001'
'CONNECT'

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

____________________________________________________

Apr 12 19:15:28 e-smith diald[529]: Connect script failed.
Apr 12 19:15:29 e-smith diald[529]: Delaying 10 seconds before clear to dial.
Apr 12 19:15:39 e-smith diald[529]: Calling site 0.0.0.0
Apr 12 19:15:40 e-smith chat[1265]: abort on (BUSY)
Apr 12 19:15:40 e-smith chat[1265]: abort on (ERROR)
Apr 12 19:15:40 e-smith chat[1265]: abort on (NO CARRIER)
Apr 12 19:15:40 e-smith chat[1265]: abort on (NO DIALTONE)
Apr 12 19:15:40 e-smith chat[1265]: abort on (Invalid Login)
Apr 12 19:15:40 e-smith chat[1265]: abort on (Login incorrect)
Apr 12 19:15:40 e-smith chat[1265]: report (CONNECT)
Apr 12 19:15:40 e-smith chat[1265]: send (ATZ&E0^M)
Apr 12 19:15:40 e-smith chat[1265]: expect (OK)
Apr 12 19:15:40 e-smith chat[1265]: ATZ&E0^M^M
Apr 12 19:15:40 e-smith chat[1265]: OK
Apr 12 19:15:40 e-smith chat[1265]:  -- got it
Apr 12 19:15:40 e-smith chat[1265]: send (AT^M)
Apr 12 19:15:40 e-smith chat[1265]: expect (OK)
Apr 12 19:15:40 e-smith chat[1265]: ^M
Apr 12 19:15:40 e-smith chat[1265]: AT^M^M
Apr 12 19:15:40 e-smith chat[1265]: OK
Apr 12 19:15:40 e-smith chat[1265]:  -- got it
Apr 12 19:15:40 e-smith chat[1265]: send (ATDT08089933001^M)
Apr 12 19:15:41 e-smith chat[1265]: expect (CONNECT)
Apr 12 19:15:41 e-smith chat[1265]: ^M
Apr 12 19:15:41 e-smith chat[1265]: ATDT08089933001^M^M
Apr 12 19:15:41 e-smith chat[1265]: BUSY
Apr 12 19:15:41 e-smith chat[1265]:  -- failed
Apr 12 19:15:41 e-smith chat[1265]: Failed (BUSY)
Apr 12 19:15:41 e-smith diald[529]: Connect script failed.
Apr 12 19:15:42 e-smith diald[529]: Delaying 10 seconds before clear to dial.
____________________________________________________

·   ISDN: Does not allow normal MSNs in UK. Each MSN is actually a single digit, 0 - 9, corresponding to the last digit of the actual phone number. You either have *no* MSNs (then configure isdn4linux to use '0' as MSN, e.g. with AT&E0), or 10 MSNs; you then always get a block of 10 sequential telephone numbers (xxx0-xxx9), of which the last digit (0-9) is your MSN (0 is used in case you use an invalid number).
·   ISDN2e: Seems to be normal EuroISDN. You are assigned MSNs which you can use and configure for isdn4linux. The MSN is reported to consist of the last 6 digits of your telephone number (try to add digits from your area code, if the local number part is shorter than 6 digits).
·   BTHH (BT HomeHighway): additionally to 2 ISDN ports it includes two analog lines with separate telephone number - but calls to and fro for those won't be signalled on the ISDN line, even so they use up a B-channel. Additional MSN are NOT available (therefore use '0' as MSN to configure isdn4linux). Charge info is possible for extra cost. Configure isdn4linux only with your 'digital number' as MSN.
·   BTBH (BT BusinessHighway): The additional paperwork including a credit-check enables you to get MSNs and other extras for extra cost. Otherwise pretty much like BTHH. Configure isdn4linux to use your 'digital number' and/or your MSNs.

[Ian Martin]

Me Again,

BTW please be gentle with me, I'm a Linux (UNIX) newbie, but love it.

It took me a sleepless night trying to work out how to get the text files from my e-smith box over to my windoze system to be able to post them to the user group. that why I didn't manage it yesterday.

I managed it in the end by using the files directory in my primary web domain in e-smith. And what then... yes your right I could'nt open them with my file editor!, luckily my brain was working better tonight and a quick CHMOD on the files did the trick.

As an aside Klaus Mueller is right there are lots of us out in europe using passive ISDN cards, especially in the UK using the same card and system setup as mine, most small businesses operate with the ISDN British Telecom system as I do, there is a gaping hole in the market which e-smith with a few tweaks could exploit. Most small businesss over here in the UK are like my looking for a cheaper easier more viable alternative to MS Windows and its spiraling software cost

Regards All

Ian Martin

[Engelmann]

sorry, i go to holiday today - but i will have a deeper look on your problem in about 1 week.
your chat-ppp0 should look more like this:

ABORT' 'BUSY'
'ABORT' 'ERROR'
'ABORT' 'NO CARRIER'
'ABORT' 'NO DIALTONE'
'ABORT' 'Invalid Login'
'ABORT' 'Login incorrect'
REPORT CONNECT
'' 'ATZ&E0'                <-- try only the ATZ  (without &E0)
'OK' 'AT'                   <--this line can also be deleted
'OK' 'ATDT08089933001'  <-- is the number right? do u have to dial a prefix (eg. 0)?
'CONNECT'

have u tried another ISPs number?

i will help u in one week - sorry - btw. i changed my isp - so i have ADSL now - that makes all ISDN questions harder to test for me!

[Ian Martin]

Sorry Engelmann,

I have just realised I copied the wrong bit of the messages log, this is the bit it should have been.

Have a nice holiday, We will speak again on your return, in the mean time I will give your last suggestions a try.

Regards Ian Martin

Apr 11 14:55:15 e-smith diald[529]: Connect script failed.
Apr 11 14:55:16 e-smith diald[529]: Delaying 10 seconds before clear to dial.
Apr 11 14:55:27 e-smith diald[529]: Calling site 0.0.0.0
Apr 11 14:55:28 e-smith chat[1188]: abort on (BUSY)
Apr 11 14:55:28 e-smith chat[1188]: abort on (ERROR)
Apr 11 14:55:28 e-smith chat[1188]: abort on (NO CARRIER)
Apr 11 14:55:28 e-smith chat[1188]: abort on (NO DIALTONE)
Apr 11 14:55:28 e-smith chat[1188]: abort on (Invalid Login)
Apr 11 14:55:28 e-smith chat[1188]: abort on (Login incorrect)
Apr 11 14:55:28 e-smith chat[1188]: report (CONNECT)
Apr 11 14:55:28 e-smith chat[1188]: send (ATZ&E0^M)
Apr 11 14:55:28 e-smith chat[1188]: expect (OK)
Apr 11 14:55:28 e-smith chat[1188]: ATZ&E0^M^M
Apr 11 14:55:28 e-smith chat[1188]: OK
Apr 11 14:55:28 e-smith chat[1188]:  -- got it
Apr 11 14:55:28 e-smith chat[1188]: send (AT^M)
Apr 11 14:55:28 e-smith chat[1188]: expect (OK)
Apr 11 14:55:28 e-smith chat[1188]: ^M
Apr 11 14:55:28 e-smith chat[1188]: AT^M^M
Apr 11 14:55:28 e-smith chat[1188]: OK
Apr 11 14:55:28 e-smith chat[1188]:  -- got it
Apr 11 14:55:28 e-smith chat[1188]: send (ATDT08089933001^M)
Apr 11 14:55:28 e-smith chat[1188]: expect (CONNECT)
Apr 11 14:55:28 e-smith chat[1188]: ^M
Apr 11 14:55:35 e-smith chat[1188]: ATDT08089933001^M^M
Apr 11 14:55:35 e-smith chat[1188]: NO CARRIER
Apr 11 14:55:35 e-smith chat[1188]:  -- failed
Apr 11 14:55:35 e-smith chat[1188]: Failed (NO CARRIER)
Apr 11 14:55:35 e-smith diald[529]: Connect script failed.
Apr 11 14:55:36 e-smith diald[529]: Delaying 10 seconds before clear to dial.

[Kees Blokland]

Something just caught my eye..

(..not knowing what hardware you have I might be totally wrong, but:)


Apr 11 14:55:35 e-smith chat[1188]: ATDT08089933001^M^M

you are saying here Attention, Dial TONE 0808etc..
Now being ISDN, there is NO dial TONE

Maybe this is the reason you get a Carrier Failed etc..

worth giving it a try !

I once used an external TA adaptor and I clearly remember that it was ATD0808.. as in Attention, Dial 08

...I had a fight for a while with similar stuff and in the end went to a seperate router, which works like a dream on bthighway.
(have a look at www.fli4l.de )

[Kees Blokland]

Just looked up a bit from a message I posted at the time on the LRP list:


Jul 16 15:58:40 roetert chat[509]: -- got it
Jul 16 15:58:40 roetert chat[509]: send (ATD08007317964^M)
Jul 16 15:58:41 roetert chat[509]: expect (PPP)
Jul 16 15:58:41 roetert chat[509]: ^M
Jul 16 15:58:42 roetert chat[509]: ATD08007317964^M^M
Jul 16 15:58:42 roetert chat[509]: CONNECT 64000/Async. To Sync. PPP
Jul 16 15:58:42 roetert chat[509]: -- got it
Jul 16 15:58:42 roetert chat[509]: send (ppp'\dc'^M)
Jul 16 15:58:43 roetert pppd[501]: Serial connection established.
Jul 16 15:58:44 roetert pppd[501]: Connect: ppp0 <--> /dev/ttyS0
Jul 16 15:58:44 roetert pppd[501]: sent [LCP ConfReq id=0x1
As you see, it connects on ATD !!

[Ian Martin]

Hi Kees,

Thanks for your advice, unfortunately dropping the T (ATDTxxxxx) didn’t work. Following this theme I tried adding a &C0 (&C0 = Carrier detect override) to the script, this didn’t work either. Never mind I will keep trying.

I am going to dissect my dual boot Win98/Red Hat machine and see if I can work out how that manages to connect using the same type of ISDN card (AVM Fritz PCI) under Red Hat 7.

But being a Linux newbie it’s quite a steep learning curve at the moment, still the more I investigate the more I learn, two weeks ago I couldn’t get into root on my e-smith machine!

Regards Ian

[guestFF]

Hi all,

Ian, try the following:

Edit the file:
'/etc/e-smith/templates/etc/sysconfig/network-scripts/chat-ppp0/15reports'

It contains 'REPORT CONNECT'

Delete this line so the file is empty.

Try to connect.

btw, because we use modem emulation mode of isdn4k instead of 'pure' ISDN, ATDT is ok to use.

Please let us know.

Regards,

HFW

[Charlie Brady]

guestFF wrote:

> Ian, try the following:
>
> Edit the file:
> '/etc/e-smith/templates/etc/sysconfig/network-scripts/chat-ppp0/15reports'
>
> It contains 'REPORT CONNECT'
>
> Delete this line so the file is empty.

This is incorrect advice. Instead of editing that file, create an empty file:

/etc/e-smith/templates-custom/etc/sysconfig/network-scripts/chat-ppp0/15reports

See http://www.e-smith.org/custom/.

Charlie

[guestFF]

Hi Charlie,

That would be my 'second' advice, just after Ian would report it would or would not work.

This is a more 'simple 'quick' check' instead of explaining the procedure to make a custom template, expand template etc.

Like I did before, I will point out the chapter of customising the e-smith server installation by referring to: http://www.e-smith.org/content/custom/.

Thanks.

HFW

[Ian Martin]

Hi Guys,

Thanks for the advice, I have tried both H F Wang & Charlie Brady’s advice and still get a NO CARRIER error. Never mind I have a few direct responses to my query, one suggesting I try ippd, and I will give these a try over the next few days, the only trouble is work keeps getting in the way!

I feel that now I have pricked the ears of the E-Smith support team (in the guise of Charlie)
a need to provide some background to what my ultimate aim is, especially before Charlie tells me to sign up for e-smith support! (which I fully intend to do when I ascertain that the e-smith will do what my customers require)

My company provides an IT support service for local small businesses in the UK, my work ranges from network installations, hardware and software support to web site creation. These businesses predominantly have 5-20 staff (with no permanent IT staff and most with little IT knowledge) and similar numbers of PC’s, running some sort of windoze networked either peer to peer or as clients of a NT server. Most have a ISDN dial-up account with the UK main telecom provider BT, which they use for email and web site updates, web sites are hosted normally by their ISP.
Nearly all of these small businesses would dearly love to exploit the advantages that an investment in in-house systems could bring – Their problem COST, tell the managers or directors of these business that they need NT or Win2000, MS Backoffice 5-users @ £3000+ or even Backoffice Smallbusiness 5-users @£1300+ add £50 for each additional user, then they will need a machine to run this on, oh and of course each work-station will need at least Outlook loaded to get the benefits of Exchange server. And I forgot to mention that their support cost would obviously spiral – See what I mean, their eyes glaze over after the first sentence.
That brings me to e-smith, the e-smith server can be dropped almost straight into any of these businesses at a starting price, I reckon, of about £2000. The businesses get an instant productivity boost with company email and web access for all users straight out of the box. The added intranet services using I-bays can be added later.
I don’t believe there is yet a great opening in the UK for using e-smith with a direct connection (leased line) this isn’t any bad reflection on e-smith, but the high cost of a leased line connection in the UK £3-4K. ADSL is un-available to nearly all my customers (I live and work away from the big cities – lucky me) that leaves us with ISDN and my quest to get it working from within the e-smith box.

I chose to use the AVM Fritz PCI (BT Speedway) card in this venture for three reason, firstly it’s this card that BT (UK telecom provider) ships for use with their ISDN package , secondly Klaus Mueller had got this card working in his How To instruction and thirdly I have this card in another dual boot system using Red Hat 7 and connecting over ISDN with no problems.

Well, I feel I have rambled on enough now, but I really feel if this set-up could be got working there is big market out there just waiting…



Regards, Ian Martin

[Kees Blokland]

To All:

Ian, I share all your sentiments about being able to suport and entice customers..
Without ISDN it's a no-go. For home use I do use a separate router, but for 'outside' I do need to have isdn going.

Just finished building a spare box with an AVM-A1 card...
To make it short(is), I did all the things mentioned by All The Good Guys, and do get nowhere either, which means the card is there, Hisax drivers etc all ok.
ISDNCRTL does say some nice things, but as soon as I try to dial I get a No Dialtone etc ( whih just means that someting is wrong, NOTHING to do with the dialtone!)  

Since, like yourself, I'm only learning about this, I'm not able to provide real answers.

My feeling says that we should be using a ipppd 'device'
My router works like that. (and very well too)
 
In the past I tried using the isdn card in 'modem' emulation, but 'maybe?' BT does not support that ? Speaking here without knowing/understanding what I talk about..

I found this link:

http://www.wurtel.demon.nl/i4l-howto-uk.html

and I'm trying to implement that bit.

Because it's raining ( again) all the kids are surfing, so I have no chance to pull the plug to try things out this afternoon.

Some of the log bits:

Apr 22 11:08:00 www diald[698]: Calling site 0.0.0.0
Apr 22 11:08:01 www chat[1456]: abort on (BUSY)
Apr 22 11:08:01 www chat[1456]: abort on (ERROR)
Apr 22 11:08:01 www chat[1456]: abort on (NO CARRIER)
Apr 22 11:08:01 www chat[1456]: abort on (NO DIALTONE)
Apr 22 11:08:01 www chat[1456]: abort on (Invalid Login)
Apr 22 11:08:01 www chat[1456]: abort on (Login incorrect)
Apr 22 11:08:01 www chat[1456]: report (CONNECT)
Apr 22 11:08:01 www chat[1456]: send (ATZ&E0766921^M)
Apr 22 11:08:01 www chat[1456]: expect (OK)
Apr 22 11:08:01 www chat[1456]: ATZ&E0766921^M^M
Apr 22 11:08:01 www chat[1456]: OK
Apr 22 11:08:01 www chat[1456]:  -- got it
Apr 22 11:08:01 www chat[1456]: send (AT^M)
Apr 22 11:08:01 www chat[1456]: expect (OK)
Apr 22 11:08:01 www chat[1456]: ^M
Apr 22 11:08:01 www chat[1456]: AT^M^M
Apr 22 11:08:01 www chat[1456]: OK
Apr 22 11:08:01 www chat[1456]:  -- got it
Apr 22 11:08:01 www chat[1456]: send (ATDT08007317964^M)
Apr 22 11:08:02 www chat[1456]: expect (CONNECT)
Apr 22 11:08:02 www chat[1456]: ^M
Apr 22 11:08:09 www last message repeated 4 times
Apr 22 11:08:09 www chat[1456]: ATDT08007317964^M^M
Apr 22 11:08:09 www chat[1456]: BUSY
Apr 22 11:08:09 www chat[1456]:  -- failed
Apr 22 11:08:09 www chat[1456]: Failed (BUSY)
Apr 22 11:08:09 www diald[698]: Connect script failed.

Here I tried modifying the dialstring, and MSN/EAZ
Looks like it does not care too much at this stage about what is in the MSN
as long as there is some number..
In another attempt with an external TA, I got as far as getting a link setup, but the reported string was not 'connect', but '64000 HDLC...PPP'
So, i thought I'd look for that bit coming back...


Apr 22 14:57:53 www diald[698]: Calling site 0.0.0.0
Apr 22 14:57:54 www chat[2117]: abort on (BUSY)
Apr 22 14:57:54 www chat[2117]: abort on (ERROR)
Apr 22 14:57:54 www chat[2117]: abort on (NO CARRIER)
Apr 22 14:57:54 www chat[2117]: abort on (NO DIALTONE)
Apr 22 14:57:54 www chat[2117]: abort on (Invalid Login)
Apr 22 14:57:54 www chat[2117]: abort on (Login incorrect)
Apr 22 14:57:54 www chat[2117]: send (ATZ&E7666921^M)
Apr 22 14:57:54 www chat[2117]: expect (OK)
Apr 22 14:57:54 www chat[2117]: ATZ&E7666921^M^M
Apr 22 14:57:54 www chat[2117]: OK
Apr 22 14:57:54 www chat[2117]:  -- got it
Apr 22 14:57:54 www chat[2117]: send (AT^M)
Apr 22 14:57:54 www chat[2117]: expect (OK)
Apr 22 14:57:54 www chat[2117]: ^M
Apr 22 14:57:54 www chat[2117]: AT^M^M
Apr 22 14:57:54 www chat[2117]: OK
Apr 22 14:57:54 www chat[2117]:  -- got it
Apr 22 14:57:54 www chat[2117]: send (ATD08007317964^M)
Apr 22 14:57:54 www chat[2117]: expect (PPP)
Apr 22 14:57:54 www chat[2117]: ^M
Apr 22 14:58:01 www chat[2117]: ATD08007317964^M^M
Apr 22 14:58:01 www chat[2117]: BUSY
Apr 22 14:58:01 www chat[2117]:  -- failed
Apr 22 14:58:01 www chat[2117]: Failed (BUSY)
Apr 22 14:58:01 www diald[698]: Connect script failed.

Any thoughts ??

[guestFF]

Hi Kees,

Try to enter your MSN in the reset string (20reset)

'' 'ATZ&Exxxxxx' instead of '' 'ATZ'

Maybe it helps.

Regards,

HFW

[Ian Martin]

Thanks again Guys for all of your suggestions, we will get there in the end I'm sure. I have been trying a few things over the weekend trying to load up ippd on the e-smith server without breaking anything, unfortunately I did and am now going through a reload and reconfigure, aaaahhh!

The fact is (To.Charlie and all the guys at e-smith) the same AVM Fritz PCI card works perfectly on my dual boot RH7 PC, I presume using ippd?. How about you clever e-smith guys enabling this with the e-smith server please It would be a boon to all of us over the water and would make e-smith a great interface.
And putting it bluntly, no disrespect intended here, If I cannot get this implementation to work with e-smith I will turn to building the systems I need using Red Hat 7 only.

In the mean time you all might like to take a look at the email I have received from Klaus J Mueller (the writer of the How To)

Regards All,
Ian Martin

snip...

Hi Ian,

got it.

I just tested several ISPs for their interoperability with
isdn4es. The result:
Only very few (of the german ISPs that I tested) do work.

The ones that do work:
planet-interkom (010900191799)
msn (0192658)
claranet (010880193094100)

The ones that I tested that did not work:
t-online (0191011)
callando,callero (019256190)
freenet (0101901929)
yello (010230191819)
drillisch (0100500192134)
argon (01925892)

Have a guess on the message I get with all of these?

...yepp! "NO CARRIER"


-> More than likely the ISP you're trying to use does not
support this mode!

--> can you switch to a different provider?

or else:

--> tell e-smith that you are impatiently waiting for the
"real isdn support in e-smith"

You might know of the two different modes for using
isdn-devices - the one I'm descring is the modem emulation;
that's really simple to implement (as you could see), but
it definitely has some draw-backs (now I even know another).

With the other one, you use your isdn-card as a network device.
This gives you a number of advantages (multilink...).

I already suggested to implement this in e-smith...talks
are on the way...their pressure seems not too hard yet, though...

Regards, K.