AW: kannel 1.3.0 lacks rc5 algorith
RC5 is a patented algorithm. That's why the OpenSSL version included in Linux distributions comes without Rc5. Download the original SSL sources and compile from scratch. Regards Joerg -Ursprüngliche Nachricht- Von: Ivone Uribe [mailto:[EMAIL PROTECTED]] Gesendet: Freitag, 31. Januar 2003 02:13 An: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Betreff: kannel 1.3.0 lacks rc5 algorith Hi all!! I'm trying to install the kannel 1.3.0,I had the kannel 1.2.0 running, well I uninstalled it for install the kannel 1.3.0 :::(( But I don't understand why I get this error when I run the make, gcc -D_REENTRANT=1 -I. -Igw -g -O2 -DBROKEN_PTHREADS=1 -I/usr/include/libxml -I/usr/include -I/usr/local/ssl/include -o wap/wtls_statesupport.o -c wap/wtls_statesupport.c wap/wtls_statesupport.c:15:2: #error your OpenSSL installation lacks RC5 algorithm support make: *** [wap/wtls_statesupport.o] Error 1 I have the rc5.h in the /usr/local/ssl/include/lib I did it: ./configure --prefix=/usr/local/gw --with-ssl=/usr/local/ssl --with-wtls=openssl --enable-start-stop-daemon --disable-docs make (the error is here) make install I have the following enviroments variables CPPFLAGS=-I/usr/local/ssl/include LDFLAGS=-L/usr/local/ssl/lib I have already done it with the kannel 1.2 and I can install it!, do I need something else? Please, someone can help me! thanks a lot, Ivone _
AW: Problem with packing headers
So I think case 3 must not break specification. Do I miss something? It might be legal, but it's at least unusual. In this case the IETF guideline be conservative with what you send comes into play. Why would you insist in something that might (and obviously does) cause trouble when there is a perfectly fine and wildly used alternative available? Just don't do it! Regards Joerg
AW: Kannel WAP gateway and Linux Virtual Server (LVS)
I think Stipe does this. At least his latest sig was: -- Hope to see you at my presentations: Virtual Server solution for Linux using FreeVSD at O'Reilly Open Source Convention 2002, Sheraton San Diego Hotel and Marina, San Diego, CA. USA July 22-26, 2002 Regards Jörg -Ursprüngliche Nachricht- Von: Paul Keogh [mailto:[EMAIL PROTECTED]] Gesendet am: Dienstag, 30. Juli 2002 10:23 An: Kannel Development List (E-mail) Betreff: Kannel WAP gateway and Linux Virtual Server (LVS) Hi, Has anyone tried to run the WAP g/way behind LVS ? Thanx, 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
AW: Phone as MMSC
Maybe a better question would be: Can one send a MMS message with just a GPRS enabled mobile phone as network attachment. I think this would be possible. The onliest requirement would be that the phone gets a public IP address from the carrier (so that the MMS server can be reached). Regards Jörg -Ursprüngliche Nachricht- Von: Stipe Tolj [mailto:[EMAIL PROTECTED]] Gesendet am: Dienstag, 16. Juli 2002 10:21 An: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Betreff: Re: Phone as MMSC David Chkhartishvili wrote: Is it possible to use MMS enabled phone as MMSC? the MMSC consists of an MMS Proxy (which is actually Kannel's WAP gateway part) and an MMS Server (which is an HTTP based application). I'd suggest you to have a deeper look into the MMS architecture specs. 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
AW: Phone as MMSC
-Ursprüngliche Nachricht- Von: Aarno Syvänen [mailto:[EMAIL PROTECTED]] Gesendet am: Dienstag, 16. Juli 2002 11:42 An: Jörg Pommnitz Cc: [EMAIL PROTECTED] Betreff: Re: AW: AW: Phone as MMSC You mean are there AT commands for sending a MM ? A No, I'm quite sure that there are no ready made AT commands to send a MM. But what does Kannel require to send one? A SMSC and IP connectivity, right? A GPRS phone could provide this (Actually, if you dont mind the cost for beiing online forever, every GSM phone would do). Am I right? Regards Jörg
AW: AW: Phone as MMSC
-Ursprüngliche Nachricht- Von: Stipe Tolj [mailto:[EMAIL PROTECTED]] It regardless if the phone has direct IP connectivity. The MMS has to be encoded in the appropirate binary format and uses WAP as bearer to transmit the MMS to the MMS Server (the HTTP server). Stipe Right. I don't see any major problem to run Kannel on a WinCE device (they come with 128MB RAM and WinCE 3.0). Assuming this works, one could send a MMS from a GSM/GPRS connected SmartPhone or a Laptop with GPRS. This way one would run a smallish MMSC one a Phone. Regards Jörg
AW: patch
-Ursprüngliche Nachricht- Von: Andreas Fink [mailto:[EMAIL PROTECTED]] Gesendet am: Mittwoch, 10. Juli 2002 19:45 An: [EMAIL PROTECTED] Betreff: Re: patch And furthermore you have number portability so you wont know which prefix really belongs where because the number might now belong to another carrier. I aggree. Number portability makes a mess out of a lot of things. Everything was nice and clean and suddenly sending a SMS through a carrier SMSC becomes a nightmare. Is there any way at all to figure out the carrier when you only have the MSISDN in an environment with number portability? Maybe some central MSISDN to carrier server? Regards Jörg
AW: patch
Nope, have to talk SS7 and query the HLR Steve Then there should be some kind of (HTTP?) frontend to SS7 that allows just this kind of queries. I don't think that this would violate privacy because it only provides the same kind of information one could previously get from looking at the MSISDN. How feasible is this? Regards Jörg
AW: Is Kannel only for GSM? And how about TDMA, CDMA, CDMA1XRTT and iDEN?
Kannel does not care about what kind of network is actually used to talk to the mobiles. The WAP part speaks WTP/WSP over UDP/IP, the SMS part speaks the SMSC access protocols. As long as theses interfaces are supported Kannel will work. Regards Joerg -Ursprüngliche Nachricht- Von: Mauricio Ramos [mailto:[EMAIL PROTECTED]] Gesendet am: Montag, 24. Juni 2002 21:51 An: '[EMAIL PROTECTED]' Cc: '[EMAIL PROTECTED]' Betreff: Is Kannel only for GSM? And how about TDMA, CDMA, CDMA1XRTT and iDEN? Wichtigkeit: Hoch Hi, I'm a witness that Kannel works with TDMA because this is the network I've been testing on and as far as I know, this has no much thing to do with a SMS Gateway. It's important to me to know if Kannel works well on TDMA, CDMA, CDMA1XRTT and iDEN, because in my Country we have all of these in production and now GSM also. Thanks for you advice. Maurício Collaça Ramos Systems Integration Manager w-Aura
AW: XSL Stylesheet for Kannel's status.xml
I think it's a stupid idea that is hard to implement and beyond the scope of Kannel. You can always transform the XML-data on the client side. I think I have to explain why I consider this a stupid idea. The point of XSLT is, that you can transform XML streams to conform to different formats (DTDs). That's why it's common sense to apply the transformation as close to the final user as possible. See, if you would apply the transformation in Kannel, you would get something like this: HTTP Kannel --- Transformer + XSLT - Consumer If you make the XSLT transformation at the client side, you get HTTP Kannel -- Transformer + XSLT1 - Consumer 1 Transformer + XSLT2 - Consumer 2 Transformer + XSLT3 - Consumer 3 See? Transformation at the client side is much more flexible and the way it is supposed to be. Regards Joerg
AW: XSL Stylesheet for Kannel's status.xml
And just who would execute the stylesheet? Kannel does not include a library that provides a XSLT transformer... I think it's a stupid idea that is hard to implement and beyond the scope of Kannel. You can always transform the XML-data on the client side. Regards Jörg -Ursprüngliche Nachricht- Von: Mauricio Ramos [mailto:[EMAIL PROTECTED]] Gesendet am: Montag, 24. Juni 2002 20:57 An: '[EMAIL PROTECTED]' Betreff: XSL Stylesheet for Kannel's status.xml Hi All, I would like to know how and by the way suggest you to have a configurable XSL stylesheet to be used when acessing status.xml. It's just a simple idea which would be easy to implement. Regards.
AW: SMS to WAP functionality
Depends on the SMS reader software. The implementation from Magic4 (www.magic4.com) supports it. Generally you can't depend on this feature. Regards Jörg -Ursprüngliche Nachricht- Von: Alex Judd [mailto:[EMAIL PROTECTED]] Gesendet am: Donnerstag, 16. Mai 2002 22:09 Cc: Kannel-devel (E-mail) Betreff: SMS to WAP functionality Apoligies - not directly a development question but the forum here is the most knowledgable I know so I thought I might ask a quick usage question. In order to embed a WAP URL in an SMS does anyone know if standard WAP enabled phones allow a 'click-to-wap' type functionality or does it have to be sent as an OTA or WAP Push message? Thanks everyone Alex -- Alex Judd http://www.skywire.co.uk
AW: About KWTLS
KWTLS leaks memory like a seave. It's nowhere near ready for production use. Regards Jörg
AW: MMS status.
-Ursprüngliche Nachricht- Von: Stipe Tolj [mailto:[EMAIL PROTECTED]] We'd needs someone familiar with SAR for IP to implement this in WTP. Is this SAR as in Segmentation and Reassembly? Regards Jörg
AW: Broken Ericsson T68
For a different internal project I wrote a little function that calls the chat program to initialize the mobile phone/modem. Maybe this is the way to go for Kannel as well. This way we could trim SMSC AT2 and leave all the little ugly details in an external chat script. What do you think? Regards Jörg -Ursprüngliche Nachricht- Von: Bruno David Rodrigues [mailto:[EMAIL PROTECTED]] Gesendet am: Freitag, 15. März 2002 18:41 An: Kannel-devel (E-mail) Betreff: Broken Ericsson T68 I've discovered that Ericsson T68 is REALLY broken! When receiving SMS's, there's at least two bugs. First non-bug is that the init string have to be AT+CNMI=3,3 Because that's almost the only parameteres accepted: AT+CNMI=? +CNMI: (3),(0,1,3),(0,2),(0),(0) but that's ok, because it delivers the message to kannel anyway. But then when I receive a message: +CMT: 31 Without the colon!!! Broken. But it gets worst: Ericsson counts the wole string, with SMSC included! 07915396161604098519494002F739002030515191730005F4F29C5E06 I have 07 bytes for SMSC and 23 bytes for PDU, I should receive +CMT: ,23 Bad broken Ericsson...
RE: [RFI+Patch] AT2 Modems.conf
I just commited the following patch:
diff -u -r1.31 smsc_at2.c
--- gw/smsc_at2.c 13 Mar 2002 00:28:31 - 1.31
+++ gw/smsc_at2.c 13 Mar 2002 11:09:59 -
@@ -544,26 +544,34 @@
if(ModemTypes[privdata-modemid].pin_support)
{
ret = at2_send_modem_command(privdata, AT+CPIN?, 10, 0);
-if(ret == -1)
- return -1;
-if(ret == 2)
-{
-if(privdata-pin == NULL)
-return -1;
-setpin = octstr_format(AT+CPIN=%s,
octstr_get_cstr(privdata-pin));
- ret = at2_send_modem_command(privdata, octstr_get_cstr(setpin),
0, 0);
- octstr_destroy(setpin);
- if(ret !=0 )
- return -1;
-}
+
+ if (!privdata-pin_ready)
+ {
+ if(ret == 2)
+ {
+ if(privdata-pin == NULL)
+ return -1;
+ setpin = octstr_format(AT+CPIN=%s,
octstr_get_cstr(privdata-pin));
+ ret = at2_send_modem_command(privdata,
octstr_get_cstr(setpin), 0, 0);
+ octstr_destroy(setpin);
+ if(ret !=0 )
+ return -1;
+ } else if(ret == -1)
+ return -1;
+ }
+
/* we have to wait until +CPIN: READY appears before issuing
the next command. 10 sec should be suficient */
if(!privdata-pin_ready)
{
- ret = at2_wait_modem_command(privdata,10, 0);
- if(ret == -1) /* timeout */
- return -1;
+ at2_wait_modem_command(privdata,10, 0);
+ if(!privdata-pin_ready) {
+ at2_send_modem_command(privdata, AT+CPIN?, 10, 0);
+ if(!privdata-pin_ready) {
+ return -1; /* give up */
+ }
+ }
}
}
// Set the GSM SMS message center address if supplied
With this patch applied Wavecom works again for me. Please give it a try.
Regards
Jörg
-Original Message-
From: Oded Arbel
To: Andreas Fink; Abd Rahman Johari
Cc: [EMAIL PROTECTED]
Sent: 3/13/02 10:12 AM
Subject: RE: [RFI+Patch] AT2 Modems.conf
-Original Message-
From: Andreas Fink [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, March 13, 2002 10:12 AM
To: Abd Rahman Johari
Cc: [EMAIL PROTECTED]
Subject: Re: [RFI+Patch] AT2 Modems.conf
I think what we see here is
-- AT+CPIN?
--- +CPIN: SIM PIN
--- OK
-- AT+CPIN=1234
--- waiting for +CPIN READY not appearing.
Oded what's your view of this?
No, I don't think so - a proper wavecom session will looks like this
(given propert timeout everywhere) :
-- AT+CPIN?
-- +CPIN: SIM PIN
-- AT+CPIN=1234
-- OK
-- AT+CPIN?
-- +CPIN: READY
notice that wavecom does not send OK after +CPIN replys.
--
Oded Arbel
m-Wise Inc.
[EMAIL PROTECTED]
What on earth would a man do with himself if something did not stand in
his way?
-- H.G. Wells
RE: charset question (Greek)
-Original Message- From: Andreas Fink To: Richard Braakman Cc: [EMAIL PROTECTED] Sent: 3/13/02 12:51 PM Subject: Re: charset question (Greek) Another way would be to carry the SMS always in binary format around. This means the format actually used on the over the air. This is more or less the binary version of the PDU format of the AT interface. In this case, the SMSC driver would simply do things like encoding the data in hex or so. For EMI it woudl split off the UDH, for AT it would work as is and for SMPP its pretty similar. this would also work for HTTP interface for kannel-kannel (providing coding / charset are set correctly). Any SMSC types however who dont take binary format as input would be a problem then (some content gateway recently added could be a problem). If we cant code something in GSM binary format, we cant send it to a phone so its THE common format. However the question is also what happens to non GSM networks in this case. Are there any issues there maybe? I know of a SMS reseller in Taiwan where they use a proprietary gateway to connect to the SMSC of the network operator. This gateway wants the SMS text to be in BIG5 encoding. Your proposal would make support for such a setup very hard. Regards Jörg
RE: charset question (Greek)
I aggree with you that the current code is rather messy. We need just two cases: text and binary. Text should be in unicode while binary messages should be left alone. Then the the SMSC drivers could convert text messages into their local encoding, perform required splitting (with common infrastructure) and send the messages. Regards Jörg -Original Message- From: Andreas Fink To: Oded Arbel Cc: [EMAIL PROTECTED] Sent: 3/13/02 2:19 PM Subject: RE: charset question (Greek) A library function would be sufficient to handle this. So its not lots of recoding. We do lots of recoding already in kannel for no reason. And it makes current kannel non transparent which I consider pretty bad way to go.
RE: charset question (Greek)
Is a greek unicode text now to be sent as unicode or as GSM alphabeth?
Common infrastructure: provide conversion from Unicode to GSM 7bit
(including
Greek). Drivers can override the common fucntion to use whatever their
corresponding SMSC requires.
is a text suitable for ISO8859-1?
This is something we cannot decide. Where would you place the limit?
Is a single character that is out of range enough? Or 25%?
how about characters which exist in multiple unicode character tables?
I don't understand this. Where is the problem? (I know that the ASCII
characters appear multiple times in Unicode as part of the ISO8859
encodings).
how to do pattern matching?
We could use UTF-8 to encode Unicode and use the normal ANSI-C string
operations.
... and is an incoming SMS now binary or unicode?
This is a task for the SMSC driver. In the common case this is what the DCS
tells you.
what if we have an SMSC which supports ascii text but not binary or
unicode?
Don't use it for Unicode or binary messages. We cannot prevent stupidity
in Kannel.
how do we decide at routing if input=unicode or input=binary
but containing clean 7 bit text?
We know the original character set (e.g. from the content-type for POST
and the charset CGI parameter for GET).
What I envision is something like this
struct smsc_msg_ops {
int (*unicode_to_smsc)(Msg *);
int (*split_message)(Msg *);
};
Then we could do:
...at initialization...
SMSCenter *smsc;
struct smsc_ops ops;
ops = default_ops ();
smsc = smscenter_construct(ops);
...at runtime...
smsc-msg_ops-unicode_to_smsc(msg);
smsc-msg_ops-split_message(msg);
smsc-delivermsg (msg);
This is a very rough darft, but you get the idea.
Regards
Jörg
RE: [RFI] octstr_recode
Yeah, this is because we use the character conversion functions from libxml. I have a different version based on iconv that behaves more sane. Problem: iconv is not guaranteed to be portable (e.g. to Win). Regards Jörg -Original Message- From: Bruno David Rodrigues To: Kannel-devel (E-mail) Sent: 3/5/02 7:27 PM Subject: [RFI] octstr_recode I'm trying to use the octstr_recode function to convert a MO message from UCS2 to ISO-8859-1 or UTF-8 I was thinking in trying to recode to ISO-8859-1 if possible, otherwise convert to UTF-8 and set coding acordly. I thought that if the text couldn't be translated to ISO-8859, octstr_recode (octstr_imm(iso-8859-1), octstr_imm(UTF-16BE), text)) would return false and I could switch to octstr_recode (octstr_imm(utf-8), octstr_imm(UTF-16BE), text) but the first recode converts my %06%4A to a #1610; and returns ok. 2002-03-05 18:04:51 [6] INFO: DAVI:Received message with coding 3 2002-03-05 18:04:51 [6] INFO: DAVI:Received unicode message -J-064A- 2002-03-05 18:04:51 [6] INFO: DAVI: recode to iso8859-1 -#1610;-2623313631303B- 2002-03-05 18:04:51 [6] INFO: Starting to service #1610; from my-number to short-number 2002-03-05 18:04:51 [6] DEBUG: formatted text answer: Go away 2002-03-05 18:04:51 [6] DEBUG: message length 7, sending 1 messages May I search for #; in utf16-be to iso8859-1 and reject it, switching then to utf8 ??
RE: WTLS implementation status (restrictions of RSA) ?
The RSA patent expired in 2000. The algorithm is in the public domain now (RSA Inc. released it into the public domain a few weeks before the patent expired). See: http://www.rsasecurity.com/news/pr/000906-1.html However the RC5 algorithm is still patented. Regards Jörg -Original Message- From: Stipe Tolj To: Bjoern Buettner Cc: [EMAIL PROTECTED] Sent: 2/21/02 8:05 PM Subject: Re: WTLS implementation status (restrictions of RSA) ? Bjoern Buettner wrote: Is is possible to use openssl for WTLS? yes, currently it's the only supported configure option flag for --with-wlts. But hey, it's currently ony in the state to compile cleanly, I'm not aware how far Nick did get when implementing this, Nick?! Are there any restrictions regarding RSA encryption? You mean patent issues?! Hmmm, what do the others think about this? Which type of encryption does kannel support? Which cellular phones are supported? How can I configure Kannel for WTLS? you can configure using ./configure --with-wtls=openssl, but you can't *use* it. We need to addopt 3ui.com's wtlsbox for this, and unfortunatly no one is (or seems) currently working on this. It's on top of my TODO list, but I can put my hands on it for the next 2 weeks. Any volonteers with OpenSSL knowledge?! 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: Modification of gwthread_sleep for SMPP throttling
I second this. gwthread_sleep does what you want right now or I'm missing something. Regards Jörg -Original Message- From: Oded Arbel To: Alex Judd; [EMAIL PROTECTED] Sent: 2/20/02 4:33 PM Subject: RE: Modification of gwthread_sleep for SMPP throttling I don't think I understand. as gwthread_sleep accepts times in double and not integer, its easy to sleep for less then a second. for example - I usually use gwthread_sleep(0.1) which sleeps for a tenth of a second. what's wrong with the current implementation ? Oded Arbel m-Wise Inc. [EMAIL PROTECTED] -- Some say life is hell and death an escape, others say heaven awaits us in the world beyond, but either way I need a new pair of shoes. -- Privateer. -Original Message- From: Alex Judd [mailto:[EMAIL PROTECTED]] Sent: Wednesday, February 20, 2002 5:20 PM To: [EMAIL PROTECTED] Subject: Modification of gwthread_sleep for SMPP throttling In order to add (hopefully nice) throttling to the SMPP driver I'd like to modify the behaviour of the gwthread_sleep function in gwthread-pthread.c very slightly. Currently the function receives the amount of seconds to sleep as a double, multiplies it by 1000 to get that value in milliseconds and then sleeps for that amount of time in milliseconds. What I'd like to do is if the function recieves a value of 1 as the number of seconds to sleep for, that it instead assumes this to be the number of milliseconds to sleep for, skips the *1000 part and sleeps for this time instead. This way I can sleep nicely for 1 second periods. Any objections to this before I do so? Regards Alex -- Alex Judd http://www.skywire.co.uk/ http://www.enpocket.com/
AW: Wapbox does an idle loop in some cases
can you point that workaround more out, please? I have not found anything on the list itself. This is from Frederik Ammitzbøll: -- -Ursprüngliche Nachricht- Von: Frederik Ammitzbøll [mailto:[EMAIL PROTECTED]] Gesendet am: Freitag, 30. November 2001 15:45 An: KannelDevel Betreff: SV: smsbox eating CPU ? See below (sent in July): --- On a different note I believe to have located the source of CPU-hungry boxes. The problem lies in Kannel's handling of HTTP 1.1 requests. Try using the send-sms interface or the Kannel-admin module from a HTTP 1.1 compliant browser, leave the browser window open and watch the bearerbox or smsbox go powerhungry ~1 minute after the request. It happens every time!! My temporary workaround has been to treat all HTTP-requests as HTTP 1.0 (in http.c), but this is only a short-term solution as there are important benefits from using HTTP 1.1. --- This problem has existed for a long time and has never been fixed. Unfortunately, while my workaround has severely helped, two simultaneous HTTP-request to Kannel can sometimes have the same effect. cheers, Frederik Ammitzbøll Unwire Vestergade 12A, 3. 1456 København K Tlf.: +45 33 33 08 70 Mobil: +45 27 11 99 99 Fax : +45 33 33 09 70 Web: www.unwire.dk -- Has this been incorporated to the cvs tree? I don't think so. Regards Jörg
AW: AW: AW: Timeout-A - more info
What's the easiest way to compile the on my Win NT4-machine with VS6.0? I don't think there is an easy way for VS6.0. You will want to try cygwin (see http://sources.redhat.com/cygwin/). Regards Jörg
RE: [PATCH] smsc_at2.c not counting escape caracters (gsm7bit)
Hi List, I'm thinking about a general overhaul in this area. The interaction of * 7bit escape characters * UDH with multiple IEI's * message splitting and concatenation is a big mess right now (IMHO). What I would suggest is to discourage the use of the generic udh parameter (X-Kannel-UDH) and replace it with an iei parameter. This way Kannel could collect all IEI's in a message and easily distribute them over multiple separate SM's and prepend the correct concatenation header. I think this is needed for a fully working EMS implementation. Regards Jörg -Original Message- From: Stipe Tolj Cc: Devel@Kannel. 3glab. Org Sent: 1/23/02 9:06 PM Subject: Re: [PATCH] smsc_at2.c not counting escape caracters (gsm7bit) Lucio Ferrao wrote: When smsc_at2 sent a message in 7bit the length written in the PDU did not include the escape chars. I solved the problem calling the charset_latin1_to_gsm a little earlier. This lead to missing end chars when using escaped chars []... Thanks a lot Lucio for the patch. Any votes for commiting this to cvs please?! I'm +0 due to imperfect knowledge about it ;) 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: [RFC] new single-group 'ring-service'
This ring-service could be used in conjunction with other devices than GSM modems. You could attach an ISDN card with multiple channels listening on the same MSN and ease the problem of the busy phone. The answer would still have to be sent by SMS, of course. Regards Jörg
AW: Any SSL HTTP development for Kannel?
What's missing in http://www.kannel.3glab.org/cgi-bin/viewcvs.cgi/gateway/gwlib/conn.c.diff?r1 =1.39r2=1.40 ? Regards Jörg -Ursprüngliche Nachricht- Von: Stipe Tolj [mailto:[EMAIL PROTECTED]] Gesendet am: Montag, 21. Januar 2002 10:43 An: charles Cc: '[EMAIL PROTECTED]' Betreff: Re: Any SSL HTTP development for Kannel? SSL support is fully (ok, certification checking is yet not done)
AW: Looking after UDH coding and binary code for Siemens,Motorola, Ericsson...
3GPP: http://www.3gpp.org/specs/specs.htm -Ursprüngliche Nachricht- Von: Nicolas DAGNET [mailto:[EMAIL PROTECTED]] Gesendet am: Freitag, 18. Januar 2002 11:44 An: [EMAIL PROTECTED] Betreff: Looking after UDH coding and binary code for Siemens,Motorola, Ericsson... Hello, The nokia specifications are easy to find, but do you know where I can find them for others manufacturers (Ericsson, siemens,...)? Thanks in advance Nicolas
AW: EMS and splitting
Well, you do not have to teach Kannel about EMS for correct splitting. After all, EMS is just an extension for the default GSM UDH header. If the current code panics, it is clearly buggy in this regard. So my opinion: adding UDH-splitting is useful and can be added to Kannel without violating KISS principles. Regards Jörg -Ursprüngliche Nachricht- Von: Alexei Pashkovsky [mailto:[EMAIL PROTECTED]] Gesendet am: Donnerstag, 17. Januar 2002 00:08 An: Kannel Developers Betreff: Re: EMS and splitting I think as the kannel target is to stay as simple as possible, all the functionality for advanced sms services (EMS, SMART-SMS, WAP PUSH etc) should be implemented externally, so that kannel would not deal with things custom applications take care about, besides it gives more freedom for application developers. The only thing usefull indeed could be sharing the example code for such functionality. In my opinion, best way to achive kannel compatibility with udh-containing messages is to continue development of php scripts, as it was started long time ago, but depricated now. I can personally take care of this part, if there're enough interested developers. At the moment I have written scripts to support Nokia and Siemens gfx/ringtones implementations. As another usefull functionality there's a way to implement mySQL+PHP based retry mechanism for kannel, since currently Kannel does not deal with failed messages out of the box. Alexei. I'm working on an application that uses EMS to send graphic elements in messages. It's almost done, but I've came up with a problem with large messages that needs splitting: smsbox fails to do the work, it exists with a failed assertion. If the message fits in a single sms, everything is fine. Of course I have a workaround for this: my application takes care of correctly splitting the message into fragments, then send the fragments individually through Kannel. But I'm interested in contributing to Kannel a patch to do the required splitting for EMS correctly. Anyone with EMS knowlegde has any ideas or advise on how to acomplish this? I mean, currently Kannel duplicates the UDH part of a large SMS into all the fragments after splitting. That's not the case win EMS, we'll have to avoid that under certain scenarios, and maintain it for others (Nokia NBS headers for example). So, traversing the UDH and treating each of the IE's separately, based on known IEI's, could be a solution. Anyone with a more elegant idea? Of course, is there any interest in doing EMS stuff inside kannel? (I mean only proper splitting, not message composition). Angel Fradejas.
AW: if make fails, try gmake
-Ursprüngliche Nachricht- Von: Bernino Lind [mailto:[EMAIL PROTECTED]] Gesendet am: Donnerstag, 17. Januar 2002 16:14 The Gnu make tool distributed with Linux has some differences from the BSD derived Make tool which is shipped with Solaris and *BSD. Solaris and those its make are SYS V based. Regards Jörg
AW: Message splitting - UDH header problems?
Does your phone support message concatenation? -Ursprüngliche Nachricht- Von: P. A. Bagyenda [mailto:[EMAIL PROTECTED]] Gesendet am: Donnerstag, 17. Januar 2002 16:28 An: [EMAIL PROTECTED] Betreff: Message splitting - UDH header problems? Hi, I am trying out Kannel 1.1.5 and have experienced some problems with message splitting. If I set concatenation = true for any service, and that service generates a message that is too large to fit in one sms, then the messages sent to the phone are garbled. It appears that kannel is doing something wrong with the udh headers for splitting (according to the spec it is doing the right thing, so am a bit confused). Any ideas? I am using an SMPP gateway. Thanks. Paul Bagyenda
AW: high load troubles...
Could this be relevant? http://sources.redhat.com/ml/libc-hacker/2001-11/msg00028.html Regards Jörg
AW: Two part question!
I think it highly unlikely that C:/phpdev/www/mobile/samp1.php?sec_para=%sthr_para=%sphone=%p is a valid filename. If you want to get the output of the PHP script, you have to put it into an environment that will run it for you (normally a HTTP server). In this case you have to use a URL to access it. Regards Jörg -Ursprüngliche Nachricht- Von: Torbjorn Zetterlund [mailto:[EMAIL PROTECTED]] Gesendet am: Donnerstag, 10. Januar 2002 17:34 An: [EMAIL PROTECTED]; [EMAIL PROTECTED] Betreff: Two part question! Hi, I have a two part question, first I am trying to send an sms message to the kannel which should read a file and return the content. I do not receive the file content back to me, my config looks like # # Mobile payment confirmation # group = sms-service keyword = pay file = C:/phpdev/www/mobile/samp1.php?sec_para=%sthr_para=%sphone=%p am I missing something! Second question for me to learn more about OTA, SMS and about downloading ring tones, graphics elements to a phone, what documentation or sites should I use to get a full understanding. TZ Torbjorn Zetterlund VP, Mobile Commerce CertaPay Inc. [t] 416-777-5081 - Direct [f] 416-360-7121 [e] [EMAIL PROTECTED]
AW: Charset problem
I think you should fix your servlet. The content type ahs to match the content. Just claiming that it is UTF8 encoded does not magically recode the contents. You have to do this manually (and it's really easy in Java). So: this is NOT a Kannel problem but one inside your Servlet and besides one that should be very easy to fix. Java gives you all the tools. Regards Joerg -Ursprüngliche Nachricht- Von: Charles Poitvin [mailto:[EMAIL PROTECTED]] Gesendet am: Donnerstag, 20. Dezember 2001 13:15 An: [EMAIL PROTECTED] Betreff: Re: Charset problem You have to be a little bit more specific. What do you do? SMS or WAP? Regards Jörg Hi, I use it with WAP. I have tried to modify the charset with the servlet, using setContentType with a charset of UTF-8 but apparently it doesn't modify mail with an iso-8859-1 charset. So, I got an error in the gateway which can't translate. Is there a way to modify the default charset in kannel(UTF-8) or to permit multiple charset ? Thanks for all Charles
RE: mutex failure?
The things you are using are thread safe, so they lock their
inner state against concurrent access. You might want to add
a wrapper around mutex_unlock in the following way:
#define mutex_unlock(mtx)
mutex_unlock_inline(mtx,__FILE__,__LINE__,__PRETTY_FUNCTION__)
static inline mutex_unlock_inline(Mutex mtx, const char *file, int line,
const char *func) {
debug(mutex, 0, mutex_unlock called from %s: %d in function %s, file,
line, func);
mutex_unlock_real(mtx);
}
and rename the real mutex_unlock call to mutex_unlock_real.
This should give you an idea what mutex calls misbehave.
BTW.: Did you test the EMI2 code from todays CVS? I think your problems
should be fixed now.
Regards
Jörg
-Original Message-
From: Andreas Fink
To: [EMAIL PROTECTED]
Sent: 12/13/01 4:29 PM
Subject: mutex failure?
Can someone tell me what this message is exactly all about?
2001-12-13 15:13:38 [16] PANIC: mutex_unlock: Mutex failure!
2001-12-13 15:13:38 [16] PANIC: System error 22: Invalid argument
I get it in my app while using gwlib. I'm not using any mutexes. I'm
using octstr stuff, http stuff, lists, config and thats about it. the
odd thing is that this only happens if running memory=native but not
with memory=checked.
I dont have an idea why any of those areas would need to unlock a mutex.
--
Andreas Fink
Fink-Consulting
--
Tel: +41-61-6932730 Fax: +41-61-6932729 Mobile: +41-79-2457333
Address: A. Fink, Schwarzwaldallee 16, 4058 Basel, Switzerland
E-Mail: [EMAIL PROTECTED] Homepage: http://www.finkconsulting.com
--
Something urgent? Try http://www.smsrelay.com/ Nickname afink
RE: Ref-Counted octstr
Currently we often do a octstr_duplicate instead of the
octstr_get_ref in my made up example. This is simplified
but the pattern occurs quite often...
Regards
Jörg
-Original Message-
From: Aarno Syvänen
To: Jörg Pommnitz
Cc: ''[EMAIL PROTECTED]' '
Sent: 12/12/01 11:37 AM
Subject: Re: Ref-Counted octstr
Hi,
Jörg Pommnitz wrote:
I'm not sure I completely understand you. What I'd like
to allow would be something like this:
Octstr *foo;
Octstr *bar;
if (condition (bar)) {
foo = do_something_with (bar); /* foo points to a new Octstr,
refcount =
1 */
} else {
foo = octstr_get_ref (bar);/* foo becomes a new reference to
the
Octstr
pointed to by bar; refcount = 2
*/
}
do_something_else (foo);
octstr_destroy (foo);/* refcount gets decremented. if it
reaches zero,
the Octstr actually gets
released */
Huh. What did you mean with unneeded octstr_duplicate calls ?
Aarno
RE: Ref-Counted octstr
No, not if it's done right. It would only affect code that uses references. It would mean however that there are more ways to screw up in the code (modifying shared Octstrs being the prime candidate). Regards Jörg -Original Message- From: Stipe Tolj Cc: '''[EMAIL PROTECTED]' ' ' Sent: 12/12/01 3:49 PM Subject: Re: Ref-Counted octstr Aarno Syvänen schrieb: Jörg Pommnitz wrote: Currently we often do a octstr_duplicate instead of the octstr_get_ref in my made up example. This is simplified but the pattern occurs quite often... Yeah, octstr_get_ref would be nice. Forget my email: I think about another type of unneeded octstr_duplicate. I'm not into deep here, but would a major change have any global impacts? 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
AW: gwlib broken
-Ursprüngliche Nachricht- Von: Andreas Fink [mailto:[EMAIL PROTECTED]] Gesendet am: Dienstag, 11. Dezember 2001 01:07 An: [EMAIL PROTECTED] Betreff: gwlib broken a) It suddendly requires libxml2 which it didn't before. Is this really needed? Maybe I'm responsible for this. I introduced octstr_recode to convert an Octstr from one encoding to another. It uses the charset functions (part of gwlib, too) to achieve this. The charset functions are based on libxml. Regards Jörg
AW: charset_latin1_to_gsm in msg_to_pdu
It's probably a bug. The call should be made when coding is 1 (e.g. GSM 7bit character set). Regards Jörg -Ursprüngliche Nachricht- Von: Worik Macky Turei Stanton [mailto:[EMAIL PROTECTED]] Gesendet am: Dienstag, 11. Dezember 2001 00:12 An: kannel-devel Betreff: charset_latin1_to_gsm in msg_to_pdu Friends Whhat is the purpose of the call to charset_latin1_to_gsm in msg_to_pdu? It is only called if the udhdata length is not 0. Worik -- Worik Macky Turei Stanton Whew! [EMAIL PROTECTED] Aotearoa
AW: AW: Kannel on PPC
Im somewhat troubled by the following lines from the gdb backtrace: #2 0x10048048 in octstr_format (fmt=0x0) at gwlib/octstr.c:1958 #3 0x10015938 in smsc_http_create (conn=0x101a6908, cfg=0x0) at gw/smsc_http.c:444 Either gdb is lying or something really strange is going on. fmt cannot be NULL... Regards Jörg
Open problem with WAPPush routing
Hi Aarno, some time ago we discussed the problems with routing PAP-requests through IPv4 or SMS bearers. Do you have a proper fix or should I provide a band aid? Regards Jörg
Question regarding charset_processing in smsbox.c
Hi List, I'm trying to find my way through this function. Somehow this looks broken to me: If we request that the final SMS is in GSM 7bit encoding, than this function can return inconsistent results: if the body is already in ISO-8859-1, than the resulting body will be in ISO-8859-1 as well (no transformation). If the original body is in something else, than the code will transform it into UTF-8 and return this. There used to be a transformation to ISO-8859-1, but this is currently commented out. Why? Regards Jörg
RE: Kannel and http://wap.yahoo.de
Hi Richard, glad you are still reading this list! Anyway, I think the current Kannel behaviour is correct. I contacted Yahoo! Germany and it turned out to be a problem in their configuration. They fixed it and everything is fine now. Regards Jörg -Original Message- From: Richard Braakman To: [EMAIL PROTECTED] Sent: 12/10/01 11:45 AM Subject: Re: Kannel and http://wap.yahoo.de On Fri, Dec 07, 2001 at 01:12:22PM +0100, Jörg Pommnitz wrote: Kannel has trouble to reach the URL mentioned in the Subject. The first culprit is, that in wap-appl.c the follow parameter to http_start_request is zero. This way Kannel does not follow redirects. Is there any reason not to change this to 1? There is. The client is supposed to follow redirects. If the gateway does it, then the client will have inaccurate information about what the document url is, and will then process relative urls wrongly. What Kannel should do is send the redirect reply back to the client, appropriately encoded. Is it doing this? Richard Braakman
RE: Heads up: SSL client code to verify SSL server certificates
Sorry if I stepped on some toes. I did not consider the changes to be THAT intrusive. They do not change the structure of the code, they just add a new feature. I took care not to change the behaviour of the system when the new configuration option is not set. I'm willing to back the changes out if you oppose them. Do you? Regards Jörg
Kannel and http://wap.yahoo.de
Hi List, Kannel has trouble to reach the URL mentioned in the Subject. The first culprit is, that in wap-appl.c the follow parameter to http_start_request is zero. This way Kannel does not follow redirects. Is there any reason not to change this to 1? Even with this change in place it still fails, but at least it fails in the same way the Nokia toolkit does when trying to reach the site through HTTP. Regards Jörg
RE: Heads up: SSL client code to verify SSL server certificates
I just commited a fix for this problem. The code was incorrect in multiple ways: 1. The SSL error queue for the thread might not have been empty, so incorrect error codes might have been handled. FIX: call ERR_clear_error() before calling SSL_connect 2. SSL_ERROR_WANT_READ and SSL_ERROR_WANT_WRITE was not handled at all. FIX: I overcame this problem by making the socket blocking while calling SSL_connect. This should not be a problem since this function calls conn_open_tcp which might block, too. 3. In case of an error conn_destroy might have been called with a half initialized Connection. This might cause a crash when the ssl_mutex was still NULL. FIX: make sure the mutex is created before any error handling. I suspect 1.) might be true for other SSL I/O calls as well. This should be audited. Regards Jörg -Original Message- From: Jörg Pommnitz To: 'Stipe Tolj ' Cc: ''[EMAIL PROTECTED]' ' Sent: 12/7/01 12:07 PM Subject: RE: Heads up: SSL client code to verify SSL server certificates Thanks, however I just discovered some misbehaviour that I'm unsure whom to blame for: If a certificate gets rejected than this currently not detected in Connection *conn_open_ssl(Octstr *host, int port, Octstr *certkeyfile, Octstr *our_host) and I don't understand why. HTTP requests over a SSL connection later fail when they try to write something. I suspect this never came up until now because the SSL negotiations always succeeded. Any ideas? Regards Jörg
RE: charset_init()
-Original Message- From: Tuomas Luttinen To: Kannel Development List (E-mail) Sent: 12/7/01 2:57 PM Subject: Re: charset_init() PS. What has happened to the checks, they all seem to fail now? They report a failure because they do not expect the SSL debug output. Maybe this should be removed. Regards Jörg
More than one root CA for Kannel as SSL client
Hi List, the documentation says Using SSL client support To use the client support please use the following configuration directive within the core group group = core ... ssl-client-certkey-file = filename Now you are able to use https:// scheme URLs within your WML decks and SMS services. Well, I suspect that the ssl-client-certkey is actually a root CA certificate. Am I right or is this a client certificate to be presented to the server to prove the client identity? If it is a root certificate, just one is of little use. Mozilla comes with 98 root certificates and growing. How do I use more than one root certificate? Regards Jörg
Heads up: new configure option for emi2
From the updated Userguide: idle-timeout - number (seconds) If this option is set to a value larger than 0, then the connection will be closed after the configured amount of seconds without activity. This option interacts with the keepalive configuration option. If keepalive is smaller than idle-timeout, then the connection will never be idle and those this option has no effect. If keepalive is larger than idle-timeout, than keepalive reopens the connection. This allows one to poll for pending mobile originated Short Messages at the SMSC. In my limited testing everything worked fine. If nobody objects I'm going to commit my changes soon. Regards Jörg
RE: Heads up: new configure option for emi2 idle-timeout
The code is now in CVS. Please look at it and test it. All features work fine for me. Regards Jörg -Original Message- From: Jörg Pommnitz To: '[EMAIL PROTECTED]' Sent: 12/5/01 10:38 AM Subject: Heads up: new configure option for emi2 From the updated Userguide: idle-timeout - number (seconds) If this option is set to a value larger than 0, then the connection will be closed after the configured amount of seconds without activity. This option interacts with the keepalive configuration option. If keepalive is smaller than idle-timeout, then the connection will never be idle and those this option has no effect. If keepalive is larger than idle-timeout, than keepalive reopens the connection. This allows one to poll for pending mobile originated Short Messages at the SMSC. In my limited testing everything worked fine. If nobody objects I'm going to commit my changes soon. Regards Jörg
Found and fixed SSL locking bug
Hi List, I just found and fixed a long standing bug in SSL locking. The problem was that both, the client and the server context used the same SSL locking callback function. Unfortunately this function referenced only one set of mutexes. The fresh and shiny server mutexes never got used. On shutdown the SSL server code then tried to access the already released client SSL mutexes which caused the crash on shutdown. The fix is obvious: use a separate callback for the server context. This is implemented and in CVS. Regards Jörg
Heads up: Proposed changes to smsc_emi2.c
Hi List, while trying to find my way through the emi2 code I ended up rewriting static void emi2_send_loop(SMSCConn *conn, Connection *server) I will not commit these changes without at least silent consent from the EMI2 hackers here on the list. Please have a look and provide me with some kind of feedback. The code received cursory testing, but some features (DLR, keep-alive) were not tested at all. Regards Jörg smsc_emi2.c Description: Binary data
RE: Heads up: Proposed changes to smsc_emi2.c
No functional changes, yet. As I wrote some time ago we (Condat) need a way to use EMI2 over ISDN dialup connections. Currently this fails because the EMI2 code keeps the ISDN connection up all the time. My proposed current changes make the code more readable for me and hopefully others. They prepare the stage for the next step: introducing a configure option idle-timeout that allows one to specify an idle timeout for the SMSC connection. Regards Jörg -Ursprüngliche Nachricht- Von: Andreas Fink [mailto:[EMAIL PROTECTED]] Gesendet am: Montag, 3. Dezember 2001 13:52 An: Jörg Pommnitz Betreff: Re: Heads up: Proposed changes to smsc_emi2.c what did you really change in it? -- Andreas Fink Fink-Consulting -- Tel: +41-61-6932730 Fax: +41-61-6932729 Mobile: +41-79-2457333 Address: A. Fink, Schwarzwaldallee 16, 4058 Basel, Switzerland E-Mail: [EMAIL PROTECTED] Homepage: http://www.finkconsulting.com -- Something urgent? Try http://www.smsrelay.com/ Nickname afink
WAPPushPPG: Fix got reverted
Hi Aarno, going from version 1.27 to 1.28 you backed out my previous fix for freeing an uninitialized username. This happens when a trusted PI is configured. Was this accidently or did you dislike the fix for some reason? Regards Jörg
EMI2: Feature enhancements
Hi List, I'm just staring at the emi2 sources to figure out how to best add features we need. Here is our situation: We have an EMI/IP account with a GSM operator here in Germany. To access the SMSC we use a dial-up ISDN line, this means we have to make a long distance call every time we want to send some messages. EMI2 does not handle this situation well: 1. It always keeps the TCP connection open, even if there is no need. (high charges for the long distance call) 2. It does never close the TCP connection. This leads to a second problem unrelated to 1): EMI sessions are bound to the TCP connections. If the ISDN connection breaks down for some reason (e.g. idle timeout) the TCP connection is not terminated properly, so the EMI session stays active until the TCP connection times out on the SMSC side. During this time new connection attempts are refused because we exceed our session limit. Since Kannel treats every refused login request as fatal, no future connection attempts are possible without a bearerbox restart. What do I want? 1. A configuration option that allows me to specify how long the TCP connection is allowed to be idle. 2. Graceful handling of temporary login failures. I'd like some input on this from the EMI2 hackers here on the list. Regards Jörg
(no subject)
Second try, this time the attachment is compressed with gzip. Hi List, while trying to find my way through the emi2 code I ended up rewriting static void emi2_send_loop(SMSCConn *conn, Connection *server) I will not commit these changes without at least silent consent from the EMI2 hackers here on the list. Please have a look and provide me with some kind of feedback. The code received cursory testing, but some features (DLR, keep-alive) were not tested at all. Regards Jörg smsc_emi2.c.gz Description: Binary data
Heads up: EMI2 hackers please read the (no subject) mail
Those interested in EMI2, please read the mail with the Subject (no subject). Regards Jörg
RE: recent WAPPush with IPv4 bearer crashes
Hi Aarno, I think I know what's going on. The key is the following comment: /* * We support networks using IP as a bearer and GSM using SMS as bearer, so we * must reject others. Default bearer is IP, it is (currently) not-SMS. After * the check we change meaning of the bearer_required-attribute: it will tell * do we use WAP over SMS. */ I think this attribute is never changed. With a QoS element in the PAP request and bearer-required and network-required set to true, Kannel will always send a SMS. Do you aggree? Regards Jörg -Original Message- From: Aarno Syvänen To: Jörg Pommnitz Sent: 11/29/01 9:30 AM Subject: Re: recent WAPPush with IPv4 bearer crashes Jörg Pommnitz wrote: Aarno Syvänen [mailto:[EMAIL PROTECTED]] wrote: quality-of-service bearer=Any bearer-required=true delivery-method=unconfirmed network=Any network-required=true priority=medium/ If bearer and/or network are Any, PPG should use some reasonable bearer and/or network. It should depend on address, being either GSM+SMS or GSM+CSD. I modified my code to set bearer=CSD and network=GSM for IPv4 addresses in the quality-of-service tag. It still tries to send a SMS to an IP address. I will investigate this, too. Aarno
RE: recent WAPPush with IPv4 bearer crashes
OK, a slight correction: select_bearer_network correctly modifies bearer/network_required. Unfortunately this is not what Kannel actually uses. It uses the old copy of the data stored in the PPGPushMachine. Regards Jörg -Original Message- From: Jörg Pommnitz To: 'Aarno Syvänen '; Jörg Pommnitz Cc: '[EMAIL PROTECTED]' Sent: 11/29/01 10:43 AM Subject: RE: recent WAPPush with IPv4 bearer crashes Hi Aarno, I think I know what's going on. The key is the following comment: /* * We support networks using IP as a bearer and GSM using SMS as bearer, so we * must reject others. Default bearer is IP, it is (currently) not-SMS. After * the check we change meaning of the bearer_required-attribute: it will tell * do we use WAP over SMS. */ I think this attribute is never changed. With a QoS element in the PAP request and bearer-required and network-required set to true, Kannel will always send a SMS. Do you aggree? Regards Jörg -Original Message- From: Aarno Syvänen To: Jörg Pommnitz Sent: 11/29/01 9:30 AM Subject: Re: recent WAPPush with IPv4 bearer crashes Jörg Pommnitz wrote: Aarno Syvänen [mailto:[EMAIL PROTECTED]] wrote: quality-of-service bearer=Any bearer-required=true delivery-method=unconfirmed network=Any network-required=true priority=medium/ If bearer and/or network are Any, PPG should use some reasonable bearer and/or network. It should depend on address, being either GSM+SMS or GSM+CSD. I modified my code to set bearer=CSD and network=GSM for IPv4 addresses in the quality-of-service tag. It still tries to send a SMS to an IP address. I will investigate this, too. Aarno
AW: recent WAPPush with IPv4 bearer crashes
I don't have a strong opinion in this matter, so I won't argue. I would suggest, however, to make the communication of the bearer more explicit. The current overloading of the bearer/network_required fields seems hackish to me. Regards Jörg -Ursprüngliche Nachricht- Von: Aarno Syvänen [mailto:[EMAIL PROTECTED]] Gesendet am: Donnerstag, 29. November 2001 12:11 An: Jörg Pommnitz Cc: '''[EMAIL PROTECTED]' ' ' Betreff: Re: recent WAPPush with IPv4 bearer crashes Hi Jörg, Jörg Pommnitz wrote: I think the bearer selection needs some thoughts. IMHO making this decision in wap_push_ppg is a slight layering violation (debatable). IMHO this decision should be made in dispatch_datagram(WAPEvent *dgram) in wapbox.c. One problem: at this point we lost the information about the type of the address. I think this should be made part of the WAPEvent. What do you think? I agree, in principle. However, PPG updates PAP attribute after it has found an unssupported bearer. (And PI can query it if it wants.) I think it is better to have all functions manipulating PAP attribute in same module (data cohesion of modules is one architectural principles of Kannel.) Aarno
AW: bearerbox - smsbox communication ???
This should get you started: http://liw.iki.fi/liw/texts/cpp-trick.html Regards Jörg -Ursprüngliche Nachricht- Von: Veljo Otsason [mailto:[EMAIL PROTECTED]] Gesendet am: Montag, 26. November 2001 13:12 An: [EMAIL PROTECTED] Betreff: bearerbox - smsbox communication ??? hello! does anybody have description of bearerbox and smsbox communication protocol. i want to write my own smsbox for a specific application, but i could'nt find the description. please help me if you can.. yours, Veljo
AW: AW: SEGV on program termination
Do you mean that it happens *everytime* you use *all* of these programs ? Aarno Right. On RedHat-7.1 and Suse 6.4 Regards Jörg
AW: Kannel PPG seems to insist on qos element
I have to qualify this message: IPv4 works fine without the qos tag, but PLMN gives: 2001-11-15 15:41:14 [11] DEBUG: HTTP: Creating HTTPClient for `10.1.25.120'. 2001-11-15 15:41:14 [13] INFO: PPG: Accept request /cgi-bin/wap-push.cgi from 10.1.25.120 2001-11-15 15:41:14 [13] DEBUG: PPG: Content-Type is multipart/related; boundary=332daf4c:ea30a33dc8:-714c; type=application/xml; charset=UTF-8 2001-11-15 15:41:14 [13] DEBUG: PPG: http_read_thread: pap multipart accepted 2001-11-15 15:41:14 [13] INFO: client address was +491718997592, accepted 2001-11-15 15:41:14 [13] DEBUG: PAP COMPILER: doing semantic analysis for address type a phone number 2001-11-15 15:41:14 [13] DEBUG: PAP COMPILER: network or bearer does not accept PLMN address 2001-11-15 15:41:14 [13] WARNING: wrong type of address for requested bearer 2001-11-15 15:41:14 [13] DEBUG: PPG: send_bad_message_response: telling pi 2001-11-15 15:41:14 [13] DEBUG: HTTP: Resetting HTTPClient for `10.1.25.120'. 2001-11-15 15:41:14 [13] WARNING: PPG: pap control entity erroneous, the request unacceptable 2001-11-15 15:41:19 [10] DEBUG: HTTP: Destroying HTTPClient area 0x81e4b68. 2001-11-15 15:41:19 [10] DEBUG: HTTP: Destroying HTTPClient for `10.1.25.120'. it seems bearer defaults to WSP instead of something sensible for the given address type. Regards Jörg -Ursprüngliche Nachricht- Von: Jörg Pommnitz [mailto:[EMAIL PROTECTED]] Gesendet am: Donnerstag, 15. November 2001 16:44 An: '[EMAIL PROTECTED]' Betreff: Kannel PPG seems to insist on qos element Hi Aarno, it seems the PPG does not work without the quality-of-service tag and network related attributes. According to the DTD this tag is optional. Is this a bug? Regards Jörg
SEGV on program termination
Hi List, am I the onliest one who sees regular crashes on program termination (all the boxes)? They are hard to track down (gdb is useless, no core dumps) so I'd like to hear other ideas. Regards Joerg
AT2: Timestamp 100 years off?
Hi List, the following code from at2 looks suspiciously out of date: /* get the timestamp */ mtime.year = octstr_get_char(pdu, pos) + 1900; pos++; mtime.month = octstr_get_char(pdu, pos); pos++; mtime.day= octstr_get_char(pdu, pos); pos++; mtime.hour = octstr_get_char(pdu, pos); pos++; mtime.minute = octstr_get_char(pdu, pos); pos++; mtime.second = octstr_get_char(pdu, pos); pos++; Currently this assigns mtime.year the value 1901. This seems wrong to me. Regards Jörg
AW: AW: Kannel PPG, PI and character encoding
What do you do with Content-Encoding header ? If you change encoding, you must change the header, too. Aarno Good question. It should be changed to binary, shouldn't it? Regards Jörg
RE: Kannel PPG, PI and character encoding
Good question. It should be changed to binary, shouldn't it? I think so, too. Aarno The fix is in CVS now. Regards Jörg
AW: configure Makefile changes... (MacOS X) PS
How about adding a gw_ prefix to all the Kannel gwlib functions? Regards Jörg -Ursprüngliche Nachricht- Von: Andreas Fink [mailto:[EMAIL PROTECTED]] Gesendet am: Freitag, 2. November 2001 12:34 An: [EMAIL PROTECTED] Betreff: configure Makefile changes... (MacOS X) PS for got to say that the functions semaphore_create, semaphore_destroy do already exist in the pthread library of MacOS X. So there is a conflict there too while linking.
AW: Kannel developer meeting
If we decide to meet in Berlin, Jan de Meer, our standard body observer, will be happy to talk about EMS/MMS and current WAP developments. Regards Jörg I think Paul has a point here. We must first agree meeting schedule. I hope you can suffer a presentation of Push Proxy Gateway by me. aarno
AW: Does Kannel work with PDA
Do you want to run Kannel on a PDA? This might be possible with embedded Linux, but what's the point? -Ursprüngliche Nachricht- Von: guru [mailto:[EMAIL PROTECTED]] Gesendet am: Mittwoch, 24. Oktober 2001 09:41 An: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Betreff: Does Kannel work with PDA Hi List, I wanted to know whether Kannel can work with PDA's. Any pointers will be appreciated. regards Guru
AW: Does Kannel work with PDA
Depends. You can easily use most Palm and WinCE devices with a mobile phone with IrCOM. Aditionally you can use PCCard GSM modems with most WinCE machines. The MSISDN depends on the SIM of the device you use for network access. -Ursprüngliche Nachricht- Von: guru [mailto:[EMAIL PROTECTED]] Gesendet am: Mittwoch, 24. Oktober 2001 10:58 An: [EMAIL PROTECTED] Cc: Jörg Pommnitz Betreff: RE: Does Kannel work with PDA I meant can kannel serve WAP request from PDA. The reason being how does Kannel identify a PDA? Does PDA also have something similar to MSSISDN? Can you tell me as to how a WAP request from a PDA is routed to Kannel? regards Guru
AW: PANIC: Too many concurrent allocations
It's either a bug in Kannel (memory leak) or a heavily stressed system running in debug limits. If it's not a memory leak, you can prevent the emergency shutdown by disabling debug malloc while calling configure. Regards Jörg -Ursprüngliche Nachricht- Von: Tim Hammonds [mailto:[EMAIL PROTECTED]] Gesendet am: Mittwoch, 24. Oktober 2001 17:58 An: [EMAIL PROTECTED] Betreff: PANIC: Too many concurrent allocations I am using a cvs version of Kannel as an SMS Gateway to a UCP/EMI SMSC. I was originally having throughput problems with Kannel V1.1.5, as the SMSC was ignoring messages sent if they received more than 5 a second. My earlier posting to this list resulted in the suggestion that I use the CVS version as it has flow control built in and the stop-and-wait protocol would sort things out. By setting flow-control to 1 in the config, Kannel now waits for the ACK from the SMSC and the maximum throughput is achieved. Great stuff. My next problems is that after submitting batches of (over 2000) messages to Kannel (using the http interface) I invariably get the message PANIC: Too many concurrent allocations in the log file followed by the Kannel processes dying and the remainder of the messages in the batch being lost. Is this a Kannel issue, Linux/Kernel issue, hardware issue, network issue or SMSC issue? Have any of you kind people got a suggestion as to what causes this problem and how I can overcome it, as I need to use Kannel in a live system! Regards, Tim.
AW: Kannel PPG, PI and character encoding
I just read RFC2387: it uses base64 as transfer encoding for application/octet-stream data. While there is a void octstr_base64_to_binary(Octstr *ostr) function in the Kannel source tree it seems not to be used in the PPG code. Aarno, what's your opinion? Regards Jörg -Ursprüngliche Nachricht- Von: Jörg Pommnitz [mailto:[EMAIL PROTECTED]] Gesendet am: Montag, 22. Oktober 2001 14:13 An: [EMAIL PROTECTED] Betreff: Kannel PPG, PI and character encoding Hi List, I have a question about the character encoding to be used for documents (PAP/SI/SL) to be sent as part of a PAP request. Normally character encoding is not an issue with XML files, both ISO-8859 or UTF-8 are OK. Unfortunately the WAP Push specification adds MIME to the mix: SMTP as one of the oldest Internet Protocols is not considered to be 8 bit clean. That's why unclean content is normally wrapped either in quoted-printable or BASE64 encoding. I'm not sure what to do with multipart MIME messages to be sent over a HTTP POST request. In this case eight bit cleanliness is not an issue yet most MIME libraries (in my case JavaMail) still play it safe and insist on additional layers of encoding. So here is my question: What should I do? The WAP Push spec seems not to address this issue (the examples do not even include an encoding= statement in their DOCTYPE)... Regards Jörg
RE: Still WAP Push
-Original Message- From: Aarno Syvänen To: Jörg Pommnitz Cc: ''[EMAIL PROTECTED] ' ' Sent: 10/18/01 9:40 AM Subject: Re: Still WAP Push What content type did you use ? You should set it wml. (Default is si.) And yes, I will add these things to the useguide. Aarno All of them :-). A si works as expected, but a the emulator does not display a pushed WML deck. It's hard to decide whether the problem is in Kannel or whether this is what the Nokia Toolkit just does in such a case. I know the R520m supports WAP Push. Does anybody know about any other actual phones with this feature out there? Regards Jörg
AW: Siemens M20 and Kannel
Von: Ronan Derby [mailto:[EMAIL PROTECTED]] Does it matter if the smsbox is or isn't running? bearerbox is required by smsbox. You cannot start smsbox without a running bearerbox. Regards Jörg
Still WAP Push
Hi List, I'm trying to get WAP Push to work with the Nokia Mobile Internet Toolkit 3.0. My setup is the one Aarno suggested: * todays (Oct 17th) CVS Kannel on RedHat Linux * the Nokia Toolkit running on NT40 in a VMWare session I'm trying to send the attached messages with the test_ppg program. There is no suspictious message on the Kannel side, it just hangs waiting for something I don't know. wapbox says: 2001-10-17 12:05:24 [0] INFO: 2001-10-17 12:05:24 [0] INFO: Kannel wapbox version cvs starting up. 2001-10-17 12:05:24 [0] DEBUG: Started thread 1 (wap/wsp_session.c:main_thread) 2001-10-17 12:05:24 [0] DEBUG: Started thread 2 (wap/wsp_unit.c:main_thread) 2001-10-17 12:05:24 [0] DEBUG: Started thread 3 (wap/wsp_push_client.c:main_thread) 2001-10-17 12:05:24 [0] DEBUG: Started thread 4 (wap/timers.c:watch_timers) 2001-10-17 12:05:24 [0] DEBUG: Started thread 5 (wap/wtp_init.c:main_thread) 2001-10-17 12:05:24 [0] DEBUG: Started thread 6 (wap/wtp_resp.c:main_thread) 2001-10-17 12:05:24 [0] DEBUG: Started thread 7 (gw/wap-appl.c:main_thread) 2001-10-17 12:05:24 [0] DEBUG: Started thread 8 (gw/wap-appl.c:return_replies_thread) 2001-10-17 12:05:24 [0] DEBUG: Started thread 9 (gw/wap_push_ota.c:main_thread) 2001-10-17 12:05:24 [0] DEBUG: HTTP: Opening server at port 8080. 2001-10-17 12:05:24 [0] DEBUG: Started thread 10 (gwlib/fdset.c:poller) 2001-10-17 12:05:24 [0] DEBUG: Started thread 11 (gwlib/http.c:server_thread) 2001-10-17 12:05:24 [0] DEBUG: Started thread 12 (gw/wap_push_ppg.c:ota_read_thread) 2001-10-17 12:05:24 [0] DEBUG: Started thread 13 (gw/wap_push_ppg.c:http_read_thread) 2001-10-17 12:05:24 [0] DEBUG: Add encoding for WIN-1257 2001-10-17 12:05:24 [0] DEBUG: Add encoding for WINDOWS-1257 2001-10-17 12:05:24 [0] DEBUG: Add encoding for WINDOWS-1251 2001-10-17 12:05:24 [0] DEBUG: Add encoding for WIN-1251 2001-10-17 12:05:24 [0] DEBUG: Add encoding for WINDOWS-1253 2001-10-17 12:05:24 [0] INFO: Connected to bearerbox at localhost port 13002. 2001-10-17 12:05:24 [0] DEBUG: Started thread 14 (gw/heartbeat.c:heartbeat_thread) 2001-10-17 12:05:36 [11] DEBUG: HTTP: Creating HTTPClient for `127.0.0.1'. 2001-10-17 12:05:36 [13] INFO: PPG: Accept request /cgi-bin/wap-push.cgi from 127.0.0.1 2001-10-17 12:05:36 [13] DEBUG: PPG: http_read_thread: pap multipart accepted and test_ppg claims: [jpo@jpo test]$ ./test_ppg http://localhost:8080/cgi-bin/wap-push.cgi?password=condatusername=condat; ~/Push/pushdeck.wml ~/Push/pap.xml 2001-10-17 12:05:35 [0] DEBUG: Started thread 1 (test/test_ppg.c:push_thread) 2001-10-17 12:05:35 [1] DEBUG: we have push content 2001-10-17 12:05:35 [1] DEBUG: Octet string at 0x819e468: 2001-10-17 12:05:35 [1] DEBUG: len: 888 2001-10-17 12:05:35 [1] DEBUG: size: 889 2001-10-17 12:05:35 [1] DEBUG: immutable: 0 2001-10-17 12:05:35 [1] DEBUG: data: 0d 0a 2d 2d 61 73 64 6c ..--asdl 2001-10-17 12:05:35 [1] DEBUG: data: 66 6b 6a 69 75 72 77 67 fkjiurwg 2001-10-17 12:05:35 [1] DEBUG: data: 68 61 73 66 0d 0a 43 6f hasf..Co 2001-10-17 12:05:35 [1] DEBUG: data: 6e 74 65 6e 74 2d 54 79 ntent-Ty 2001-10-17 12:05:35 [1] DEBUG: data: 70 65 3a 20 61 70 70 6c pe: appl 2001-10-17 12:05:35 [1] DEBUG: data: 69 63 61 74 69 6f 6e 2f ication/ 2001-10-17 12:05:35 [1] DEBUG: data: 78 6d 6c 0d 0a 3c 3f 78 xml..?x 2001-10-17 12:05:35 [1] DEBUG: data: 6d 6c 20 76 65 72 73 69 ml versi 2001-10-17 12:05:35 [1] DEBUG: data: 6f 6e 3d 22 31 2e 30 22 on=1.0 2001-10-17 12:05:35 [1] DEBUG: data: 3f 3e 0d 0a 3c 21 44 4f ?..!DO 2001-10-17 12:05:35 [1] DEBUG: data: 43 54 59 50 45 20 70 61 CTYPE pa 2001-10-17 12:05:35 [1] DEBUG: data: 70 20 50 55 42 4c 49 43 p PUBLIC 2001-10-17 12:05:35 [1] DEBUG: data: 20 22 2d 2f 2f 57 41 50-//WAP 2001-10-17 12:05:35 [1] DEBUG: data: 46 4f 52 55 4d 2f 2f 44 FORUM//D 2001-10-17 12:05:35 [1] DEBUG: data: 54 44 20 50 41 50 2f 2f TD PAP// 2001-10-17 12:05:35 [1] DEBUG: data: 45 4e 22 0d 0a 20 20 20 EN.. 2001-10-17 12:05:35 [1] DEBUG: data: 20 20 20 20 20 20 20 20 2001-10-17 12:05:35 [1] DEBUG: data: 20 20 20 20 20 20 20 20 2001-10-17 12:05:35 [1] DEBUG: data: 20 20 20 20 20 20 20 20 2001-10-17 12:05:35 [1] DEBUG: data: 20 20 22 68 74 74 70 3a http: 2001-10-17 12:05:35 [1] DEBUG: data: 2f 2f 77 77 77 2e 77 61 //www.wa 2001-10-17 12:05:35 [1] DEBUG: data: 70 66 6f 72 75 6d 2e 6f pforum.o 2001-10-17 12:05:35 [1] DEBUG: data: 72 67 2f 44 54 44 2f 70 rg/DTD/p 2001-10-17 12:05:35 [1] DEBUG: data: 61 70 5f 31 2e 30 2e 64 ap_1.0.d 2001-10-17 12:05:35 [1] DEBUG: data: 74 64 22 3e 0d 0a 3c 70 td..p 2001-10-17 12:05:35 [1] DEBUG: data: 61 70 3e 0d 0a 09 3c 70 ap...p 2001-10-17 12:05:35 [1] DEBUG: data: 75 73 68 2d 6d 65 73 73 ush-mess 2001-10-17 12:05:35 [1] DEBUG: data: 61 67 65 20 70 75 73 68 age push 2001-10-17 12:05:35 [1] DEBUG: data: 2d 69 64 3d 22 39 66 6a -id=9fj 2001-10-17 12:05:35
Kannel developer meeting
Hello Developers, in response to the suggestion made by Andreas Fink Condat AG would be willing to host the next Kannel developer meeting, too. Our premises in Berlin/Germany could comfortably accommodate up to 20 people. With WapIT gone we need some way to make a decision. In my opinion the process should look like this: 1. Fix a date 2. Get a head count of participants 3. depending on the outcome of the steps 1 and 2 find a suitable location 4. Take a vote if step 3 yields more than one possibility. What do you think? Regards Jörg on behalf of Business Unit Wireless Applications Condat AG Berlin
Testing WAP Push with Nokia-Toolkit
Hi List, I think I remember that Aarno tested the Kannel PPG implementation with the Nokia WAP Toolkit. Am I dreaming? If not, how does one do this (obviously I cannot send a SM)? Thanks Joerg
AW: Concat with UDH?
Do you mean the UDH is more than one SM? I don't think that's valid... -Ursprüngliche Nachricht- Von: Steve Rapaport [mailto:[EMAIL PROTECTED]] Gesendet am: Montag, 15. Oktober 2001 15:33 An: [EMAIL PROTECTED] Betreff: Concat with UDH? Has anyone successfully sent a binary SMS with UDH that takes *more than one SMS*, using Kannel's HTTP push interface? I promise eternal gratitude for the working sample HTTP calls. Best, Steve
AW: sms message ID
Your basic SMS message is just unstructured text. Any clever things you want to do with this has to live within these limits. WAP was/is supposed to be used for more advanced services. Regards Jörg -Ursprüngliche Nachricht- Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Gesendet am: Mittwoch, 10. Oktober 2001 11:08 An: [EMAIL PROTECTED] Betreff: sms message ID Hi. Once in a while, somebody asks on this list if it is possible to put some sort of ID in an SMS, so that when people reply to it, the reply can be recognized as a reply to that message. I don't remember seing any positive replys to that. So, I wonder - can one do something like that with Reply-Path or UDH ? Is there some sort of 'optional msg ID UDH part ? If there was, it would of course eat a bit of the available msg space. Also, there is some sort of msg ref number, but it is only 8 bit, and I assume it is not connected to replies ?
AW: rpm libxml problem
i am using Redhat 6.2. anyone knows how to fix? thanks! Yes. Upgrade RPM. And no, this is in no way related to Kannel. Regards Jörg
AW: Sms answer to a ring call
-Ursprüngliche Nachricht- Von: Andrea Viscovich [mailto:[EMAIL PROTECTED]] Gesendet am: Freitag, 24. August 2001 11:56 An: [EMAIL PROTECTED] Betreff: Re: Sms answer to a ring call I completely understand that you do not want to do this. What you want to do is reject the incoming call. I don't know the AT command to do this. I tried with ATH and it works. OK. In this case there is an alternative that at least two people (me and Hubert) think is much better than messing with smsc_at: a small external program that handles the Well an external program that does it is always an alternative solution isn't it? Not always, but quite often. By the way don't forget the other solution is easier Under Unix enviroment, but not so easy under Windoze. Why not? It should work equally well under Windows. Regards Andrea
AW: Sms answer to a ring call
Why not? It should work equally well under Windows. You should try to compile mgetty, and then how can you run the script? While mgetty sounds like a sensible solution, I was not strictly talking about it. A simple program (C, Java or whatever) that opens a serial port, initializes the modem, waits for RINGs and forwards the caller id through HTTP to Kannel is enough. Sounds like just a few hours hacking. Regards Jörg Andrea
AW: Sms answer to a ring call
Uhm, so you would have Kannel and another program to initialise the same port, I don't know if it's possible. Andrea No, doing both, handling SMS and incoming calls over the same modem would require that smsc_at does it all. That's why I jumped to my current proposal only when you told us that you want to handle SMS over a different channel. Regards Jörg
AW: Unicode characters
Of course it does. The WAP-1.x specification requires this. You have to use UTF-8 encoding for your WML pages. Regards Jörg -Ursprüngliche Nachricht- Von: Venugopal Panchamukhi [mailto:[EMAIL PROTECTED]] Gesendet am: Donnerstag, 23. August 2001 10:20 An: [EMAIL PROTECTED] Betreff: Unicode characters Hi, Does Kannel support Unicode characters - if so, how to test them. Regards, Venu -- Venugopal Panchamukhi Mobile# +358-(0)9-4110 1675 E-Mail: [EMAIL PROTECTED] [EMAIL PROTECTED]
AW: Sms answer to a ring call
-Ursprüngliche Nachricht- Von: Hubert Kubik [mailto:[EMAIL PROTECTED]] Gesendet am: Mittwoch, 22. August 2001 10:26 An: [EMAIL PROTECTED] Betreff: ODP: Sms answer to a ring call There is a standard gsm AT command set, you can find it somewhere. I got AT command set description for siemens m20 GSM modem (www.siemens.de) I don't think this can help, I would rather suggest hacking some dial-in software, like mgetty. Maybe mgetty can be ported to win2000. Maybe there is any other open source dial-in software for win2000. I feel the same way, but my understanding is that Andrea want's to use the same modem for SMS and the incoming call. In this case sharing the line is hard (impossible??). Regards Joerg
AW: Sms answer to a ring call
OK, in this case my suggestion is to leave Kannel alone and write a tiny program that does what you want. You can use smsc_at for inspiration, but maybe it's easier to just compile mgetty inside the Cygnus environment. Putting this feature into the smsc_at just doesn't make sense. smsc_at has a well defined task and adding complexity to make it do something that could easily and cleaner done by an outside program is just a bad architecture that will come back and bite you. Regards Joerg -Ursprüngliche Nachricht- Von: Andrea Viscovich [mailto:[EMAIL PROTECTED]] Gesendet am: Mittwoch, 22. August 2001 11:31 An: [EMAIL PROTECTED] Betreff: Re: Sms answer to a ring call I feel the same way, but my understanding is that Andrea want's to use the same modem for SMS and the incoming call. In this case sharing the line is hard (impossible??). Well, as I may send sms by other connections, I just would like to have bearerbox listen to incoming ring, and then habe smsbox call an url passing the caller id, as actually is done when receiving an sms. Andrea
AW: Start marker damage
Some kind of memory overrun. To fix it you have to figure out what went wrong. This is just a symptom. Regards Jörg -Ursprüngliche Nachricht- Von: Matt Flax [mailto:[EMAIL PROTECTED]] Gesendet am: Mittwoch, 22. August 2001 11:51 An: gatewayZgalore Betreff: Start marker damage Could someone please explainthe following error ? and perhaps suggest a way to fix it ? ... 2001-08-22 09:48:19 [8] DEBUG: data: 41 67 65 6e 74 3a 20 4b Agent: K 2001-08-22 09:48:19 [8] DEBUG: data: 61 6e 6e 65 6c 20 63 76 annel cv 2001-08-22 09:48:19 [8] DEBUG: data: 73 0d 0a 0d 0a s 2001-08-22 09:48:19 [8] DEBUG: Octet string dump ends. 2001-08-22 09:48:19 [7] DEBUG: HTTP: Status line: HTTP/1.1 200 OK 2001-08-22 09:48:19 [5] ERROR: Start marker was damaged for area 0x819e4c8 2001-08-22 09:48:19 [5] ERROR: Could not find area information. 2001-08-22 09:48:19 [5] PANIC: gwlib/octstr.c:2033: seems_valid_real: Assertion `gw_check_is_allocated(ostr)' failed. (Called from gw/smsbox.c:666:url_result_thread.) -- Matt Common computer data descriptions bit licknibble byte
AW: bb_udp and ppp interaction?
PPP has nothing to do with ports. It's enough if your mobile phone knows the port number. Oh, and besides mgetty you need a ppp daemon, too. I suggest you read some appropriate documents (like the Linux PPP-HOWTO). Regards Joerg -Ursprüngliche Nachricht- Von: manish [mailto:[EMAIL PROTECTED]] Gesendet am: Donnerstag, 16. August 2001 12:57 An: [EMAIL PROTECTED] Betreff: bb_udp and ppp interaction? hi, i'm running kannel 1.1.5 on rhlinux 6.2 and very happy with the sms functionality with nokia 7110 but i've been trying for a long time and have not been able to make any wdp requests to the bearerbox. specifically i have not been able to figure out how does the datagram go to the 9200 udp port on which the bearerbox is waiting. the stuff given in the user guide tells about setting up the ppp dial up connection but i don't understand how does the datagram get forwarded to the bearerbox because nowhere are we mentioning anything about port numbers in the ppp setup.all we tell is the bearerbox host ip. i'll be ver grateful to anyone who can guide me how the thing works -from the point the mobile dials in and what happens after ppp has authincated the user. also the 7110 modem needs to be initialized i guess before the mobile can send the ppp request. i tried to check what the mobile was sending by checking the mgetty logs it keeps waiting for an OK ?? is it because the modem is not initialized? i have 7:2345:respawn:/sbin/mgetty ttyS0 -x 6 -D /dev/ttyS0 in my inittab but is that sufficient?i don't think this initializes the modem,does it? thanks manish thanks manish
RE: Kannel CVS and 1.0.3 do not work with some WAP sites
Some more information, a dump of the deck in question (including http headers): 2001-08-16 10:52:38 [8] DEBUG: Headers Content-type = text/vnd.wap.wml 2001-08-16 10:52:38 [8] DEBUG: Headers Connection = Close 2001-08-16 10:52:38 [8] DEBUG: Headers Pragma = no-cache 2001-08-16 10:52:38 [8] DEBUG: ?xml version=1.0? !DOCTYPE wml PUBLIC -//WAPFORUM//DTD WML 1.1//EN http://www.wapforum.org/DTD/wml_1.1.xml;wmlheadmeta http-equiv=Cache-Control content=max-age=0 forua=true//headtemplatedo type=prev label=Prevprev/prev/do/templatecard id=c1 title=Yahoo! Deutschland p align=centerimg src=/img/yicon.wbmp alt=Yahoo!//ppa href=http://oa.europe.yahoo.com/dir/de/index.wml; title=OKY! Verzeichnis/abr/a href=http://oa.europe.yahoo.com/http://mail.yahoo.de/; title=OKY! Mail/abr/a href=http://oa.europe.yahoo.com/mfA5Ens7rN.eL7R9pETM; title=OKMein Yahoo!/abr/a href=http://yeb1.lng.yahoo.com/finance/top?intl=de; title=OKY! Finanzen/abr/a href=http://oa.europe.yahoo.com/de/news/index.wml; title=OKY! Schlagzeilen/abr/a href=http://oa.europe.yahoo.com/de/sport/index.wml; title=OKY! Sport/abr/a href=http://oa.europe.yahoo.com/mfA5Ins7fXCdzHNEGITs; title=OKY! Wetter/abr/a href=http://oa.europe.yahoo.com/de/horo/index.wml; title=OKY! Horoskop/abr/a href=http://oa.europe.yahoo.com/de/mv/index.wml; title=OKY! Kino/abr/a href=http://oa.europe.yahoo.com/mfA5Mns7DUegeeo97bXI; title=OKY! Auktionen/abr/a href=http://oa.europe.yahoo.com/de/wsweek/index.wml; title=OKY! Wap-Site der Woche/abr/a href=http://oa.europe.yahoo.com/mfA5Qns7ewISo2XBlDNM;Y! Messenger/abr/a href=http://oa.europe.yahoo.com/mfA5Uns7a1gAfgtaib5x; title=OKY! Adre#223;buch/abr/a href=http://oa.europe.yahoo.com/mfA5Yns7Jd3C1bJhVTY2; title=OKY! Kalender/abr/a href=http://oa.europe.yahoo.com/mfA5cns7381udFFOfz8O; title=OKY! Bookmarks/abr/a href=#c2 title=OKMehr.../abr//p/cardcard id=c2 title=Yahoo! Deutschland pa href=http://oa.europe.yahoo.com/de/wc.wml; title=OKY! Weltzeituhr/abr/a href=http://oa.europe.yahoo.com/de/tv/index.wml; title=OKY! TV/abr/a href=http://oa.europe.yahoo.com/de/lotto/index.wml; title=OKY! Lotto/abr/a href=http://oa.europe.yahoo.com/mfA5gns7BEfphRMhjFEP; title=OKY! Weltweit/abr/a href=#c1 title=OKZur#252;ck zur Hauptseite/abr//p/card/wml Regards Jörg -Original Message- From: Jörg Pommnitz To: '[EMAIL PROTECTED]' Sent: 8/16/01 12:30 PM Subject: Kannel CVS and 1.0.3 do not work with some WAP sites Hi List, I'm just starting to investigate a strange problem that happens with some WAP sites and the Nokia WAP toolkit 2.x. When I try to visit for instance http://wap.yahoo.de the WAP toolkit fails to display the site. This happens with both, Kannel 1.0.3 and a fresh CVS tree. The detailed error log of the toolkit shows a Java exception: loadNewContent: (http://wap.yahoo.de) null java.lang.NullPointerException at com.nokia.wap.sdk.http.URLCache.isReplyCacheable(Unknown Source) at com.nokia.wap.sdk.http.URLCache.putReply(Unknown Source) at com.nokia.wap.sdk.http.URLloader.load(Unknown Source) at com.nokia.wap.sdk.browser.WMLBrowserImpl$3.run(Unknown Source) at com.nokia.wap.sdk.util.ThreadedOperation.perform(Unknown Source) at com.nokia.wap.sdk.util.ThreadedOperation.access$000(Unknown Source) at com.nokia.wap.sdk.util.ThreadedOperation$1.run(Unknown Source) at java.lang.Thread.run(Unknown Source) My gut feeling (surprise, surprise) is that Kannel encodes some cache control headers different from what the Nokia toolkit expects. I'm going to distill a test case but I'm also interested in other opinions. Thanks in advance Joerg
Kannel CVS and 1.0.3 do not work with some WAP sites
Hi List, I'm just starting to investigate a strange problem that happens with some WAP sites and the Nokia WAP toolkit 2.x. When I try to visit for instance http://wap.yahoo.de the WAP toolkit fails to display the site. This happens with both, Kannel 1.0.3 and a fresh CVS tree. The detailed error log of the toolkit shows a Java exception: loadNewContent: (http://wap.yahoo.de) null java.lang.NullPointerException at com.nokia.wap.sdk.http.URLCache.isReplyCacheable(Unknown Source) at com.nokia.wap.sdk.http.URLCache.putReply(Unknown Source) at com.nokia.wap.sdk.http.URLloader.load(Unknown Source) at com.nokia.wap.sdk.browser.WMLBrowserImpl$3.run(Unknown Source) at com.nokia.wap.sdk.util.ThreadedOperation.perform(Unknown Source) at com.nokia.wap.sdk.util.ThreadedOperation.access$000(Unknown Source) at com.nokia.wap.sdk.util.ThreadedOperation$1.run(Unknown Source) at java.lang.Thread.run(Unknown Source) My gut feeling (surprise, surprise) is that Kannel encodes some cache control headers different from what the Nokia toolkit expects. I'm going to distill a test case but I'm also interested in other opinions. Thanks in advance Joerg
Don't puke!! Was: Kannel CVS and 1.0.3 do not work with some WAP sites
Hi List, I came up with a most ugly work around to make the Nokia WAP Toolkit happy again. All occurences of Pragma: no-cache are replaced by Cache-Control: max-age=0. I stared at the packed HTTP headers Kannel generates and to me they look just fine. That's why my conclusion is that the bug is in the Nokia WAP toolkit. Since I cannot fix the Nokia toolkit I have to work around the problem in Kannel. Lars had a very strong opinion about working around somebody else's bugs in Kannel. I agree with him. That's why I won't commit the hack, but others here on the list might find it useful. Regards Jörg -Original Message- From: Jörg Pommnitz To: Jörg Pommnitz; ''[EMAIL PROTECTED]' ' Sent: 8/16/01 3:26 PM Subject: RE: Kannel CVS and 1.0.3 do not work with some WAP sites It seems the Pragma header is the culprit. Removing this header from the header list makes the Nokia toolkit happy again. I'm still tracking... Regards Jörg -Original Message- From: Jörg Pommnitz To: '[EMAIL PROTECTED]' Sent: 8/16/01 12:57 PM Subject: RE: Kannel CVS and 1.0.3 do not work with some WAP sites Some more information, a dump of the deck in question (including http headers): 2001-08-16 10:52:38 [8] DEBUG: Headers Content-type = text/vnd.wap.wml 2001-08-16 10:52:38 [8] DEBUG: Headers Connection = Close 2001-08-16 10:52:38 [8] DEBUG: Headers Pragma = no-cache pragma-band.diff
RE: keyword on sms-service
I just commited a change that adds the X-Kannel-From header to the HTTP GET requests (before this it was only available in the POST headers). It can be enabled with the send-sender=1 option at the SMS service configuration in question. Regards Jörg -Original Message- From: Stefano Baronio To: Jörg Pommnitz Sent: 7/26/01 7:00 PM Subject: R: keyword on sms-service I read the User Guide many times, but probably too fast. Now I see it. Thanks. Im also interested for the ME phone number. I have a work to do in my university and they ask me for that function. Could you provide me the patch ? Thank you Stefano -Messaggio originale- Da: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]Per conto di Jörg Pommnitz Inviato: giovedì 26 luglio 2001 18.45 A: devel@kannel Oggetto: AW: keyword on sms-service Try %a (for all) BTW: I have a local patch that adds the ME phone number into a X-Kannel header. Anybody interested in this minor addition? It's useful for us... MfG Joerg -Ursprüngliche Nachricht- Von: Stefano Baronio [mailto:[EMAIL PROTECTED]] Gesendet am: Donnerstag, 26. Juli 2001 18:36 An: Tuomas Luttinen; Stefano Baronio Cc: devel@kannel Betreff: R: keyword on sms-service Thanks Thomas, thanks Andrea, but I can't find my mistake. This is the config part for the sms-box and service: group = smsbox bearerbox-host = localhost sendsms-port = 13013 global-sender = SMSC-TORINO #sendsms-chars = 0123456789 +- log-file = /var/log/kannel/smsbox.log log-level = 0 access-log = /var/log/kannel/access.log max-messages=0 #group = sms-service #keyword = nop #text = You asked nothing and I did it! group = sms-service keyword = default url = http://test.domain.com/uview?call=play.Kannelsender=%ptext=%r; # group = sendsms-user username = test password = test faked-sender = +393481234567 Both %s and %r cut the first sms word. I can see this from the smsbox logs. Any idea ? Thank you Stefano Stefano Baronio wrote: hello everybody, I'm trying to set up the java applet in order to receive sms from kannel, but I don't use any keyword in the message. Is there a way to handle all the sms words and send them to the url specified ? Maybe, with a parameter not listed on the docs... I'm using kannel 1.0.3. Do I have to upgrade to devel version ? There is a special keyword default for this; it is used when there is no other keyword that matches. So leave only the keyword default in your configuration file and set it to point to the URL where your applet is running. Something like this: group = sms-service keyword = default url = http://my.applet.machine/Servlet/kludge2?sender=%ptext=%r; -- Tuomas Luttinen Application Developer -- Reach U **
RE: SMSC Driver features
I think this needs some serious thinking about. We have a lot of new requirements for the HTTP interface: 1. non-iso8859-1 character sets 2. the UDH/text/binary problem 3. the DCS value problem Anything else? And please people, make sure that the cure is not worse than the problem. We should DESIGN a solution, not create a temporary hack. Regards Jörg P.S.: Nobody replied to my proposal of always sending Unicode Octstr's to the SMSC drivers. If nobody objects I take this as consent... Regards Joerg -Original Message- From: Christian Have To: Bruno David Simões Rodrigues; [EMAIL PROTECTED] Sent: 7/23/01 1:06 PM Subject: RE: SMSC Driver features I'm asking this because now if you set udh, the message is automatically 8bit :( in smsbox.c. Youre right, and this isn't particularly clever. Theres acutally a comment about it in the source... from smsbox.c, line ~1180: if (udh) binary = 1; else binary = 0; /* * XXX in future, we should allow both 7bit or 8bit data as 'text', * maybe as data vs. text argument, and then set binary accordingly. * But that would be a compatibility breaker, so have to think about * that a bit more... */ I have an actual example of why this is not practical: Ericsons ems, this needs to be sent 7bit, but also have an udh. Christian.
RE: SMSC Driver features
-Original Message- From: Andreas Fink To: [EMAIL PROTECTED] Sent: 7/23/01 1:59 PM Subject: RE: SMSC Driver features coming back to the unicode discussion, a encoding=text would indicate it has to be encoded but encoding=raw would mean the data is already encoded. I can live with this but I think already encoded should mean byte values (e.g. %ab%cd%ef...), not a single long string. Regards Joerg
RE: SMSC Driver features
-Original Message- From: Bruno David Simões Rodrigues To: Jörg Pommnitz; [EMAIL PROTECTED] Sent: 7/23/01 3:22 PM Subject: Re: SMSC Driver features Of course you are right, that 00330034 isn't a nice thing. But as I see in Etsi specs, the only encoding supported is UCS2 (the one, right?) and as you said, we should accept other encodings. But then we'll have to convert to ucs2, because that's the only one we'll need to inject into smsc's. If that's your idea, and as there is no encoding function already done, I need to know how to send the UCS2 chars through the http interface (sorry, I haven't had time to see the RFC you gave me). This way, I can change it to text=??0034??0035encoding=UCS2 Please help me. http:?encoding=UCS2text=?? Hi Bruno, do not use UCS2 aka. UTF-16 inside the URL. It's broken. The right way to go is UTF-8. I suggest you read the reference I did provide and RFC 2044 (http://www.cis.ohio-state.edu/cgi-bin/rfc/rfc2044.html) for a detailed explanation of UTF-8. As for other encoding than Unicode or ISO-8859-1: of course we have to recode them. But it makes sense to do so. A lot of applications can easily create strings in their native encoding. We should support these applications. And if we are really going to tackle this area, we should come up with a unified method to convert to the GSM 7bit character set. Up until now most drivers seem to do it on their own and do not do a good job at it. Regards Jörg
RE: [RFC] mysql interface to kannel?
PS: who controls Kannel releases now? Good question. That's why I said we need either a new gateway architect, a stearing commitee/core group or the Kannel foundation. Regards Joerg
AW: [patch] Flash, MWI and Unicode
Hi Bruno, I'm sorry if I sounded too harsh in my criticism. It's just that I really feel that this approach is wrong and that we should discuss how to implement what you want. The ad-hoc solution to pass the string from the CGI variable directly to the SMSC driver is broken. There are multiple goals for the HTTP interface: * it must be independend from the SMSC protocol * it must be flexible, general and reasonable easy to use * it should be standard conformant as far as possible My design proposal would be: 1. use the encoding tag to specify the name of the character set used for the text. 2. add a field to the sms message structur to hold the MIB-Enum value of this character set as specified by IANA. 3. Inside the SMSC driver you can than convert to your hearts desire and get the message into a format suitable for the SMSC protocol. IMHO this approach is general enough to cover every sensible use case and it provides an actual framework for further work. Regards Joerg -Ursprüngliche Nachricht- Von: Bruno David Simões Rodrigues [mailto:[EMAIL PROTECTED]] Gesendet am: Donnerstag, 19. Juli 2001 22:25 An: Jörg Pommnitz Betreff: Re: [patch] Flash, MWI and Unicode Hi. It's not my intention to make Kannel unmaintainable in the long run. I am coding some simple things that I have already done and which I've seen people asking for it. If I'm coding it the best way, I don't know. I'm doing it the way I know, and I hope you accept it just for it. Of course I'm opened to suggestions and improvements, and I'll be glad to recode it in a better way. I'm gonna see better the encoding stuff and if everybody says yes, I'm available to do (or help doing) the code. As I told you, this way you can send some unicode, even if you have to encode it from the outside. I think it's better than nothing. But I'll change the unicode field to a encoding field limited to ucs2 for now. After all, this is a development kannel, not a stable one, right. It's meant to improvements. And I'm available to improve it as I can. Hope you don't take it bad. regards, -- Bruno Rodrigues - Original Message - From: Jörg Pommnitz [EMAIL PROTECTED] To: 'Bruno David Simões Rodrigues ' [EMAIL PROTECTED]; Jörg Pommnitz [EMAIL PROTECTED]; [EMAIL PROTECTED] Sent: Thursday, July 19, 2001 4:53 PM Subject: RE: [patch] Flash, MWI and Unicode For binary messages (e.g. nokia smart messaging messages) you actually give the byte values to Kannel. This is very different from your code. Decoding UTF-8 by hand is easy and it is even easier using the iconv function. You just tell iconv that you want to convert the message. Here is an iconv based function I wrote: (...) You can use it this way: msg_data = octstr_recode (UTF-16BE, UTF-8, msg-smart_sms.msgdata); In this example msgdata is in UTF-8. The destination is in UCS2-BE. I don't think iconv should be used directly. I understand the Win32 API has its own functions to convert strings in different character sets. That's why iconv should be wrapped similiar to the pthread code. The W3C recommendation I was talking about can be found under http://www.w3.org/International/O-URL-code.html As for your proposal of %1234: DON'T! That's not a valid URL and it asks for trouble in the future. Maybe we really need either a chief architect or a stearing committe. Otherwise I'm afraid Kannel will become unmaintainable in the long run. Regards Jörg -Original Message- From: Bruno David Simões Rodrigues To: Jörg Pommnitz; [EMAIL PROTECTED] Sent: 7/19/01 5:10 PM Subject: Re: [patch] Flash, MWI and Unicode but this way you have to have code to do the utf-8 encoding inside kannel. I don't know if it's easy or not. My patch only activates the unicode bit and pass the text in raw mode. This way, something outside kannel could encode the unicode and pass it to kannel. Which RFC are you talking about? I did it this way inspired in the way of nokia smart messaging messages. You just activate the bits and give the raw data to kannel send. Something else knows how to encode it. I think wapit had some code to unicode but we can't use it anymore. Could Richard or Lars say something about it? -- Bruno Rodrigues - Original Message - From: Jörg Pommnitz [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Thursday, July 19, 2001 3:46 PM Subject: RE: [patch] Flash, MWI and Unicode I think this interface change needs some discussion. I strongly feel we should follow the RFC's in this case. This means Unicode should be sent in UTF-8 encoding. As a quick hack to the stable code I once made the following changes: * add a CGI parameter encoding With this change in place one could use
RE: CVS WTLS state
There's only one file supported in the CVS code, I'm afraid. That's as far as we got :- Are you still working on this or did you drop the project? Regards Joerg
RE: [patch] Flash, MWI and Unicode
I think this interface change needs some discussion. I strongly feel we should follow the RFC's in this case. This means Unicode should be sent in UTF-8 encoding. As a quick hack to the stable code I once made the following changes: * add a CGI parameter encoding With this change in place one could use something like this: http://kannel:8090/cgi-bin/sendsms?user=userpassword=passfrom=1234to=1234 5text=Hiencoding=utf-8 This is more flexible and actually conforms to the W3C recommendations. Regards Jörg rowentryliteralunicode/literal/entry entry valign=bottom Optional. If given, the message will be encoded using the Unicode text given in literaltext/literal field. ex: text=0041007200610062002006306350636. /entry/row
