i know udev rule is not reliable, because its executed at boot time
again,
parse the dmesg each time you start/stop kannel , reset proper simlink
and use cronted monitoring script to check the kannel state and according to
the state to use the start/stop srcipt
Dennis Low Weng Kin wrote:
Thanks for you immediate reply.
So you are saying that I should detect the device name and change the
device name in the kannel config accordingly?
I've tried to write a udev rule to map the usb port to use the port name
"/dev/GSMMODEM". It works well at first. When I unplug the modem, and
replug it in, Kannel stop working. When I restart the kannel service, I
receive a kernel failure notification. Any suggestions again?
Regards,
Low
> Date: Thu, 11 Jun 2009 10:05:41 +0300
> From: seik...@gmail.com
> CC: users@kannel.org
> Subject: Re: Unplugging USB GSM Modem and replugging
>
> the KISS solution :
> at the head of the kannel start/stop script include short bash script
to detect the latest device name of the modem
> the script should remove if existing the old simlink and create new
simlink to the real usb device named like "/dev/MyUsbModem"
> use that in the kannel config
>
>
> Dennis Low Weng Kin wrote:
> > Hi everyone,
> >
> > I am running Kannel 1.4.3 in Fedora Core 10. For the moment, I am
using
> > a USB GSM Modem and in my setting, I mapped the device to
/dev/ttyUSB0.
> > However, if I unplugged and replug the GSM Modem to my PC, the port
will
> > change to ttyUSB1. Therefore, my Kannel will not be able to locate the
> > device. Any suggestion? Or is it better to use Serial Modem?
> >
> > Regards,
> > Low
> >
> >
> >
> >
------------------------------------------------------------------------
> > See all the ways you can stay connected to friends and family
> > <http://www.microsoft.com/windows/windowslive/default.aspx>
>
------------------------------------------------------------------------
What can you do with the new Windows Live? Find out
<http://www.microsoft.com/windows/windowslive/default.aspx>
