[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: What's the SAR status ??
We are using SAR here at Global Network Inc for wap gateway serving our mmsc. It works quite fine. Aarno On Thursday, February 27, 2003, at 05:23 AM, [EMAIL PROTECTED] wrote: hi all ! We've seen some of SAR patches moving around. I think newer kannel version(1.2.1) supports it. Has anybody tested this functionality with newer gateways ? Or are they still developing SAR ? Does anyone have a new patch ? urs, denzel.
Re: Kannel _ WTLS
Nick Clarey did wtls, maybe he can help you ? Aarno On Monday, February 24, 2003, at 10:21 AM, Obakeng wrote: I would like to develop a WTLS setup using kannel. Do you know if anyone has tried it?
Re: multiple bearer box ?
I once stress tested stand-alone bearerbox. (Standalone meaning I was using smsboxes that did not do any fetch, but returned a standard text message instead.) I got value 1200 msg/s and must use ~20 smsboxes before I reached 100 % cpu utilisation. Cpu was AMD Athlon, 800 MHz. Aarno On Thursday, February 20, 2003, at 08:58 AM, Illimar Reinbusch wrote: Hi We have in total 14 connections to different operators SMSC in thee different countryes and in short term we have reached about 150-200 msg/sec. Illimar I think my peak was in a campaign that was delayed and then I needed every resource available to do it and I had something like 50+15+5+3+2+several 1 msg/sec connections, which gives like 80 msg/sec -- Davi / Bruno.RodriguesatLitux.Org Litux.org: 20:36:09 up 88 days, 21:51, 4 users, load average: 0.85, 0.54, 0.36 'AUTHOR FvwmAuto just appeared one day, nobody knows how. -- FvwmAuto(1x)'
Re: Kannel wap limits ?
If the phone really supports ESAR, it should send number of groups tpi. Otherwise it is just sending content SAR could not handle. Aarno On Tuesday, February 18, 2003, at 11:56 AM, Bruno Rodrigues wrote: Citando Igor Ivoilov [EMAIL PROTECTED]: I have to fix wpt layer to do not panic if psn is going to be 255 but this is a limit of SAR and can be overcome with ESAR. Does 3650 support ESAR? I don't have such a phone to check it by myself So it seems altough kannel's only relevant information is the 350K sdu. -- Davi / Bruno.RodriguesatLitux.Org Litux.org: 10:54:26 up 87 days, 12:10, 8 users, load average: 0.03, 0.05, 0.01 'Linus? Whose that? -- clueless newbie on #Linux'
Re: Urgent Query ??
On Friday, February 14, 2003, at 09:41 PM, Stipe Tolj wrote: Bruno Rodrigues wrote: Citando Stipe Tolj [EMAIL PROTECTED]: No, Kannel is not fully WAP 1.2.1 compliant. We cover the most important parts: WTP-SAR, WAP Push, no UAProf. I might have some news about UAProf one of these days ;) Hint: Deli, Cocoon, Vodafone live that would be great. No, that would very, very, great. You implementation is WAP UAProf based on Profile headers ? (No User Agent header read ?). Most MMS phones actually support UAProf, so one can really use this. New release is OK fro me, because UAProf mean 1.5, and we can bundle all other things into it. Aarno
Re: SMSC emulators
And there is another for cimd2: test/test_cimd2.c. I and others used it as a basis for a server testing environment. Aarno On Friday, February 14, 2003, at 09:21 PM, Stipe Tolj wrote: Benoit Doreau wrote: Hi, I just wanted to know the state in the development of this project, as listed in the web: == == [80 days] SMSC emulators for stress testing In order to properly test the SMSC protocol implementations, we should implement SMSC emulators. This may or may not be helpful for making sure the protocol implmentation themselves are correct, but will make sure there are no timing etc. problems in Kannel related to them. == == Has anything been done? yes. Kannel includes a dummy SMPP server, test/drive_smpp.c which can be used to test the client SMPP side. We at Wapme have implemented an SMPP server/proxy based on Kannel's lib code. It will be open sourced and contributed to Kannel in some upcoming time (without exact estimation yet). 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: [RFC] yesterday commits
I will fix this.
Aarno
On Friday, February 14, 2003, at 08:41 AM, Stipe Tolj wrote:
Hi Aarno,
can you comment on this part of your patch, please:
Index: gateway/gwlib/socket.c
diff -u gateway/gwlib/socket.c:1.53 gateway/gwlib/socket.c:1.54
--- gateway/gwlib/socket.c:1.53 Wed Nov 13 10:22:56 2002
+++ gateway/gwlib/socket.c Thu Feb 13 10:35:48 2003
@@ -510,7 +510,7 @@
}
-static void setup_official_name(void)
+static int setup_official_name(void)
{
struct utsname u;
struct hostent h;
@@ -519,14 +519,15 @@
if (uname(u) == -1)
panic(0, uname failed - can't happen, unless GW_NAME is
buggy.);
if (gw_gethostbyname(h, u.nodename) == -1) {
-error(0, Can't find out official hostname for this host,
- using `%s' instead., u.nodename);
+/*error(0, Can't find out official hostname for this host,
+ using `%s' instead., u.nodename);*/
official_name = octstr_create(u.nodename);
official_ip = octstr_create(127.0.0.1);
-} else {
-official_name = octstr_create(h.h_name);
- official_ip = gw_netaddr_to_octstr(AF_INET, h.h_addr);
-}
+return 0;
+}
+
+official_name = octstr_create(h.h_name);
+official_ip = gw_netaddr_to_octstr(AF_INET, h.h_addr);
}
why is that change necessary?
BTW, it throughs warnings on the automatic compilation test, as you
may have noticed. See devel-report@ 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: [RFC] yesterday commits
As a matter of fact, there is one: make check will fail, when socket.c reports this error. It is not always fatal one: config file may supply official name and official ip. But yes, it would be better to fix make check. Aarno On Friday, February 14, 2003, at 10:54 AM, Stipe Tolj wrote: Aarno Syvänen wrote: I will fix this. I'd prefer a roll-back to the previous revision for the gwlib/socket.c file, cause there haven't been any bug or problem reports on this issue. 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: MMS-Ind: Ports and expiry date
Actually, in mms notification, you can use any source port, but you must use *some*. (Sms port IE is defined this way.) Aarno On Tuesday, February 11, 2003, at 03:04 AM, Stipe Tolj wrote: Friedrich, Jason Brian wrote: could somebody tell me more about the ports section in the mms notification? Why is there a source and destination port? I thought that only a destination port is necessary. (Nokia has different ports for different applications). MMS notifications are pushed via WAP Push, which may also been utilaized over IP, hence source addresses are of possible relevance. 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 = foo # the default smsc-id to use in bearerbox this is pretty easy, but what about this: ... grou = wap-push-user ... smsc-id = foo # 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: MMS over WAP
On Sunday, January 26, 2003, at 01:37 PM, Stipe Tolj wrote: Shridhar Raju wrote: In my opinion, MMS is nothing but a glorified WAP. As capabilities of Mobile terminals increasing day by day, newer media are transfered over WAP. WAP is a building block for MMS. that's true. But remember that basically you need only HTTP to transfer MMS messages. So WAP is used to encapsulate HTTP. You may leave it if you wanted to. (from the perspective of an device manufacturer). The problem would be that the officials would claim, that you are not allowed to call your device MMS-capable, because it does not follow the WAP specific specs. Stipe There is more in MMS than just tokenized HTTP. You must be able to push notifications and delivery reports to the phone. 3GPP spec indeed mention future IP based MMS. But: a) protocol mentioned is WAP 2.0. (Which means wireless TCP and wireless HTTP.) b) it does not yet specify the push protocol. Aarno
Re: Sending push using sendsms?
The phones must first support this kind of push, of course. Aarno On Thursday, January 23, 2003, at 10:21 AM, Damir Salantic wrote: In Kannel user guide I found: The push content is sended to the phones over SMS, but the content is fetched by the phone over IP bearer, for instance CSD or GPRS. Because Push Proxy Gateway tokenises SI and SL documents, it may fit one SMS message (if not, it is segmented for transfer). Using two bearers seems to be an unnecessary complication. But quite simply, phones currently operate this way. Push over GPRS can only simplify matters. I'm not sure if that answers your question, and if that works, but I have an additional question: Is it possible to send SI directly over WSP (IP bearer - GPRS) and not over SMS? It seems to me that WAP PUSH specification enables that possibility. Is that (going to be) supported in Kannel? Thanks Damir Salantic On Thu, 23 Jan 2003, [iso-8859-1] Peter Löfman wrote: Is it possible to send a SI message using sendsms cgi script? If so, has anyone done it? Any example? /Peter Lofman
Re: WSPMachine destroying question
Implementing timers at wsp level is easiest way to do this. Aarno On Tuesday, January 14, 2003, at 10:20 AM, Vjacheslav Chekushin wrote: Hi, Aarno. Aarno Syvänen wrote: Hi Vjacheslav, On Monday, January 13, 2003, at 03:13 PM, Vjacheslav Chekushin wrote: WSPMachine is destroyed if state=NULL_SESSION But how WSPMachine will be desroyed if client doesn't send disconnect event but simply end his session without any indication (And WSPMachine remains in state CONNECTED). You mean stop wap browsing ? This does not indeed end session, because the client may resume browsing. Disconnecting is a separate event. After browsing you can select from menu something like 'Quit browsing' and user agent correctly sends disconnect event. But I suspect if you simply press HangUp button, UserAgent simply go out without disconnect event. (I checked it at least with some phones). And users mostly end its sessions by this way. So if you have heavy load it becomes the problem. For example our WAP gateway grows approximatly at 100MB every day. So I agree that this is phone problem, but I think kannel must handle it someway. Will WSPMachine be destroyed after some time or it will be stored in WSPMachine list untill we stop WAP gateway? WSPSessionMachine will stay until client disconnects separately, if connection- oriented service is used. I describe it with example: I work with one phone and sequentialy create 3 sessions. But thease sessions has been removed only when I stpopped gateway: 2003-01-10 14:19:40 [0] DEBUG: Waiting for 1 (wap/wsp_session.c:main_thread) to terminate 2003-01-10 14:19:40 [1] DEBUG: Thread 1 (wap/wsp_session.c:main_thread) terminates. 2003-01-10 14:19:40 [0] DEBUG: WSP: 3 session machines left. 2003-01-10 14:19:40 [0] DEBUG: Destroying WSPMachine 0x41a10388 2003-01-10 14:19:40 [0] DEBUG: Destroying WSPMachine 0x41a07fd8 2003-01-10 14:19:40 [0] DEBUG: Destroying WSPMachine 0x8209500 You can always use connectionless service, if you for some reason cannot disconnect sessions. Aarno -- Vjacheslav Chekushinmailto:[EMAIL PROTECTED] Latvian Mobile Phone Companyhttp://www.lmt.lv
Re: WSPMachine destroying question
Hi Vjacheslav, On Monday, January 13, 2003, at 03:13 PM, Vjacheslav Chekushin wrote: WSPMachine is destroyed if state=NULL_SESSION But how WSPMachine will be desroyed if client doesn't send disconnect event but simply end his session without any indication (And WSPMachine remains in state CONNECTED). You mean stop wap browsing ? This does not indeed end session, because the client may resume browsing. Disconnecting is a separate event. Will WSPMachine be destroyed after some time or it will be stored in WSPMachine list untill we stop WAP gateway? WSPSessionMachine will stay until client disconnects separately, if connection- oriented service is used. I describe it with example: I work with one phone and sequentialy create 3 sessions. But thease sessions has been removed only when I stpopped gateway: 2003-01-10 14:19:40 [0] DEBUG: Waiting for 1 (wap/wsp_session.c:main_thread) to terminate 2003-01-10 14:19:40 [1] DEBUG: Thread 1 (wap/wsp_session.c:main_thread) terminates. 2003-01-10 14:19:40 [0] DEBUG: WSP: 3 session machines left. 2003-01-10 14:19:40 [0] DEBUG: Destroying WSPMachine 0x41a10388 2003-01-10 14:19:40 [0] DEBUG: Destroying WSPMachine 0x41a07fd8 2003-01-10 14:19:40 [0] DEBUG: Destroying WSPMachine 0x8209500 You can always use connectionless service, if you for some reason cannot disconnect sessions. Aarno
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
MMS OTA configuration for Siemens S55
Hi List, Have anybody succeeded sending OTA config message to this phone ? Aarno
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: http_header_pack
It is supposed to create a comma separated list for http header values.
Aarno
On Thursday, January 2, 2003, at 11:03 AM, Vjacheslav Chekushin wrote:
Hi, list
There is http_header_pack() function declared in http.h.
It used in wap-appl.c
Now it doesn't implemented:
void http_header_pack(List *headers)
{
gwlib_assert_init();
gw_assert(headers != NULL);
/* XXX not implemented yet. */
}
And I can't find any description for it.
Does anybody know what it intended for?
--
Vjacheslav Chekushinmailto:[EMAIL PROTECTED]
Latvian Mobile Phone Companyhttp://www.lmt.lv
Re: Configuration variable timer-freq
Yes, this was a case of disappearing patch, but user guide still mentioned timer-freq. Setting value 2 doubles all timers, and so on. Btw, I noticed that when kannel returns 30 kb mm content, it sends about 60 segments, which takes quite a time. Igor, is is this Kannel or the phone ? Aarno On Thursday, December 26, 2002, at 04:58 PM, Stipe Tolj wrote: Aarno Syvänen wrote: noticed that this one has no effect at all. We may need it, when doing mm, because mm contents are much bigger wap wml decks. So I would commit patch making timer-freq working as stated in user guide. are the new directives documented in the user's guide?! 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
Configuration variable timer-freq
Hi List, noticed that this one has no effect at all. We may need it, when doing mm, because mm contents are much bigger wap wml decks. So I would commit patch making timer-freq working as stated in user guide. Aarno
Bug in wtp_pack_sar_ack
Hi List, in wtp_pack_sar_ack we have following: unsigned char cpsn; sprintf(cpsn, %c, psn); this does not work, because sprintf tries to add /0 for an end of the string, and cspn is only one byte long. simply doing: unsigned char cpsn; unsigned char damn[256]; sprintf(cpsn, %c, psn); removes segfault, because now sprintf writes /0 to space reserved by damn. But of course one wants a real fix. aarno
Re: WAP in CVS
Do you mean with simple browsing or with mms with messages containing say 40 kb pics ? Aarno On Tuesday, December 10, 2002, at 12:19 PM, Stipe Tolj wrote: Andreas Fink wrote: The WAP version in CVS seems to be totally screwed. It doesnt work for Nokia 7650 and Nokia 7210. Not for MMS or for WAP browsing. It was working fine before. Whats wrong now? hmm, works for me with the current cvs tree and Nokia Mobile Toolkit in both, connection orientated and non-orientated modes. Any others that have problems running the default setup?! 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: more m-notification-ind
What are your http headers ? And our udh ? Aarno On Wednesday, December 4, 2002, at 05:16 PM, Matias Lahti wrote: Hello! I'm trying to send a m-notification-ind, which has been the source of plenty of headaches for plenty of people too.. Hopefully Alex releases the FAQ soon :) Anyway - this is what I'm sending, without getting any reply from my nokia 7650: 01 transaction id 06 pushtype 20 headerlen 6170706C69636174696F6E2F766E642E7761702E6D6D732D6D65737361676500 a p p l i c a t i o n / v n d . w a p . m m s - m e s s a g e 8C 82 m-notification 98 41 00 transid: A 8D 90 mmsver 1.0 89 16 from, length 22 802B3132333435363738392F545950453D504C4D4E00 + 1 2 3 4 5 6 7 8 9 / T Y P E = P L M N 96 subject 7465737400 t e s t 8A 80 msgclass personal 8E 02 0B 05 msgsize 2 bytes, 0b 05 = 2821 88 05 81 03 01 51 80 expiry, relative 86400 83 location 687474703A2F2F772F74657374692E6D6D7300 h t t p : / / w w w / t e s t i . m m s Any ideas what might be wrong? - Matias Lahti
Re: MMS m-notification-ind and test_ppg
On Tuesday, December 3, 2002, at 07:07 PM, Alex Judd wrote: Yep agreed. We can either force all carriage returns to use the CRLF standard on parsing of the page (recommended route) or have a system/carriage return character switch on the command line. I would go for standard confirming There's a few other minor modifications I'd like to make to test_ppg etc. so I'd be happy to implement the changes necessary. BTW does the content look right? Yes, all mandatory headers were there. Aarno Alex - Original Message - From: Aarno Syvänen [EMAIL PROTECTED] To: Alex Judd [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Tuesday, December 03, 2002 3:41 PM Subject: Re: MMS m-notification-ind and test_ppg This indeed causes problems, though CRLF line break is one defined by MIME standard. Perhaps command line option for line break would be usefull - i mean one translating input break to standard ones. Aarno On Friday, November 29, 2002, at 05:13 PM, Alex Judd wrote: I was using binary as wappush returns a syntax error if I wasn't encoding the data. test_ppg seems to use windows (oa,od) carriage returns for it's joined lines, whereas my system is using xnix(oa) carriage returns. Don't know if this would cause the problem I enclosed the dumps below. 2002-11-29 17:11:42 [1] DEBUG: data: 3c 62 61 64 6d 65 73 73 badmess 2002-11-29 17:11:42 [1] DEBUG: data: 61 67 65 2d 72 65 73 70 age-resp 2002-11-29 17:11:42 [1] DEBUG: data: 6f 6e 73 65 20 63 6f 64 onse cod 2002-11-29 17:11:42 [1] DEBUG: data: 65 3d 22 32 30 30 30 22 e=2000 2002-11-29 17:11:42 [1] DEBUG: data: 20 64 65 73 63 3d 22 4e desc=N 2002-11-29 17:11:42 [1] DEBUG: data: 6f 74 20 75 6e 64 65 72 ot under 2002-11-29 17:11:42 [1] DEBUG: data: 73 74 6f 6f 64 20 64 75 stood du 2002-11-29 17:11:42 [1] DEBUG: data: 65 20 74 6f 20 6d 61 6c e to mal 2002-11-29 17:11:42 [1] DEBUG: data: 66 6f 72 6d 65 64 20 73 formed s 2002-11-29 17:11:42 [1] DEBUG: data: 79 6e 74 61 78 22 3e 3c yntax 2002-11-29 17:11:42 [1] DEBUG: data: 2f 62 61 64 6d 65 73 73 /badmess 2002-11-29 17:11:42 [1] DEBUG: data: 61 67 65 2d 72 65 73 70 age-resp 2002-11-29 17:11:42 [1] DEBUG: data: 6f 6e 73 65 3e 3c 2f 70 onse/p 2002-11-29 17:11:42 [1] DEBUG: data: 61 70 3e ap From debugging the message the total wappush is POST /wappush?username=password= HTTP/1.1 (0a,0d)Host: localhost:8080 (0a,0d)Content-Type:multipart/related; boundary=asdlfkjiurwghasf; type=application/xml (0a,0d)X-WAP-Application-Id: mms.ua (0a,0d)Content-Length: 779 (0a,0d) (0a,0d) (0a,0d)--asdlfkjiurwghasf (0a,0d)Content-Type: application/xml (0a,0d)?xml version=1.0? (0a)!DOCTYPEpap PUBLIC -//WAPFORUM//DTD PAP//EN http://www.wapforum.org/DTD/pap_1.0.dtd; (0a)pap (0a) push-message push-id=[EMAIL PROTECTED] progress-notes-requested=false (0a) address address-value=[EMAIL PROTECTED] (0a) /address (0a) /push-message (0a)/pap (0a,0d) (0a)--asdlfkjiurwghasf (0a,0d)Content-Type: application/vnd.wap.mms-message (0a,0d)Content-Type:application/vnd.wap.mms-message (0a)X-Mms-Message-Type:m-notification-ind (0a)X-Mms-Transaction-Id:125 (0a)X-Mms-Version:1.0 (0a)X-Mms-Message-Class:Personal (0a)X-Mms-Message-Size:4910 (0a)X-Mms-Expiry:256;type=relative (0a)X-Mms-Content-Location:http://212.118.244.25/mmstest/m4.mms (0a)X-WAP-Application-Id:x-wap-application:mms.ua\ (0a,0d) (0a)--asdlfkjiurwghasf--
Re: MMS m-notification-ind and test_ppg
This indeed causes problems, though CRLF line break is one defined by MIME standard. Perhaps command line option for line break would be usefull - i mean one translating input break to standard ones. Aarno On Friday, November 29, 2002, at 05:13 PM, Alex Judd wrote: I was using binary as wappush returns a syntax error if I wasn't encoding the data. test_ppg seems to use windows (oa,od) carriage returns for it's joined lines, whereas my system is using xnix(oa) carriage returns. Don't know if this would cause the problem I enclosed the dumps below. 2002-11-29 17:11:42 [1] DEBUG: data: 3c 62 61 64 6d 65 73 73 badmess 2002-11-29 17:11:42 [1] DEBUG: data: 61 67 65 2d 72 65 73 70 age-resp 2002-11-29 17:11:42 [1] DEBUG: data: 6f 6e 73 65 20 63 6f 64 onse cod 2002-11-29 17:11:42 [1] DEBUG: data: 65 3d 22 32 30 30 30 22 e=2000 2002-11-29 17:11:42 [1] DEBUG: data: 20 64 65 73 63 3d 22 4e desc=N 2002-11-29 17:11:42 [1] DEBUG: data: 6f 74 20 75 6e 64 65 72 ot under 2002-11-29 17:11:42 [1] DEBUG: data: 73 74 6f 6f 64 20 64 75 stood du 2002-11-29 17:11:42 [1] DEBUG: data: 65 20 74 6f 20 6d 61 6c e to mal 2002-11-29 17:11:42 [1] DEBUG: data: 66 6f 72 6d 65 64 20 73 formed s 2002-11-29 17:11:42 [1] DEBUG: data: 79 6e 74 61 78 22 3e 3c yntax 2002-11-29 17:11:42 [1] DEBUG: data: 2f 62 61 64 6d 65 73 73 /badmess 2002-11-29 17:11:42 [1] DEBUG: data: 61 67 65 2d 72 65 73 70 age-resp 2002-11-29 17:11:42 [1] DEBUG: data: 6f 6e 73 65 3e 3c 2f 70 onse/p 2002-11-29 17:11:42 [1] DEBUG: data: 61 70 3e ap From debugging the message the total wappush is POST /wappush?username=password= HTTP/1.1 (0a,0d)Host: localhost:8080 (0a,0d)Content-Type:multipart/related; boundary=asdlfkjiurwghasf; type=application/xml (0a,0d)X-WAP-Application-Id: mms.ua (0a,0d)Content-Length: 779 (0a,0d) (0a,0d) (0a,0d)--asdlfkjiurwghasf (0a,0d)Content-Type: application/xml (0a,0d)?xml version=1.0? (0a)!DOCTYPEpap PUBLIC -//WAPFORUM//DTD PAP//EN http://www.wapforum.org/DTD/pap_1.0.dtd; (0a)pap (0a) push-message push-id=[EMAIL PROTECTED] progress-notes-requested=false (0a) address address-value=[EMAIL PROTECTED] (0a) /address (0a) /push-message (0a)/pap (0a,0d) (0a)--asdlfkjiurwghasf (0a,0d)Content-Type: application/vnd.wap.mms-message (0a,0d)Content-Type:application/vnd.wap.mms-message (0a)X-Mms-Message-Type:m-notification-ind (0a)X-Mms-Transaction-Id:125 (0a)X-Mms-Version:1.0 (0a)X-Mms-Message-Class:Personal (0a)X-Mms-Message-Size:4910 (0a)X-Mms-Expiry:256;type=relative (0a)X-Mms-Content-Location:http://212.118.244.25/mmstest/m4.mms (0a)X-WAP-Application-Id:x-wap-application:mms.ua\ (0a,0d) (0a)--asdlfkjiurwghasf--
Re: MMS m-notification-ind and test_ppg
Why base64 ? Why not binary (without -e flag)? Aarno On Wednesday, November 27, 2002, at 06:20 PM, Alex Judd wrote: Aarno/Paul/Ivor/Andreas/Marco I've been reading everyones post and problems on the Kannel mailing list in depth with MMS notification sending and so far are still having problems which I can't resolve - therefore wondering if you anyone can shed any light with a couple of problems that I'm having with it. 1. Tokenisation of the m-notification txt file I'm currently doing this using test_ppg and the output I'm getting is very different from your 'humanised' tokenizing. Using ../test/test_ppg -e base64 -a mms -c mms http://localhost:8080/wappush?username=yyypassword=xxx; m-notification-ind.txt pap.txt' I get 2002-11-27 16:42:05 Sent SMS [SMSC:889567] [SVC:test] [ACT:] [from:2199] [to:+447740305115] [flags:0:2:0:0:0] [msg:128:06063ABE966C6F63616C686F73743A3830383000AF84436F6E74656E742D54 72616 E736665722D456E636F64696E670062696E617279008D020146B480436F6E74656E742D 54797 0653A206170706C69636174696F6E2F766E642E7761702E6D6D732D6D6573736167650A 582D4 D6D732D4D6573736167652D547970653A206D] [udh:12:0B05040B8423F3060301] 2002-11-27 16:42:05 Sent SMS [SMSC:889567] [SVC:test] [ACT:] [from:2199] [to:+447740305115] [flags:0:2:0:0:0] [msg:128:72793A203235363B20747970653D72656C61746976650A582D4D6D732D436F 6E746 56E742D4C6F636174696F6E3A20687474703A2F2F3231322E3131382E3234342E32352F 6D6D7 3746573742F6D312E6D6D730A582D5741502D4170706C69636174696F6E2D49643A2078 2D776 1702D6170706C69636174696F6E3A6D6D732E] [udh:12:0B05040B8423F3060303] 2002-11-27 16:42:05 Sent SMS [SMSC:889567] [SVC:test] [ACT:] [from:2199] [to:+447740305115] [flags:0:2:0:0:0] [msg:128:2D6E6F74696669636174696F6E2D696E640A582D4D6D732D5472616E736163 74696 F6E2D49643A203132350A582D4D6D732D56657273696F6E3A20312E300A582D4D6D732D 4D657 3736167652D436C6173733A20506572736F6E616C0A582D4D6D732D4D6573736167652D 53697 A653A20343931300A582D4D6D732D45787069] [udh:12:0B05040B8423F3060302] from (m-notification-ind.txt) X-Mms-Message-Type: m-notification-ind X-Mms-Transaction-Id: 125 X-Mms-Version: 1.0 X-Mms-Message-Class: Personal X-Mms-Message-Size: 4910 X-Mms-Expiry: 256; type=relative X-Mms-Content-Location: http://212.118.244.25/mmstest/m1.mms X-WAP-Application-Id: x-wap-application:mms.ua and (pap.txt) ?xml version=1.0? !DOCTYPE pap PUBLIC -//WAPFORUM//DTD PAP//EN http://www.wapforum.org/DTD/pap_1.0.dtd; pap push-message push-id=[EMAIL PROTECTED] progress-notes-requested=false address address-value=[EMAIL PROTECTED] /address /push-message /pap whereas my understanding is that I should get 8c8298 etc. The working m-notification-ind message I've been using to test is http://212.118.244.25:13013/cgi-bin/ sendsms?username=xxxpassword=yyyto=+44 7740305115from=testudh=%06%05%04%0b%84%23%f0text=%0f%06%03%be%af%84% 8c%82 %98%39%39%39%35%40%66%6c%79%65%72%6f%6e%65%2e%63%6f%6d%00%8d%90%8a%80%8 e%01% 64%88%06%80%04%3d%64%8d%80%83http://212.118.244.25/mmstest/mms.wml%00 which at least initiates a call to my wap server to receive the content. The 3 part message I can 'hear' receiving the message but can't see any call to the webserver. Also interestingly, my external server looks as though it receives the multipart message in order of 0,2,1 however I'm guessing the message will still be arranged correctly by Kannel. 2. Serving MMS content I've configured Apache to serve .mms files with the content type application/vnd.wap.mms-message (thanks Ivor) however the phone complains of a formatting error when it recieves the message. I'm using Nokia encoded binary messages here which should in theory work. Again, open for suggestions as how to verify these messages are correct. Thoughts are that I may need to use Kannel as a proxy to fetch the content from the Apache server and serve it itself. Guessing that might be the SAR issue that has been resolved that stopped this happening before however now works. Thanks for the help so far :) Alex Skywire
Re: m-notification-ind question
What phone are you working with ? Aarno On Monday, November 25, 2002, at 04:47 PM, Alex Judd wrote: I'm seem to be getting very different udh's generated from test_ppg than those from the text m-notification-ind that works. 1. Working udh udh=%06%05%04%0b%84%23%f0 2. Nonworking test_ppg generated UDH(s) [multi-part-message] [udh:12:0B05040B8423F3000301] [udh:12:0B05040B8423F3000302] [udh:12:0B05040B8423F3000303] My SMSC is returning FAILED at trying to deliver the test_ppg generated ones. However, sending a manual created message works fine. Any ideas? Regards Alex
Re: [Fwd: Re: wap push receiving on siemens]
can you use siemens as a modem ? Then logs would be more revealing. Aarno On Monday, November 25, 2002, at 12:07 PM, Szymon Stasik wrote: kannel.log is only (with log-level 0): 2002-11-22 02:58:20 [16] DEBUG: boxc_receiver: got sms from wapbox 2002-11-22 02:58:20 [9] DEBUG: smscconn_sender (CIMD2:xxx.xxx.xxx.xxx:9971:test_ae): sending message 2002-11-22 02:58:20 [1] DEBUG: Dumping 0 messages and 0 acks to store regards, Szymon Aarno Syvänen wrote: And the bearerbox log ? Aarno On Sunday, November 24, 2002, at 02:25 PM, Szymon Stasik wrote: my mistake - I have replied to the sender, not the mailing list. Original Message Subject: Re: wap push receiving on siemens Date: Sun, 24 Nov 2002 04:00:27 +0100 From: Stipe Tolj [EMAIL PROTECTED] Organization: Wapme Systems AG To: Szymon Stasik [EMAIL PROTECTED] References: [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] Szymon Stasik wrote: wapbox.log looks faine - here it is: 2002-11-22 02:58:19 [11] DEBUG: HTTP: Creating HTTPClient for `127.0.0.1'. 2002-11-22 02:58:20 [14] INFO: PPG: Accept request /cgi-bin/wap-push.cgi from 127.0.0.1 2002-11-22 02:58:20 [14] DEBUG: PPG: http_read_thread: pap multipart accepted 2002-11-22 02:58:20 [14] INFO: client address was +48x, accepted 2002-11-22 02:58:20 [14] DEBUG: PAP COMPILER: doing semantic analysis for address type a phone number 2002-11-22 02:58:20 [14] DEBUG: using defaults instead of anys 2002-11-22 02:58:20 [14] DEBUG: PPG: http_read_thread: pap control entity compiled ok 2002-11-22 02:58:20 [14] DEBUG: PPG: transform_message: push message content and headers valid 2002-11-22 02:58:20 [14] DEBUG: PPG: push machine 9 created 2002-11-22 02:58:20 [14] DEBUG: PPG: store_push_data: push machine 9 appended to unit push list 2002-11-22 02:58:20 [14] DEBUG: PPG: send_push_response: telling pi 2002-11-22 02:58:20 [14] DEBUG: HTTP: Resetting HTTPClient for `127.0.0.1'. 2002-11-22 02:58:20 [14] INFO: PPG: handle_push_message: push message accepted for processing 2002-11-22 02:58:20 [9] DEBUG: OTA: event arrived 2002-11-22 02:58:20 [9] DEBUG: OTA: made connectionless session service request 2002-11-22 02:58:20 [2] DEBUG: WSP_UNIT: Connectionless push accepted 2002-11-22 02:58:20 [2] DEBUG: WSP_UNIT: delivering to wdp 2002-11-22 02:58:20 [14] DEBUG: PPG: OTA request for unit push 2002-11-22 02:58:20 [14] INFO: PPG: unconfirmed push delivered to OTA 2002-11-22 02:58:20 [14] DEBUG: PPG: destroying push machine 9 2002-11-22 02:58:20 [10] DEBUG: HTTP: Destroying HTTPClient area 0x810aba8. 2002-11-22 02:58:20 [10] DEBUG: HTTP: Destroying HTTPClient for `127.0.0.1'. please pass log snapshots allways to the mailing list and not to persons seperately. This way everyone can check them and quote if they recognize something that may point to the probelm itself. So please forward 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: Request UAProf??
Fetch url in Profile header. Aarno On Tuesday, November 26, 2002, at 11:53 AM, amit sehgal wrote: Hi All, Can anyone plz tell how to specifically request a mobile phone for its UAProfile ? Thanx in advance regards amit sehgal
Re: wap push to siemens again
UDH (both ports and SAR) are defined in WAP-259 (WDP Spec). Port numbers are capitulated in appendix 4 (A.4). SI spec is WAP-167 (contains an example tokenized SI document). Usually only Content-type is required here (actually WAP-145 states that only it is mandatory). What kind of Siemens phone did you use ? And a very stupid question: does it support WAP 1.2 ? Aarno On Friday, November 22, 2002, at 02:11 AM, Szymon Stasik wrote: and which wap spec should I look into? I guess there is something wrong in UDH... Stipe Tolj wrote: I'd like to investigate the problem deeper and my question is if there is any possibility to have some push message correctly recognised on siemens phone? I can look into wapforum specs, however any working case or some other tips would be helpfull. unfortunatly we at Wapme don't have these phones here, otherwise I may test too. Anyone that could provide more debugging here?! 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: [Fwd: Re: wap push receiving on siemens]
And the bearerbox log ? Aarno On Sunday, November 24, 2002, at 02:25 PM, Szymon Stasik wrote: my mistake - I have replied to the sender, not the mailing list. Original Message Subject: Re: wap push receiving on siemens Date: Sun, 24 Nov 2002 04:00:27 +0100 From: Stipe Tolj [EMAIL PROTECTED] Organization: Wapme Systems AG To: Szymon Stasik [EMAIL PROTECTED] References: [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] Szymon Stasik wrote: wapbox.log looks faine - here it is: 2002-11-22 02:58:19 [11] DEBUG: HTTP: Creating HTTPClient for `127.0.0.1'. 2002-11-22 02:58:20 [14] INFO: PPG: Accept request /cgi-bin/wap-push.cgi from 127.0.0.1 2002-11-22 02:58:20 [14] DEBUG: PPG: http_read_thread: pap multipart accepted 2002-11-22 02:58:20 [14] INFO: client address was +48x, accepted 2002-11-22 02:58:20 [14] DEBUG: PAP COMPILER: doing semantic analysis for address type a phone number 2002-11-22 02:58:20 [14] DEBUG: using defaults instead of anys 2002-11-22 02:58:20 [14] DEBUG: PPG: http_read_thread: pap control entity compiled ok 2002-11-22 02:58:20 [14] DEBUG: PPG: transform_message: push message content and headers valid 2002-11-22 02:58:20 [14] DEBUG: PPG: push machine 9 created 2002-11-22 02:58:20 [14] DEBUG: PPG: store_push_data: push machine 9 appended to unit push list 2002-11-22 02:58:20 [14] DEBUG: PPG: send_push_response: telling pi 2002-11-22 02:58:20 [14] DEBUG: HTTP: Resetting HTTPClient for `127.0.0.1'. 2002-11-22 02:58:20 [14] INFO: PPG: handle_push_message: push message accepted for processing 2002-11-22 02:58:20 [9] DEBUG: OTA: event arrived 2002-11-22 02:58:20 [9] DEBUG: OTA: made connectionless session service request 2002-11-22 02:58:20 [2] DEBUG: WSP_UNIT: Connectionless push accepted 2002-11-22 02:58:20 [2] DEBUG: WSP_UNIT: delivering to wdp 2002-11-22 02:58:20 [14] DEBUG: PPG: OTA request for unit push 2002-11-22 02:58:20 [14] INFO: PPG: unconfirmed push delivered to OTA 2002-11-22 02:58:20 [14] DEBUG: PPG: destroying push machine 9 2002-11-22 02:58:20 [10] DEBUG: HTTP: Destroying HTTPClient area 0x810aba8. 2002-11-22 02:58:20 [10] DEBUG: HTTP: Destroying HTTPClient for `127.0.0.1'. please pass log snapshots allways to the mailing list and not to persons seperately. This way everyone can check them and quote if they recognize something that may point to the probelm itself. So please forward 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: Client SDU size problem with nokia 7210
Can we vote for giving Igor commit rights, too ? +1 from me, SAR patch was very good. Aarno On Sunday, November 24, 2002, at 04:38 AM, Stipe Tolj wrote: Some time ago this problem was reported by Vjacheslav, but the reason was pointed not correctly. Actually n7210 sends SDU size, but it concatenates connect and get requests into 1 packet. Wsp layer made update of client_SDU_size on S-Connect.res, that happens after get event in this case. So here is a patch to fix the problem that works fine for me thanks for the patch Igor. Can anyone confirm this and vote for the patch?! 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: SDU-Size and UAProfiles
Hi Vjacheslav, Long way to do this is: a) take value of Profile header, fetch the url. b) parse the document, get Client SDU size here b) store size, use stored value later Yes, there are rdf parsers around (one called sirpac, at least, if memory servers me rigth). If you are interested doing, I would like to help you. There are of course short cuts: a) store data of all phone models to a database (not all phones do User Agent Profiling, of course). b) not *parse* the document, just do octstr_search for client SDU size. In long run, UA prof would be useful, because profile contains lots of data about phone. You would be able customize your application for a particular phone. Aarno On Thursday, November 14, 2002, at 08:25 AM, Vjacheslav Chekushin wrote: Hi, list. New phones go to market, they support new specifications... I have tested how Nokia 7210 handles MMS. The problem is that this phone (at least with my soft version) don't use SDU-Size parameter but UAprofiling (http://nds.nokia.com/uaprof/N7210r100.xml). So WAP gw take default value 1400 and phone can't fetch mms from server. Now I simply remove SDU-Size checking from kannel, but it's temporary solution. What people think about this? -- Vjacheslav Chekushinmailto:[EMAIL PROTECTED] Latvian Mobile Phone Companyhttp://www.lmt.lv
Re: wap push receiving on siemens
Hello, there is a bug in ppg, it sends host header to the phone, even though this one is meaningful only for pi-ppg transaction. So can you add function call http_ header_remove_all(push_headers, Host) into module gw/wap_push_ppg.c, into function pap_request thread, before test if (!headers_acceptable). Aarno On Saturday, November 16, 2002, at 01:13 PM, Szymon Stasik wrote: Hello, I'm tring the wap push service with different phones. It works for me with all newer ericssons, nokia 3410, 6310, motorola v66, however I have a problem with siemens me45 and mt50 (same as m50). Kannel version is 1.2.0 the problem is that wap push message shows in sms inbos as data mesasge containing some strange characters ending with something like 'Host' header and sending user agent. While checking push settings in a phone - everyting seems to be ok - full access for receiving push messages. maybe someone have some test example that works with siemens? I am using folowing test (problem exists for both si and sl messages; all works for any other phones): $test_ppg -c si http://127.0.0.1:8181/cgi-bin/wap-push.cgi?username=***''password=*** si.xml pap.xml here is data http-posted to kannel: POST /cgi-bin/wap-push.cgi?username=***password=*** HTTP/1.1 Host: 127.0.0.1:8181 Content-Type: multipart/related; boundary=asdlfkjiurwghasf; type=application/xml X-WAP-Application-Id: http://www.efigence.com:* Content-Length: 1175 --asdlfkjiurwghasf Content-Type: application/xml ?xml version=1.0? !DOCTYPE pap PUBLIC -//WAPFORUM//DTD PAP//EN http://www.wapforum.org/DTD/pap_1.0.dtd; pap push-message push-id=[EMAIL PROTECTED] deliver-before-timestamp=2002-11-28T06:45:00Z deliver-after-timestamp=2002-10-28T06:45:00Z progress-notes-requested=false address address-value=[EMAIL PROTECTED] /address quality-of-service priority=low delivery-method=unconfirmed network-required=true network=GSM bearer-required=true bearer=SMS /quality-of-service /push-message /pap --asdlfkjiurwghasf Content-Type: text/vnd.wap.si ?xml version=1.0? !DOCTYPE si PUBLIC -//WAPFORUM//DTD SI 1.0//EN http://www.wapforum.org/DTD/si.dtd; si indication href=http://wap.sth.pl/test/g.wml; si-id=[EMAIL PROTECTED] action=signal-high created=2002-10-28T15:23:15Z si-expires=2002-11-28T00:00:00Z Some tested content /indication /si --asdlfkjiurwghasf-- regards, Szymon
Re: Bug in wap_push_ppg.c ?
Yeah. Thanks for the report. Aarno On Monday, November 18, 2002, at 02:52 PM, Paul Keogh wrote: The push response seems to be inconsistent with the DTD for this spec. Specifically, the child element response-result is outside the push-response element when according to the DTD and the PAP spec (wap-247,section 8.3 page 21) it should be inside the push-response element. Attached is a patch which may not apply as my srcs are a little out of sync... Patch: RCS file: /home/cvs/cvsroot/wirelesswindow/gw/wap_push_ppg.c,v retrieving revision 1.28 diff -r1.28 wap_push_ppg.c 2774d2773 /push-response 2786a2786 /push-response 2794c2794,2795 debug(wap.push.ppg, 0, PPG: send_push_response: telling pi); --- debug(wap.push.ppg, 0, PPG: send_push_response: telling pi (%s), octstr_get_cstr (reply_body)); Paul Keogh ANAM Wireless Internet Solutions http://www.anam.com +353 1 284 7555 (wired) +353 86 234 6047 (wireless) Castle Yard, Saint Patrick's Road, Dalkey, County Dublin, Ireland
Re: Problems with large wap-push?
Notifications worked for me, too, until I send one having only a few letters in its second segment. This did not work. Aarno On Monday, November 11, 2002, at 08:28 PM, Stipe Tolj wrote: Yes, there is indeed is a bug in wapbox (ppg) sms splitting. You should remove gw/wapbox.c, line max_msgs = (msg_len/MAX_SMS_OCTETS) + 1; Are you sure about this ? - it's working OK for me... yep, our PPG doing MMS notifications works too. 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: Problems with large wap-push?
Yes, there is indeed is a bug in wapbox (ppg) sms splitting. You should remove gw/wapbox.c, line max_msgs = (msg_len/MAX_SMS_OCTETS) + 1; one should instead use max-messages (and concatenate) configuration variables. Yes, adding another config variable is not a good thing. But this way wapbox would be consistent with smsbox. Aarno On Thursday, November 7, 2002, at 02:36 PM, Stipe Tolj wrote: We're using Kannel 1.2.0 as a PPG/wap-gateway. Push is working very fine up to a certain size of the push message (somewhere around 150-160 bytes). When pushing larger messages everything looks ok, but the phone rejects/discards the push message. Is there a limitation in Kannel, or could it be any configuration?? we send MMS notification messages via PPG and it splits to two SMS which is in sum larger then 160 bytes and it works. Hmmm, can you provide us (espacially Aarno) what document you are pushing and what the access.log lines of bearerbox is for those when they go out of the door to your SMSC provider. 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: Problems compiling the gateway 1.2.0 on windows nt 4
What where your input (pap control and content files )? It would be nice, too, to see your wapbox logs in full. Aarno On Friday, October 18, 2002, at 11:20 AM, Stipe Tolj wrote: Guido Meyer schrieb: Hi to all! I have a problem compiling the kannel 1.2 gateway. I want to compile it on windows nt 4/sp6 with cygwin. I tried cygwin 1.3.12. I have compiled it without problems, but if i want to test the push proxy gateway with the included test programm test_ppg.exe the wapbox crashed with the error message: 2002-10-15 09:07:13 [14] PANIC: gwlib/octstr.c:2099: seems_valid_real: Assertion `ostr != NULL' failed. (Called from gwlib/octstr.c:743:octstr_compare.) obviously you feeded wapbox's PPG with some input that caused the panic. Aarno are you aware of this?! If i tried to debug it with the gdb, the wapbox crahed in the beginning with a segmentation fault. Then i tried to compile it with the newest cygwin distribution (1.3.13 i think). If i start configure i got the message: checking whether the C compiler (gcc ) is a cross-compiler... yes checking for /usr/lib/sgml/stylesheet/dsssl/docbook/nwalsh/html/docbook.dsl... configure: error: Cannot check for file existence when cross compiling The binary distribution works fine, but i need to add some featrues to the gateway so i must compile it. Can anyone help me? Please describe us what you actually tried to send via test_ppg. 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: test_ppg - current status?
On Friday, October 11, 2002, at 05:58 PM, [EMAIL PROTECTED] wrote: Yippee! test_ppg works now, thanks very much. Now the real questions start ;-) 1. Is there a dependancy on running the test server on port 8080? I changed the ppg-port in group = ppg to 8086, started the test_http_server with -p 8086 but got the original xml parse error. When I set these back to 8080 it works again. Did I miss something? You have ppg server, kannel and http server kannel forwards push requests. Ppg is a http server, too. Ppg-port is port where ppg is listening. Test_http_server's p option defines port http server is listening. Your error message is strange, however; you should get address already in use. 2. I use resin on the same machine on port 8080. Can I configure resin to do the same job as the test_http_server? Kannel http smsc has a configuration variable send-url. Kannel relays http requests to this url. So only thing you must do is to change the send-url. 3. How do I do it for real? What I mean is, I have a web-interface to both sendsms and sendota which passes the xml docs to sendota or the payloads to sendsms. I now would like the same for wap push, sort of like http://localhost:8080/http://localhost:8080/cgi-bin/wap- push.cgi?username=foopassword=barcontent=content.xmlcontrol=control. xml (i.e. the test_ppg command line expressed as a a url). I presume you are sending SI or SL. They are normal binary SMs, only special thing is the udh; you must tell the phone the port handling the message: udh=%06%05%04%0b%84%23%f0 If you send sms yourself you should configure smsc accordingly. Thanks again for a great job. You are wellcome. Aarno
Re: Response.
On Monday, October 7, 2002, at 04:03 PM, Nigar Sultana wrote: Hello We tested, to send a post req to http server, the response got back in the wap gateway: HTTP: Status line: HTTP/1.1 200 OK WSP: Fetched http://127.0.0.1:8514 (application/vnd.wap.mms-message, charset='') 1 what it means? Gateway fetched OK mms content with default charset 2 will wap gateway create a wml file for the following response? Gateway just *passes* the files. MMS content is SMIL, gateway just passes it as it is. (It does compile wml to wmlc.) 3 Any code to be added in the wapgateway to send back the reply to mobile phone. For MMS SAR is missing, but there is a patch by Igor for that. 4 In which format will the wap gateway sends back the response to mobile. Kannel does not change mms content at all. Aarno
Re: WSP SAR and PDU types
MMS requires connection-oriented mode and is specified to use only it. Cless cannot SAR, because it does not have WTP. Another issue is that Kannel must support cless WAP fetch regardless the content size. Have you problems with simple WAP fetches ? Aarno On Thursday, October 3, 2002, at 12:43 PM, Anders Lindh wrote: image.tiff> Yep, I meant WTP. Anyway, your patch seems makes submitting / retrieval of MMS messages (from the handset) work ok when using connection oriented mode. Connectionless is still doesn't work, Kannel gives an "unsupported PDU type -1" error. Any clues to why this this is happening? Will these patches make it into the cvs, as SAR is something quite many seem to be missing...
Re: test_ppg - current status?
My bad. Will correct it soon. Aarno On Monday, September 30, 2002, at 09:10 PM, [EMAIL PROTECTED] wrote: Hi, I've just installed from cvs today and ran my usual test_ppg test set. Previously this failed with this test_http_server log: 2002-08-29 12:20:31 [1] DEBUG: HTTP: Destroying HTTPClient area 0x100be730. 2002-08-29 12:20:31 [1] DEBUG: HTTP: Destroying HTTPClient for `127.0.0.1'. 2002-08-29 12:20:31 [2] DEBUG: HTTP: Creating HTTPClient for `127.0.0.1'. 2002-08-29 12:20:31 [1] ERROR: HTTP: Content-Length header wrong: : 1184 2002-08-29 12:20:31 [1] DEBUG: HTTP: Destroying HTTPClient area 0x100be6a0. Some work has been done since then because, with the same test set, I get what looks like a real compile from the server. Great, except test_ppg now shows: 2002-09-30 19:03:13 [2] DEBUG: HTTP: Status line: HTTP/1.1 200 Foo 2002-09-30 19:03:13 [1] DEBUG: TEST_PPG: push 0 done: reply from, http://localh ost:8080/cgi-bin/wap-push.cgi?username=foopassword=bar Entity: line 1: error: Start tag expected, '' not found Sent. ^ 2002-09-30 19:03:13 [1] WARNING: PAP COMPILER: pap_compile: parse error in pap s ource 2002-09-30 19:03:13 [1] WARNING: TEST_PPG: receive_push_reply: cannot compile pa p message The command line is: ./test_ppg -q http://localhost:8080/cgi-bin/wap-push.cgi?username=foopassword=bar; content.xml control.xml content.xml: ?xml version=1.0? !DOCTYPE si PUBLIC -//WAPFORUM//DTD SI 1.0//EN http://www.wapforum.org/DTD/si.dtd;; si indication href=http://wap.iobox.fi;; si-id=[EMAIL PROTECTED] action=signal-medium created=1999-06-25T15:23:15Z si-expires=2002-06-30T00:00:00Z Want to test a fetch? /indication /si control.xml: ?xml version=1.0? !DOCTYPE pap PUBLIC -//WAPFORUM//DTD PAP//EN http://www.wapforum.org/DTD/pap_1.0.dtd;; pap push-message push-id=[EMAIL PROTECTED] deliver-before-timestamp=2001-09-28T06:45:00Z deliver-after-timestamp=2001-02-28T06:45:00Z progress-notes-requested=false address address-value=WAPPUSH [EMAIL PROTECTED] /address quality-of-service priority=low delivery-method=unconfirmed network-required=true network=GSM bearer-required=true bearer=SMS /quality-of-service /push-message /pap Does anyone else get this or have I missed something dumb please? ___ Freeserve AnyTime, only £13.99 per month with one month's FREE trial! For more information visit http://www.freeserve.com/time/ or call free on 0800 970 8890
Re: Wap over GPRS kannel support
Hi, On Tuesday, October 1, 2002, at 08:32 AM, Cipher Strength wrote: Do kannel supports Wap over GPRS. I am newbie to GPRS . If not is there any open source software available . Kannel does support *all* IP bearers. Does your operator force you their own wap gateway, is another matter. Aarno
Re: Set up.
On Tuesday, October 1, 2002, at 09:29 AM, Nigar Sultana wrote: Hello All i want to test the kannel wap gateway using the actual mobile phone. so i was just going thro' few documents which i had downloaded from the Net. while going thro' i came across a basic doubt: 1 The WAP gateway recieves data from CSD. What is actually CSD. please guide me. Never mind, it is better start using with a sendsms service (or with a phone as a virtual smsc). 2 Can we run the SMS-C using HTTP interface. if so how can we. Then you must of course connect to so url of some sms service provider. I attach an example file for that. See group = smsc. Aarno
Re: help: how to improve the performatce of concurrence
Is the limit due to the cpu usage (what top tells you) ? Of course you can use many ppgs and one bearerbox, but this is another story. Aarno On Thursday, September 26, 2002, at 08:59 AM, Guanghua Hou wrote: Dear Sir, The concurrent service is very limited. Why? How to solve? The environment is: Sloaris8, Kannel1.2.0. Here only PPG function is used. In PI, the push-response delay maximum time is 1 second. Only less than 20 cuncurrent PI users can be provided. Best Regards, Guanghua Hou
Re: MMS-WSP GET Request??
Hi, On Wednesday, September 25, 2002, at 07:22 AM, amitsehgal wrote: Hi All, I sent a m-notification.ind using this pdu on Nokia 7650 in connection oriented mode (Permanent). udh=%06%05%04%0b%84%23%f0 UDH is OK. text=%0f%06%03%be%af%84% WSP PDU is OK, too. 8c%82% Message-Type, ok 98%39%39%37%35%40%66%6c%79%65%72%6f%6e%65%2e%63%6f%6d%00% Transaction-Id, ok 8d%90% MMS-Version, ok. 8a%80% Message-Class, OK. 8e%01%64% Content-Length, OK 88%06%80%04%43%c5%46% Expiry: length is 4, but you have only three bytes. You probably have one byte missing here (or have typo in this mail). Token for Content-Location is 83. 8f%MY URI%00 Did you put literal "My URI" here ? This should normally browsable content location. (You can test it with any browser.) In response the phone originated a data call but the wapbox is crashing after some time. Is the pdu for m-notification.ind correct? Of course wapbox should not crash with wrong input, so this is a bug. Thanks for report- ing it. I caught the wdp packet in bearerbox, but it contains no URI info, is it a WSP/HTTP get request (as per WAP-206-MMSCTR-20010612-a Section 6-Fig 4 (pg 12(33)) ??? Hm. Get request should certainly contain URI, so there must some problems here. Aarno
Re: Packing User Agent Header.
On Saturday, September 21, 2002, at 04:02 PM, Nigar Sultana wrote:
Hello All
i want to have few clarification regarding the kannel wap gateway.
Listing out them:
1#define PDU(name, docstring, fields, is_valid) struct name { fields
} name;
what does this declaration means. we were not able to understand it.
This defines the structure itself. When called with PDU(something) you
get after the
expansion:
struct something {
fields
} something;
Then (conceptually) fields is expanded.
It may help to use gcc -E (or whatever option indicates precompiling
only in your
compiler).
2In the Get request header portion we have added the User Agent Name
and Value,
The User-agent:0x29
The Value can be either Nokia or Ericsson
Wap box is throwing an error: Error parsing application-header what
might be the problem.
This is because value should be a text string. Grab User-Agent headers
your phone is
sending or try using any text string as a value.
Aarno
Re: Get PDU
On Wednesday, September 18, 2002, at 11:54 AM, Nigar Sultana wrote:
I downloaded the source code from the Kannel site.
I have some doubt regarding the code for the test.
In the /test/fakewap.c , the WSP_Get PDU is declared as
WSP_Get[ ] = { 0x0E , 0x00 , 0x00 , 0x02 , 0x40 }
The last byte represents the encoded value for the GET
Method. The fakewap.c is a test program, which is working
in the connection oriented mode.
Fakewap checks only method, because this is only thing common
with *all* pdus.
According to WSP 230 document , GET PDU shoud start
with binary value for GET and since this is connection oriented
mode of data transfer, there is no Transaction-ID
What are the values before 0x40
i.e( 0x0E , 0x00 , 0x00 , 0x02 )
This is wtp invoke pdu.
Aarno
Re: m-notification-ind again
Is the version indeed 2.0 or is this just a typo ? (Version should of course be 1.0.) On Wednesday, September 4, 2002, at 10:04 AM, David Chkhartishvili wrote: Hi, Still trying to send m-notification-ing to SonyErcisson T68i using SMPP. It seems like evrything goes well, and phone tries to recieve message, but nothing happens. My files look like that: m-notification-ind.txt: Content-Type: application/vnd.wap.mms-message X-Mms-Message-Type: m-notification-ind X-Mms-Transaction-Id: 125 X-Mms-Version: 2.0 X-Mms-Message-Class: Personal X-Mms-Message-Size: 500 X-Mms-Expiry: 256; type=relative X-Mms-Content-Location: http://localhost/mms.txt X-WAP-Application-Id: x-wap-application:mms.ua pap.txt: ?xml version=1.0? !DOCTYPE pap PUBLIC -//WAPFORUM//DTD PAP//EN http://www.wapforum.org/DTD/pap_1.0.dtd; pap push-message push-id=[EMAIL PROTECTED] progress-notes-requested=false address address-value=[EMAIL PROTECTED] /address quality-of-service priority=low delivery-method=unconfirmed network-required=true network=gsm bearer-required=true bearer=sms /quality-of-service /push-message /pap Please correct me if I'm missing something in my files. -- David Chkhartishvili Tel: 995 99 182418
Re: Help: memory leak of kannel1.2.0
I commit today ppg related bugfixes. Maybe you can test it, and check is leak still present ? A On Wednesday, August 28, 2002, at 08:55 AM, Guanghua Hou wrote: Dear sir, When I test PPG (kannel1.2.0) using 'test_ppg' tools, I find that memory leak is serious. Would you pls tell me how to solve it? or When will you overcome it? Best Regards, Guanghua Hou UTStarCom Beijing RD
Re: WAP Push to T68
Hi, I do not have the phone, so I cannot test it. But there is a thread about some phones demanding a specific dcs (more than binary flag). can you check this ? If this works with other phones, I can patch wapbox accordingly. A On Monday, August 26, 2002, at 02:21 PM, Stephane Pointu wrote: Hi All, I'm trying to send a Wap Push to a mobile. It gets sent but never gets displayed o n the mobile. I have a file named si.txt containing: ?xml version=1.0? !DOCTYPE si PUBLIC -//WAPFORUM//DTD SI 1.0//EN http://www.wapforum.org/DTD/si.dtd; si indication action=signal-high href=http://wap.tf1.fr/; created=2002-08-19T12:26:33Z si-expires=2002-09-21T12:26:33Z TF1 /indication /si and another one named pap.txt containing: ?xml version=1.0? !DOCTYPE pap PUBLIC -//WAPFORUM//DTD PAP//EN http://www.wapforum.org/DTD/pap_1.0.dtd; pap push-message push-id=0001 deliver-before-timestamp=2005-10-31T06:45:00Z deliver-after-timestamp=2001-02-28T06:45:00Z progress-notes-requested=false address address- value=[EMAIL PROTECTED] /address /push-message /pap The command i issue to the ppg is: ./test_ppg -q http://localhost:8080/cgi-bin/wap-push.cgi?username=xxx''password=xxx si.txt pap.txt I can say that it gets sent because in the bearerbox logs i see: 2002-08-26 13:08:10 [5] DEBUG: AT2[nokia]: international starting with + (+336) 2002-08-26 13:08:10 [5] DEBUG: AT2[nokia]: TP-Validity-Period: 24.0 hours 2002-08-26 13:08:10 [5] DEBUG: AT2[nokia]: -- AT+CMGS=110^M 2002-08-26 13:08:10 [5] DEBUG: AT2[nokia]: -- 2002-08-26 13:08:10 [5] DEBUG: AT2[nokia]: send command status: 1 2002-08-26 13:08:10 [5] DEBUG: AT2[nokia]: -- 0051000B913366567902F60004A7600605040B8423F625AE966B65726265726F732E7075 72706C656C6162732E636F6D3A3830383000AF808DB1B48002056A0045C6080C037761702E74 66312E66722F000AC3072002081912263310C307200209211226330103544631000101 2002-08-26 13:08:10 [5] DEBUG: AT2[nokia]: -- ^Z 2002-08-26 13:08:16 [5] DEBUG: AT2[nokia]: -- 2002-08-26 13:08:16 [5] DEBUG: AT2[nokia]: -- +CMGS: 65 2002-08-26 13:08:16 [5] DEBUG: AT2[nokia]: -- OK 2002-08-26 13:08:16 [5] DEBUG: AT2[nokia]: send command status: 0 I imagine that it is received by the mobile but not recognised. Am i missing something? Thanks, Stephane.
Re: creating an smsc directory
Harrie Hazewinkel kirjoittaa keskiviikkona, 7. elokuuta 2002, kello 18:22: --On Wednesday, August 7, 2002 6:09 PM +0300 Oded Arbel odeda@m- wise.com wrote: -Original Message- From: Stipe Tolj [mailto:[EMAIL PROTECTED]] Harrie Hazewinkel wrote: Hi, I would like to ask if people would object if I would move the files into a new directory gw/smsc/ This would clean up the 'gw' directory a bit and group the sms center modules What about smpp_pdu.* modules ? These are part of smpp implementation. A
Re: Question on posting WAP209 binary data from a Nokia 7650
[EMAIL PROTECTED] kirjoittaa torstaina, 1. elokuuta 2002, kello 18:25: Good Day, I have started using your WAP Server with our MMS Relay / Server prototype a few days ago. I am testing with both a Nokia 9210 and a 7650. The 9210 works fine, but I encountered problems with the 7650, as described below. Sending small text messages works fine, but we encounter problems when we try to send larger image and / or sound attachments with the 7650. The content seems to arrive at the MMS Server / Relay truncated. The WAP Server never posts more than 1261 bytes to the MMS Server prototype. Problem is that Kannel misses WTP SAR (reassembly, more properly). But I start coding it today, so stay tuned ! Aarno
Re: MMS PDU
Maria Turk kirjoittaa keskiviikkona, 31. heinäkuuta 2002, kello 14:19:Hi, Does anyone have an MMS PDU and UDH for mms notification that they know works and have tested it.. I want to test the MMS notification sent over SMS.. test/test_http http://localhost:13013/cgi- bin/sendsms?username=*''password=*'' to=*''udh=%06%05%04%0b%84%23%f0'' text=%0f%06%03%be%af%84%8c%82%98%39%39%39%35%40%66%6c%79%65%72%6f%6e%65%2e%63%6f%6d%00 %8d%90%8a%80%8e%01%64%88%06%80%04%3d%64%8d%80% 83%YourURI%00 A
Re: PDU with unknown type for MMS
Vjacheslav Chekushin kirjoittaa maanantaina, 29. heinäkuuta 2002, kello 15:46:Hi. Did anybody try to send multimedia message from Nokia 7650? I am trying ;) I can't send message because: 1) In permanet mode (connection oriented) it require SAR. 2) In temporary mode (conection less) WAP gw doesn't undestand request: 2002-07-29 15:02:13 [2] WARNING: WSP PDU with unknown type -1 MMS requires connection oriented mode and WTP SAR (at least WAP gateway must implement it), so it not a surprise that connectionless mode does not work. (The warning this time means that connectionless port got a connection- oriented pdu.) And this 'unknown' request is: 00 50 8b ad 5a db 00 30 f2 c9 86 78 08 00 45 00 .P.╜ZЫ.0 тЙ.x..E. 0010 00 67 00 01 00 00 f9 11 84 f7 d4 5d 61 21 0a 0a .gщ. .чФ]a!.. 0020 fd 04 3e 88 23 f0 00 53 81 74 0a 7e 89 12 01 10 э.>.#р.S .t.~ 0030 13 30 04 80 86 a0 00 04 81 92 a7 60 02 82 00 02 .0... .. ..╖` 0040 83 05 02 84 01 80 80 83 99 81 ea a9 4e 6f 6b 69 ..к©Noki 0050 61 37 36 35 30 2f 31 2e 30 20 53 79 6d 62 69 61 a7650/1. 0 Symbia It uses PDU type '7e' as I undestand? No, there is no such pdu. (SonyEricsson T68/R201A sends MM without problem) This is interesting. It seems that Kannel lacks 'only' WTP SAR. I start working on it later this week. I trust you like to test the code. A
Re: MMS
Rubén Mellado Muñoz kirjoittaa tiistaina, 30. heinäkuuta 2002, kello 15:53:Kannel can support the download of smil files (MMS message)? It should. Kannel simply passes contents it does not translate unchanged. Aarnoo
Re: MMS problems
Charles Burgoyne kirjoittaa tiistaina, 23. heinäkuuta 2002, kello 19:34:Thanks to Stripe, Enzo and Aarno for replies so far, but I am still out of luck. I have decided to try and attack this one from another angle as I was getting nowhere fast with test_ppg. What I was wonder was if anybody had successfully used the pdu: Text part: 0f 06 0d be 96 7f 00 a9 7f 00 af 84 8d c1 b4 80 3f 3f 3f 39 39 39 39 40 66 6c 79 65 72 6f 6e 65 2e 63 6f 6d 00 3f 90 3f 3f 3f 01 64 3f 06 3f 04 3d 2b 2f 4a 3f 68 74 74 70 3a 2f 2f 77 77 77 2e 66 6c 79 65 72 6f 6e 65 2e 63 6f 6d 2f 00 3f be udh: 06 05 04 0b 84 23 f0 From: http://www.mail-archive.com/devel@kannel.3glab.org/msg04209.html I tried sending that to a T68i using the sendsms interface, and still no MMS shows up on the phone. When the phone gets a notification, it starts the fetch. To get content, you must implement other MMSC features. I was also wondering if the content type is set correctly, it starts off as 'bc' at the top of the message but becomes 'be' towarsd the end. Be is rigth. You must set Expiry to some future date. A
Re: logging in Kannel
From: Harrie Hazewinkel [EMAIL PROTECTED] To: dev-kannel [EMAIL PROTECTED] Subject: logging in Kannel Date: Tue, 23 Jul 2002 20:06:05 +0200 HI, In order to make things more modular I have looked into the way logging is handled in Kannel. To my horrible discovery there are two kinds of logging in gwlib namely, access_log.[c|h] and log.[c|h]. I think these are meant to be roughly speaking billing log and debug log. Accesslog is supposed to be a more simple API/function as the log version. I also noticed accesslog is not even used in the wap portion for instance. So first question is: Why is only in smsbox and bearerbox the accesslog used and not in the wap portion?? No one interested in the accesslog there?? Or are people trying to get the access log part out of a generic logfile containing also many (potentially) debug logs. This is a good question. Is someone using wapbox logs for billing ? second question: Would it not be easier to provide to the alog function only the Msg structure (and maybe an extra note) where the alog function determines the output format?? Now a 'const chat*fmt,' is given. OK, this looses flexibility, but it can unify all the formats going into the accesslog. But a more common API would allow for multiple logpaths when this layered. Meaning firs the common logfunction is called in there depending on the module a different logfunction. Logging formats for billing are usually *very* strict. Someone suggested using CDR . One way to do this is indeed to let alog to do all formatting. Only input would then be type of format used. A _ Send and receive Hotmail on your mobile device: http://mobile.msn.com
Re: MMS problems
Charles Burgoyne kirjoittaa maanantaina, 22. heinäkuuta 2002, kello 19:43:Hi, If any kind person out there could put me out of my misery then I would be most grateful (I'm probably being an idiot here). I have setup kannel to perform as a WAP gateway as well as a SMS gateway. PAP works fine as I have been able to send both si, as well as sl documents. I am now trying to send a MMS (just the header) to a phone. This is where I'm running in to problems. Now I know kannel does not fully support MMS, however from reading the devel list it appears people have had success at sending MMS Notification messages. I am currently using: kannel 1.2.0 libxml 2.4.23 Now I have tried to use test_ppg to send a text version of the MMS header (below): Content-Type: application/vnd.wap.message X-MMS-Message-Type: m-notification-ind X-MMS-Transaction-Id: 125 X-MMS-Version: 1.0 X-MMS-Message-Class: personal X-MMS-Message-Size: 100 X-MMS-Expiry: 256; type=relative X-MMS-Content-Location: http://tribe.hn.org/test.php3 Subject: MMS message However when that failed, I assumed that test_ppg does not support the encoding of MMS messages, is that correct? Yes. MMSC does tokenization of MMS headers. After that I swiped the raw message block from: http://www.mail-archive.com/devel@kannel.3glab.org/msg04208.html Which is: 84bc 8c82 9831323500 8d90 8a80 8e0164 880481020100 83yout URI00 Absolute expiry time, set in future, worked for (when I send a binary SM to the phone). Kannel should support this, too. and have tried to send that to a phone with no success either. I have also tried playing with the content and application settings on test_ppg to no avail. If anybody could help and tell me what is wrong, possibly with correct document and command line options that I can throw at test_ppg I would be eternally grateful, thanks in advance. HTTP headers Content-Type and X-WAP-Application-Id are indeed required here. A
Re: MMS problems
Charles Burgoyne kirjoittaa tiistaina, 23. heinäkuuta 2002, kello 13:06:Thanks to everyone who has replied so far! Just to clarify some points. The files that I'm using are: ---pap.txt--- ?xml version=1.0? !DOCTYPE pap PUBLIC -//WAPFORUM//DTD PAP 1.0//EN http://www.wapforum.org/DTD/pap_1.0.dtd; pap push-message push-id=[EMAIL PROTECTED] source-reference=ents24 address address- value=[EMAIL PROTECTED] / quality-of-service priority=high delivery-method=unconfirmed/ /push-message /pap ---pap.txt--- ---mms.txt--- X-MMS-Message-Type: m-notification-ind X-MMS-Transaction-ID: 125 X-MMS-MMS-Version: 1.0 X-MMS-Message-Class: personal X-MMS-Message-Size: 100 X-MMS-Expiry: 256; type=relative X-MMS-Content-Location: http://styx.ents24.com/test.php3 Subject: hello ---mms.txt--- Executing test_ppg thus: ./test_ppg http://localhost:13007/wappush?username=password= -a mms -c mms mms.txt pap.txt I will try this myself in a few days. I am going to use Kannel for sending notifica- tions. The pap file is one that I have successfully used to send si/sl documents to a phone. In mms.txt I have used not only X-MMS-MMS-Version, but also X-MMS-Version (there seems to be some confusion about that). Wait. The text version is only for human readers. You should not send it to the phone. The MMS content to be send to the phone is tokenized. If I try to send this message, test_ppg comes back with a bad message response code=2000 which seems to be related to the Content-Location line. Can you send wapbox logs. I would like to know what ppg believes it is doing. Content-Type: application/vnd.wap.messsage This should be application/vnd.wap.mms-message. (Use this as a content type for push multipart content part.) For the MMS type. This seems to work, I get another 1001 response code, but still no MMS notification at the phone. Any ideas? In addition, it is probably better to use absolute expiry time. Problem with relative is that to which it is relative. A
Re: MMS problems
Stipe Tolj kirjoittaa tiistaina, 23. heinäkuuta 2002, kello 18:49:However when that failed, I assumed that test_ppg does not support the encoding of MMS messages, is that correct? Yes. MMSC does tokenization of MMS headers. So Aarno means it's not in the scope of test_ppg to tokenize your MMS headers, you have to pass it on your own. Yes. Test_ppg reads push contents (of any type) from a file and passes it unmodified. A
Re: wapbox crash
Peter Löfman kirjoittaa maanantaina, 22. heinäkuuta 2002, kello 09:16:Hi, I have a problem that the wapbox keeps crashing frequently. I'm not so sure what the error messages in the log means, can anyone help me? Below is a printout from wapbox.log: 2002-07-21 12:38:57 [2] WARNING: WSP PDU with unknown type -1 2002-07-21 12:38:59 [2] WARNING: WSP PDU with unknown type -1 2002-07-21 12:39:02 [2] WARNING: WSP PDU with unknown type -1 2002-07-21 12:39:08 [2] WARNING: WSP PDU with unknown type -1 2002-07-21 12:39:20 [2] WARNING: WSP PDU with unknown type -1 Wapbox is getting a wrong type of PDU, or at least it thinks so. 2002-07-21 12:42:57 [1] ERROR: WSP: Cannot find session machine for event. 2002-07-21 12:42:57 [6] ERROR: WTP_RESP: resp_machine_find_or_create: WSP primitive to a wrong WTP machine WSP get an event, but there is no established session (WTP error message means same) 2002-07-21 12:42:58 [6] INFO: WTP_RESP: resp_machine_find_or_create: abort received, yet having no machine This is OK: both peers abort, wapbox doing it first. 2002-07-21 12:44:24 [1] ERROR: WSP: Cannot find session machine for event. 2002-07-21 12:44:24 [6] ERROR: WTP_RESP: resp_machine_find_or_create: WSP primitive to a wrong WTP machine 2002-07-21 12:44:24 [6] INFO: WTP_TID: tid out of the window 2002-07-21 12:44:24 [6] INFO: WTP_TID: tid out of the window This it not problem either (wapbox got stange tid, and will verify it) Do you use force-sar ? One explanation for "unkown PDUs" will be that this is a segment, PDU being one of segmentation PDUs A
Re: OTA Truncation?
Eric Carlson kirjoittaa perjantaina, 19. heinäkuuta 2002, kello 23:10:Perhaps you can correct the segmentation ? This should not be too much work, the code is already available, you must just call it. I hav this problem too.Anyone planning this fix? Is 1.2.1 rearing its head here ? This is quite bad bug; it is certainly reasonable to send bookmark with settings. I will do the bug correction, if anybody else does not (I certainly hope that somebody does), but not very soon. Aarno
Re: Sending MMS with kannel ...
Enzo dell'Aquila kirjoittaa torstaina, 18. heinäkuuta 2002, kello 17:44:Hi, I've just subscribed this mailing-list, so, what I have to ask could be in previous posts. I want to send MMS from Kannel to compliant MMS phones. I have a look to MMS specifications, so it seems there are 2 ways: a) M-send.request: sending MMS to MMSC Relay/server b) M-notification.ind: sending directly MMS to phone What's the best way? Is b) way correct? B) is OK. Case a) I suppose I must have a link to operator MMSC ... how can I use/configure kannel to communicate with operator MMSC ? Is this way for mobile users only or can I use kannel to communicate with operator MMSC? MMSCs does the communicating to the other MMSCs. But protocols are SMTP and IMAP. But does operators let you in, is another matter. Case b) Are there any interoperability problems? No, because all phones must understand notification, otherwise they do not fetch the message from the center. I have found an example here: http://www.mail-archive.com/users@kannel.3glab.org/msg00972.html This should work (have tested it). A
Re: OTA Truncation?
Aarno Syvänen kirjoittaa perjantaina, 19. heinäkuuta 2002, kello 08:06:[EMAIL PROTECTED] kirjoittaa torstaina, 18. heinäkuuta 2002, kello 17:20:Hi - I posted a message here last week regarding bad OTA. I now have more info. Using the CVS from yesterday it looks like the PDU is getting truncated. Can anyone confirm this please or see what I'm doing wrong? 2002-07-18 14:48:29 [3] DEBUG: message length 158, sending 1 messages 2002-07-18 14:48:29 [3] DEBUG: Status: 202 Answer: Sent. Sending 158 binary octets in one message is certainly wrong, the message should be segmented. This looks to me like the message is just cut off after the Wap string!!! If all octets does not fit in one message, and there are no segmentation, leftover octets are cut. System is Cygwin, sending with Ericsson R320 as SMSC using AT2, reciever is T68i. Anyone please!!! (I'm quite new to this so please don't assume I can see the obvious ;-)) Perhaps you can correct the segmentation ? This should not be too much work, the code is already available, you must just call it. A
Re: how to use the MACROs?
ww kirjoittaa torstaina, 18. heinäkuuta 2002, kello 04:29:i am puzzled by the macros used in the source code of kannel
just like the difinition of the MSG and the State-machine
here is the source code in the wtls_state-decl.h
ROW(CREATING,
SEC_Exception_Req,
1,
{
info(0,"begin a new 12 machine---");
/* Send off a T_Unitdata_Req containing an exception as specified */
send_alert(event->u.SEC_Exception_Req.alert_level,
event->u.SEC_Exception_Req.alert_desc, wtls_machine);
},
CREATING)
This is directly from state table:
ROW(state,
event,
condition,
action,
state after action)
Condition 1 means always, {} means no action. Action is a normal C block.
the source code in the wtls.c
if(event->type == T_Unitdata_Ind)
{
if( wtls_machine->encrypted )
{
info(0, "lyl: start pdu list ");
wtls_decrypt_pdu_list(wtls_machine, event->u.T_Unitdata_Ind.pdu_list);
}
info(0, "lyl: end pdu list ");
du_list);
}
#define STATE_NAME(state)
#define ROW(wtls_state, event_type, condition, action, next_state) \
if (wtls_machine->state == wtls_state \
event->type == event_type \
(condition)) { \
action \
wtls_machine->state = next_state; \
debug("wap.wtls", 0, "WTLS %ld: New state %s", wtls_machine->mid
, #next_state); \
} else
#include "wtls_state-decl.h"
{
error(0, "WTLS: handle_event: unhandled event!");
debug("wap.wtls",0, "lyl: event->type = %d", event->type);
wap_event_destroy(event);
return;
}
Do not touch code in wtls.c, edit wtls_state-decl,h instead. Either change
code in action part in normal way or add a new row to the state table (for
unhandled events).
Aarno
Re: m-notification-ind (cont.)
Anders Lindh kirjoittaa maanantaina, 8. heinäkuuta 2002, kello 13:52:Hi, I've been struggling with the PPG and m-notification-ind messages, but haven't been able to get the handset to react to the indication. There's probably something I'm missing, so I'd appreciate if someone could lend their eyes and check through the used material. The notification is received by the handset, but apparently silently ignored. No fetch is occuring at http://www.flyerone.com/. I submit this to the PPG: Headers: content-type: multipart/related; boundary=wFwKoCsDInFRxqmburDFMeqxu; type=application/xml x-wap-application-id: x-wap-application:mms.ui This should be x-wap-application:mms.ua connection: keep-alive content-length: 656 content: 2002-07-08 13:28:34 [14] DEBUG: data: 0d 0a 2d 2d 4b 62 66 66 ..--Kbff 2002-07-08 13:28:34 [14] DEBUG: data: 51 73 46 51 69 5a 4f 6f QsFQiZOo 2002-07-08 13:28:34 [14] DEBUG: data: 66 6c 56 43 57 75 4a 46 flVCWuJF 2002-07-08 13:28:34 [14] DEBUG: data: 65 63 46 76 52 0d 0a 43 ecFvR..C 2002-07-08 13:28:34 [14] DEBUG: data: 6f 6e 74 65 6e 74 2d 74 ontent-t 2002-07-08 13:28:34 [14] DEBUG: data: 79 70 65 3a 20 61 70 70 ype: app 2002-07-08 13:28:34 [14] DEBUG: data: 6c 69 63 61 74 69 6f 6e lication 2002-07-08 13:28:34 [14] DEBUG: data: 2f 78 6d 6c 0d 0a 3c 3f /xml..? 2002-07-08 13:28:34 [14] DEBUG: data: 78 6d 6c 20 76 65 72 73 xml vers 2002-07-08 13:28:34 [14] DEBUG: data: 69 6f 6e 3d 22 31 2e 30 ion=1.0 2002-07-08 13:28:34 [14] DEBUG: data: 22 20 65 6e 63 6f 64 69 encodi 2002-07-08 13:28:34 [14] DEBUG: data: 6e 67 3d 22 49 53 4f 2d ng=ISO- 2002-07-08 13:28:34 [14] DEBUG: data: 38 38 35 39 2d 31 22 3f 8859-1? 2002-07-08 13:28:34 [14] DEBUG: data: 3e 0d 0a 3c 70 61 70 3e ..pap 2002-07-08 13:28:34 [14] DEBUG: data: 3c 70 75 73 68 2d 6d 65 push-me 2002-07-08 13:28:34 [14] DEBUG: data: 73 73 61 67 65 20 70 75 ssage pu 2002-07-08 13:28:34 [14] DEBUG: data: 73 68 2d 69 64 3d 22 31 sh-id=1 2002-07-08 13:28:34 [14] DEBUG: data: 32 33 34 40 66 6c 79 65 234@flye 2002-07-08 13:28:34 [14] DEBUG: data: 72 6f 6e 65 2e 63 6f 6d rone.com 2002-07-08 13:28:34 [14] DEBUG: data: 22 20 64 65 6c 69 76 65 delive 2002-07-08 13:28:34 [14] DEBUG: data: 72 2d 62 65 66 6f 72 65 r-before 2002-07-08 13:28:34 [14] DEBUG: data: 2d 74 69 6d 65 73 74 61 -timesta 2002-07-08 13:28:34 [14] DEBUG: data: 6d 70 3d 22 32 30 30 32 mp=2002 2002-07-08 13:28:34 [14] DEBUG: data: 2d 30 37 2d 30 38 54 31 -07-08T1 2002-07-08 13:28:34 [14] DEBUG: data: 30 3a 33 33 3a 33 32 5a 0:33:32Z 2002-07-08 13:28:34 [14] DEBUG: data: 22 20 64 65 6c 69 76 65 delive 2002-07-08 13:28:34 [14] DEBUG: data: 72 2d 61 66 74 65 72 2d r-after- 2002-07-08 13:28:34 [14] DEBUG: data: 74 69 6d 65 73 74 61 6d timestam 2002-07-08 13:28:34 [14] DEBUG: data: 70 3d 22 32 30 30 32 2d p=2002- 2002-07-08 13:28:34 [14] DEBUG: data: 30 37 2d 30 38 54 31 30 07-08T10 2002-07-08 13:28:34 [14] DEBUG: data: 3a 32 38 3a 33 32 5a 22 :28:32Z 2002-07-08 13:28:34 [14] DEBUG: data: 20 73 6f 75 72 63 65 2d source- 2002-07-08 13:28:34 [14] DEBUG: data: 72 65 66 65 72 65 6e 63 referenc 2002-07-08 13:28:34 [14] DEBUG: data: 65 3d 22 46 6c 79 65 72 e=Flyer 2002-07-08 13:28:34 [14] DEBUG: data: 4f 6e 65 20 4c 74 64 22 One Ltd 2002-07-08 13:28:34 [14] DEBUG: data: 3e 3c 61 64 64 72 65 73 addres 2002-07-08 13:28:34 [14] DEBUG: data: 73 20 61 64 64 72 65 73 s addres 2002-07-08 13:28:34 [14] DEBUG: data: 73 2d 76 61 6c 75 65 3d s-value= 2002-07-08 13:28:34 [14] DEBUG: data: 22 57 41 50 50 55 53 48 WAPPUSH 2002-07-08 13:28:34 [14] DEBUG: data: 3d 2b 33 35 38 34 30 35 =+358405 2002-07-08 13:28:34 [14] DEBUG: data: 31 33 34 32 36 35 2f 54 134265/T 2002-07-08 13:28:34 [14] DEBUG: data: 59 50 45 3d 50 4c 4d 4e YPE=PLMN 2002-07-08 13:28:34 [14] DEBUG: data: 40 66 6c 79 65 72 6f 6e @flyeron 2002-07-08 13:28:34 [14] DEBUG: data: 65 2e 63 6f 6d 22 20 2f e.com / 2002-07-08 13:28:34 [14] DEBUG: data: 3e 3c 71 75 61 6c 69 74 qualit 2002-07-08 13:28:34 [14] DEBUG: data: 79 2d 6f 66 2d 73 65 72 y-of-ser 2002-07-08 13:28:34 [14] DEBUG: data: 76 69 63 65 20 70 72 69 vice pri 2002-07-08 13:28:34 [14] DEBUG: data: 6f 72 69 74 79 3d 22 6d ority=m 2002-07-08 13:28:34 [14] DEBUG: data: 65 64 69 75 6d 22 20 2f edium / 2002-07-08 13:28:34 [14] DEBUG: data: 3e 3c 2f 70 75 73 68 2d /push- 2002-07-08 13:28:34 [14] DEBUG: data: 6d 65 73 73 61 67 65 3e message 2002-07-08 13:28:34 [14] DEBUG: data: 3c 2f 70 61 70 3e 0d 0a /pap.. 2002-07-08 13:28:34 [14] DEBUG: data: 0d 0a 2d 2d 4b 62 66 66 ..--Kbff 2002-07-08 13:28:34 [14] DEBUG: data: 51 73 46 51 69 5a 4f 6f QsFQiZOo 2002-07-08 13:28:34 [14] DEBUG: data: 66 6c 56 43 57 75 4a 46 flVCWuJF 2002-07-08 13:28:34 [14] DEBUG: data: 65 63 46 76 52 0d 0a 43 ecFvR..C 2002-07-08 13:28:34 [14] DEBUG: data: 6f 6e 74 65 6e
Re: smsbox terminating
Harrie Hazewinkel kirjoittaa torstaina, 4. heinäkuuta 2002, kello 01:45: I would be nice to see bearerbox log. After all, there was a message bearerbox closing the connection. Certainly wapbox goes down in this case. --On Wednesday, July 3, 2002 8:05 PM +0200 Stipe Tolj [EMAIL PROTECTED] wrote: If I sent the process a SIGTERM (kill -TERM) the smsbox process just gives back 'terminated' no additional info of shutting down. If I give it a SIGINT it nicely says it recieved it and terminates with info what it is closing all. Harrie, you're right of course. Of course?? Would this mean I am perfect and thus nobody?? ;-)) Serious, for the problem on Linux I am not much of a help. I don't have such a system, but just noticed it while playing yesterday on FreeBSD. Harrie Internet Management Consulting mailto:[EMAIL PROTECTED]http ://www.mod-snmp.com/
Re: m-notification-ind
Anders Lindh kirjoittaa keskiviikkona, 3. heinäkuuta 2002, kello 16:48:Hi si and sl work fine, but can I send a m-notification-ind message to the handset? If so, what is the correct syntax of the content file, and the test_ppg command line?. MMS content should be fully tokenized MMS document. See Wapforum spec WAP-209- MMSEncapsulation-20020105-a.pdf. Aarno
Re: CIMD2 - DLR not crashing!
Oded Arbel kirjoittaa torstaina, 27. kesäkuuta 2002, kello 21:45:It looks like the driver's fault - the timestamp value for dlr_add is not being generated because the relevant line cimd2_request is commented out : snip next_reply: /*reply = cimd2_get_packet(smsc,ts);*/ reply = cimd2_get_packet(smsc, NULL); if (!reply) goto io_error; /snip I haven't tested it, but the way I see it the first cimd2_get_packet() line should be uncommented and the second line removed Yes, but then we will a dynamic memory leak (for timestamp area in every message). Aarno -Original Message- From: Stefan Cars [mailto:[EMAIL PROTECTED]] Sent: Thursday, June 27, 2002 4:44 PM To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: CIMD2 - DLR not crashing! Hi! I have checked the latest cvs and it is not crashing any more when receiving DLRs on CIMD2. Althogh the DLR is still not working (log below): Maybe it is not a showstopper, but it is indeed something worth looking at. Maybe Andreas could help us out here, I can assist with access to CIMD2 SMSC. /S 2002-06-27 15:40:57 [1] DEBUG: Dumping 0 messages and 0 acks to store 2002-06-27 15:41:03 [6] DEBUG: Looking for DLR smsc=CIMD2:217.174.67.135:9972:globalwire, ts=020627154023, dst=46708443600, type=1 2002-06-27 15:41:03 [6] DEBUG: DLR not found! - Stefan Cars CTO Globalwire Communications Phone: +46 18 10 79 50 Mobile(UK): +44 788 061 36 69 Mobile(SE): +46 708 44 36 00
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: EMI: Serious Problem PANIC: Too many concurrent allocations
Bruno David Rodrigues kirjoittaa keskiviikkona, 12. kesäkuuta 2002, kello 12:22: Yes, it indeed seems that this code can use some rewriting :( Does Paul's suggestion met your big file needs (let us plan better this time). Aarno Paul Keogh kirjoittaa tiistaina, 4. kesäkuuta 2002, kello 14:51: Yes, but when this is triggered bb_smscconn_receive () logs the event and returns -1. All the SMSC drivers except HTTP ignore the return code from bb_smscconn_receive (). Therefore, the message is silently dropped from the application and the SMSC point of view. This is IMHO a bad thing and not something you could use in a production environment. I think a better solution would be to; * When possible, map the queue full event to an SMSC protocol error indicating a temporary resource shortage; otherwise fail the message with the most appropriate error code. * Introduce a flow control admin. message to tell the SMS box (and any other clients using the SMS box interface) to stop/start sending messages. The SMS box could in turn signal to the various sendsms applications that a temporary resource shortage event has occurred (HTTP 503 maybe ?) * Use high and low watermark variables instead of maximum-queue-length. This prevents thrashing around the maximum-queue-length value. A sort of SMS hysteresis curve :-). Maximum-queue-length is supposed to prevent crashing caused by too long queues. Congestion control is used to *prevent* long queues. It is, of course, something Kannel can use. Aarno I've been looking at the code and I can't find what I've been looking for :((( On May 3, as I told you, I've sent 200k messages through emi2 (30msg/sec I think). On that day I've tryed my post-xml code. As 100k per post gave me http timeout, I've send 10k at a time, 20 posts. At the end, I've lost 25% of the messages (smsbox logs vs bearerbox logs). Could it be from this code ? I did got store.lock with 30 or 40 MB. As I saw in the code, even if this code is activated, we get a DROPPED in logs, right ? I didn't care much at the time, but there's somewhere a bug looking for us.
Re: EMI: Serious Problem PANIC: Too many concurrent allocations
Paul Keogh kirjoittaa tiistaina, 4. kesäkuuta 2002, kello 14:51: Yes, but when this is triggered bb_smscconn_receive () logs the event and returns -1. All the SMSC drivers except HTTP ignore the return code from bb_smscconn_receive (). Therefore, the message is silently dropped from the application and the SMSC point of view. This is IMHO a bad thing and not something you could use in a production environment. I think a better solution would be to; * When possible, map the queue full event to an SMSC protocol error indicating a temporary resource shortage; otherwise fail the message with the most appropriate error code. * Introduce a flow control admin. message to tell the SMS box (and any other clients using the SMS box interface) to stop/start sending messages. The SMS box could in turn signal to the various sendsms applications that a temporary resource shortage event has occurred (HTTP 503 maybe ?) * Use high and low watermark variables instead of maximum-queue-length. This prevents thrashing around the maximum-queue-length value. A sort of SMS hysteresis curve :-). Maximum-queue-length is supposed to prevent crashing caused by too long queues. Congestion control is used to *prevent* long queues. It is, of course, something Kannel can use. Aarno
Re: smsbox crashed
Cipher Strength kirjoittaa tiistaina, 4. kesäkuuta 2002, kello 10:31: smsbox crashed with the followong last entry in smsbox log file. I am using Kannel develepment release on Redhat 6.2 2002-06-04 16:30:27 [1] PANIC: gwlib/http.c:1535: port_put_request: Assertion `p!= NULL' failed. what should i DO. Sending smsbox and bearerbox logs is useful ;) In addition, more data about the message causing the crash (there are unhandled NULL pointer here, and one must know first, is the assertion itself necessary) Also i want to purchase new hardware for machine. How much RAM would enough. I have decided to buy P3 Intel server board (Scsi built-in) 400 - 500 M would certainly be enough. Kannel should not let long queues happen in the first place. Aarno
Re: EMI: Serious Problem PANIC: Too many concurrent allocations
Kalle Marjola kirjoittaa maanantaina, 3. kesäkuuta 2002, kello 10:37:On Sat, 1 Jun 2002, Jari Juslin wrote: So, panic to Too many concurrent allocations can happen if a) Kannel just has so high load, that is needs huge amounts of memory or b) if Kannel leaks too much memory. Am I right? Yes. The reason a) is encountered when incoming traffic is faster than the outgoign handle (namely SMS centers) and usually results in that 'too many concurrent allocations'. This can be avoided by increasing the size of the checking malloc buffers, but if things keep going like that it will eventually panic. Moreover, store files of several megabytes is more than a problem. This entire thing should be fixed so that more priority is given to outgoing messages, i.e. just make it impossible to grow queues inside Kannel - just make the queues to build up into sockets/other programs. Of course this is far from trivial with some SMS centers. Kannel currently has configuration variable maximum-queue-length. See user- guide for details. Aarno
Re: [BUG] EMI2 crashing.
Oded Arbel kirjoittaa maanantaina, 3. kesäkuuta 2002, kello 10:04:Attached is a patch for octstr.c to make sure that even if null is submitted for an Octstr, nothing will break. Applying it is really a philosophical question : does NULL is a valid Octstr* value ? the code is confusing about it : some functions choke when fed a NULL pointer, while others return with no error (w/o doing anything useful either, but that is to be expected when you're handed a NULL pointer). Some modules use NULL Octstr for this variable has no value, and handle NULL using this semantics. For others, it is plain error. But I think they should handle NULL, too, for robustness. Aarno
Re: MMS
shaan j kirjoittaa maanantaina, 3. kesäkuuta 2002, kello 08:32:Hi List, I have following querries: 1). Can I use Kannel for testing my MMS applications ? 2). If yes, which version should I use ? Should I wait for the stable release 1.2.0 ? 3). What all is required to set up such an environment ? 4). Has anybody tested MMS applications with Kannel ? I will start (after some bug corrections) work on this. I mean, making Kannel PPG and WAP gateway able to work with MMS centers. It is nice ti have testers ;) I think 1.2.0 will happen very soon, and without MMS support (there is vote on it now). Aarno
Re: version 1.1.6 processing limits
Harrie Hazewinkel kirjoittaa perjantaina, 31. toukokuuta 2002, kello 12:36: --On Friday, May 31, 2002 9:57 AM +0200 Stipe Tolj tolj@wapme- systems.de wrote: yep, that may be. Aarno, what do you mean of this? Did you recognize anything at your benchmark testings? I understood the others were thinking of some malloc function. Those are system calls and probably locked for exclusive use in a process. Meaning the many multiple threads have to wait on each other. This is just theory, nothing I tested or so. Therefore, I used 'just a thought'. This is an idea Lars had during Wapit time. Yes, it would help, dark though then that best way to boost Kannel performance is making it do less memory allocations. If this is handled by a new memory wrapper, so that there is no need to change code outside this module, the change is even practical. Aarno
RE: version 1.1.6 processing limits
From: Harrie Hazewinkel [EMAIL PROTECTED] --On Thursday, May 30, 2002 10:14 AM +0300 Oded Arbel [EMAIL PROTECTED] Just a thought, but is the amount of system-call casuing some problems. Not knowing how much there are, but malloc is one of them. If so, maybe some memory handling needs to be added whichallocates a huge block from the system and then in user land claims pieces where needed. At the end of some cycle all is returned at once, instead of all those small bits. Kannel was once profiled, and results showed that is uses about 98% of its time doing mallocs. Memory planning would certainly be usefull. Aarno _ Send and receive Hotmail on your mobile device: http://mobile.msn.com
Re: sms format for WAP SI push
Hi, see answers between the lines Aarno - Original Message - From: Stone Zhang [EMAIL PROTECTED] To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED] Sent: Tuesday, May 21, 2002 1:38 PM Subject: sms format for WAP SI push I am stucked with the SMS format of wap SI push via SMS If this helps: you are certainly not the first one. does wdp header is necessary in the SMS Wdp header means here SMS headers (UDHs, as they are called). These are defined in WAP-259-WDP-20010614-a, appendix D. and how about wsp header? See WAP-230-WSP-20010705-a, chapters 8.2.4 and 8.4 do I need put X-Wap-Application-ID and Push-Flag in the SMS? Only Content-Type is mandatory, see WAP-251-PushMessage-20010322-a, chapter 5.2. where can I find all these specification? http://www.wapforum.org anyone can share your successful samples will be greatly appreciated! Kannel userguide contains an example binary SI document in http URL encoded format Aarno
Re: WAP Push
Hi, log files for succesfull v. unsuccessfull delivery attempt would be nice. In addition, I would like to see configuration files. Aarno - Original Message - From: Randeep Singh Bhatia [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Friday, May 17, 2002 6:09 PM Subject: FW: WAP Push Hi, We are trying to use the WAP push implemented via the Kannel PPG gateway in development version 1.1.6. We are using Hay Systems Limited (www.hsl.uk.com) for the underlying SMS messaging via SMPP 3.4. In our tests the WAP push seems to work once in a while, but most of the time the WAP push is not recieved by the phone. The SMS provider claims that they are delivering the SMS to the phone everytime and so the message must show up on the phone. Also the phone has no problem recieving SMS via other interfaces (http) from the same SMS provider. Does anyone have any clue on what might be going wrong Our settings for the SMSC in pushkannel.conf uses system-type = SMPP Thanks Randeep
Re: USSD Center
- Original Message - From: Shridhar Raju [EMAIL PROTECTED] To: Kannel Developers [EMAIL PROTECTED] Sent: Monday, May 06, 2002 12:25 PM Subject: Re: USSD Center - Original Message - From: Aarno Syvänen [EMAIL PROTECTED] To: Shridhar Raju [EMAIL PROTECTED]; Kannel Developers [EMAIL PROTECTED] Sent: Saturday, May 04, 2002 2:35 AM Subject: Re: USSD Center Hi, see answers between the lines aarno - Original Message - From: Shridhar Raju [EMAIL PROTECTED] To: Kannel Developers [EMAIL PROTECTED] Sent: Monday, May 06, 2002 8:21 AM Subject: USSD Center In my sms apllication, user has to send msg like stock infy where stock is keyword and kannel passes it to proper sms-service. But, in USSD, user has to dial some number, lets say *123# What should be my sms-service configuration. Will USSD send value 123 in user data parameter or in service code parameter. I want to make some service, how to go about it. I think you must use default sms-service, get the SM out with %a and receiver phone number with %P. Aarno
Re: Bug in wap_push_ppg.c ?
Yeah. Thanks. Aarno Paul Keogh wrote: The function send_to_pi () takes a first argument of HTTPClient *c. This is passed directly to http_send_reply (c...). If the c is NULL http_send_reply () crashes as it immediately deferences c. I don't think send_to_pi () should assume that the PI is still around and hence should check that the HTTPClient ptr is non-NULL before invoking http_send_reply (). Paul Keogh ANAM Wireless Internet Solutions http://www.anam.com +353 1 284 7555 (wired) +353 86 234 6047 (wireless) Castle Yard, Saint Patrick's Road, Dalkey, County Dublin, Ireland
Re: Question on wap_push_pap_mime.c- Extension Headers
Paul Keogh wrote: This module contains the pass_extension_headers() function, the purpose of which is to valid the structure of extension headers in the Push message. However, the function contains the line of code - if ((octstr_case_search(*body_part, octstr_imm(Content), 0)) 0) goto end; which fails completely if the message body actually contains the word 'Content'. Yep. We must parse this properly. Why is this check necessary at all - at this point the message could contain a mixture of WAP header extensions, User header extensions and non-normative Internet header extensions - so what's the point in looking for a specific keyword ? These are multipart part headers. Also, on a related note, the pass_data_headers() function looks for headers of type Content-Transfer-Encoding, Content-ID and Content-Description. These are not listed among the generic headers in 6.2.1 (WAP-145-PushMessage), so why are they expected ? I wanted parser to parse a general multipart message (which is actually a requirement). Aarno
Re: Compilation Warnings
Bruno David Simões Rodrigues wrote: bruno@laptop:~/work/gateway$ make -s wap/wsp_session.c:437: warning: `REFERER' redefined wap/wsp.h:47: warning: this is the location of the previous definition wap/wsp_session.c:490: warning: `REFERER' redefined wap/wsp_session.c:437: warning: this is the location of the previous definition bruno@laptop:~/work/gateway/wap$ grep OCTSTR wsp.h wsp_session.c wsp.h: #define OCTSTR(name) Octstr *name; wsp_session.c: #define OCTSTR(name) p-name = NULL; wsp_session.c: #define OCTSTR(name) octstr_destroy(p-name); bruno@laptop:~/work/gateway/wap$ grep REFERER wsp.h wsp_session.c wsp.h: #define REFERER(name) Octstr *name; wsp_session.c: #define REFERER(name) p-name = NULL; wsp_session.c: #define REFERER(name) octstr_destroy(p-name); I really don't understand what tha hell is this warning. OCTSTR macro (and others nearby) is defined just like REFERER and gives no warning. Could someone fix this and elucidate us what is this warning ? REFERER was not *undefined* at the end of wap/wsp_server_session_machine.def. So precompiler thougth that there was a redefinition of it. Aarno
Re: Issue with CO Push
Hi, Michael Mulcahy wrote: To support connection oriented push, Kannel appears to require the Push Initiator to specify the application identifier as push.sia. I think this is incorrect, I think Kannel should be able to accept any application identifier for connection oriented push. In connection oriented push, if there is no session established then the server, Kannel, should send a Pom-SessionRequest to the client. The SIA Content field of Pom-SessionRequest contains a list of Application Ids required for push sessions. Kannel should put the Application Id received from the Push Initiator into this list. It is just for the Pom-SessionRequest that the Push headers should have the a content type for sia and an application id for sia. Yes, you are right. Thanks. Aarno
Re: USSD Center
Hi, - Original Message - From: Shridhar Raju [EMAIL PROTECTED] To: Kannel Developers [EMAIL PROTECTED] Sent: Friday, April 26, 2002 9:21 AM Subject: USSD Center Hi, Does kannel sms gateway connect to ussd center like Nokia Artus USSD Center (CIMD). If yes, does it require any changes to be made in source. Has anybody testes it and what benefits you get with USSD connection. I I have some code for this (tested with simulator, not with real SMSC center). Can you test it with one ? I think we should not have much untested code in Kannel sources ;) apologise, if my questions are irrelevent in this list, kindly guide me to resources available in internet. This is rigth place to ask this kind of questions. Kannel, of course, will support all SMSCs.
Re: Fw: Kannel version 1.1.5-1 fault tolerance and memory leaks
Hi James, From: James Wang [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Fw: Kannel version 1.1.5-1 fault tolerance and memory leaks Date: Mon, 22 Apr 2002 12:29:26 +0100 - Original Message - From: James Wang [EMAIL PROTECTED] Dear Sir/Madam, I have the following problems and wonder if this had already been reported and if you have a fix: ++ 1). If I send an empty UDP packet to the WAP box, it does not serve any more. (I have to restart the service.) Can you report your settings with more details ? 2). Memory leaks: starting points: sizeres Wapbox: 8659K5256K Bearbox: 9552K4920K After 239,000 hits: sizeres Wapbox: 8912K5552K Bearbox: 10M 6040K Yes, bearerbox leak no hopefully fixed, thanks Aarno _ Send and receive Hotmail on your mobile device: http://mobile.msn.com
Re: Push with M20 (fix)
Paul Keogh wrote: My push test set-up is test_ppg - wapbox - bearerbox - m20t - t68 This won't work with the current wapbox.c module I had to change msg-sms.coding = DC_UCS2; to msg-sms.coding = DC_8BIT; in pack_sms_datagram() in wapbox.c This problem and fix has been reported before. What's the rationale for using DC_UCS2? Also, the relevant WAP form spec - WAP-159-WDPWCMPAdapt-19991105-a - in section 7.1.4 specifies an SMPP data coding parameter of 8-bit binary. Did not look that spec, thanks. Aarno
Re: [RFC] status for wapbox internals
Hi, Stipe Tolj wrote: we'd like to have the option to have more information about wapbox's current operational status, i.e. how many WSP machines are active and how many client IPs are connected to the wapbox. Unfortunatly we can't get that information into bearerbox's status report so easily. Now should be consider to * addopt the admin status interface to wapbox or * should be screw up communication between wapbox and bearerbox I'm personaly for option 1, because this is pretty easy and does not hurd anything inside bearerbox. I like that too. This may result into general http admin module :) Aarno
Re: smsbox panic when receiving garbadge in to field!
Hi,
you, of course, use native malloc ?
Stefan Cars wrote:
When a stupid customer of ours is trying to send via the sendsms interface
and formatting the to field wrong after a short while the smsbox panics
becuase of too many concurrent allocations. I've been trying to locate
the problem without success.
anyone ?
2002-04-23 16:14:14 [3] INFO: smsbox: Got HTTP request /cgi-bin/sendsms
from
X
2002-04-23 16:14:14 [3] INFO: sendsms used by awardit
2002-04-23 16:14:14 [3] INFO: Illegal characters in 'to' string
('46708109311,46
733278') vs '0123456789 +-'
2002-04-23 16:14:14 [3] DEBUG: Status: 400 Answer: Garbage 'to' field,
rejected
.
2002-04-23 16:14:14 [3] DEBUG: HTTP: Destroying HTTPClient area 0x8231490.
2002-04-23 16:14:14 [3] DEBUG: HTTP: Destroying HTTPClient for
`X'.
2002-04-23 16:14:15 [2] DEBUG: HTTP: Creating HTTPClient for
`X'.
2002-04-23 16:14:15 [3] INFO: smsbox: Got HTTP request /cgi-bin/sendsms
from
X
2002-04-23 16:14:15 [3] INFO: sendsms used by awardit
2002-04-23 16:14:15 [3] INFO: Illegal characters in 'to' string
('46708109311;46
733278') vs '0123456789 +-'
2002-04-23 16:14:15 [3] PANIC: Too many concurrent allocations
Re: Is libxml2 invoked whenever Kannel fetches a XML file
Hi, I am summarizing the actions once more here: 1) RENAMED hello.wml TO hello.xml FILE. BUT text/html 2) COPIED SAMPLE libxml2 (WAP-GENERATING) XML FILE TO APACHE DOCUMENTROOT STILL text/html 3) CONFIGURED XML ENGINE COCOON WITH APACHE. IN SAMPLE COCOON XML FILE REPLACED HTML TAGS WITH WML TAGS. BUT STILL text/html Kannel is a gateway, not a content server. It cannot know file extensions. (Or tags, before parsing the content!). But does see response headers. 4) WROTE A SERVLET PROGRAM, SET CONTENT-TYPE AS text/vnd.wap.wml AND HURRAH OUTPUT OF SERVLET SEEN IN ERICSSON R380 That's true. Kannel compiles content with wml compiler, if Content-Type is text/vnd.wap.wml. (If Content-Type text/vnd.wap.wmlscript, it uses wmlscript compiler.) 5) CONCLUSION: WHENEVER KANNEL SEES .xml EXTENSION, FETCHES OUTPUT AND PASSES IT ON TO libxml2. GNOME XML LIBRARY FAILS TO PROCESS OUTPUT AND LABELS IT AS text/html Yes, Kannel does use Gnome XML. But decisions are based on Content-Type, as I said previously. Aarno
Re: SMS PDU for OTA-WSP connectionless Wap Push
Anarchy wrote: --- Aarno Syvänen [EMAIL PROTECTED] wrote: WSP Push Pdu 00 - app id? 06 - push 0D - header length? AE 92 04 3C 21 A5 6E 84 81 B4 80 AF 80 - no idea about the rest Is this a working tokenized SI document ? It is, have you tested it with a phone ? i copied this header from a previous message and it does work by trial and error, i've managed to trim it to just 00 06 01 AE though i still have no idea where the AE comes in This is the Content Type, only necessary header. It means application/vnd.wap.sic. (Compiled SI document.) See WSP Content-Type definitions in http://www.wapforum.org/wina. And remember that you must add 80 (turn first bit), content type value being a short integer actually, i'm only interested in sending the SI and both the UDH and WSP headers are not really important so i'll only want the bare necessities... the push can be successfully received by a T68. Yep, defaults works in most cases. Content Type is required, because there are many possible push content types. Aarno
Re: [RFC] Conffiguration variable for setting maximum incomingmessages queue length
Hi Nisan, Nisan Bloch wrote: Hi Aarno At 04:52 PM 4/19/02 +0300, Aarno Syvänen wrote: Hi List, There have been some high stress Kannel tests (continous 350 msg/s, peak 560 msg/s) here at Wiral. Kannel will crash, because incoming messages queue what hardware are you running this on? There were four processors, two Kannels (with cimd simulators) running in 850 MHz Celerons and an application protocol running in a two-processor machine. Is this using Mysql or mem based dlr lists? No dlrs at all. This is because application protocol on the top of Kannel is of request - response type. So, one could say, dlrs are build into the protocol itself. Yes, it would be nice to test results with dlrs - this being more normal Kannel usage. What type of SMSCs are u connecting to? SMSCs were CIMD simulators running in same machine than Kannels. You must remember Kannel queue problem I mentioned. But this shows itself more in crashes than in performance. I report again when the queue problem is fixed. Aarno
Re: SMS PDU for OTA-WSP connectionless Wap Push
Anarchy wrote: i've figured out how to tokenise the SI but the encoding of the WSP headers still eludes me what do the numbers mean? WSP Push Pdu 00 - app id? 06 - push 0D - header length? AE 92 04 3C 21 A5 6E 84 81 B4 80 AF 80 - no idea about the rest Is this a working tokenized SI document ? It is, have you tested it with a phone ? WAP-230-WSP-20010705 doesn't help much... is there another doc? No. And anyway, it is normative. Note that you should add 80 to values (turn first bit, because these are short integers). Aarno
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
Re: [RFC] implementing XML-SMS calls using libxml2 functions
Hi, Stipe Tolj wrote: Hi all, I'd like to hear votes for rolling current cvs tree back, espacially the parts Bruno added for the XML-SMS support using the octstr_append() implementation. We should do this with libxml2 functions. At least I would like to strip things out again as soon as I have finished the libxml2 implementation. Comments and votes please. Keeping code until you have libxml implementation is, I think, best thing to do. This attribute value parsing code may have some testing. Aarno
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
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
