| MMS 1.1 |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - MMS & Advanced Issues ⬆ Archive through December 19, 2005 ⬆ |
◄ ► |
| Author | Message | |||
| Deepesh Aggarwal New member Username: Deepesha Post Number: 9 Registered: 02-2005 |
I am using NOWSMS Gateway v5.51 (b20040823). Does it suport MMS 1.1 ? If yes then how to setup MMSC to use 1.1? It supports 1.0 that I can see from the logs. Do let me know if you need any other information. Would appreciate a quick response in this regard. | |||
| Deepesh Aggarwal New member Username: Deepesha Post Number: 10 Registered: 02-2005 |
Hi Bryce, You seem to be quite busy these days..:-) I posted one of the query regarding MMS 1.1 about two weeks back and still waiting for the response. Anyways, I hope to get a quick response for this one. Have a query about Delivery indicator. I am able to get delivery indicator from the NowSMS with "Retrieved" status, if I sucessfully retrieve the message and responds back with "Retrieved" status in notification response indicator ( assuming immediate delivery). But NowSMS does not generate any Delivery indicator with "Rejected"or "Expired" status if I responds back to NOwSMS with the "Rejected"or "Expired" status in notification response indicator (without actually retrieving the messgae). Does NowSMS has the capability to generate Delivery indicator with "Rejected" or "Expired" status? If yes, then under what scenario exactly it does that? I would appreciate your response in this regard. | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 4668 Registered: 10-2002 |
Hi Deepesh, Sorry, a combination of vacation and then work backlog has left me playing "catch up" on the discussion board. We will be adding MMS 1.2 support (and 1.1, which never really caught on) in a new release before the end of the year (excpected late 3Q, early to mid 4Q). Primarily this will just be adding support for the read receipt related PDUs. We may do a rudimentary implementation of MMBox functions, but their implementation is "optional" according to the MMS spec, so they don't have to be implemented in order to be considered MMS 1.2 compliant. (In fact, the read receipt PDUs are also consider optional, but we believe that in the real world, MMS 1.2 clients will assume that they are implemented.) If you are working with an MMS 1.2 (or 1.1) client, I would advise updating to the v5.51b patch (http://support.nowsms.com/discus/messages/53/9502.html). There is a requirement in the MMS 1.x specs that all MMS 1.x clients and servers must be able to support other 1.x implementations, regardless of the subversion. And there is one thing that we were not doing correctly, which could confuse an MMS 1.2 (or 1.1) client. Namely, if the client issues a request for a PDU that we do not support, we were not returning the proper error response. While these additional PDUs are all optional for implementation for an MMS 1.2 compliant server (so there is no required functionailty missing by their advance), it is a requirement that the server tell the client that the PDU is not supported. v5.51b fixes the problems that we have in that area. We do not generate "rejected" or "expired" statuses. There is a possibility that we may be supporting an "expired" status report in the next major release. We did complete an update for a specific customer which allows them to specify an expiration time, after which MMS messages that have not been retrieved are rerouted for delivery via SMS with a web link. We are not planning to include that as standard product functionality until the next major release, but we could easily adapt that option to support sending back an "expired" status instead. -bn | |||
