RE: Caller ID

["Steve Jones" <email@xxxxxxxxxxxxxx>]

------=_NextPart_000_000A_01C44340.11CA3910
Content-Type: multipart/alternative;
boundary="----=_NextPart_001_000B_01C44340.11CA3910"

------=_NextPart_001_000B_01C44340.11CA3910
Content-Type: text/plain;
charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable

Kevin,
=20
Thanks for your reply.  Please see addin text below.
=20

-----Original Message-----
From: Kevin Hawkins [mailto:lists@xxxxxxx]=20
Sent: 26 May 2004 12:51
To: xap_automation@xxxxxxx
Subject: RE: [xap_automation] Caller ID


Hello Steve,
=20
I take it by "xAP Caller ID " you mean you have installed the
Pace
software from mi4 ?=20=20
=20
Yes that is what I meant to say=20
=20
What I am guessing is happening here is that the Zoom modem does not
enable and report CallerID information in the same way that the Pace modem
does and the mi4 application is specifically for the Pace modem as the name
suggests. Are you using the Zoom modem in the UK on a BT CallerID system I
wonder ? - just curious as it's nice to know there is another modem that
works here for CallerID.=20
=20
Yes I'm using BT Caller ID in the UK=20
=20
So we need an application to support the internal Zoom modem I guess.
Can you provide  the 'AT' command sequence that is sent to the modem to
'enable' Caller ID reporting and then an example of the message that the
modem sends when it receives an incoming call. The very best way to do this
would be to open a communications window using something like Hyperterminal
to the modem on COM3  I am ok up to here ! and then show the typed command
to the modem and the responses,  < I don't understand this part!  and
then
to dial in and show the incoming callerID message. Copy this screen and
pos=
t
it here. With that information it should be possible to fairly easily add
support for your modem and get you up and running in xAP. Indeed if anyone
else has a CallerID capable modem (US or UK) that they would like supported
then please supply this information.=20
=20
Here is a copy of a post on the TiVo community by BobBlueUK which maybe of
interest:-
=20
There aren't very many modems around that support UK/BT CLI, and even fewer
internal ones. Only three manufacturers have ever officially or
unofficiall=
y
supported it to my knowledge - US Robotics (now owned by 3Com), Hayes (now
owned by Zoom) and PMC/Pace Consumer Electronics (now no more!). Of these,
=
I
think Hayes was the only one that made internal modems that supported UK/BT
CLI (although PMC made a lone ISA version), so you're choice of modem is
limited to those - you might be able to pick one up on Ebay?

Personally I went for an external US Robotics modem (there are a fair
numbe=
r
of USR external modems that support UK/BT CLI) - works a treat with YAC on
my TiVo!   <http://www.tivocommunity.com/tivo-vb/images/smilies/smile.gif>=
=20

Some more useful info on which modems support Caller ID in the UK at the
following links:

<http://www.modem-help.co.uk/help/clid.html#modem>
http://www.modem-help.co.uk/help/clid.html#modem
<http://www.ainslie.org.uk/callerid/cli_faq.htm#Q_18>
http://www.ainslie.org.uk/callerid/cli_faq.htm#Q_18
<http://www.uk-software.com/whoscall...htm#whichmodems>
http://www.uk-software.com/whoscall...htm#whichmodems=20
=20
Also this TiVo post may also be of interest:-
=20
There are two ways programs can communicate with your modem to get caller
I=
D
info - either directly with the modem over the com port, as your
'communicate' program probably does, or through Windows' TAPI (Telephony
API), as YAC does. Using Windows TAPI is much easier for programmers as it
basically lets Windows worry about how to communicate with the modem, but
many modem drivers have incorrect settings that don't work with TAPI that
well...

So, what to do:

First, check that TAPI is the problem. Go to your modem's properties
settings and with any luck you'll find a 'view log' option on the
diagnostics tab. Click this and you'll see a log of all communication with
the modem - look for lines containing NAME, TIME, DATE, NMBR, MESG (after
you have received an incoming call) as these represent the caller ID info.
When TAPI is working these should all be on one line, but you may find them
split up over multiple lines (e.g. N AME, TI ME, DAT E, N MBR, ME SG etc),
or they may be surrounded by erroneous <cr> or <lf> strings. If
so, TAPI is
your problem...

How to fix it:

You'll need to modify the modem settings in your registry slightly,
following the instructions  <http://www.talkingcallerid.com/ModemDriver.htm=
>
here. It's not difficult and should only take a minute or two... Once
you'v=
e
made the changes check your modem log again after an incoming call and see
if things have improved. If not, you may have to improvise a little and
change the modem settings to look out for AME, ME, E, MBR, SG instead of
NAME, TIME, DATE, NMBR, MESG (as in the above example). Basically these are
the markers that identify caller id info and TAPI will use whatever text
follows them - so whatever follows NMBR should be the number of the
incomin=
g
caller...

I had similar problems when I first got my external USR modem up and
runnin=
g
with YAC, but it's working fairly reliably now after a bit of tinkering
wit=
h
the driver settings. Still not perfect, but I'd say 85-90% of the time it
works. Also I've noticed that when you first boot up Windows the caller ID
sometimes won't work properly on the first incoming call but will work fine
subsequently - so try repeating a few calls before you give up on it as not
working. You'll get there eventually...

=20
=20
I am about to release xAPCTI which is a Windows CID/telephony
integration conduit for xAP, hopefully the final beta will be posted here
today . The conduit initially supports CallerID and dialled digit reporting
but later will support automated dialling via xAP assuming you have capable
hardware, a Pegasus or modem of course would have this. Although my
application currently supports the Meteor, Meteor Plus and Pegasus units I
am looking to support some CID capable modems too in an upcoming version,
so with this information I can add the Zoom.  It may also be possible for
the mi4 application to be tweaked to support the Zoom too and I'll leave
that to James to address.  James if you supply me the Pace init strings and
response I can add your modem to xAPCTI if you wish...
=20
Lastly Steve, if you are struggling with this info then maybe you can point
me to a list of the Hayes 'AT' sommands that your modem uses somewhere on
the internet and I may be able to gleam some info from there. What is the
exact model number of the modem.  Hayes Zoom 3025-72-00 C (Apparently the C
denotes caller ID)
=20
Kevin=20
=20
Sorry for the long post guys, I thought it best to include as much info as
possible
=20
Steve=20
=20
=20
=20
=20


_____=20=20

From: Steve Jones [mailto:email@xxxxxxx]=20
Sent: 26 May 2004 08:53
To: xap_automation@xxxxxxx
Subject: [xap_automation] Caller ID



I have a win2000 PC with YAC installed (Yet Another CallerID) it runs ok
of=
f
an internal Zoom modem (CID compatible) fixed to com3. A little window pops
up with caller ID info in it no problems!

I have now installed Xap Caller ID and amended the properties to
"C:\Progra=
m
Files\xAP Pace\xAPPace.exe" 3=20

When I press the test button the test 1234567890 number comes up.  But when
I call my number it just says waiting for call!.

What could be wrong?,  Any help would be appreciated=20

Steve=20