Hi Falko,, Thanks for your comments, I tried what you said and I get
2009-05-08 02:09:50 [5317] [3] ERROR: Failed to convert string from <UTF-8> to <UTF-8>, errno was <84> 2009-05-08 02:09:50 [5317] [3] DEBUG: Found an invalid multibyte sequence at position <0> 2009-05-08 02:09:50 [5317] [3] DEBUG: Status: 400 Answer: <Charset or body misformed, rejected> My URL: http://localhost:13014/cgi-bin/sendsms?username=test3&password=test3&from=ELTON&to=355672509006&text= £&coding=0&charset=UTF-8 But when I send: http://localhost:13014/cgi-bin/sendsms?username=test3&password=test3&from=ELTON&to=355672509006&text=$&coding=0&charset=UTF-8 The message is delivered properly. I think both £(pound) and $(dollar) are in the alphabet Any clue? Regards Elton On Fri, May 8, 2009 at 9:22 AM, Falko Ziemann <fal...@gmail.com> wrote: > Unimportant...Your http-client (if you write some script in .NET it is > also a http-client, just a very personal one) states the encoding while > connecting and that is the one you must use. That has nothing to do with > coding! > > See: > you send UTF-8 string to kannel with coding=0. Than kannel takes the UTF-8 > string an makes it GSM. But if you already send a GSM string, and your > http-function tells kannel it is UTF-8 and kannel tries to make GSM out of > it everything gets messed up. You do too much of the work that kannel wants > to do. Just take the normal string and do an url_encode function (don't know > how it is called in .NET) on it and pass it to kannel. Kannel and the > compiler will do the job for you. > > Regards > Falko > > Am 08.05.2009 um 08:58 schrieb Elton Hoxha: > > LEts forget about HTTP Client. When I call send-sms from .NET service, what > is the procedure of encoding that suits for kannel? > > Regards > Elton > > On Fri, May 8, 2009 at 8:19 AM, Elton Hoxha <elt...@gmail.com> wrote: > >> Thanks Jyoti, I will give it a try. >> >> Falko, If I use UTF-8 in URL, it should be used with coding = 1, which >> cause that the content will be delivered in unreadable format for the >> mobile. Otherwise, If I use ISO-8859-1, i should add coding=2 which encodes >> it in 16-bit (the characters are normally delivered) but I reduce the bytes >> having only 70 characters. >> >> Regards >> elton >> >> >> On Fri, May 8, 2009 at 7:35 AM, Falko Ziemann <fal...@gmail.com> wrote: >> >>> Elton, >>> please read my last mail again. >>> You must not encode the text in the sendsms URL in gsm! You must send the >>> text to kannel in the encoding the http-client tells kannel which >>> characterset it uses, so mostly UTF-8 or Iso-Latin >>> >>> Regards >>> Falko >>> >>> Am 07.05.2009 um 16:18 schrieb Elton Hoxha: >>> >>> SMPP configuration is simple, I think everybody has it like this >>> >>> group=smsc >>> smsc=smpp >>> smsc-id=internal1 >>> interface-version=34 >>> host=10.x.x.x >>> port=1600 >>> system-id=test >>> smsc-password=test >>> system-type=test >>> transceiver-mode=false >>> address-range=7070 >>> >>> Can anyone please who is able to send these kind of characters (for >>> example @), paste me the smpp configuration or the send-sms url that is used >>> with the required parameters? >>> >>> Regards >>> Elton >>> >>> >>> On Thu, May 7, 2009 at 1:48 PM, Jovan Kostovski <chomb...@gmail.com>wrote: >>> >>>> On Thu, May 7, 2009 at 1:26 PM, Elton Hoxha <elt...@gmail.com> wrote: >>>> > I checked many many times, kannel is sending empty message when i type >>>> these >>>> > special characters. I traced by ethereal the smpp block and there is >>>> no text >>>> > forwarded by kannel to SMSC. Also there is no ascii configuration in >>>> SMSC >>>> > just GSM alphabet. >>>> > >>>> > Strange anyway here is the debug >>>> >>>> Can you send your configuration and the way you are sending the message >>>> so someone which has SMPP connection with a SMSC can reproduce this >>>> situation? >>>> >>>> BR, Jovan >>>> >>> >>> >>> >> > >
