| NowMMS, EAIF and Nokia MMSC |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - MMS & Advanced Issues ⬆ Archive through December 01, 2004 ⬆ |
◄ ► |
| Author | Message | ||||
| Dmitry Unregistered guest |
Hello ! I am try to using a trial version of NowSMS 5.50 with Nokia MMSC 2.1 (protocol EAIF). MMS from MMSC side received and decomposed successfully but when I sending message to MMSC, MMSC cannot receive my message. I think problem in http-header which sends from NowSMS to MMSC: connection: close When I using a Nokia NMSS SDK 1.4 to connect to MMSC, MMS sends ok and http-header looks like: connection: keep-alive Can anyone help me with this problem ?
| ||||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 3201 Registered: 10-2002 |
Hi Dmitry, That is definitely confusing. The HTTP "Connection:" header shouldn't have any bearing on this. I'd like to try to get some more diagnostic information on what is occurring. Could you please download the update for NowSMS at http://www.nowsms.com/download/nowsms550e.zip. And let's see if there is any additional information in the log file with that version. -bn | ||||
| Dmitry Unregistered guest |
Hi, Bryce ! I got update nowsms550e.zip and test connection with a new version. Same problem exists. Maybe you compile a version with additional debug information? I think in this case we can better understand problem and solve it. Other ideas ?
| ||||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 3211 Registered: 10-2002 |
Hi Dmitry, Actually, we did get some helpful information there. The connection seems to be reset while we are sending. It seems that there is something that the server does not like, and it is resetting the connection. Perhaps an issue of IP address restrictions (are you trying with the SDK from the same IP)? Can you try a smaller message? I'm wondering if we still see these indications in the debug log with a smaller message: SendData: Error on send data HttpResponseWait: ioctlsocket indicates end of request HttpResponseWait: Expected 0 bytes, got 0 bytes | ||||
| Dmitry Unregistered guest |
Hi, Bryce ! You are right. When I sends a smaller message (small text body part) - MMSC receives MMS ok and sends to me valid http-response '204 No content'. About IP restrictions - I trying Nokia SDK from the same IP. I can't speak anything wrong about operator's MMSC - it is real MMSC in commercial use.
| ||||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 3220 Registered: 10-2002 |
Hi Dmitry, Ok. This is getting interesting. I'm going to e-mail you an update that is going to try something different, and report some more debug info to try to figure this out. If you don't receive my e-mail, please send a message to nowsms@now.co.uk and I'll reply back with the file. -bn | ||||
| Dmitry Unregistered guest |
Hi Bryce, Thank you very much ! It seems to all works fine ! Can you tell me about problems were here ?
| ||||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 3239 Registered: 10-2002 |
Hi Dmitry, I'm glad that resolved it. We'll have an official patch that incorporates this change shortly. I am a bit confused myself, but there seems to be an issue of buffering with the TCP/IP connection to the provider. Normally the IP stack would do more buffering, but we are now doing some of our own buffering. -bn | ||||
MMSCDEBUG.LOG
