I'll check that. Actually there's a way to automatically reconnect if
the connection fails. That's probably better. Mixing memory based and
MySQL based is not a good idea. Kannel would always have to search
the two.
mysql_ping() is used to be checking the connection and re-establish it
if it
Also I've modified delivery reports so they can optionally work with
MySQL instead of being memory based. To make this work, you got to
modify the Makefile to include the mysqlclient library and you got to
edit dlr.c to define MYSQL_DLR and to set your host's username
passwords.
shouldn't
Also I've modified delivery reports so they can optionally work with
MySQL instead of being memory based. To make this work, you got to
modify the Makefile to include the mysqlclient library and you got to
edit dlr.c to define MYSQL_DLR and to set your host's username
passwords.
Hi Andreas
Your mysql additions to bearerbox are great. We built a Q manager
that sits in front of kannel, and implemented our own delivery
additions also http callbacks) to Kannel, allthough I am now going
to swap to yours.
I had some problems using mysql they way you are. Under constant
I've found a bug in the delivery reports with EMI2.
The SMSC I'm connecting to does reply with messages containing
slashes in the dates. However the / is used to separate the text from
the URL when sent back. So I got a message that a very strange URL
could not be delivered.
I'm applyign thea
Hi Andreas
Your mysql additions to bearerbox are great. We built a Q manager that sits
in front of kannel, and implemented our own delivery additions also http
callbacks) to Kannel, allthough I am now going to swap to yours.
I had some problems using mysql they way you are. Under constant
