Kannel usage in my project (Was: Re: Bug discovered with long text messages and escape sequences...)

[Bruno David Simões Rodrigues]

No, I haven't finished it yet the encoding code. :(

As I said, our system started production and my primary concern now is to
fix all small
bugs like:

2001-07-31 Bruno Rodrigues <[EMAIL PROTECTED]>

        * bearerbox.c, smsbox.c: added alog_reopen to HUP signal handler.
        * smsbox.c: removed "include <strings.h>" -> not needed anymore;
        set sms_type to mt_push when receiving messages through http
        interface: When I restarted kannel, all messages on store were
        returned to the default service instead of beeing retransmitted.
        * smsc_at.c: added some ATI queries to modem; On the while loop
        to retransmit PDU, added sending AT+CMGS; removed \n from
AT:command;
        Added "Read from modem" debug dump;
        * smsc_emi2.c: accept XSER 02 with DCS, but didn't yet convert it
        to other fields (flash, encoding, etc); Added wait-ack configuration
        to define for how long to wait for (N)ACKs (default still 60
secongs).
        * smsc_emi2.c: added flow-control configuration. If unset or 0,
stays
        in windowed mode (I'll do later the code to define the window
value).
        If 1, uses stop-and-wait flow control.

I can now say that kannel is working great in here.
We have sent and receive, since last monday (three days), 25k sms. I think
my
company were doing 1.5M per month, and that means this project are doing
almost 15% of total sms traffic. :p

This is a messaging project and my kannel piece does three things:
We have a short number and a M20 modem that accepts messages to provisioning
the system from our clients and other national mobile telcos. Then we reply
back
trough the smsc the new password to them.
Second, an web form to send sms that sends it with the from of the client,
like if he
was sending through the phone and with deferred time (the delay is done in a
database,
not in kannel, because the delay offered to clients is bigger than the one
configured
on smsc).
Third we have alerts associated with the scheduler of Outlook Web Access. Of
course
that Microsoft Mobile Information Server sucks and we had use kannel for it.
(*)

I have done a perl script that converts bearerbox_access.log to split the
several services
in several files in common log format and have injected it in webalizer to
have some stats.

Now I'm adding "alowed-prefix" to smsc and "allowed/denied-prefix" to sms
services so
I can control which services is available to our network or to others (we
had already one
international provisioning register, other sent through an email to sms
gateway and other
through an external web form (of course that exchange didn't liked when I
sent it a from
number in a "strange" format :))))) ).

I have to check smsc_at code because I've tried to send a sms with text from
to the M20
and smsc_at gave very strange results :( (like the from was like a memory
dump from
somewhere).

I hope this mail is not too much confuse :)

(*) MS MIS sucks sucks sucks. It can only send messages, not receive. It
doesn't have
fixed our-port. It doesn't have keepalive neither login. It doesn't have
gsm_alphabet.
I LOVE kannel! :))))))))))))))))

regards,
--
Bruno Rodrigues


----- Original Message -----
From: "Andreas Fink" <[EMAIL PROTECTED]>
To: "Bruno David Simões Rodrigues" <[EMAIL PROTECTED]>
Sent: Thursday, August 02, 2001 11:56 AM
Subject: Re: Bug discovered with long text messages and escape sequences...


> Did you fix it finally? I need to fix the problem where kannel is
> sending long text messages to another kannel. So the encoding field
> would be needed to indicate that it is still plain text and not
> binary.