| Long Text Message Gives Following Error |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - SMS Issues ⬆ Archive through January 23, 2007 ⬆ |
◄ ► |
| Author | Message | |||
| salman raza New member Username: Salman4raza Post Number: 3 Registered: 10-2006 |
I am using motorola C390 as gsm modem, it send one sms, but if tries to send more than one concateneted sms i gives error. 11:16:56:468 [2] ThreadProcessModem: Processing SAR-03008677725-d8-2-1.req... 11:16:56:468 [2] ThreadProcessModem: OUT: AT+CMGS=153 11:16:56:531 [2] ThreadProcessModem: IN: > 11:16:56:531 [2] ThreadProcessModem: OUT: 0041020B813000687727F50010A0050003D80201E661763BEC06C9C3FA30481D369BE579507A0E6A E741EE70BB0C72B95CA03B3A4C07D1D16510BACC6683D273101D5D9E93D96635684E36ABE720F29A 6D56CFC96BB579CD5693E766F2DC6C2683D4F335D9AC06ADE76CB2793D6783E661763BEC06C9C3FA 30481D369BE579507A0E6AE741EE70BB0C72B95CA03B3A4C07D1D16510BACC6683D2 11:18:57:156 [2] ThreadProcessModem: ERROR - Error waiting for response from modem (2) 11:18:57:156 [2] ThreadProcessModem: Error: ERROR - Error waiting for response from modem (2) 11:19:34:156 [2] ThreadProcessModem: Before ModemRelease - COM4: 11:19:34:156 [2] ThreadProcessModem: After ModemRelease - COM4: 11:19:40:156 [2] ThreadProcessModem: Before ModemAllocate - COM4: 11:19:40:156 [2] ThreadProcessModem: After ModemAllocate - COM4: - OK 11:19:40:156 [2] ThreadProcessModem: Re-initializing modem: COM4: ... 11:20:28:265 [2] OpenDevice: Could not negotation modem speed 11:20:28:265 [2] HammerNonResponsiveModem: Begin 11:21:58:296 [2] HammerNonResponsiveModem: FAILED 11:21:58:296 [2] ThreadProcessModem: Before ModemRelease - COM4: 11:21:58:296 [2] ThreadProcessModem: After ModemRelease - COM4: this is the smsdebug.log discription of the activity kindly guide. also how can i disable more than one sms same time from server side, concatenated? also how can i disable sms if some other country code found, from server side. | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 6756 Registered: 10-2002 |
Hi, There are definite bugs in most Motorola phones that prevent them from being used to send SMS messages that include "User Data Header (UDH)". Usually, you would see "CMS ERROR: 304" reported back as the error code, but it appears this model is just getting confused, and becoming unresponsive. Unfortunately, since I've yet to see a Motorola phone that could be used as a GSM modem for sending SMS messages that include UDH ... I have to write this off as a limitation of the modem. Without support for UDH, they are limited to text messages only. There is an SMSGW.INI file setting that can be used to prevent any non-text messages from being sent to the device, which would help prevent this particular modem from going off-line and becoming unresponsive ... but unfortunately, aside from that, all I can suggest is a different modem. To disable all binary SMS messages from being sent to the device (including long SMS), edit SMSGW.INI, and under the [Modem - driver name] header, add ModemTextMode=Yes. (This setting does have the side effect that it uses text mode AT commands instead of PDU mode AT commands.) To stop the server from accepting messages addressed to a different country code, you would need to implement an SMS accounting callback that rejected the messages: http://www.nowsms.com/support/bulletins/tb-nowsms-001.htm If that is too complicated, you could also just silently "throw away" such messages. First, you want to make sure that your real SMSC connection does not have "Support any outbound message traffic" checked. Define "Preferred Connection for" prefixes for valid recipient addresses that should be routed via this connection. (E.g., "+44*" and/or "0*". Include "*" to match 0 or more characters, or "?" to match exactly 1 character as a wildcard ... see http://support.nowsms.com/discus/messages/1/18056.html for an unusual explanation that may help you understand.) Now the only SMS messages that will be routed via this connection are the ones that match the "preferred connection" list. Messages to other destinations will be discarded. If you want to see the discarded messages (and maybe generate an error back), then you could define a dummy HTTP SMSC entry in NowSMS to have NowSMS make an HTTP request to a URL that you provide every time it has a non-routable message. Define this URL as an HTTP SMSC, and check "Support any outbound message traffic". This means that any recipient addresses that are not in another SMSC's "Preferred connection" list will be routed via this dummy HTTP SMSC connection. -bn | |||
