Greetings All !
Several weeks ago, I had several pieces of equipment get "fried" due to power surges. (I've since then had the electric company come out and give us whole-house surge-protection.)
Two items that I seem to have lost in the failure were a serial-to-USB adapter and my NetCallerID box. So, I've been without the WAF NetCallerID functionality for almost two months now.
I just bought and installed a new PCI card with two RS232 serial ports on it. I decided to go this way instead of the USB route, as I was having trouble getting this old Dell Optiplex 100 to recognize any sort of USB expansion device / ports.
So, I bought that PCI card and a brand new NetCallerID box. I set them both up this morning and then cycled the box.
When Homeseer comes up it does write the following to the log file:
"Script version 1.1.6: Port opened on Com 3"
And yet, I can call my house and WAF NetCallerID never seems to "kick in". There's never any logging about the incoming call.
I opened up Hyperterminal and verified that I could NOT connect to Com3 (as it was in-use) and yet COULD connect to Com4 (the second port on that PCI card), so I THINK everything is alright with that card and its drivers.
But I did have some slight difficulty, when I installed the PCI card, in choosing the correct drivers, as the card's manual wasn't specific about which driver (off of their CD) to choose if one was running XP.
So, like I said, since I got that message from Homeseer, and since I couldn't connect to Com3 with Hyperterminal, I THINK everything's alright with the connection, but I'm not entirely sure.
And I'm not quite sure how to troubleshoot things from here. Is there anything else I can do to make sure that Com 3 (and its drivers) are working properly? Is there anything else I can do to figure out why Homeseer isn't triggering the WAFNET script?
I don't have anything wrong in my config file (below), do I? It's set to go fire off a customized script. The file's last modification date is 04/06/06, which is about the time I thought I took the power surges. Can't remember WHAT, if anything, I may have modified here:
[Settings]
InstallDone=True
i_com_port=3
i_com_port_resource=3
i_hsp_installed=0
i_hs_announces_caller=0
s_cid_prefix=
i_cid_reversed=1
i_cid_comma_delimiter=0
i_call_external_script=1
s_script_name=WAF-NetCallerID-Sample-CID-Processing_DR4296.vbs
s_function_name=process_ncid_data
s_phone_list_file=phone_list.txt
i_enable_logging=1
That "i_hs_announces_caller" is suppossed to be zero if you're handing off to your own custom script, right?
Thanks!
-= Dave =-
Several weeks ago, I had several pieces of equipment get "fried" due to power surges. (I've since then had the electric company come out and give us whole-house surge-protection.)
Two items that I seem to have lost in the failure were a serial-to-USB adapter and my NetCallerID box. So, I've been without the WAF NetCallerID functionality for almost two months now.
I just bought and installed a new PCI card with two RS232 serial ports on it. I decided to go this way instead of the USB route, as I was having trouble getting this old Dell Optiplex 100 to recognize any sort of USB expansion device / ports.
So, I bought that PCI card and a brand new NetCallerID box. I set them both up this morning and then cycled the box.
When Homeseer comes up it does write the following to the log file:
"Script version 1.1.6: Port opened on Com 3"
And yet, I can call my house and WAF NetCallerID never seems to "kick in". There's never any logging about the incoming call.
I opened up Hyperterminal and verified that I could NOT connect to Com3 (as it was in-use) and yet COULD connect to Com4 (the second port on that PCI card), so I THINK everything is alright with that card and its drivers.
But I did have some slight difficulty, when I installed the PCI card, in choosing the correct drivers, as the card's manual wasn't specific about which driver (off of their CD) to choose if one was running XP.
So, like I said, since I got that message from Homeseer, and since I couldn't connect to Com3 with Hyperterminal, I THINK everything's alright with the connection, but I'm not entirely sure.
And I'm not quite sure how to troubleshoot things from here. Is there anything else I can do to make sure that Com 3 (and its drivers) are working properly? Is there anything else I can do to figure out why Homeseer isn't triggering the WAFNET script?
I don't have anything wrong in my config file (below), do I? It's set to go fire off a customized script. The file's last modification date is 04/06/06, which is about the time I thought I took the power surges. Can't remember WHAT, if anything, I may have modified here:
[Settings]
InstallDone=True
i_com_port=3
i_com_port_resource=3
i_hsp_installed=0
i_hs_announces_caller=0
s_cid_prefix=
i_cid_reversed=1
i_cid_comma_delimiter=0
i_call_external_script=1
s_script_name=WAF-NetCallerID-Sample-CID-Processing_DR4296.vbs
s_function_name=process_ncid_data
s_phone_list_file=phone_list.txt
i_enable_logging=1
That "i_hs_announces_caller" is suppossed to be zero if you're handing off to your own custom script, right?
Thanks!
-= Dave =-
Comment