Re: Adding support for OMA-WAP Provisioning OTA
The phones mentioned probably do *not* use WAP provisioning. But some Siemenses actually do, I remember. Do someone know what Siemens models do ? Btw, I agree with Stipe that code *looks* good. But it is code you definitely must test first (all these tokenization rules). Aarno On 12.3.2004, at 15:51, Stipe Tolj wrote: Paul Bagyenda schrieb: Attached are some diffs to implement OMA-style sending of OTA settings. Refer to OMA-WAP-ProvCont-v1_1-20021112-C (at http://www.openmobilealliance.org/tech/docs/) for details on how this works. The changes include all (most) the HMAC computation stuff required for authentication. What I've done is modified the ota_compiler.c and ota_prov.c files to detect oma-style settings and build the WBXML file differently. I've checked its output against samples provided in the docs and against samples provided by SonyEricsson, Nokia & Motorola. Looks ok. Alas my phone seems to be having issues so I haven't received anything there yet. If someone out there can test and confirm, then we have a new addition to kannel! Aarno will give it a try and review. Can you please describe in more detail what the patch does actually in Kannel's components, so the reviewer has a more easier way to check the patch and understand your changes. Thanks. 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: Backtrace of crash
> So wapbox log at debug level (level 0), with configured Kannel > --with-defaults=debug would be useful. Well. Maybe I found something. Before crash I'm getting the message "WARNING: WTP: got a truncated datagram, ignoring". Lines 130-131 contains the following code: event = unpack_wdp_datagram_real(subdgram); wap_event_assert(event); And unpack_wdp_datagram_read returns NULL if it detects truncated datagram. Without assertions the wapbox crashes by trying to access event->type in wap/wap_events.c line 222. How to fix that? Mindaugas
Question about Set-Cookie encoding
Hi, list. I've encode Set-Cookie header as specified in WSP (encoding-version 1.3): c1 - Set-Cookie header 0e - value-length 9f - version (1) 74 t 65 e 73 s 74 t 00 73 s 73 s 73 s 73 s 73 s 73 s 73 s 00 (From WSP: Set-Cookie-value = Value-length Cookie-version Cookie-name Cookie-val *Parameter Cookie-version = Version-value Cookie-name = Text-string Cookie-val = Text-string) But seems phone does not accept it. (At least it does not send Cookie header back to server) I can't find out where I am wrong. Test phone is SonyEricsson t68i and it accepts encoding version 1.3 -- Vjacheslav Chekushinmailto:[EMAIL PROTECTED] Latvian Mobile Phone Companyhttp://www.lmt.lv VAS Technologies Division
Re: Question about Set-Cookie encoding
Vjacheslav Chekushin wrote: > > Hi, list. > > I've encode Set-Cookie header as specified in WSP (encoding-version 1.3): > > c1 - Set-Cookie header > 0e - value-length > 9f - version (1) > 74 t > 65 e > 73 s > 74 t > 00 > 73 s > 73 s > 73 s > 73 s > 73 s > 73 s > 73 s > 00 > > (From WSP: > Set-Cookie-value = Value-length Cookie-version Cookie-name Cookie-val *Parameter > Cookie-version = Version-value > Cookie-name = Text-string > Cookie-val = Text-string) > > But seems phone does not accept it. (At least it does not send Cookie header > back to server) > > I can't find out where I am wrong. > > Test phone is SonyEricsson t68i and it accepts encoding version 1.3 did you ask the Ericsson developer's zone (where some of the staff is answering) if the phone is able to do the operation? AFAIK, even while phones indicate specific encoding versions, that *does not* mean they have all the sets implemented. Is the set-cookie feature in encoding version 1.3 optional or mandatory according to the WSP specs and unit conformance documents?! 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: Question about Set-Cookie encoding
Hi, Stipe. No, I didn't ask. But if phone states in connect PDU that it supports version-encoding 1.3, then, I think, it must support this version. And Set-Cookie header is in the 1.3 header subset. I'll try to get some other phones that works with 1.3. Stipe Tolj wrote: did you ask the Ericsson developer's zone (where some of the staff is answering) if the phone is able to do the operation? AFAIK, even while phones indicate specific encoding versions, that *does not* mean they have all the sets implemented. Is the set-cookie feature in encoding version 1.3 optional or mandatory according to the WSP specs and unit conformance documents?! -- Vjacheslav Chekushinmailto:[EMAIL PROTECTED] Latvian Mobile Phone Companyhttp://www.lmt.lv VAS Technologies Division
Re: Question about Set-Cookie encoding
Vjacheslav Chekushin schrieb: > > Hi, Stipe. > No, I didn't ask. > But if phone states in connect PDU that it supports version-encoding 1.3, > then, I think, it must support this version. > And Set-Cookie header is in the 1.3 header subset. > I'll try to get some other phones that works with 1.3. I could offer a request with an SE P800 on your Kannel instance to check?! 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: Backtrace of crash
NULL pointer should be tested before anything else and handled separately (by just ignoring it) But: where does this truncated datagram come from ? can you dump it ? Aarno On 15.3.2004, at 13:40, Mindaugas Riauba wrote: So wapbox log at debug level (level 0), with configured Kannel --with-defaults=debug would be useful. Well. Maybe I found something. Before crash I'm getting the message "WARNING: WTP: got a truncated datagram, ignoring". Lines 130-131 contains the following code: event = unpack_wdp_datagram_real(subdgram); wap_event_assert(event); And unpack_wdp_datagram_read returns NULL if it detects truncated datagram. Without assertions the wapbox crashes by trying to access event->type in wap/wap_events.c line 222. How to fix that? Mindaugas
Re: Question about Set-Cookie encoding
Hi, Stipe. Thank for advice, I got SE P900 (it supports even 1.4) And it processed encoded cookie successfully. So I hope that my packing code is ok. Stipe Tolj wrote: Vjacheslav Chekushin schrieb: Hi, Stipe. No, I didn't ask. But if phone states in connect PDU that it supports version-encoding 1.3, then, I think, it must support this version. And Set-Cookie header is in the 1.3 header subset. I'll try to get some other phones that works with 1.3. I could offer a request with an SE P800 on your Kannel instance to check?! Stipe -- Vjacheslav Chekushinmailto:[EMAIL PROTECTED] Latvian Mobile Phone Companyhttp://www.lmt.lv VAS Technologies Division
HTTP API
Anyone using a SMS Center that you connect via HTTP only from Kannel. I am trying to get SMSgui.com working using their HTTP API. r.b.
Re: HTTP API
Hi Richard, Richard Bottoms wrote: > > Anyone using a SMS Center that you connect via HTTP only from Kannel. I am > trying to get SMSgui.com working using their HTTP API. yes, we at Wapme/Centrium have several of those running here. Some are (ie. brunet, xidris) are implemented as seperatate 'type' in the gw/smsc/smsc_http.c module. We could add smsgui.com too, in case you can provide us the API. 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: HTTP API
Hi, I'm a programmer from Croatia and I'm using Kannel in few projects here in Croatia. We've also developed a web2SMS page www.infobiiip.com (similar to smsgui.com).We support HTTP as well as SOAP (web service). If someone is interested in colaboration can contact me at this email. Thank you very much and have a nice day . Silvio Kutic - Original Message - From: "Stipe Tolj" <[EMAIL PROTECTED]> To: "Richard Bottoms" <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Monday, March 15, 2004 4:52 PM Subject: Re: HTTP API > Hi Richard, > > Richard Bottoms wrote: > > > > Anyone using a SMS Center that you connect via HTTP only from Kannel. I am > > trying to get SMSgui.com working using their HTTP API. > > yes, we at Wapme/Centrium have several of those running here. Some are > (ie. brunet, xidris) are implemented as seperatate 'type' in the > gw/smsc/smsc_http.c module. > > We could add smsgui.com too, in case you can provide us the API. > > 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- > > > __ NOD32 1.629 (20040220) Information __ > > This message was checked by NOD32 Antivirus System. > http://www.nod32.com > >
WTLS support in Kannel
Title: Message Hi, I just joined this mailing list, don't know if it is active, but I have a question about Kannel. It seems from the website that WTLS support will be added this May to Kannel, but it's not clear. So my questions is: does anyone know the status of WTLS support and when it will be available in Kannel? Thanks, Gummi Gudmundur "Gummi" HafsteinssonMIT Sloan - MBA Class of 2005[EMAIL PROTECTED] - +1-781-588-5588 "The higher you go in a company, the less oxygen there is, so supporting intelligent life becomes difficult." - Guy Kawasaki
Re: Adding support for OMA-WAP Provisioning OTA
Hi, I have located a phone that should work, so I can test and finalise before you begin working on integration. Will get back to you. P. - Paul A. Bagyenda Digital Solutions P.O.Box 23833 58 Bukoto Str. Kampala, UGANDA Tel: +256-31-262117 Mob: +256-77-507743 Email: [EMAIL PROTECTED] Web: http://www.dsmagic.com -
Re: Backtrace of crash
> NULL pointer should be tested before anything else > and handled separately (by just ignoring it) > But: > where does this truncated datagram come from ? > can you dump it ? OK. But can we split this problem into two? First - can you provide the patch to ignore such message. Second - what function can I use to dump that datagram? Thanks, Mindaugas
Re: Question about Set-Cookie encoding
Hi. It is funny how my SE P900 encode version-value in Cookie header: Version "0" it encodes as octet 80 (instead of "30 00") Version "1" it encodes as octet 81 (instead of "9F") Vjacheslav Chekushin wrote: Hi, Stipe. Thank for advice, I got SE P900 (it supports even 1.4) And it processed encoded cookie successfully. So I hope that my packing code is ok. Stipe Tolj wrote: Vjacheslav Chekushin schrieb: Hi, Stipe. No, I didn't ask. But if phone states in connect PDU that it supports version-encoding 1.3, then, I think, it must support this version. And Set-Cookie header is in the 1.3 header subset. I'll try to get some other phones that works with 1.3. I could offer a request with an SE P800 on your Kannel instance to check?! Stipe -- Vjacheslav Chekushinmailto:[EMAIL PROTECTED] Latvian Mobile Phone Companyhttp://www.lmt.lv VAS Technologies Division