| MMS Send Issue |  Search
|
|
NowSMS Support Forums ⬆ MMS & SMS Technical Discussions (unsupported) ⬆ Archive through November 21, 2009 ⬆ |
◄ ► |
| Author | Message | |||
| Manjunath V New member Username: Manjunathsvbang Post Number: 1 Registered: 06-2009 |
Hi. I am using Testing MMS send using vodafone SIM. When message-id field is present in m-send-conf, MMS is sent successfully to recipient. Sometimes, message-id field is not present in m-send-conf, in this case MMS is not delivered to recipient (Response Status & Response Text fields indicate Message send is successful). Both case Delivery report is requested. Could any one tell where does the problem exist?... | |||
| atifsahib New member Username: Atifsahib Post Number: 1 Registered: 06-2009 |
i m rubab}}}} | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 952 Registered: 08-2008 |
Why don't you post a hex dump of your submission and response. Maybe there's something in the status response that you are missing? What is different about the submissions that work vs. those that do not? | |||
| Manjunath V New member Username: Manjunathsvbang Post Number: 2 Registered: 06-2009 |
Both in Successful and failure case i send same data(MMS). There is no different b/w "submissions that work vs. those that do not" Usually when i try to send big data ( say above 100kb ) message-id field is not present in m-send-conf.In this case, message will not be delivered. Message is delivered only if message-id field is present in m-send-conf I get Response Status = 128, Response Text = Ok (m-send-conf)in both the cases.. | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 958 Registered: 08-2008 |
Exactly the same, byte for byte? The MMSC might consider it to be a duplicate re-transmission. | |||
| Manjunath V New member Username: Manjunathsvbang Post Number: 3 Registered: 06-2009 |
Only Message body is same. MMS PDU data is different.. | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 972 Registered: 08-2008 |
I suggested posting a hex dump of messages that work vs. those that don't. From that maybe someone could offer a suggestion of what is wrong. However, if you say everything is encoded correctly, then I guess it must be ... | |||
| Manjunath V New member Username: Manjunathsvbang Post Number: 4 Registered: 06-2009 |
Hi. Thanks for u response.. I compared messages that work vs. those that don't. Header part is same in both case. Header data: ------------ 8c 80 98 4d 4d 53 5f 54 52 41 4e 53 41 43 54 49 4f 4e 49 44 5f 31 00 8d 92 89 18 80 39 31 39 37 33 39 39 37 39 34 36 33 2f 54 59 50 45 3d 50 4c 4d 4e 00 97 39 31 39 37 33 39 39 37 39 34 36 33 2f 54 59 50 45 3d 50 4c 4d 4e 00 96 53 61 6d 73 75 6e 67 00 8a 80 8f 81 94 81 86 80 90 80 84 1f 1f b3 8a As u say, MMSC might consider as duplicate re-transmission. Then m-send-conf should contain details about this... But message-id field is not present in m-send-conf... | |||
