Do you mean concurrent connections of the same user?
That is by design.
== Rene
From: users-boun...@kannel.org [mailto:users-boun...@kannel.org] On Behalf
Of Mike Nwaogu
Sent: Sunday, 01 April, 2012 01:02
To: users@kannel.org
Subject: Multiple concurrent client connections
I'm
Dears,
I faced problem kannel 1.5.0 in the tariff code; I connect with the USA
operator with the SMPP protocol so I have a TLV parameter for the tariff code
(0x1401) the following my TLV configuration:
group = smpp-tlv
name = TLV-name
tag = 0x1401
type = octetstring
length = 20
smsc-id =
Hi,
I searched the list for incorrect Dlr mapping and found some of the threads
discussing what was close to our issue, but that was with CIMD and other smsc
types not with SMPP. Hence I ask the following:
Bearerbox puts 13 as the 'ts' field value which is also found in the Sent Sms
entry in
can you please check?
ta
Hi,
you have to send metadata in your request that include tlv name. Please check
metadata section in userguide.
Thanks,
Alex
Am 01.04.2012 um 12:55 schrieb Michael Farouk:
Dears,
I faced problem kannel 1.5.0 in the tariff code; I connect with the USA
operator with the SMPP protocol so
Hi,
cyrillic can only be send with ucs2 therefore coding=2.
Kannel behavior for coding=2 and 3 is simple: don't touch it it's binary and up
to user to encode it BUT
if you need that kannel converts some charset to ucs2 for you then just use two
params:
charset=YOUR_CHARSET
Exactly what I've said :)
If your source text is in utf8 you need to specify charset=utf8 and
coding=2.
2012/4/2 Alexander Malysh amal...@kannel.org
Hi,
cyrillic can only be send with ucs2 therefore coding=2.
Kannel behavior for coding=2 and 3 is simple: don't touch it it's binary
and up
Then I don't understand what should be the issue here :-) ?
Thanks,
Alex
Am 01.04.2012 um 23:15 schrieb spameden:
Exactly what I've said :)
If your source text is in utf8 you need to specify charset=utf8 and coding=2.
2012/4/2 Alexander Malysh amal...@kannel.org
Hi,
cyrillic can only
I think Chad was referring to But the important thing is that it has no
relevance to the data_coding that gets sent over SMPP to the coding
specified in the SMPP message... I've just checked in kannel smpp logs it
sets data_coding: 8 = 0x0008 when coding=2 specified.
2012/4/2 Alexander Malysh
That sentence was about the charset parameter (not coding). The charset
parameter has no effect on data_coding integer.
Only the coding can effect it, but its effects are quite limited. SMPP has
several encodings in the spec (listed in my first email) but coding 0,1,2
can only set data_coding
Correct, sir. Also had this problem when was testing out kannel's
functionality for non-english symbols. (i.e. if you don't set charset=utf8
you'd get bollocks on your phone instead).
Would be good if this moment could be covered in kannel's user guide.
About coding=3, yes you're right coding=3
About coding=3, yes you're right coding=3 stands for LATIN1 in SMPP v3.4
documentation. But coding=0 defines SMSC Default Alphabet.
So the question is is LATIN1 encoding the same as 'SMSC Default
Alphabet' ? And what is SMSC Default Alphabet actually ? (Most likely
its a LATIN1 aka ISO8859-1
12 matches
Mail list logo
