| Read Report PDU in v2006 |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - MMS & Advanced Issues ⬆ Archive through July 28, 2006 ⬆ |
◄ ► |
| Author | Message | |||
| Steve Bennett New member Username: Steveb Post Number: 3 Registered: 04-2005 |
Hi, We are trying the support for PDU style read reports with the new version 2006 but without success. We have tried sending read reports back to the NowSMS MMSC version 2006 and the MMSC reports that it has successfully received it, but it does not send them back to the originator. Transcrive of messages below. Best regards Steve Here is what we sent to the MMSC MMS Message Encapsulation, Type: m-read-rec-ind X-Mms-Message-Type: m-read-rec-ind (0x87) X-Mms-MMS-Version: 1.1 Message-Id: 20060303/16/E878DA2E@pixermms.dynip.com Date: Mar 3, 2006 16:08:14.000000000 X-Mms-Read-Status: Read (0x80) And the MMSC responded:- 6:09:10:969 [9] ThreadProcessConnection: Got application/vnd.wap.mms-message 16:09:10:969 [9] ThreadProcessConnection: Got m-read-rec-ind 16:09:10:969 [9] ThreadProcessConnection: got alias 447803987862 for +447803987862 16:09:10:969 [9] ThreadProcessConnection: got auth for user +447803987862 16:09:10:969 [9] ThreadProcessConnection: HTTP/1.1 200 OK Connection: Keep-Alive Content-Type: application/vnd.wap.mms-message Content-Length: 0 But did not send out an MMS or SMS WAP Push PDU back to the originator. | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 5595 Registered: 10-2002 |
Hi Steve, I'd have to see more detail. (A full dump of the packet would be good ... I think that goes in to the mmscdebug.log.) One thing I do notice is that if the m-read-rec-ind packet encounters an error, we don't return an error code. It always returns an ok response. The most common error condition would be not being able to identify the user who is submitting the message ... but I see the "got auth" from the mmscdebug.log, so that is ok. The only other thing that I could think of would be a lack of a "To:" header in the packet. It is a mandatory field, and we don't generate the m-read-orig-ind if that header is not present. Similarly, we require a "Message-ID:", but you mention that header. -bn | |||
| Steve Bennett New member Username: Steveb Post Number: 4 Registered: 04-2005 |
Hi Bryce, Thanks. It looks like we aren't setting and sending the To: header - doh!. We'll test again and I'll post back. FYI Here's the full packet we sent to the MMSC (decoded in Ethereal and raw). Best regards Steve. Hypertext Transfer Protocol POST /447803987862=447803987862 HTTP/1.1\r\n Request Method: POST Request URI: /447803987862=447803987862 Request Version: HTTP/1.1 Content-Type: application/vnd.wap.mms-message\r\n User-Agent: TREO650R7\r\n Profile: electricpocket.com/UAProf/Palm/TREO650R7.xml\r\n Accept: */*\r\n Host: pixermms.dynip.com:8001\r\n Content-Length: 53\r\n Cache-Control: no-cache\r\n \r\n MMS Message Encapsulation, Type: m-read-rec-ind X-Mms-Message-Type: m-read-rec-ind (0x87) X-Mms-MMS-Version: 1.1 Message-Id: 20060303/16/E878DA2E@pixermms.dynip.com Date: Mar 3, 2006 16:08:14.000000000 X-Mms-Read-Status: Read (0x80) 0000 00 30 05 11 58 87 00 30 eb d2 3e 0c 08 00 45 80 .0..X..0..>...E. 0010 01 5f a5 4a 40 00 77 06 25 6b 54 0c 21 a7 c0 a8 ._.J@.w.%kT.!... 0020 01 08 34 ab 1f 41 95 3d 60 29 5d 14 41 95 50 18 ..4..A.=`)].A.P. 0030 ff ff 2a f1 00 00 50 4f 53 54 20 2f 34 34 37 38 ..*...POST /4478 0040 30 33 39 38 37 38 36 32 3d 34 34 37 38 30 33 39 03987862=4478039 0050 38 37 38 36 32 20 48 54 54 50 2f 31 2e 31 0d 0a 87862 HTTP/1.1.. 0060 43 6f 6e 74 65 6e 74 2d 54 79 70 65 3a 20 61 70 Content-Type: ap 0070 70 6c 69 63 61 74 69 6f 6e 2f 76 6e 64 2e 77 61 plication/vnd.wa 0080 70 2e 6d 6d 73 2d 6d 65 73 73 61 67 65 0d 0a 55 p.mms-message..U 0090 73 65 72 2d 41 67 65 6e 74 3a 20 54 52 45 4f 36 ser-Agent: TREO6 00a0 35 30 52 37 0d 0a 50 72 6f 66 69 6c 65 3a 20 65 50R7..Profile: e 00b0 6c 65 63 74 72 69 63 70 6f 63 6b 65 74 2e 63 6f lectricpocket.co 00c0 6d 2f 55 41 50 72 6f 66 2f 50 61 6c 6d 2f 54 52 m/UAProf/Palm/TR 00d0 45 4f 36 35 30 52 37 2e 78 6d 6c 0d 0a 41 63 63 EO650R7.xml..Acc 00e0 65 70 74 3a 20 2a 2f 2a 0d 0a 48 6f 73 74 3a 20 ept: */*..Host: 00f0 70 69 78 65 72 6d 6d 73 2e 64 79 6e 69 70 2e 63 pixermms.dynip.c 0100 6f 6d 3a 38 30 30 31 0d 0a 43 6f 6e 74 65 6e 74 om:8001..Content 0110 2d 4c 65 6e 67 74 68 3a 20 35 33 0d 0a 43 61 63 -Length: 53..Cac 0120 68 65 2d 43 6f 6e 74 72 6f 6c 3a 20 6e 6f 2d 63 he-Control: no-c 0130 61 63 68 65 0d 0a 0d 0a 8c 87 8d 91 8b 32 30 30 ache.........200 0140 36 30 33 30 33 2f 31 36 2f 45 38 37 38 44 41 32 60303/16/E878DA2 0150 45 40 70 69 78 65 72 6d 6d 73 2e 64 79 6e 69 70 E@pixermms.dynip 0160 2e 63 6f 6d 00 85 04 44 08 69 ee 9b 80 .com...D.i... | |||
| Steve Bennett New member Username: Steveb Post Number: 5 Registered: 04-2005 |
Hi, We've re-formatted our read-report message with the To header and we can confirm read report PDU style is working fine in MMS 2006  Thanks Steve. | |||
