CMS error 549 sending SMS
Added by admin about 6 years ago
I recently (I believe) started to have a problem, I can receive SMS but can't send them. This used to work a while ago with the same application, but I haven't looked at it in a while.
I get the following in the log file:
2012.01.10-12.57.17: Response: <cr><lf>+CSCA: "+40722004000",145<cr><lf><cr><lf>OK<cr><lf>
2012.01.10-12.57.17: Sending: AT+CMGS=81
2012.01.10-12.57.17: Response: <cr><lf>>
2012.01.10-12.57.17: Sending: 07910427024000F011C30B910427261031F20000A74CC33719442E83D869BB3C2C2F83D26E7B989D26B34069F7B82C1F87E9691039ED06B9DF751728E9B687D96932885C66A7ED65791E347E93CB2C105D9E0785CFE1B4DB05 2012.01.10-12.57.17: Unable to find any descripton for error code 549. Exception: Requested value '_549' was not found.
2012.01.10-12.57.17: Sending message: Unsupported feature: SendSmsFeature: Send SMS (Unable to find any descripton for error code 549. Exception: Requested value '_549' was not found.)
2012.01.10-12.57.17: Trace: at MessagingToolkit.Core.Mobile.BaseMobileGateway`1.SendMessage(Sms message)
at MessagingToolkit.Core.Mobile.BaseMobileGateway`1.Send(IMessage message)
2012.01.10-12.57.18: Sending: AT+CMMS=1
2012.01.10-12.57.19: Error in command AT+CMMS=1 : ERROR
Do you have any ideas? I believe 549 means invalid PDU length or something similar (from google searches). But why would the modem say that? Any solution? The modem is a Siemens MC35i if I remember correctly (it's in a remote location and it's been installed a long time ago so I don't remember exactly)
If you think rebooting the modem could work, I'll have a technical support guy at the remote location go and reboot it, but I'm not sure it will help.
Replies (6)
RE: CMS error 549 sending SMS - Added by admin about 6 years ago
Hi,
There does not seem to be anything wrong with the PDU. Can you validate if the phone SIM is not blocked for sending?
If the SIM is not blocked, can you send us the log files for the previous month?
Thanks
Regards
admin
RE: CMS error 549 sending SMS - Added by admin about 6 years ago
Hi,
Can you also let us know what version of the library you are using?
Try to use the latest version for .NET 4.0
Thanks
Regards
admin
RE: CMS error 549 sending SMS - Added by legenden about 6 years ago
I'm using the latest version for .NET 4.0. I upgraded to it while troubleshooting the problem.
I had someone at the remote location reboot the modem and I was able to send one SMS right after it came up. But after that one, no more luck.
I also tried the bulkgateway sample app and after about 20 tries I was able to get one SMS through.
I see a similar problem here: https://bugs.cihar.com/view.php?id=794
It's for a different library but the error seems to be related. No definitive fix that I see, except for the mention of it being a timing issue of some sort.
One thing to note is that I'm running this application inside a virtual machine, and it's COM port is passthrough'd from the Host server via named pipes. The modem is plugged into the Host. But this isn't a problem for receiving messages, and it used to work.
RE: CMS error 549 sending SMS - Added by legenden about 6 years ago
Is there a way to have a small delay between AT+CMGS=81 and the actual PDU being sent?
From what I can see from timestamps in my log, they both go through immediately one after another, down to the milisecond:
2012.01.10-02.44.53: Sending: AT+CMGS=81
2012.01.10-02.44.53: Response: <cr><lf>>
2012.01.10-02.44.53: Sending: 079104............ (pdu)
RE: CMS error 549 sending SMS - Added by admin about 6 years ago
Hi,
The PDU is sent right after the response ">" is received (which means the modem is ready). Right now there is no delay on this.
Can you try using hyperterminal to send the SMS from the virtual machine to see if the same problem is still happening?
Thanks
Regards
admin
RE: CMS error 549 sending SMS - Added by legenden about 6 years ago
Ok, it seems like the named-pipe/com port virtualization stuff I was using is faulty for some reason. I saw the PDU ending up corrupted on the host, either missing characters or having doubled characters.
I'm not sure who to blame but I got it working again by switching software and using Physical COM on host->Ethernet->Virtual COM on VM. All is well now. This might help someone. :)