Hi Thomas,

I have similar problems and mine comes down to two issues. First the
/dev/ttyS0 have root.tty as owner, so the user you are trying with need to
have the right premissions. I overcome this (at this moment, because its
only a test box) by running kannel as root.
I tried this morning to reboot the box and the start kannel, but got the log
as you write here, I started minicom and tried to isue some at commands
directly to the phone modem and it responde like it should. After closing
down minicom I had no problem starting kannel. So the modem might be in a
strangs state that kannel can not get it out of (I guess its a bug).

regards

Steffen



-----Oprindelig meddelelse-----
Fra: Tampier Thomas [mailto:[EMAIL PROTECTED]] 
Sendt: 19. juni 2002 00:43
Til: [EMAIL PROTECTED]
Emne: TC-35 Startup


Hi list,

i have troubles starting my Siemens TC35. Every time i try to start the 
bearerbox i get this log (i tried all possible configurations in 
kannel.conf, its always the same) --> any ideas?

thx for your help 
Thomas

2002-06-19 00:38:30 [5] INFO:  AT2[/dev/ttyS0]: speed set to 19200
2002-06-19 00:38:30 [5] DEBUG: AT2[/dev/ttyS0]: --> ^M 
2002-06-19 00:38:32 [5] DEBUG: AT2[/dev/ttyS0]: --> AT^M 
2002-06-19 00:38:36 [5] DEBUG: AT2[/dev/ttyS0]: --> AT^M 
2002-06-19 00:38:40 [5] DEBUG: AT2[/dev/ttyS0]: -->AT^M 
2002-06-19 00:38:44 [5] INFO: AT2[/dev/ttyS0]: closing device
2002-06-19 00:38:44 [5] INFO: AT2[/dev/ttyS0]: opening device 
2002-06-19 00:38:44 [5] DEBUG: AT2[/dev/ttyS0]: device opened 
2002-06-19 00:38:44 [5] INFO: AT2[/dev/ttyS0]: speed set to 9600 
2002-06-19 00:38:44 [5] DEBUG: AT2[/dev/ttyS0]: --> ^M 
2002-06-19 00:38:46 [5] DEBUG: AT2[/dev/ttyS0]: --> AT^M 
2002-06-19 00:38:50 [5] DEBUG: AT2[/dev/ttyS0]: --> AT^M
2002-06-19 00:38:54 [5] DEBUG: AT2[/dev/ttyS0]: --> AT^M 
2002-06-19 00:38:58 [5] INFO: AT2[/dev/ttyS0]: closing device 
2002-06-19 00:38:58 [5] INFO: AT2[/dev/ttyS0]: cannot detect speed
2002-06-19 00:38:58 [5] DEBUG: Thread 5 (gw/smsc_at2.c:at2_device_thread) 
terminates.                                              



Reply via email to