smpp

问题 I have created SMS gateway application in which I'm using kannel to connect to MNO(Mobile Network Operators) SMSCs.I have set of clients who are connected to my application given the API (JSON API) and in my application I basically send the request to kannel via its http API. How I have this new clients whose requirement is that his request should go via SMPP protocol as he doesn't feel that JSON API is that much secure as messages can be altered on its way to the recipient. To create SMPP

问题 I am writing ESME using logica smpp lib, but have a serious problem - when SMSC send to ESME [FIN, ACK] , ESME do not answer correct. Here TCP dump: 2751.016216 ESME -> SMSC SMPP SMPP Submit_sm 2751.019818 SMSC -> ESME SMPP SMPP Submit_sm - resp: "Throttling error (ESME exceeded allowed message limits)" 2751.136172 ESME -> SMSC TCP 42265 > 5001 [ACK] Seq=1651885221 Ack=3959508692 Win=123 Len=0 2774.588453 SMSC -> ESME TCP 5001 > 42265 [FIN, ACK] Seq=3959508692 Ack=1651885221 Win=32768 Len=0

问题 I want to write a simple SMPP Server that basically forwards traffic to another SMPP server (C#, PHP). What are the things I need to know? How do I proceed? 回答1: With regards to Goran's comment, one possible solution would be a simple tcp proxy such as simpleproxy. From the Ubuntu package description: simpleproxy acts as a simple TCP proxy. It opens a listening socket on the local machine and forwards any connection to a remote host. It can be run as a daemon or through inetd. 回答2: Olaseni, I

问题 Is it correct that the Message ID returned as part of the SUBMIT_SM_RESP does not match the Message ID returned in the DELIVER_SM delivery receipt? From reading the SMPP 3.4 spec 1.2 I thought it would, because the spec states in Appendix B for the delivery receipt: The message ID allocated to the message by the SMSC when originally submitted. but I'm finding for example the hex returned in the SUBMIT_SM_RESP to be c81f136b00116d53000000000b68c86e01481101 whilst the decimal returned in the

问题 Is it correct that the Message ID returned as part of the SUBMIT_SM_RESP does not match the Message ID returned in the DELIVER_SM delivery receipt? From reading the SMPP 3.4 spec 1.2 I thought it would, because the spec states in Appendix B for the delivery receipt: The message ID allocated to the message by the SMSC when originally submitted. but I'm finding for example the hex returned in the SUBMIT_SM_RESP to be c81f136b00116d53000000000b68c86e01481101 whilst the decimal returned in the

问题 For concatenated SMS messages (in GSM encoding), if extended table symbol (one of these: }{[]|~^\€) is placed at the end of segment, what is correct way to split such message: Leave first byte of symbol (0b) at the end of segment and put second byte to the beginning of next one, and so fill all available bytes of UD (which seems logically correct) OR Move whole symbol bytes to the next segment and leave unused byte at the end? I didn't found any clarification neither in SMPP 3.4 specs or

问题 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

问题 Demo from https://github.com/twitter/cloudhopper-smpp/blob/master/src/test/java/com/cloudhopper/smpp/demo/ServerMain.java provides an example of receiving MT messages from client. But how to send messages (deliver_sm) from server to connected client? 回答1: I just took code from ClientMain and changed SubmitSm to DeliverSm. For testing purpose I read msg text from Console and send Message using this code. You should call this method in separate thread. Also you should handle list of sessions so

问题 Hi Followed the blog mentioned in SMS Transport sender in wso2 ESB and configured axis2.xml for transportSender and transportReceiver . I am able to send a message from ESB to SMPP simulator but I am unable to receive message from SMPP simulator to ESB . In the SMPP Simulator, I tried by adding bot 't'/'r' to enable transmitter/receiver and also tried by giving tr assuming that it is for tranceiver in users.txt but still I am unable to get a response in ESB. Could you please help in

问题 exports.sendSMS = function (session, to, text, sourceAddress, jsonMessageHistoryIds, callback) { console.log('messege',text); session.submit_multi({ source_addr: sourceAddress, dest_address: to, short_message: text }, function (pdu) { console.log('submit_multi: ', pdu.command_status); console.log("PDU", pdu); if (pdu.command_status == 0) { // insert into sms smpp logs var values = { type: 'bulk', message: text, numbers: JSON.stringify(to) }; console.log(pdu.message_id); callback(null, pdu