-
Wow so your SMSC provider is keeping their broken implementation of their protocol the way it is? That seems crazy to me. Any SMPP implementation, not just this smppapi, will be confused by that stray nul byte. Ah well, SEP.
2009-10-26 17:01:24 UTC in Java SMPP API
-
Yes, that's what I said. You receive the delivery receipt via a deliver\_sm packet. Setting the registered property on your submit\_sm packet only *requests* a delivery receipt.
1. You send a submit\_sm with registered == 1
2. You receive a submit\_sm\_resp which contains a message ID.
3. When the message is delivered, the SMSC generates a delivery receipt which it delivers to you via a...
2009-10-08 09:12:06 UTC in Java SMPP API
-
You request a delivery receipt by setting the "registered" property to 1 on your submit_sm:
submitSm.setRegistered(1);
When you receive the delivery receipt (via a deliver_sm) you have to parse the text of the message to locate the message ID for the originally submitted message. This will be the same message ID as you received in your submit_sm_resp.
2009-10-08 08:44:26 UTC in Java SMPP API
-
I parsed out a valid deliver_sm packet starting at offset 70 (decimal) in the bytes you provided. Afraid it all looks pretty standard to me, there don't appear to be any magic values in there that the iphone is setting. At least, none that are being passed through by the SMSC, as that is what will have formed this deliver_sm packet.
2009-09-29 14:25:48 UTC in Java SMPP API
-
I'm not clear what's not working for you. Are you saying that after your application sends an enquire\_link packet, that from that point onward the Connection fails to respond to enquire\_link, deliver\_sm packets received from the SMSC? Or does your application fail to send any further packets at all? Is this something to do with the autoAckLink functionality of the Connection?
You should...
2009-09-28 07:51:41 UTC in Java SMPP API
-
What DCS value does the iphone set on the unicode message sent from it?.
2009-09-28 07:46:13 UTC in Java SMPP API
-
Asynchronous mode is enabled using an alternate constructor for the Connection:
Connection c = new Connection(smsLink, true);
autoAckLink and autoAckMessages are only designed to be used with asynchronous communications. Enabling them with synchronous comms can cause problems.
2009-09-28 07:40:08 UTC in Java SMPP API
-
The javadocs are included in the smppapi download bundle. Look in the docs subdirectory.
2009-09-17 19:33:30 UTC in Java SMPP API
-
By string length of 0 to 16 characters I mean a byte array containing between 0 and 16 7-bit characters which I unpacked.
I haven't looked at the spec for UDH+concatenated messages using the packing algorithm but I am reasonably sure that you should strip off the UDH *before* you attempt to unpack. So you should be doing something like:
byte[] fullMessage = deliverSm.getMessage();
byte[]...
2009-09-09 12:15:06 UTC in Java SMPP API
-
I am unable to reproduce any pack or unpack problem with any string length between 0 and 16 characters. You'd expect encoding problems to occur at some modulo 7 index since that's where the encoding trickery happens.
I would be interested to see how you are carving up the message into the UDH and the concatenated part because I suspect this to be the root cause of the issue.
2009-09-08 15:51:23 UTC in Java SMPP API
