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
Errors when compiling
Hi! When I compile the development version 1.3.0 I get an undefined reference to 'gw_panic' error when it gets to the wmlscript folder. The errors occur in wserror.c and wslexer.c. What should I do? Regards, Kari
Re: Requesting User Agent Profile
Azeemuddin Mohammed wrote: Hi, When the client sends a request it also sends this user agent information by the help of this you can differentiate if its a WAP enabled client or imode or something else. I don't think that i-mode devices will be sending WAP packets to an WAP gateway, or am I wrong?! Has anyone seen such a beast? ;) Stipe [EMAIL PROTECTED] --- Wapme Systems AG Münsterstr. 248 40470 Düsseldorf Tel: +49-211-74845-0 Fax: +49-211-74845-299 E-Mail: [EMAIL PROTECTED] Internet: http://www.wapme-systems.de --- wapme.net - wherever you are
Re: ppg smsc routing
Aarno Syvänen wrote: Definitely. Actually this may be a simple thing to do. (Ppg should have url parameters as sendsms does.) so we need to duplicate code?! hmm, not that style we really want, or?! Stipe [EMAIL PROTECTED] --- Wapme Systems AG Münsterstr. 248 40470 Düsseldorf Tel: +49-211-74845-0 Fax: +49-211-74845-299 E-Mail: [EMAIL PROTECTED] Internet: http://www.wapme-systems.de --- wapme.net - wherever you are
Re: Method not supported problem
patch applied and commited to cvs. Thanks Vjacheslav! 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: Errors when compiling
When I compile the development version 1.3.0 I get an undefined reference to 'gw_panic' error when it gets to the wmlscript folder. The errors occur in wserror.c and wslexer.c. What should I do? did you compile from a clean source tree?! send us a log of the make process, including information what OS, gcc etc. 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: Requesting User Agent Profile
Hi Stipe, If you have a common Web/Application Server serving both WAP and CHTML pages, it needs to detect the type of client and this is relevant only in this kind of scenario. You are correct, i-mode devices will never send WAP packets. Regards, Azeem. -Original Message- From: Stipe Tolj [mailto:[EMAIL PROTECTED]] Sent: Thu 1/9/2003 4:46 PM To: Azeemuddin Mohammed Cc: amit sehgal; [EMAIL PROTECTED] Subject:Re: Requesting User Agent Profile Azeemuddin Mohammed wrote: Hi, When the client sends a request it also sends this user agent information by the help of this you can differentiate if its a WAP enabled client or imode or something else. I don't think that i-mode devices will be sending WAP packets to an WAP gateway, or am I wrong?! Has anyone seen such a beast? ;) 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 **Disclaimer** Information contained in this E-MAIL being proprietary to Wipro Limited is 'privileged' and 'confidential' and intended for use only by the individual or entity to which it is addressed. You are notified that any use, copying or dissemination of the information contained in the E-MAIL in any manner whatsoever is strictly prohibited.
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: Requesting User Agent Profile
If you have a common Web/Application Server serving both WAP and CHTML pages, it needs to detect the type of client and this is relevant only in this kind of scenario. yes the application side with destinguish between WAP related and i-mode related clients. But the device will not do that. 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: Errors when compiling
I configured it again using --disable-ssl and then it worked. For now I don't use SSL. The source I'm using was downloaded from www.kannel.3glab.org and is the official development release and not from the source tree. I've downloaded the previous development version and then I had no problem. Also, I would like to vote +1 on the tariff patch that has been circling the mailing lists. Kari -Original Message- From: Stipe Tolj [mailto:[EMAIL PROTECTED]] Sent: den 9 januari 2003 13:33 To: Kari Bengs Cc: [EMAIL PROTECTED] Subject: Re: Errors when compiling When I compile the development version 1.3.0 I get an undefined reference to 'gw_panic' error when it gets to the wmlscript folder. The errors occur in wserror.c and wslexer.c. What should I do? did you compile from a clean source tree?! send us a log of the make process, including information what OS, gcc etc. Stipe [EMAIL PROTECTED] --- Wapme Systems AG Münsterstr. 248 40470 Düsseldorf Tel: +49-211-74845-0 Fax: +49-211-74845-299 E-Mail: [EMAIL PROTECTED] Internet: http://www.wapme-systems.de --- wapme.net - wherever you are
Re: ppg smsc routing
The suggestion would be to add smsc=... to the ppg URL as it is in the sendsms URL. This would allow the same mechanisms to work for SMSC selection for PPG and normal SMS delivery. On Donnerstag, Januar 9, 2003, at 12:50 Uhr, Aarno Syvänen wrote: All duplicate code should go gw/shared. But ppg must send cgi parameter values through many protocol layers, as smbox does not. There would be differences. Aarno On Thursday, January 9, 2003, at 12:17 PM, Stipe Tolj wrote: Aarno Syvänen wrote: Definitely. Actually this may be a simple thing to do. (Ppg should have url parameters as sendsms does.) so we need to duplicate code?! hmm, not that style we really want, or?! Stipe [EMAIL PROTECTED] --- Wapme Systems AG Münsterstr. 248 40470 Düsseldorf Tel: +49-211-74845-0 Fax: +49-211-74845-299 E-Mail: [EMAIL PROTECTED] Internet: http://www.wapme-systems.de --- wapme.net - wherever you are Andreas Fink Fink Consulting GmbH --- Tel: +41-61-332 Fax: +41-61-331 Mobile: +41-79-2457333 Address: Clarastrasse 3, 4058 Basel, Switzerland E-Mail: [EMAIL PROTECTED] Homepage: http://www.finkconsulting.com ---
Memory leak suspicion in wap-appl.c
Hi, list.
I suspect memory leak in wap-appl.c
It's about set_referer_url():
static void set_referer_url(Octstr *url, WSPMachine *sm)
{
gw_assert(url != NULL);
gw_assert(sm != NULL);
sm-referer_url = octstr_duplicate(url);
}
In wap-appl.c we use it:
if (session_id != -1) {
debug(wap.wsp.http,0,WSP: Setting Referer URL to %s,
octstr_get_cstr(url));
if ((sm = find_session_machine_by_id(session_id)) != NULL) {
set_referer_url(url, sm);
} else {
error(0,WSP: Failed to find session machine for ID %ld,
session_id);
}
}
I don't see where preovious sm-referer_url destroyed.
Must we before
sm-referer_url = octstr_duplicate(url);
Insert
octstr_destroy(sm-referer_url); ?
Or may be I simply didn't find where it destroyed ;-) .
--
Vjacheslav Chekushinmailto:[EMAIL PROTECTED]
Latvian Mobile Phone Companyhttp://www.lmt.lv
Re: ppg smsc routing
Andreas Fink wrote: The suggestion would be to add smsc=... to the ppg URL as it is in the sendsms URL. This would allow the same mechanisms to work for SMSC selection for PPG and normal SMS delivery. sounds reasonable and practible. +1 from me. Stipe [EMAIL PROTECTED] --- Wapme Systems AG Münsterstr. 248 40470 Düsseldorf Tel: +49-211-74845-0 Fax: +49-211-74845-299 E-Mail: [EMAIL PROTECTED] Internet: http://www.wapme-systems.de --- wapme.net - wherever you are
Problem with SMPP 3.3 SMSC in message delivery
Hi YJ, How did u solved the prob. of Incomplete replies I am trying to connect with logica smsc. I am also getting the same prob. which The Kannel bearer's log text indicated that it: SMPP handle_pdu Got DELIVER REPORTBut then it followed up with ERROR:Got DELIV REPORT but couldnt find messageor was not interested in it For deliver_sm I am getting service_type "NOREP" (No Reply), We have defined the system-type = Ext. ###deliver_sm dump 2003-01-09 19:44:28 [6] DEBUG: type_name: deliver_sm2003-01-09 19:44:28 [6] DEBUG: command_id: 5 = 0x00052003-01-09 19:44:28 [6] DEBUG: command_status: 0 = 0x2003-01-09 19:44:28 [6] DEBUG: sequence_number: 3 = 0x00032003-01-09 19:44:28 [6] DEBUG: service_type: "NOREP"2003-01-09 19:44:28 [6] DEBUG: source_addr_ton: 1 = 0x00012003-01-09 19:44:28 [6] DEBUG: source_addr_npi: 1 = 0x00012003-01-09 19:44:28 [6] DEBUG: source_addr: "919029392923"2003-01-09 19:44:28 [6] DEBUG: dest_addr_ton: 0 = 0x2003-01-09 19:44:28 [6] DEBUG: dest_addr_npi: 1 = 0x00012003-01-09 19:44:28 [6] DEBUG: destination_addr: "1234"## and then there is no submit_sm for this msg. following is the dump of bind_transmitter and bind_receiver ## 2003-01-09 17:37:41 [5] DEBUG: type_name: bind_transmitter2003-01-09 17:37:41 [5] DEBUG: command_id: 2 = 0x00022003-01-09 17:37:41 [5] DEBUG: command_status: 0 = 0x2003-01-09 17:37:41 [5] DEBUG: sequence_number: 0 = 0x2003-01-09 17:37:41 [5] DEBUG: system_id: "test"2003-01-09 17:37:41 [5] DEBUG: password: "test"2003-01-09 17:37:41 [5] DEBUG: system_type: "Ext"2003-01-09 17:37:41 [5] DEBUG: interface_version: 51 = 0x00332003-01-09 17:37:41 [5] DEBUG: addr_ton: 0 = 0x2003-01-09 17:37:41 [5] DEBUG: addr_npi: 1 = 0x00012003-01-09 17:37:41 [5] DEBUG: address_range: "^1234" 2003-01-09 17:37:41 [6] DEBUG: type_name: bind_receiver2003-01-09 17:37:41 [6] DEBUG: command_id: 1 = 0x00012003-01-09 17:37:41 [6] DEBUG: command_status: 0 = 0x2003-01-09 17:37:41 [6] DEBUG: sequence_number: 1 = 0x00012003-01-09 17:37:41 [6] DEBUG: system_id: "test"2003-01-09 17:37:41 [6] DEBUG: password: "test"2003-01-09 17:37:41 [6] DEBUG: system_type: "Ext"2003-01-09 17:37:41 [6] DEBUG: interface_version: 51 = 0x00332003-01-09 17:37:41 [6] DEBUG: addr_ton: 1 = 0x00012003-01-09 17:37:41 [6] DEBUG: addr_npi: 1 = 0x00012003-01-09 17:37:41 [6] DEBUG: address_range: "^1234" # This prob. is only coming with logica smsc, there was no prob. connecting with other types of SMSC's. RegardsRitesh Shah
Re: Problem with SMPP 3.3 SMSC in message delivery
Hi please give more of the log file, we need to see the full deliver_sm PDU dump nisan At 12:09 AM 1/10/03 +0530, Ritesh Shah wrote: Hi YJ, How did u solved the prob. of Incomplete replies I am trying to connect with logica smsc. I am also getting the same prob. which The Kannel bearer's log text indicated that it: SMPP handle_pdu Got DELIVER REPORT But then it followed up with ERROR: Got DELIV REPORT but couldnt find message or was not interested in it For deliver_sm I am getting service_type NOREP (No Reply), We have defined the system-type = Ext. ###deliver_sm dump 2003-01-09 19:44:28 [6] DEBUG: type_name: deliver_sm 2003-01-09 19:44:28 [6] DEBUG: command_id: 5 = 0x0005 2003-01-09 19:44:28 [6] DEBUG: command_status: 0 = 0x 2003-01-09 19:44:28 [6] DEBUG: sequence_number: 3 = 0x0003 2003-01-09 19:44:28 [6] DEBUG: service_type: NOREP 2003-01-09 19:44:28 [6] DEBUG: source_addr_ton: 1 = 0x0001 2003-01-09 19:44:28 [6] DEBUG: source_addr_npi: 1 = 0x0001 2003-01-09 19:44:28 [6] DEBUG: source_addr: 919029392923 2003-01-09 19:44:28 [6] DEBUG: dest_addr_ton: 0 = 0x 2003-01-09 19:44:28 [6] DEBUG: dest_addr_npi: 1 = 0x0001 2003-01-09 19:44:28 [6] DEBUG: destination_addr: 1234 ## and then there is no submit_sm for this msg. following is the dump of bind_transmitter and bind_receiver ## 2003-01-09 17:37:41 [5] DEBUG: type_name: bind_transmitter 2003-01-09 17:37:41 [5] DEBUG: command_id: 2 = 0x0002 2003-01-09 17:37:41 [5] DEBUG: command_status: 0 = 0x 2003-01-09 17:37:41 [5] DEBUG: sequence_number: 0 = 0x 2003-01-09 17:37:41 [5] DEBUG: system_id: test 2003-01-09 17:37:41 [5] DEBUG: password: test 2003-01-09 17:37:41 [5] DEBUG: system_type: Ext 2003-01-09 17:37:41 [5] DEBUG: interface_version: 51 = 0x0033 2003-01-09 17:37:41 [5] DEBUG: addr_ton: 0 = 0x 2003-01-09 17:37:41 [5] DEBUG: addr_npi: 1 = 0x0001 2003-01-09 17:37:41 [5] DEBUG: address_range: ^1234 2003-01-09 17:37:41 [6] DEBUG: type_name: bind_receiver 2003-01-09 17:37:41 [6] DEBUG: command_id: 1 = 0x0001 2003-01-09 17:37:41 [6] DEBUG: command_status: 0 = 0x 2003-01-09 17:37:41 [6] DEBUG: sequence_number: 1 = 0x0001 2003-01-09 17:37:41 [6] DEBUG: system_id: test 2003-01-09 17:37:41 [6] DEBUG: password: test 2003-01-09 17:37:41 [6] DEBUG: system_type: Ext 2003-01-09 17:37:41 [6] DEBUG: interface_version: 51 = 0x0033 2003-01-09 17:37:41 [6] DEBUG: addr_ton: 1 = 0x0001 2003-01-09 17:37:41 [6] DEBUG: addr_npi: 1 = 0x0001 2003-01-09 17:37:41 [6] DEBUG: address_range: ^1234 # This prob. is only coming with logica smsc, there was no prob. connecting with other types of SMSC's. Regards Ritesh Shah
Extensive DLR testing with SMPP found lots of bugs
Hi All, We spent a lot of time testing almost all possible DLR conditions with SMPP; We did it using Kannel stable 1.2.1, 1.3.0 and also CURRENT CVS. So, this behaviour is VERY OLD; We are using external dlr storage with MySQL and SMPP interface-version 33; The SMSC is a CMG one; I will further do the same tests with Logica's SMSC and with interface version 34 when Kannel supports message payload; If somebody want to join us in testing SMPP DLR, feel free to look inside the attached Excel spreadsheet, with all testing data and also DEBUG information extracted from Kannel's logfiles. The summary of symptoms are: 1) Kannel is not doing multiple DLR notifications per message when requested (e.g. sendms dlrmask=31) 2) Kannel is not inserting a record in mysql dlr table when sendsms dlrmask is 16 3) Kannel is setting the mysql drl field status to 0 when dlrmask is 4 or 20 and also setting mysql dlr field timestamp to 000 4) Dlrmasks 8,9,10,25,26 or 27 are returning dlr-status equal to 12 when should return 8 5) In many test cases (dlrmasks 9,10,11,13,14,15,25,26, 27,29,30 or 31) Kannel says DLR not deleted because we wait on more reports but after receiving a correct deliver_sm (DLR) it just didn't find the mysql row, telling no rows found and then got DLR but could not find message or was not interested in it 6) When Kannel says removing DLR from database the respective mysql row remains on the dlr table I hope it helps everybody, including me. I would like to heare comments and suggestions on that. Best regards, Mauricio. dlr_tests.xls dlr_tests.xls Description: MS-Excel spreadsheet
Re: Extensive DLR testing with SMPP found lots of bugs
On Freitag, Januar 10, 2003, at 12:36 Uhr, Mauricio Ramos wrote: Hi All, We spent a lot of time testing almost all possible DLR conditions with SMPP; We did it using Kannel stable 1.2.1, 1.3.0 and also CURRENT CVS. So, this behaviour is VERY OLD; We are using external dlr storage with MySQL and SMPP interface-version "33"; The SMSC is a CMG one; I will further do the same tests with Logica's SMSC and with interface version "34" when Kannel supports message payload; If somebody want to join us in testing SMPP DLR, feel free to look inside the attached Excel spreadsheet, with all testing data and also DEBUG information extracted from Kannel's logfiles. The summary of symptoms are: 1) Kannel is not doing multiple DLR notifications per message when requested (e.g. sendms dlrmask=31) Hmm. this is to be considered a BUG. only when a final state has been reached the db entries should be removed. In a temporary state (buffered), it should be notified and still kept (EMI driver does this correctly). 2) Kannel is not inserting a record in mysql dlr table when sendsms dlrmask is "16" it might insert one but a different one. for status 1, 2, 4 the message ID from the remote SMSC are needed. for 8 and 16, a temporary internal ID is used as the message ID is not being received back yet. In the EMI driver the sequence number is used for that. Now in SMPP it might be done different but be aware that it might not even add anything as the answer will be back within seconds (worst case is the timeout of the SMPP session) so the statuses could be very well kept in memory. 3) Kannel is setting the mysql drl field status to "0" when dlrmask is "4" Thats an appropriate status for a message not being delivered to the SMSC yet. or "20" and also setting mysql dlr field timestamp to "000" correct. this happens when the SMS is being submitted to the SMSC. we dont know if it has been buffered yet and we dont have any update from the other side about the message ID. 4) Dlrmasks 8,9,10,25,26 or 27 are returning dlr-status equal to "12" when should return "8" I've seen that as well. They should return a status 8 and another message with status 4 instead. 5) In many test cases (dlrmasks 9,10,11,13,14,15,25,26, 27,29,30 or 31) Kannel says "DLR not deleted because we wait on more reports" but after receiving a correct deliver_sm (DLR) it just didn't find the mysql row, telling "no rows found" and then "got DLR but could not find message or was not interested in it" then the message-id mapping is wrong. it doesnt find the message in the database. This is SMSC dependent and requires proper configuration for really odd SMSC who once send you message ID in hex, once in alphanumeric and once in decimal (really stupid...). 6) When Kannel says "removing DLR from database" the respective mysql row remains on the dlr table Now this is really odd. edit the dlr.c and enable a variable to do SQL dumps so you see the SQL statements its executing. This helps a lot to debug those things. Maybe its the same issue as above, wrong type of message ID. Andreas Fink Fink Consulting GmbH --- Tel: +41-61-332 Fax: +41-61-331 Mobile: +41-79-2457333 Address: Clarastrasse 3, 4058 Basel, Switzerland E-Mail: [EMAIL PROTECTED] Homepage: http://www.finkconsulting.com ---
