Re: Picking esme in round robin or randomly for dlr in Opensmppbox

Any suggestion for the problem ?? I am not sure this question should go in devel list or users list. Regards, Manas On Tue, Oct 6, 2015 at 8:48 PM, Manas Mohanty wrote: > Hi, > > I am using opensmppbox. > I have noticed certain thing that in the case of multiple Rx

Re: Bug in Kannel Response Status codes

Hi Andreas, Thanks for your response . I have allowed all smsc that are used in the allowed-smsc-id parameter, there are no entries in denied-smsc-id. For example for fake smsc I am using : smsc = fake smsc-id = fake1 and allowed that smsc in the kannel configuration. allowed-smsc-id = fake1

patch to allow data_coding to be set to 3

Hi Alex, >From this thread that you responded to see http://www.kannel.org/pipermail/users/2012-April/017611.html and the current user guide, it seems Kannel has never allowed data_coding to be set to 3. See the coding parameter in the current spec

Re: patch to allow data_coding to be set to 3

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.

Re: patch to allow data_coding to be set to 3

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

Re: patch to allow data_coding to be set to 3

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