Hi
I have a newly purchased Way2Call USB Hi-Phone attached to a Windows XP SP3 PC and also attached to a standard UK BT POTS phone line. I want to use the Hi-Phone with HomeSeer 2. I have the latest drivers from your website installed and the Hi-Phone worked ok with HomeSeer for a few days. However I noticed that if someone left me a voicemail message that HomeSeer kept recording for a couple of minutes, even if the calling party had hung up. I installed the Way2Call test application to see what was happening. When I dial the Hi-Phone and hang up the test application shows this in the log:
SIT detected - no circuit found.
In the UK international tone settings this makes sense as a continuous 400Hz tone is shown to be the "no circuit found". I ensured that the Hi-Phone in TAPI setup was configured to use the FastBusy/re-order tone to disconnect. I tried to change the re-order tone to listen instead for a 400Hz continual tone but this didn't work. The Hi-Phone is also configured to look at line current to detect the line's status but this doesn't work either. In the international tone settings I changed the SIT detected tone to 4000Hz (to remove it from service) and then added a new item to the congestion tone with 400Hz on, 2500 duration to try and tell the Hi-Phone that this tone means disconnect. This change had the effect of stopping "SIT Detected" being displayed in the test application but now now call progress messages are displayed. How can I make the Hi-Phone understand when the calling party has cleared down?
The Way2Call test application crashed once during use and this created another issue in that I couldn't open the Way2Call TAPI setup screen any more. I've tried rebooting the PC but if I click on the TAPI setup icon I receive a few seconds of hour glass and then nothing happens.
I've tried removing and re-installing the Hi-Phone drivers, rebooting the PC and powering the PC and Hi-Phone off for several minutes before booting again but the same thing happens. I assumed this problem was caused by the running application crashing while the TAPI setup screen was open and the TAPI application had a lock somewhere. I thought that when the app was re-started it thought it was already running and shutdown. I think I've fixed this by changing the registry key hkey_local_machine\software\Way2call\w2cusbdll\globals\DoingSetup from 1 to a 0. This now allows me to start TAPI setup. Can you let me know if there is anything else I need to change to recover from the software crash I had?
Thanks
Andy.
|