| NowSMS - v2013.06.30 sending MMS slow |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - MMS & Advanced Issues ⬆ Archive through October 14, 2015 ⬆ |
◄ ► |
| Author | Message | |||
| charles man ling New member Username: Droid Post Number: 1 Registered: 03-2015 |
Hi, We used to install the old version(v2008.06.03) . After upgrade to v2013.06.30, we find it very slow when try to connect from PHP scripts to our window NOWSMS server. From PHP example: http://www.nowsms.com/doc/submitting-mms-messages/send-mms-message-with-php function MmsSend ($host, $port, $username, $password, $data_to_send){ ... .. //hang at this section for more than 1 mins per mms. while(!feof($fp)) { $res .= fread($fp,1); // tried changing 1 to 1024 and 2048. Still same. } .. My PHP scripts hang about more than 1 mins then it continue with success result. The old version of NowSMS(v2008.06.03) give us less than 10 secs. Any idea how to tune up or setting i need to look at in order to speed up the submission from PHP to my Window based NOWSMS http call? Thank you. | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 5246 Registered: 08-2008 |
Hi, I ran a test and I don't see any delay. The script returns with no delay (under a second). My guess is that it has something to do with HTTP Keep-Alive sockets, as 2008 versions did not support them for HTTP submissions. The PHP script example assumes no Keep-Alive connection, as it is designed to wait until the server closes the connection. But that is not a problem, as the PHP script signals that it does not support HTTP Keep-Alive. Is it possible that you made any changes to the MmsSend function? For example, changing HTTP/1.0 to HTTP/1.1 would cause this problem. (HTTP/1.1 defaults to Keep-Alive unless you also add Connection: close) Here's my advice...try editing SMSGW.INI and add these settings under the [SMSGW] header: EnableKeepAlive=No AccountingKeepAlive=No This will disable Keep-Alive sockets to quickly determine if this is where the problem is. If this does not resolve the problem, enable SMSDEBUG.LOG, perform another submission, and let's look at the sequence of activity shown in SMSDEBUG.LOG. You can either post in reply here, or email the file to nowsms@nowsms.com with Attention: Des in the subject line. If you do send via email, please also post a short reply here to tell me to look for the email. -- Des NowSMS Support | |||
