| Where is Bryce? |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - MMS & Advanced Issues ⬆ Archive through December 01, 2004 ⬆ |
◄ ► |
| Author | Message | ||||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 3030 Registered: 10-2002 |
I apologise for having fallen behind in responding to questions and issues on the discussion board over the past couple of weeks. We've been very busy planning for the next release of NowSMS. While the next major release is still several months off, there are some interesting new features that we are making available before the next major release. For example, here are some of the highlights of our recent updates:
A ZIP file containing updates for v5.50 to add these and other capabilities can be found in http://www.nowsms.com/download/nowsms550d.zip. I've uploaded the changes note for this update in the following text attachment:
| ||||
| David Chkhartishvili New member Username: Datoch Post Number: 8 Registered: 06-2004 |
Bryce, I've tried to upgrade, NowSMS to version 5.50d, but without any luck. I did try several methods: 1. stopped services and copy files from zip archive - NO LUCk. 2. Uninstall nowsms, and install ver 5.50 and then upgrade to 5.50d - NO LUCK. I both cases, phone responds with something like: "no service avaliable". | ||||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 3120 Registered: 10-2002 |
David, What happens? Do you restart the services after applying the updates? If you go to the "service" page ... does the "Event Log" show any errors about port allocations? | ||||
| David Chkhartishvili New member Username: Datoch Post Number: 9 Registered: 06-2004 |
Bryce, Once again, I've tried to upgrade NowSMS: I've stopped SMS Gateway and MMSC services. Uncompressed patch in to nowsms dir, and started services again. Here is event logs (informational): NwSMS Error Report. Now MMSC v5.50d (b20040713) using SMTP port 25. NwSMS Error Report. Now MMSC v5.50d (b20040713) service started. Using web port 80. NwSMS Error Report. Now MMSC v5.50d (b20040713) service started. Using web port 8800. That's all. I still can't send messages, using v5.50d. | ||||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 3126 Registered: 10-2002 |
Let's get a debug log then, I'm puzzled. I was suspecting that maybe the ports were not being allocated properly, but it looks like they are. I assume that you're using NowSMS as an MMSC, correct? Let's enable the debug log. Manually edit MMSC.INI, and under the [MMSC] section header, add Debug=Yes. Restart the service after you make this edit (or make this edit before you start the service after updating). Attempt your connection from the phone again. Do you see any activity in the MMSCDEBUG.LOG? | ||||
| David Chkhartishvili New member Username: Datoch Post Number: 10 Registered: 06-2004 |
Bryce, Sorry for delay. Here is my debug log and you can see, that after processing MMSAccountingURL directive I got 'service not avaliable' from MMSC. I commented out MMSAccountingURL and now it works. Please tell me, what is wrong with MMSAccountingURL in ver 5.50d? It worked in 5.50. Thanks, David
| ||||
| Bryce Norwood - NowSMS Support Board Administrator Username: Bryce Post Number: 3157 Registered: 10-2002 |
Hi David, We quietly changed a lot of our internals to use HTTP/1.1 instead of HTTP/1.0. (Mostly this just affects anywhere that we retrieve a URL, such as accounting callbacks, 2-way SMS, or HTTP SMSC interfaces.) For some reason this change seems to be causing a problem for your accounting callbacks. I'm curious ... does your accounting callback return any content, or does it return a header only? I'm suspecting it is a header only, and we could be having a problem with that under some conditions. Please don't make any changes to your accounting callback script. I've got another update that I'd like to send you to see if it resolves this issue. Could you please send me an e-mail to nowsms@now.co.uk referencing this problem, and I will reply back with the update. -bn | ||||
readme.txt
