| Repeated Retry Pending Error |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - SMS Issues ⬆ Archive through October 03, 2004 ⬆ |
◄ ► |
| Author | Message | |||
| Dan Eichenwald New member Username: Ikes Post Number: 1 Registered: 08-2004 |
I am trying to send a binary SMS from NowSMS such that it does not display a notification upon arrival to the user. I am using a DCS of 0xF5 which specifies this to be a SIM specific message. However, when I specifiy a PID of 0x7F for a SIM data download, I repeatedly (every 2-3 minutes) get the following error in my NowSMS out.log files: 2004-08-27 10:14:47,412F2A11.req,127.0.0.1,16172301346,Retry Pending - ERROR - Modem Response (2): +CMS ERROR: 500 -- Ericsson T68 Cable Modem This error message just keeps showing up and I can't stop it! Any idea why this is happening and how to stop these Retry Pending errors? I am still able to send and recieve other SMSs via NowSMS between these errors with no problem. Also, is it possible to send a Text SMS from Now SMS such that the user is not notified? Maybe by specifying message classes? Thanks, Dan | |||
| Dan New member Username: Ikes Post Number: 2 Registered: 08-2004 |
Correction: I'm using 0xF6 for a SIM specific message, but still can not avoid the notification that a message has arrived. | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 3376 Registered: 10-2002 |
Hi Dan, It is likely that the modem or the SMSC simply will not accept the message with the PID and DCS values that you have specified. Sometimes it takes quite a bit of trial and error. Does the message have a UDH? If so, make sure that the UDH length is set properly, as that is another problem that can show up when sending binary messages. On the retry logic handling, see the following: http://support.nowsms.com/discus/messages/1/5885.html Note that a CMS ERROR 500 can occur for many reasons. It is very frequent to get this error when the modem has simply lost its connection to the operator (weak signal). But it can also happen for other reasons as well. However, that is why we are retrying. I'm not aware of any SMS attributes for not notifying the user that a message has arrived. Flash SMS (class 0) is commonly for telling the phone not to save the message (it just pops up on the screen). But I can't think of any SMS attributes that would cause the message to be saved to the inbox, but not displayed. | |||
| Dan New member Username: Ikes Post Number: 3 Registered: 08-2004 |
Thanks Bryce, I verified with another phone that our SMSC does not accept a pid of 0x7F. I'm trying to do something similar to how a network operator would update a user's SIM via SMS without the user ever knowing. This SMS "passes through" the handset and is not even saved in the users Inbox. Can you please clarify the difference between an ME and a SIM specific message (class 1 and 2). I was under the impression that a SIM specific message went directly to the SIM and did not alert the user. Is this an operator only privilege? Thanks again, Dan | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 3392 Registered: 10-2002 |
Hi Dan, A SIM specific message is generally a message that updates data on the SIM ... such as SIM toolkit update, or an update to a SIM data file with information such as a preferred networks list. (My operator seems to send me a new preferred networks list a couple of times a year ... although I have noticed that I get such a message it still shows up in my inbox, but when I open the message the phone says something like "OTA provisioning complete". I do forget the exact text.) ETSI GSM 11.11, 03.48, and 11.14 have a lot of information about the formatting of the SIM specific messages. (The first covers SIM updating, the other two cover SIM toolkit.) Basically, when you send a SIM specific message, what you're doing is sending a command to update information on the SIM. So unless you're sending out a command, I don't think you can use the SIM specific interface. You might want to try DCS = 0x16 instead of 0xF6, along with PID = 0x7F and see if that makes a difference. I did try to help someone out with some of this in the past, but the specifics are really beyond my expertise: http://support.nowsms.com/discus/messages/1/884.html | |||
