We do not provide support for Diafaan SMS Server in the trial period of the software but if you send the configuration (menu options 'File-Export-Configuration') and the event log (menu options 'File-Export-Event log') I will set up a test system to see if I am able to replicate the problem with your configuration and settings.
Normally, any problems with unresponsive ports in Diafaan SMS Server should be resolved after restarting the Diafaan service. When the service is stopped, Windows releases all the IP ports that Diafaan SMS Server has in use. The fact that you have to restart Windows to resolve the problem indicates that there might be an underlying problem with a firewall, virus scanner or other process that causes the problem.
We're ready to buy the full license but there's something that we've noticed on the first test and now again: sometimes one of the SMPP binds is lost (but may still show as bound) and it becomes necessary to reboot the Windows machine, restarting the Diafaan service isn't enough.
The first test was on Win7, but now I'm testing on Windows Server 2008 R2, on a dedicated VMWare virtual machine.
Not all the binds get lost, but typically the busiest ones are more affected, and I don't see the symptoms in Diafaan, I only get to know it when there is a complaint.
What can be done?
Most Users Ever Online: 494
Currently Browsing this Page:
Guest Posters: 542
Newest Members:, Henk Helmantel
Administrators: Henk Helmantel: 1084