[
https://issues.apache.org/jira/browse/CAMEL-3834?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13018333#comment-13018333
]
Steve Gansemer commented on CAMEL-3834:
---------------------------------------
The value that ends up being sent on the smpp request for the data_coding byte
ends up being 1,5, or 9. I believe this is caused because the GeneralDataCoding
object that is used by the SmppProducer is using a MessageClass.CLASS1 which
ends up masking an additional bit onto the value.
In my case, our back end aggregator expects the data_coding value to be 0 which
I can't specify because this extra bit is being set.
> 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.5.0
> Reporter: Steve Gansemer
> Assignee: Christian Müller
>
> 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
