[
https://issues.apache.org/jira/browse/CAMEL-5455?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14201919#comment-14201919
]
Daniel Pocock commented on CAMEL-5455:
--------------------------------------
Just some observations about dataCoding and alphabet:
- alphabet (either the header or config value) is still being used exclusively
when deciding which charset to use for converting the message body (possibly a
String) to a byte array for the wire
- if both CamelSmppDataCoding and CamelSmppAlphabet headers are present,
CamelSmppDataCoding is used in the SMPP message
- if neither header is present on the exchange, then the alphabet config value
is ignored, the dataCoding config value (default 0) is chosen.
- data coding does not just contain alphabet details, it also contains data
about message class. If message class is specified, it clobbers the lower two
bits of the alphabet. This is a limitation of the protocol, not Camel.
> Allow configuring dataCoding independend of alphabet
> ----------------------------------------------------
>
> Key: CAMEL-5455
> URL: https://issues.apache.org/jira/browse/CAMEL-5455
> Project: Camel
> Issue Type: Bug
> Components: camel-smpp
> Affects Versions: 2.9.2, 2.10.0
> Reporter: Christian Müller
> Assignee: Christian Müller
> Fix For: 2.9.3, 2.10.1, 2.11.0
>
>
> See
> - http://camel.465427.n5.nabble.com/Datacoding-issue-td5715971.html
> -
> http://camel.465427.n5.nabble.com/Datacoding-Alphabet-issue-in-SMPP-td5280997.html
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
