I tried this: http://10.1.21.137:13014/cgi-bin/sendsms?username=test3&password=test3&from=ELTON&to=355672509006&text=%C3%A9&coding=0 character is transformed again in kannel
Debug logs: 2009-05-08 03:50:23 [5641] [3] INFO: smsbox: Got HTTP request </cgi-bin/sendsms> from <10.1.21.146> 2009-05-08 03:50:23 [5641] [3] INFO: sendsms used by <test3> 2009-05-08 03:50:23 [5641] [3] INFO: sendsms sender:<test3:ELTON> (10.1.21.146) to:<355672509006> msg:<é> 2009-05-08 03:50:23 [5641] [3] DEBUG: Stored UUID 531b8b7e-526b-4605-b0bf-79f8faf91854 2009-05-08 03:50:23 [5641] [3] DEBUG: message length 2, sending 1 messages 2009-05-08 03:50:23 [5641] [3] DEBUG: Status: 202 Answer: <Sent.> 2009-05-08 03:50:23 [5641] [3] DEBUG: Delayed reply - wait for bearerbox 2009-05-08 03:50:23 [5632] [9] DEBUG: boxc_receiver: sms received 2009-05-08 03:50:23 [5632] [9] DEBUG: send_msg: sending msg to box: <10.1.21.137> 2009-05-08 03:50:23 [5641] [0] DEBUG: Got ACK (0) of 531b8b7e-526b-4605-b0bf-79f8faf91854 2009-05-08 03:50:23 [5641] [0] DEBUG: HTTP: Resetting HTTPClient for `10.1.21.146'. 2009-05-08 03:50:23 [5632] [6] DEBUG: SMPP[internal2]: Sending PDU: 2009-05-08 03:50:23 [5632] [6] DEBUG: SMPP PDU 0x99d2650 dump: 2009-05-08 03:50:23 [5632] [6] DEBUG: type_name: submit_sm 2009-05-08 03:50:23 [5632] [6] DEBUG: command_id: 4 = 0x00000004 2009-05-08 03:50:23 [5632] [6] DEBUG: command_status: 0 = 0x00000000 2009-05-08 03:50:23 [5632] [6] DEBUG: sequence_number: 127 = 0x0000007f 2009-05-08 03:50:23 [5632] [6] DEBUG: service_type: NULL 2009-05-08 03:50:23 [5632] [6] DEBUG: source_addr_ton: 5 = 0x00000005 2009-05-08 03:50:23 [5632] [6] DEBUG: source_addr_npi: 0 = 0x00000000 2009-05-08 03:50:23 [5632] [6] DEBUG: source_addr: "ELTON" 2009-05-08 03:50:23 [5632] [6] DEBUG: dest_addr_ton: 2 = 0x00000002 2009-05-08 03:50:23 [5632] [6] DEBUG: dest_addr_npi: 1 = 0x00000001 2009-05-08 03:50:23 [5632] [6] DEBUG: destination_addr: "355672509006" 2009-05-08 03:50:23 [5632] [6] DEBUG: esm_class: 3 = 0x00000003 2009-05-08 03:50:23 [5632] [6] DEBUG: protocol_id: 0 = 0x00000000 2009-05-08 03:50:23 [5632] [6] DEBUG: priority_flag: 0 = 0x00000000 2009-05-08 03:50:23 [5632] [6] DEBUG: schedule_delivery_time: NULL 2009-05-08 03:50:23 [5632] [6] DEBUG: validity_period: NULL 2009-05-08 03:50:23 [5632] [6] DEBUG: registered_delivery: 0 = 0x00000000 2009-05-08 03:50:23 [5632] [6] DEBUG: replace_if_present_flag: 0 = 0x00000000 2009-05-08 03:50:23 [5632] [6] DEBUG: data_coding: 0 = 0x00000000 2009-05-08 03:50:23 [5632] [6] DEBUG: sm_default_msg_id: 0 = 0x00000000 2009-05-08 03:50:23 [5632] [6] DEBUG: sm_length: 1 = 0x00000001 2009-05-08 03:50:23 [5632] [6] DEBUG: short_message: 2009-05-08 03:50:23 [5632] [6] DEBUG: Octet string at 0x99d2fd0: 2009-05-08 03:50:23 [5632] [6] DEBUG: len: 1 2009-05-08 03:50:23 [5632] [6] DEBUG: size: 3 2009-05-08 03:50:23 [5632] [6] DEBUG: immutable: 0 2009-05-08 03:50:23 [5632] [6] DEBUG: data: 05 . 2009-05-08 03:50:23 [5632] [6] DEBUG: Octet string dump ends. On Fri, May 8, 2009 at 11:17 AM, Falko Ziemann <fal...@gmail.com> wrote: > No?! é is %C3%A9 in UTF-8. é is %E9 in RAW encoding. > http://kellyjones.netfirms.com/webtools/ascii_utf8_table.shtml > > Regards > Falko > > Am 08.05.2009 um 10:49 schrieb Elton Hoxha: > > I got this error > > 2009-05-08 02:49:48 [5641] [3] INFO: sendsms sender:<test3:ELTON> > (10.1.21.146) to:<355672509006> msg:<é> > 2009-05-08 02:49:48 [5641] [3] DEBUG: Stored UUID > 73f6686e-e184-4e3d-986b-32fb88d30878 > 2009-05-08 02:49:48 [5641] [3] WARNING: Incomplete UTF-8 char discovered, > skipped. 2 > 2009-05-08 02:49:48 [5641] [3] WARNING: Incomplete UTF-8 char discovered, > skipped. 2 > 2009-05-08 02:49:48 [5641] [3] WARNING: Incomplete UTF-8 char discovered, > skipped. 2 > > Then the character comes empty instead of %E9 (in send-sms url) which is é > > > > On Fri, May 8, 2009 at 10:00 AM, Falko Ziemann <fal...@gmail.com> wrote: > >> Don't set the charset!!!You there define the output charset, not the >> input charset and charset UTF-8 with coding 0 is ... well ... >> >> The UTF-8 is NOT defined in the URL, your http-client/scipt/whatever >> defines it for itself in the HTTP-header. Put all that stuff away, just send >> this: >> >> >> <http://localhost:13014/cgi-bin/sendsms?username=test3&password=test3&from=ELTON&to=355672509006&text=> >> >> >> >> http://localhost:13014/cgi-bin/sendsms?username=test3&password=test3&from=ELTON&to=355672509006&text= >> %24%40&coding=0 >> >> >> That should bring you a sms containing a $ (dollar) and a @ (at) >> >> Regards >> Falko >> >> Am 08.05.2009 um 09:43 schrieb Elton Hoxha: >> >> 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 >>>>>> >>>>> >>>>> >>>>> >>>> >>> >>> >> >> > >
