| Duplicate notifications and MMS |  Search
|
|
NowSMS Support Forums ⬆ MMS & SMS Technical Discussions (unsupported) ⬆ Archive through October 05, 2005 ⬆ |
◄ ► |
| Author | Message | |||
| Stuart Walker Unregistered guest |
help me please Bryce!!!!!!!!!!!! Here's the situation. Device under test is a development feature phone, network is a UK MVNO, MMS client is Teleca. In static and dynamic environment testing MT MMS using GPRS manual attach the device successfuly receives the MMS as either a complete auto download or as a manual download after receipt of an SMS notification (Depending on network conditions). So far so good. Except for the fact that duplicate notifications and complete downloads are received.Not just once but more times than I care to admit. From what I understand a repeat delivery occurs when the M-NotifyResp.ind message is sent to the URL for the MMSC that has been configured in the phone, which does not have any relationship to the URL of the retrieved MMS message. So it assumes a single MMSC environment (which is one of the reasons that we do not currently perform the retry, as we are frequently used as a secondary MMSC There are some MMSCs that will retry the notification on a very aggressive schedule, and a device that has not returned the acknowledgement M-NotifyResp.ind will keep receiving the MMS notification. So my questions are: Why the hell do I keep getting duplicates when my trace says that I am returning the M-NotifyResp.ind correctly? And, Do high end competitor handsets mask or reject duplicates? Thanks, Stu | |||
