| Problem sending binary sms to custom port on mobile device |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - SMS Issues ⬆ Archive through October 31, 2007 ⬆ |
◄ ► |
| Author | Message | |||
| venkata ramana New member Username: Venkatrv75 Post Number: 2 Registered: 05-2007 |
Hi, I am using SonygEricsson-GC79 (/t-mobile) gprs wireless PC card as modem for sending binary sms using the web interface of nowsms. It doesn't seem to work. When tried to send a text msg to default port, it did work fine. Below is the log trace. Gurus, pls help. -------------------- Message type: other UDH: 06050442040000 binary data="MyTestMsg" pid and dcs=0; -----------Log file start--------- 17:37:23:484 [7] ThreadProcessConnection: Processing request /Send%20Binary%20Message%20Other.htm?PhoneNumber=17324065592&UNUSED=on&UDH=06050 442040000&Data=MyTestMsg&PID=0&DCS=0&Submit=Submit&Binary=1 17:37:23:484 [7] Debug: 1 recipient entries 17:37:23:484 [7] ThreadProcessConnection: Before message loop 17:37:23:484 [7] ThreadProcessConnection: Before message loop 17:37:23:494 [7] ThreadProcessConnection: Begin message loop 17:37:23:494 [7] ThreadProcessConnection: End message loop 17:37:23:494 [7] ThreadProcessConnection: Request processing complete 17:37:51:163 [3] ThreadProcessModem: ERROR - Error waiting for response from modem (2) 17:37:51:163 [3] ThreadProcessModem: Error: ERROR - Error waiting for response from modem (2) 17:37:57:482 [3] ThreadProcessModem: Before ModemRelease - Sony Ericsson GC79 Wireless Modem 17:37:57:482 [3] ThreadProcessModem: After ModemRelease - Sony Ericsson GC79 Wireless Modem 17:38:03:491 [3] ThreadProcessModem: Before ModemAllocate - Sony Ericsson GC79 Wireless Modem 17:38:03:491 [3] ThreadProcessModem: After ModemAllocate - Sony Ericsson GC79 Wireless Modem - OK 17:38:03:491 [3] ThreadProcessModem: Re-initializing modem: Sony Ericsson GC79 Wireless Modem ... 17:38:04:983 [3] ThreadProcessModem: Modem initialization complete: Sony Ericsson GC79 Wireless Modem 17:38:04:983 [3] ThreadProcessModem: Processing 464CBB41.req... 17:38:04:983 [3] ThreadProcessModem: OUT: AT+CMGS=25 17:38:05:143 [3] ThreadProcessModem: IN: > 17:38:05:143 [3] ThreadProcessModem: OUT: 00411E0B817123045695F200000D0600442040000E8E5393D0603 17:38:05:304 [3] ThreadProcessModem: ERROR - Modem Response (2): +CMS ERROR: 304 17:38:05:304 [3] ThreadProcessModem: Error: ERROR - Modem Response (2): +CMS ERROR: 304 17:38:05:464 [3] ThreadProcessModem: Processing 464CBB42.req... 17:38:05:985 [3] ThreadProcessModem: OUT: AT+CMGS=25 17:38:06:145 [3] ThreadProcessModem: IN: > 17:38:06:145 [3] ThreadProcessModem: OUT: 00411F0B817123045695F2AAAA0C060504420400112233445566 17:38:09:950 [3] ThreadProcessModem: ERROR - Modem Response (2): +CMS ERROR: 38 17:38:09:950 [3] ThreadProcessModem: Error: ERROR - Modem Response (2): +CMS ERROR: 38 17:38:10:050 [3] ThreadProcessModem: Processing 464CC770.req... 17:38:10:050 [3] ThreadProcessModem: OUT: AT+CMGS=25 17:38:10:211 [3] ThreadProcessModem: IN: > 17:38:10:211 [3] ThreadProcessModem: OUT: 0041200B817123045695F2AAAA0C060504420400112233445566 17:38:13:866 [3] ThreadProcessModem: ERROR - Modem Response (2): +CMS ERROR: 38 17:38:13:866 [3] ThreadProcessModem: Error: ERROR - Modem Response (2): +CMS ERROR: 38 17:38:14:016 [3] ThreadProcessModem: Processing 464CC771.req... 17:38:14:016 [3] ThreadProcessModem: OUT: AT+CMGS=25 17:38:14:116 [3] ThreadProcessModem: IN: > 17:38:14:116 [3] ThreadProcessModem: OUT: 0041210B817123045695F200000D0600442040000E8E5393D0603 17:38:14:266 [3] ThreadProcessModem: ERROR - Modem Response (2): +CMS ERROR: 304 17:38:14:266 [3] ThreadProcessModem: Error: ERROR - Modem Response (2): +CMS ERROR: 304 17:38:14:367 [3] ThreadProcessModem: Processing 464CC774.req... 17:38:15:017 [3] ThreadProcessModem: OUT: AT+CMGS=24 17:38:15:178 [3] ThreadProcessModem: IN: > 17:38:15:178 [3] ThreadProcessModem: OUT: 0041220B817123045695F200000C06050442040000F4F29C0E 17:38:18:412 [3] ThreadProcessModem: +CMGS: 104 OK 17:38:18:412 [3] ThreadProcessModem: Processing 464CC775.req... 17:38:18:412 [3] ThreadProcessModem: OUT: AT+CMGS=28 17:38:18:573 [3] ThreadProcessModem: IN: +CME ERROR: 513 17:38:18:573 [3] ThreadProcessModem: OUT: 0041230B817123045695F200001106050442040000CD3CB53CA737E767 ------------------- | |||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 7244 Registered: 10-2002 |
Can you provide details about what you are submitting for the messages that fail? I see some corrupt messages in your examples that are failing. I think the problem is that they are binary messages but the DCS is set to text. If you are submitting actual binary data, set the DCS to a value that supports binary content, such as 4 or F5. -bn | |||
