Delivery reports for MMS over gsm modem | Search |
NowSMS Support Forums ⬆ NowSMS Support - MMS & Advanced Issues ⬆ Archive through May 02, 2013 ⬆ |
◄ ► |
Author | Message | |||
dinos New member Username: Dinaras Post Number: 41 Registered: 02-2006 |
Hello, I am sending some mms over a gsm modem to operator smsc. In order to do that, i have created a vasp account and an mms outbound route. MMS gets properly delivered to recipient handset, but i dont see anywhere any callbacks for delivery report. Is there any way to get delivery reports for mms send by a gsm modem? Also if i use a 3g capable modem for sending mms, will it be faster? Thank you very much in advance Regards Konstantinos Liadakis | |||
Des - NowSMS Support Board Administrator Username: Desosms Post Number: 3535 Registered: 08-2008 |
Hi Konstantinos, It gets confusing because there are so many different configuration possibilities, and protocol differences. When using a modem to send and receive MMS messages, the "MMSC VASP" account is not used. MMS messages received via the modem are processed via the "Receive MMS Settings" under the modem definition in the SMSC list. The default behaviour is to route any received messages (including delivery receipts) to a file based interface in the MMS-IN directory. If you submit an MMS message with a delivery report requested, and the operator supports delivery receipts, you'll end up with a file like this in the MMS-IN directory: X-NowMMS-RCPT-TO: original-sender-address-here Message-type: m-delivery-ind MMS-version: 1.1 Date: Mon, 17 Oct 2011 18:38:42 GMT Message-id: 20111017/14/049DD2D6@des.nowsms.com Status: Retrieved To: +xxxxxxxxxxx/TYPE=PLMN That said, there are some operators that don't support delivery receipts. When testing, instead of continually checking the MMS-IN directory, look for the SMS received count to increase, because the delivery receipt will arrive via SMS. Read reports can also be requested, but they are far less reliable. Some devices give recipients the option to not return a read report. And quite a few operator interconnects do not support them. You need to set the MMS version in the outbound route to 1.2 to have any hope of receiving them.
Yes. Note that it is upload speed that you need for faster performance in sending. -- Des NowSMS Support | |||
dinos New member Username: Dinaras Post Number: 42 Registered: 02-2006 |
Hello Des and thank you for your reply, How do you request a delivery report when sending a message over MMSC Vasp account (mm4 smtp protocol)? Thanks again Regards Dinos | |||
Des - NowSMS Support Board Administrator Username: Desosms Post Number: 3544 Registered: 08-2008 |
Hi Dinos, Use the following SMTP header: X-Mms-Delivery-Report: Yes -- Des NowSMS Support | |||
dinos New member Username: Dinaras Post Number: 44 Registered: 02-2006 |
Hello Des, I am returning to this thread because i tried what you proposed above, but nothing happened. No mms dlr report. What should i expect to happen. I dont see any accounting callback neither i see any dlr sms arriving. Thank you very much in advance Regards Dinos | |||
Des - NowSMS Support Board Administrator Username: Desosms Post Number: 3578 Registered: 08-2008 |
Hi Dinos, To try to narrow things down, try sending an MMS message from the NowSMS web interface, asking for a delivery report. The delivery report will come back via an SMS message. For example, I just tried a test, and this is what I see in the SMSDEBUG.LOG: 10:42:45:167 [31] ModemReceiveMessages: +CMGL: 1,0,,132 07914140540500F944038102F800F511114001349069750605040B8423F00006291F226170706C69 636174696F6E2F766E642E7761702E6D6D732D6D657373616765008184AF848D01008C868D918B67 756C616A62767A6977726C333640772E746D6F6D61696C2E6E657400972B31383433323930393135 392F545950453D504C4D4E0085044EB3F9F39581 OK 10:42:45:167 [31] ModemReceiveMessages: Decoding received message index 1 from message storage SM 10:42:45:167 [31] ModemReceiveMessages: 07914140540500F944038102F800F511114001349069750605040B8423F00006291F226170706C69 636174696F6E2F766E642E7761702E6D6D732D6D657373616765008184AF848D01008C868D918B67 756C616A62767A6977726C333640772E746D6F6D61696C2E6E657400972B31383433323930393135 392F545950453D504C4D4E0085044EB3F9F39581 10:42:45:167 [31] ModemReceiveMessages: SMSC address len = 7 10:42:45:168 [31] ModemReceiveMessages: SMSC Address = +14044550009 10:42:45:168 [31] ModemReceiveMessages: SMS Message Type = SMS-DELIVER 10:42:45:168 [31] ModemReceiveMessages: User Data Header is present 10:42:45:168 [31] ModemReceiveMessages: Sender address len = 3 10:42:45:168 [31] ModemReceiveMessages: Sender Address = 208 10:42:45:168 [31] ModemReceiveMessages: PID = 00 10:42:45:168 [31] ModemReceiveMessages: DCS = F5 10:42:45:168 [31] ModemReceiveMessages: Anticipated user data length = 117 10:42:45:170 [31] ModemReceiveMessages: Binary message = 0605040B8423F0 0006291F226170706C69636174696F6E2F766E642E7761702E6D6D732D6D657373616765008184AF 848D01008C868D918B67756C616A62767A6977726C333640772E746D6F6D61696C2E6E657400972B 31383433323930393135392F545950453D504C4D4E0085044EB3F9F39581 10:42:45:171 [19] ThreadProcessInboundSMS: Processing 4CFDDD06.in... 10:42:45:171 [19] ThreadProcessInboundSMS: Processing WAP Push Message 10:42:45:171 [19] ThreadProcessInboundSMS: Processing MMS message 10:42:45:171 [19] ThreadProcessInboundSMS: Processing remote receipt id gulajbvziwrl36@w.tmomail.net 10:42:45:171 [31] ModemReceiveMessages: AT+CMGD=1 10:42:45:173 [19] ThreadProcessInboundSMS: Processing local receipt id 20111104/10/806F07A9@destest1.nowsms.com If you can get a delivery receipt when sending via the web, but not MM4, then we need to take a closer look at the MM4 transaction. If you don't get a delivery receipt when sending via the web, your mobile operator might have delivery report support disabled. -- Des NowSMS Support |