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]

RE: Caller ID


  • Subject: RE: Caller ID
  • From: "Steve Jones" <email@xxxxxxxxxxxxxx>
  • Date: Mon, 7 Jun 2004 07:40:54 +0100

------=_NextPart_000_000B_01C44C62.C3E160D0
Content-Type: text/plain;
charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Yes you should be able to see that from the screen print, it says it was
successfully succeeded!
=20
=20





Regards=20


Steve Jones=20
mailto:email@xxxxxxx=20
Tel 07966 339 409=20

-----Original Message-----
From: Kevin Hawkins [mailto:lists@xxxxxxx]=20
Sent: 06 June 2004 13:03
To: xap_automation@xxxxxxx
Subject: RE: [xap_automation] Caller ID


Steve - did you install the ActiveCTI  OCX - and the xAP OCX ??=20=20
=20
There are some instructions in the beta distribution download available
fro=
m
the previous link.
=20
<http://www.ukusa.demon.co.uk/xAPTel.zip>
http://www.ukusa.demon.co.uk/xAPTel.zip
=20
Although in your particular scenario you arent going to be using Active CTI
the application you have caters for switching between the Meteor (which
use=
s
this) and the TAPI config which doesnt so it still requires the ActiveCTI
OCX.
=20
Kevin
=20
=20=20=20=20


_____=20=20

From: Steve Jones [mailto:email@xxxxxxx]=20
Sent: 06 June 2004 12:51
To: xap_automation@xxxxxxx
Subject: RE: [xap_automation] Caller ID


Kevin,
=20
I have installed "CallerIDActiveXDemo" then ran your app but i am
getting a
error, please see attached screen print.
=20
Steve
=20
=20





Regards=20


Steve Jones=20
mailto:email@xxxxxxx=20
Tel 07966 339 409=20

-----Original Message-----
From: Kevin Hawkins [mailto:lists@xxxxxxx]=20
Sent: 03 June 2004 21:50
To: xap_automation@xxxxxxx
Subject: RE: [xap_automation] Caller ID


Steve - I have sent you a new version offlist which should work using TAPI
:-)=20=20
=20
- let me know how you get on ...
=20
Kevin


_____=20=20

From: Steve Jones [mailto:email@xxxxxxx]=20
Sent: 03 June 2004 16:37
To: xap_automation@xxxxxxx
Subject: RE: [xap_automation] Caller ID


Kevin that's ok, I can work around it lets do that.
=20
Once again thanks for your work on this
=20
Steve
=20
=20





Regards=20


Steve Jones=20
mailto:email@xxxxxxx=20
Tel 07966 339 409=20

-----Original Message-----
From: Kevin Hawkins [mailto:lists@xxxxxxx]=20
Sent: 03 June 2004 16:17
To: xap_automation@xxxxxxx
Subject: RE: [xap_automation] Caller ID


I was lookin at the TAPI approach a bit and I am sure this will be the best
way but it may take a little longer than the modem kludge. I could code you
a specific Zoom support quicker Steve if you are keen to go on this - it
would monopolise the modem though whilst running.=20
=20
Kevin
=20


_____=20=20

From: Steve Jones [mailto:email@xxxxxxx]=20
Sent: 29 May 2004 14:28
To: xap_automation@xxxxxxx
Subject: RE: [xap_automation] Caller ID


=20
=20

You can always free the modem up by quitting xAPTel should you need to use
it. COM port 'sharing' is not practical to accomplish - however I will look
at whether I can get at the TAPI CID info (as YAC does) later. Does YAC
allow you to us the modem from other apps eg for internet dialup whilst it
remains running still handling incoming CID when needed ? Or do you have to
quit YAC to use the modem ?  It is possible that the init strings sent by
a.n.other app could disable the CID reporting too
=20
=20
K=20
=20
Kevin
=20
Even when YAC is active and sitting in the system tray I can still use the
modem to connect to the internet etc.   When I disconnect from the internet
Yac automatically allows CID info to come in again.



I  just double checked this and it works ok
=20
Steve=20










xAP_Automation Main Index | xAP_Automation Thread Index | xAP_Automation 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.