[
https://issues.apache.org/jira/browse/CAMEL-3834?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13018938#comment-13018938
]
Christian Müller commented on CAMEL-3834:
-----------------------------------------
Steve, I think I fixed this issue. I applied a patch which uses the same
configuration as in the jsmpp
[SimpleSubmitExample|http://code.google.com/p/jsmpp/source/browse/tags/2.1.0/src/java/examples/org/jsmpp/examples/SimpleSubmitExample.java]
for the data coding.
Could you please test this fix with the latest code from trunk or with the
snapshot version from tomorrow?
Christian
> SmppProducer sends incorrect data_coding parameter
> --------------------------------------------------
>
> Key: CAMEL-3834
> URL: https://issues.apache.org/jira/browse/CAMEL-3834
> Project: Camel
> Issue Type: Bug
> Components: camel-smpp
> Affects Versions: 2.7.0
> Reporter: Steve Gansemer
> Assignee: Christian Müller
> Fix For: 2.8.0
>
>
> The dataCoding parameter on the SMPP uri allows for a value of 0,4, or 8.
> Our aggregator expects the data_coding parameter on the SMPP request from the
> SmppProducer to be 0=SMSC Default Alphabet. However, when 0, 4, or 8 is
> specified for the dataCoding parameter, the actual value sent on the smpp
> request is 1, 5, or 9. It appears the MessageClass.Class1 on the
> GeneralDataCoding object in SmppProducer is masking an additional 1 to the
> byte value.
> It seems the dataCoding parameter should allow you to specify the actual
> value that is needed as defined by the SMPP Protocol specification.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
