ea what is the
problem.. log-level = 0 might help.
I found few case that SMS failed to be sent, becoz traffic jam from
cellphone provider.
> and could not be send out. Is there anything to do with the config file or the
> initialization of my gsm modem?
>
>
>
> >
>
Hi Thom,
I think you should include your kannel config. It will help to analyze
the problem.
On Sat, 2004-01-31 at 13:13, [EMAIL PROTECTED] wrote:
> Hi Guys,
>
> Been testing kannel for few weeks. It has been a great s/w but i got 2 problems.
> I'm using a iTegno gsm modem as the smsc.
>
>
On Sun, 2004-01-04 at 04:28, Thomas Bolioli wrote:
> I am new to SMS and I am looking for something very specific but I do
> not know what terminology to use to google for it. Also, Kannel may do
> what I need, I am just not sure. Anyhow, I just moved from sprint to
> t-mobile and I have a servi
I believe it much more safer to use group-based access permission. E.g:
# chown .kannel /dev/ttyS0
# chmod ug+rw,o-rwx /dev/ttyS0
If you use Debian default installation, then device file /dev/ttyS0 will
be owned by 'uucp' group. You can easily set your kannel user to be in
'uucp' group, in order
I jz look into 1.2.1 version. And it has exact code that running into my
last bug (buffer bug). If you want to keep using 1.2.1 you could try to
modify gw/smsc/smsc_at2.c. Replace 3 functions in that files (Below, I
copy&paste those 3 functions from cvs-version..), and recompile them.
On Mon, 2003
Hi,
I try to use iTegno 3000/WM1080A as virtual SMSC in Kannel.
Apparently it can't send SMS more than 19 chars. When I used another
application (gsmlib, http://www.pxh.de/fs/gsmlib/download/), it was
successfully send SMS at any length of chars.
I try to trace the problem using minicom, and retyp