| MMSC log? |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - MMS & Advanced Issues ⬆ Archive through July 14, 2004 ⬆ |
◄ ► |
| Author | Message | |||
| Peter Nyquist Unregistered guest |
Is it possible to see a log for the MMSC? I would like to see why the MMSC rejects my SOAP format as being invalid. | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 2262 Registered: 10-2002 |
Hi Peter, First suggestion ... if you have the v5.0 version of NowSMS, update to the v5.01 version, which is the current download from this web site. There were some parsing problems in v5.0, errors parsing some recipient formats, and an error parsing a request that included binary content that was not base64 encoded. There is also a beta version of v5.50, it would also be worth trying that version. I'm not aware of any specific issues related to inbound MM7 parsing that were fixed in this update, but there could be some subtle changes as I know the MM7 output was tweaked substantially. (http://www.nowsms.com/newsletter to find links for the v5.50 beta.) Beyond that, what is the error message that you are receiving back? It would appear in the <Details> element. I can often tell you what the error is based upon the text of the error that you receive back. Since this would probably be a useful resource, I'll go ahead and list some of the current error messages that could be returned: "No Valid Recipients" - We were unable to parse any recipients out of the MM7 header. "Message Quota Exceeded" - The message quota defined for the VASP account has been execeeded. "Error Delivering Message" - Internal error, should not happen. "Insufficient Memory" - Internal error, should not happen. "Multipart MIME boundary invalid or missing" - Could not find a "boundary=" parameter associated with the "Content-type:" header of the request. "Invalid MIME boundary" - Could not locate the MIME boundary defined in the header anywhere in the posted data. (This boundary would define the start of the first part of the multipart.) "Closing MIME boundary not found" - Could not locate the MIME boundary that would close the first part of the multipart data. "Second MIME content part not found" - Could not find any content in the second part of the multipart data. "Closing MIME boundary for second content part not found" - Could not find the MIME boundary that marks the end of the second part of the multipart data. "Unsupported MM7 Transaction" - Request was of the content type "text/xml", and the request was not of the DeliveryReportReq type. (SubmitReq and DeliverReq are also supported, but they do require that the content type be a "multipart/" type.) "Missing transaction id in request" - Request was of the content type "text/xml", and the request did not include a "TransactionID", which is required in a DeliveryReportReq request. "Unsupported content type in request" - Content type of the request was not a "mutlipart/*" type or "text/xml". The request must have one of those content types. I hope that helps. Also, there is a debug log that can be enabled in NowSMS. Edit MMSC.INI, and under the [MMSC] section header, add Debug=Yes. Then restart the service. The gateway will produce an MMSCDEBUG.LOG as it runs. This log may contain additional information about your post. -bn | |||
