| CDR Generation of actual carrier SMSC transactions |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - MMS & Advanced Issues ⬆ Archive through April 05, 2007 ⬆ |
◄ ► |
| Author | Message | |||
| Keeran Janin New member Username: Keeranj Post Number: 4 Registered: 03-2006 |
I'm aware that NowSMS can store MMS and SMS messages in the SMS-IN/OUT directories. Is there a way or function to have the gateway produce full CDR log files for the actual SMSC tansactions which log all information such as the carrier SMSC assigned messageID's, delivery notifications, timeStamps, etc. I am connecting to my carrier's SMSC via SMPP and then using the NowSMS web interface to submit and receive SMS message's from numerous different application servers and services. I have been using NowSMS 5.51 and all my services are configured for the HTTP responses generated by that version (which does not supply the SMSC messageID nor does it indicate how many messages were sent in the case of concatenation). I have been doing some preliminary testing with V2006 and notice that now when submitting via the Web interface it does respond with messageID's of the messages submitted although it seems these are messageID's generated by the NowSMS internal SMSC. In the event that there is a problem with the recipient MSISDN, connection or what not I have no idea whether the message was actually delivered to the carrier SMSC or the handset. This has been a major obstacle for me as at the end of every month I need to reconcile my usage with my carrier's CDR for revenue payments. Basically I need to know exactly all the carrier SMSC and MMSC tansactions and information, preferably in the form of a CDR file or even an interface to a MS SQL Databse which I can specify. An suggestions to how this can be accomplished in NowSMS 5.51 or V2006. Any migration I may undertake to V2006 will mean a lot of recoding as my services are hard coded to parse the HTML responses from the NowSMS 5.51 web interface. Thanks in advance. | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 6181 Registered: 10-2002 |
Hi, You can find the operator assigned message ids in the SMSOUT-yyyymmdd.LOG file. (It is not generated until the message is actually submitted to the operator, so we do not have it at the time of the HTTP response.) If you request delivery receipts, NowSMS can return the delivery/non-delivery receipts back to you (via 2-way SMS) with the NowSMS assigned message id. But I don't think that would help you, because it sounds like you want to correlate with the operator assigned message ids, in which case you would need to look at the SMSOUT-yyyymmdd.LOG files. -bn | |||
| Keeran Janin New member Username: Keeranj Post Number: 5 Registered: 03-2006 |
Bryce, Thank you for the information. in the INI files are there any attributes which can be set so I can have some control over the way or location where the SMSOUT andn SMSIN log files are written. Say for example I would like to write them to a seperate partition or a network drive where I can have my other services process that data seperately | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 6279 Registered: 10-2002 |
Yes. Under the [SMSGW] header in SMSGW.INI, add: LogDirectory=x:\path or LogDirectory=\server\path (Note: This does not affect the debug log, just the normal logs.) | |||
