Re: Bug in wsp_server_method_states.def
Hi Pail, I think this code is wrong. /* * The Siemens S35 adds an extra NUL character to the end * of the request body which may not work with certain cgi * scripts. It is removed here by truncating the length. */ req_body_size = octstr_len(pdu-u.Post.data); if(octstr_get_char(pdu-u.Post.data,(req_body_size - 1)) == 0) octstr_truncate(pdu-u.Post.data,(req_body_size - 1)); I posted in an MMS message where the last byte of the encoding was 0. This code truncated the last byte and corrupted the MMS message. I suggest that certain cgi scripts be made more robust rather than hacking bytes out of the lower layers. hmm, did you use a specific handset for this where it corrupts?! This thing works for me with various devices and does not corrupt MMS messages. Can you explain a bit more in details, please?! Stipe mailto:[EMAIL PROTECTED] --- Wapme Systems AG Münsterstr. 248 40470 Düsseldorf, NRW, Germany phone: +49.211.74845.0 fax: +49.211.74845.299 mailto:[EMAIL PROTECTED] http://www.wapme-systems.de/ --- -BEGIN PGP PUBLIC KEY BLOCK- Version: GnuPG v1.2.2 (Cygwin) mIsEP6mcYwEEAMDnUiUwrbb+xwTFWN6TxF2+XZu7/alwJMeCwMBRvXtPZqfjpPhS OkBpU0F4TrVuugz1HINTSaJTYq10AzDQXp5NkyWgckqW79nPAWuOX0dicbJk+cN2 nM2TI4KaxUDe6u8hghNEnH/i2lXsUu9apnP/iixzV81VC2je3uc9hZpnAAYptEVT dGlwZSBUb2xqIChUZWNobm9sb2d5IENlbnRlciAmIFJlc2VhcmNoIExhYikgPHRv bGpAd2FwbWUtc3lzdGVtcy5kZT6ItAQTAQIAHgUCP6mcYwIbAwYLCQgHAwIDFQID AxYCAQIeAQIXgAAKCRABV0w1BqPYRuSqA/wPzsQxao2YePENCtgRTrO86U6zg3sl OcS6CJFI4FZP5h/xD3GRsNH1+MPSvZlomDdpFnr547DGz/Kq9MXuQwVvlVig5yWZ K5dtKp1r5YLhxJQBhfirZbRFFnYmf19f18J8OoS28tuFVftDl1AIwJS3HLyBTv6H g2HyLAEKQIp30Q== =aYCI -END PGP PUBLIC KEY BLOCK-
RE: Latest kannel on RedHat v9 configuration problem
I use http://10.1.1.11:13013/cgi-bin/sendsms?username=smspassword=smsto=98081888 text=ok -Original Message- From: Stipe Tolj [mailto:[EMAIL PROTECTED] Sent: Thursday, February 19, 2004 6:17 PM To: Jan Cc: [EMAIL PROTECTED] Subject: Re: Latest kannel on RedHat v9 configuration problem I have posted on the [EMAIL PROTECTED] but the problem remains - I still cannot send and receive SMS I have a RHv7.2 running gateway v1.0.3 which can send and receive SMS, but I need to send and receive in unicode. I tried but it cannot work. So I install gateway on RHv9. I have tried v1.2.1, v.1.3.1 and the latest snapshot, I still cannot send and receive. If you look at the kannel.log below, it encountered errors when sending a message. Is it a config issue or can the gateway work in RHv9? Please help! Thanks in advance. config looks ok. Seems to be an GSM modem issue. Can you please provide us the sendsms HTTP call that you do while trying to send the message?! Stipe mailto:[EMAIL PROTECTED] --- Wapme Systems AG Münsterstr. 248 40470 Düsseldorf, NRW, Germany phone: +49.211.74845.0 fax: +49.211.74845.299 mailto:[EMAIL PROTECTED] http://www.wapme-systems.de/ --- -BEGIN PGP PUBLIC KEY BLOCK- Version: GnuPG v1.2.2 (Cygwin) mIsEP6mcYwEEAMDnUiUwrbb+xwTFWN6TxF2+XZu7/alwJMeCwMBRvXtPZqfjpPhS OkBpU0F4TrVuugz1HINTSaJTYq10AzDQXp5NkyWgckqW79nPAWuOX0dicbJk+cN2 nM2TI4KaxUDe6u8hghNEnH/i2lXsUu9apnP/iixzV81VC2je3uc9hZpnAAYptEVT dGlwZSBUb2xqIChUZWNobm9sb2d5IENlbnRlciAmIFJlc2VhcmNoIExhYikgPHRv bGpAd2FwbWUtc3lzdGVtcy5kZT6ItAQTAQIAHgUCP6mcYwIbAwYLCQgHAwIDFQID AxYCAQIeAQIXgAAKCRABV0w1BqPYRuSqA/wPzsQxao2YePENCtgRTrO86U6zg3sl OcS6CJFI4FZP5h/xD3GRsNH1+MPSvZlomDdpFnr547DGz/Kq9MXuQwVvlVig5yWZ K5dtKp1r5YLhxJQBhfirZbRFFnYmf19f18J8OoS28tuFVftDl1AIwJS3HLyBTv6H g2HyLAEKQIp30Q== =aYCI -END PGP PUBLIC KEY BLOCK- /---\ Raffles Medical Group (The Company) accepts no liability for the content of this email, or for the consequences of any actions taken on the basis of the information. Any views or opinions presented in this email are solely those of the author and do not necessarily represent those of the Company. The Company will not accept any liability in respect of such communication, and the author responsible will be personally liable for any damages or other liability arising. The recipient should check this email and any attachments for the presence of viruses. The Company accepts no liability for any damage caused by any virus transmitted by this email. This message may contain confidential or legally privileged information and is intended solely for the use of the individual or entity to which it is addressed and others authorized to receive it. If you are not the intended recipient you are hereby notified that any disclosure, copy, distribution or taking action in reliance on the contents of this information is strictly prohibited and may be unlawful. If you have received this communication in error, please notify us immediately, and then delete it from your system. \--/
Re: Bug in wsp_server_method_states.def
Hi, all It is funny, but problem was discussed already in list: http://www.mail-archive.com/[EMAIL PROTECTED]/msg02191.html And we got +1 from Stipe already for fixing this! Paul Keogh wrote: hmm, did you use a specific handset for this where it corrupts?! I don't believe it is handset specific. This thing works for me with various devices and does not corrupt MMS messages. Can you explain a bit more in details, please?! Sure. The MM1 M-Send.req is carried by a WSP POST request which is issued by the device. The MMS message is WBXML encoded, so its quite possible that the last byte of this encoding is 0x00, depending on what the user has put into the MMS message. The offending code in wsp_server_method_states.def looks at the last byte of the POST data and truncates it if it is == 0x00. So the MMS message gets truncated and hence corrupted. I've done a round trip test against an MMSC and the test fails with the code in and succeeds with it out. Anyway, regardless of the scenario, does it make any sense that the WSP layer chops off the last byte of its POST data just because it is == 0x00 ? No, of course it does'nt. -- Vjacheslav Chekushinmailto:[EMAIL PROTECTED] Latvian Mobile Phone Companyhttp://www.lmt.lv VAS Technologies Division +371 7773436 +371 9248284 (mobile)
RE: Bug in wsp_server_method_states.def
LOL, they catched you, Stipe ;-) -Mensaje original- De: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] En nombre de Vjacheslav Chekushin Enviado el: jueves, 19 de febrero de 2004 11:46 Para: [EMAIL PROTECTED] Asunto: Re: Bug in wsp_server_method_states.def Hi, all It is funny, but problem was discussed already in list: http://www.mail-archive.com/[EMAIL PROTECTED]/msg02191.html And we got +1 from Stipe already for fixing this! Paul Keogh wrote: hmm, did you use a specific handset for this where it corrupts?! I don't believe it is handset specific. This thing works for me with various devices and does not corrupt MMS messages. Can you explain a bit more in details, please?! Sure. The MM1 M-Send.req is carried by a WSP POST request which is issued by the device. The MMS message is WBXML encoded, so its quite possible that the last byte of this encoding is 0x00, depending on what the user has put into the MMS message. The offending code in wsp_server_method_states.def looks at the last byte of the POST data and truncates it if it is == 0x00. So the MMS message gets truncated and hence corrupted. I've done a round trip test against an MMSC and the test fails with the code in and succeeds with it out. Anyway, regardless of the scenario, does it make any sense that the WSP layer chops off the last byte of its POST data just because it is == 0x00 ? No, of course it does'nt. -- Vjacheslav Chekushinmailto:[EMAIL PROTECTED] Latvian Mobile Phone Companyhttp://www.lmt.lv VAS Technologies Division +371 7773436 +371 9248284 (mobile)
