| Logging and stored MMS messages |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - SMS Issues ⬆ Archive through September 15, 2003 ⬆ |
◄ ► |
| Author | Message | |||
| Rob |
Hi, I am having some troubles understanding the format of the MMSC-date.log, and where can I find a description for the purposes of the following directories: MMSCDATA, MMSCIN, MMSCOUT; the reason I ask is because messages arrive at the NowSMS MMSC, and is relayed to my email account, but it isn't saved in any of the files.... strange.. Regards, Rob PS: I had a similar post earlier, but I can't see it anymore. | |||
| Bryce Norwood - NowSMS Support (Bryce) |
Hi, The content for MMS to e-mail messages doesn't get stored in MMSCDATA, because the message is immediately converted to e-mail format and sent to the e-mail recipient. Messages destined for mobile phones will be temporarily stored under the MMSCDATA subdirectory structure (for a default of 30 days). This is because when an MMS message is sent to a mobile phone user, the phone is notified with a speical SMS message, and the phone then needs to fetch the content from the MMSC. As for the format of the logs, I don't have anything handy at the moment, but I'll see if I can talk to some of our other folks about getting some info posted next week ... so I'll post a follow-up reply when I have this information. -bn | |||
| Rob |
From your explanation, I understand that MMS messages will be stored in MMSCDATA if I use the web interface to send an MMS message to a phone number for a user defined in the MMSC User list. This does not happen for me. Regards, Rob | |||
| Rob |
...Sorry, my error; the MMS message does get saved in MMSCDATA. Can you please tell me what the directories MMSCIN and MMSCOUT are used for? Also, in regars, to the logging, I see things similar to this: ",D98CAFEA,00E90000.RFC" (the second value D98... is not constant) Cheers, Rob | |||
| Bryce Norwood - NowSMS Support (Bryce) |
Rob, MMSCIN and MMSCOUT are "staging areas" for MMS messages going to/from e-mail. When an SMTP message is received, it goes into the MMSCIN directory (with a .RFC file extension) before it is processed. At this point, the message is pretty much in the same raw SMTP format that it was received, except that we've added a couple of headers during the receive. (X-MMSC-RCPT-TO: +phonenumber has the phone number of the recipient to receive this message. If multiple phone numbers, multiple headers.) MMSCOUT holds SMTP messages that are ready to be sent out. Again with a .RFC file extension. Now let me get info on those logs ... -bn | |||
| Bryce Norwood - NowSMS Support (Bryce) |
In the MMSC-date.log, there are three basic types of log entries. The type of entry is the first CSV entry in the record. MMSIN - This records an inbound phone-to-phone MMS message. Additional fields: IP Address (usually the IP address of a WAP GW) MMSC User ID Message Recipient (phone number or e-mail addr) MMS Message ID Message ID for SMS (or SMTP) Gateway notification Note: An MMS notification usually requires two SMS messages, so you may see multiple entries for a single message sent. You can tell this because the MMS Message ID is the same for both records, but the Message ID for the SMS Gateway changes. MMSRETRIEVE - This records when a message is retrieved from the MMSC. (We also record other web access attempts.) Additional fields: IP Address (usually the WAP Gateway) Not used Message recipient (if available) MMS Message ID Status - OK or FAILED Note: The MMS Message ID includes a ".MMS" on the MMSRETRIEVE record that is not present on the MMSIN record. This may change in the future to improve consistency, suggest that ".MMS" extension be ignored if present. SMTPIN - Records an inbound SMTP message. Additional fields: IP Address From address Message Recipient MMS Message ID Message ID for SMS Gateway notification == Hope that helps! Let me know if you have further questions! -bn | |||
| SteveBennett |
Is there a way of changing the default time they are stored in MMSCDATA to greater than 30 days (We've just lost all our test messages : ( At present they remain there even after they ahve been retrieved - which is fine for us. In the future will they be deleted if they have been successfully retrieved and an m-acknowledge-ind is received by the MMSC? | |||
| Bryce Norwood - NowSMS Support (Bryce) |
Manually edit MMSC.INI, and under the [MMSC] section header, add the statement: DataRetainDays=#### This will change the number of days that old messages are kept around, beyond "####" days. The default is 30. Similarly, there is an entry in that INI file: LogRetainDays=#### This specifies the number of days to keep log files around. Again the default is 30, so add a setting for this value if you want to keep the logs around for a longer period of time. -bn | |||
| Vratislav |
Hi, } I have problem with matching logs (automatically) in SMSOUT and MMSC files. I want to automatically monitor delivery of MMS. How can I unambiguously compare SMS Notification in SMSOUT with MMS retrive in MMSC. In most cases it is easy, but in some cases it is not possible. Is possible to use additional parametr(message id) to Web interface? Regards, Vratislav | |||
| Bryce Norwood - NowSMS Support |
Vratislav, I'm going to have to think about this question a little bit more. How are the MMS messages being submitted? I can see that if they come in through the MMSC, there would be an MMSIN record in the MMSC log that includes the ".req" name that would match up to the SMSOUT log. But if the message gets submitted through the web interface, it doesn't always go through the MMSC like this. Is that the problem that you're having? If it is, then I might have a work-around for you. Historically, when you use the web interface to submit an MMS message, NowSMS has bypassed much of the logic of the MMSC. But in the v5.0 release (yes, still in beta), because of external routing capabilities that allow the MMSC to route to other MMSCs ... the web interface of NowSMS cannot bypass the MMSC. It still does in a default configuration (for compatibility reasons), but if you define an additional "MMSC Routing", then NowSMS will route the web submitted MMS messages through the MMSC, and they will be logged to the MMSC log. To activate this, just go to the "MMSC Routing" page. Leave the "Default Route" as "Direct Delivery (internal MMSC)". "Add" an additional route. Give it an "Account name" of "X" or any other name you like. "Account Description" and "Default Sender Address" can be left blank. Under "Route messages to this account for recipient phone number", enter an invalid phone number, like "00000000000000". For "Route messages to VASP via", check "Multimedia WAP Push". This tells the MMSC that if it has an MMS message for "00000000000000", it should send the message as a multimedia WAP push instead of as an MMS. But it also signals the web interface of NowSMS that when an MMS message is submitted, it should go to the MMSC for routing, instead of NowSMS using the backdoor to the MMSC that it used in previous versions. -bn | |||
