This is just a curiosity now in that I built a workaround...
Windows NT 4.0 sp 6
VB 6, sp 4
I built a automated dialer using a dialogic T-1 card
24 lines
due to the nature of the third party control I am using (visual voice) each tel line needs it's own seperate program running. It won't instantiate.
So I built 24 programs and tied them back to a control program using winsocks. The control program tied to an access database for phone numbers and writes the call detail records to an ascii file.
Everything worked fine for about two weeks, (about 2 calls a minute, per line) and then one day all of the dialers were stuck in the ringing state. But after trouble shooting, I find that the winsockets were connected and sending, but were not recieving the commands.
Thinking some sort of buffering, or threads problem, rebooting seemed the thing to do, but behold, the program will not work anymore. All commands, both directions, were not being recieved, more than once or twice anyway. Slowly but surely each line would die.
The control program uses an array of 24 winsock controls, and thinking maybe port conflicts, I changed all of these and recompiled. No joy.
Tests on another NT machine, using a couple of controls, worked flawlessly, so I move the programs to a new machine, and voila, it works for two weeks and dies.
Now, even my little test program won't work on either machine.
Changing from http to udp was even less useful.
Does anybody have any idea why NT would be doing this...?
Windows NT 4.0 sp 6
VB 6, sp 4
I built a automated dialer using a dialogic T-1 card
24 lines
due to the nature of the third party control I am using (visual voice) each tel line needs it's own seperate program running. It won't instantiate.
So I built 24 programs and tied them back to a control program using winsocks. The control program tied to an access database for phone numbers and writes the call detail records to an ascii file.
Everything worked fine for about two weeks, (about 2 calls a minute, per line) and then one day all of the dialers were stuck in the ringing state. But after trouble shooting, I find that the winsockets were connected and sending, but were not recieving the commands.
Thinking some sort of buffering, or threads problem, rebooting seemed the thing to do, but behold, the program will not work anymore. All commands, both directions, were not being recieved, more than once or twice anyway. Slowly but surely each line would die.
The control program uses an array of 24 winsock controls, and thinking maybe port conflicts, I changed all of these and recompiled. No joy.
Tests on another NT machine, using a couple of controls, worked flawlessly, so I move the programs to a new machine, and voila, it works for two weeks and dies.
Now, even my little test program won't work on either machine.
Changing from http to udp was even less useful.
Does anybody have any idea why NT would be doing this...?
