I have been working for hours to solve this problem.
As you see above, I got CMS error 321
explanation of the eror code 321
The memory/message storage index assigned to the AT command is invalid.
source: http://www.developershome.com/sms/resultCodes2.asp
With that code, I wanted to get message count, and to read sms and I got the same error..
I can send sms with AT commands but I want to read sms from mobil phone. I connected via usb and bluetooth, and the result is the same.. I can send sms but cant read sms ..
What is the wrong on it?
For reading sms I use that code
AT+CMGL="ALL" or "REAC UNREAD" .. etc.
I've used Samsung Galaxy S I9000 and HTC Evo 3d
I know this is old but... I see you used AT+CPMS="SM" so you are trying to read messages from the SIM card. It appears you may be looking to a folder that is empty. Have you tried all of the other storages where the messages may have arrived? Those are detailed in your screen capture (AT+CPMS=?)
At this point I think you have already solved that.
Here's the link from where you can search your error and came to know about the reason/logic behind the error:
http://www.developershome.com/sms/resultCodes2.asp#16.2.1.1.Table of +CMS Error Codes and Their Meanings|outline
From there, we know that the read message operation failed because an invalid memory index was assigned to the AT command +CMGL.
Note that after the occurrence of a +CMS error, the GSM/GPRS modem or mobile phone will not process the remaining AT commands in the command line.
Related
I'm integrating SagePay Server and am stuck at step 4 here: https://developer-eu.elavon.com/docs/opayo-server/taking-payments
I get this error: Server error 5006: Unable to redirect to Vendor's web site. The Vendor failed to provide a RedirectionURL.
I know there are quite a lot of suggestions for this error out there. That it basically means there is something wrong with your code on the Notification URL.
I know it is completing the previous steps fine (I get the correct response parameters), I have made sure Opayo's IPs are allowed, the MD5 signatures match.
I think the problem is how I am "Responding to the Notification Post".
I am doing a standard WebRequest to send our RedirectUrl to SagePay - but the link here - SagePay RedirectURL failure - suggests it doesn't need that. Rather I should just "write to the simple Response object." The trouble is, I don't know what they mean by that.
Any help / experience with this, much appreciated.
Jon
I hope this answer isn't too late to be useful to you.
You're suffering from the main issue I've always had with Opayo (formerly SagePay) - namely that their integration guides for developers are terrible.
As the Opayo Server integration method is identical to the old SagePay version, I found it helpful to follow the much more in-depth instructions from before they rebranded. You can find those instructions here:
https://www.opayo.co.uk/file/12246/download-document/SERVER_Integration_and_Protocol_Guidelines_010814.pdf
In answer to your specific question, you can refer to page 68 of the above PDF guide. RE: You acknowledge receipt of the Notification POST, quote, "This is the plain text response part of the POST originated by the Server in the step above. Encoding must be as Name=Value fields separated by carriage-return linefeeds (CRLF)."
Literally, your script just has to print or echo something along the lines of:
Status=OK\r\n
StatusDetail=Hashes match - proceeding\r\n
RedirectURL=https://www.yoursite.com/endpointpage/
Or the equivalent for errors, aborts, etc.
Bear in mind that any output not formatted like the above will break the foldback process, so you must supress any errors or warnings your script might generate (ideally capturing them in a log or some other way).
Opayo give you basically no help in bugfixing, so if you continue to encounter errors you pretty much have to work in the dark.
I just pushed my new updates on play store and all over sudden am getting this error, I have tried to research online for answers but I get non, any help what this error means and how to fix it?
Any help and guidance on how to fix this is highly appreciated
I'm glad to see others have been impacted and it was not just me!
It seems to be a bug with the Google review system. Best thing to do is contact them via the link to their form in the footer of the email you received.
Update 2:
I did not take any action and passed the review process today.
Update 1:
I received the reply I have screenshot below, which does not help much. I asked what the notification was about and he did not address the issue at all, so now I don't know what to do. However he did confirm that my app was currently in the review queue, so maybe we just need to wait. Maybe the email notification with errors can be ignored. I will wait a few days to see if my app passes review without taking any further action.
I've just updated my Data Safety forms adding Device or other identifiers because my app request Ad Id, BSSID etc.
I've faced the same issue, and the solution is :
You need to check if you're using third-party libraries (in my case, IronSource and AdMob) that collect the user data.
If you're using IronSource you need to fill the Data Safety from here :
https://developers.is.com/ironsource-mobile/general/google-data-safety-questionnaire/
After you fill the Data Safety, hit the save button and wait for the review to complete.
I get the above error message while running replay query. Although in the documentation I could only find this:
“interactions” will contain “FORCE_ACTIVE” (this can be used by clients to detect the inactive stream and stop playback, instead of having to look for specific types).
In my understanding, we can just observe the value of "FORCE_ACTIVE" parameter to stop playback. While in the error message, I am being told to resume the stream by using "FORCE_ACTIVE". I couldn't find out through the documentation about sending the "FORCE_ACTIVE" parameter from my end. Please help me understand the proper course of action if I get the above error message. Thank you.
For now, you should display a message saying "Someone else is listening to your Pandora account. Only one person can listen at a time. Please try again later." We are working on adding a mechanism which would allow users to decide if they want to "take over control" but it's not ready yet. For reference, this is what shows up in the Pandora app when this situation arises:
The option to "Let me listen" is what we're adding. For now, you just have to default to "Let them listen".
I have problem with launching Google-Cast application similar to sample CastHelloText-chrome. I slightly modified example code for my specific purposes. The goal for creating this application is to send and show image data directly in Chromecast device.
Particularly the difference between official sample and my code is in message format and its content, sent by sender application. Sender application took png image coded by base64 and send through message bus with custom namespace. Receiver application get this message and use this as data source for html object <img>.
Error appears when I do this steps:
Reload sender page, checking console if any device found.
Send the form by just pushing enter on input box (text is ignored).
Now a popup from Chromecast extension shows. Next there are two scenarios:
3a) I confirm casting to device by choosing one from the list, then I get this error message in console:
onError: {"code":"channel_error","description":"Error: Timeout","details":null}
3b) I just click somewhere else, I get this error:
onError: {"code":"cancel","description":"User closed popup menu","details":null}
Both of errors are caused by calling function chrome.cast.requestSession in chromehellotext.html at line 161, but what's really wrong I don't know.
When I step sender script I realize that function sessionListener is never called. I know that something go wrong when code try to call chrome.cast.requestSession, where described error raises. So I need help if I missed about right way to use Google-Cast API or If this problem has something to do with networking issues.
Receiver application is registered on Google Cast SDK Developer Console and I'm testing on registered device with some serial number. I'm using Google Chrome in version 42.0.2300.2 canary (64-bit) and Chrome version 40.0.2214.111 (current stable I suppose). For testing I also tried to turn off Windows Firewall entirely but with no luck.
Edit:
There were some syntactic errors that caused error message described above.
It seems like you are trying to use the data/control channel to send an image; please don't do that; that channel is not meant to be used for large data communications; in fact it cannot send anything which approaches or exceeds 64k. If your goal is to send images from your local machine, you would need to run a local web server on your local machine and serve images through the web server.
For and easiest tutorial you can have a look to this tutorial.
It is well explained in this tutorial.
Chromecast Sender application
There is no need to maintain session by yourself.
just add button and enjoy casting
mCastManager.addMediaRouterButton(mediaRoutebtn);
I found a source of my problem. There was something wrong in receiver code - syntactic and runtime errors, so I must admit that my code wasn't functional. Now its working in terms of launching application and getting session.
Unfortunate thing is that the error message generated by Chromecast extension didn't match the actual error - at least it was a bit confusing when I didn't know what's really happening on receiver side without ability to debug the code.
I am using sim 900a modem. I want to read the messages coming to this modem. I have enabled the text mode AT+CMGF=1; I am sending message:
http://www.hughes.com/AT_Command_Reference.html#AT_plusCMGF
but I am receiving in this format...
+CMT: "+919841675265","","14/06/14,12:04:14+22"
0068007400740070003A002F002F006D006100700073002E0067006F006F0067006C0065002E0068
+CMT: "+919841675265","","14/06/14,12:04:17+22"
00200020002000540069006D0065003A00310034003A00330033003A003400340020002000440067
If I send the same message from another phone, I am receiving correctly....
I cant find where the problem is... please help me on this.
Maybe is because of the codepage you are using.
With the AT command AT+CSCS try to set your codepage in IRA or GSM.
Example: AT+CSCS="IRA"