smpp

I'd like to set up Kannel to send SMS messages without going through a 3rd party gateway like Clickatell or Twilio. In other words, I'd like to connect to the SMPP server for each wireless services (AT&T, Verizon, etc.). How difficult/easy is it to run a Kannel server this way? Each SMSC has to be configured for each mobile network. What is the support like for each network in the US (AT&T, Verizon, T-mobile, Sprint)? Can someone point me to a tutorial/blog for pulling this off (besides the docs)? Cotopaxi, Kannel will happily work with all the carriers in the US. Unfortunately a number of

Lets say there are two receiver session from same application to a SMPP over different TCP ports. Message is sent to application and reply is (i.e deliver_sm_resp) is coming to SMPP via the other session Is this possible or reply should be come over the same SMPP session? No, the deliver_sm_resp should be sent back using the same session as the deliver_sm was received on. The response is linked with the request by a sequence number that is incremented with each request on the session so the it only makes sense within the same session. 来源： https://stackoverflow.com/questions/5909687/multiple

I am currently trying to figure out how sms classes are correctly represented in SMPP. However I am by now completely confused by the standard and it's documentation. In normal sms we have Class0: Flash sms, which are shown on the display Class1: Normal Sms to be stored on the sim or internally in the device Looking at the SMPP spec, I first find the parameter data_coding in the submit_sm operation, which is used to set the DCS sent via MAP. As far as I understand this, if we want to explicitly set the message class we need to set the first four bits of this parameter to ones, then two bits

What is the meaning of "data_coding" field in the SMPP protocol? I searched for this but couldn't find any helpful resource. In short, datacoding contains the information on how the text in an smpp SubmitSM (i.e. a typical SMS message) message is encoded. The SubmitSM packet contains a binary encoded body, and the dataCoding is how the text is stored in this body. The most important values are: 00000000 (0) - usually GSM7 (the default 7 bit encoding for messages, with a few characters that are encoded as two bytes), but technically could be something else 00000011 (3) for standard ISO-8859-1

We're about to begin a project which requires the use of SMPP as the primary integration exchange channel. Now since SMS isn't necessarily core to our business, I'd like to use an SMPP library for Java that will be the least hassle. Aside from riding on the actual protocol, its unlikely we'll need fancier abilities or to ever tweak under the hood. To that end, I've shortlisted some of the possible options that we have: Logica's Open SMPP Apache's Camel JSMPP Twitter's Cloudhopper Can someone who's more experienced in their uses throw some of their experiences my way ? EDIT: Just to give scope

Recently I read an article about Sending SMS notifications using WSo2 esb . Unfortunately it does not work for me and I am not 100% sure about some of those configurations. Following are the problems that I have. Are there any other library files, rather than the two files below, that can be used to enable SMS transport sender over SMPP? axis2-transport-sms-1.0.0.jar jsmpp-2.1.0.jar What is the actual directory into which I should put each of those jars - is it $ESB_HOME/repository/components/lib ?. Finally, what should the address endpoint for sending a specific number look like? Is it like