| NowSMS does not send the MMS Delivery Report |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - MMS & Advanced Issues ⬆ Archive through June 06, 2005 ⬆ |
◄ ► |
| Author | Message | |||
| Eddy Kvetny New member Username: Eddyk Post Number: 6 Registered: 11-2004 |
Hi, I can't trigger sending the MMS Delivery Report by the NowSMS MMSC application. I tried doing it in two ways: 1. I pre-compiled an MMS message using MMSCOMP. Both "X-Mms-Delivery-Report: Yes" and "FROM" (with phone number and "/TYPE=PLMN" suffix )header were added to the header file. Then I uploaded and sent the composed message using "Send MMS Message" via the WEB interface 2. I composed the whole message adding all content files via "Send MMS Message", specified the FROM data putting the international phone number, checked the "Delivery Report" option on the web page and then submitted. In both cases my MMS client succesfully got a notification and then retrieved a message from MMSC but no MMS Delivery Report was sent by NowSMS MMSC. As I see for both cases no <msg>.INI file was created under the specific folder in MMSCDATA dir (I saw this file created and updated with a delivery status only when a message is sent to NowSMS using M-Send.req). Don't see anything suspisious in MMSCDEBUG log file. Can the reason for non-sending MMS Delivery Report be the fact that the MMS message is sent and received by the same MMS client (of course, using the same PLMN phone number) ? Actually, it does not pose any problem for rest of MMS transactions. Thanks in advance for any idea | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 3771 Registered: 10-2002 |
Hi Eddy, I don't see that problem on my system. But, it is an interesting observation that you see that no <msg>.INI file is created. That gives me a clue. Go into the "MMSC Routing" page. Add a new connection ... any connection ... let's say this: Account name: x Route Messages to this account for recipient phone number(s): 99999999999999999 Route messages to VASP via: Convert to Multimedia WAP Push Everything else can be left blank. Try it again. If any "MMSC Routing" definitions are defined, this changes how the web interface submits messages. By default, the web interface bypasses the MMSC. However, if there are any "MMSC Routing" definitions defined, the web interface will route the message properly through the MMSC ... and you will see the <msg>.INI file and the delivery notification will be generated properly. -bn | |||
