Hey everyone...I'm having a bit of an issue using kannel to connect to multiple SMSCs.
I have 3 SMPP connections, and 1 CIMD2 connection. They're in my kannel as:
include smppConnect1.conf
include cimd2connect1.conf
include smppConnect2.conf
include smppConnect3.conf
When I start
hey guys, I must be doing something silly in my kannel use/config. However, this is
what happens:
When I send from a handset to my operator assigned shortcode the character @, it
comes to kannel and I see the message in the kannel.log debug output as being of hex
value '00'. When it reaches
(and a Latin-GSM conversion when sending TO the
SMSC) and thus the double conversion.
Is there a way to tell kannel not to do that conversion? I'm using 1.3.1 development
version.
Many thanks,
Bryce
-Original Message-
From: Bryce Pasechnik
Sent: Wed 10/1
Hey everyone, I posted a message regarding this awhile ago, but didn't understand
enough at the time to properly formulate my question.
The problem is this, a number of the SMSC's we're connected to send us data in
different character sets. Sometime it is the latin iso standard character set,
Hey Everyone,
Using kannel, I'm connected to a tanla solutions SMSC via SMPP3.4.
I'm encountering a possible character set issue. When users send a message to us with
an '_' (underscore) character in it, it arrives as a different character. (a wierd
ascii character that looks a blurry S).
I noticed a really interesting problem when using Kannel hooked up to an operator
using an SMPP3.4 server.
When the send_enquire_link interval was set to 5 seconds, I noticed in the kannel logs
that it did indeed send the keepalive. However, only the first keepalive request
received a
I have several SMSC groups in my kannel.conf, one for each smsc I connect to. At run
time, if any SMSC connection disapears, it patiently tries to reconnect.
If one of the connections is unavailable at load time, however, it will not load!
Is there a way to get kannel to load, and just
