| Chronological order of MM4 Callbacks. |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - MMS & Advanced Issues ⬆ Archive through April 05, 2007 ⬆ |
◄ ► |
| Author | Message | ||||||
| Adolfo Abegg New member Username: Adol Post Number: 12 Registered: 01-2006 |
Hi Bryce, Could you explain us the order in which callbacks are executed. We need a way to conciliate incoming/outgoing messages with other operators. For this porpuse, we are using the Accounting Callbacks to generate logs for both incoming and outgoing messages. That is for un/delivered messages. When SENDING a MM. (Outgoing messages) -------------------------------------- I've attached a file named outgoing.txt where you can see how CallBacks are executed when sending a MM to another operators' MMSC via MM4. This is a short explanation of the steps: 1- MMSRouteCheck 2- MMSSend PreAuth 3- MMSSend 4- SMTP Transaction. What happens if SMTP Transact. was not successfully executed? We want to use the MMSSend Accounting Callback to charge the user who is sendig the MM. Shouldn't it be in this order?: 1- MMSRouteCheck 2- MMSSend PreAuth 3- SMTP Transaction. 4- MMSSend (If SMTP transaction was successful) As I read on your Accounting CallBacks Bulletin, they should be executed in this way. "MMSSend: This callback is executed after an MMS message that has been sent by an MMS user has been accepted by the gateway for delivery." When SENDING a MM. (Incoming messages) -------------------------------------- I've attached a file named incoming.txt Is "MMSSend PreAuth" the only Callback executed on incoming messages? I cannot find the "MMSSend" Callback on the MMSCDEBUG.LOG after the "PreAuth" one was executed. Again, what happens if the SMTP transaction was not succesfully completed? There's no way to know if the MM was successfuly delivered to the other operator's MMSC. Thank you Bryce for your help and patience. Adolfo Abegg
| ||||||
| Adolfo Abegg New member Username: Adol Post Number: 13 Registered: 01-2006 |
Hi Bryce, Any comments about this post? | ||||||
| Adolfo Abegg New member Username: Adol Post Number: 14 Registered: 01-2006 |
Hi Bryce, I hope you can help us this week. Have a nice day. | ||||||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 6004 Registered: 10-2002 |
Hi Adolfo, I'm back. Apologies for the delay in response. There are no HTTP callbacks related to the MM4 transmission of the message. The "MMSSend" callback only indicates that the message was accepted for delivery locally by the NowSMS MMSC. Currently there are no HTTP callbacks to track a message being routed externally via MM4 (or MM7 etc). There are "MMSOUT" log file entries that record these transactions as messages are routed to an external MMSC connection ... but no HTTP callbacks. I suppose we could look at adding a callback here ... maybe Type=MMSOut? I've been discussing this with our engineering team, and the consensus is that we should add this callback. Regarding the inbound transactions, there should be an "MMSSend" callback when the inbound message is actually processed. Unlike messages received from a local client, this type of message is not processed immediately when it is received. Typically it is processed several seconds later. I checked your ZIP file, and these callbacks do seem to be occurring correctly with inbound messages. We're going to do some more investigation to see whether we can easily add a "Type=MMSOut" callback for the external MMSC message delivery. -bn | ||||||
| Adolfo Abegg New member Username: Adol Post Number: 15 Registered: 01-2006 |
Hi Bryce, Thank you very much for you help. We'll be waiting for the new callback  In the meantime, we would like to build a middleware to solve this problem. Do you have any thougths about it? Have a nice day! | ||||||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 6035 Registered: 10-2002 |
Hi Adolfo, Are you running NowSMS 2006? The reason I ask, is because after reviewing the above, we have produced an update that includes a "Type=MMSOut" accounting callback which can be enabled. We're not posting this update on the web yet, because there are still a few more minor changes that we want to complete before posting this update. But it is stable. I can send it to you via e-mail if you like. If you want to do this, then send an e-mail to nowsms@now.co.uk with "Attention: Bryce" in the subject line. Aside from this update, the only solution that I can see is to scan the MMSC-yyyymmdd.LOG files. However, when we were reviewing this area, we noticed an inconsisteny between the accounting callbacks and the log entries when messages are routed to an external MMSC. The MMSC-yyyymmdd.LOG records a different message id than what is reported in the accounting callbacks. The message id reported in the log file is the same for both the in and the out ... but it is a different id than the one reported in the accounting callback. This is not a problem ... if you are only using the log. But it is a problem if you are using the accounting callbacks, and then want to scan the log to find the matching "MMSOut" record. So I'm not sure what to suggest. The update with an added "MMSOut" callback sounds like the easiest approach to me. -bn | ||||||
| Adolfo Abegg New member Username: Adol Post Number: 16 Registered: 01-2006 |
Hi Bryce, Again, thanks for your support. We've got the 5.51k(b20051013) Now SMS/MMS Gw version running in our server. Unfortunately, the size of our logs increase very fast. Scanning them will result in a performace problem. We're thinking on building our SMTP Relay to process each request for MM4 messages, so when routing a message to another operator we'll preprocessing for the messages before sending them to the operator's host. Do you have any thougths about this idea? Adolfo Abegg | ||||||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 6043 Registered: 10-2002 |
Hi Adolfo, Yes ... I don't like the idea of scanning the log files in any real-time type of fashion. It works ok for some people who perform daily batch processing ... but even then, I prefer a real-time approach. An SMTP relay would be reasonable approach, it wouldn't be that difficult of a task. Of course, I don't know what code might be out there to provide a starting point ... if there might be an existing SMTP relay that could be easily adapted for this task. You might want to look at upgrading to NowSMS 2006. I think the update with an added "Type=MMSOut" callback would be the quickest solution. -bn | ||||||
| Adolfo Abegg New member Username: Adol Post Number: 17 Registered: 01-2006 |
Hi Bryce, We'd downloaded your trial version of the NowSMS 2006. Now we would like to install the update with the "Type=MMSOut" callback to make some tests related to MM4 transmissions, can you help us in getting this update? Once we finish with the tests, we might upgrade to NowSMS 2006. Adolfo Abegg | ||||||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 6360 Registered: 10-2002 |
Hi Adolfo, Download http://www.nowsms.com/download/patch2006.zip for the latest official update. For information on the changes, see http://support.nowsms.com/discus/messages/53/15129.html. -bn | ||||||
| José Britos New member Username: Jose_britos Post Number: 1 Registered: 08-2006 |
Hi Bryce, I'm Adolfo Abegg's Partner, I have questions for you: - I've installed the trial version 2006 Nowsms, but I didn't find the MMSOut callback, the MMSC.INI was modified and I putted MMSAccountingEnableMMSOut=Yes, but the callback did not appear. - I have modify other .ini file? You can tell me what file I need modify or what I can do about this. Best Regards. PD: please sorry, but my english grammar is not much good Jose Britos | ||||||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 6377 Registered: 10-2002 |
Hi Jose, Did you also install the patch referenced above after installing NowSMS 2006? (http://www.nowsms.com/download/patch2006.zip) After installing that patch, you should only need to edit MMSC.INI, and under the [MMSC] header, add MMSAccountingEnableMMSOut=Yes. To check that you have the updated patch installed, verify that MMSC.EXE has a date of 23-Jun-2006 or later. -bn | ||||||
| José Britos New member Username: Jose_britos Post Number: 2 Registered: 08-2006 |
Bryce, I install the patch, the mmsc.exe has 23-Jun-2006 and under the [MMSC] header, add MMSAccountingEnableMMSOut=Yes. in the MMSC.INI, however did not generate MMSCALLBACK type= MMSOut. Do you have any suggestion for this case? | ||||||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 6379 Registered: 10-2002 |
Jose, I am trying to determine what conditions might cause the callbacks not to be performed when this MMSC.INI file setting is present. You are receiving other MMS accounting callbacks, correct? And there are MMSOUT log entries being written to the MMSC-yyyymmdd.LOG, correct? (This accounting callback occurs at the same time as the log file entry is made.) I expect the easiest way to figure this problem out would be to ask you enable the MMSCDEBUG.LOG (this is done via the "Serial #" page of the configuration dialog). Send another MMS message that will get routed to an external "MMSC Routing" connection (MM4). Then send me the MMSCDEBUG.LOG and your MMSC.INI file. You can either post those files in a reply here, or if you prefer, e-mail them to nowsms@now.co.uk with "Attention: Bryce" in the subject line. (If you send via e-mail, please include a reference to this thread, so I can remember why I asked for the logs. Mention the MMSOUT callback and that should be enough for me to remember.) -bn | ||||||
| José Britos New member Username: Jose_britos Post Number: 3 Registered: 08-2006 |
Bryce, I upload the zip file, with log files, mmsc .ini, please take a look and tell me what fuound. jb
| ||||||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 6392 Registered: 10-2002 |
Hi Jose, It looks like the issue is that the test server can't connect to your MM4 partner. The MMSOUT callbacks only occur when a message actually gets delivered over the connection. In this case, these external connection attempts are failing. -bn | ||||||
| José Britos New member Username: Jose_britos Post Number: 4 Registered: 08-2006 |
Bryce, The mmsout it is work and this solve my problems with that. Now I have a question for you: - When I install the Nowsms/mms v2006 with the last patch, this installation will be erase all my Vaspout configuration and all others setting's. I will be not lost all configuration from v5.51k, that is it correct?. -How can I update from nowsms v5.51k to nowsms v2006 with the las patch, without lost all my configuration existent in old version, it is possible? Please confirm that because I have a lot of vaspaccount, vasproute, and others specific's configuration. What recommend me in this case. I hearing you soon, Best regards, José Britos PD: Please send me to the commercial contact. To purchase license for the new | ||||||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 6412 Registered: 10-2002 |
Hi José, All configuration information will be saved if you upgrade from v5.51k to 2006. Currently, it is a two-step process to update from NowSMS v5.51k to the June patch of NowSMS 2006. However, all of your configuration information will be saved. First you install NowSMS 2006 into the same directory as v5.51k. Next you install the June patch for NowSMS 2006 into this same directory. Only the NowSMS program files (and some HTML templates for the web interface) are updated as part of this process. No configuration files are updated. -bn | ||||||
Log for outgoing msgs
MMSCDEBUGLOG
