MMS Receiving Example using AT commands


#1

In chapter 9 “Examples of Application” of the WIP AT Commands User Guide there is an example of sending an MMS.
It there a converse example available somewhere “Receiving an MMS”. That would be good.

If I can’t find an example I’d like to develop one here.
Scenario
I have sent myself a test MMS using the example in Chapter 9.
Then I poll for SMS messages using AT+CMGL
+CMGR:1,“REC UNREAD”,“99”,“13/03/08,11:05:23+44”

OK
+CMGR:2,“REC UNREAD”,“99”,“13/03/08,11:05:23+44”
/1?APEgRxjlFU-d7BCfp

OK
I get 2 SMS messages. Why two?
One of these is the MMS M-Notification.ind message.
I presume that the “/1?APEgRxjlFU-d7BCfp” line is the location of the MMS meta data. Please correct me if I am wrong. :slight_smile:


How do I send this. I can request a HTTP get as shown in example 9.6
AT+WIPCREATE=5,1,“proxy.server.com”, 8070[,“username”,“password”,"header name”,” header value”,…]
OK
+WIPREADY: 5,1
AT+WIPFILE=5,1,1,”/1?APEgRxjlFU-d7BCfp”[,”username”, ”password”, ”Accept”, ”application/vnd.wap.mms-message”, …]
+CME ERROR: 839 Error during channel creation

This is where I get stuck, through shear ignorance but not for lack of perseverance though. I’ll add to this post as I find out more.
Any help would be appreciated


#2

Hi,

CME ERROR :839 is received during channel createion.This error is due to the fact that basic sockets (TCP/UDP) is not commercial but other features are locked by a commercial feature named “internet plug-in”.
The WIPsoft commands used for socket/session creation (HTTP session in this case)will return a “+CME ERROR: 839” error code if the feature is not enabled. To enable the features, you can refer to the AT Commands Interface Manual ( AT+WCFM command) .

Also,please contact your Sierra Wireless distributor or sales point for further details.

Thanks.


#3

https://forum.sierrawireless.com/t/faq-forum-wiki/3491/15


#4

That may have been tha case once. I was told by my M2M equipment supplier that in the latest Firmware that none of the features are locked and I can proved it with a Telstra SIM.

>AT+WIPCFG=1
OK
>AT+WIPBR=1,6
OK
>AT+WIPBR=2,6,11,"telstra.internet"
OK
>AT+WIPBR=4,6,0
OK
>AT
OK
>AT+WIPCREATE=5,1,"11.1.1.111",9999
OK

+WIPREADY: 5, 1
>AT+WIPFILE=5,1,1,"http://m2manalyzer.appspot.com/http"
CONNECT
<html><body>method: GET<br>query_string: <br>url: http://m2manalyzer.appspot.com/http<br>request.body: <br>body_file: <cStringIO.StringI object at 0xf44df58fa102be0><br>remote_addr: 101.172.255.238<br
>headers: {'User-Agent': '', 'Host': 'm2manalyzer.appspot.com', 'X-Appengine-Region': 'vic', 'X-Appengine-City': 'melbourne', 'X-Appengine-Citylatlong': '-37.811367,144.971829', 'X-Appengine-Country':
 'AU'}<br></body></html>♥
+WIPFILE: 5,1,1,200,"OK"

OK

So that is not the issue here.

I think the issue is with the configuration settings. I was using ‘mms’ as the APN but I should be using the APN for the internet. I’ll give that a go when the Optus GPRS network is working again.


#5

Yes - that was my understanding.


#6
>AT+WIPCFG=1
OK
>AT+WIPBR=1,6
OK
>AT+WIPBR=2,6,11,"internet"     // I was using the wrong APN before
OK
>AT+WIPBR=4,6,0
OK
>AT+WIPCREATE=5,1
OK
+WIPREADY: 5, 1
>AT+WIPFILE=5,1,1,"http://61.88.190.10:8070/1?AgfTxxxx5nYUpfv2I","411","optus"
+CME ERROR: 819 Error on Ping channel

So now I am getting this error. I have tried many combinations of URI and header parameters.
I can’t ping the server either. Perhaps it does not have a ping service switched on.
I get the same results for other mms proxy servers too.

WIPCREATE clarification

>AT+WIPCREATE=5,1,"61.88.190.10",8070
OK

+WIPREADY: 5, 1

+WIPREADY: 5, 1 would indicate that a connection to the proxy server 61.88.190.10 can be established. Well it turns out that no checking, pinging or anything else is done to confirm the connection. 10.0.0.130 does not exist and yet the client is created.

>AT+WIPCREATE=5,1,"10.0.0.130",8070
OK

+WIPREADY: 5, 1

#7

Or perhaps your service provider blocks PINGs…?


#8

Not mine. I also tried an online ping service. Same result.

ping google.com
Pinging google.com [74.125.237.38] with 32 bytes of data
Reply from 74.125.237.38: bytes=32 time=47ms TTL=54

now ping the optus proxy server
ping 61.88.190.10
Pinging 61.88.190.10 with 32 bytes of data:
Request timed out.


#9

Has anyone been able to download MMS messages using either AT commands or custom code?