I have gathered some STATUS information and compiled the attached text
file. Basicly this was inspired by the automatic STATUS report at
Apache's developer list.
Should I commit file STATUS to cvs and let it be posted once a week to
the developer's list?! It would be great if all cvs write permission
owners would update this file with recent developments and issues of
the devel@ list.
Stipe
[EMAIL PROTECTED]
-------------------------------------------------------------------
Wapme Systems AG
M�nsterstr. 248
40470 D�sseldorf
Tel: +49-211-74845-0
Fax: +49-211-74845-299
E-Mail: [EMAIL PROTECTED]
Internet: http://www.wapme-systems.de
-------------------------------------------------------------------
wapme.net - wherever you are
KANNEL 1.x STATUS:
Last modified at [$Id: STATUS,v 1.1 2002/01/28 10:10:08 tolj Exp tolj $]
Release:
RELEASE SHOWSTOPPERS:
* HTTP/1.1 Keep-Alive connection handling causes heavy CPU cycling on
Linux and system error on other platforms. Seems to be a file
descriptor and/or polling issue. Any box is affected which uses the
HTTP server implementation.
Initial report by: Frederik Ammitzboll <[EMAIL PROTECTED]>
Posted by: Stipe Tolj <[EMAIL PROTECTED]>
Message-ID: <[EMAIL PROTECTED]>
Status:
RELEASE NON-SHOWSTOPPERS BUT WOULD BE REAL NICE TO WRAP THESE UP:
Available Patches:
* Weighted round-robin SMS load balancer
Posted by: Choong Hong Cheng <[EMAIL PROTECTED]>
Message-ID: <[EMAIL PROTECTED]>
Status:
* SMSC specific sender number configuration
Posted by: "Angel Fradejas" <[EMAIL PROTECTED]>
Message-ID: <[EMAIL PROTECTED]>
Status: Stipe -1 (conceptual clash to global-sender?!)
Open issues:
* Clashing unified-prefix when several SMSCs send their incoming messages
with or without international prefix.
Suggested solution: introduce unified-prefix on smsc group level
Posted by: [EMAIL PROTECTED]
Message-ID: <[EMAIL PROTECTED]>
Status:
* Configuring 2 HTTP interfaces for sendsms, one SSL-enabled and one not.
Config may look like this:
group = smsbox
...
sendsms-port = 13013 # for plain HTTP
sendsms-port-ssl = 13014 # for SSL-enabled HTTP
This would allow to let HTTP and HTTPS clients to connect to different
ports. If sendsms-port = send-port-ssl, then we assume we have only *one*
SSL-enabled HTTP interface at that port.
Posted by: <[EMAIL PROTECTED]>
Message-ID: <[EMAIL PROTECTED]>
Status: Stipe: Apache + mod_ssl does this, we should derive that from there
* ring-service group for smsc_at2.c to enable triggering of services while
users call the GSM modem.
Posted by: Stipe Tolj <[EMAIL PROTECTED]>
Message-ID: <[EMAIL PROTECTED]>
Status: Stipe: "Andrea Viscovich" <[EMAIL PROTECTED]> has done this for a
own solutions, needs to be revised and cleaned up.
