camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sandeep Shukla (JIRA)" <>
Subject [jira] [Commented] (CAMEL-5963) camel-smpp: Support TRX connection mode to the SMSC
Date Fri, 21 Jun 2013 10:27:20 GMT


Sandeep Shukla commented on CAMEL-5963:

The inability of the SMPP component to provide TRX support is stopping many of us to not use
the component for USSD as most of the gateways in our region just support TRX( with TX sometimes).
Anyhow - since this is in the camel roadmap, I am sure you guys will come out with the functionality
enhancement. I would only suggest to do this sooner to increase the acceptance of the component.

Coming back to the discussion - 
1. I think this will apply both to the consumer and the producer. This will mean  that the
binding mode is a configurable item (TRX, TX and RX) defaulting to TX for producer and RX
for consumer. 
2. As of now the producer and the consumer both have there own SMPPSession. This session should
recide with the endpoint and created  by the createProducer/createConsumer only once in case
the mode is TRX ( for other modes it will continue to work as it is ) . 
3. While using a TRX mode, the user will have to create an endpoint and then refer the same
in the process ( I am not sure on this part and would need your guidance on the same). 
<camelContext xmlns="">
  <endpoint id="trxEndPoint"  uri="smpp://smppclient@localhost:2775?
    <from ref="trxEndPoint"/>
    <to uri="jms:incomingOrders"/>
    <from ref="jms:incomingOrders"/>
    <to uri="trxEndPoint"/>

Please guide. 

> camel-smpp: Support TRX connection mode to the SMSC
> ---------------------------------------------------
>                 Key: CAMEL-5963
>                 URL:
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-smpp
>    Affects Versions: 2.10.3
>            Reporter: Christian Müller
>            Assignee: Christian Müller
>             Fix For: 2.12.0
> See for details

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message