| MMS Deliver report |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - SMS Issues ⬆ Archive through August 10, 2011 ⬆ |
◄ ► |
| Author | Message | ||||
| Alexandre Frequent Contributor Username: Alexd Post Number: 155 Registered: 01-2008 |
Hello! I have some questionsabout delivery report of MMS messages. Now I'll try to explain the logic. 1. I made a connection to the MMS center tab in the "MMSC Routing" 2. I made an entry in the "MMSC Vasp" for MMS Center to receive reports from him about the delivery of MMS messages 3. Also I have made available to the client tab in the "MMSC Vasp", the client can send MMS messages (using MM7). Question. How to redirect a client delivery reports which come from the MMS Center? When a client sends a message to Callback I see: Type = MMSSend; From = XXXXX; VASPIN = XXX.XXX.XXX.XX; VASP = MMS; To = + xxxxxxxxxxxxxxx; MessageID = 20110413/00/5095796D; Size = 13809; When it comes to the delivery report from the MMS Center, I see: Type = MMSDeliveryReport; From = + xxxxxxxxxxxxxxx; VASPIN = XX.XX.XX.XX; VASP = MMSHANDLER; To = + xxxxxxxxxxxxxxx; MessageID = TaSvl6wYeYcAAGTMAAAAKgAAAAEAAAAA; Size = 70; It turns out that the MessageID different and I can not link the message in my handler. Is there an opportunity to establish processes delivery reports in SMPP? Ie when it comes to the delivery report from SMS center, the report is placed in a folder User \ Q | ||||
| Alexandre Frequent Contributor Username: Alexd Post Number: 156 Registered: 01-2008 |
And one more thing i see. In Wireshark i see when NowSMS make request sent MMS to MMS Center, MMS center response: ......... <mm7p550:MM7Version>5.3.0</mm7p550:MM7Version> <mm7p550:Status> <mm7p550:StatusCode>1000</mm7p550:StatusCode> <mm7p550:StatusText>Success</mm7p550:StatusText> </mm7p550:Status> <mm7p550:MessageID>Ta8ARawYeYcAAGTMAAAALgAAAAUAAAAA</mm7p550:MessageID> </mm7p550:SubmitRsp> ...... But i don`t see that MessageID in NowSMS callback. I see only: MessageID=20110420/19/3A84EA55 It posible to put MessageID from response to callback ? | ||||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 3114 Registered: 08-2008 |
Hi Alexandre, This translation of message IDs should be automatic. Unless there is a scenario that we are missing ... or there is a mismatch of the ID that is actually being returned in the delivery report. Unfortunately, none of the logs or callbacks record the upstream assigned MMS message ID. (Actually, that is not entirely true, as it looks like the MMSOUT callback is recording the upstream message ID instead of the local message ID, which is not what is intended.) Basically, we need to look at the MMSCDEBUG.LOG, and see what the <MessageID> value is in the MM7 submit response, and then compare that with the <MessageID> in the delivery report. If "TaSvl6wYeYcAAGTMAAAAKgAAAAEAAAAA" is the value for both, then NowSMS should convert it properly. If you need to send me an MMSCDEBUG.LOG to look at, send it to nowsms@nowsms.com with Attention: Des in the subject line. -- Des NowSMS Support | ||||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 3115 Registered: 08-2008 |
I am mistaken about the MMSOUT callback including the wrong (upstream) message ID. But as I stated, the message ID conversion is all supposed to be transparent. I think I need to see an MMSCDEBUG.LOG in order to understand the complete transaction flow. -- Des NowSMS Support | ||||
| Alexandre Frequent Contributor Username: Alexd Post Number: 157 Registered: 01-2008 |
Here is mmsc debug log
| ||||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 3120 Registered: 08-2008 |
This is a puzzle. Everything looks perfectly normal, except that I can see a debug statement indicating that the message ID could not be resolved. The message ID formats look normal, so it is not clear why there would be a problem. My only guess is that there is something wrong with the tracking database. Can I see the MR201104.DB and ML201104.DB files from your SMPPDATA directory? -- Des NowSMS Support | ||||
| Alexandre Frequent Contributor Username: Alexd Post Number: 158 Registered: 01-2008 |
Hmmm strange but no any SMPPDATA in NowSMS directory, maybe need add some params in SMSGW.INI filr ? | ||||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 3122 Registered: 08-2008 |
Hmm ... one of the first things I tried yesterday when attempting to recreate this problem was to delete the SMPPDATA directory and see if it got recreated. It did for me. A MessageIDTrackingDir= parameter in SMSGW.INI can relocate this directory. (We use it for both SMPP and MM7/MM4 message ID tracking.) Another thought ... make sure you are looking in ProgramData\NowSMS, not necessarily Program Files\NowSMS. SMPPDATA would normally be in the same directory structure as SMSGW.INI. -- Des NowSMS Support | ||||
| Alexandre Frequent Contributor Username: Alexd Post Number: 159 Registered: 01-2008 |
hmmm yeah my mistake now i see tracking DB :) In callback now i see: Type=MMSOut;From=SourceAddress/TYPE=PLMN;VASP=MMS;To=+XXXXXX;MessageID=20110422/ 21/33497A0E;Size=1751; PreAuth=Yes;Type=MMSDeliveryReport;From=+XXXXXX;VASPIN=127.0.0.1;To=+SourceAddre ss;MsgCount=1; Type=MMSDeliveryReport;From=+XXXXXX;VASPIN=78.24.57.53;VASP=MMSHANDLER;To=+Sourc eAddress;MessageID=20110422/21/33497A0E@127.0.0.1;Size=68; So for get delivery state i need parse posted xml data on handler ? No any way to get it from callback in parameter ? :) like MMStatus=Retrieved or it`s imposible ? | ||||
| Alexandre Frequent Contributor Username: Alexd Post Number: 160 Registered: 01-2008 |
And 2 another little questions how get from MMS callback User login who send MMS ? :) If i turn on SMSAccountingURL then i see that: PreAuth=Yes;Type=SMSSend;From=login;To=+XXXXXXX;MsgCount=1;SubmitIP=127.0.0.1;Se nder=Test1;Binary=1;DCS=F5;ReceiptRequested=Yes; Type=SMSSend;From=login;To=+XXXXXXX;MessageID=unknown;SubmitIP=127.0.0.1;Sender= Test1;Binary=1;DCS=F5; Type=MMSOut;From=SourceAddress/TYPE=PLMN;VASP=MMS;To=+XXXXXXX;MessageID=20110423 /00/34281C6E;Size=1751; So i have 2 questions: 1. Why in MMS callback i did`t see user login? 2. Why in SMS callback MessageID=unknown ? As i see if someone send MMS via MM7, i can get him login from VASPIN parameter. | ||||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 3132 Registered: 08-2008 |
Hi Alexandre, What was the problem that was preventing these tracking databases from being created? The MMSDeliveryReport callback was not designed to provide message status information. The callback was designed simply to tell the provider the type of message that is being transported. I do agree that it would be a good idea if this callback was extended to include the status. I will get this added to our engineering queue. Regarding the submission of MMS messages via the URL parameters submission interface, I would discourage the use of this interface if you need accounting information. This interface was designed for convenience, but has a limitation that it uses a separate set of user accounts for authentication from the MMSC. I will make an engineering suggestion that perhaps an SMS User account can be associated with an MMSC VASP account for accounting purposes, as perhaps that would provide a good solution. However, I am not optimistic that any changes will be made in this area. -- Des NowSMS Support | ||||
| Alexandre Frequent Contributor Username: Alexd Post Number: 161 Registered: 01-2008 |
Thanks. But what is a parameter MessageID=unknown ? It must be the same like in MMSOut callback ? (MessageID=20110423 /00/34281C6E) | ||||
| Alexandre Frequent Contributor Username: Alexd Post Number: 162 Registered: 01-2008 |
Maybe I'm not entirely true explain what I want:) I make a GET request: http://127.0.0.1:8800/?PhoneNumber=%2BXXXXXX&MMSFrom=XXXXX&MMSSubject=test&MMSTe xt=test2&MMSFile=&MMSFile=&MMSFile=&MMSDeliveryReport=Yes PreAuth=Yes;Type=SMSSend;From=userlogin;To=+XXXXXX;MsgCount=1;SubmitIP=127.0.0.1 ;Binary=1;DCS=F5;ReceiptRequested=Yes; Type=SMSSend;From=userlogin;To=+XXXXXX;MessageID=unknown;SubmitIP=127.0.0.1;Bina ry=1;DCS=F5; Type=MMSOut;From=XXXXX/TYPE=PLMN;VASP=MMS;To=+XXXXXX;MessageID=20110426/18/81F31 990;Size=1752; In MMSOut callback I do not see userlogin, how do I link sent MMS from userlogin? I tried to substitute the query parameter MessageID, but in the callback I see MessageID = unknown; I'm doing something wrong? How to build a scheme of processing MMS callbacks? | ||||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 3134 Registered: 08-2008 |
Hi Alexandre, I'm sorry that I was not clear. Let me restate. Regarding the submission of MMS messages via the URL parameters submission interface, I would discourage the use of this interface if you need accounting information. This interface was designed for convenience, but has a limitation that it uses a separate set of user accounts for authentication from the MMSC. As such, the SMS Accounting callback does not include the MMS Message ID (because there is no defined parameter for this), and returns UNKNOWN as the SMS message ID (because there is no SMS message ID). Similarly, the MMS Accounting callback does not record a submitting user, because has no knowledge of the SMS user account that created the message, because it expects an MMSC User or VASP account. In other words ... The URL submission interface for sending MMS is not recommended if you rely on accounting callbacks. --- All this said, I did ask our engineering team to revisit the limitations in this area. We will be adding an "MMSMessageID=" parameter to the SMS Accounting callback. And we will be adding an "MMSStatus=" parameter to the "MMSDeliveryReport" accounting callback. I don't have an estimate for when this will be available yet. Most likely it will be available by early next week. -- Des NowSMS Support | ||||
| Alexandre Frequent Contributor Username: Alexd Post Number: 163 Registered: 01-2008 |
Big thanks DES! You said: "The URL submission interface for sending MMS is not recommended if you rely on accounting callbacks." But what interface is recommended for sending MMS ? I get your php example for POST MMS, it`s a normal for sending ? | ||||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 7953 Registered: 10-2002 |
Hi Alexandre, We do not have a good option for you at this time. The MMS accounting interfaces were designed for MMS service providers that support standard MMS clients and protocols. This particular interface was developed as an extension of our SMS APIs, and it doesn't integrate well with the accounting callbacks. The changes that Des mentioned have been implemented, but unfortunately we are busy this week integrating and testing a number of other updates. So an update that includes these changes will not be released until we have completed testing. The UK holiday schedule is giving us a bit of additional delay. But hopefully toward the end of next week, we will be ready to post something. -bn | ||||
| Alexandre Frequent Contributor Username: Alexd Post Number: 164 Registered: 01-2008 |
Big Thanks Bryce and Des! I`ll waiting for update :) | ||||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 3165 Registered: 08-2008 |
Better late than never. The two changes I mentioned previously have been incorporated in the latest update at http://www.nowsms.com/download/nowsms20110509.zip An "MMSMessageID=" parameter has been added to the SMS Accounting callback. An "MMSStatus=" parameter has been added to the "MMSDeliveryReport" accounting callback. There are more details in the text file included in the ZIP. -- Des NowSMS Support | ||||
| Alexandre Frequent Contributor Username: Alexd Post Number: 166 Registered: 01-2008 |
Big thanks for update! Very goog functions! | ||||
| Alexandre Frequent Contributor Username: Alexd Post Number: 167 Registered: 01-2008 |
Hello DES! There is another issue. If the login sends MMS messages using the MM7 protocol. NowSMS does not return to the field <mm7p550:MessageID> message ID (eg 20110513/14/1BB7EF21). Is there some setting that NowSMS returned ID? | ||||
| Alexandre Frequent Contributor Username: Alexd Post Number: 168 Registered: 01-2008 |
I would like to add. Reply from NowSMS is as follows: <?xml version="1.0" ?> <env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"> <env:Header> <TransactionID xmlns="http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-5-MM7-1 env:mustUnderstand="1">TransID</TransactionID> </env:Header> <env:Body> <SubmitRsp xmlns="http://www.3gpp.org/ftp/Specs/archive/23_series/23.140/schema/REL-5-MM7-1-0"> <MM7Version>5.3.0</MM7Version> <Status> <StatusCode>1000</StatusCode> <StatusText>Success</StatusText> </Status> </SubmitRsp> </env:Body> </env:Envelope> | ||||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 3176 Registered: 08-2008 |
Hi Alexandre, That is because the 1-0 schema version does not support that parameter. 1-2 is a good baseline version for the MM7 schema. Early schema versions were not completely thought out. -- Des NowSMS Support | ||||
MMSCDEBUGLOG
