search

google-code-export / smslib

Automatically exported from code.google.com/p/smslib
1 stars 0 forks source link

Protocols Gateway #485

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
Hello,
Could you tell me what the difference between the protocols:
AGateway.Protocols.PDU?
AGateway.Protocols.TEXT?

Messages I send to the 158 character count next arrive at the destination 
broken into about 3 pieces. These protocols deal with this? I sent in standard 
PDU. When should I use TEXT?

Original issue reported on code.google.com by thinform...@gmail.com on 13 Apr 2012 at 1:29

GoogleCodeExporter commented 9 years ago 
You should definitely use PDU as long as your modem supports this - and forget 
about the TEXT protocol.

For the multipart issue, check if you are sending messages with UCS2 (Unicode) 
encoding. With this encoding, each message part can hold up to 70 chars.

Original comment by T.Delenikas on 16 Apr 2012 at 9:53

GoogleCodeExporter commented 9 years ago 
Exactly what I'm using this code:
msg.setEncoding (org.smslib.Message.MessageEncodings.ENCUCS2);

I'm using it so that the messages are sent with accents (à,á,ã,õ,ç...). Is 
there any other encoding that can handle this grammar correctly?

Original comment by thinform...@gmail.com on 16 Apr 2012 at 11:19

GoogleCodeExporter commented 9 years ago 
I am afraid not. You need to use UCS2 to safely send such characters.

Original comment by T.Delenikas on 16 Apr 2012 at 12:21

GoogleCodeExporter commented 9 years ago 
No other alternative?
For I am doing mass uploads, and I believe that this encoding is slower letting 
shipments, given that they are divided into parts.

Original comment by thinform...@gmail.com on 16 Apr 2012 at 12:30

GoogleCodeExporter commented 9 years ago 
No alternative that I know of.

And yes, you are right: it's slower and probably less reliable as well, as all 
message fragments must reach the recipient.

Original comment by T.Delenikas on 17 Apr 2012 at 5:17