I've had some more time to study both the jsmpp and Camel-smpp code.
The way Camel-smpp abstracts the data coding by using an Alphabet property
and then deriving a datacode value by using a hard coded Message Class(class
1) restricts the possible datacoding values one can send to an smsc. (I am
re
You would think so, but the SMPP 3.4 spec isn't limited to just those 4
values when it comes to datacoding.
--
View this message in context:
http://camel.465427.n5.nabble.com/Datacoding-Alphabet-issue-in-SMPP-tp5281005p5440992.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Thanks for the reply Taariq.
If I try any other value I get an IllegalArgumentException with "No enum
const Alphabet with value ...". This is thrown by the jsmpp Alphabet enum
that also only caters for datacodings of 0, 4 and 8.
In the SmppSubmitSmCommand class, the GeneralDataCoding is constru
I am currently using the camel 2.9 smpp component to send sms's via our smpp
provider. The smmp 3.4 spec lists a number of available datacoding
possibilities, whereas with camel smpp you can specify datacoding of just 0,
4 or 8.
Is there any way to override this limitation, as we have a need to s
I am currently using the camel 2.9 smpp component to send sms's via our smpp
provider. The smmp 3.4 spec lists a number of available datacoding
possibilities, whereas with camel smpp you can specify datacoding of just 0,
4 or 8.
Is there any way to override this limitation, as we have a need to s
