camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Claus Ibsen (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CAMEL-4501) Allow CAMEL to act as SMPP router/gateway
Date Tue, 17 Feb 2015 07:11:12 GMT

    [ https://issues.apache.org/jira/browse/CAMEL-4501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14323763#comment-14323763
] 

Claus Ibsen commented on CAMEL-4501:
------------------------------------

What it is that today's camel-smpp cannot do?
http://camel.apache.org/smpp

> Allow CAMEL to act as SMPP router/gateway
> -----------------------------------------
>
>                 Key: CAMEL-4501
>                 URL: https://issues.apache.org/jira/browse/CAMEL-4501
>             Project: Camel
>          Issue Type: New Feature
>          Components: camel-core
>    Affects Versions: 2.8.1
>         Environment: Linux, Java java version "1.6.0_26"
>            Reporter: Brendan Moynihan
>             Fix For: Future
>
>
> Please see the following thread for futher information. 
> http://camel.465427.n5.nabble.com/SMPP-to-SMPP-using-camel-td4845410.html
> The improvement would be to allow CAMEL be a bi directional router between SMPP peers.
> ie. ESME/SMSC <=> CAMEL <=> SMSC/ESME.
> Typical flow might be ESME sends submit-sm to CAMEL.
> Based on destination address, CAMEL can route the submit-sm to a specific SMSC connection.
> Deliver SM for receipt can subsequently be received into CAMEL from SMSC and routed to
the specific originating ESME.
> Also, Can CAMEL consume a submit sm from an ESME and produce a deliver sm to SMSC?
> Should be able to perform this operation for SUBMIT, DELIVER, DATA type SMPP messages.
>  



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message