| HTTP/1.0 500 Internal Error during MMS sending with Ericsson Z1010 |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - MMS & Advanced Issues ⬆ Archive through June 06, 2005 ⬆ |
◄ ► |
| Author | Message | |||||
| dominique pannekoecke Unregistered guest |
Hi, You will find attached 2 logfiles. 1 is for MMS sending failed with ericsson Z1010, and the other is to compare with a successfull MMS sending with motorola T725. Could you please, give me informations, regarding the reason of the HTTP 500 internal, during HTTP/POST processing. Thanks by advance Dominique pannekoecke
| |||||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 3399 Registered: 10-2002 |
Hi Dominique, Thanks for the report and the detailed logs. NowSMS is not correctly parsing an MMS submission when HTTP chunked encoding is used. Please try the update at http://www.nowsms.com/download/20040901.zip. I've tested it with some manually created test submissions, but not with a Z1010, so please let me know if that resolves the problem. -bn | |||||
| Nambu New member Username: Nambu Post Number: 8 Registered: 08-2004 |
Hi Bryce, I also have the same problem as Dominique. Then, the problem was not solved although the patch which Bryce proposed was applied. When the patch was applied, as for the TCP connection with NowSMS, not only Z1010 but other UE became impossible. As well as rebooting NowSMS, although Windows was also rebooted, the result did not change. The following is a log at that time. This log was recorded by Ethereal. (IP is hidden) Log==================================== Source -> Destination (Protocol) : Info -------------------------------------------------------- UE -> NowSMS (TCP) : [SYN] Seq=0 Ack=0 Win=24820 Len=0 MSS=1500 WS=0 TSV=23188 TSER=0 NowSMS -> UE (TCP) : [RST, ACK] Seq=0 Ack=0 Win=0 Len=0 ======================================= Thank you for your consideration. | |||||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 3747 Registered: 10-2002 |
Hi Nambu, The Ethereal trace suggests that there is no server listening on that port. Based upon our e-mail exchange, I believe you already resolved that problem by re-installing v5.51 based upon the download from this web site ... and then re-applying the patch. However, you are still having a problem with the Z1010. Is the Z1010 connecting to NowSMS directly, or is it going through a proxy/gateway? If it is going through a proxy/gateway, then there may be a problem with the proxy/gateway. If you are using Now.WAP, make sure you have v2.54 to resolve known issues with the Z1010. If you are not using Now.WAP, enable the MMSCDEBUG.LOG in NowSMS, and repeat your attempt to send an MMS message using the Z1010. Then post the excerpt from the MMSCDEBUG.LOG that shows this connection attempt. That will help us determine where the problem is. But I would suspect the problem is in the proxy. -bn | |||||
| Nambu New member Username: Nambu Post Number: 9 Registered: 08-2004 |
Hi Bryce, By re-applying the patch, server came to listen port. However, Z1010 cannnot submit MMS messages. If Windows in which NowSMS is installed is rebooted, only 1 message will succeed in transmission. The messages transmission after it serves as 500 Internal Error. I have connected with NowSMS directly by Z1010. Proxy/gateway is no using. Now, I am checking my environment. Isn't such a prblem reported else? Thank you for your consideration. | |||||
| Nambu New member Username: Nambu Post Number: 10 Registered: 08-2004 |
Hi Bryce, We finished comparing the dumping data of Ethereal when submitting is successful with the dumping data when failing. To conclude, there is not difference in the data submitted to NowSMS. When transmission went wrong, the error recorded on MMSDEBUG.LOG was as follows. --------------------------------------------- 19:19:42:628 [7] HttpChunkComplete: Invalid character following last chunk: 00 00 00 19:19:42:748 [7] HttpChunkComplete: Invalid character following chunk: 00 00 00 19:19:42:748 [7] HttpChunkComplete: Invalid length in chunked HTTP response --------------------------------------------- Thank you for your consideration. | |||||
| Nambu New member Username: Nambu Post Number: 11 Registered: 08-2004 |
Hi Bryce, We have waited for a long time. What has progress of investigation for which I asked you? Please let me know the progress. | |||||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 3768 Registered: 10-2002 |
Hi Nambu, My web browser crashed while posting a reply to you. So this reply is going to be a bit shorter than I originally intended. I am curious why you are using the MMSC without a proxy, as I would suggest that. I believe the problem is that the phone expects the MMSC to support HTTP keep-alive sockets, which we do not by default. When a proxy server is in the picture, the proxy server takes care of that. I'm going to suggest that you try another update download, where we've enabled keep-alive sockets by default. The download is http://www.nowsms.com/download/20041202.zip. If you are still seeing any "500 internal error" situations after installing that update, I would like to see the complete MMSCDEBUG.LOG that shows the transaction sequence. -bn | |||||
| Nambu New member Username: Nambu Post Number: 12 Registered: 08-2004 |
Hi Bryce, I am sorry that a reply becomes slow. I tested the patch by Z1010. As you say, Z1010 uses Keep-Alive. However, it seems that it did not cause the problem which I have said. The situation did not change with the patch. I attach MMSDEBUG.LOG and dumping of Ethereal which submittted MMS message from Z1010. Thank you for your consideration.
| |||||
| Nambu New member Username: Nambu Post Number: 13 Registered: 08-2004 |
Hi Bryce, Could you please update the status on this issue? | |||||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 3798 Registered: 10-2002 |
Hi Nambu, We've had difficulty recreating this. We see the same packet sizes trying the Z1010 on our system, but packets are slightly different. I finally devised a simulation using the data from your capture, and that allowed us to recreate the problem with a simulation, so that we'd see the same thing that you are seeing. Hopefully we should have a fix in the next 24 to 48 hours. Also, are you using the Z1010 on a UMTS/3G network, or are you using circuit switched data? I'm thinking that timing is also an issue with this problem. -bn | |||||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 3799 Registered: 10-2002 |
Hi again Nambu, Please give the update at http://www.nowsms.com/download/20041216.zip a try. We have tried in vain to recreate your problem in a live environment. But we were able to recreate it with some simulated data from your trace log. It appears that there was a boundary issue with how that particular device (I'm suspecting it is only certain firmware versions from the device) is sending HTTP chunks. If we receive a packet and it contains the end of a chunk followed only by a CR, then we get confused. In this particular case, the device seems to send the chunk followed by a CR ... and then the required LF comes in the next packet. HTTP chunking is a bizarre protocol. But based upon our simulated tests, I believe this update will resolve the problem. -bn | |||||
| Nambu New member Username: Nambu Post Number: 14 Registered: 08-2004 |
Hi Bryce, Thank you for your reply. NowSMS operated correctly with this patch. I am testing MMS using Signalling Tester by Anritsu. Thank you for your consideration. | |||||
HTTP 500 error with ericsson Z1010
