I think I found a better way to provide the data coding. If we do DataCoding.newInstance(dataCoding).value()
instead of new GeneralDataCoding(false, true, MessageClass.CLASS1, determinedAlphabet).value() the user can choose between all possible data coding values. This would be much more flexible. I wonder if we also should still support the alphabet option or whether we should use DataCoding.newInstance(dataCoding).getAlphabet() instead, to determine the alphabet.. Will have a deeper look into it tomorrow... Best, Christian On Thu, Jul 12, 2012 at 10:27 PM, Christian Müller < christian.muel...@gmail.com> wrote: > The is already a thread about this [1]. > I'm looking into it right now... > > [1] > http://camel.465427.n5.nabble.com/Datacoding-Alphabet-issue-in-SMPP-td5281005.html > > Best, > Christian > > > On Thu, Jul 12, 2012 at 9:45 PM, cannotcode <aydin.fa...@gmail.com> wrote: > >> Hi all, >> >> We use 2.9.2 version of camel-smpp. Recently, we realized that it is not >> possible to set dataCoding to 0. There is only "alphabet" parameter in >> hand, >> but when I set it to 0, i see that dataCoding is set to 17 (0x11). In >> order >> to work this around, I just changed the following line SmppSubmitSmCommand >> class: >> >> template.setDataCoding(new GeneralDataCoding(false, false, >> MessageClass.CLASS0, determinedAlphabet).value()); >> >> Was this reported before? >> >> -- >> View this message in context: >> http://camel.465427.n5.nabble.com/Datacoding-issue-tp5715971.html >> Sent from the Camel - Users mailing list archive at Nabble.com. >> > >
