Re: [FYI] Adding delivery reports to ppg
Aarno Syvänen wrote: > > i now have code for ppg delivery reports. It use dlr-url and drl-mask, > quite normal Kannel style. > But there is one thing: dlrs are delivered by smsbox, so the use must > define one. And there > must be smsbox-id defined for smsbox sending the dlrs and service-name > for ppg (smsbox > will names). > > However, I think it is better that smsbox sends the delivery reports in > all cases. Only wap over > sms would merit wapbox handling of mo sms. great Aarno. Can you post the patch to the list before commiting please. 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
[FYI] Adding delivery reports to ppg
Hi List, i now have code for ppg delivery reports. It use dlr-url and drl-mask, quite normal Kannel style. But there is one thing: dlrs are delivered by smsbox, so the use must define one. And there must be smsbox-id defined for smsbox sending the dlrs and service-name for ppg (smsbox will names). However, I think it is better that smsbox sends the delivery reports in all cases. Only wap over sms would merit wapbox handling of mo sms. Aarno
Re: PPG: wap-push-user specific smsc-id config
Bruno Rodrigues wrote: > > Don't we have a "forced-smsc-id" in sendsms ? please use it instead of smsc-id > to maintain consistency ;) yep, that's for the sendsms-user group, *not* for the wap-push-user group. They are not the same. I agree that we may name the "smsc-id" config directive in the wap-push-user group better "force-smsc" in compliance with the same behaviour for the sendsms-user group. 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: PPG: wap-push-user specific smsc-id config
Citando Andreas Fink <[EMAIL PROTECTED]>: > > On Montag, Februar 3, 2003, at 12:52 Uhr, Stipe Tolj wrote: > > > Hi list, Hi Aarno, > a) if &smsc=... is set on the push, use it otherwhise use the one > defined in group=ppg > b) if group wap-push user has a default-smsc-id, use it if &smsc=.. is > not set by step a) > c) if group wap-push user has a smsc-id, discard any already set > smsc-id and force it to the value of the config file. Don't we have a "forced-smsc-id" in sendsms ? please use it instead of smsc-id to maintain consistency ;) --
Re: PPG: wap-push-user specific smsc-id config
Andreas Fink wrote: > > I think both variants make sense. I would actually recommend the following approach: > > a) if &smsc=... is set on the push, use it otherwhise use the one defined in >group=ppg > b) if group wap-push user has a default-smsc-id, use it if &smsc=.. is not set by >step a) > c) if group wap-push user has a smsc-id, discard any already set smsc-id and force >it to the value of the config file. +1, that's the approach I wanted to look like. The problem is the smsc-id value transport accross the function levels. 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: PPG: wap-push-user specific smsc-id config
Hi Stipe & List, PPG keeps push users list for authentication purposes. This list would contain all other user specific information, too. Authentication module should return this data to pap_request_thread. Aarno On Monday, February 3, 2003, at 12:52 PM, Stipe Tolj wrote: Hi list, Hi Aarno, I'm wondering how we can do something like this: (has been discussed already) ... group = ppg ... default-smsc-id = # the default smsc-id to use in bearerbox this is pretty easy, but what about this: ... grou = wap-push-user ... smsc-id = # user specific smsc-id to use this is harder. I don't see any easy way in passing the smsc-id config value of a specific wap-push-user, let's say from gateway/wap_push_ppg.c:655:pap_request_thread() up to gateway/wapbox.c:334:pack_sms_datagram() where the sms splits are send to the bearerbox. Any ideas? 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: PPG: wap-push-user specific smsc-id config
On Montag, Februar 3, 2003, at 12:52 Uhr, Stipe Tolj wrote: Hi list, Hi Aarno, I'm wondering how we can do something like this: (has been discussed already) ... group = ppg ... default-smsc-id = # the default smsc-id to use in bearerbox this is pretty easy, but what about this: ... grou = wap-push-user ... smsc-id = # user specific smsc-id to use this is harder. I don't see any easy way in passing the smsc-id config value of a specific wap-push-user, let's say from gateway/wap_push_ppg.c:655:pap_request_thread() up to gateway/wapbox.c:334:pack_sms_datagram() where the sms splits are send to the bearerbox. I think both variants make sense. I would actually recommend the following approach: a) if &smsc=... is set on the push, use it otherwhise use the one defined in group=ppg b) if group wap-push user has a default-smsc-id, use it if &smsc=.. is not set by step a) c) if group wap-push user has a smsc-id, discard any already set smsc-id and force it to the value of the config file. Andreas Fink Global Networks Switzerland AG -- Tel: +41-61-333 Fax: +41-61-334 Mobile: +41-79-2457333 Global Networks, Inc. Clarastrasse 3, 4058 Basel, Switzerland Web: http://www.global-networks.ch/ [EMAIL PROTECTED] -- Member of the GSM Association
PPG: wap-push-user specific smsc-id config
Hi list, Hi Aarno, I'm wondering how we can do something like this: (has been discussed already) ... group = ppg ... default-smsc-id = # the default smsc-id to use in bearerbox this is pretty easy, but what about this: ... grou = wap-push-user ... smsc-id = # user specific smsc-id to use this is harder. I don't see any easy way in passing the smsc-id config value of a specific wap-push-user, let's say from gateway/wap_push_ppg.c:655:pap_request_thread() up to gateway/wapbox.c:334:pack_sms_datagram() where the sms splits are send to the bearerbox. Any ideas? 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: ppg smsc routing
Andreas Fink wrote: > > On Freitag, Januar 10, 2003, at 08:01 Uhr, Szymon Stasik wrote: > > But would it allow to controll access to aprticular SMSC? eg one wap-push-user >can only access some SMSCs and not some others. > > no this would not be implemented. However this is also not implemented for sms >pushes as far as I remember. You can also use several config files of kannel and run >one kannel instance per user to achieve this. yes you can. At least in theory, reading the user's guide, I haven't tried this. Like this: group = smsc smsc-id = A ... allowed-smsc-id = "A; user_A" group = smsc smsc-id = B ... allowed-smsc-id = "B; user_A" group = sendsms-user username = user_A ... forced-smsc = user_A Hhich means if user_A sends an sms the smsc-id field in the Kannel internal protocoll will be set to user_A. Even while there is no smsc-id 'user_A' configured, you *can* use this in the allowed-smsc-id of an smsc group. (We do this to group Vodafone D2 large accounts to one virutal smsc-id). If you set for smsc-id B an allowed-smsc-id of user_A, then user_A is able to send via A and B. Other smsc-ids may not provide the user_A allowed-smsc-id and hence they never get routed there. Stipe [EMAIL PROTECTED] --- Wapme Systems AG Münsterstr. 248 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: ppg smsc routing
On Freitag, Januar 10, 2003, at 08:01 Uhr, Szymon Stasik wrote: But would it allow to controll access to aprticular SMSC? eg one wap-push-user can only access some SMSCs and not some others. no this would not be implemented. However this is also not implemented for sms pushes as far as I remember. You can also use several config files of kannel and run one kannel instance per user to achieve this. Andreas Fink Fink Consulting GmbH --- Tel: +41-61-332 Fax: +41-61-331 Mobile: +41-79-2457333 Address: Clarastrasse 3, 4058 Basel, Switzerland E-Mail: [EMAIL PROTECTED] Homepage: http://www.finkconsulting.com ---
Re: ppg smsc routing
But would it allow to controll access to aprticular SMSC? eg one wap-push-user can only access some SMSCs and not some others. Szymon Stipe Tolj wrote: Andreas Fink wrote: The suggestion would be to add &smsc=... to the ppg URL as it is in the sendsms URL. This would allow the same mechanisms to work for SMSC selection for PPG and normal SMS delivery. sounds reasonable and practible. +1 from me. Stipe [EMAIL PROTECTED] --- Wapme Systems AG Münsterstr. 248 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: ppg smsc routing
Andreas Fink wrote: > > The suggestion would be to add &smsc=... to the ppg URL as it is in the sendsms URL. > This would allow the same mechanisms to work for SMSC selection for PPG and normal >SMS delivery. sounds reasonable and practible. +1 from me. Stipe [EMAIL PROTECTED] --- Wapme Systems AG Münsterstr. 248 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: ppg smsc routing
The suggestion would be to add &smsc=... to the ppg URL as it is in the sendsms URL. This would allow the same mechanisms to work for SMSC selection for PPG and normal SMS delivery. On Donnerstag, Januar 9, 2003, at 12:50 Uhr, Aarno Syvänen wrote: All duplicate code should go gw/shared. But ppg must send cgi parameter values through many protocol layers, as smbox does not. There would be differences. Aarno On Thursday, January 9, 2003, at 12:17 PM, Stipe Tolj wrote: Aarno Syvänen wrote: Definitely. Actually this may be a simple thing to do. (Ppg should have url parameters as sendsms does.) so we need to duplicate code?! hmm, not that style we really want, or?! Stipe [EMAIL PROTECTED] --- Wapme Systems AG Münsterstr. 248 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 Andreas Fink Fink Consulting GmbH --- Tel: +41-61-332 Fax: +41-61-331 Mobile: +41-79-2457333 Address: Clarastrasse 3, 4058 Basel, Switzerland E-Mail: [EMAIL PROTECTED] Homepage: http://www.finkconsulting.com ---
Re: ppg smsc routing
All duplicate code should go gw/shared. But ppg must send cgi parameter values through many protocol layers, as smbox does not. There would be differences. Aarno On Thursday, January 9, 2003, at 12:17 PM, Stipe Tolj wrote: Aarno Syvänen wrote: Definitely. Actually this may be a simple thing to do. (Ppg should have url parameters as sendsms does.) so we need to duplicate code?! hmm, not that style we really want, or?! Stipe [EMAIL PROTECTED] --- Wapme Systems AG Münsterstr. 248 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: ppg smsc routing
Aarno Syvänen wrote: > > Definitely. Actually this may be a simple thing to do. (Ppg should have > url parameters > as sendsms does.) so we need to duplicate code?! hmm, not that style we really want, or?! Stipe [EMAIL PROTECTED] --- Wapme Systems AG Münsterstr. 248 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: ppg smsc routing
Definitely. Actually this may be a simple thing to do. (Ppg should have url parameters as sendsms does.) Aarno On Wednesday, January 8, 2003, at 03:44 PM, Stipe Tolj wrote: Szymon Stasik wrote: I wonder if this matter has been solved in some recent cvs version? I have found some thread about this. I would be useful to have possibility of routing different push messages through apriopriate smsc. AFAIK, no. Aarno, this should go to the STATUS and/or TODO file?! Patches welcome. Stipe [EMAIL PROTECTED] --- Wapme Systems AG Münsterstr. 248 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: ppg smsc routing
Szymon Stasik wrote: > > I wonder if this matter has been solved in some recent cvs version? I > have found some thread about this. I would be useful to have possibility > of routing different push messages through apriopriate smsc. AFAIK, no. Aarno, this should go to the STATUS and/or TODO file?! Patches welcome. Stipe [EMAIL PROTECTED] --- Wapme Systems AG Münsterstr. 248 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
ppg smsc routing
Hello, I wonder if this matter has been solved in some recent cvs version? I have found some thread about this. I would be useful to have possibility of routing different push messages through apriopriate smsc. regards, Szymon
Re: Kannel used as a PPG
Thank you. This account isno more used actually. Evelyne Stipe Tolj wrote: > > > #SMPP 1 > > group = smsc > > smsc = smpp > > smsc-id=mw_test_smpp > > host = 62.80.122.178 > > port = 7901 > > receive-port = 8100 > > smsc-username = "mw_test_smpp" > > smsc-password = eD2dq4L > > system-type = "VMA" > > address-range = "" > > my-number= 333 > > enquire-link-interval=120 > > reconnect-delay=30 > > first of all I'd recommend you *not* to send real SMSC usernames and > passwords to the list. If your SMSC provider has no firewall to let > only your specific IPs in, then people may use your account to send > sms and *you* will be charged for it. > > Please ask your SMSC provider to change your password ASAP! and don't > provide it to the list! > > 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: Kannel used as a PPG
Dear all, I have tried to analyse the binary request made by Kannel. But I do not undersatnd why some fields appear in the SMPP request, such as login, PPG IP address ... Here my configuration file and the resquest send by my PI. Can you please help me ? Is there some other data that I have to configure ? group = core admin-port = 13000 wapbox-port = 13002 admin-password = bar box-allow-ip = "127.0.0.1" unified-prefix = "+,00" access-log = "/usr/mobileway/log/access.log" # WAPBOX SETUP, for pushing and for pulling (fetching) the wap data group = wapbox bearerbox-host = localhost syslog-level = none # PPG CORE SETUP, for defining the push request interface group = ppg ppg-url = /cgi-bin/wap-push.cgi ppg-port = 8080 #ppg-ssl-port = 8081 concurrent-pushes = 100 trusted-pi = no #users = 1024 ppg-deny-ip = 194.100.32.89;194.100.32.103 ppg-allow-ip = *.*.*.*; #ssl-server-cert-file = "/Users/aarno/gateway/test/cert.pem" #ssl-server-key-file = "/Users/aarno/gateway/test/key.pem" global-sender="mobileway" # TPOA sent on SMPP request. Must be alpha num, due to trouble on TON value #SMPP 1 group = smsc smsc = smpp smsc-id=mw_test_smpp host = 62.80.122.178 port = 7901 receive-port = 8100 smsc-username = "mw_test_smpp" smsc-password = eD2dq4L system-type = "VMA" address-range = "" my-number= 333 enquire-link-interval=120 reconnect-delay=30 group = wap-push-user wap-push-user = picom ppg-username = mw_test_smpp ppg-password = eD2dq4L deny-ip = 222.222.222.222; allow-ip = *.*.*.*; Here the request sends by my PI: Message to http://203.208.227.203:8080/cgi-bin/wap-push.cgi Content-Type: multipart/related; boundary=PMasdfglkjhqwert; type="application/xml" --PMasdfglkjhqwert Content-Type: application/xml http://www.wapforum.org/DTD/pap_1.0.dtd";> --PMasdfglkjhqwert Content-Type: text/vnd.wap.si http://www.wapforum.org/DTD/SI.dtd";> http://www.boursorama.fr"; si-id = "WapIDE_SI/1" >Do you want to download boursorama information ? --PMasdfglkjhqwert-- PPG Responses Received: http://www.wapforum.org/DTD/pap_1.0.dtd";> What I do not understand is why in the binary message generated for SMPP, I found: - mw_test_smpp - WapIDE 3.1 PO - 203.208.227.203:8080 Can you please help me ? Thanks, Evelyne NOTTON Stipe Tolj wrote: > > Evelyne Notton wrote: > > > > I have configured Kannel to work as a PPG on input, and SMPP on output. I have >several remarks > > concerning the configuration: > > - I have seen that the field Source_Addr on the SMPP request is not filled in >using field my_number > > of smsc group, but using field global-sender of ppg group. Is there any reason or >is it a bug ? > > currently there is no logic in the PPG part to set the source addr for > the sms transmissions, AFAIK. > > > - on SMPP request, if the Source_addr is a numeric value, the TON set is not >correct > > - I have tried to analyse the binary request made by Kannel. Here my configuration >file: > > group = core > > admin-port = 13000 > > wapbox-port = 13002 > > admin-password = bar > > box-allow-ip = "127.0.0.1" > > unified-prefix = "+,00" > > access-log = "/usr/mobileway/log/access.log" > > > > # WAPBOX SETUP, for pushing and for pulling (fetching) the wap data > > group = wapbox > > bearerbox-host = localhost > > syslog-level = none > > > > # PPG CORE SETUP, for defining the push request interface > > group = ppg > > ppg-url = /cgi-bin/wap-push.cgi > > ppg-port = 8080 > > #ppg-ssl-port = 8081 > > concurrent-pushes = 100 > > trusted-pi = no > > #users = 1024 > > ppg-deny-ip = 194.100.32.89;194.100.32.103 > > ppg-allow-ip = *.*.*.*; > > #ssl-server-cert-file = "/Users/aarno/gateway/test/cert.pem" > > #ssl-server-key-file = "/Users/aarno/gateway/test/key.pem" > > global-sender="mobileway" # TPOA sent on SMPP request. Must be alpha num, >due to trouble on > > TON value > > > > #SMPP 1 > > group = smsc > > smsc = smpp > > smsc-id=mw_test_smpp > > host = 62.80.122.178 > > port = 7901 > > receive-port = 8100 > > smsc-username = "mw_test_smpp" > > smsc-password = eD2dq4L > > system-type = "VMA" > > address-range = "" > > my-number= 333 > > enquire-link-interval=120 > > reconnect-delay=30 > > you have to set > > source-addr-ton = x > > accordingly to your needs. > > 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: Kannel used as a PPG
> #SMPP 1 > group = smsc > smsc = smpp > smsc-id=mw_test_smpp > host = 62.80.122.178 > port = 7901 > receive-port = 8100 > smsc-username = "mw_test_smpp" > smsc-password = eD2dq4L > system-type = "VMA" > address-range = "" > my-number= 333 > enquire-link-interval=120 > reconnect-delay=30 first of all I'd recommend you *not* to send real SMSC usernames and passwords to the list. If your SMSC provider has no firewall to let only your specific IPs in, then people may use your account to send sms and *you* will be charged for it. Please ask your SMSC provider to change your password ASAP! and don't provide it to the list! 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: Kannel used as a PPG
Evelyne Notton wrote: > > I have configured Kannel to work as a PPG on input, and SMPP on output. I have >several remarks > concerning the configuration: > - I have seen that the field Source_Addr on the SMPP request is not filled in using >field my_number > of smsc group, but using field global-sender of ppg group. Is there any reason or is >it a bug ? currently there is no logic in the PPG part to set the source addr for the sms transmissions, AFAIK. > - on SMPP request, if the Source_addr is a numeric value, the TON set is not correct > - I have tried to analyse the binary request made by Kannel. Here my configuration >file: > group = core > admin-port = 13000 > wapbox-port = 13002 > admin-password = bar > box-allow-ip = "127.0.0.1" > unified-prefix = "+,00" > access-log = "/usr/mobileway/log/access.log" > > # WAPBOX SETUP, for pushing and for pulling (fetching) the wap data > group = wapbox > bearerbox-host = localhost > syslog-level = none > > # PPG CORE SETUP, for defining the push request interface > group = ppg > ppg-url = /cgi-bin/wap-push.cgi > ppg-port = 8080 > #ppg-ssl-port = 8081 > concurrent-pushes = 100 > trusted-pi = no > #users = 1024 > ppg-deny-ip = 194.100.32.89;194.100.32.103 > ppg-allow-ip = *.*.*.*; > #ssl-server-cert-file = "/Users/aarno/gateway/test/cert.pem" > #ssl-server-key-file = "/Users/aarno/gateway/test/key.pem" > global-sender="mobileway" # TPOA sent on SMPP request. Must be alpha num, due >to trouble on > TON value > > #SMPP 1 > group = smsc > smsc = smpp > smsc-id=mw_test_smpp > host = 62.80.122.178 > port = 7901 > receive-port = 8100 > smsc-username = "mw_test_smpp" > smsc-password = eD2dq4L > system-type = "VMA" > address-range = "" > my-number= 333 > enquire-link-interval=120 > reconnect-delay=30 you have to set source-addr-ton = x accordingly to your needs. 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
Kannel used as a PPG
Hello, I have configured Kannel to work as a PPG on input, and SMPP on output. I have several remarks concerning the configuration: - I have seen that the field Source_Addr on the SMPP request is not filled in using field my_number of smsc group, but using field global-sender of ppg group. Is there any reason or is it a bug ? - on SMPP request, if the Source_addr is a numeric value, the TON set is not correct - I have tried to analyse the binary request made by Kannel. Here my configuration file: group = core admin-port = 13000 wapbox-port = 13002 admin-password = bar box-allow-ip = "127.0.0.1" unified-prefix = "+,00" access-log = "/usr/mobileway/log/access.log" # WAPBOX SETUP, for pushing and for pulling (fetching) the wap data group = wapbox bearerbox-host = localhost syslog-level = none # PPG CORE SETUP, for defining the push request interface group = ppg ppg-url = /cgi-bin/wap-push.cgi ppg-port = 8080 #ppg-ssl-port = 8081 concurrent-pushes = 100 trusted-pi = no #users = 1024 ppg-deny-ip = 194.100.32.89;194.100.32.103 ppg-allow-ip = *.*.*.*; #ssl-server-cert-file = "/Users/aarno/gateway/test/cert.pem" #ssl-server-key-file = "/Users/aarno/gateway/test/key.pem" global-sender="mobileway" # TPOA sent on SMPP request. Must be alpha num, due to trouble on TON value #SMPP 1 group = smsc smsc = smpp smsc-id=mw_test_smpp host = 62.80.122.178 port = 7901 receive-port = 8100 smsc-username = "mw_test_smpp" smsc-password = eD2dq4L system-type = "VMA" address-range = "" my-number= 333 enquire-link-interval=120 reconnect-delay=30 group = wap-push-user wap-push-user = picom ppg-username = mw_test_smpp ppg-password = eD2dq4L deny-ip = 222.222.222.222; allow-ip = *.*.*.*; Here the request sends by my PI: Message to http://203.208.227.203:8080/cgi-bin/wap-push.cgi Content-Type: multipart/related; boundary=PMasdfglkjhqwert; type="application/xml" --PMasdfglkjhqwert Content-Type: application/xml http://www.wapforum.org/DTD/pap_1.0.dtd";> --PMasdfglkjhqwert Content-Type: text/vnd.wap.si http://www.wapforum.org/DTD/SI.dtd";> http://www.boursorama.fr"; si-id = "WapIDE_SI/1" >Do you want to download boursorama information ? --PMasdfglkjhqwert-- PPG Responses Received: http://www.wapforum.org/DTD/pap_1.0.dtd";> What I do not understand is why in the binary message generated for SMPP, I found: - mw_test_smpp - WapIDE 3.1 PO - 203.208.227.203:8080 Can you please help me ? Thanks, Evelyne NOTTON
test-ppg crashed
Hello I have some problem with Kannel as PPG. When I use the test_ppg tools the wapbox crashed. ./test_ppg -q http://localhost:1/push?user=smssendr'&'password=futurelab sl.txt smstestppg.txt 2002-08-21 09:10:33 [0] INFO: an input without a configuration file assumed 2002-08-21 09:10:33 [0] DEBUG: using sl.txt as a content file 2002-08-21 09:10:33 [0] DEBUG: using smstestppg.txt as a control file 2002-08-21 09:10:33 [1] DEBUG: Started thread 2 (gwlib/fdset.c:poller) 2002-08-21 09:10:33 [0] DEBUG: Started thread 1 (test/test_ppg.c:push_thread) 2002-08-21 09:10:33 [1] DEBUG: Started thread 3 (gwlib/http.c:write_request_thread) 2002-08-21 09:10:33 [1] DEBUG: TEST_PPG: started pushing job 0 2002-08-21 09:10:33 [3] DEBUG: HTTP: Opening connection to `localhost:1' (fd=13). 2002-08-21 09:10:33 [3] DEBUG: HTTP: Sending request: 2002-08-21 09:10:33 [3] DEBUG: Octet string at 0x81e0328: 2002-08-21 09:10:33 [3] DEBUG: len: 1178 2002-08-21 09:10:33 [3] DEBUG: size: 1179 2002-08-21 09:10:33 [3] DEBUG: immutable: 0 2002-08-21 09:10:33 [3] DEBUG: data: 50 4f 53 54 20 2f 70 75 POST /pu 2002-08-21 09:10:33 [3] DEBUG: data: 73 68 3f 75 73 65 72 3d 2002-08-21 09:10:33 [3] DEBUG: data: 67 68 22 3e 0a 3c 2f 73 gh">. 2002-08-21 09:10:33 [3] DEBUG: data: 6c 3e 0d 0a 2d 2d 61 73 l>..--as 2002-08-21 09:10:33 [3] DEBUG: data: 64 6c 66 6b 6a 69 75 72 dlfkjiur 2002-08-21 09:10:33 [3] DEBUG: data: 77 67 68 61 73 66 2d 2d wghasf-- 2002-08-21 09:10:33 [3] DEBUG: data: 0d 0a .. 2002-08-21 09:10:33 [3] DEBUG: Octet string dump ends. 2002-08-21 09:10:33 [3] ERROR: connect failed 2002-08-21 09:10:33 [3] ERROR: System error 111: Connection refused 2002-08-21 09:10:33 [3] ERROR: error connecting to server `localhost' at port `1' 2002-08-21 09:10:33 [3] DEBUG: HTTP: Opening NEW connection to `localhost:1' (fd=0). 2002-08-21 09:10:33 [3] ERROR: Couldn't send request to 2002-08-21 09:10:33 [1] ERROR: push failed, no reason found 2002-08-21 09:10:33 [1] INFO: TEST_PPG: In thread 1 0 succeeded, 1 failed 2002-08-21 09:10:33 [1] DEBUG: Thread 1 (test/test_ppg.c:push_thread) terminates. 2002-08-21 09:10:33 [0] INFO: TEST_PPG: 1 requests in 0.00 seconds, inf requests per second 2002-08-21 09:10:33 [0] DEBUG: Waiting for 3 (gwlib/http.c:write_request_thread) to terminate 2002-08-21 09:10:33 [3] DEBUG: Thread 3 (gwlib/http.c:write_request_thread) terminates.2002-08-21 09:10:33 [2] DEBUG: Thread 2 (gwlib/fdset.c:poller) terminates. 2002-08-21 09:10:33 [0] DEBUG: Immutable octet strings: 8. 2002-08-21 09:10:33 [0] DEBUG: Current allocations: 0 areas, 0 bytes 2002-08-21 09:10:33 [0] DEBUG: Highest number of allocations: 154 areas 2002-08-21 09:10:33 [0] DEBUG: Highest memory usage: 24082 bytes I use cvs from 19.08. Here are the logs from bearerbox and wapbox wapbox.log 2002-08-21 09:08:59 [0] INFO: Kannel wapbox version cvs-20020819 starting up. 2002-08-21 09:08:59 [0] DEBUG: Started thread 1 (wap/wsp_session.c:main_thread) 2002-08-21 09:08:59 [0] DEBUG: Started thread 2 (wap/wsp_unit.c:main_thread) 2002-08-21 09:08:59 [0] DEBUG: Started thread 3 (wap/wsp_push_client.c:main_thread) 2002-08-21 09:08:59 [0] DEBUG: Started thread 4 (wap/timers.c:watch_timers) 2002-08-21 09:08:59 [0] DEBUG: Started thread 5 (wap/wtp_init.c:main_thread) 2002-08-21 09:08:59 [0] DEBUG: Started thread 6 (wap/wtp_resp.c:main_thread) 2002-08-21 09:08:59 [0] DEBUG: Started thread 7 (gw/wap-appl.c:main_thread) 2002-08-21 09:08:59 [0] DEBUG: Started thread 8 (gw/wap-appl.c:return_replies_thread) 2002-08-21 09:08:59 [0] DEBUG: Started thread 9 (gw/wap_push_ota.c:main_thread) 2002-08-21 09:08:59 [0] DEBUG: HTTP: Opening server at port 1. 2002-08-21 09:08:59 [0] DEBUG: Started thread 10 (gwlib/fdset.c:poller) 2002-08-21 09:08:59 [0] DEBUG: Started thread 11 (gwlib/http.c:server_thread) 2002-08-21 09:08:59 [0] DEBUG: Started thread 12 (gw/wap_push_ppg.c:ota_read_thread) 2002-08-21 09:08:59 [0] DEBUG: Started thread 13 (gw/wap_push_ppg.c:http_read_thread) 2002-08-21 09:08:59 [0] DEBUG: Started thread 14 (gw/wap_push_ppg.c:pap_request_thread) 2002-08-21 09:08:59 [0] INFO: Connected to bearerbox at localhost port 14002. 2002-08-21 09:08:59 [0] DEBUG: Started thread 15 (gw/heartbeat.c:heartbeat_thread) 2002-08-21 09:10:33 [11] DEBUG: HTTP: Creating HTTPClient for `127.0.0.1'. 2002-08-21 09:10:33 [14] ERROR: Start marker was damaged for area 0x8246a70 2002-08-21 09:10:33 [14] ERROR: Could not find area information. 2002-08-21 09:10:33 [14] PANIC: gwlib/octstr.c:2106: seems_valid_real: Assertion `gw_check_is_allocated(ostr)' failed. (Called from gwlib/octstr.c:247:octstr_destroy.) bearerbox.log 2002-08-21 09:08:50 [0] DEBUG: HTTP: Opening server at port 14000. 2002-08-21 09:08:50 [0] DEBUG: Started thread 1 (gwlib/fdset.c:po
PPG test
Hi all, I was doing PPG testing as explained in userguide. I'm using kannel1.2.0 RH 6.2. The kannel.conf shown below group = core admin-port = 13000 smsbox-port = 13001 wapbox-port = 13002 admin-password = vqindia wdp-interface-name = "*" log-file = "/home/shridhar/kannel.log" log-level = 0 box-deny-ip = "*.*.*.*" box-allow-ip = "127.0.0.1" unified-prefix = "+91" group = ppg ppg-url = /wappush ppg-port = 8080 concurrent-pushes = 100 users = 1024 ppg-allow-ip = "127.0.0.1" ppg-deny-ip = "192.168.1.*" trusted-pi = false group = wapbox bearerbox-host = localhost log-file = "/home/shridhar/wapbox.log" log-level = 0 syslog-level = none group = smsc smsc = http smsc-id = HTTP port = 13003 system-type = kannel smsc-username = foo smsc-password = bar no-sender = true no-coding = true send-url = http://localhost:12000/cgi-bin/sendsms group = smsbox bearerbox-host = localhost group = wap-push-user wap-push-user = foo ppg-username = foo ppg-password = bar allow-ip = 127.0.0.1 Running #./test_ppg -q http://localhost:8080/wappush iptestppg.txt sl.txt 2002-08-02 12:17:43 [3] DEBUG: Octet string dump ends. 2002-08-02 12:17:43 [3] ERROR: connect failed 2002-08-02 12:17:43 [3] ERROR: System error 111: Connection refused 2002-08-02 12:17:43 [3] ERROR: error connecting to server `localhost' at port `8080' 2002-08-02 12:17:43 [3] DEBUG: HTTP: Opening NEW connection to `localhost:8080'(fd=0). 2002-08-02 12:17:43 [3] ERROR: Couldn't send request to <http://localhost:8080/wappush> 2002-08-02 12:17:43 [1] ERROR: push failed, no reason found 2002-08-02 12:17:43 [1] INFO: TEST_PPG: In thread 1 0 succeeded, 1 failed 2002-08-02 12:17:43 [1] DEBUG: Thread 1 (test/test_ppg.c:push_thread) terminates. 2002-08-02 12:17:43 [0] INFO: TEST_PPG: 1 requests in 0.00 seconds, inf requests per second 2002-08-02 12:17:43 [0] DEBUG: Waiting for 3 (gwlib/http.c:write_request_thread) to terminate 2002-08-02 12:17:43 [3] DEBUG: Thread 3 (gwlib/http.c:write_request_thread) terminates. 2002-08-02 12:17:43 [2] DEBUG: Thread 2 (gwlib/fdset.c:poller) terminates. 2002-08-02 12:17:43 [0] DEBUG: Immutable octet strings: 8. I'm running test_hhtp_server, which does not show any activity in whole process. #./test_http_server -l /home/shridhar/http.log -p 12000 The bearerbox log 2002-08-02 12:01:09 [0] INFO: MAIN: Start-up done, entering mainloop 2002-08-02 12:01:09 [7] DEBUG: sms_router: list_len = 0 2002-08-02 12:01:14 [13] DEBUG: Started thread 15 (gw/bb_boxc.c:function) 2002-08-02 12:17:39 [17] INFO: Client connected from <127.0.0.1> 2002-08-02 12:17:39 [17] DEBUG: setting up systems for new wapbox 2002-08-02 12:17:39 [17] DEBUG: Started thread 18 (gw/bb_boxc.c:boxc_sender) 2002-08-02 12:17:43 [17] INFO: Connection closed by the box <127.0.0.1> 2002-08-02 12:17:43 [18] DEBUG: Thread 18 (gw/bb_boxc.c:boxc_sender) terminates. 2002-08-02 12:17:43 [17] DEBUG: Thread 17 (gw/bb_boxc.c:function) terminates. The wapbox log 2002-08-02 12:22:06 [0] INFO: Kannel wapbox version 1.2.0 starting up. 2002-08-02 12:22:06 [0] DEBUG: Started thread 1 (wap/wsp_session.c:main_thread) 2002-08-02 12:22:06 [0] DEBUG: Started thread 2 (wap/wsp_unit.c:main_thread) 2002-08-02 12:22:06 [0] DEBUG: Started thread 3 (wap/wsp_push_client.c:main_thread) 2002-08-02 12:22:06 [0] DEBUG: Started thread 4 (wap/timers.c:watch_timers) 2002-08-02 12:22:06 [0] DEBUG: Started thread 5 (wap/wtp_init.c:main_thread) 2002-08-02 12:22:06 [0] DEBUG: Started thread 6 (wap/wtp_resp.c:main_thread) 2002-08-02 12:22:06 [0] DEBUG: Started thread 7 (gw/wap-appl.c:main_thread) 2002-08-02 12:22:06 [0] DEBUG: Started thread 8 (gw/wap-appl.c:return_replies_thread) 2002-08-02 12:22:06 [0] DEBUG: Started thread 9 (gw/wap_push_ota.c:main_thread) 2002-08-02 12:22:06 [0] DEBUG: HTTP: Opening server at port 8080. 2002-08-02 12:22:06 [0] DEBUG: Started thread 10 (gwlib/fdset.c:poller) 2002-08-02 12:22:06 [0] DEBUG: Started thread 11 (gwlib/http.c:server_thread) 2002-08-02 12:22:06 [0] DEBUG: Started thread 12 (gw/wap_push_ppg.c:ota_read_thread) 2002-08-02 12:22:06 [0] DEBUG: Started thread 13 (gw/wap_push_ppg.c:http_read_thread) 2002-08-02 12:22:06 [0] DEBUG: Started thread 14 (gw/wap_push_ppg.c:pap_request_thread) 2002-08-02 12:22:06 [0] INFO: Connected to bearerbox at localhost port 13002. 2002-08-02 12:22:06 [0] DEBUG: Started thread 15 (gw/heartbeat.c:heartbeat_thread) 2002-08-02 12:22:06 [0] INFO: Connected to bearerbox at localhost port 13002. 2002-08-02 12:22:06 [0] DEBUG: Started thread 15 (gw/heartbeat.c:heartbeat_thread) 2002-08-02 12:22:42 [11] DEBUG: HTTP: Creating HTTPClient for `127.0.0.1'.Segmentation fault and wapbox stops after this. I don't know where I'm going wrong in this whole process. Can some body guide me or send their conf file for reference. If I user ppg username & password #./test_ppg -q http://localhost:8080/wappush?usernam
Note about PPG
Hi, This is not a _bug_ but... When I submit push-message to a PPG, it responses two "Content-Length" headers: HTTP/1.1 202 Foo Server: Kannel/1.2.0 Content-Length: 408 Content-Type: application/xml Content-Length: 408 -- Vjacheslav Chekushinmailto:[EMAIL PROTECTED] Latvian Mobile Phone Companyhttp://www.lmt.lv
Re: PPG
Hi Aarno, My HTTP SMSC routing work fine for PPG. When PPG get PAP request, it directed the processed SI/SL to my HTTP SMSC and then HTTP SMSC use cgi/sendsms to send it to SMSC. I just want to see push PPG via SMS bearer (: The problem was in file: wap_push_ppg.c=>pap_request_thread() First Request from PI succesfully accepted by WAP Box , But second request (with different session id) just get accepted by PPG http server. For detail, please look at WAPBox debug message : 2002-06-24 22:29:26 [0] INFO: 2002-06-24 22:29:26 [0] INFO: Kannel wapbox version cvs- starting up. 2002-06-24 22:29:26 [0] DEBUG: Started thread 1 (wap/wsp_session.c:main_thread) 2002-06-24 22:29:26 [0] DEBUG: Started thread 2 (wap/wsp_unit.c:main_thread) 2002-06-24 22:29:26 [0] DEBUG: Started thread 3 (wap/wsp_push_client.c:main_thread) 2002-06-24 22:29:26 [0] DEBUG: Started thread 4 (wap/timers.c:watch_timers) 2002-06-24 22:29:26 [0] DEBUG: Started thread 5 (wap/wtp_init.c:main_thread) 2002-06-24 22:29:26 [0] DEBUG: Started thread 6 (wap/wtp_resp.c:main_thread) 2002-06-24 22:29:26 [0] DEBUG: Started thread 7 (gw/wap-appl.c:main_thread) 2002-06-24 22:29:26 [0] DEBUG: Started thread 8 (gw/wap-appl.c:return_replies_thread) 2002-06-24 22:29:26 [0] DEBUG: Started thread 9 (wap/wtls-secmgr.c:main_thread) 2002-06-24 22:29:26 [0] DEBUG: Started thread 10 (wap/wtls.c:main_thread) 2002-06-24 22:29:26 [0] DEBUG: Started thread 11 (gw/wap_push_ota.c:main_thread) 2002-06-24 22:29:26 [0] INFO: Using global server SSL certificate from file /usr/local/openssl/newcerts/cert.pem 2002-06-24 22:29:26 [0] INFO: Using global server SSL key from file /usr/local/openssl/private/certkey.pem 2002-06-24 22:29:26 [0] DEBUG: HTTP: Opening server at port 8081. 2002-06-24 22:29:26 [0] DEBUG: Started thread 12 (gwlib/fdset.c:poller) 2002-06-24 22:29:26 [0] DEBUG: Started thread 13 (gwlib/http.c:server_thread) 2002-06-24 22:29:26 [0] DEBUG: HTTP: Opening SSL server at port 8082. 2002-06-24 22:29:26 [0] DEBUG: Started thread 14 (gw/wap_push_ppg.c:ota_read_thread) 2002-06-24 22:29:26 [0] DEBUG: Started thread 15 (gw/wap_push_ppg.c:http_read_thread) 2002-06-24 22:29:26 [0] DEBUG: Started thread 16 (gw/wap_push_ppg.c:https_read_thread) 2002-06-24 22:29:26 [0] DEBUG: Started thread 17 (gw/wap_push_ppg.c:pap_request_thread) 2002-06-24 22:29:26 [0] INFO: Connected to bearerbox at localhost port 13002. 2002-06-24 22:29:26 [0] DEBUG: Started thread 18 (gw/heartbeat.c:heartbeat_thread) 2002-06-24 22:30:26 [13] DEBUG: HTTP: Creating HTTPClient for `127.0.0.1'. 2002-06-24 22:30:26 [17] INFO: PPG: Accept request from <127.0.0.1> 2002-06-24 22:30:26 [17] DEBUG: PPG: http_read_thread: pap multipart accepted 2002-06-24 22:30:26 [17] INFO: client address was <+358408676001>, accepted 2002-06-24 22:30:26 [17] DEBUG: PAP COMPILER: doing semantic analysis for address type a phone number 2002-06-24 22:30:26 [17] DEBUG: using defaults instead of anys 2002-06-24 22:30:26 [17] DEBUG: PPG: http_read_thread: pap control entity compiled ok 2002-06-24 22:30:26 [17] DEBUG: PPG: transform_message: push message content and headers valid 2002-06-24 22:30:26 [17] DEBUG: PPG: push machine 0 created 2002-06-24 22:30:26 [17] DEBUG: PPG: store_push_data: push machine 0 appended to unit push list 2002-06-24 22:30:26 [17] DEBUG: PPG: send_push_response: telling pi 2002-06-24 22:30:26 [17] DEBUG: HTTP: Resetting HTTPClient for `127.0.0.1'. 2002-06-24 22:30:26 [17] INFO: PPG: handle_push_message: push message accepted for processing 2002-06-24 22:30:26 [17] DEBUG: PPG: OTA request for unit push 2002-06-24 22:30:26 [17] INFO: PPG: unconfirmed push delivered to OTA 2002-06-24 22:30:26 [17] DEBUG: PPG: destroying push machine 0 2002-06-24 22:30:26 [11] DEBUG: OTA: event arrived 2002-06-24 22:30:26 [11] DEBUG: OTA: made connectionless session service request 2002-06-24 22:30:26 [2] DEBUG: WSP_UNIT: Connectionless push accepted 2002-06-24 22:30:26 [2] DEBUG: WSP_UNIT: delivering to wdp 2002-06-24 22:30:26 [12] DEBUG: HTTP: Destroying HTTPClient area 0x80d5818. 2002-06-24 22:30:26 [12] DEBUG: HTTP: Destroying HTTPClient for `127.0.0.1'. 2002-06-24 22:31:59 [13] DEBUG: HTTP: Creating HTTPClient for `127.0.0.1'. 2002-06-24 22:31:59 [17] DEBUG: Thread 17 (gw/wap_push_ppg.c:pap_request_thread) terminates. The last line show that when second http client arrive, pap_request_thread misteriously terminated ??? Best Regards, *** REPLY SEPARATOR *** On 24/06/2002 at 17:00 Aarno Syvänen wrote: >Eko Yanuar kirjoittaa maanantaina, 24. kesäkuuta 2002, kello 16:49:Hi >all, >> >> I use Kannel 1.1.6 from CVS and find it working correctly except for >> PPG. >> When I test it with testppg utility and also with Ericsson Push >> Initiator, I got this bug. >> At first time , Kannel PPG successfully route my message to defined >> SMSC. But on
Re: PPG
Eko Yanuar kirjoittaa maanantaina, 24. kesäkuuta 2002, kello 16:49:Hi all, I use Kannel 1.1.6 from CVS and find it working correctly except for PPG. When I test it with testppg utility and also with Ericsson Push Initiator, I got this bug. At first time , Kannel PPG successfully route my message to defined SMSC. But only at the first time! Second time I send PPG, WAPBox just accept its as new HTTP connection and its do nothing. Is there anyone that have got success with PPG? Please let me know, maybe I was wrong with my config file, or maybe I should wait for stable release 1.2. PPG does not have SMSC routing yet. This is in my todo list, though. Aarno
Re: wapbox panic with wap-push-ppg
Bruno David Simões Rodrigues wrote: > > last patch to disable wap-push-ppg http port if its group > is not defined on conf is not finished :P > > If wap_psh_ppg_init is not done, wap_push_ppg_shutdown should > be modified too. yep, you're right. I saw that one already, but dropped it by mistake. Thanks for pointing this out again. > I got a PANIC: gw/wappush_ppg.c:359: ASsertion 'run_status ==running' > failed. yep, same for me. > if config group is not present, shouldn't the full init be disabled > instead of only half ? yep, I think the problem is about the cfg structure passing. > If not, if some parts could still run without the open port, could > please someone patch _shutdown function too ? Consider this assigned to me. BTW, have you updated STATUS with this bug?! We should keep it up to date. Stipe [EMAIL PROTECTED] --- Wapme Systems AG Münsterstr. 248 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
wapbox panic with wap-push-ppg
last patch to disable wap-push-ppg http port if its group is not defined on conf is not finished :P If wap_psh_ppg_init is not done, wap_push_ppg_shutdown should be modified too. I got a PANIC: gw/wappush_ppg.c:359: ASsertion 'run_status ==running' failed. if config group is not present, shouldn't the full init be disabled instead of only half ? If not, if some parts could still run without the open port, could please someone patch _shutdown function too ?
Re: running ppg by default?
Stipe Tolj wrote: > > Hi list, > > I'd like to discuss if we should allow a default PPG HTTP instance > running on port 8080 if no PPG group is defined, which is the way it > currently works. > > For security reasons I'd like to switch that off, if no PPG group is > defined. Votes? Yeah, it is better this way. For testing purposes, one can allways use trusted-pi option, for which userguide supplies configuration file. Aarno
running ppg by default?
Hi list, I'd like to discuss if we should allow a default PPG HTTP instance running on port 8080 if no PPG group is defined, which is the way it currently works. For security reasons I'd like to switch that off, if no PPG group is defined. Votes? Stipe [EMAIL PROTECTED] --- Wapme Systems AG Münsterstr. 248 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: PPG and cimd2
Vjacheslav Chekushin wrote: > > Aarno SyvÄnen wrote: > > > > Vjacheslav Chekushin wrote: > > > > > > Hi. > > > I am testing PPG. I define SMSC as CIMD2 and try to send SI to phone. I use > > > test_ppg program with my own pap and si files. Files are compiled normally, > > > but when bearerbox sends it to smsc through smsc_cimd2 driver it reports about > > > error: > > > > > > > > > cimd2_submit_msg: non-digits in originating phone number '0.0.0.0', discarded > > > > > > > > > I didn't found how could I provide sender number to PPG, > > > and simply patch smsc_cimd2.c with hard coded value in case of this error. > > > > > > And after that I got SI on my phone. > > > > > > Question: how must I deal with sender address? > > > > Global-sender should work. I add this to the documentation. > > > > Aarno > > I have tried it already. > As I understand global-sender is processed only in smsbox. But in case of pure > PPG this part not involved at all. So this doesn't help. I meant (or rather, I should have meant ;) that PPG needs global-sender, too. This bug seems to be a release showstopper. Happily, I have code for this already. I'll commit it tomorrow. Aarno
Re: PPG and cimd2
Aarno SyvÄnen wrote: > > Vjacheslav Chekushin wrote: > > > > Hi. > > I am testing PPG. I define SMSC as CIMD2 and try to send SI to phone. I use > > test_ppg program with my own pap and si files. Files are compiled normally, > > but when bearerbox sends it to smsc through smsc_cimd2 driver it reports about > > error: > > > > > > cimd2_submit_msg: non-digits in originating phone number '0.0.0.0', discarded > > > > > > I didn't found how could I provide sender number to PPG, > > and simply patch smsc_cimd2.c with hard coded value in case of this error. > > > > And after that I got SI on my phone. > > > > Question: how must I deal with sender address? > > Global-sender should work. I add this to the documentation. > > Aarno I have tried it already. As I understand global-sender is processed only in smsbox. But in case of pure PPG this part not involved at all. So this doesn't help. -- Vjacheslav Chekushinmailto:[EMAIL PROTECTED]
Re: PPG and cimd2
Vjacheslav Chekushin wrote: > > Hi. > I am testing PPG. I define SMSC as CIMD2 and try to send SI to phone. I use > test_ppg program with my own pap and si files. Files are compiled normally, > but when bearerbox sends it to smsc through smsc_cimd2 driver it reports about > error: > > > cimd2_submit_msg: non-digits in originating phone number '0.0.0.0', discarded > > > I didn't found how could I provide sender number to PPG, > and simply patch smsc_cimd2.c with hard coded value in case of this error. > > And after that I got SI on my phone. > > Question: how must I deal with sender address? Global-sender should work. I add this to the documentation. Aarno
PPG and cimd2
Hi. I am testing PPG. I define SMSC as CIMD2 and try to send SI to phone. I use test_ppg program with my own pap and si files. Files are compiled normally, but when bearerbox sends it to smsc through smsc_cimd2 driver it reports about error: cimd2_submit_msg: non-digits in originating phone number '0.0.0.0', discarded I didn't found how could I provide sender number to PPG, and simply patch smsc_cimd2.c with hard coded value in case of this error. And after that I got SI on my phone. Question: how must I deal with sender address? -- Vjacheslav Chekushinmailto:[EMAIL PROTECTED]
Re: PPG doc review
Aarno Syvänen wrote: > thing to PPG. I must admit that I do not understand what "supplied cgi" > means neither me. Stipe [EMAIL PROTECTED] --- Wapme Systems AG Münsterstr. 248 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: PPG doc review
> LOESCH Jean-Jacques wrote: > > > > Hi the list, > > > > I'm sorry it's a question that Jason has already asked in this mailing > list but I think the answer or From: Aarno Syvänen wasn't very clear. > > It might point that the doc regarding the use of the PPG is really not > very clear. > > I wold like to set up a PPG gateway to initate push through my AT > SMSC. > > > > I hope all the config is OK, but I don't know what to do with the SI > tokenizer or with the supplied cgi ? SI tokenizer is a part of PPG. PPG uses it automatically when you send some- thing to PPG. I must admit that I do not understand what "supplied cgi" means Aarno
PPG doc review
Hi the list, I’m sorry it’s a question that Jason has already asked in this mailing list but I think the answer or From: Aarno Syvänen wasn’t very clear. It might point that the doc regarding the use of the PPG is really not very clear. I wold like to set up a PPG gateway to initate push through my AT SMSC. I hope all the config is OK, but I don’t know what to do with the SI tokenizer or with the supplied cgi ? Any help ? Jean-Jacques LOESCH Chief Architect Volubill > Tel: +33 4 76 04 37 11 Mob: +33 6 18 41 03 80 Fax: +33 4 76 04 37 98 mailto:[EMAIL PROTECTED] http://www.volubill.com BEGIN:VCARD VERSION:2.1 N:LOESCH;;Jean-Jacques FN:Jean-Jacques LOESCH ([EMAIL PROTECTED]) ORG:VOLUBILL TITLE:Chief Architect TEL;WORK;VOICE:+33 4 76 04 37 11 TEL;CELL;VOICE:+33 (6) 18 41 03 80 TEL;WORK;FAX:+33 4 76 04 37 98 ADR;WORK;ENCODING=QUOTED-PRINTABLE:;;80 All=E9e Saint Exup=E9ry=0D=0AZIRST Montbonnot;St. Ismier CEDEX;;F-38334= ;France LABEL;WORK;ENCODING=QUOTED-PRINTABLE:80 All=E9e Saint Exup=E9ry=0D=0AZIRST Montbonnot=0D=0ASt. Ismier CEDEX F-383= 34=0D=0AFrance EMAIL;PREF;INTERNET:[EMAIL PROTECTED] REV:20020227T002944Z END:VCARD
[Fwd: PPG and CIMD2 patches]
--- Begin Message ---
N.B. -- My copy of 'diff' seems not to have a "unified" switch, so these
are context diffs.
Patch 1 fixes the incorrect use of DCS 8 for WDP/SMS WSP-push messages.
dave@ispdev2# diff -c kannel-snapshot/gw/wapbox.c
kannel-patched/gw/wapbox.c
*** kannel-snapshot/gw/wapbox.c Sun Jan 27 23:57:15 2002
--- kannel-patched/gw/wapbox.c Tue Mar 5 14:57:59 2002
***
*** 324,330
msg->sms.smsc_id = NULL;
msg->sms.sms_type = mt_push;
msg->sms.mwi = MWI_UNDEF;
! msg->sms.coding = DC_UCS2;
msg->sms.mclass = MC_UNDEF;
msg->sms.validity = 0;
msg->sms.deferred = 0;
--- 324,330
msg->sms.smsc_id = NULL;
msg->sms.sms_type = mt_push;
msg->sms.mwi = MWI_UNDEF;
! msg->sms.coding = DC_8BIT;
msg->sms.mclass = MC_UNDEF;
msg->sms.validity = 0;
msg->sms.deferred = 0;
Patch 2 makes the CIMD2 driver truncate non-numeric origin addresses
instead of gagging.
dave@ispdev2# diff -c kannel-snapshot/gw/smsc_cimd2.c
kannel-patched/gw/smsc_cimd2.c
*** kannel-snapshot/gw/smsc_cimd2.c Thu Oct 11 19:18:33 2001
--- kannel-patched/gw/smsc_cimd2.c Tue Mar 5 15:01:29 2002
***
*** 1220,1233
warning(0, "cimd2_submit_msg: non-digits in "
"destination phone number '%s', discarded",
octstr_get_cstr(msg->sms.receiver));
! return NULL;
}
if (!parm_valid_address(msg->sms.sender)) {
warning(0, "cimd2_submit_msg: non-digits in "
! "originating phone number '%s', discarded",
octstr_get_cstr(msg->sms.sender));
! return NULL;
}
packet = packet_create(SUBMIT_MESSAGE, BOGUS_SEQUENCE);
--- 1220,1233
warning(0, "cimd2_submit_msg: non-digits in "
"destination phone number '%s', discarded",
octstr_get_cstr(msg->sms.receiver));
! return NULL;
}
if (!parm_valid_address(msg->sms.sender)) {
warning(0, "cimd2_submit_msg: non-digits in "
! "originating phone number '%s', truncating",
octstr_get_cstr(msg->sms.sender));
! octstr_truncate(msg->sms.sender,0);
}
packet = packet_create(SUBMIT_MESSAGE, BOGUS_SEQUENCE);
Please let me know if these patches help or not.
David WHITE
CONNECT AUSTRIA
--- End Message ---
Re: AW: Kannel PPG seems to insist on qos element
Jörg Pommnitz wrote: > I have to qualify this message: > IPv4 works fine without the qos tag, but PLMN gives: > > 2001-11-15 15:41:14 [11] DEBUG: HTTP: Creating HTTPClient for `10.1.25.120'. > 2001-11-15 15:41:14 [13] INFO: PPG: Accept request > from <10.1.25.120> > 2001-11-15 15:41:14 [13] DEBUG: PPG: Content-Type is multipart/related; > boundary="332daf4c:ea30a33dc8:-714c"; type="application/xml; charset=UTF-8" > 2001-11-15 15:41:14 [13] DEBUG: PPG: http_read_thread: pap multipart > accepted > 2001-11-15 15:41:14 [13] INFO: client address was <+491718997592>, accepted > 2001-11-15 15:41:14 [13] DEBUG: PAP COMPILER: doing semantic analysis for > address type a phone number > 2001-11-15 15:41:14 [13] DEBUG: PAP COMPILER: network or bearer does not > accept PLMN address > 2001-11-15 15:41:14 [13] WARNING: wrong type of address for requested bearer > 2001-11-15 15:41:14 [13] DEBUG: PPG: send_bad_message_response: telling pi > 2001-11-15 15:41:14 [13] DEBUG: HTTP: Resetting HTTPClient for > `10.1.25.120'. > 2001-11-15 15:41:14 [13] WARNING: PPG: pap control entity erroneous, the > request unacceptable > 2001-11-15 15:41:19 [10] DEBUG: HTTP: Destroying HTTPClient area 0x81e4b68. > 2001-11-15 15:41:19 [10] DEBUG: HTTP: Destroying HTTPClient for > `10.1.25.120'. > > it seems bearer defaults to WSP instead of something sensible > for the given address type. > Actually, this case the request is rejected. But GSM+SMS would be much better default. I do this tomorrow, too. Aarno
Re: Kannel PPG seems to insist on qos element
Hi Jörg, > it seems the PPG does not work without the > tag and network related attributes. According to the DTD this > tag is optional. Is this a bug? Yes it is. PPG should use default values for missing optional attributes. And I like it use IP when there are no bearer specified. Aarno
AW: Kannel PPG seems to insist on qos element
I have to qualify this message: IPv4 works fine without the qos tag, but PLMN gives: 2001-11-15 15:41:14 [11] DEBUG: HTTP: Creating HTTPClient for `10.1.25.120'. 2001-11-15 15:41:14 [13] INFO: PPG: Accept request from <10.1.25.120> 2001-11-15 15:41:14 [13] DEBUG: PPG: Content-Type is multipart/related; boundary="332daf4c:ea30a33dc8:-714c"; type="application/xml; charset=UTF-8" 2001-11-15 15:41:14 [13] DEBUG: PPG: http_read_thread: pap multipart accepted 2001-11-15 15:41:14 [13] INFO: client address was <+491718997592>, accepted 2001-11-15 15:41:14 [13] DEBUG: PAP COMPILER: doing semantic analysis for address type a phone number 2001-11-15 15:41:14 [13] DEBUG: PAP COMPILER: network or bearer does not accept PLMN address 2001-11-15 15:41:14 [13] WARNING: wrong type of address for requested bearer 2001-11-15 15:41:14 [13] DEBUG: PPG: send_bad_message_response: telling pi 2001-11-15 15:41:14 [13] DEBUG: HTTP: Resetting HTTPClient for `10.1.25.120'. 2001-11-15 15:41:14 [13] WARNING: PPG: pap control entity erroneous, the request unacceptable 2001-11-15 15:41:19 [10] DEBUG: HTTP: Destroying HTTPClient area 0x81e4b68. 2001-11-15 15:41:19 [10] DEBUG: HTTP: Destroying HTTPClient for `10.1.25.120'. it seems bearer defaults to WSP instead of something sensible for the given address type. Regards Jörg > -Ursprüngliche Nachricht- > Von: Jörg Pommnitz [mailto:[EMAIL PROTECTED]] > Gesendet am: Donnerstag, 15. November 2001 16:44 > An: '[EMAIL PROTECTED]' > Betreff: Kannel PPG seems to insist on qos element > > Hi Aarno, > it seems the PPG does not work without the > tag and network related attributes. According to the DTD this > tag is optional. Is this a bug? > > Regards > Jörg >
Kannel PPG seems to insist on qos element
Hi Aarno, it seems the PPG does not work without the tag and network related attributes. According to the DTD this tag is optional. Is this a bug? Regards Jörg
RE: Kannel PPG, PI and character encoding
> > Good question. > > It should be changed to "binary", shouldn't it? > > I think so, too. > > Aarno The fix is in CVS now. Regards Jörg
AW: AW: Kannel PPG, PI and character encoding
> What do you do with Content-Encoding header ? If you change encoding, > you must > change the header, too. > > Aarno Good question. It should be changed to "binary", shouldn't it? Regards Jörg
Re: AW: Kannel PPG, PI and character encoding
Hi Jörg, > Code for BASE64 encoded Push content is now in CVS. Please > have a look. What do you do with Content-Encoding header ? If you change encoding, you must change the header, too. Aarno
PPG Authentication
Hi list, I committed today somewhat tested version of ppg authentication. Basic authentication, ip lists, whitelists and blacklists should no work. Any bugreports are very wellcome. Aarno
Re: AW: Kannel PPG, PI and character encoding
Hi Jörg, Jörg Pommnitz wrote: > Code for BASE64 encoded Push content is now in CVS. Please > have a look. It looks nice, and it will be easy to add new encodings. Aarno
AW: Kannel PPG, PI and character encoding
> -Ursprüngliche Nachricht- > Von: Aarno Syvänen [mailto:[EMAIL PROTECTED]] > Gesendet am: Dienstag, 23. Oktober 2001 13:03 > An: Jörg Pommnitz > Cc: [EMAIL PROTECTED] > Betreff: Re: AW: AW: Kannel PPG, PI and character encoding > > Hi Jörg, > > Well, I misunderstood it, too. I agree that checking > Content-Transfer- > Encoding is usefull, and simple. Perhaps you can add it ? > > Aarno Code for BASE64 encoded Push content is now in CVS. Please have a look. Regards Jörg
Re: BUG in PPG when sending malformed PAP document
Stipe Tolj wrote: > Hi, > > I found this bug recently by patching the hard coded PAP document to > use a SI instead of the WML deck in test/test_ppg.c. > > To support SI/SL over SMS I changed the following: > > [...] >[...] > network-required="true" > network="GSM" > > and by mistake added the following: > > bearer-required="true"> // BUG! > bearer="SMS"> > > [...] > > which is obviously not a valid XML structured document! > > Running > > $ ./test_ppg -H http://localhost/cgi-bin/wap-push.cgi > > caused wapbox to panic and crash with the following wapbox.log entry: > > [...] > 2001-10-25 17:02:49 [11] DEBUG: HTTP: Creating HTTPClient for > `127.0.0.1'. > 2001-10-25 17:02:49 [13] INFO: PPG: Accept request > from <127.0.0.1> > 2001-10-25 17:02:49 [13] DEBUG: PPG: http_read_thread: pap multipart > accepted > 2001-10-25 17:02:49 [13] PANIC: gwlib/octstr.c:2032: seems_valid_real: > Assertion `ostr != NULL' failed. (Called from > gwlib/octstr.c:728:octstr_compare.) > [...] > > so obviously we do not parse the PAP document very good here?! What happens here is that PAP compiler drops text nodes (because otherwise blanks would cause problems). So it ignores "bearer="SMS"">. But this is not *semantically* rigth: if document contains bearer-required field, it should contain bearer field, too. So now pap compiler drops this document after compiling it. Aarno
Re: BUG in PPG when sending malformed PAP document
Stipe Tolj wrote: > Hi, > > I found this bug recently by patching the hard coded PAP document to > use a SI instead of the WML deck in test/test_ppg.c. > > To support SI/SL over SMS I changed the following: > > [...] >[...] > network-required="true" > network="GSM" > > and by mistake added the following: > > bearer-required="true"> // BUG! > bearer="SMS"> > > [...] > > which is obviously not a valid XML structured document! > > Running > > $ ./test_ppg -H http://localhost/cgi-bin/wap-push.cgi > > caused wapbox to panic and crash with the following wapbox.log entry: > > [...] > 2001-10-25 17:02:49 [11] DEBUG: HTTP: Creating HTTPClient for > `127.0.0.1'. > 2001-10-25 17:02:49 [13] INFO: PPG: Accept request > from <127.0.0.1> > 2001-10-25 17:02:49 [13] DEBUG: PPG: http_read_thread: pap multipart > accepted > 2001-10-25 17:02:49 [13] PANIC: gwlib/octstr.c:2032: seems_valid_real: > Assertion `ostr != NULL' failed. (Called from > gwlib/octstr.c:728:octstr_compare.) > [...] > > so obviously we do not parse the PAP document very good here?! Thanks for bug report. I will correct this. Aarno
Re: [RFC] ppg-deny-ip and ppg-allow-ip for PPGs HTTP server
Hi Stipe, Stipe Tolj wrote: > are there ppg-deny-ip and ppg-allow-ip ranges possible for the PPG > itself? I am actually coding this feature just now. It will have two levels: ppg self can deny and allow ip and a specific user can do same (it is, deny or allow pushes from a specific ip). > Comments from the list?! I indeed hope that people interested on ppg will send their comments to the list. Aarno
BUG in PPG when sending malformed PAP document
Hi, I found this bug recently by patching the hard coded PAP document to use a SI instead of the WML deck in test/test_ppg.c. To support SI/SL over SMS I changed the following: [...] // BUG! bearer="SMS"> [...] which is obviously not a valid XML structured document! Running $ ./test_ppg -H http://localhost/cgi-bin/wap-push.cgi caused wapbox to panic and crash with the following wapbox.log entry: [...] 2001-10-25 17:02:49 [11] DEBUG: HTTP: Creating HTTPClient for `127.0.0.1'. 2001-10-25 17:02:49 [13] INFO: PPG: Accept request from <127.0.0.1> 2001-10-25 17:02:49 [13] DEBUG: PPG: http_read_thread: pap multipart accepted 2001-10-25 17:02:49 [13] PANIC: gwlib/octstr.c:2032: seems_valid_real: Assertion `ostr != NULL' failed. (Called from gwlib/octstr.c:728:octstr_compare.) [...] so obviously we do not parse the PAP document very good here?! Stipe [EMAIL PROTECTED] --- Wapme Systems AG Münsterstr. 248 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
[RFC] ppg-deny-ip and ppg-allow-ip for PPGs HTTP server
Hi Aarno, are there ppg-deny-ip and ppg-allow-ip ranges possible for the PPG itself? I suggest this would be quite usefull when not explicitely using user credentials. Comments from the list?! Stipe [EMAIL PROTECTED] --- Wapme Systems AG Münsterstr. 248 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: AW: AW: Kannel PPG, PI and character encoding
Hi Jörg, Well, I misunderstood it, too. I agree that checking Content-Transfer- Encoding is usefull, and simple. Perhaps you can add it ? Aarno Jörg Pommnitz wrote: > I think I misrepresented my point: I just encountered > an example in RFC2387 where application/octet-stream > is represented in BASE64. The same could theoretically > happen with any other content (XML encoded in UCS-16 or > UTF-8 being a good candidate). > I think Kannel should check the Content-Transfer-Encoding > header and do its best to correctly handel encoded content. > It will most likely encounter BASE64 (quoted printable > is just ugly). Supporting BASE64 should be easy: we already > have the octstr_base64_to_binary(Octstr *ostr) function, > so just a few more lines of code would be required to glue > this in. > > Regards > Jörg > > > -Ursprüngliche Nachricht- > > Von: Aarno Syvänen [mailto:[EMAIL PROTECTED]] > > Gesendet am: Dienstag, 23. Oktober 2001 11:50 > > An: Jörg Pommnitz > > Cc: [EMAIL PROTECTED] > > Betreff: Re: AW: Kannel PPG, PI and character encoding > > > > Hi Jörg, > > > > Jörg Pommnitz wrote: > > > > > I just read RFC2387: it uses base64 as transfer > > > encoding for application/octet-stream data. While > > > there is a void octstr_base64_to_binary(Octstr *ostr) > > > function in the Kannel source tree it seems not to > > > be used in the PPG code. Aarno, what's your opinion? > > > > This is a good question. Will Kannel do any transform- > > ations to multipart application/octet-stream data ? If it > > does not (and I think it should not) it should only pass > > (and tokenize, of course) content headers to the client. > > It the client that decodes transfer-encoding. > > > > aarno > >
AW: AW: Kannel PPG, PI and character encoding
I think I misrepresented my point: I just encountered an example in RFC2387 where application/octet-stream is represented in BASE64. The same could theoretically happen with any other content (XML encoded in UCS-16 or UTF-8 being a good candidate). I think Kannel should check the Content-Transfer-Encoding header and do its best to correctly handel encoded content. It will most likely encounter BASE64 (quoted printable is just ugly). Supporting BASE64 should be easy: we already have the octstr_base64_to_binary(Octstr *ostr) function, so just a few more lines of code would be required to glue this in. Regards Jörg > -Ursprüngliche Nachricht- > Von: Aarno Syvänen [mailto:[EMAIL PROTECTED]] > Gesendet am: Dienstag, 23. Oktober 2001 11:50 > An: Jörg Pommnitz > Cc: [EMAIL PROTECTED] > Betreff: Re: AW: Kannel PPG, PI and character encoding > > Hi Jörg, > > Jörg Pommnitz wrote: > > > I just read RFC2387: it uses base64 as transfer > > encoding for application/octet-stream data. While > > there is a void octstr_base64_to_binary(Octstr *ostr) > > function in the Kannel source tree it seems not to > > be used in the PPG code. Aarno, what's your opinion? > > This is a good question. Will Kannel do any transform- > ations to multipart application/octet-stream data ? If it > does not (and I think it should not) it should only pass > (and tokenize, of course) content headers to the client. > It the client that decodes transfer-encoding. > > aarno >
Re: AW: Kannel PPG, PI and character encoding
Hi Jörg, Jörg Pommnitz wrote: > I just read RFC2387: it uses base64 as transfer > encoding for application/octet-stream data. While > there is a void octstr_base64_to_binary(Octstr *ostr) > function in the Kannel source tree it seems not to > be used in the PPG code. Aarno, what's your opinion? This is a good question. Will Kannel do any transform- ations to multipart application/octet-stream data ? If it does not (and I think it should not) it should only pass (and tokenize, of course) content headers to the client. It the client that decodes transfer-encoding. aarno
AW: Kannel PPG, PI and character encoding
I just read RFC2387: it uses base64 as transfer encoding for application/octet-stream data. While there is a void octstr_base64_to_binary(Octstr *ostr) function in the Kannel source tree it seems not to be used in the PPG code. Aarno, what's your opinion? Regards Jörg > -Ursprüngliche Nachricht- > Von: Jörg Pommnitz [mailto:[EMAIL PROTECTED]] > Gesendet am: Montag, 22. Oktober 2001 14:13 > An: [EMAIL PROTECTED] > Betreff: Kannel PPG, PI and character encoding > > Hi List, > I have a question about the character encoding to be used > for documents (PAP/SI/SL) to be sent as part of a PAP > request. Normally character encoding is not an issue with > XML files, both ISO-8859 or UTF-8 are OK. Unfortunately > the WAP Push specification adds MIME to the mix: SMTP as > one of the oldest Internet Protocols is not considered to > be 8 bit clean. That's why "unclean" content is normally > wrapped either in quoted-printable or BASE64 encoding. > I'm not sure what to do with multipart MIME messages to be > sent over a HTTP POST request. In this case eight bit > cleanliness is not an issue yet most MIME libraries (in my > case JavaMail) still play it safe and insist on additional > layers of encoding. > So here is my question: What should I do? The WAP Push spec > seems not to address this issue (the examples do not even > include an encoding= statement in their DOCTYPE)... > > Regards > Jörg >
Kannel PPG, PI and character encoding
Hi List, I have a question about the character encoding to be used for documents (PAP/SI/SL) to be sent as part of a PAP request. Normally character encoding is not an issue with XML files, both ISO-8859 or UTF-8 are OK. Unfortunately the WAP Push specification adds MIME to the mix: SMTP as one of the oldest Internet Protocols is not considered to be 8 bit clean. That's why "unclean" content is normally wrapped either in quoted-printable or BASE64 encoding. I'm not sure what to do with multipart MIME messages to be sent over a HTTP POST request. In this case eight bit cleanliness is not an issue yet most MIME libraries (in my case JavaMail) still play it safe and insist on additional layers of encoding. So here is my question: What should I do? The WAP Push spec seems not to address this issue (the examples do not even include an encoding= statement in their DOCTYPE)... Regards Jörg
Re: First version of PPG committed
I will commit documentation today or tomorrow. Aarno - Original Message - From: "Abd Rahman Johari" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Friday, September 28, 2001 10:31 PM Subject: Re: First version of PPG committed > err... > any documentation on this? i wanna give a shot too with my R520m > > regards, > -man- > > On Fri, 28 Sep 2001, Stipe Tolj wrote: > > > > I committed first version of WAP Push Proxy Gateway. This works with SMS > > > bearer, though recently > > > only with HTTP smsc. This means that it translates PAP protocol requests > > > to HTTP requests. All sendsms > > > interfaces should understand these. It is tested with Ericsson T39m > > > mobile phone. > > > > > > Of course test results and comments are very wellcome. > > > > we'll have a shot on that ASAP and report. > > > > Thanks for the great work. > > > > Stipe > > > > >
Re: First version of PPG committed
err... any documentation on this? i wanna give a shot too with my R520m regards, -man- On Fri, 28 Sep 2001, Stipe Tolj wrote: > > I committed first version of WAP Push Proxy Gateway. This works with SMS > > bearer, though recently > > only with HTTP smsc. This means that it translates PAP protocol requests > > to HTTP requests. All sendsms > > interfaces should understand these. It is tested with Ericsson T39m > > mobile phone. > > > > Of course test results and comments are very wellcome. > > we'll have a shot on that ASAP and report. > > Thanks for the great work. > > Stipe >
Re: First version of PPG committed
> I committed first version of WAP Push Proxy Gateway. This works with SMS > bearer, though recently > only with HTTP smsc. This means that it translates PAP protocol requests > to HTTP requests. All sendsms > interfaces should understand these. It is tested with Ericsson T39m > mobile phone. > > Of course test results and comments are very wellcome. we'll have a shot on that ASAP and report. Thanks for the great work. Stipe [EMAIL PROTECTED] --- Wapme Systems AG Münsterstr. 248 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
First version of PPG committed
Hi List, I committed first version of WAP Push Proxy Gateway. This works with SMS bearer, though recently only with HTTP smsc. This means that it translates PAP protocol requests to HTTP requests. All sendsms interfaces should understand these. It is tested with Ericsson T39m mobile phone. Of course test results and comments are very wellcome. Aarno
Re: A note on Kannel PPG
Hi, aarno, Do you mean you are trying to implement push above the bearer of SMS? Is there mobile terminal supporting this? It seems that we will lose another initiator of the kannel project. - Original Message - From: "Aarno Syvänen" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Friday, August 31, 2001 7:41 PM Subject: A note on Kannel PPG > Hi List, > > Wiral put me today on indefinite leave, starting 16.9. I hope that PPG > will work before > this at least with one SMSC (http one is a priority), but I cannot be > certain. After this, > all bets are off. > > Well, only thing I can say is that job offers are very wellcome :( > > aarno > > > >
A note on Kannel PPG
Hi List, Wiral put me today on indefinite leave, starting 16.9. I hope that PPG will work before this at least with one SMSC (http one is a priority), but I cannot be certain. After this, all bets are off. Well, only thing I can say is that job offers are very wellcome :( aarno
