Camel SMPP component support for optional parameters such as operator etc.

[justinblandford]

Hi,

I have a question regarding the use of the Camel SMPP component (http://camel.apache.org/smpp.html).  There are a few optional SMPP PDU header parameters such as Operator, Session Id etc (http://www.mpulse.eu/sites/mpulse_eu/files/files/SMPP_specifications_v1-0-5_2011-02-22.pdf).  Additional there are parameters such as Tariff which also don't seem to be supported on the Camel PDU headers spec?  Does anyone have any information on how to get around this or whether it will be supported in a future version?

Regards,

Justin

[Christian Mueller]

We could do this if there is a need for it.
Contributions are very welcome [1]. Raise a JIRA [2] and make some
suggestions how we could do it.

[1] http://camel.apache.org/contributing.html
[2] https://issues.apache.org/jira/browse/CAMEL

Best,
Christian

On Thu, Jul 26, 2012 at 6:27 PM, justinblandford <
[hidden email]> wrote:

> Hi,
>
> I have a question regarding the use of the Camel SMPP component
> (http://camel.apache.org/smpp.html).  There are a few optional SMPP PDU
> header parameters such as Operator, Session Id etc
> (
> http://www.mpulse.eu/sites/mpulse_eu/files/files/SMPP_specifications_v1-0-5_2011-02-22.pdf
> ).
> Additional there are parameters such as Tariff which also don't seem to be
> supported on the Camel PDU headers spec?  Does anyone have any information
> on how to get around this or whether it will be supported in a future
> version?
>
> Regards,
>
> Justin
>
>
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/Camel-SMPP-component-support-for-optional-parameters-such-as-operator-etc-tp5716523.html
> Sent from the Camel Development mailing list archive at Nabble.com.
>

[chris snow]

Could something similar to this approach work?

http://www.activexperts.com/files/sms-messaging-server/manual.htm#API_Tlv_Class

Taking the example from:

http://www.activexperts.com/support/sms-messaging-server/index.asp?kb=Q8300140

would give us this:

optionalParameterTag[0]=0x1403
optionalParameterType[0]=Octet
optionalParameterValueAsOctetString[0]=3132333435

where the OptionalParameterTypes are:

Null
Short
Int
Byte
OctetString
COctetString

I.e. the types map to jsmpp OptionalParameter subclasses


On Fri, Jul 27, 2012 at 11:03 PM, Christian Müller
<[hidden email]> wrote:

> We could do this if there is a need for it.
> Contributions are very welcome [1]. Raise a JIRA [2] and make some
> suggestions how we could do it.
>
> [1] http://camel.apache.org/contributing.html
> [2] https://issues.apache.org/jira/browse/CAMEL
>
> Best,
> Christian
>
> On Thu, Jul 26, 2012 at 6:27 PM, justinblandford <
> [hidden email]> wrote:
>
>> Hi,
>>
>> I have a question regarding the use of the Camel SMPP component
>> (http://camel.apache.org/smpp.html).  There are a few optional SMPP PDU
>> header parameters such as Operator, Session Id etc
>> (
>> http://www.mpulse.eu/sites/mpulse_eu/files/files/SMPP_specifications_v1-0-5_2011-02-22.pdf
>> ).
>> Additional there are parameters such as Tariff which also don't seem to be
>> supported on the Camel PDU headers spec?  Does anyone have any information
>> on how to get around this or whether it will be supported in a future
>> version?
>>
>> Regards,
>>
>> Justin
>>
>>
>>
>> --
>> View this message in context:
>> http://camel.465427.n5.nabble.com/Camel-SMPP-component-support-for-optional-parameters-such-as-operator-etc-tp5716523.html
>> Sent from the Camel Development mailing list archive at Nabble.com.
>>

--
Chris Snow - http://uk.linkedin.com/pub/christopher-snow-mba-tech-mgmt/6/0/316

[Christian Mueller]

The camel-smpp component is based on JSMPP [1].
I could imagine we add an option "optionalParameter" for static addition
parameters.
We could also add a message header which we check and add these optional
parameters also to the short message.

[1]
http://code.google.com/p/jsmpp/source/browse/tags/2.1.0/src/java/main/org/jsmpp/bean/OptionalParameter.java

Best,
Christian

On Fri, Jul 27, 2012 at 10:15 PM, chris snow <[hidden email]> wrote:

> Could something similar to this approach work?
>
>
> http://www.activexperts.com/files/sms-messaging-server/manual.htm#API_Tlv_Class
>
> Taking the example from:
>
>
> http://www.activexperts.com/support/sms-messaging-server/index.asp?kb=Q8300140
>
> would give us this:
>
> optionalParameterTag[0]=0x1403
> optionalParameterType[0]=Octet
> optionalParameterValueAsOctetString[0]=3132333435
>
> where the OptionalParameterTypes are:
>
> Null
> Short
> Int
> Byte
> OctetString
> COctetString
>
> I.e. the types map to jsmpp OptionalParameter subclasses
>
>
> On Fri, Jul 27, 2012 at 11:03 PM, Christian Müller
> <[hidden email]> wrote:
> > We could do this if there is a need for it.
> > Contributions are very welcome [1]. Raise a JIRA [2] and make some
> > suggestions how we could do it.
> >
> > [1] http://camel.apache.org/contributing.html
> > [2] https://issues.apache.org/jira/browse/CAMEL
> >
> > Best,
> > Christian
> >
> > On Thu, Jul 26, 2012 at 6:27 PM, justinblandford <
> > [hidden email]> wrote:
> >
> >> Hi,
> >>
> >> I have a question regarding the use of the Camel SMPP component
> >> (http://camel.apache.org/smpp.html).  There are a few optional SMPP PDU
> >> header parameters such as Operator, Session Id etc
> >> (
> >>
> http://www.mpulse.eu/sites/mpulse_eu/files/files/SMPP_specifications_v1-0-5_2011-02-22.pdf
> >> ).
> >> Additional there are parameters such as Tariff which also don't seem to
> be
> >> supported on the Camel PDU headers spec?  Does anyone have any
> information
> >> on how to get around this or whether it will be supported in a future
> >> version?
> >>
> >> Regards,
> >>
> >> Justin
> >>
> >>
> >>
> >> --
> >> View this message in context:
> >>
> http://camel.465427.n5.nabble.com/Camel-SMPP-component-support-for-optional-parameters-such-as-operator-etc-tp5716523.html
> >> Sent from the Camel Development mailing list archive at Nabble.com.
> >>
>
>
>
> --
> Chris Snow -
> http://uk.linkedin.com/pub/christopher-snow-mba-tech-mgmt/6/0/316
>