X-MMS-Read-Report interpreted as X-MMS-Read-Reply

X-MMS-Read-Report interpreted as X-MMS-Read-Reply SearchSearch
Author Message
Venkat Akella
Unregistered guest
Posted on Friday, April 16, 2004 - 06:24 pm:   

Looks like NowSMS MMSC is interpreting the X-MMS-Read-Report header as X-MMS-Read-Reply. I am sending out a message with this header set and the email generated by NowSMS for my message contains this header as X-MMS-Read-Reply? Any comments?
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 2302
Registered: 10-2002
Posted on Monday, April 19, 2004 - 02:37 pm:   

Hi Venkat,

I assume that you are setting this header when submitting a message from an MMS client.

Essentially, the headers mean the same thing. In the MMS 1.0 specification, the header is defined as "X-MMS-Read-Reply", and in later versions, it is changed to "X-MMS-Read-Report".

The binary encoding and options for this header are the same.

When routing to e-mail, the NowSMS MMSC translates this header to a text format so that if the message gets routed to another NowSMS MMSC, it can be translated. So I don't think it is a problem which version of the text header is used.

It is puzzling that the OMA would change the text description of this header between versions for no good reason.

While I do believe that the new text is more descriptive, the original text is consistent with the 3GPP specification. Even the newer OMA MMS specifications reference in an appendix that the X-MMS-Read-Report header maps to the "Read Reply" header defined in the abstract 3GPP specifications.

Bottom line, it is a little confusing, but there is no difference between the headers.

-bn
Venkat Akella
Unregistered guest
Posted on Tuesday, April 20, 2004 - 06:11 pm:   

Thanks Bryce for the explanation. I didnt know that it was different in MMS1.0. Yeah its not a porblem as the binary encoding is same.