Hi
You can use vwdial config option to have it search for the modem and
test some basic init-strings.
use
# wvdialconf wvdial.conf
It will scan all available ports/speeds and will try to fecth a basic
config. With
the info gathered, you can test a manual connection with minicom and
if it works go and configure kannel.
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, Jun 23, 2010 at 10:20 AM, Milan P. Stanic <m...@arvanta.net> wrote:
> [ A: Because it messes up the order in which people normally read text.
> Q: Why is top-posting such a bad thing? ]
>
> On Wed, 2010-06-23 at 16:52, Helge Wiemann wrote:
>> My kannel.conf looks like this:
>>
>> group = smsc
>> smsc = at
>> modemtype = wavecom
>> device = /dev/ttyUSB0
>> speed = 9600
>> pin = mypin
>>
>> group = modems
>> id = wavecom
>> name = "Wavecom WM0D2"
>> detect-string = "Wavecom"
>> detect-string2 = "WM0D2"
>> need-sleep = true
>>
>> What might by the problem?
>>
>> Now I am getting a:
>>
>> 2010-06-23 16:51:42 [6610] [0] DEBUG: AT2[/dev/ttyUSB0]: start called
>> 2010-06-23 16:51:42 [6610] [14] DEBUG: Thread 14
>> (gw/bearerbox.c:wdp_router) maps to pid 6610.
>> 2010-06-23 16:51:42 [6610] [12] DEBUG: Thread 12
>> (gw/bb_boxc.c:wdp_to_wapboxes) maps to pid 6610.
>> 2010-06-23 16:51:42 [6610] [6] DEBUG: AT2[/dev/ttyUSB0]: device opened.
>> Telnet mode = 0
>> 2010-06-23 16:51:43 [6610] [6] DEBUG: AT2[/dev/ttyUSB0]: device opened
>> 2010-06-23 16:51:43 [6610] [6] INFO: AT2[/dev/ttyUSB0]: Logging in
>> 2010-06-23 16:51:43 [6610] [6] INFO: AT2[/dev/ttyUSB0]: init device
>> 2010-06-23 16:51:43 [6610] [6] INFO: AT2[/dev/ttyUSB0]: speed set to 9600
>> 2010-06-23 16:51:43 [6610] [6] DEBUG: AT2[/dev/ttyUSB0]: --> ATZ^M
>> 2010-06-23 16:51:47 [6610] [6] ERROR: AT2[/dev/ttyUSB0]: Wrong or no
>> answer to ATZ, ignoring
>
> Looks like your modem is not connected.
>
>> 2010-06-23 16:51:47 [6610] [6] DEBUG: AT2[/dev/ttyUSB0]: --> AT^M
>> 2010-06-23 16:51:51 [6610] [6] ERROR: AT2[/dev/ttyUSB0]: Wrong or no
>> answer to AT. Trying again
>> 2010-06-23 16:51:51 [6610] [6] DEBUG: AT2[/dev/ttyUSB0]: --> AT^M
>
> Try to connect to modem with minicom and issue some commands to see if
> it works.
>
> --
> Kind regards, Milan
> --------------------------------------------------
> Arvanta, IT Security http://www.arvanta.net
> Please do not send me e-mail containing HTML code.
>
>
