+CMS ERROR: 304 with WAP Push on Mot V180

+CMS ERROR: 304 with WAP Push on Mot V180 SearchSearch

SMS & MMS Technical Forum » NowSMS Support - SMS Issues (Product Support Only) » Archive through June 02, 2006 » +CMS ERROR: 304 with WAP Push on Mot V180 « Previous || Next »
Author Message
Mark Eisenberg
New member
Username: Mheisenberg

Post Number: 1
Registered: 04-2006
Posted on Sunday, April 02, 2006 - 01:31 pm:   

Hello,

I am running a trial of the gateway software. SMS is working fine, but WAP Push is giving me grief. Debug log info is below. I'm using a V180 on Cingular. I found this posting (http://support.nowsms.com/discus/messages/1/7229.ht ml) which would seem to be a duplicate of my problem, but there was never a resolution posted. I have followed the HyperTerminal test procedure and still get the error.

Any thoughts on where I can look next?

Thanks,
Mark

10:00:34:914 [6] ThreadProcessConnection: Processing connection from 127.0.0.1...

10:00:34:929 [6] ThreadProcessConnection: Processing request /Send%20WAP%20Push%20Message.htm?WAPSL=&PhoneNumber=9788359851&WAPURL=http%3A%2F %2Fwap.oa.yahoo.com&Text=Try+this&WAPSIACTION=signal-medium&WAPSIID=&WAPSICREATE D=&WAPSIEXPIRES=
10:00:34:929 [6] Debug: 1 recipient entries
10:00:34:929 [6] Debug: 9788359851
10:00:34:945 [6] ThreadProcessConnection: Request processing complete
10:00:35:398 [2] ThreadProcessModem: Processing 442FD8D9.req...
10:00:35:398 [2] ThreadProcessModem: OUT: AT+CMGS=62

10:00:35:460 [2] ThreadProcessModem: IN:
>
10:00:35:460 [2] ThreadProcessModem: OUT: 0041030A81798853891500F5320605040B8423F0020601AE02056A0045C60C037761702E6F612E79 61686F6F2E636F6D000701035472792074686973000101
10:00:35:538 [2] ThreadProcessModem: ERROR - Modem Response (2): +CMS ERROR: 304
10:00:35:538 [2] ThreadProcessModem: Error: ERROR - Modem Response (2): +CMS ERROR: 304
10:00:36:617 [2] ThreadProcessModem: Processing 442FD8D9.req...
10:00:36:617 [2] ThreadProcessModem: OUT: AT+CMGS=62

10:00:36:679 [2] ThreadProcessModem: IN:
>
10:00:36:679 [2] ThreadProcessModem: OUT: 0041040A81798853891500F5320605040B8423F0020601AE02056A0045C60C037761702E6F612E79 61686F6F2E636F6D000701035472792074686973000101
10:00:36:757 [2] ThreadProcessModem: ERROR - Modem Response (2): +CMS ERROR: 304
10:00:36:757 [2] ThreadProcessModem: Error: ERROR - Modem Response (2): +CMS ERROR: 304
Mark Eisenberg
New member
Username: Mheisenberg

Post Number: 2
Registered: 04-2006
Posted on Monday, April 03, 2006 - 01:10 am:   

Tried a V220 and a Razr. No luck either. Is there an issue with Mot phones?
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 5768
Registered: 10-2002
Posted on Monday, April 03, 2006 - 04:16 pm:   

Hi Mark,

I'm seeing the exact same thing with a RAZR here.

And I've done some web searching, enough to see that this seems to be a common problem with Motorola phones. (It is normally referred to as a problem sending long SMS messages via the GSM modem interface.)

So far, I've tried a number of different formatting approaches, but it appears that the modem does not like messages if they include any user data header. So this effects, WAP Push, EMS, and long SMS messages. Basically, if the flag is set to indicate user data header is present, you get this 304 error.

We'll do some more investigation ... but it is hard to guess what the bug is in how the modem is handling the message. There's definitely something wrong in how the modem interface in one of these phones processes a message that includes a User Data Header.

-bn
Mark Eisenberg
New member
Username: Mheisenberg

Post Number: 3
Registered: 04-2006
Posted on Monday, April 03, 2006 - 04:35 pm:   

Bryce,

Thanks for the feedback. At least it confirms that I am not doing anything wrong. I will see if we can come up with another brand to try.

Mark

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