Re: [RFI] octstr_recode

----- Original Message -----
From: "Andreas Fink" <[email protected]>
To: "Bruno David Rodrigues" <[email protected]>
Cc: <[email protected]>
Sent: Wednesday, March 06, 2002 3:32 PM
Subject: Re: [RFI] octstr_recode


> >with mo-record = true, kannel will TRY to convert to iso-8859-1 only.
> >
> >If mo-record is false or kannel can't convert UCS2 to iso-8859-1 (because
> >of a unknown char), kannel will behave just like before: text will have
the
> >ucs2 string, coding (%c) will have 3 and charset (%C) will have UTF16-BE.
>
>
> I see, so there's more than I even thought there is. Good to see %c
> being supported. Has this been documented yet? Anyone tested this
> with kannel-kannel HTTP smsc?


It's documented and it's not yet ported to smsc_http (and unfortunatly to
sms-service POST)


> What I am missing besides that is incoming support for UDH so we can
> receive incoming a ringtone or similar. So a %u could be used (if
> thats not taken).

Incoming udh will have to wait until we have incoming concatenation
I'm now thinking about a way to do it :)