More than 160 characters from HTTP request

More than 160 characters from HTTP request SearchSearch

SMS & MMS Technical Forum » NowSMS Support - SMS Issues (Product Support Only) » Archive through June 02, 2006 » More than 160 characters from HTTP request « Previous || Next »
Author Message
Manish
New member
Username: Txttester

Post Number: 1
Registered: 04-2006
Posted on Wednesday, April 05, 2006 - 10:16 pm:   

I have configured the 2way SMS gateway to do an http request for every incoming SMS. The HTTP request simply prints some text and exists. I have noticed that when the application (called via HTTP request) prints < 160 characters, it gets delivered to the phone. However, then the application print > 160 characters, the message does not get delivered to the phone.

Can the 2way gateway process long messages in this scenario?

thanks
Manish
New member
Username: Txttester

Post Number: 2
Registered: 04-2006
Posted on Wednesday, April 05, 2006 - 10:30 pm:   

An alternative is that my application (called using an HTTP request) breaks the response and returns back multiple messages. Will that work?

Something like:

print "Content-type: text/plain\n\n";

print " .... 160 characters ...\n";

print ".... second 160 characters ...\n";

Manish
New member
Username: Txttester

Post Number: 3
Registered: 04-2006
Posted on Thursday, April 06, 2006 - 12:43 am:   

Hi !

This is the debug log:

18:34:48:375 [3] RetrieveURL:
18:34:48:453 [3] HttpResponseWait: Chunked response Ok
18:34:48:453 [3] RetrieveURL: got success response
18:34:48:453 [3] RetrieveURL: text/plain
18:34:48:453 [3] ThreadProcessInboundSMS: this is a long text message to determine

18:34:49:265 [2] ThreadProcessModem: Processing SAR-14084800824-6-2-2.req...
18:34:49:265 [2] ThreadProcessModem: OUT: AT+CMGS=48

18:34:49:343 [2] ThreadProcessModem: IN:
>
18:34:49:343 [2] ThreadProcessModem: OUT: 0041140B814180840028F4000027050003060202D6653728EC2683E6EF3A1D7D2FCFE9A0313A3D5E 97DD2078784E0F2B00
18:34:49:421 [2] ThreadProcessModem: ERROR - Modem Response (2): +CMS ERROR: 304
18:34:49:421 [2] ThreadProcessModem: Error: ERROR - Modem Response (2): +CMS ERROR: 304
18:34:49:500 [2] ThreadProcessModem: Processing 44346F07.req...
18:34:50:265 [2] ThreadProcessModem: OUT: AT+CMGS=50

18:34:50:343 [2] ThreadProcessModem: IN:
>
18:34:50:343 [2] ThreadProcessModem: OUT: 0001150B814180840028F400002A74747A0E4ACF416110FBED3E83E8653C1DD42ECFE7E17319447F 83C8657A59DE4EBBCB2005
18:34:53:343 [2] ThreadProcessModem: +CMGS: 94

OK
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 5816
Registered: 10-2002
Posted on Thursday, April 20, 2006 - 03:18 pm:   

Hi Manish,

Are you using a Motorola phone as a GSM modem?

There seems to be a bug in the GSM modem implementation of many (if not all) Motorola phones.

They return "CMS ERROR: 304" on any attempts to send a message that includes "user data header".

Unfortunately, user data header is required for any long messages (standard text messages > 160 characters or Unicode text messages > 70 characters).

There might be a firmware update available for some Motorola phones to fix this problem (but I am not aware of any such fix). The best alternative would be a different modem device.

-bn

Login Login / Register Logout Logout Search Last 30 Days Topics Topics