| Understanding MMSc Log entries. |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - SMS Issues ⬆ Archive through October 16, 2008 ⬆ |
◄ ► |
| Author | Message | |||
| Brandon Francis New member Username: Bfrancis Post Number: 8 Registered: 03-2006 |
Hello support, I want to know if you have a definition table for all the different fields that can appear in the MMSC logs please? We want to implement some reports and need to define all the possible fields that appear in these logs into our data base. Aside from regular local MMS, we are also doing VASP accounts and MMS Outbound routing. We also intend to implement the MNP feature in MMS. So I would like all these log scenarios covered please. Thanks in advance. | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 60 Registered: 08-2008 |
Hi Brandon, Unfortunately, we do not have a clear concise document that describes these records. The following information may be complete, but it is a good starting point if you use it as a guide when looking at a log file. In the MMSC-date.log, there are several basic types of log entries. The type of entry is the first CSV entry in the record following the date/time stamp. MMSIN - This records an inbound MMS message. Additional fields: * IP Address (usually the IP address of a WAP GW) * MMSC User ID (local "MMSC Users" account, or if prefixed by "VASP:" this refers to "MMSC VASP" account) * Message Recipient (phone number or e-mail address) * MMS Message ID or the name of the outbound "MMSC Routing" to which this message is being routed * Message ID for SMS Gateway notification or outbound "MMSC Routing" message queue id * Message Size (if available) 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. MMSIN-DeliveryReport - Same format as MMSIN, but for a delivery report message. MMSIN-ReadReport - Same format as MMSIN, but for a read report (read receipt) message. MMSRETRIEVE - This records when a message is retrieved from the MMSC. (We also record other web access attempts Various viruses and trojans constantly scan the web looking for web servers to infect, and it is not unusual to see these scan attempts appearing in these log entries.) Additional fields: * IP Address (usually the WAP Gateway) * Message Sender (if available) * Message recipient (if available) * MMS Message ID or URL request * Status - OK or FAILED * Message size (if available) 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, we suggest that ".MMS" extension be ignored if present. MMSOUT - Records an outbound MMS message being routed to an external MMSC (e.g., "MMSC Routing" definition). Additional fields: * MMSC Routing Account to which message is being delivered (prefixed by "VASP:") * Message Sender Address * Message Recipient Address * Status - OK or FAILED * "MMSC Routing" message queue id * Message size (if available) MMSOUT-DeliveryReport - Same format as MMSOUT, but for a delivery report message. MMSOUT-ReadReport - Same format as MMSOUT, but for a read report (read receipt) message. SMTPIN - Records an inbound SMTP message. Additional fields: * IP Address * From address * Message Recipient * MMS Message ID * Message ID for SMS Gateway notification * Message Size (if available) -- Des NowSMS Support | |||
