Does NowMMSC support ReadRplyReport from mobile handset via HTTP/WA...

Does NowMMSC support ReadRplyReport from mobile handset via HTTP/WA... SearchSearch
Author Message
Frank Grygus
Unregistered guest
Posted on Wednesday, August 18, 2004 - 12:12 am:   

I am able to send MMS messages from the NowMMSC to a GSM mobile handset via SMPP connection through SMSC Aggregator; and the NowSMS/MMSC gateway is internet accessible so the phone can download contect via HTTP/WAP session.

I set the ReadRplyReport flag in my application, and successfully deliver the MMS message with read receipt set. The GSM phone acknoledges that the sender marked the message for read receipt, and then asks the user if OK to send read receipt. I click "OK", traced on NowMMSC port 80, and saw that the phone did reply back to the NowMMSC. The NowMMSC does not appear to act on the read receipt report.

What am I missing? or doing wrong? Is it supported
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 3291
Registered: 10-2002
Posted on Wednesday, August 18, 2004 - 03:18 pm:   

Hi Frank,

One of the limitations to the design of the MMS protocols is that the phone is always going to generate its response back to the MMSC that has been pre-configured on the phone.

So the read reply report is going to go back through the MMSC that has been configured on the phone.

-bn
Frank Grygus
Unregistered guest
Posted on Wednesday, August 18, 2004 - 03:30 pm:   

Bryce,

I agree with your assessment. However, the SonyEricsson T616 does have a visible parameter(as I suspect many other phones do too), which the end user(me) can change to point to a different MMSC. I changed the value to point to my internet accessible NowMMSC, and did see through TCP traces that the phone contact the NowMMSC via HTTP/WAP(port 80) and delivered a READ RECEIPT. Can the NowMMSC act on that, and send the delivery receipt back to my application. The original sender address was preserved in the READ RECEIPT, and I do have a static MMS Route that should get back to my VASP. The MMS Route works to my VASP because I do get DELIVERY REPORTS.

I can provide you the an email trace of that message?

Frank
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 3299
Registered: 10-2002
Posted on Wednesday, August 18, 2004 - 04:36 pm:   

Frank,

Yes, changing the MMSC will work. I just figured that if you were not seeing any activity on the MMSC's HTTP port, that the MMSC setting on the phone was pointing elsewhere.

I checked the log that you sent me via e-mail.

There is a read receipt coming in, but it is likely that the MMSC does not know how to route the recipient.

The read receipt gets routed back like a normal MMS message, and it is going to be sent back to the sender of the original message.

In this particular case, it appears that the original sender was "xxxxxxxMMSC".

My advice would be to setup a special sender address, something like 99999999. Use that as the sender address when sending messages.

In the MMSC Routing definition, then define 99999999 (or 9999*) as an address that gets routed back to your application.

You could probably also add your text string sender name in there as well. I believe we would route it properly back to your application then, but I'm not 100% positive as I have not tried that.

-bn
Frank Grygus
Unregistered guest
Posted on Thursday, August 19, 2004 - 05:36 pm:   

Bryce,

The original sender address was "xxxxxxxMMSC". That is the same address used for DeliveryReports, and that route worked. That was the special route I added to the MMSC Routing tab which point back to my VASP Account. The ReadReplyReceipt is coming back with the same sender address.

I don't think SMSC's likes ASCII characters in sender addresses because my stuff locked up majorly this morning on me and I couldn't even reboot the server remotely - had to get someone to physically power cycle the machine. So I will try this test again with numberic sender address as you suggested.

Frank