The UK Home Automation Archive

Archive Home
Group Home
Search Archive


Advanced Search

The UKHA-ARCHIVE IS CEASING OPERATIONS 31 DEC 2024


[Message Prev][Message Next][Thread Prev][Thread Next][Message Index][Thread Index]

HV & CTI Meteor problems




A few months ago I had to rebuild my HA server (still on w2k) due to a
hardware fault. Before this time I was successfully running HV interfaced
to CTI Meteor.

I did originally receive ActiveCID3 software with the Meteor (but never
really used it). I "played" with a couple of free CTI tools, but
eventually I paid for the HV CID key and used that instead and it worked
fine, up to the rebuild when it no longer works.

Since then I have had a couple of goes at fixing it, but without any luck.
The only thing that apprears to have changed is that I am using a different
comms port.

After the rebuild I reconfigured the comms port in HV (the red Meteor LED
goes on ok). When an incoming call comes, meteor does its normal red/green
"disco" effect - so I think that is working OK.

The problem appears to be that HV does not recognise when a call is coming
in. I have tried different comms ports, without any success.

HV is reading serial data OK (because is reads my weather station every 5
mins).

When I re-installed HV, I did so using software from HV website (v3.2a -
prom3.0) and then re-loaded a previously saved schedule (I did not re-enter
the HV CID key at this time.... maybe this is the problem). I made no other
changes to the HV config options or re-installed any software/drivers for
the CTI Meteor (as I have not got any -  other than ActiveCID3)

I am sure that it is something really stupid that I have forgot to do......
any ideas??

Regards

Clive


[Non-text portions of this message have been removed]




UKHA_D Main Index | UKHA_D Thread Index | UKHA_D Home | Archives Home

Comments to the Webmaster are always welcomed, please use this contact form . Note that as this site is a mailing list archive, the Webmaster has no control over the contents of the messages. Comments about message content should be directed to the relevant mailing list.