Can't forward notification from mm1

Can't forward notification from mm1 SearchSearch
Author Message
William Kong
New member
Username: William

Post Number: 1
Registered: 04-2006
Posted on Friday, April 14, 2006 - 03:45 am:   

Hi Bryce,
I have downloaded a 60 dyas trail version "Now SMS/MMS Gateway v2006.03.09". It is quite good for me to run MMS1.2 functions. But now I meet a problem that when forwarding a notification (which means the notification is not downloaed yet) NOWSMS gateway returns an error string "message forward transaction not supported". You can refer to OMA MMS1.2 Encapsulation Protocol document "OMA-MMS-ENC-V1_2-20050301-A.pdf", items from "MMSEFWD-C-001" to "MMSEFWD-C-025".
Can you tell me whether the trail version really disable it? If I purchase the license can the gateway support it? And it really support MMS1.3 all standard?

Thank you very much!
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 5790
Registered: 10-2002
Posted on Tuesday, April 18, 2006 - 08:59 pm:   

Hi William,

The m-forward-req transaction is optional in the MMS 1.2 specification. (You'll notice an "O" in the "Status" column of the tables that you reference.) It is not required to be supported in order to conform to the specification.

In reference to optional MMS 1.2 features, we do support the read receipt PDUs, but we do not currently support m-forward-req (forward without downloading) or the MMBox functions.

It is our intent to support the m-forward-req PDU, however, we did not complete this prior to the first NowSMS 2006 release. We are planning an update release early next week, and expect support for m-forward-req to be included in the update release.

MMBox support is still being investigated, and we have not made any commitments for MMBox support, as we do not expect this functionality to be widely implemented in the real world (although it appears to be used in Japan). (If anyone has an MMS client with MMBox support, we would be interested in testing it.)

Regarding MMS 1.3, we are still evaluating the candidate release of the specification. Unfortunately, most of the new features of MMS 1.3 are also considered "optional" in the conformance specification, which is unfortunate, as it causes confusion.

The primary new optional protocol features of MMS 1.3 seem to be application level addressing, as well as the delete and cancel PDUs. While the delete and cancel PDUs appear to offer little new functionality, application level addressing is an exciting new capability. Unfortunately, JSR-205 implemented its own method of attempting to support application level addressing for MMS, so it remains to be seen how this will mesh with the different mechanism defined in MMS 1.3.

I expect that we'll be adding support for the optional MMS 1.3 application level addressing features, as well as the delete PDU in the next several months (probably along the same timeline in which the MMS 1.3 specification becomes an official release).

In any event, support for the MMS 1.2 optional m-forward-req transaction will be present in next week's update.

-bn
William Kong
New member
Username: William

Post Number: 2
Registered: 04-2006
Posted on Wednesday, April 19, 2006 - 08:25 am:   

Hi Bryce,
Thank you very much for the detailly feedback. Now I'm waiting for the next week coming:-)
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 5853
Registered: 10-2002
Posted on Thursday, April 27, 2006 - 07:52 pm:   

Follow-up. Update posted to support "m-forward-req". See details at http://support.nowsms.com/discus/messages/53/15129.html.