| TransactionID in DeliveryReportReq |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - MMS & Advanced Issues ⬆ Archive through April 21, 2010 ⬆ |
◄ ► |
| Author | Message | |||
| Latitude De New member Username: Latitudede Post Number: 10 Registered: 07-2009 |
When I send the MM7 requiest, I get the following response from NowSMS: <?xml version="1.0" ?> <env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"> <env:Header> <mm7:TransactionID xmlns:mm7="http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-5-MM7-1-2" env:mustUnderstand="1">2483369702339370818_SYNC</mm7:TransactionID> </env:Header> <env:Body> <SubmitRsp xmlns="http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-5-MM7-1-2"> <MM7Version>5.3.0</MM7Version> <Status><StatusCode>1000</StatusCode> <StatusText>Success</StatusText></Status> <MessageID>20090709/14/8E257D31@217.112.80.78</MessageID> </SubmitRsp> </env:Body> </env:Envelope> I am happy with the TransactionID so far. But the respective DeliveryReportReq shows me different TransactionID. MessageID and ShortCode are fine. <?xml version="1.0" ?> <env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"> <env:Header> <mm7:TransactionID xmlns:mm7="http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-5-MM7-1-2" env:mustUnderstand="1">AC86CF6B-temp@217.112.80.78</mm7:TransactionID> </env:Header> <env:Body> <DeliveryReportReq xmlns="http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-5-MM7-1-2"> <MM7Version>5.3.0</MM7Version> <MessageID>20090709/14/8E257D31@217.112.80.78</MessageID> <Recipient> <Number>XXXXX</Number> </Recipient> <Sender> <ShortCode>2007</ShortCode> </Sender> <TimeStamp>2009-07-09T13:36:59Z</TimeStamp> <MMStatus>Retrieved</MMStatus> <StatusText>Retrieved</StatusText> </DeliveryReportReq> </env:Body> </env:Envelope> How TransactionID in DeliveryReportReq changed to AC86CF6B-temp@217.112.80.78? Regards. | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 1016 Registered: 08-2008 |
Hi, This seems to be a fairly common point of confusion with MM7. "TransactionID" applies to an individual transaction (i.e., a SubmitReq/SubmitRsp transaction or a DeliveryReportReq/DeliveryReportRsp transaction), not the lifespan of a message. When you submit a message, the SubmitRsp returns a "MessageID". Any future delivery reports or read reports will reference this "MessageID" to identify the message. -- Des NowSMS Support | |||
| Latitude De New member Username: Latitudede Post Number: 13 Registered: 07-2009 |
Apart from <MMStatus>Retrieved</MMStatus>, what are other MMStatus codes? When does MMS message gets expired? Thanks. | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 1018 Registered: 08-2008 |
The MMStatus codes would be documented in the MM7 specification. There may be others, but Retrieved, Expired, Rejected and Indeterminate are the ones in the list that I have.
That is up to your provider. 72 hours is a fairly common value, but it could be longer. It is also very possible that your provider won't send expired notifications. -- Des NowSMS Support | |||
| Latitude De New member Username: Latitudede Post Number: 14 Registered: 07-2009 |
Thanks. I'll go through the specifications to know more about the delivery statuses. Coming back to the transaction id issue: is it possible to send some custom info in the MM7Request and then expect it back in the respective DeliveryDeportReq? For example <MyTransacID>1234</MyTransacID> Thanks | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 1022 Registered: 08-2008 |
No. There's no parameter in MM7 (or any of the other MMS protocols) to allow the original message submitter to assign any type of long lifed message identifier. This issue is pretty common with most SMS related protocols as well. You need to check the id assigned in the submission to know the id to be included in future reports. -- Des NowSMS Support | |||
