Re: SMPP v3.4 protocol - submit_sm / data_coding / short_message / GSM 03.40 7 bit alphabet and missing packing?

Oh yeah, of course I'd rather that 7 bit encoding in 8 bit octets be
correct to the SMPP standard... because 7 bit packed isn't very readable...
sheesh...  ;-P

On Tuesday, 2003-03-11 at 06:20:35 PM, Benjamin Lee scribbled:
> 
> Hi all,
> 
> I need to confirm something in regards to the SMPP protocol v3.4.
> 
> I'm interested in the submit_sm pdu, its data_coding field and
> short_message data.
> 
> According to the SMPP developers forum 'Short Messsage Peer to Peer
> Protocol Specification v3.4 document' ... sections 5.2.19 data_coding (p.
> 126) and 5.2.22 short_message (p. 128) ...
> 
> A data_coding value of 0x00 means message centre default alphabet, thus MC
> / provider specific. However, usually this tends to be the GSM 03.40 7 bit
> alphabet.
> 
> However, since the SMPP submit_pdu's short_message field is up to 254
> *Octets* then, if the alphabet coding is GSM 7 bit, should not the Bytes in
> the short_message Octet buffer be converted to septets before sending?
> 
> I've found that of the providers / MCs that we use, they accept GSM 7 bit
> characters encapsulated in 8 bit Octets. Is this correct behaviour? Or are
> we all doing it wrong (including kannel)?... maybe we should be packing the
> Bytes into septets?
> 
> Anybody on the SMPP developers forum on this list?
> 
> Anyway...
> Later.
> 

-- 
Benjamin Lee

Level 2 71-75 City Rd, South Melbourne, VIC 3006 Australia
Phone +61 3 8699 1333  Mobile +61 414 717 573  Fax +61 3 8699 1388