Understanding the bearerbox.

Hello,
I have few functionalities that we would like to see in kannel. Since
this is open source I was considering doing it by myself. I thus began
to read the source of bearer box, but time is expensive for us (we are a
small cpie!) so I would be interested in any docs that could help me
understand faster the whole SMS part of the bearer box. 
 
If no docs are available, maybe someone have a reading path and a global
picture that could help me, other ways I will do it the slow way…
 
In case someone has already working on this, the first things I would
like to do is 
-          When using a SMPP SMS center, when we get an error 0x14 to
submit_sm (receiver message queue full) kannel try to send 10 times
(approx) the messages every 20 secs. In our case we sometime have 10 or
much more receiver with full queue and this has a great impact on global
sms services perfs. I so would like to change this behavior (ie : try
only once and if I get a 0x14, I immediately put the message in a
waiting queue and do not try it 10 times. Special delay could be set for
this queue in config files).
-          Commands to “play” with messages queues with http. I begin to
see how this could be done. (ie : in few cases, like the one above, I
may want to delete some messages in queue).
-          Put some more interaction for an active monitoring system. I
have written a log file analyzer (not finished yet, in erlang) which
goal is to provide us with some “service qualities information”. The
above event (msg queue full) is directed toward people of our staff
(because for some professional services we are operating, this is
something that should not happen). It could be send directly from
kannel.
 
If anyone can point me toward (or give me) information that could help
me work faster that would be great.
 
Regards. 
 
 
Raphaël Bellec
Manobi France
Cap Alpha
Avenue de l'Europe, Clapiers
34940 Montpellier Cedex 09
Tél : + 33 (0) 4 67 59 36 56
Fax : + 33 (0) 4 67 59 30 10
E-mail : [email protected]