RE: charset question (Greek)

> Another way would be to carry the SMS always in binary format around. 
> This means the format actually used on the over the air. This is more 
> or less the binary version of the PDU format of the AT interface. In 
> this case, the SMSC driver would simply do things like encoding the 
> data in hex or so. For EMI it woudl split off the UDH, for AT it 
> would work "as is" and for SMPP its pretty similar.  this would also 
> work for HTTP interface for kannel-kannel (providing coding / charset 
> are set correctly). Any SMSC types however who dont take binary 
> format as input would be a problem then (some content gateway 
> recently added could be a problem). If we cant code something in GSM 
> binary format, we cant send it to a phone so its THE common format. 
> However the question is also what happens to non GSM networks in this 
> case. Are there any issues there maybe?
> 
> The advantage of this solution is that there is much less processing 
> power needed in bearerbox and the cpu intensive tasks would be done 
> in SMSBox which can be load shared easily. Also routing can work more 
> efficiently as you would never have to think about recoding. The 
> binary format is as close to GSM as it can be so every SMS protocol 
> should be supportable.
> 
> Comments?

That would be bad - I'm currently working with two (different) SMSC
protocols that both use some sort of text for transfer : weirdly encoded
ASCII or utf-8. if you lug the messages around in binary, whenever a
non-standard SMSC protocol comes along you'll have to do lotsa recoding
in the module itself.

--
Oded Arbel
m-Wise Inc.
[email protected]

You're not who you are, you're only what other people think of you.
	-- Fishizm