Topic: modems

[Gary]

I'm trying to put a modem onto my linux box so that I can use it to dial up my ISP.

I have an external modem but can't get SME to recognise it at all.

Will sme work with a pci modem (connexant chipset)?

Gary

[Del]

Hi Gary,
What modem have you got? I have used US Robotics and Hayes Accura modems no problem. I believe that most PCI modems will not work, of course if they have jumpers on to select com 3 or com 4 etc then they may well be OK. I have a ISA modem with the said jumpers and it works fine on SME5.5
Hope this helps,
Del

[dave]

I am surprised sme doesn't recognize your external modem.  If you have an isa modem I would try that.  I don't know of any pci modems that are not winmodems.  Try going to linmodems.org and find a driver for your pci modem.
good luck,
dave

[Gary]

I'm not entirely sure what my external modem is. It seems to have no label on it although it has a common chipset inside. I can't remember but I'm pretty sure it's Connexant.

I plug it in and try to get SME to dial my ISP and nothing happens. A couple of lights flicker but nothing happens. I assume that SME 5.6 is incapable of using it.

Gary

[Steven]

Can you get this modem to work on windows?
If you do a listing to it does it respond? ls- l >/ttyS0 or whatever port
After the last two prove successful go in to minicom and type
atdt#######
###### being the telephone number and atdt being tone dialing - use atdp for pulse

Let us know what happens

Steven

[Gary]

No joy. You can see why I called it billgates, can't you!

login as: root
root@billgates's password:
Last login: Fri Jun 27 21:20:24 2003 from pc-00012
Welcome to the Mitel Networks SME Server.
[root@billgates root]#  ls- l >/ttyS0
bash: ls-: command not found
[root@billgates root]# ls -1
anaconda-ks.cfg
install.log
install.log.syslog
[root@billgates root]# ls -1 >/ttys0
[root@billgates root]# atdt
bash: atdt: command not found
[root@billgates root]# atdt08089916001
bash: atdt08089916001: command not found
[root@billgates root]#

[Terry]

yah, but did you go into minicom and try to talk to the modem directly from there? From a command prompt type minicom and see what happens.

[Gary]

This is much more interesting. ls -1>/ttys0 doesn't seem to do anything though.
I seem to be getting "no dialtone". That would indicate a line fault or a message on the answering machine. Neither of which is seems to be the source (I use the same cables with my Windows machine) and there were no messages waiting.

I'm not really sure how to go about using the modem on my Windows machine since I already have an ISA modem built in (don't really fancy moving the piles of stuff resting on top of and against my windows machine). My Windows machine probably wouldn't have the right drivers (it runs NT)

It seems like a configuration problem. I'm using a standard BT phoneline.


Welcome to minicom 2.00.0

OPTIONS: History Buffer, F-key Macros, Search History Buffer, I18n
Compiled on Feb 26 2002, 09:38:06.

Press CTRL-A Z for help on special keys

AT S7=45 S0=0 L1 V1 X4 &c1 E1 Q0
OK
atdt08089916001
NO DIALTONE
atdt08089916001
NO DIALTONE
ls -1>/ttys0

[Charlie Brady]

Gary wrote:

> I seem to be getting "no dialtone".

Try "X3" as init string. If that fails, check that the phone line is plugged into the modem

Charlie

[Steven]

If your modem doesn't respond, them either you have it on another port, or the modem/cable/port if faulty
try ls -l >/dev/ttyS1/2/3/4
if nothing happens, change to another port and try again from 0
if nothing again thing you need to replace the cable then if nothing try borrow a modem from someone and test with that.

Steven

[Gary]

I'm not sure how to pass X3 and an init. How do I do that?

I've had a bash but I'm not sure I'm getting it right. This ls -l> business. Is the -l a -L or a -one?

login as: root
root@billgates's password:
Last login: Tue Jul  1 20:41:00 2003 from pc-00012
Welcome to the Mitel Networks SME Server.
[root@billgates root]# minicom
Device /dev/ttyS1 lock failed: Operation not permitted.
[root@billgates root]# ls -l>/ttys0
[root@billgates root]# minicom

Welcome to minicom 2.00.0

OPTIONS: History Buffer, F-key Macros, Search History Buffer, I18n
Compiled on Feb 26 2002, 09:38:06.

Press CTRL-A Z for help on special keys

AT S7=45 S0=0 L1 V1 X4 &c1 E1 Q0
OK
ls -l>/ttys1












 CTRL-A Z for help | 38400 8N1 | NOR | Minicom 2.00.0 | VT102 |      Offline
[root@billgates root]# minicom
Device /dev/ttyS1 lock failed: Operation not permitted.
[root@billgates root]# minicom

Welcome to minicom 2.00.0

OPTIONS: History Buffer, F-key Macros, Search History Buffer, I18n
Compiled on Feb 26 2002, 09:38:06.

Press CTRL-A Z for help on special keys

AT S7=45 S0=0 L1 V1 X4 &c1 E1 Q0
OK
opjopjo












 CTRL-A Z for help | 38400 8N1 | NOR | Minicom 2.00.0 | VT102 |      Offline
[root@billgates root]# init
Usage: init 0123456SsQqAaBbCcUu
[root@billgates root]# init x3
Usage: init 0123456SsQqAaBbCcUu
[root@billgates root]# minicom

Welcome to minicom 2.00.0

OPTIONS: History Buffer, F-key Macros, Search History Buffer, I18n
Compiled on Feb 26 2002, 09:38:06.

Press CTRL-A Z for help on special keys

AT S7=45 S0=0 L1 V1 X4 &c1 E1 Q0
OK
AT S7=45 S0=0 L1 V1 X4 &c1 E1 Q0
OK











 CTRL-A Z for help | 38400 8N1 | NOR | Minicom 2.00.0 | VT102 |      Offline
[root@billgates root]# ls
anaconda-ks.cfg  install.log  install.log.syslog
[root@billgates root]# ls -l
total 92
-rw-r--r--    1 root     root          997 Apr 17 19:27 anaconda-ks.cfg
-rw-r--r--    1 root     root        11658 Apr 17 19:26 install.log
-rw-r--r--    1 root     root        73728 Apr 17 19:27 install.log.syslog
[root@billgates root]# ls -l>/dev/ttys1/2/3/4
bash: /dev/ttys1/2/3/4: Not a directory
[root@billgates root]# ls -l>/dev/ttys1
bash: /dev/ttys1: Input/output error
[root@billgates root]# ls -l>/dev/ttys0
bash: /dev/ttys0: Input/output error
[root@billgates root]# ls -l>/dev/ttys2
bash: /dev/ttys2: Input/output error
[root@billgates root]# ls -l>/dev/ttys3
bash: /dev/ttys3: Input/output error
[root@billgates root]# ls -l>/dev/ttys4
bash: /dev/ttys4: Input/output error
[root@billgates root]# ls -1>/dev/ttys0
bash: /dev/ttys0: Input/output error
[root@billgates root]# ls -l>ttys0
[root@billgates root]# ls -l>ttys1
[root@billgates root]# ls -1>ttys0
[root@billgates root]# shutdown now -h

Broadcast message from root (pts/0) (Wed Jul  2 14:47:26 2003):

The system is going down for system halt NOW!
[root@billgates root]#

[Dave Liquorice]

I'm not sure why you are messing about trying to redirect the consoll when you have minicom working and talking to the modem.

The

> AT S7=45 S0=0 L1 V1 X4 &c1 E1 Q0
> OK

Sequence shows that minimcom is sending data to the modem (the top sequence) and the modem is seeing it and interpreting correctly (the OK).

A while back you had tried atdt in minicom and got back "NO DIALTONE". You need to find out why the modem isn't detecting dialtone. Possibilties are:

1) Not plugged into a working phone line. Check with a known working telephone into the same socket that you are connecting the modem.

2) Duff cable between socket and modem. If you can do a contiinuity check for each pin that  is the best. Each one should only appear at one pin at the other end.

3) Using a cable from a different modem, instead of the one supplied with the modem. Some modems  expect the line to appear on the inner most pair of contacts, others on the next out pair.  Cables are thus wired accordingly depending on what the modem expects. There is no indication of the cable how it is wired. You'll have to test it out to find out.

4) Modem settings. It is possible to set a modem to "blind dial" but I doubt that will help 'cause if you haven't got dialtone there is little point in dialling...

Cheers
Dave.

[Charlie Brady]

Dave Liquorice wrote:

> 4) Modem settings. It is possible to set a modem to "blind
> dial" but I doubt that will help 'cause if you haven't got
> dialtone there is little point in dialling...

Blind dialling *can* help, if there is dialtone, but the modem doesn't recognise it.  [Enter "X3" via the console configuration wizard.]

Charlie

[Steven]

I think we need to start again from the beginning
Get a telephone - plug the cable from the back of the modem into the phone - do you get a dial tone? If yes then carry on, otherwise your line is faulty
From the prompt type ls -l >/ttyS0/1/2 - which one makes the lights flash?
In minicom Press CTRL+A then O - go down to serial port setup - does the serial device match which ttyS you ls -l'd to?
If not I would swap com ports - changing the port in the software i find doesn't always work - so swap it physically and list to the port stated in minicom until you find the right port
Once that is done go into minicom type atdt########
if it comes up with no dialtone then type atdtx3#######
This should now dial.

Let us know if it works

Steven

[Dave Liquorice]

> I think we need to start again from the beginning

Lets see what response we get to the 4 points I mentioned earlier... It's gone very quiet so prehaps Gary is too embarrassed to say what the problem was.  B-)

>  Get a telephone - plug the cable from the back of the modem into
> the phone - do you get a dial tone?

Not 100% fool proof in the UK. See my  point 3. Indeed it may well add to the confusion depending on the wiring of the phone and modem. *If* they are the same all well and good but you have no way of telling  what the wiring of either is by simply looking at the cable or socket.

He has got the right port as lights flash and he gets back OK responses in minicom. I suspect it is either a duff socket on the wall,   a broken cable or the wrong sort of cable for the modem.

A long time ago (>15years) some modems, of US orgin, wouldn't recognise UK dialtone. But it wasn't very many and I haven't come across that for years and years.

Cheers
Dave.