On Dienstag, Januar 14, 2003, at 12:05 Uhr, Mauricio Ramos wrote:
Hi Guys,
I follow some Andreas' tips and found that most of my problems were due to:
1) Wrong type of MySQL dlr field 'ts'. I used TIMESTAMP type and now using
VARCHAR type for correctness. It would be great to have sample dlr field
data types in userguide!
oh... this is an excellent idea. never came to my mind that this could be your problem.
2) Not in accordance with the userguide, the default msg-id-type IS NOT 1.
I still doesn't know what is the default for msg-id-type BUT setting this to
1 solved the problem. Another thing to fix in userguide!
Yes
These two misconfigurations above were enough to make a big mess.
The only things that last were:
1) The use of DLRMASK equal to 4 or 20 inserts a DLR that potentially will
remain in database forever. Although this is an error, it can be avoided;
Should be easy to fix. Simply remove entry if buffered is final state because there are no other statuses possible to follow.
2) The use of DLRMASK equal to 16 never inserts a DLR in databas. Comparing
with previous situation, this maybe considered an error, it can be avoided
too;
Not necessarily. The submission of SMS to the SMSC while not having received an ACK is a very temporary transaction. In EMI we decided to store this temporarely solution into the database, but this doesn't have to be this way. The answer is almost immediate by an ACK or NACK to the submission so if you don't ask for any other reports, it can be hold in memory related to pending transactions. It depends on the design of the driver and the DLR code of it.
Andreas Fink
Fink Consulting GmbH
---------------------------------------------------------------
Tel: +41-61-6666332 Fax: +41-61-6666331 Mobile: +41-79-2457333
Address: Clarastrasse 3, 4058 Basel, Switzerland
E-Mail: [EMAIL PROTECTED]
Homepage: http://www.finkconsulting.com
---------------------------------------------------------------
