On Wed, 2010-11-24 at 09:41 +0000, alejandro.guerri...@gmail.com wrote: > Messages with UDH are actually binary in SMS terms. Maybe J2ME behaves the > same?
Yes and no... For one thing, the UDH itself is not part of the J2ME BinaryObject I get. The bytes in the BinaryObject are actually all ASCII. A bit of context: we are in the process of migrating away from NowSMS. We are setting the UDH header in the SMS sent from NowSMS, but J2ME creates a TextMessage anyway, so this has to be possible somehow. I think this must be some charset or encoding issue, but since I'm pretty much an SMPP newb, I thought I'd ask here... Thank you, peter. > Regards, > > Alex > BlackBerry de movistar, allí donde estés está tu oficin@ > > -----Original Message----- > From: Peter Sabaini <pe...@sabaini.at> > Sender: users-boun...@kannel.org > Date: Wed, 24 Nov 2010 10:00:05 > To: <users@kannel.org> > Subject: [resend] Sending SMS with UDH results in BinaryMessage > > Resending -- anyone with J2ME experience here? Thanks alot!\ > > -- > Hello list, > > I use the sendsms interface to send SMS with a UDH to set the > destination port. Setting the port works, but one oddity remains -- the > J2ME platform returns a com.sun.midp.io.j2me.sms.BinaryObject instead of > a TextObject in this case. > > Does anyone know how this behaviour is triggered? The message body only > contains ASCII... > > Thanks, > peter. >
signature.asc
Description: This is a digitally signed message part
