KANNEL 1.x STATUS: 
  Last modified at [$Id: STATUS,v 1.14 2002/03/26 15:13:41 davi Exp $]

Release:


RELEASE SHOWSTOPPERS:

    * sms-service might not reply back the sms 
    Posted by: Alex Judd <ajudd@skywire.co.uk>
    Message-ID: <Pine.LNX.4.44.0202270925420.23783-100000@samsara.kgbinternet.com>
    Status: Bruno Rodrigues: I'm checking that.
 
RELEASE NON-SHOWSTOPPERS BUT WOULD BE REAL NICE TO WRAP THESE UP:

    * forced-smsc not working with concatenated, probably routing issue 
      between several configured smscs and concatenated messages
    Posted by: Stefan Cars <stefan@globalwire.se>
    Message-ID: <Pine.LNX.4.40.0201281929290.3610-100000@tjatte.globalwire.se>
    Status: Stipe: workaround see <3C55D821.B930320C@wapme-systems.de>

    * incoming concatenation ;)
    Posted by: Bruno Rodrigues <bruno.rodrigues@litux.org>
    Status: 

    * add check for empty messages in check_sendsms
    Posted by: Aarno =?iso-8859-1?Q?Syv=E4nen?= <aarno@wiral.com>
    Message-ID: <3C848209.FAE8FCB7@wiral.com>
    Status: Aarno will add it
    
Available Patches:

    * DLR handling logic change 
    Posted by: Oded Arbel <oded@m-wise.com>
    Message-ID: <2CFC21DAF860CC49AF57333C4459DD4B166E85@exchange.m-wise.com>
    Status: 

    * Weighted round-robin SMS load balancer
    Posted by: Choong Hong Cheng <chc79@yahoo.com>
    Message-ID: <20011228013937.25092.qmail@web13805.mail.yahoo.com>
    Status:

    * SMSC specific default-sender and forced-sender 
    Posted by: "Angel Fradejas" <afradejas@mediafusion.es>
    Message-ID: <FMEKKCFKIGBADHGIJKPJGENPCKAA.afradejas@mediafusion.es>
    Updated: <FMEKKCFKIGBADHGIJKPJAEFECPAA.afradejas@mediafusion.es>
    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: jakob.gaardsted@coment.dk
    Message-ID: <OF7A262989.8F1B64DC-ON41256B4C.002DEDAD@coment.dk>
    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: <bbuettner@vodafone-telecommerce.de>
    Message-ID: <NCBBLDCBEKKMINJKJNBPKECMCNAA.bbuettner@vodafone-telecommerce.de>
    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 <tolj@wapme-systems.de>
    Message-ID: <3C4F4BFE.AE3C687B@wapme-systems.de>
    Status: Stipe: "Andrea Viscovich" <anviscov@tin.it> has done this for a 
            own solutions, needs to be revised and cleaned up.