----- Original Message -----
From: "Paul Keogh" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, September 03, 2001 1:33 PM
Subject: RE: Data Coding Scheme...
>
> > SMSC's shouldn't interpret DCS field (That's why I'm pissed
> > with Siemens
> > M20)
> >
>
> It makes sense to me that GSM modems should interpret the DCS
> because they have no responsibility for encoding the data.
> GSM 03.38 chapter 4 makes it reasonably clear about when the DCS
> value specifies 8 bit or default alphabet. Thus, if you supply
> 8 bit encoded data with a DCS value that indicates 7 bit encoding,
> the device is entitled to complain.
How do you know the difference between a 7bit encoded message and a 8 bit
raw message ? for me (and for the modem) it's just a bunch of bits!
the only way to know what is that bunch of bits is to look at DCS field. And
that
should be done in the handset when it need to show the message. Why should
any bearer (smsc, modem sending, etc) look at it ?
I'll read 03.38 better then.
> This also means that Kannels approach to encoding based on UDH
> presence/absence is broken now that the DCS value is exposed at the
sendsms
> interface.
What do you mean?
Was it broken before or is broken now ?
