| Unable to send MMS |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - MMS & Advanced Issues ⬆ Archive through April 21, 2010 ⬆ |
◄ ► |
| Author | Message | |||
| Michal Dolkowski New member Username: Adventure Post Number: 1 Registered: 08-2009 |
I just started with NowSMS and I have problem with sending MMS using NowSMS (they work properly when send from PC where application is installed), i got such errors when trying: MMSC log: 2009-08-13 16:57:35,MMSIN,193.23.132.45,VASP:mms,+48508xxxxxx,VASP:mms,574D391E.MMS,8885 2009-08-13 16:57:52,MMSOUT,VASP:mms,52xxxxxxx/TYPE=PLMN,+48508xxxxxx,FAILED,574D391E.MMS,90 51 2009-08-13 16:57:52,MMSIN-DeliveryReport,,SMS:localsystem,52xxxxxxx,VASP:mms,2F14409A.MMS,6 3 2009-08-13 16:57:53,MMSOUT-DeliveryReport,VASP:mms,+48508xxxxxx/TYPE=PLMN,52xxxxxxx,FAILED, 2F14409A.MMS,16 MMSCDebug LOG 16:57:52:140 [10] ThreadProcessVASPQ: Packet Length is 126 bytes 16:57:52:140 [10] ThreadProcessVASPQ: 48 54 54 50 2F 31 2E 30 20 32 30 30 20 4F 6B 0D HTTP/1.0 200 Ok 16:57:52:150 [10] ThreadProcessVASPQ: 0A 43 6F 6E 74 65 6E 74 2D 74 79 70 65 3A 20 61 Content-type: a 16:57:52:150 [10] ThreadProcessVASPQ: 70 70 6C 69 63 61 74 69 6F 6E 2F 76 6E 64 2E 77 pplication/vnd.w 16:57:52:150 [10] ThreadProcessVASPQ: 61 70 2E 6D 6D 73 2D 6D 65 73 73 61 67 65 0D 0A ap.mms-message 16:57:52:150 [10] ThreadProcessVASPQ: 43 6F 6E 74 65 6E 74 2D 6C 65 6E 67 74 68 3A 20 Content-length: 16:57:52:150 [10] ThreadProcessVASPQ: 34 30 0D 0A 0D 0A 8C 81 98 41 44 34 46 43 41 44 40 AD4FCAD 16:57:52:150 [10] ThreadProcessVASPQ: 44 00 8D 90 92 83 93 6D 65 73 73 61 67 65 2D 66 D message-f 16:57:52:150 [10] ThreadProcessVASPQ: 6F 72 6D 61 74 2D 63 6F 72 72 75 70 74 00 ormat-corrupt 16:57:52:150 [10] ThreadProcessVASPQ: MM1 - got http ok response 16:57:52:150 [10] ThreadProcessVASPQ: Packet Length is 40 bytes 16:57:52:150 [10] ThreadProcessVASPQ: 8C 81 98 41 44 34 46 43 41 44 44 00 8D 90 92 83 AD4FCADD 16:57:52:150 [10] ThreadProcessVASPQ: 93 6D 65 73 73 61 67 65 2D 66 6F 72 6D 61 74 2D message-format- 16:57:52:150 [10] ThreadProcessVASPQ: 63 6F 72 72 75 70 74 00 corrupt 16:57:52:150 [10] ThreadProcessVASPQ: MM1 - no message id in response 16:57:52:150 [10] ThreadProcessVASPQ: MM1 - MMS Response Status indicates error 16:57:52:270 [6] ThreadRouteSMTPIn: 90CF875C.RFC 16:57:52:270 [6] ThreadRouteSMTPIn: X-Mms-Message-Type: MM4_delivery_report.REQ 16:57:52:270 [6] ThreadRouteSMTPIN: X-Mms-Message-Type: m-delivery-ind 16:57:52:270 [6] ThreadRouteSMTPIn: X-MMSC-RCPT-TO: 523491862/TYPE=PLMN 16:57:52:270 [6] ThreadRouteSMTPIn: To: 52xxxxxxx/TYPE=PLMN@193.23.xxx.xxx 16:57:52:270 [6] ThreadRouteSMTPIn: X-Mms-Message-ID: "20090813/16/88B9D5E0@193.23.xxx.xxx" 16:57:52:270 [6] ThreadRouteSMTPIn: X-Mms-Status: Rejected 16:57:52:270 [6] ThreadRouteSMTPIn: X-Mms-MM-Status-Code: Rejected 16:57:52:270 [6] ThreadRouteSMTPIn: X-MMSC-Auth-User: localsystem 16:57:52:270 [6] ThreadRouteSMTPIn: Sender: system-user@ 16:57:52:270 [6] ThreadRouteSMTPIn: From: +48508xxxxxx/TYPE=PLMN 16:57:52:270 [6] ThreadRouteSMTPIn: Subject: Not Delivered: call from 52xxxxxxx 16:57:52:290 [6] MMSRoutingCallback: 52xxxxxxx/TYPE=PLMN 16:57:52:290 [6] MMSRoutingCallback: 52xxxxxxx/TYPE=VASP:mms 16:57:52:290 [6] DeliverMMSMessage: Message ID 20090813/16/88B9D5E0@193.23.xxx.xxx receipt originally came from 52xxxxxxx via mms 16:57:52:290 [6] DeliverMMSMessage: Message ID 20090813/16/88B9D5E0@193.23.xxx.xxx receipt should route via mms 16:57:52:290 [6] DeliverMMSMessage: 52xxxxxxx/TYPE=VASP:mms 16:57:52:290 [6] DeliverMMSMessage: Found VASP Recip - mms 16:57:52:290 [6] DeliverMMSMessage-VASP: 52xxxxxxx 16:57:53:151 [10] ThreadProcessVASPQ: recipArray count = 1 16:57:54:153 [10] ThreadProcessVASPQ: Before WSPRasHangUp (#3) - Modem: ZTE Proprietary USB Modem 16:57:56:336 [10] ThreadProcessVASPQ: After WSPRasHangUp (#3) - Modem: ZTE Proprietary USB Modem 16:57:56:336 [10] ThreadProcessVASPQ: Before ModemRelease - ZTE Proprietary USB Modem 16:57:56:336 [10] ThreadProcessVASPQ: After ModemRelease - ZTE Proprietary USB Modem Would appreciate any help/suggestions. Regards | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 1141 Registered: 08-2008 |
Hi Michal, I need to see the part of the MMSCDEBUG.LOG before that in order to better understand what might be corrupt. For the "MMSC Routing" definition in NowSMS ... make sure that "Default Sender Address" is blank, and that "Allow Sender Address Override" is NOT checked. That is the most common problem. Aside from that, what is the content that you are sending? There may be a MIME type issue. Do MMS messages that contain only text work? -- Des NowSMS Support | |||
| Michal Dolkowski New member Username: Adventure Post Number: 2 Registered: 08-2009 |
Des I did as you suggested - however there still is a problem. MMS contains voice message Below you can see log that you asked (if thats not enough tell me how much more do you need). 16:57:35:526 [11] MMSRoutingCallback: +48508xxxxxx/TYPE=PLMN 16:57:35:526 [11] MMSRoutingCallback: +48508xxxxxx/TYPE=PLMN 16:57:35:526 [11] DeliverMMSMessage: TO: +48508xxxxxx/TYPE=VASP:mms 16:57:35:526 [11] DeliverMMSMessage: Found VASP Recip - mms 16:57:35:536 [11] DeliverMMSMessage-VASP: +48508xxxxxx 16:57:35:566 [11] mm7 Recip: TO: +48508037460/TYPE=VASP:mms 16:57:35:566 [11] ProcessMM7Request: HTTP/1.0 200 OK Content-Length: 610 Content-Type: text/xml Connection: close 16:57:35:566 [11] ProcessMM7Request: <?xml version="1.0" ?> <env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"> <env:Header> <TransactionID xmlns="http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-5-MM7-1-2" env:mustUnderstand="1">1250174853-789300</TransactionID> </env:Header> <env:Body> <SubmitRsp xmlns="http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-5-MM7-1-2"> <MM7Version>5.3.0</MM7Version> <Status> <StatusCode>1000</StatusCode> <StatusText>Success</StatusText> </Status> <MessageID>20090813/16/88B9D5E0@193.xxx.xxx.xxx</MessageID> </SubmitRsp> </env:Body> </env:Envelope> 16:57:35:566 [11] ThreadProcessConnection: Processing Complete 16:57:35:576 [11] InternalProcessConnection: Thread ended 16:57:38:480 [10] ThreadProcessVASPQ: recipArray count = 1 16:57:38:480 [10] ThreadProcessVASPQ: Before ModemAllocate - ZTE Proprietary USB Modem 16:57:44:239 [10] ThreadProcessVASPQ: After ModemAllocate - ZTE Proprietary USB Modem - OK 16:57:44:239 [10] ThreadProcessVASPQ: Before WSPRasDial - Modem: ZTE Proprietary USB Modem 16:57:49:005 [10] ThreadProcessVASPQ: After WSPRasDial - OK 16:57:49:226 [10] ThreadProcessVASPQ: POST http://mms.plusgsm.pl:8002/ HTTP/1.1 Content-Length: 8844 Content-Type: application/vnd.wap.mms-message Accept: application/vnd.wap.mms-message Cache-Control: No-Cache Host: mms.plusgsm.pl:8002 Regards Michal | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 1147 Registered: 08-2008 |
Hi Michal, Can you please send me a complete log via e-mail. Send it to nowsms@nowsms.com and put "Attention: Des" in the subject line. Then drop a reply here to let me know to look for it. Before you do that ... here's my thought for what might be wrong ... What is the MIME type for the voice message? Is it audio/amr? (If it's not, the MMSC might not accept it.) Also, make sure that the file extension for the name of the audio file is ".amr". -- Des NowSMS Support | |||
| Michal Dolkowski New member Username: Adventure Post Number: 3 Registered: 08-2009 |
Des Please check your email. Regards | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 1153 Registered: 08-2008 |
Hi Michal, I understand that company restrictions will not allow you to send the log. NowSMS will perform that conversion from MM7 to send out to the client via MM1. But in that type of connection, it will not transcode the content for individual parts of the MMS message (it will decode from base64 if you've used that, but it will not convert the content type). Whatever the content type arriving via MM7 is the content type that will be sent out in the MM1 format message. The mobile operator may limit the content types that they accept via MM1 messages. That's why I was curious to see your debug log, so that I could see the structure of the MM7 message to see if you were using an unusual content type for the audio. If everything is working when sending MMS from the web interface of NowSMS, I would suspect a content-type issue. It is also possible that the MM7 message is not structured properly. We have seen that in some recent postings. So in order to provide a clear answer of what could be going wrong, we really need to see a dump of an example MM7 submission. One other setting that might be an issue. In the "MMSC Routing" definition that you have defined for the the outbound MM1/modem connection in NowSMS, make sure that "Allow Sender Address Override" is NOT checked, and that "Default Sender Address" is blank. Otherwise, if your MM7 request specifies a sender address, NowSMS will try to encode it in the MM1 request, and with most operators that will result in some type of error response. Beyond that, we'd really need to see the MM7 submission. -- Des NowSMS Support | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 1182 Registered: 08-2008 |
Follow-up for others who might be reading this thread. The problem was related to a "Content-disposition: inline" header included in the MM7 submission. We tested with several operator MMSCs which had no problem with this header being present. However, Michal's operator consistently rejected the message as corrupt. As it turns out, the WSP binary multipart encoding for MMS is based upon WAP-203-WSP, but the "inline" attribute for "Content-Disposition:" was not introduced until WAP-230-WSP. NowSMS was incorrectly using the WAP-230-WSP encoding, and that was what confused this particular operator MMSC. NowSMS was updated on 2009.08.20 to not encode the "Content-Disposition:" header for an MMS binary multipart. -- Des NowSMS Support | |||
