Sending messages suddenly generates "communication error"! | Search |
NowSMS Support Forums ⬆ NowSMS Support - MMS & Advanced Issues ⬆ Archive through June 06, 2005 ⬆ |
◄ ► |
Author | Message | |||
Tiago Loureiro Unregistered guest |
Hello, I'm designing a MMSC for a project for my university and all of the sudden came across this problem... everything seemed to work fine, we were able to send a message to our server, send out notification and then fetch the message but, all of the sudden, the reply from our server seems to not be functioning... When we submit a message to our server we always get the message "Communication error" although our server successfully receives the message and sends back the reply as it always has and it used to work perfectly... what can be the source of this problem? Is it possible that the carrier has somehow blocked the access from a server that is not their own? Is it possible that the necessary HTTP headers have changed? We are one step away from finishing our project but this problem that we see no reason to happen has blocked us completely! Any sort of help will be welcome! Thank u | |||
Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 4325 Registered: 10-2002 |
Sorry, this is the support forum for the Now SMS/MMS Gateway product. I have to give priority to answering support questions relating to our product. As a brief comment, if you are receiving the MMS message request, then it doesn't sound like you are being blocked ... it sounds like the MMS client doesn't like the response that your server is returning. Double check that you really haven't changed anything. And double check the response that you are generating. Try a phone connected to a different operator. | |||
Tiago Loureiro Unregistered guest |
I'm sorry I've posted this in the wrong section... but by the way, is there anywhere where I can check exactly how my answer should look like (aka, which HTTP headers must go...)? | |||
Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 4337 Registered: 10-2002 |
To be honest, other than setting the correct MIME type ... and formatting the MMS packet correctly, I can't imagine what it would be. Other than the MIME type, I don't think any client is that picky about the HTTP header. It's more likely a problem in the MMS data in the response. I'd suggest using Ethereal to take a closer look at the actual requests to/responses from your server. -bn |