| Compatibility with O2's ArcSoft MMS ver 2.0.0.22 |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - MMS & Advanced Issues ⬆ Archive through July 28, 2006 ⬆ |
◄ ► |
| Author | Message | |||
| Yew Thean Hoo New member Username: Theanhoo Post Number: 4 Registered: 01-2006 |
I am customer running Now SMS v5.51k (b20051013). When I send an MMS to an O2 running ArcSoft MMS ver 2.0.0.22, I get a blank screen, nothing is downloaded. O2s running ArcSoft ver 2.0.0.13 and 2.0.0.16 tested fine with identical content. Content is a JPEG file (169x98 pixels, 4,885 bytes) followed by plain text (863 bytes). Relevant excerpt from MMSCDEBUG.LOG: 17:31:21:578 [7] ThreadProcessConnection: HTTP/1.0 200 OK 17:31:21:578 [7] ThreadProcessConnection: Content-Length: 5900 17:31:21:578 [7] ThreadProcessConnection: Content-Type: application/vnd.wap.mms-message 17:31:21:578 [7] ThreadProcessConnection: Connection: close 17:31:21:578 [7] ThreadProcessConnection: Processing Complete 17:31:57:578 [7] ThreadProcessConnection: Processing connection from 202.75.133.20... 17:31:57:578 [7] ThreadProcessConnection: Packet Length is 1040 bytes 17:31:57:578 [7] ThreadProcessConnection: 47 45 54 20 2F 32 30 30 36 30 35 31 37 2F 31 37 GET /20060517/17 17:31:57:578 [7] ThreadProcessConnection: 2F 34 34 36 39 41 44 43 34 61 2E 4D 4D 53 20 48 /4469ADC4a.MMS H 17:31:57:578 [7] ThreadProcessConnection: 54 54 50 2F 31 2E 31 0D 0A 48 6F 73 74 3A 20 6D TTP/1.1 Host: m 17:31:57:578 [7] ThreadProcessConnection: 6D 73 2E 6F 61 67 6D 6F 62 69 6C 65 61 73 69 61 ms.oagmobileasia 17:31:57:578 [7] ThreadProcessConnection: 2E 63 6F 6D 3A 38 30 39 30 0D 0A 41 63 63 65 70 .com:8090 Accep 17:31:57:578 [7] ThreadProcessConnection: 74 3A 20 69 6D 61 67 65 2F 62 6D 70 2C 20 69 6D t: image/bmp, im 17:31:57:578 [7] ThreadProcessConnection: 61 67 65 2F 78 2D 62 6D 70 2C 20 69 6D 61 67 65 age/x-bmp, image 17:31:57:578 [7] ThreadProcessConnection: 2F 78 2D 6D 73 2D 62 6D 70 2C 20 69 6D 61 67 65 /x-ms-bmp, image 17:31:57:578 [7] ThreadProcessConnection: 2F 76 6E 64 2E 77 61 70 2E 77 62 6D 70 2C 20 69 /vnd.wap.wbmp, i 17:31:57:578 [7] ThreadProcessConnection: 6D 61 67 65 2F 67 69 66 2C 20 69 6D 61 67 65 2F mage/gif, image/ 17:31:57:578 [7] ThreadProcessConnection: 6A 70 65 67 2C 20 69 6D 61 67 65 2F 6A 70 67 2C jpeg, image/jpg, 17:31:57:578 [7] ThreadProcessConnection: 20 69 6D 61 67 65 2F 70 6E 67 2C 20 61 75 64 69 image/png, audi 17:31:57:578 [7] ThreadProcessConnection: 6F 2F 61 6D 72 2C 20 61 75 64 69 6F 2F 78 2D 61 o/amr, audio/x-a 17:31:57:578 [7] ThreadProcessConnection: 6D 72 2C 20 61 75 64 69 6F 2F 6D 69 64 2C 20 61 mr, audio/mid, a 17:31:57:578 [7] ThreadProcessConnection: 75 64 69 6F 2F 6D 69 64 69 2C 20 61 75 64 69 6F udio/midi, audio 17:31:57:578 [7] ThreadProcessConnection: 2F 73 70 2D 6D 69 64 69 2C 20 61 75 64 69 6F 2F /sp-midi, audio/ 17:31:57:578 [7] ThreadProcessConnection: 78 2D 6D 69 64 2C 20 61 75 64 69 6F 2F 78 2D 6D x-mid, audio/x-m 17:31:57:578 [7] ThreadProcessConnection: 69 64 69 2C 20 61 75 64 69 6F 2F 33 67 70 70 2C idi, audio/3gpp, 17:31:57:578 [7] ThreadProcessConnection: 20 61 75 64 69 6F 2F 6D 70 34 2C 20 61 75 64 69 audio/mp4, audi 17:31:57:578 [7] ThreadProcessConnection: 6F 2F 77 61 76 2C 20 61 75 64 69 6F 2F 78 2D 77 o/wav, audio/x-w 17:31:57:578 [7] ThreadProcessConnection: 61 76 2C 20 76 69 64 65 6F 2F 33 67 70 70 2C 20 av, video/3gpp, 17:31:57:578 [7] ThreadProcessConnection: 76 69 64 65 6F 2F 6D 70 34 2C 20 74 65 78 74 2F video/mp4, text/ 17:31:57:578 [7] ThreadProcessConnection: 78 2D 76 43 61 6C 65 6E 64 61 72 2C 20 74 65 78 x-vCalendar, tex 17:31:57:578 [7] ThreadProcessConnection: 74 2F 78 2D 76 43 61 72 64 2C 20 74 65 78 74 2F t/x-vCard, text/ 17:31:57:578 [7] ThreadProcessConnection: 70 6C 61 69 6E 2C 20 61 70 70 6C 69 63 61 74 69 plain, applicati 17:31:57:578 [7] ThreadProcessConnection: 6F 6E 2F 73 6D 69 6C 2C 20 61 70 70 6C 69 63 61 on/smil, applica 17:31:57:578 [7] ThreadProcessConnection: 74 69 6F 6E 2F 76 6E 64 2E 77 61 70 2E 6D 6D 73 tion/vnd.wap.mms 17:31:57:578 [7] ThreadProcessConnection: 2D 6D 65 73 73 61 67 65 2C 20 61 70 70 6C 69 63 -message, applic 17:31:57:578 [7] ThreadProcessConnection: 61 74 69 6F 6E 2F 76 6E 64 2E 77 61 70 2E 6D 75 ation/vnd.wap.mu 17:31:57:578 [7] ThreadProcessConnection: 6C 74 69 70 61 72 74 2E 72 65 6C 61 74 65 64 2C ltipart.related, 17:31:57:578 [7] ThreadProcessConnection: 20 61 70 70 6C 69 63 61 74 69 6F 6E 2F 76 6E 64 application/vnd 17:31:57:578 [7] ThreadProcessConnection: 2E 77 61 70 2E 6D 75 6C 74 69 70 61 72 74 2E 6D .wap.multipart.m 17:31:57:578 [7] ThreadProcessConnection: 69 78 65 64 2C 20 61 70 70 6C 69 63 61 74 69 6F ixed, applicatio 17:31:57:578 [7] ThreadProcessConnection: 6E 2F 76 6E 64 2E 6F 6D 61 2E 64 72 6D 2E 6D 65 n/vnd.oma.drm.me 17:31:57:578 [7] ThreadProcessConnection: 73 73 61 67 65 2C 74 65 78 74 2F 78 2D 68 64 6D ssage,text/x-hdm 17:31:57:578 [7] ThreadProcessConnection: 6C 2C 69 6D 61 67 65 2F 6D 6E 67 2C 69 6D 61 67 l,image/mng,imag 17:31:57:578 [7] ThreadProcessConnection: 65 2F 78 2D 6D 6E 67 2C 76 69 64 65 6F 2F 6D 6E e/x-mng,video/mn 17:31:57:578 [7] ThreadProcessConnection: 67 2C 76 69 64 65 6F 2F 78 2D 6D 6E 67 2C 69 6D g,video/x-mng,im 17:31:57:578 [7] ThreadProcessConnection: 61 67 65 2F 62 6D 70 2C 74 65 78 74 2F 68 74 6D age/bmp,text/htm 17:31:57:578 [7] ThreadProcessConnection: 6C 0D 0A 41 63 63 65 70 74 2D 43 68 61 72 73 65 l Accept-Charse 17:31:57:578 [7] ThreadProcessConnection: 74 3A 20 75 73 2D 61 73 63 69 69 2C 20 75 74 66 t: us-ascii, utf 17:31:57:578 [7] ThreadProcessConnection: 2D 38 2C 20 69 73 6F 2D 31 30 36 34 36 2D 75 63 -8, iso-10646-uc 17:31:57:578 [7] ThreadProcessConnection: 73 2D 32 2C 20 49 53 4F 2D 38 38 35 39 2D 31 2C s-2, ISO-8859-1, 17:31:57:578 [7] ThreadProcessConnection: 2A 0D 0A 41 63 63 65 70 74 2D 4C 61 6E 67 75 61 * Accept-Langua 17:31:57:578 [7] ThreadProcessConnection: 67 65 3A 20 65 6E 0D 0A 55 73 65 72 2D 41 67 65 ge: en User-Age 17:31:57:578 [7] ThreadProcessConnection: 6E 74 3A 20 58 64 61 32 6D 69 6E 69 2F 61 72 63 nt: Xda2mini/arc 17:31:57:578 [7] ThreadProcessConnection: 73 6F 66 74 2D 6D 6D 73 75 61 2D 32 2E 30 2E 30 soft-mmsua-2.0.0 17:31:57:578 [7] ThreadProcessConnection: 2E 78 78 20 55 50 2E 4C 69 6E 6B 2F 31 2E 31 0D .xx UP.Link/1.1 17:31:57:578 [7] ThreadProcessConnection: 0A 58 2D 4D 53 49 53 44 4E 3A 20 36 30 31 32 33 X-MSISDN: 60123 17:31:57:578 [7] ThreadProcessConnection: 31 38 38 30 34 30 0D 0A 78 2D 75 70 2D 64 65 76 188040 x-up-dev 17:31:57:578 [7] ThreadProcessConnection: 63 61 70 2D 63 68 61 72 73 65 74 3A 20 75 73 2D cap-charset: us- 17:31:57:578 [7] ThreadProcessConnection: 61 73 63 69 69 2C 20 75 74 66 2D 38 2C 20 69 73 ascii, utf-8, is 17:31:57:578 [7] ThreadProcessConnection: 6F 2D 31 30 36 34 36 2D 75 63 73 2D 32 2C 20 49 o-10646-ucs-2, I 17:31:57:578 [7] ThreadProcessConnection: 53 4F 2D 38 38 35 39 2D 31 0D 0A 78 2D 75 70 2D SO-8859-1 x-up- 17:31:57:578 [7] ThreadProcessConnection: 64 65 76 63 61 70 2D 6D 61 78 2D 70 64 75 3A 20 devcap-max-pdu: 17:31:57:578 [7] ThreadProcessConnection: 35 31 32 30 30 30 0D 0A 78 2D 75 70 2D 75 70 6C 512000 x-up-upl 17:31:57:578 [7] ThreadProcessConnection: 69 6E 6B 3A 20 77 61 70 32 2E 6D 79 6D 61 78 69 ink: wap2.mymaxi 17:31:57:578 [7] ThreadProcessConnection: 73 2E 63 6F 6D 2E 6D 79 0D 0A 78 2D 77 61 70 2D s.com.my x-wap- 17:31:57:578 [7] ThreadProcessConnection: 70 72 6F 66 69 6C 65 3A 20 22 68 74 74 70 3A 2F profile: "http:/ 17:31:57:578 [7] ThreadProcessConnection: 2F 77 77 77 2E 68 74 63 6D 6D 73 2E 63 6F 6D 2E /www.htcmms.com. 17:31:57:578 [7] ThreadProcessConnection: 74 77 2F 67 65 6E 2F 70 6D 31 30 2D 31 2E 30 2E tw/gen/pm10-1.0. 17:31:57:578 [7] ThreadProcessConnection: 78 6D 6C 22 0D 0A 56 69 61 3A 20 31 2E 31 20 73 xml" Via: 1.1 s 17:31:57:578 [7] ThreadProcessConnection: 62 61 67 65 6E 74 66 65 30 31 2E 6D 79 6D 61 78 bagentfe01.mymax 17:31:57:578 [7] ThreadProcessConnection: 69 73 2E 63 6F 6D 2E 6D 79 0D 0A 43 6F 6E 6E 65 is.com.my Conne 17:31:57:578 [7] ThreadProcessConnection: 63 74 69 6F 6E 3A 20 63 6C 6F 73 65 0D 0A 0D 0A ction: close 17:31:57:578 [7] ThreadProcessConnection: C:\PROGRA~1\NowSMS\MMSCDATA\20060517/17/4469ADC4a.INI 17:31:57:578 [7] GetLocalUaProfFile: Profile: 17:31:57:578 [7] GetLocalUaProfFile: http://www.htcmms.com.tw/gen/pm10-1.0.xml 17:31:57:578 [7] ThreadProcessConnection: C:\PROGRA~1\NowSMS\UAPROF\pm10-1.0.xml 17:31:57:578 [7] ConvertMMSFileForUAProf: MMS Image Resolution = 240 x 320 17:31:57:578 [7] ConvertMMSFileForUAProf: MMS Max Message Size = 307200 17:31:57:593 [7] ConvertMMSFileForUAProf: image/bmp 17:31:57:593 [7] ConvertMMSFileForUAProf: image/x-bmp 17:31:57:593 [7] ConvertMMSFileForUAProf: image/x-ms-bmp 17:31:57:593 [7] ConvertMMSFileForUAProf: image/vnd.wap.wbmp 17:31:57:593 [7] ConvertMMSFileForUAProf: image/gif 17:31:57:593 [7] ConvertMMSFileForUAProf: image/jpeg 17:31:57:593 [7] ConvertMMSFileForUAProf: image/jpg 17:31:57:593 [7] ConvertMMSFileForUAProf: image/png 17:31:57:593 [7] ConvertMMSFileForUAProf: audio/amr 17:31:57:593 [7] ConvertMMSFileForUAProf: audio/x-amr 17:31:57:593 [7] ConvertMMSFileForUAProf: audio/mid 17:31:57:593 [7] ConvertMMSFileForUAProf: audio/midi 17:31:57:593 [7] ConvertMMSFileForUAProf: audio/sp-midi 17:31:57:593 [7] ConvertMMSFileForUAProf: audio/x-mid 17:31:57:593 [7] ConvertMMSFileForUAProf: audio/x-midi 17:31:57:593 [7] ConvertMMSFileForUAProf: audio/wav 17:31:57:593 [7] ConvertMMSFileForUAProf: audio/x-wav 17:31:57:593 [7] ConvertMMSFileForUAProf: audio/3gpp 17:31:57:593 [7] ConvertMMSFileForUAProf: audio/mp4 17:31:57:593 [7] ConvertMMSFileForUAProf: video/3gpp 17:31:57:593 [7] ConvertMMSFileForUAProf: video/mp4 17:31:57:593 [7] ConvertMMSFileForUAProf: text/x-vCalendar 17:31:57:593 [7] ConvertMMSFileForUAProf: text/x-vCard 17:31:57:593 [7] ConvertMMSFileForUAProf: text/plain 17:31:57:593 [7] ConvertMMSFileForUAProf: application/smil 17:31:57:593 [7] ConvertMMSFileForUAProf: application/vnd.wap.mms-message 17:31:57:593 [7] ConvertMMSFileForUAProf: application/vnd.wap.multipart.mixed 17:31:57:593 [7] ConvertMMSFileForUAProf: application/vnd.wap.multipart.related 17:31:57:593 [7] ConvertMMSFileForUAProf: application/vnd.oma.drm.message 17:31:57:593 [7] ParseMMSMessageToFile: body part #1 Content-Type = image/jpeg 17:31:57:593 [7] ParseMMSMessageToFile: body part #1 Content-ID = <OAGMobile.jpg> 17:31:57:593 [7] ParseMMSMessageToFile: body part #1 Content-location = OAGMobile.jpg 17:31:57:593 [7] ParseMMSMessageToFile: body part #2 Content-Type = text/plain 17:31:57:593 [7] ParseMMSMessageToFile: body part #2 Content-ID = <OAGMobile.txt> 17:31:57:593 [7] ParseMMSMessageToFile: body part #2 Content-location = OAGMobile.txt 17:31:57:593 [7] GetImageAttributes: C:\PROGRA~1\NowSMS\ImageBin\identify.exe -format "%wx%h" C:\PROGRA~1\NowSMS\MMSCDATA\TEMP\5DB7722A\OAGMobile.jpg 17:31:57:609 [7] GetImageAttributes: 169x98 17:31:57:609 [7] ConvertMMSFileForUAProf: 5DB7722A\OAGMobile.jpg Image attributes 169 x 98 17:31:57:609 [7] ThreadProcessConnection: Sending C:\PROGRA~1\NowSMS\MMSCDATA\20060517/17/4469ADC4a.MMS 17:31:57:609 [7] ThreadProcessConnection: HTTP/1.0 200 OK 17:31:57:609 [7] ThreadProcessConnection: Content-Length: 5900 17:31:57:609 [7] ThreadProcessConnection: Content-Type: application/vnd.wap.mms-message 17:31:57:609 [7] ThreadProcessConnection: Connection: close 17:31:57:609 [7] ThreadProcessConnection: Processing Complete | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 5949 Registered: 10-2002 |
Can you configure the phone to use NowSMS as its MMSC? And can it then send a message to itself? The reason I ask this is because this will determine if the problem is somehow related to the content format, or if it is some other delivery issue. I have seen some phones that do not like an MMS message if there is no SMIL presentation file included in the MMS message. (A SMIL file is not technically required by the specs.) We have made changes in NowSMS 2006 so that when messages are submitted via the web interface, a SMIL file is automatically generated if one is not already present. But in v5.x, you would need to create your own and include it as one of the files in the MMS message submission. Anyway, that is why, if it is possible, I recommend that you try configuring the phone to use NowSMS as its MMSC, and have it send a message to itself. Then we can see if the issue is related to the MMS message content. -bn | |||
