| MM4 and delivery reports |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - MMS & Advanced Issues ⬆ |
◄ ► |
| Author | Message | |||
| Robert Kristensen New member Username: Linkmobilitymms Post Number: 10 Registered: 11-2015 |
Hi Des I have now set up a connection to a provider and the messages get delivered. But I can't figure out how to configure NowSMS to convert from MM4 to MM7 and forward the delivery reports to a URL. But I do not get any calls from NowSMS to our URL   | |||
| Robert Kristensen New member Username: Linkmobilitymms Post Number: 11 Registered: 11-2015 |
Hi Suppprt Can I get some feedback? | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 5551 Registered: 08-2008 |
Hi Robert, I'm sorry, I thought I replied last week, but I must have switched away before posting. I wanted to see what log entries you are seeing in MMSC-yyyymmdd.LOG, so that I could better understand the flow. However, taking a fresh look, I think I see the problem... In MMSC-yyyymmdd.LOG, do you see MMSOUT-DeliveryReport entries that look like the delivery reports being routed to your app (VASP:NOWSMS)? If so, the reason it is not working is because the non-standard PHP Upload format is being used. That format does not have any parameters defined for handling delivery reports. So they are being discarded. If the standard XML MM7 format were being used, they would be forwarded. I spoke with one of our engineers, who indicated that no parameter format was ever defined for delivery reports. He suggested that an MMSSTATUS variable be used to indicate a delivery report. Standard MM7 status strings would be used (Retrieved, Expired, Rejected, Indeterminate). MMSFROM would contain the original sender, and PHONENUMBER would contain the original recipient. He said that if this is sufficient, it could be implemented rather quickly. But we'd have to run this past his boss to get it scheduled. Thoughts? Or would it be possible for you to use the MM7 XML interface? -- Des NowSMS Support | |||
| Robert Kristensen New member Username: Linkmobilitymms Post Number: 12 Registered: 11-2015 |
Hi Des Sorry for the late reply. I see this in our log: 08:24:21:835 [26] ThreadProcessConnectionSMTP: 354 Ok, end with "." on a new line... 08:24:22:162 [26] ThreadProcessConnectionSMTP: Message received 409 bytes ... processing ... 08:24:22:162 [26] ThreadRouteSMTPIn: X-MMSC-RCPT-TO: +15880001/TYPE=PLMN 08:24:22:162 [26] ThreadRouteSMTPIn: BCC: +15880001/TYPE=PLMN 08:24:22:162 [26] ThreadRouteSMTPIn: X-MMSC-Auth-User: VASP:211.237.69.60 08:24:22:163 [26] ThreadRouteSMTPIn: X-MMSC-Received-From: 211.237.69.60 08:24:22:163 [26] ThreadRouteSMTPIn: X-MMSC-ENV-MAIL-FROM: <+821088815156/TYPE=PLMN@smsimm4.sktelink.com> 08:24:22:163 [26] ThreadRouteSMTPIn: X-Mms-Message-Type: MM4_delivery_report.REQ 08:24:22:163 [26] ThreadRouteSMTPIN: X-Mms-Message-Type: m-delivery-ind 08:24:22:163 [26] ThreadRouteSMTPIn: X-Mms-Transaction-ID: smsi_02_64138076 08:24:22:163 [26] ThreadRouteSMTPIn: X-Mms-Message-ID: "20160126-08-9FF0188F@10.115.0.126" 08:24:22:163 [26] ThreadRouteSMTPIn: Message-ID: "20160126-08-9FF0188F@10.115.0.126" 08:24:22:163 [26] ThreadRouteSMTPIn: To: +15880001/TYPE=PLMN 08:24:22:163 [26] ThreadRouteSMTPIn: TO: +15880001/TYPE=PLMN 08:24:22:163 [26] ThreadRouteSMTPIn: From: +821088815156/TYPE=PLMN 08:24:22:163 [26] ThreadRouteSMTPIn: X-Mms-Ack-Request: Yes 08:24:22:163 [26] ThreadRouteSMTPIn: X-Mms-MM-Status-Code: Retrieved 08:24:22:164 [26] RouteDeliveryReport: Message ID 20160126-08-9FF0188F@10.115.0.126, receipt should go to 15880001 08:24:22:164 [26] MMSRoutingCallback: 15880001/TYPE=PLMN 08:24:22:165 [26] MMSRoutingCallback: 15880001/TYPE=PLMN 08:24:22:165 [26] DeliverMMSMessage: 15880001/TYPE=PLMN 08:24:22:165 [26] DeliverMMSMessage: Processing delivery report or read report 08:24:22:165 [26] DeliverMMSMessage: 20160126-08-9FF0188F@10.115.0.126 08:24:22:165 [26] DeliverMMSMessage: 15880001/TYPE=VASP:NOWSMS 08:24:22:166 [26] DeliverMMSMessage: Found VASP Recip - NOWSMS 08:24:22:166 [26] DeliverMMSMessage-VASP: 15880001 08:24:22:166 [14] Debug: Signaled The MMSSTATUS solution sounds just what we need. | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 5560 Registered: 08-2008 |
Hi Robert, OK...we have an update pending for the next week or two, but we have delayed it slightly to sneak this capability in. We should have a preliminary update for you to try by Friday. -- Des NowSMS Support | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 5561 Registered: 08-2008 |
Hi Robert, Try this update: http://www.nowsms.com/download/nowsms20160128.zip Delivery reports will be passed to PHP scripts, with the following parameters: PhoneNumber, MMSFrom, MMSStatus and MMSMessageID. The presence of MMSStatus is a signal that it is a report. -- Des NowSMS Support | |||
