About PDU Read Report

About PDU Read Report SearchSearch
Author Message
bamboo
New member
Username: Bamboo

Post Number: 3
Registered: 08-2006
Posted on Friday, October 27, 2006 - 12:28 pm:   

Hi!
We want to send a PDU read report through nowsms, can we do it?
We can send MMS read report through nowsms, but we don't know how to send a PDU read report?
Can you help me?
Thanks very much!!!
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 6771
Registered: 10-2002
Posted on Wednesday, November 01, 2006 - 06:31 pm:   


quote:

We can send MMS read report through nowsms, but we don't know how to send a PDU read report?




I'm sorry, but I don't understand the difference between these two things. To me, they are the same.

Can you please clarify what you are trying to do with more detail?
bamboo
New member
Username: Bamboo

Post Number: 4
Registered: 08-2006
Posted on Thursday, November 02, 2006 - 01:11 pm:   

I'm sorry!
I mean that MMS read report have two forms, one is the MMS form read report, another is the PDU form read report. We can send a MMS form read report, but we don't know how to send PDU form read report. Can we do it use nowsms? The nowsms that We bought is the latest version.
Can you help me to test the PDU read report function?

I also have another question:
We want to test the mobile phone reject MMS function, so we set the mobile phone is reject MMS mode, but it seems that the nowsms(MMSC) cann't delete the MMS notification which belong to the Mobile phone when the phone send delete request.
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 6801
Registered: 10-2002
Posted on Tuesday, November 07, 2006 - 10:14 pm:   


quote:

I mean that MMS read report have two forms, one is the MMS form read report, another is the PDU form read report. We can send a MMS form read report, but we don't know how to send PDU form read report. Can we do it use nowsms? The nowsms that We bought is the latest version.
Can you help me to test the PDU read report function?




I'm still confused.

Maybe it would help if we used the terminology from the MMS encapsulation protocol specification?

I think you are saying that you currently generate a "Multimedia Message Read Report", as described in Section 6.7.1 of that specification. This is just a standard MMS message that includes text that indicates that the message has been read ... there is no standard format for this.

But you want to generate a PDU Read Report, as described in Section 6.7.2.

If so, then you should just generate one. Send an M-Read-Rec.ind PDU back to the MMSC.

The MMSC will then generate an M-Read-Orig.ind PDU back to the original message sender ... or the MMSC might convert the read receipt into a "Multimedia Message Read Report". For each user defined to the MMSC under "MMSC Users", the MMSC remembers what "MMS Version" the client specfied in its last request to the MMSC. If the client specfied MMS 1.1 or higher, then the MMSC will send an M-Read-Orig.ind PDU. If the recipient has never sent a message to the MMSC, or the recipient is not defined to "MMSC Users", then the client is assumed to be MMS 1.0, and the read report is converted to a "multimedia message read report".

It is possible to change the default MMS version that NowSMS assumes is supported for unknown recipients by editing MMSC.INI, and under the [MMSC] header, adding DefaultMMSVersion=1.2


quote:

We want to test the mobile phone reject MMS function, so we set the mobile phone is reject MMS mode, but it seems that the nowsms(MMSC) cann't delete the MMS notification which belong to the Mobile phone when the phone send delete request.




Do you mean send an M-NotifyResp.ind message with a status value of "rejected" (or similar)? That is a good point, we do not use this request to delete a notification.

By default, this doesn't matter, as we don't retry notifications. But now that there are options for retrying notifications, we should be supporting this request for deleting a pending notification. I will put this into the development queue.