Trying to send my first MMS | Search |
NowSMS Support Forums ⬆ NowSMS Support - MMS & Advanced Issues ⬆ Archive through May 02, 2013 ⬆ |
◄ ► |
Author | Message | ||||
Franck Raveau New member Username: Fraveau Post Number: 1 Registered: 06-2012 |
Hi, I just installed NowSMS and I'm trying to send my first MMS but I get an strange error. I is my log file:
Do you know what it is about? Thanks | ||||
Franck Raveau New member Username: Fraveau Post Number: 2 Registered: 06-2012 |
The error is: 15:37:43:421 [12] ThreadProcessConnection: C:\ProgramData\NowSMS\MMSCDATA\.INI 15:37:43:421 [12] ThreadProcessConnection: File not found on Windows seven thanks | ||||
Des - NowSMS Support Board Administrator Username: Desosms Post Number: 3980 Registered: 08-2008 |
Hi Franck, I'm not clear exactly what your question is. What exactly are you trying? How far are you getting? The error in the debug log doesn't show much ... it just looks like a web browser trying to connect to the MMSC. Unless that is the problem? There are multiple ports being listened to. The NowSMS web interface (configured on the "Web" page of the NowSMS configuration) is different from the MMSC HTTP port (configured on the "MMSC" page of the NowSMS configuration). I guess it is confusing that the MMSC configuration refers to it as an "HTTP Port Number". But to avoid confusion, it is only for applications talking MM1 or MM7 over HTTP, not for a web browser. Web browsers or HTTP URL submissions go via the "port number for the web interface". I'd suggest verifying that you can send an SMS first, before going on to MMS. The 'Quick Start Guides #1-3' at http://www.nowsms.com/doc/quick-start-guide are a good starting point for a configuration using modems. -- Des NowSMS Support | ||||
FRaveau New member Username: Fraveau Post Number: 3 Registered: 06-2012 |
Hi, Sorry, my previous post was pretty much unclear. I've been playing around since: I can send SMS, MMS and Wap push from the MMS gateway to my phone in Direct delivery mode. But I still can't send an MMS from my phone to the NowSMS MMSc. I've been looking to the firewall and nothing goes through it. A simple request using the handset browser to a file in the MMCDATA works. So the firewall settings are ok. The http request is stopped/lost before reaching my machine. I see two explanations: - The MMS configuration on my handset is wrong - My MNO stops the MMS request. Is that possible? How can I go further? Should I try to see what is the request made by the MMS client by installing a proxy server on my mobile? Or maybe there a way to install a MMS client on a PC to simulate an handset? Does nowsms can help about that? Any help much appreciated Regards | ||||
FRaveau New member Username: Fraveau Post Number: 4 Registered: 06-2012 |
Hi, Actually the MMS retrieving doesn't work. The notification works but the phone can't get the MMS's content. Only SMS and Wap push work. Regards | ||||
Des - NowSMS Support Board Administrator Username: Desosms Post Number: 3984 Registered: 08-2008 |
Hi Franck, OK ... your question is very different than I was expecting. Thank you for clarifying. It is very common for mobile operators to block access to external MMSCs. The issue is more of a billing related issue than a blocking issue. Some operators use a different APN for MMS. They do not charge for any data sent/received over that APN, but instead just charge for the MMS message. Because the data access is not being charged, the APN is locked down to only allow communication with the operator MMSC. So the short answer is that in addition to change the MMS server URL, you must also change the APN. There is more discussion here: http://www.nowsms.com/faq/how-mms-works -- Des NowSMS Support | ||||
Des - NowSMS Support Board Administrator Username: Desosms Post Number: 3985 Registered: 08-2008 |
Moderator Note: The unrelated question from Yopie has been moved to a different thread. If you are looking for that question, please see http://support.nowsms.com/discus/messages/485/71037.html | ||||
FRaveau New member Username: Fraveau Post Number: 7 Registered: 06-2012 |
I've installed the WAP.NOW GW and things are getting a litlle further. I send an MMS using NOW lite and I get the following in the GW's logs: 195.132.255.1 - [06/Jun/2012:15:44:55 +0200] "POST http://XXX.XXX.XXX.XXX:8080" 200 102 "" "iPhoneOS/4.2.1 (8C148)" where XXX.XXX.XXX.XXX is the IP adress of my MMSc In the MMSC log I get: 2012-06-06 15:44:55,MMSIN,YYY.YYY.YYY.YYY,,,User Not Defined,FAILED where YYY.YYY.YYY.YYY is the IP of my GW The debug (without the binary) 15:44:55:114 [11] InternalProcessConnection: Thread started 15:44:55:114 [11] ThreadProcessConnection: Processing connection from 85.169.94.127... 15:44:55:114 [11] ThreadProcessConnection: Packet Length is 10075 bytes 15:44:55:114 [11] ThreadProcessConnection: 50 4F 53 54 20 2F 20 48 54 54 50 2F 31 2E 31 0D POST / HTTP/1.1 15:44:55:114 [11] ThreadProcessConnection: 0A 43 6F 6E 74 65 6E 74 2D 4C 65 6E 67 74 68 3A Content-Length: 15:44:55:114 [11] ThreadProcessConnection: 20 39 37 31 39 0D 0A 43 6F 6E 74 65 6E 74 2D 54 9719 Content-T 15:44:55:114 [11] ThreadProcessConnection: 79 70 65 3A 20 61 70 70 6C 69 63 61 74 69 6F 6E ype: application 15:44:55:114 [11] ThreadProcessConnection: 2F 76 6E 64 2E 77 61 70 2E 6D 6D 73 2D 6D 65 73 /vnd.wap.mms-mes 15:44:55:114 [11] ThreadProcessConnection: 73 61 67 65 0D 0A 41 63 63 65 70 74 3A 20 61 70 sage Accept: ap 15:44:55:114 [11] ThreadProcessConnection: 70 6C 69 63 61 74 69 6F 6E 2F 76 6E 64 2E 77 61 plication/vnd.wa 15:44:55:114 [11] ThreadProcessConnection: 70 2E 6D 6D 73 2D 6D 65 73 73 61 67 65 0D 0A 43 p.mms-message C 15:44:55:114 [11] ThreadProcessConnection: 61 63 68 65 2D 43 6F 6E 74 72 6F 6C 3A 20 4E 6F ache-Control: No 15:44:55:114 [11] ThreadProcessConnection: 2D 43 61 63 68 65 0D 0A 55 73 65 72 2D 41 67 65 -Cache User-Age 15:44:55:114 [11] ThreadProcessConnection: 6E 74 3A 20 69 50 68 6F 6E 65 4F 53 2F 34 2E 32 nt: iPhoneOS/4.2 15:44:55:114 [11] ThreadProcessConnection: 2E 31 20 28 38 43 31 34 38 29 0D 0A 78 2D 77 61 .1 (8C148) x-wa 15:44:55:114 [11] ThreadProcessConnection: 70 2D 70 72 6F 66 69 6C 65 3A 20 68 74 74 70 3A p-profile: http: 15:44:55:114 [11] ThreadProcessConnection: 2F 2F 77 77 77 2E 61 70 70 6C 65 2E 63 6F 6D 2F //www.apple.com/ 15:44:55:114 [11] ThreadProcessConnection: 6D 6D 73 2F 75 61 70 72 6F 66 2E 72 64 66 0D 0A mms/uaprof.rdf 15:44:55:114 [11] ThreadProcessConnection: 43 6F 6E 6E 65 63 74 69 6F 6E 3A 20 4B 65 65 70 Connection: Keep 15:44:55:114 [11] ThreadProcessConnection: 2D 41 6C 69 76 65 0D 0A 58 2D 46 6F 72 77 61 72 -Alive X-Forwar 15:44:55:114 [11] ThreadProcessConnection: 64 65 64 2D 46 6F 72 3A 20 31 39 35 2E 31 33 32 ded-For: 195.132 15:44:55:114 [11] ThreadProcessConnection: 2E 32 35 35 2E 31 0D 0A 58 2D 57 41 50 2D 43 6C .255.1 X-WAP-Cl 15:44:55:114 [11] ThreadProcessConnection: 69 65 6E 74 2D 49 50 3A 20 31 39 35 2E 31 33 32 ient-IP: 195.132 15:44:55:114 [11] ThreadProcessConnection: 2E 32 35 35 2E 31 0D 0A 48 6F 73 74 3A 20 38 35 .255.1 Host: 85 15:44:55:114 [11] ThreadProcessConnection: 2E 31 36 39 2E 39 34 2E 31 32 37 3A 38 30 38 30 .169.94.127:8080 15:44:55:114 [11] ThreadProcessConnection: 0D 0A 0D 0A 8C 80 98 42 33 45 36 30 44 42 41 00 B3E60DBA 15:44:55:114 [11] ThreadProcessConnection: 8D 90 89 01 81 97 30 36 36 34 32 32 32 33 34 37 0664222347 15:44:55:114 [11] ThreadProcessConnection: 2F 54 59 50 45 3D 50 4C 4D 4E 00 96 74 65 73 74 /TYPE=PLMN test 15:44:55:114 [11] ThreadProcessConnection: 35 00 8A 80 8F 81 86 81 90 81 84 1F 24 B3 8A 3C 5 $ < 15:44:55:114 [11] ThreadProcessConnection: 43 42 39 33 41 35 31 30 2E 73 6D 69 6C 3E 00 89 CB93A510.smil> 15:44:55:114 [11] ThreadProcessConnection: 61 70 70 6C 69 63 61 74 69 6F 6E 2F 73 6D 69 6C application/smil 15:44:55:114 [11] ThreadProcessConnection: 00 03 45 82 45 1F 22 61 70 70 6C 69 63 61 74 69 E E "applicati 15:44:55:114 [11] ThreadProcessConnection: 6F 6E 2F 73 6D 69 6C 00 85 43 42 39 33 41 35 31 on/smil CB93A51 15:44:55:114 [11] ThreadProcessConnection: 30 2E 73 6D 69 6C 00 81 EA C0 22 3C 43 42 39 33 0.smil "<CB93 15:44:55:114 [11] ThreadProcessConnection: 41 35 31 30 2E 73 6D 69 6C 3E 00 8E 43 42 39 33 A510.smil> CB93 15:44:55:114 [11] ThreadProcessConnection: 41 35 31 30 2E 73 6D 69 6C 00 3C 73 6D 69 6C 3E A510.smil <smil> 15:44:55:114 [11] ThreadProcessConnection: 0D 0A 3C 68 65 61 64 3E 0D 0A 3C 6C 61 79 6F 75 <head> <layou 15:44:55:114 [11] ThreadProcessConnection: 74 3E 0D 0A 3C 72 65 67 69 6F 6E 20 69 64 3D 22 t> <region id=" 15:44:55:114 [11] ThreadProcessConnection: 49 6D 61 67 65 22 20 68 65 69 67 68 74 3D 22 31 Image" height="1 15:44:55:114 [11] ThreadProcessConnection: 30 30 25 22 20 77 69 64 74 68 3D 22 31 30 30 25 00%" width="100% 15:44:55:114 [11] ThreadProcessConnection: 22 20 66 69 74 3D 22 6D 65 65 74 22 2F 3E 0D 0A " fit="meet"/> 15:44:55:114 [11] ThreadProcessConnection: 3C 72 65 67 69 6F 6E 20 69 64 3D 22 54 65 78 74 <region id="Text 15:44:55:114 [11] ThreadProcessConnection: 22 20 68 65 69 67 68 74 3D 22 31 30 30 25 22 20 " height="100%" 15:44:55:114 [11] ThreadProcessConnection: 77 69 64 74 68 3D 22 31 30 30 25 22 20 66 69 74 width="100%" fit 15:44:55:114 [11] ThreadProcessConnection: 3D 22 73 63 72 6F 6C 6C 22 2F 3E 0D 0A 3C 2F 6C ="scroll"/> </l 15:44:55:114 [11] ThreadProcessConnection: 61 79 6F 75 74 3E 0D 0A 3C 2F 68 65 61 64 3E 0D ayout> </head> 15:44:55:114 [11] ThreadProcessConnection: 0A 3C 62 6F 64 79 3E 0D 0A 3C 70 61 72 20 64 75 <body> <par du 15:44:55:114 [11] ThreadProcessConnection: 72 3D 22 33 73 22 3E 0D 0A 3C 74 65 78 74 20 73 r="3s"> <text s 15:44:55:114 [11] ThreadProcessConnection: 72 63 3D 22 43 42 39 33 41 35 31 30 2E 74 78 74 rc="CB93A510.txt 15:44:55:114 [11] ThreadProcessConnection: 22 20 72 65 67 69 6F 6E 3D 22 54 65 78 74 22 2F " region="Text"/ 15:44:55:114 [11] ThreadProcessConnection: 3E 0D 0A 3C 2F 70 61 72 3E 0D 0A 3C 70 61 72 20 > </par> <par 15:44:55:114 [11] ThreadProcessConnection: 64 75 72 3D 22 35 73 22 3E 0D 0A 3C 69 6D 67 20 dur="5s"> <img 15:44:55:114 [11] ThreadProcessConnection: 73 72 63 3D 22 37 36 33 32 5F 31 34 30 2E 70 6E src="7632_140.pn 15:44:55:114 [11] ThreadProcessConnection: 67 22 20 72 65 67 69 6F 6E 3D 22 49 6D 61 67 65 g" region="Image 15:44:55:114 [11] ThreadProcessConnection: 22 2F 3E 0D 0A 3C 2F 70 61 72 3E 0D 0A 3C 2F 62 "/> </par> </b 15:44:55:114 [11] ThreadProcessConnection: 6F 64 79 3E 0D 0A 3C 2F 73 6D 69 6C 3E 0D 0A 20 ody> </smil> 15:44:55:114 [11] ThreadProcessConnection: C7 42 A0 C0 22 3C 37 36 33 32 5F 31 34 30 2E 70 B "<7632_140.p 15:44:55:114 [11] ThreadProcessConnection: 6E 67 3E 00 8E 37 36 33 32 5F 31 34 30 2E 70 6E ng> 7632_140.pn 15:44:55:114 [11] ThreadProcessConnection: 67 00 89 50 4E 47 0D 0A 1A 0A 00 00 00 0D 49 48 g PNG IH 15:44:55:114 [11] ThreadProcessConnection: 44 52 00 00 00 8C 00 00 00 8C 08 02 00 00 00 21 DR ! 15:44:55:114 [11] ThreadProcessConnection: A2 D6 69 00 00 00 09 70 48 59 73 00 00 0B 12 00 i pHYs 15:44:55:114 [11] ThreadProcessConnection: 00 0B 12 01 D2 DD 7E FC 00 00 00 C9 7A 54 58 74 ~ zTXt 15:44:55:114 [11] ThreadProcessConnection: 52 61 77 20 70 72 6F 66 69 6C 65 20 74 79 70 65 Raw profile type 15:44:55:114 [11] ThreadProcessConnection: 20 65 78 69 66 00 00 78 DA 5D 50 5B 0E C3 20 0C exif x ]P[ 15:44:55:114 [11] ThreadProcessConnection: FB E7 14 3B 42 42 1E C0 71 68 35 A4 DD 60 C7 9F ;BB qh5 ` 15:44:55:114 [11] ThreadProcessConnection: A1 41 55 17 89 E0 D8 21 72 48 EF EF 67 A4 D7 0C AU !rH g 15:44:55:114 [11] ThreadProcessConnection: 6E 2D A9 95 EA CD 9D 10 DA B4 E5 0E 50 E9 8A 42 n- P B 15:44:55:114 [11] ThreadProcessConnection: C4 99 98 04 98 83 8B 9B 3B 90 DD 75 F2 1C C2 F1 ; u 15:44:55:114 [11] ThreadProcessConnection: 14 BC 5F 77 AE 7F 83 A2 5F 18 0C 30 5B 0C 2A 5B _w _ 0[ *[ 15:44:55:114 [11] ThreadProcessConnection: C8 21 E8 55 D7 12 03 1B 90 DE 83 DA 41 8F D0 70 ! U A p 15:44:55:114 [11] ThreadProcessConnection: 9F 76 C3 26 76 6D E4 D5 47 51 1F EA 58 FD 2C 5A v &vm GQ X ,Z ................................................... 15:44:55:161 [11] ThreadProcessConnection: 25 74 45 58 74 64 61 74 65 3A 63 72 65 61 74 65 %tEXtdate:create 15:44:55:161 [11] ThreadProcessConnection: 00 32 30 31 32 2D 30 35 2D 32 31 54 31 32 3A 30 2012-05-21T12:0 15:44:55:161 [11] ThreadProcessConnection: 30 3A 30 32 2B 30 32 3A 30 30 D0 32 97 3C 00 00 0:02+02:00 2 < 15:44:55:161 [11] ThreadProcessConnection: 00 25 74 45 58 74 64 61 74 65 3A 6D 6F 64 69 66 %tEXtdate:modif 15:44:55:161 [11] ThreadProcessConnection: 79 00 32 30 31 32 2D 30 35 2D 32 31 54 31 32 3A y 2012-05-21T12: 15:44:55:161 [11] ThreadProcessConnection: 30 30 3A 30 32 2B 30 32 3A 30 30 A1 6F 2F 80 00 00:02+02:00 o/ 15:44:55:161 [11] ThreadProcessConnection: 00 00 11 74 45 58 74 6A 70 65 67 3A 63 6F 6C 6F tEXtjpeg:colo 15:44:55:161 [11] ThreadProcessConnection: 72 73 70 61 63 65 00 32 2C 75 55 9F 00 00 00 20 rspace 2,uU 15:44:55:161 [11] ThreadProcessConnection: 74 45 58 74 6A 70 65 67 3A 73 61 6D 70 6C 69 6E tEXtjpeg:samplin 15:44:55:161 [11] ThreadProcessConnection: 67 2D 66 61 63 74 6F 72 00 32 78 32 2C 31 78 31 g-factor 2x2,1x1 15:44:55:161 [11] ThreadProcessConnection: 2C 31 78 31 49 FA A6 B4 00 00 00 00 49 45 4E 44 ,1x1I IEND 15:44:55:161 [11] ThreadProcessConnection: AE 42 60 82 20 05 83 C0 22 3C 43 42 39 33 41 35 B` "<CB93A5 15:44:55:161 [11] ThreadProcessConnection: 31 30 2E 74 78 74 3E 00 8E 43 42 39 33 41 35 31 10.txt> CB93A51 15:44:55:161 [11] ThreadProcessConnection: 30 2E 74 78 74 00 74 65 73 74 35 0.txt test5 15:44:55:161 [11] ThreadProcessConnection: Got application/vnd.wap.mms-message 15:44:55:161 [11] ThreadProcessConnection: Got m-send-req 15:44:55:161 [11] ThreadProcessConnection: Packet Length is 16 bytes 15:44:55:161 [11] ThreadProcessConnection: 8C 81 98 42 33 45 36 30 44 42 41 00 8D 90 92 84 B3E60DBA The MSISDN is I set in Nos lite is not forwarded by the GW to the MMSc? Do I have to set a radius link? Is there a workaround? Thanks | ||||
FRaveau New member Username: Fraveau Post Number: 8 Registered: 06-2012 |
I'll put it in another way: is there a way, for testing purpose, to accept MMS without identification or with a simple one? Thanks | ||||
Des - NowSMS Support Board Administrator Username: Desosms Post Number: 3988 Registered: 08-2008 |
Hi Franck, Yes. This is typical of what we refer to as a "test lab" setup. In this case, user identity is accomplished by appending /phonenumber=password to the MMS server URL that is configured in the device. "phonenumber" and "password" must be defined on the "MMSC Users" page of the MMSC configuration. There is an old quick start guide that covers this type of configuration in more detail. Refer specifically to steps 4 thru 6: http://www.nowsms.com/download/nowsmsquickstartguide.pdf -- Des NowSMS Support | ||||
FRaveau New member Username: Fraveau Post Number: 9 Registered: 06-2012 |
Hi Des, It worked like a charm. I can now send an MMS from SMSlite and receive it on my mobile phone throught the WAP GW and the MMSc. The Wap GW is only used for MMS. However, I can't send one from my mobile phone. There must be a difference between the ways NowLite and the mobile send the MMS. Do you have any known issue or recommandation about that ? The two configs are: NOWLite: APN: myapn WAP GW Adress: http://XXX.XXX.XXX.XXX:8081 MMS server URL: http://XXX.XXX.XXX.XXX:8080/franck=dapass My phone with one APN defined for both regular internet acces and MMS: APN: myapn MMSc: http://XXX.XXX.XXX.XXX:8080/franck=dapass ProxyMMS: http://XXX.XXX.XXX.XXX Port MMS: 8081 APN type: <empty> Thanks Franck | ||||
Des - NowSMS Support Board Administrator Username: Desosms Post Number: 3990 Registered: 08-2008 |
Hi Franck, Ok ... this is confusing. But I think I follow you. NowSMS Lite can connect and send an MMS over a modem with those settings. However an MMS client in an actual phone with the same settings CANNOT. Unless there is some different access restriction related to the SIM in the modem vs. the SIM in the phone, I'd figure that there is something in the phone's settings that is not quite right. For the MMS proxy in the phone configuration, try removing http:// ... NowSMS Lite needs that prefix, but it could be confusing the MMS client on the phone. -- Des NowSMS Support | ||||
FRaveau New member Username: Fraveau Post Number: 10 Registered: 06-2012 |
I removed the http and it works now with a samsung handset! This is excellent news! It still doesn't work on my HTC desire. Maybe it's related to this particular model as I see that there are numerous issues on web about MMS on this device. Are you aware of something Many thanks | ||||
FRaveau New member Username: Fraveau Post Number: 11 Registered: 06-2012 |
Forget about my HTC. I made a wrong typing. It fully works now Franck |