Closed GoogleCodeExporter closed 9 years ago
Original comment by T.Delenikas
on 17 Jul 2010 at 7:13
This is an SMPP issue, right?
I guess Basaam may give you a more authoritative answer than me.
Original comment by T.Delenikas
on 17 Jul 2010 at 7:15
Hi,
@Nassar,
Regarding your first issue, WAP PUSH SMS, I've not tried to send a WAP Push
through SMPP before and I tried to find an example of sending WAP Push using
JSMPP but didn't find one. However, you mentioned that the message doesn't
open, "but he/she cannot open it", do you mean that the message opens as a SMS
message rather than a WAP Push? If so, I think that's because you need to set
the UDHI (User Data Header Indicator), to do that, try passing the value 0x40
to the ESMClass constructor. In JSMPPGateway.sendMessage() method there is a
call to session.submitShortMessage() method, one of the passed parameters is
new ESMClass()
// change it to
new ESMClass(0x40)
Hope that works.
Regarding the second issue, make sure that your bind attributes match the SMSCs
connection bind attributes (especially bind type, should be Receiver or
Transceiver). If that doesn't help provide me with your bind attributes and the
log output.
Regards,
Original comment by balsar...@gmail.com
on 18 Jul 2010 at 8:11
Closing this - feel free to comment to re-open it.
Original comment by T.Delenikas
on 9 Aug 2010 at 6:27
Original issue reported on code.google.com by
sohadnas...@gmail.com
on 4 Jul 2010 at 12:45