View previous topic :: View next topic |
Author |
Message |
tlerell
Joined: 10 Jun 2009 Posts: 2
|
Posted: Wed Jun 10, 2009 12:48 pm Post subject: Windows 2003 Server - Notepager Pro - AT&T USB Smart car |
|
|
Problem: Unable to send text messages - this use to work a week ago - now I'm getting the error below:
Getting this in the Connection Monitor response - what is CMS ERROR: 500?:
Start connection to carrier: ATTNAME
Connect using GSMAT protocol
Setting communication parameters
Attempting to reset modem
Sent: AT<CR>
Received: <CR><LF>OK<CR><LF>
Modem reset
Attempting to send carrier init string
Sent:AT&FQ0V1X4&D2<CR>
Recived:<CR><LF>OK<CR><LF>
Carrier init string sent
Sent: AT+CMGF=1<CR>
Received:<CR><LF>OK<CR><LF>
Text delivery mode entered
-------------------------------------------
Working on messge to Thomas from: Alert@email_domain.com
Formatting message
Message contained in a single packet
Sending packet
Sent:AT+CMGS="8005551212"<CR>
Received:<CR><LF>>
sent: Test Message<SUB>
Received:<LF><CR><LF>+CMS ERROR: 500<CR><LF>
Error sending packet
Attempting to hang up modem
Sent: AT<CR>
Received:<CR><LF>OK<CR><LF>
Modem hung up
Thomas - tlerell@msn.com or 919-744-8960
|
|
Back to top |
|
Tech Support
Joined: 25 Aug 2003 Posts: 4387
|
Posted: Wed Jun 10, 2009 12:54 pm Post subject: |
|
|
CMS Error 500 is a general error that is returned by a modem in response to a submit request.
The times I've seen this, more often than not, this happens most often when a phone loses coverage. (For example, if you're setting things up in a server room, and the mobile coverage is spotty because you're deep inside of a building.)
Also, there are some devices require an SMSC (Short Message Service Centre) setting, and can't send messages without an SMSC configured. Normally, the SMSC value is on the SIM card, and the device reads it from the SIM. But some devices don't read it from the SIM card. Basically, the SMSC is the phone number of the operator's SMSC. Since this was working last week, I doubt this is the case.
Now, having said that, the issue may be something else entirely. This error 500 can also be caused by an attempt to send a message to an invalid phone number. If that log you posted hasn't been edited, it looks like the you're trying to send a message to an 800 phone number. As far as I know, there aren't any 800 number cel phones but I could be wrong? |
|
Back to top |
|
tlerell
Joined: 10 Jun 2009 Posts: 2
|
Posted: Wed Jun 10, 2009 2:05 pm Post subject: |
|
|
1. Yes, the 800 number was something I typed in.
2. I'm using an AT&T Smartcard (open to ideas on a more compatible device) that works fine with the 3G Watcher/AT&T Commander software sending SMS messages...
For the last few months we finally got it to work with Notepager Pro via the GSMAT protocol.
Also - AT&T Support has not been helpful in troubleshooting in that we're using the Notepager software instead of their SMS product. Grrrr!
So with that said should I try AT&T 3rd level support regarding the SMSC/SIM stuff you mentioned in your response?
T.
|
|
Back to top |
|
Tech Support
Joined: 25 Aug 2003 Posts: 4387
|
Posted: Wed Jun 10, 2009 3:59 pm Post subject: |
|
|
Well, just to make sure we've got all of our bases covered, I wanted to point out two things.
First, there are no 8XX cellular numbers native - there MAY be an 8XX# forwarded to a cell phone but it won't forward SMS.
Second, it looks like you have an email address entered as the sender's name. You may want to change that, it may be causing the issue. Go to Tools - Settings - General and make sure your Sender's name is set to a static value that isn't an email address. |
|
Back to top |
|
|