> On 08 Oct 2015, at 14:04, Hillel wrote:
>
> Hi Alex and Andreas,
>
> Vodacom says send Latin-1 characters and set your data_coding field to 3 to
> tell the SMSC to translate the characters from Latin-1 to GSM. So that if we
> want to display the curly bracket ‘}’ you have to send the escape
aign=whitepapers%20and%20guides>
From: devel [mailto:devel-boun...@kannel.org] On Behalf Of
hbil...@ecommunicate.biz
Sent: 08 October 2015 14:06
To: amal...@kannel.org; af...@list.fink.org
Cc: devel@kannel.org
Subject: Re: patch to allow data_coding to be set to 3
Importance: High
Hi Alex and An
Hi Alex and Andreas,
Vodacom says send Latin-1 characters and set your data_coding field to 3 to
tell the SMSC to translate the characters from Latin-1 to GSM. So that if we
want to display the curly bracket '}' you have to send the escape character
and the round bracket character: ESC + ) Dat
Hi Hillel,
I have to agree to Andreas. You don’t need any special data coding because
Kannel will do the whole
convert magic to GSM for you.
Alex
> Am 07.10.2015 um 15:24 schrieb Andreas Fink :
>
> theres no need for having the SMSC do the latin1 to GSM transcoding as kannel
> already does th
Hi Andreas,
Thanks for the quick response.
Even if i use utf8 charset then also all special characters allowed by GSM
7 are not getting sent properly.
I am url encoding everything before sending as per kannel document.
Can you suggest me how to send all GSM7 allowed special characters properly.
theres no need for having the SMSC do the latin1 to GSM transcoding as kannel
already does this.
you feed kannel with latin1 or utf8 and kannel will make GSM out of it
automatically.
What matters at the end is what the handset receives and the GSM character set
is hardcoded in billions of phone
