Seems your modem is not correctly connected to the kannel box

as is a serial modem, it shouldn't be a driver issue like if it was a
usb modem. The only thing mitght be the cable or your modem does not
support serial connections...

have you tried in another machine? windows/linux?


|-----------------------------------------------------------------------------------------------------------------|
Envíe y Reciba Datos y mensajes de Texto (SMS) hacia y desde cualquier
celular y Nextel
en el Perú, México y en mas de 180 paises. Use aplicaciones 2 vias via
SMS y GPRS online
              Visitenos en www.perusms.NET www.smsglobal.com.mx y
www.pravcom.com



On Wed, Feb 16, 2011 at 5:18 PM, becoco <[email protected]> wrote:
> Hi,
> with NULL MODEL cable ( not "crossover' ;-) )
>
> root@work1:/home/mickael# wvdialconf
> Editing `/etc/wvdial.conf'.
>
> Scanning your serial ports for a modem.
>
> ttyS0<*1>: ATQ0 V1 E1 -- failed with 2400 baud, next try: 9600 baud
> ttyS0<*1>: ATQ0 V1 E1 -- failed with 9600 baud, next try: 115200 baud
> ttyS0<*1>: ATQ0 V1 E1 -- and failed too at 115200, giving up.
> Modem Port Scan<*1>: S1   S2   S3
>
>
> Sorry, no modem was detected!  Is it in use by another program?
> Did you configure it properly with setserial?
>
> Please read the FAQ at http://open.nit.ca/wiki/?WvDial
>
> If you still have problems, send mail to <[email protected]>.
> root@work1:/home/mickael#
>
> Mickael
>
>
> 2011/2/16 Alvaro Cornejo <[email protected]>
>>
>> Did you test  wvdialconf commad what did you got?
>>
>> Are you talking about an ethernet crossover cable? you should use a
>> NULL MODEM cable since it is a serial device.
>>
>> Regards
>>
>> Alvaro
>>
>> |-----------------------------------------------------------------------------------------------------------------|
>> Envíe y Reciba Datos y mensajes de Texto (SMS) hacia y desde cualquier
>> celular y Nextel
>> en el Perú, México y en mas de 180 paises. Use aplicaciones 2 vias via
>> SMS y GPRS online
>>               Visitenos en www.perusms.NET www.smsglobal.com.mx y
>> www.pravcom.com
>>
>>
>>
>> On Wed, Feb 16, 2011 at 12:34 PM, becoco <[email protected]> wrote:
>> > Hello,
>> > I tried to a crosserover cable... does not functions them :-(
>> >
>> > 2011/2/15 Alvaro Cornejo <[email protected]>
>> >>
>> >> Hi
>> >>
>> >> try with
>> >>
>> >> # wvdialconfig
>> >>
>> >> This will search for all active ports and test different speeds. If it
>> >> does not found anything, it might be a problem with the cable or the
>> >> modem itself.
>> >>
>> >> Hope helps
>> >>
>> >> Alvaro
>> >>
>> >>
>> >> |-----------------------------------------------------------------------------------------------------------------|
>> >> Envíe y Reciba Datos y mensajes de Texto (SMS) hacia y desde cualquier
>> >> celular y Nextel
>> >> en el Perú, México y en mas de 180 paises. Use aplicaciones 2 vias via
>> >> SMS y GPRS online
>> >>               Visitenos en www.perusms.NET www.smsglobal.com.mx y
>> >> www.pravcom.com
>> >>
>> >>
>> >>
>> >> On Tue, Feb 15, 2011 at 4:31 PM, becoco <[email protected]> wrote:
>> >> > Hello Alvaro,
>> >> >
>> >> > With ttyS1 | ttyS2 | ttsyS3 i have:
>> >> >
>> >> > 2011-02-15 17:52:00 [2495] [6] INFO: AT2[/dev/ttyS1]: trying to use
>> >> > speed
>> >> > <9600> from modem definition
>> >> > 2011-02-15 17:52:00 [2495] [6] INFO: AT2[/dev/ttyS1]: opening device
>> >> > 2011-02-15 17:52:00 [2495] [6] DEBUG: AT2[/dev/ttyS1]: device opened.
>> >> > Telnet
>> >> > mode = 0
>> >> > 2011-02-15 17:52:00 [2495] [6] ERROR: AT2[/dev/ttyS1]: at_data_link:
>> >> > fail to
>> >> > set termios attribute
>> >> > 2011-02-15 17:52:00 [2495] [6] ERROR: System error 5: Input/output
>> >> > error
>> >> > 2011-02-15 17:52:00 [2495] [6] DEBUG: AT2[/dev/ttyS1]: device opened
>> >> > 2011-02-15 17:52:00 [2495] [6] ERROR: AT2[/dev/ttyS1]: at_data_link:
>> >> > fail to
>> >> > set termios attribute
>> >> > 2011-02-15 17:52:00 [2495] [6] ERROR: System error 5: Input/output
>> >> > error
>> >> > 2011-02-15 17:52:00 [2495] [6] INFO: AT2[/dev/ttyS1]: speed set to
>> >> > 9600
>> >> > 2011-02-15 17:52:00 [2495] [6] DEBUG: AT2[/dev/ttyS1]: --> ^M
>> >> > 2011-02-15 17:52:00 [2495] [6] ERROR: AT2[/dev/ttyS1]: Couldnot write
>> >> > to
>> >> > device.
>> >> > 2011-02-15 17:52:00 [2495] [6] ERROR: System error 5: Input/output
>> >> > error
>> >> >
>> >> > so I think it ttyS0, the motherboard has more than 1 port R232...
>> >> >
>> >> > My cable is new... I buy a cable DB9 type "extension" (female side
>> >> > motherboard, Nokia male side) it's correct ??
>> >> >
>> >> > Mickael
>> >> >
>> >> > 2011/2/15 Alvaro Cornejo <[email protected]>
>> >> >>
>> >> >> There is no answer from the modem to kannel... maybe your modem is
>> >> >> connected to a port different from /dev/ttyS0... or you are using
>> >> >> the
>> >> >> wrong cable...
>> >> >>
>> >> >> Also try with different speeds or use wvdial to find out the correct
>> >> >> port
>> >> >> config
>> >> >>
>> >> >> Regards
>> >> >>
>> >> >>
>> >> >>
>> >> >>
>> >> >> |-----------------------------------------------------------------------------------------------------------------|
>> >> >> Envíe y Reciba Datos y mensajes de Texto (SMS) hacia y desde
>> >> >> cualquier
>> >> >> celular y Nextel
>> >> >> en el Perú, México y en mas de 180 paises. Use aplicaciones 2 vias
>> >> >> via
>> >> >> SMS y GPRS online
>> >> >>               Visitenos en www.perusms.NET www.smsglobal.com.mx y
>> >> >> www.pravcom.com
>> >> >>
>> >> >>
>> >> >>
>> >> >> On Tue, Feb 15, 2011 at 12:44 PM, becoco <[email protected]> wrote:
>> >> >> > Hi all,
>> >> >> > I can not connect the Nokia 22 has kannel :-(
>> >> >> > Here's my config :
>> >> >> >
>> >> >> > # modem
>> >> >> > group = smsc
>> >> >> > smsc = at
>> >> >> > modemtype = premicell
>> >> >> > device = /dev/ttyS0
>> >> >> >
>> >> >> > group = modems
>> >> >> > id = premicell
>> >> >> > name = Premicell
>> >> >> > detect-string = "PREMICEL"
>> >> >> > no-pin = true
>> >> >> > no-smsc = true
>> >> >> >
>> >> >> > My log:
>> >> >> >
>> >> >> > 2011-02-15 17:57:57 [3040] [0] INFO:
>> >> >> > ----------------------------------------
>> >> >> > 2011-02-15 17:57:57 [3040] [0] INFO: Kannel bearerbox II version
>> >> >> > 1.4.3
>> >> >> > starting
>> >> >> > 2011-02-15 17:57:57 [3040] [0] INFO: MAIN: Start-up done, entering
>> >> >> > mainloop
>> >> >> > 2011-02-15 17:57:57 [3040] [0] DEBUG: AT2[/dev/ttyS0]: start
>> >> >> > called
>> >> >> > 2011-02-15 17:57:57 [3040] [9] DEBUG: Thread 9
>> >> >> > (gw/bb_udp.c:udp_sender)
>> >> >> > maps
>> >> >> > to pid 3040.
>> >> >> > 2011-02-15 17:57:57 [3040] [10] DEBUG: Thread 10
>> >> >> > (gw/bb_udp.c:udp_receiver)
>> >> >> > maps to pid 3040.
>> >> >> > 2011-02-15 17:57:57 [3040] [8] DEBUG: Thread 8
>> >> >> > (gw/bb_udp.c:udp_receiver)
>> >> >> > maps to pid 3040.
>> >> >> > 2011-02-15 17:57:57 [3040] [11] DEBUG: Thread 11
>> >> >> > (gw/bb_udp.c:udp_sender)
>> >> >> > maps to pid 3040.
>> >> >> > 2011-02-15 17:57:57 [3040] [7] DEBUG: Thread 7
>> >> >> > (gw/bb_smscconn.c:sms_router)
>> >> >> > maps to pid 3040.
>> >> >> > 2011-02-15 17:57:57 [3040] [12] DEBUG: Thread 12
>> >> >> > (gw/bb_boxc.c:wdp_to_wapboxes) maps to pid 3040.
>> >> >> > 2011-02-15 17:57:57 [3040] [13] DEBUG: Thread 13
>> >> >> > (gw/bb_boxc.c:wapboxc_run)
>> >> >> > maps to pid 3040.
>> >> >> > 2011-02-15 17:57:57 [3040] [14] DEBUG: Thread 14
>> >> >> > (gw/bearerbox.c:wdp_router)
>> >> >> > maps to pid 3040.
>> >> >> > 2011-02-15 17:57:57 [3040] [6] DEBUG: Thread 6
>> >> >> > (gw/smsc/smsc_at.c:at2_device_thread) maps to pid 3040.
>> >> >> > 2011-02-15 17:57:57 [3040] [6] INFO: AT2[/dev/ttyS0]: trying to
>> >> >> > use
>> >> >> > speed
>> >> >> > <9600> from modem definition
>> >> >> > 2011-02-15 17:57:57 [3040] [6] INFO: AT2[/dev/ttyS0]: opening
>> >> >> > device
>> >> >> > 2011-02-15 17:57:57 [3040] [6] DEBUG: AT2[/dev/ttyS0]: device
>> >> >> > opened.
>> >> >> > Telnet
>> >> >> > mode = 0
>> >> >> > 2011-02-15 17:57:57 [3040] [6] DEBUG: AT2[/dev/ttyS0]: device
>> >> >> > opened
>> >> >> > 2011-02-15 17:57:57 [3040] [6] INFO: AT2[/dev/ttyS0]: speed set to
>> >> >> > 9600
>> >> >> > 2011-02-15 17:57:57 [3040] [6] DEBUG: AT2[/dev/ttyS0]: --> ^M
>> >> >> > 2011-02-15 17:57:58 [3040] [13] INFO: Client connected from
>> >> >> > <127.0.0.1>
>> >> >> > 2011-02-15 17:57:58 [3040] [13] DEBUG: Started thread 15
>> >> >> > (gw/bb_boxc.c:function)
>> >> >> > 2011-02-15 17:57:58 [3040] [15] DEBUG: Thread 15
>> >> >> > (gw/bb_boxc.c:function)
>> >> >> > maps to pid 3040.
>> >> >> > 2011-02-15 17:57:58 [3040] [15] DEBUG: setting up systems for new
>> >> >> > wapbox
>> >> >> > 2011-02-15 17:57:58 [3040] [15] DEBUG: Started thread 16
>> >> >> > (gw/bb_boxc.c:boxc_sender)
>> >> >> > 2011-02-15 17:57:58 [3040] [16] DEBUG: Thread 16
>> >> >> > (gw/bb_boxc.c:boxc_sender)
>> >> >> > maps to pid 3040.
>> >> >> > 2011-02-15 17:57:58 [3040] [5] INFO: Client connected from
>> >> >> > <127.0.0.1>
>> >> >> > 2011-02-15 17:57:58 [3040] [5] DEBUG: Started thread 17
>> >> >> > (gw/bb_boxc.c:function)
>> >> >> > 2011-02-15 17:57:58 [3040] [17] DEBUG: Thread 17
>> >> >> > (gw/bb_boxc.c:function)
>> >> >> > maps to pid 3040.
>> >> >> > 2011-02-15 17:57:58 [3040] [17] DEBUG: Started thread 18
>> >> >> > (gw/bb_boxc.c:boxc_sender)
>> >> >> > 2011-02-15 17:57:58 [3040] [18] DEBUG: Thread 18
>> >> >> > (gw/bb_boxc.c:boxc_sender)
>> >> >> > maps to pid 3040.
>> >> >> > 2011-02-15 17:57:59 [3040] [2] DEBUG: HTTP: Creating HTTPClient
>> >> >> > for
>> >> >> > `192.168.1.4'.
>> >> >> > 2011-02-15 17:57:59 [3040] [2] DEBUG: HTTP: Created HTTPClient
>> >> >> > area
>> >> >> > 0x91a62f0.
>> >> >> > 2011-02-15 17:57:59 [3040] [3] DEBUG: HTTP: Resetting HTTPClient
>> >> >> > for
>> >> >> > `192.168.1.4'.
>> >> >> > 2011-02-15 17:58:59 [3040] [1] DEBUG: Timeout for fd:52 appeares.
>> >> >> > 2011-02-15 17:58:59 [3040] [1] DEBUG: HTTP: Destroying HTTPClient
>> >> >> > area
>> >> >> > 0x91a62f0.
>> >> >> >
>> >> >> >
>> >> >> > my status page:
>> >> >> >
>> >> >> > SMSC connections:
>> >> >> >     unknown    AT2[/dev/ttyS0] (connecting, rcvd 0, sent 0, failed
>> >> >> > 0,
>> >> >> > queued
>> >> >> > 0 msgs)
>> >> >> >
>> >> >> >
>> >> >> > Please help,
>> >> >> > Mickael
>> >> >
>> >> >
>> >
>> >
>
>

Reply via email to