| Let me know MMSC log's meanings |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - MMS & Advanced Issues ⬆ Archive through February 20, 2004 ⬆ |
◄ ► |
| Author | Message | |||
| lovehyun Unregistered guest |
Hi I am testing MMS Send/Receive. but my mobile phone always displays "Invalid server response" I got the MMSC Log in my PC. 2003-10-27 09:29:49,MMSRETRIEVE,165.213.141.225,,,20031027/09/3F9C66EDa.MMS,OK,63 2003-10-27 11:16:34,MMSIN,165.213.143.87,admin,,User Not Defined,FAILED 2003-10-27 11:17:48,MMSIN,165.213.143.87,admin,,User Not Defined,FAILED 2003-10-27 11:29:33,MMSIN,165.213.143.87,+1234,hyungoo.ji@samsung.com,20031027/11/35E33B8C, 00000180.RFC,610 2003-10-27 11:29:42,MMSIN,,MMS.Delivery@samsung.com,+1234,20031027/11/3976ECCA,SAR-+1234-16 -2-1.req,317 2003-10-27 11:29:42,MMSIN,,MMS.Delivery@samsung.com,+1234,20031027/11/3976ECCA,SAR-+1234-16 -2-2.req,317 2003-10-27 11:29:54,MMSIN,165.213.143.87,+1234,+1234,20031027/11/EA68C589,SAR-+1234-17-2-1. req,602 2003-10-27 11:29:54,MMSIN,165.213.143.87,+1234,+1234,20031027/11/EA68C589,SAR-+1234-17-2-2. req,602 2003-10-27 11:44:47,MMSIN,165.213.143.87,+1234,+1234,20031027/11/910C8908,SAR-+1234-18-2-1. req,602 2003-10-27 11:44:47,MMSIN,165.213.143.87,+1234,+1234,20031027/11/910C8908,SAR-+1234-18-2-2. req,602 I want to know the Log's meanings about each cases and I use also test Wap Gateway in another PC. | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 976 Registered: 10-2002 |
I don't think any of this is related to the error that you are seeing. I assume that you are getting an error back on your phone each time that you attempt to send a message? However, I don't see any indication of a problem in this area in the logs. In the log above, what I see is this:
Ignore that one for now ... it looks like a message was sent from the web interface and this is most likely just a loopback validation of the MMSC URL.
The above entries are also probably insignificant. An attempt was made to connect to a URL of "/admin".
An MMS message was submitted by "+1234", to send to "hyungoo.ji@samsung.com".
This is a delivery report going back to "+1234". Most likely based upon this log, this is a non-delivery report. The SMTP server probably was not able to send the message through the configured relay host, so a non-delivery notification is going back to the sender. An MMS notification for this non-delivery message is being queued for delivery via SMS (2 part SMS).
These are 2 MMS messages being sent from "+1234" to "+1234". MMS notifications are being queued for delivery via SMS. So where to go from here Based upon your e-mail address, I'm assuming that you're a handset developer. So I'm going to take a rather technically oriented approach. I'd suggest enabling debug mode on the MMSC. Manually edit MMSC.INI, and under the [MMSC] section header, add Debug=Yes. Then restart the MMSC service. Repeat your attempt. As the MMSC runs, it will create an MMSCDEBUG.LOG file. This file will contain complete hex dumps of a lot of the data sent and received ... and I think you should see a hex dump of the HTTP response from the MMSC to your request. Since the WAP gateway is going to translate the HTTP response, you might need to take a closer look at the data that the handset is receiving back from the WAP gateway. (Ethereal is a great tool for analysing this type of communication.) | |||
