Camel
  1. Camel
  2. CAMEL-4501

Allow CAMEL to act as SMPP router/gateway

    Details

    • Type: New Feature New Feature
    • Status: Open
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: 2.8.1
    • Fix Version/s: Future
    • Component/s: camel-core
    • Labels:
      None
    • Environment:

      Linux, Java java version "1.6.0_26"

    • Estimated Complexity:
      Unknown

      Description

      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.

        Activity

        Hide
        Claus Ibsen added a comment -

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

        Show
        Claus Ibsen added a comment - What it is that today's camel-smpp cannot do? http://camel.apache.org/smpp

          People

          • Assignee:
            Unassigned
            Reporter:
            Brendan Moynihan
          • Votes:
            3 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

            • Created:
              Updated:

              Development