Re: [RFV] late request for voting/vetting for several stuff
wap push is a normal binary sm, so wapbox has concatenation & max-messages parameter. But defaults are 10 segments message, so you do not normally need these parameters. Aarno On Thursday, July 24, 2003, at 12:26 AM, Bruno Rodrigues wrote: Bruno Rodrigues <[EMAIL PROTECTED]> wrote: I should have asked for comments before, but I'm really work-free now and I'd like to implement stuff as fast as I can, even if there's momentary cvs versions with major bugs. forgot another things implemented: wapbox now accepts configuration reloading through SIGHUP, but only to "safe" parameters: http-proxy-*, log-level, smart-errors, concatenation and max-messages (what are these?), old map-url and new url-map/user-map groups I'll do the same to bearerbox and smsbox later
Re: Segmentation Fault Fixes
Jared Odulio wrote: > > Do i need to check out anew from the CVS repository to get the latest > update or I just have to update my existing Kannel code? > > I am still having segmentation fault problems while testing fakesmsc. this has been fixed in cvs. Please update your local tree. Stipe [EMAIL PROTECTED] --- Wapme Systems AG Vogelsanger Weg 80 40470 Düsseldorf Tel: +49-211-74845-0 Fax: +49-211-74845-299 E-Mail: [EMAIL PROTECTED] Internet: http://www.wapme-systems.de --- wapme.net - wherever you are
Re: [RFV] late request for voting/vetting for several stuff
Bruno Rodrigues wrote: > > I should have asked for comments before, but I'm really work-free now > and I'd like to implement stuff as fast as I can, even if there's > momentary cvs versions with major bugs. > > If you can, please test cvs versions as hardly as you can and report > everything you find to this list so I can see if I did something wrong > and be able to fix it right away. > > These are the features I've implemented and after that, a list of stuff > I'm about to fix/implement unless you complain very hard ;) > > I'd like to ear your comments and/or any reason against them. It's still > not too late to rollback anything. > > (Here we go, by your request Stipe) to be more precise: by consensus of the group ;) > 2003.07.07 - header packing implemented > I've implemented this feature to aggregate similar headers because some > devices I have sends so many headers that if we send one header per > value, I get "too many headers", if I aggregate them all in one header, > I get "header too long". > http_header_pack packs headers with 256 characters (defineable) definetly +1. Even while we make a workarround for too tightly confiured HTTP servers. We've seen these problems on various devices too. > 2003.07.13 - wbxml dynamic version byte and wap dynamic version byte > I'm looking at device header sent and I'm setting wbxml version acordly. > I'm looking at wml's externalid declaration and settings wbxml's wap > version acordly. This was required because SE-T610 looks at them and > would ignore some 1.3 tags if version was 1.1 - it won't respect > 2003.07.13 - added wap deconverters to decode > application/vnd.wap.multipart.form-data to multipart/form-data. working +1 > 2003.07.13 - preliminary support to decode mms binary into text. > deconverter is implemented, I'm just waiting for Stipe's commits for his > mms code. +1, it's coming. Let me have my hands on the configure/make process and you will have a bunch of commits here. It's gonna be anyway after 1.3.2 has been released. > 2003.07.13 - preliminary suport for multipart/mixed to > application/vnd.wap.multipart.mixed, on hold until I fix some more > important stuff (and Stipe's mms encoder would also help me) > > 2003.07.13 - kannel now tries to adapt xml/xhtml content's charset to > the one supported by device. Kannel already adds other Accept-Charsets > to request headers, so this looks like a needed feature to me (needs to > be tested with other charsets beside utf8 and iso-8859-1) > Note: Panasonic GAD87 devices (at least in Portugal) became very broken > with this because they are really broken and announce that they only > support utf-8 but they really only support iso-8859-1 - accented chars > are totally mangled. I don't want to make exceptions in kannel and I've > already complained to Panasonic. +1, yep, good way. > 2003.07.13 - removed "Version=0" parameter when sending cookies to > external servers. This is not very explicit in specification but I > haven't ever seen a client sending this parameter +0, ok with me. > 2003.07.14 - added http response 406 back to device if content type is > not supported by it. (today I've fixed the */* problem). This was > required for (at least) Nokia 7650 +1. > 2003.07.18 - smsbox - mo-recode now tries to also recode to utf-8 if iso > fails. for external servers, it's easier to process utf8 than ucs2/utf16 > (documented) +0. > 2003.07.19 - smsbox - dlr won't work at all if smsc-id is undefined - > dlr_add and dlr_find just returns if no smsc-id. smsc-id required for > dlr processing was documented +1 > 2003.07.20 - removed smsc_at, renamed at2 to at; moved emi to emi_x25, > removed internal emi_ip and renamed emi2 to emi, documented it definetly +1. > 2003.07.20 - broken smsbox compatibility to enable mclass=0..3, > coding=0..2 and pid=0..255. This was already talked about and it's > required to be able to set pid=0 and to be consistent with specification > (it's dificult to explain to someone that for etsi's message class 0 you > need to set kannel's mclass to 1) yep, +1. Did you test all dependencies on this?! > 2003.07.20 - added hplmn and auth-code support, although not yet > implemented on smsc_emi (bug #54) ?? (have to check mantis) > 2003.07.20 - maintained parameter consistency and always use urlencoding > for udh and binary data in POST headers and in xml. I had several > complains because common sense will make you send url-encode in http > udh header and then you ask yourself why is it not working ??? (didn't get the point. too less coffee this morning? ;)) > 2003.07.21 - made wap cookies enable per default. Please complain about > what is not working with them so I can fix it. So far, I know, and I'm > working thowards it, that we should try to send cookies to device > (bug 34), that cookies are not checked for domain, path and secure (bug > 64), and that they might not work at all with connectionless wap. > I need cookie support and I'd rather activa
Re: wap push si/sl
Bruno Is there an issue with contrib/web/form.php? Running it here from the nightly snapshot it gives Warning: Variable passed to each() is not an array or object in /.../form.php on line 294 Alex - Original Message - From: "Bruno Rodrigues" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Tuesday, July 22, 2003 1:57 AM Subject: Re: wap push si/sl > Robin <[EMAIL PROTECTED]> wrote: > > Hi All, > > > > When i did a wap push via commandline "./test_ppg -q > > http://127.0.0.1:8080/wappush?username=f00'&'password=f00 ./content.xml > > ./control.xml", it works perfectly fine. > > But when i tried contrib/web/sendsms.php wap push si/sl, it doesn't work. > > My fault ;) > > Wap Push SI code includes an hardcoded validity date way back in the > past (2002). > > please apply this patch or update from cvs > > (just commenting those two lines with dates is enough) > > > Index: contrib/web/sendsms.php > === > RCS file: /home/cvs/gateway/contrib/web/sendsms.php,v > retrieving revision 1.1 > retrieving revision 1.2 > diff -u -3 -p -r1.1 -r1.2 > --- contrib/web/sendsms.php 26 Feb 2002 00:04:57 - 1.1 > +++ contrib/web/sendsms.php 22 Jul 2003 00:56:52 - 1.2 > @@ -236,8 +236,8 @@ > $fields['text'] .= "%0b" . "%03" . $fields['url'] . "%00"; > # href=$url > $fields['text'] .= "%11" . "%03" . rand(1,9)."@vodafone.pt" . > "%00";# si-id= > $fields['text'] .= "%08"; # action="signal-high" > - $fields['text'] .= "%0A" . "%C3%07%20%01%10%21%20%02%23"; # > created= > - $fields['text'] .= "%10" . "%C3%04%20%02%06%30"; # valid= > + #$fields['text'] .= "%0A" . "%C3%07%20%01%10%21%20%02%23"; # > created= > + #$fields['text'] .= "%10" . "%C3%04%20%02%06%30"; # valid= > $fields['text'] .= "%01"; # end indication params > $fields['text'] .= "%03" . urlencode($fields['name']). "%00"; >$fields['text'] .= "%01"; # >
sorry to all ! it's a italian problem with operator MMSC !!
hi to all ! (sorry for my english !...;-)) the fact that later the notify , i was not able to take the mms file on my server web ,depends on the fact that the italian operator not permit this operation !(MMSC that takes the file from my server and send it to the destination phone) sorry for my insistence on finding a solution ! but now how I do? if i can send the mms notify with smswith more sms, can i send a mms "m-send" ?(whit text and image in the same packet wsp ) if I codify the Headers of m-send instead of m-notification.ind can i send a paket mms directly with the contents ? do you have any advice on the new way that i can test ? Email.it, the professional e-mail, gratis per te: clicca qui Sponsor: DVD, libri, cibi e bevande, cosmesi, prodotti erboristici, articoli per lo sport, cellulari e PC...tutto a prezzi scontatissimi,Clicca qui Clicca qui
Re: sorry to all ! it's a italian problem with operator MMSC !!
> (sorry for my english !...;-)) > the fact that later the notify , i was not able to take the mms > file on my server web ,depends on the fact that the italian operator > not permit this operation !(MMSC that takes the file from my server > and send it to the destination phone) > sorry for my insistence on finding a solution ! > > but now how I do? > > if i can send the mms notify with smswith more sms, can i send a > mms "m-send" ?(whit text and image in the same packet wsp ) no, you can't use SMS as bearer for transmitting m.send-req (at least I never ever have seen this). And imagine how many SMS you must send to concatenate a 20 kb MMS. > if I codify the Headers of m-send instead of m-notification.ind can > i send a paket mms directly with the contents ? I don't think that any device will recognize the M-send.req PDU. But you *may* try. > do you have any advice on the new way that i can test ? I still didn't get exactly what you are trying to do. Can you please explain more briefly. Stipe [EMAIL PROTECTED] --- Wapme Systems AG Vogelsanger Weg 80 40470 Düsseldorf Tel: +49-211-74845-0 Fax: +49-211-74845-299 E-Mail: [EMAIL PROTECTED] Internet: http://www.wapme-systems.de --- wapme.net - wherever you are
Re: [RFV] late request for voting/vetting for several stuff
Aarno Syvänen <[EMAIL PROTECTED]> wrote: > wap push is a normal binary sm, so wapbox has concatenation & > max-messages parameter. But defaults are 10 segments message, > so you do not normally need these parameters. Then plese either add it to documentation or add a comment to code like "this is not needed and should not be documented" or something
Re: [RFV] late request for voting/vetting for several stuff
Stipe Tolj <[EMAIL PROTECTED]> wrote: > Bruno Rodrigues wrote: >> >> 2003.07.07 - header packing implemented >> I've implemented this feature to aggregate similar headers because some >> devices I have sends so many headers that if we send one header per >> value, I get "too many headers", if I aggregate them all in one header, >> I get "header too long". >> http_header_pack packs headers with 256 characters (defineable) > > definetly +1. Even while we make a workarround for too tightly > confiured HTTP servers. We've seen these problems on various devices > too. I don't think it's a HTTP server problem. I have devices that sends way too many headers (more than 30 accepts if I remember) and a Cisco "alteon alike" just dropped my connection with those many headers. I guess what we are doing now is the right thing. ;) >> 2003.07.13 - wbxml dynamic version byte and wap dynamic version byte >> I'm looking at device header sent and I'm setting wbxml version acordly. >> I'm looking at wml's externalid declaration and settings wbxml's wap >> version acordly. This was required because SE-T610 looks at them and >> would ignore some 1.3 tags if version was 1.1 - it won't respect >> > so this fixed the 'multipart/form-data' thing for SE? Yep, SE looked at wml-1.1 and POST'ed with appl/x-www-urlencoded. As soon as I set wml1.3, it POST's with right appl/mult.form-data. >> 2003.07.13 - preliminary support to decode mms binary into text. >> deconverter is implemented, I'm just waiting for Stipe's commits for his >> mms code. > > +1, it's coming. Let me have my hands on the configure/make > process and you will have a bunch of commits here. It's gonna be > anyway after 1.3.2 has been released. No problem to me. Code is commented and MMS in and out and multipart/mixed will be implemented only after 1.3.2 >> 2003.07.13 - removed "Version=0" parameter when sending cookies to >> external servers. This is not very explicit in specification but I >> haven't ever seen a client sending this parameter > > +0, ok with me. Anyway, $=value parameters are ignored anyway, so my removal shouldn't make any change. >> 2003.07.18 - smsbox - mo-recode now tries to also recode to utf-8 if iso >> fails. for external servers, it's easier to process utf8 than ucs2/utf16 >> (documented) > > +0. This is important to help our "clients", and besides you'll get a nice string text in logs instead of a 00xx00xx00xx... ;) >> 2003.07.20 - broken smsbox compatibility to enable mclass=0..3, >> coding=0..2 and pid=0..255. This was already talked about and it's >> required to be able to set pid=0 and to be consistent with specification >> (it's dificult to explain to someone that for etsi's message class 0 you >> need to set kannel's mclass to 1) > > yep, +1. Did you test all dependencies on this?! I've done some tests with at(2) (I was at home), which tested smsbox code and sms.c code (fields<->dcs), so it should work with all the others. SMAPI is using directly sms.mclass and other parameters, but I guess I've also fixed it. In my to-do queue there is a complete review of fakesms and http, so I'll later check out if both are working ok. >> 2003.07.20 - added hplmn and auth-code support, although not yet >> implemented on smsc_emi (bug #54) > > ?? (have to check mantis) These are only two more parameters which I've added to smsbox but forgot to add to smsc_emi2. bug 54 is to remember me to add it in there ;) >> 2003.07.20 - maintained parameter consistency and always use urlencoding >> for udh and binary data in POST headers and in xml. I had several >> complains because common sense will make you send url-encode in http >> udh header and then you ask yourself why is it not working > > ??? (didn't get the point. too less coffee this morning? ;)) in query-string, udh=%xx%yy%zz. In http headers, you use udh=xxyyzz, in my xml was more or less undefined (i guess it was xxyyzz). It's better to be consistent and always use urlencode. This is easily rollbacked (it's two lines) and I'd really like to ear comments about this. >> 2003.07.21 - made wap cookies enable per default. Please complain about >> what is not working with them so I can fix it. So far, I know, and I'm >> working thowards it, that we should try to send cookies to device >> (bug 34), that cookies are not checked for domain, path and secure (bug >> 64), and that they might not work at all with connectionless wap. >> I need cookie support and I'd rather activate it and fix it. > > +1, we have to work on passing the Cookies in WSP encoding to the > device. I'm first fixing cookie domain/path support and then I'll do this. >> 2003.07.23 - added new url-map groups (deprecating map-url directives) >> to enable, for each url, an rewriten url, a query-string parameter to >> send msisdn, an header to send msisdn, an msisdn format and if kannel >> accepts cookies or not. This is required for Telcos to enable msisdn >> sending and cookie support only
Re: wap push si/sl
Alex Judd <[EMAIL PROTECTED]> wrote: > Bruno > > Is there an issue with contrib/web/form.php? Running it here from the > nightly snapshot it gives > > Warning: Variable passed to each() is not an array or object in > /.../form.php on line 294 no changes in that code in cvs. 294 uses an array with a $mode parameter. please check in your web interface what is said after "Sendsms " and check if that mode is found in $aModeFields = array( "somemode" => ...")
Re: mmsc problem
hi, i'm working on degree thesis (engineering of tlc) on the vigilance display over IP. My task is take alarm images ,put them in a package MMS and send to client with notification message with kannel. (you are right on the dimension of the Msg, it is not a feasible way...I thought of an only little image ..but also is not good idea) if with the notification can't retrive the mms on web server (italian mmsc don't permit .)now i have one possibility ..create a packet m-send..or..i can create my mmsc!(it's possible ?)and so i can use notification with success..but configuration of terminal mobile problems arise... what you suggest me ? > > (sorry for my english !...;-)) > > the fact that later the notify , i was not able to take the mms > > file on my server web ,depends on the fact that the italian operator > > not permit this operation !(MMSC that takes the file from my server > > and send it to the destination phone) > > sorry for my insistence on finding a solution ! > > > > but now how I do? > > > > if i can send the mms notify with smswith more sms, can i send a > > mms "m-send" ?(whit text and image in the same packet wsp ) > > no, you can't use SMS as bearer for transmitting m.send-req (at least > I never ever have seen this). > > And imagine how many SMS you must send to concatenate a 20 kb MMS. > > > if I codify the Headers of m-send instead of m-notification.ind can > > i send a paket mms directly with the contents ? > > I don't think that any device will recognize the M-send.req PDU. But > you *may* try. > > > do you have any advice on the new way that i can test ? > > I still didn't get exactly what you are trying to do. Can you please > explain more briefly. > > Stipe Email.it, the professional e-mail, gratis per te: clicca qui Sponsor: Stai cercando una casella di posta professionale senza pubblicità e senza scadenza? Quello che fa per te è Email.it Po15, Pro50 o Pro100, ordinala subito, è proprio forte! Clicca qui
Re: [RFV] late request for voting/vetting for several stuff
Bruno Rodrigues wrote: > > I don't think it's a HTTP server problem. I have devices that sends way > too many headers (more than 30 accepts if I remember) and a Cisco > "alteon alike" just dropped my connection with those many headers. > > I guess what we are doing now is the right thing. ;) hmmm, yeah maybe. AFAIR there is no hard limit in RFC2818 (HTTP/1.1) for *how many* accept headers are allowed to be passed. > Yep, SE looked at wml-1.1 and POST'ed with appl/x-www-urlencoded. As > soon as I set wml1.3, it POST's with right appl/mult.form-data. ahh. > >> 2003.07.18 - smsbox - mo-recode now tries to also recode to utf-8 if iso > >> fails. for external servers, it's easier to process utf8 than ucs2/utf16 > >> (documented) > > > > +0. > > This is important to help our "clients", and besides you'll get a nice > string text in logs instead of a 00xx00xx00xx... ;) agreed. > >> 2003.07.20 - broken smsbox compatibility to enable mclass=0..3, > >> coding=0..2 and pid=0..255. This was already talked about and it's > >> required to be able to set pid=0 and to be consistent with specification > >> (it's dificult to explain to someone that for etsi's message class 0 you > >> need to set kannel's mclass to 1) > > > > yep, +1. Did you test all dependencies on this?! > > I've done some tests with at(2) (I was at home), which tested smsbox > code and sms.c code (fields<->dcs), so it should work with all the > others. > SMAPI is using directly sms.mclass and other parameters, but I guess > I've also fixed it. we'll see as soon as we update our production server that run some SM/ASI links ;) > >> 2003.07.20 - maintained parameter consistency and always use urlencoding > >> for udh and binary data in POST headers and in xml. I had several > >> complains because common sense will make you send url-encode in http > >> udh header and then you ask yourself why is it not working > > > > ??? (didn't get the point. too less coffee this morning? ;)) > > in query-string, udh=%xx%yy%zz. In http headers, you use udh=xxyyzz, in > my xml was more or less undefined (i guess it was xxyyzz). It's better > to be consistent and always use urlencode. This is easily rollbacked > (it's two lines) and I'd really like to ear comments about this. have to check, but in general I'm a fan of consitency ;) > >> 2003.07.21 - made wap cookies enable per default. Please complain about > >> what is not working with them so I can fix it. So far, I know, and I'm > >> working thowards it, that we should try to send cookies to device > >> (bug 34), that cookies are not checked for domain, path and secure (bug > >> 64), and that they might not work at all with connectionless wap. > >> I need cookie support and I'd rather activate it and fix it. > > > > +1, we have to work on passing the Cookies in WSP encoding to the > > device. > > I'm first fixing cookie domain/path support and then I'll do this. ok. Stipe [EMAIL PROTECTED] --- Wapme Systems AG Vogelsanger Weg 80 40470 Düsseldorf Tel: +49-211-74845-0 Fax: +49-211-74845-299 E-Mail: [EMAIL PROTECTED] Internet: http://www.wapme-systems.de --- wapme.net - wherever you are
Re: wap push si/sl
That error arises because the php installation has register_globals = Off in php.ini If you add this to the top of sendsms.php, you should be fine. Bruno > > Is there an issue with contrib/web/form.php? Running it here from the > nightly snapshot it gives > > Warning: Variable passed to each() is not an array or object in > /.../form.php on line 294 > *snip* On Thursday, 2003-07-24 at 11:49:15 PM, Bruno Rodrigues scribbled: > Alex Judd <[EMAIL PROTECTED]> wrote: > > Bruno > > > > Is there an issue with contrib/web/form.php? Running it here from the > > nightly snapshot it gives > > > > Warning: Variable passed to each() is not an array or object in > > /.../form.php on line 294 > > no changes in that code in cvs. > > 294 uses an array with a $mode parameter. please check in your web > interface what is said after "Sendsms " and check if that mode > is found in $aModeFields = array( "somemode" => ...") > > -- Benjamin Lee Melbourne, Australia "Always real."http://www.realthought.net/ __ Leveraging always beats prototyping.
