| MMSC Log Description |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - MMS & Advanced Issues ⬆ Archive through April 05, 2007 ⬆ |
◄ ► |
| Author | Message | |||
| Einstein Wireless New member Username: Einstein Post Number: 1 Registered: 03-2007 |
Greetings, I am looking for an "official" description of the MMSC Log output that is generated by NowSMS MMS Gateway 2006. I am looking for field definitions along with the possible values for each field. We have looked at this link allready, but require more detailed information: http://support.nowsms.com/discus/messages/1/36.html | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 7004 Registered: 10-2002 |
Hi, For the MMSC-yyyymmdd.LOG files, the format of each CSV log entry varies based upon the log record type. I'll number the fields in the descriptions below. 1.) The first field is always a date/time stamp of the format yyyy-mm-dd hh:mm:ss. 2.) The second field is the log record type field. Currently defined record types include "MMSIN", "MMSIN-DeliveryReport", "MMSIN-ReadReport", "MMSRetrieve", "SMTPIN", "MMSOUT", "MMSOUT-DeliveryReport", "MMSOUT-ReadReport". MMSIN format: This record is generated when an MMS message is submitted to the MMSC. 3.) Source IP from which the request was received. In operator environments, this is usually the WAP gateway for regular user-to-user MMS. 4.) User account that submitted the MMS. This can either be a phone number, or a text string prefixed with "VASP:" if the message was submitted by an "MMSC VASP" account (e.g., "VASP:xyz" would signify the message was submitted by "MMSC VASP" account "xyz"). 5.) Message recipient (e.g., phone number or e-mail address). If the message submission contains multiple recipients, multiple log entries will be generated. 6.) Local MMS Message ID or external route name. 6a.) If the message recipient is being processed by the MMSC directly, a local MMS message id will be in this field. Local MMS message ids have a format of YYYYMMDD/HH/XXXXXXXX. If the message is converted to SMS for delivery, the message id could have a format of ##/##/######. 6b.) If the MMS message is being routed to an external routing ("MMSC Routing" definition), this field will contain "VASP:" followed by the name of the routing definition (e.g., "VASP:xyz"). 7.) Transaction id. 7a.) If the MMSC is performing direct MMS delivery to another local user, this will be the ID associated with the SMS transaction. One thing that I personally do not like about this log is that when direct MMS delivery is performed, there are normally 2 SMS transactions created. The log contains one entry for each SMS transaction, meaning that a single MMS submission to a single recipient may generate multiple log entires with matching MMS message ids, but different transaction ids. 7b.) If the MMSC is converting to an SMS for delivery, the transaction id will appear as "unknown". 7c.) If the MMSC is routing to an external "MMSC Routing" definition, this will be an ID associated with the transaction. (A corresponding MMSOUT record will be generated when the transaction is dispatched to the external "MMSC Routing".) 8.) MMS Message Size MMSIN-DeliveryReport format: This record is generated when an MMS delivery report message is submitted to the MMSC (or generated by the MMSC because the user requested delivery confirmation). The format is the same as "MMSIN" with the following exceptions/notes: 3.) Source IP address will be blank if the message was generated by the MMSC directly. 4.) If the MMSC generated this message, it uses a reserved user account that identifies itself as "sms:localsystem". 6.) The MMS Message ID should be the same as the id of the originally submitted message. However, until recent updates, a new message id was generated and recorded here. MMSIN-ReadReport format: This record is generated when an MMS read report message is submitted to the MMSC because the sending user requested a read receipt. The format is the same as "MMSIN" and "MMSIN-DeliveryReport". Note that until very recent updates to NowSMS, this transaction was logged as "MMSIN-DeliveryReport" instead of "MMSIN-ReadReport". MMSRetrieve format: 3.) IP address from which the request to retrieve the content of the MMS message was received (i.e., recipient IP address). 4.) Sender address that sent the MMS message. 5.) Recipient address that is retrieving the MMS message. 6.) MMS Message ID. Note that this usually includes a ".MMS" suffix that was not present in the "MMSIN" record that originally recorded the message submission. Note that this records all URL requests to the MMSC (without the leading "/"). It is common to see entries where this field is blank. This happens because in many phones, the MMSC address is set as the "home page" for a connection profile ... if a user tries to use that "connection profile" with their browser, the browser will attempt to connect to the root URL of the MMSC. In these cases, the "#7" entry will record a status of "FAILED". 7.) Message retrieval status ... "OK" or "FAILED". This status can be "FAILED" if the client connection is closed before the entire MMS message is transmitted. It can also be "FAILED" if an invalid MMS message id (or URL) is requested ... or if a valid MMS message id is requested without the appropriate recipient credentials (e.g., a user fishing for the MMS messages of others) ... or if the MMS message being requested has expired. 8.) MMS Message Size SMTPIN format: This is mostly a legacy transaction, as legitimate SMTP (or MM4) to MMS transactions would be recorded as "MMSIN" transactions. However, it is still used if "E-Mail to SMS" is enabled ... and for recording all rejected SMTP transactions. 3.) Source IP from which the request was received. 4.) Sender address or authenticated user (SMTP AUTH). 5.) Recipient address. 6.) Unused. Does report "REJECTED" for rejected transactions. 7.) Transaction ID for e-mail to SMS ... or "REJECTED". 8.) Unused. MMSOUT Format: This transaction records when an MMS message is routed to an external "MMSC Routing" definition. 3.) "MMSC Routing" Definition to which the message is being routed, prefixed with "VASP:" (e.g., "VASP:xyz"). 4.) Sender address (not sender account) 5.) Recipient address 6.) Status ... "OK" or "FAILED" 7.) Transaction id ... match with transaction id of corresponding "MMSIN" record. 8.) MMS Message Size MMSOUT-DeliveryReport format: This transaction records when an MMS delivery report is routed to an external "MMSC Routing" definition. The format is the same as "MMSOUT". MMSOUT-ReadReport format: This transaction records when an MMS read report is routed to an external "MMSC Routing" definition. The format is the same as "MMSOUT". Note that until very recent updates to NowSMS, this transaction was recorded as "MMSOUT-DeliveryReport". | |||
