[
https://issues.apache.org/jira/browse/CAMEL-20061?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bruno Riemenschneider updated CAMEL-20061:
------------------------------------------
Description:
camel-smpp makes use of the library jSMPP.
When using jSMPP to bind to an SMSC, one can specify either \{
InterfaceVersion.IF_33, InterfaceVersion.IF_34, InterfaceVersion.IF_50 } as
the parameter interfaceVersion in the wrapper class BindParameter.
BindParameter can then be given to SMPPSession.connectAndBind() to establish a
connection to an SMSC.
Unfortunately, this functionality is not adopted in camel-smpp. It falls back
to SMPP v3.4 automatically, whilst not enabling the newer 5.0. Also, this is
lack of jSMPP-funtionality is not documented.
was:
camel-smpp makes use of the library jSMPP.
When using jSMPP to bind to an SMSC, one can specify either \{
InterfaceVersion.IF_33, InterfaceVersion.IF_34, InterfaceVersion.IF_50 } as
the parameter interfaceVersion in the wrapper class BindParameter.
BindParameter can then be given to SMPPSession.connectAndBind() to establish a
connection to an SMSC.
Unfortunately, this functionality is not adopted in camel-smpp. It falls back
to SMPP v3.4 automatically, whilst not enabling the newer 5.0. Also, this is
lack of jSMPP-funtionality is not documented.
> SMPP interface version cannot be set from 3.4 to latest version 5.0, even
> though underlying library jSMPP supports versions 3.3, 3.4, and 5.0
> ---------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: CAMEL-20061
> URL: https://issues.apache.org/jira/browse/CAMEL-20061
> Project: Camel
> Issue Type: Improvement
> Components: camel-smpp
> Reporter: Bruno Riemenschneider
> Priority: Major
>
> camel-smpp makes use of the library jSMPP.
> When using jSMPP to bind to an SMSC, one can specify either \{
> InterfaceVersion.IF_33, InterfaceVersion.IF_34, InterfaceVersion.IF_50 } as
> the parameter interfaceVersion in the wrapper class BindParameter.
> BindParameter can then be given to SMPPSession.connectAndBind() to establish
> a connection to an SMSC.
> Unfortunately, this functionality is not adopted in camel-smpp. It falls back
> to SMPP v3.4 automatically, whilst not enabling the newer 5.0. Also, this is
> lack of jSMPP-funtionality is not documented.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
