Caller ID Superfecta » Winunciator

I thought about this when i was creating the system - and didnt do anything about it. Both the data source and the winunciator.exe will be updated to pass a token so that winunciator cant be so easily spooked by random data reaching its port.

Added some data validation checks., changed seperator characters. The system still needs more work in this erea - as some occasion crash behavior is stil seen.

Im guessing these are related to the length of the incomming data (specifically the phone number) but will need some more failure reports before I can figure it out for sure.

Awaiting future failure reports before more wrok can be done. Some data authentication is nowpresent to prevent some of the crashing when data formatted in an unexpected way is recevied by the winunciator.

Submitted by /peter:

Yes i´ve got a "Run-time error '5' Invalid procedure call or argument"
After a recived caller id... I havn´t had time to test Winunciator until
tonight..

I put it in debug mode but i didnt get any more info there..

It happends after the cid and name is read.. I´ve tried to start the program and just press repete and then it reads the things
thats in the boxes like it should without any crash.. Is there any restart of the service that listen for the info after the name is read?

Keep the info coming guys - Im actively working on trying to duplicate, and fix these remaining crashes.

When posting info, please include the port you are using to listen on and the data format you have selected.

In fact, any information you can provide about how to trigger it reliably would be most welcome - including test phone numbers and exact proceedures. Things always get fixed fastest when I can duplicate the issue.

The recent builds of Win-nunciator are 1 million times more stable than the initial releases were. The current released version (as of this writing) is 1.1.2.

A beta version of 1.1.3 has been posted under another ticket -- and we are awaiting feedback before posting it as a public version release.

Under some rare circumstances, I am still seeing a "pseudo-crash" behavior. So far there's only been one-but I would like to understand what causes it and fix it so it no longer occurs. In this one remaining circumstance, instead of crashing the Win-nunciator application outright -- a socket error occurs (I always run in debug mode -- LOL) and then no more data is received until the Win-nunciator is stopped and restarted. I have only been able to get it to do that one time in the last four days, so it may take some time to ferret out understanding correct the remaining issue. It does seem related to the receipt of malformed HTTP requests.

QS: Pass. No further incidents of random crash have been reported