Hi Biruntha, Is this going to be part of the SMS connector or the ESB?
thanks, Dimuthu On Mon, Nov 21, 2016 at 1:26 PM, Dimuthu Leelarathne <[email protected]> wrote: > > > On Mon, Nov 21, 2016 at 11:36 AM, Biruntha Gnaneswaran <[email protected]> > wrote: > >> Hi All, >> >> I have planned to implement SMPP inbound endpoint to consume SMPP >> messages from the SMSC as described below. The behaviour of this inbound >> endpoint is Event Based. Because, inbound endpoint polls only once to >> establish a connection with the SMSC and then It listens on a given port >> for messages that are coming in. When they are available, it is injected to >> a given sequence. >> >> Architecture diagram of SMPP inbound Endpoint: >> >> >> How SMPP Message receive from SMSC: >> >> The SMSC may deliver short messages to an ESME. In this case the ESME >> must be connected to the SMSC as an ESME Receiver which is authorised to >> receive short messages from the SMSC and to return the corresponding SMPP >> message responses to the SMSC. The following diagram illustrates a typical >> SMPP request/response sequence between an SMSC and an ESME, while receiving >> the message. >> >> >> >> >> ESME - It is an external application that connects to a Short Message >> Service Center (SMSC) to sending and/or receiving of SMS >> <https://en.wikipedia.org/wiki/Short_message_service> messages. >> >> SMSC - It is to store, forward, convert and deliver Short Message >> Service (SMS) messages. >> >> outbind - Outbind operation is to allow the SMSC signal an ESME to >> originate a bind_receiver request to the SMSC while the SMSC had >> outstanding messages for delivery to the ESME. >> >> bind_receiver - In order to receive messages, the ESME should respond >> with a “bind_receiver” request to which the SMSC will reply with a >> “bind_receiver_resp”. >> >> deliver_sm - The deliver_sm is issued by the SMSC to send a message to >> an ESME. Using this command, the SMSC may route a short message to the ESME >> for delivery. >> >> The exchange of SMPP request and response PDUs (Protocol Data Units) >> between an SMSC and ESME Receiver may be implemented synchronously or >> asynchronously as shown above. Thus the SMSC may send multiple deliver_sm >> requests to the ESME, without synchronously waiting for the associated >> response PDUs. >> >> Your comments and suggestions on this are highly appreciated. >> >> Thanks, >> Biruntha >> >> Associate Software Engineer >> WSO2 >> Email : [email protected] >> Linkedin : https://lk.linkedin.com/in/biruntha >> Mobile : +94773718986 >> >> _______________________________________________ >> Architecture mailing list >> [email protected] >> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >> >> > > > -- > Dimuthu Leelarathne > Director, Solutions Architecture > > WSO2, Inc. (http://wso2.com) > email: [email protected] > Mobile: +94773661935 > Blog: http://muthulee.blogspot.com > > Lean . Enterprise . Middleware > -- Dimuthu Leelarathne Director, Solutions Architecture WSO2, Inc. (http://wso2.com) email: [email protected] Mobile: +94773661935 Blog: http://muthulee.blogspot.com Lean . Enterprise . Middleware
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
