| MMSCLOG |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - MMS & Advanced Issues ⬆ Archive through May 02, 2013 ⬆ |
◄ ► |
| Author | Message | |||
| zak New member Username: Zak Post Number: 3 Registered: 12-2010 |
Hi Support, According from MMSCLOG.Can you explain the reaaon why after it showed "OK" it will also showed "FAILED - Unable to deliver message,38C4E734.MMS".Is it these MMS deliver to user? please clarify. Thanks, Example as below:  | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 2776 Registered: 08-2008 |
There should be more information that follows the text which includes a provider-specific error code. What type of MMSC connection is being used? | |||
| zak New member Username: Zak Post Number: 4 Registered: 12-2010 |
Hi Des, Im using MM1 protocol connecting with my GSM modem. Is it error from provider or from my side? are the user successfully receive my MMS? Thanks, | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 2777 Registered: 08-2008 |
Hi Zak, Is there any information that follows that error message in the log? (I'd rather see it as full text than as a screen capture.) I would suggest enabling the MMSCDEBUG.LOG and MMSWAPDEBUG.LOG, and trying to capture some failed message transmissions in those logs, as they will provide greater insight. Also, is this DiGi in Malaysia? Try changing the WAP Gateway IP Address setting in your "MMSC Routing" definition for "Digi" to: http://203.92.128.160:80 (Include the "http://" prefix, as this tells NowSMS to use a WAP2/HTTP interface instead of WAP/WSP.) -- Des NowSMS Support | |||
| Abhishek New member Username: Abhisheknovosolbiz Post Number: 1 Registered: 09-2011 |
Hi Support, I have the following entries in the MMSC log file. 2011-08-29 17:18:04,MMSIN,127.0.0.1,,601326*****,VASP:Maxis,C737CA92.mms,202715 2011-08-29 17:18:58,MMSOUT,VASP:Maxis,,601326*****,OK,C737CA92.MMS,202943 However, the MMS was not delivered on the handset. Can I consider the MMSOUT to be a delivery confirmation log? Thanks, | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 3438 Registered: 08-2008 |
Hi Abishek, The MMSOUT entry indicates that the message was transmitted over MM7, and the MM7 server accepted the message for further processing. This does not provide any indication of what happened after the message left NowSMS. It is possible to receive delivery reports, but that is a more complicated configuration as you must setup a receiver/VASP account on your NowSMS, and the provider must configure their system to initiate a connection to you to deliver messages and delivery reports. For more info on this setup see http://www.nowsms.com/connecting-to-an-operator-mmsc-with-mm7 Talking about delivery reports doesn't get us that much closer to resolving your problems, as it may take your provider some time to configure this. So my question would be...does this happen with every message you try to send, or only certain messages? One of the most common issues that causes MMS messages to be dropped is if you are not following the policies of the operator. For example, the MMS sender address....do you have a Default Sender Address configured? Has the operator assigned a particular short code for you to be using? -- Des NowSMS Support | |||
| Abhishek New member Username: Abhisheknovosolbiz Post Number: 2 Registered: 09-2011 |
Hi Des, Appreciate the prompt response. No, the said problem does not happen with every message but randomly on some messages. In fact, the same message sent to the same MSISDN later was delivered. I am using a GSM modem with a prepaid sim card to send these MMS hence do not have a short code. In the MMSC routing setting I am using MM1 as the configuration to route messages to VASP. Could that be the reason for the failed delivery? Is there any documentation I can check out for configuring the delivery notifications in this case? Thanks, Abhishek | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 3446 Registered: 08-2008 |
Hi Abishek, I'm sorry, I don't know why I assumed you were using MM7 ... I must have gotten you confused with another question. In the case of MM1, make sure that "Default Sender Address" is blank ... and that "Allow sender address override" is NOT checked. You can request a delivery receipt when submitting an MMS message. If you are using HTTP to submit, add MMSDeliveryReport=Yes as one of the parameters. Unfortunately, these delivery reports cannot be posted back to you via HTTP, but if you configure NowSMS to receive MMS messages via your modem, they will appear as received MMS messages that can be viewed in NowSMS. It may be worth requesting delivery receipts to see if these receipts provide any additional problem information. As the problem is intermittent, the other question I would ask is whether the messages that are not received are larger than ones that are received. Sometimes to send larger messages, it is necessary to use a WAP2/HTTP proxy (the default settings we supply with NowSMS use WAP1/WSP). For Maxis in Malaysia, try changing the WAP Gateway address configured for the MMS settings in NowSMS to http://202.75.133.49:80 (include the http:// prefix to tell NowSMS that this is a WAP2/HTTP gateway, instead of a WAP1/WSP gateway). -- Des NowSMS Support | |||
