"Yes, I've changed sqlbox code, i'll post later my patch to the latest SVN trunk version."
- That would be awesome !
I would love to get that link to the SVN and try out your "add-on" !
Gesendet: Dienstag, 06. August 2013 um 21:12 Uhr
Von: spameden <[email protected]>
An: "hans joachim" <[email protected]>
Cc: "[email protected]" <[email protected]>
Betreff: Re: Re: Fw: SMS Accounting
Von: spameden <[email protected]>
An: "hans joachim" <[email protected]>
Cc: "[email protected]" <[email protected]>
Betreff: Re: Re: Fw: SMS Accounting
Hi
2013/8/6 hans joachim <[email protected]>
"If I understood you right, you want to get actual smsc_id in the table through which MT was sent?"- Yes, exactly thats what I need !!"to achieve this you need to modify sqlbox and update sent_sms table MT entry when DLR arrives from SMSC-operator. we modified sqlbox to update MT entries with all relevant DLR information including parts_number which contains number of actual sms in case of concatenated message."- Can you tell me how you did this ? Do you have changed the code of SQLBOX to archieve this behaviour ? Sounds very complicated ....
Yes, I've changed sqlbox code, i'll post later my patch to the latest SVN trunk version.
Gesendet: Dienstag, 06. August 2013 um 16:04 Uhr
Von: spameden <[email protected]>
An: "hans joachim" <[email protected]>
Cc: "[email protected]" <[email protected]>
Betreff: Re: Fw: SMS AccountingHi2013/8/6 hans joachim <[email protected]>Hello,I saw that the sending SMSC can be stored in the access-log.I made several tests with the custom access-log-format: But the problem is that I don't get a unique ID in the access-log for every message.access-log-format= " TS="%t" SMS-ID="%F" ID2="%x" USER="%n" TYPE="%l" SMSC="%i" TO="%P" TEXT="%b"Neither "%t" nor "%F" give me a unique ID :(I still need one place where every message is stored with all necessary informations.Conclusion:In sent_sms table of SQLBOX is no SMSC_ID (Only the virtual SMSC_ID used for routing purposes, which is not useful for accounting/billing purposes).In access-log there is no unique ID for every message.How can I archieve my goal, so that all necessary informations will be stored in one place ?If I understood you right, you want to get actual smsc_id in the table through which MT was sent?
to achieve this you need to modify sqlbox and update sent_sms table MT entry when DLR arrives from SMSC-operator.How do you account the costs for sending messages through different SMSC's ?we modified sqlbox to update MT entries with all relevant DLR information including parts_number which contains number of actual sms in case of concatenated message.Thank you in advance,FlorianGesendet: Montag, 05. August 2013 um 16:03 Uhr
Von: "hans joachim" <[email protected]>
An: "[email protected]" <[email protected]>
Betreff: SMS AccountingHello,I have 3 SMSC (gsm1, gsm2, gsm3) in my Kannel-Setup and I'm using sqlbox to save all kind of information about the messages in a database.My question is how can I store the sending SMSC of every message in the database ?For example:
If I call the webservice with the argument "&smsc=gsm1" and the message is sent, I see this information in the database entry :+---------------------+--------+------+---------+-----------------+---------+---------------+------------+-------------+---------+---------+------+----------+--------+------+--------+----------+----------+----------+----------+---------+------+---------+------+---------+---------+-------+
| date | sql_id | momt | sender | receiver | udhdata | msgdata | time | smsc_id | service | account | id | sms_type | mclass | mwi | coding | compress | validity | deferred | dlr_mask | dlr_url | pid | alt_dcs | rpi | charset | boxc_id | binfo |
+---------------------+--------+------+---------+-----------------+---------+---------------+------------+-------------+---------+---------+------+----------+--------+------+--------+----------+----------+----------+----------+---------+------+---------+------+---------+---------+-------+| 2013-08-05 15:43:31 | 10 | MT | xxxxxx | xxxxxxxxxxxxxx | NULL | bla | xxxxxxxxx | gsm1 | user1 | NULL | NULL | 2 | NULL | NULL | 0 | NULL | NULL | NULL | NULL | NULL | NULL | NULL | NULL | NULL | smsbox1 | NULL |
But I configured message-routing in a way, which eventually allows me to bypass a SMSC which is not working at this given moment.
Because of this message-routing I can't call the webservice with the argument "&smsc=" ! But if i don't use that argument, the information about the sending SMSC is not stored in the database :(Once a month, I need to know how many messages were sent through gsm1, gsm2 and gsm3. I'm not able to get this information, if the database field is not getting filled :(
Regards,
Florian
