I use kannel:
Kannel bearerbox version `1.4.1'. Build `Oct 16 2006 10:48:53', compiler
`4.1.1 20060525 (Red Hat 4.1.1-1)'. System Linux, release
2.6.19-1.2288.2.4.fc5, version #1 SMP Sun Mar 4 15:57:52 EST 2007,
machine x86_64. Hostname h8.dbweb.ee, IP 217.159.233.174. Libxml version
2.6.23.
Iain,
The store is not used for DLR's, just for messages. Thats why you
don't see them in the store-status. I use PostgreSQL to store my
DLRs, then I can look them up easily to see what's outstanding.
Your error looks like the web-server that you are sending the DLRs to
is not responding
ci3-software-1 = 1301
---
Margusja
+37251780
skype: margusja
msn: [EMAIL PROTECTED]
homepage: http://margusja.pri.ee
Margusja wrote:
I use kannel:
Kannel bearerbox version `1.4.1'. Build `Oct 16 2006 10:48:53', compiler
`4.1.1 20060525 (Red Hat 4.1.1-1)'. System Linux, release
If you compiled from source, AFAIK Kannel does not install a startup
script. You have to make yours or Google it from somewhere.
Regards,
Alejandro.
On 3/25/07, Piyush shingala [EMAIL PROTECTED] wrote:
Hello Friends,
I am using CentOS 4 and I tried to install Kannel it was successful but not
Hi all,
I'm having problems in getting the latest CVS to run on CentOS 4.4. It
compiles and runs OK, but when I try sending a message from the
sendsms HTTP interface, the message gets sent but the HTTP connection
doesn't return nor displays anything on the browser. It just get stuck
there.
Hi -- when doing an MT push, I want to force the SMSC I want messages to
go out on, regardless of what the handset's prefix happens to be.
However, it doesn't seem to work -- messages just go out on a random
SMSC, even when I include a smsc= value in the MT push URL.
We're recently suffering the
Diego,
You must set two almost identical configurations, except for the port
and receive-port settings, and smsc-id.
For example, if your operator directs you to use port 1234:
#TX Link
...
smsc-id = myconn-tx
allowed-smsc-id = myconn
port = 1234
receive-port = 0
...
#RX Link
...
smsc-id =
