The mclass switch isn't set. I forgot to mention I'm dealing with an HTTP SMSC of type "generic". The send-url interface for this is extremely limited and basically only allows me to pass the following parameters: from, to, msg
Is there any work around for applying a specific coding scheme to the message? Thanks, Nii. On Thu, 2009-02-12 at 16:01 +0100, Falko Ziemann wrote: > Yeah, I think everyone had this problem once: when the mclass switch > is set, the alt-charset is ignored. > > Regards > Falko > > Am 12.02.2009 um 15:39 schrieb Nii Ako Ampa-Sowa: > > > Hello, > > > > Does anyone have experience with converting between different > > character > > encoding schemes for HTTP SMSCs? > > > > Here's the scenario I'm facing: I receive messages via SMPP > > interface in > > encoded as UCS-2. I need to send these messages out formatted as UTF-8 > > to an HTTP SMSC. > > > > For some reason defining the alt-charset as UTF-8 (or anything else, > > for > > that matter) doesn't seem to have an effect on what is sent out in the > > HTTP call. Does the alt-charset directive work with HTTP SMSCs? > > > > Any help will be greatly appreciated. > > > > Thanks, > > > > Nii. > > > > > > > > > -- Rancard Solutions Ltd Web: www.rancardmobility.com mobile: +233 24 987 9795 office: +233 28 952 9573
