Modem, Caller ID and TAPI on BT Line
- From: "Martin Burnett" <martin.burnett@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Tue, 24 Jan 2006 22:35:27 +0000 (UTC)
I have a software application functioning as a fax and answering machine.
(If anyone is interested, the software is Ventafax). Ventafax supports
Caller ID, so I needed a modem that worked with UK BT Caller ID. The Hayes
Accura V.92, model number 08-15357-72C is one such model.
However, Ventafax steadfastly refused to show me the telephone number of the
incoming call. It seems others have had similar problems although I have
never found a complete solution in these newsgroups. So...for the benefit
of anyone who has tried to solve this problem I will detail the steps here.
Most software applications communicate with the modem via TAPI. The reason
TAPI applications dont work in the UK is largely because Caller ID works
differently in the UK than the US. Although the modems themselves pick up
caller id, the modem drivers do not correctly interpret it and pass the
information to TAPI. So although there are a few modems that support BT
caller id, the drivers DONT!.
An inbound call gives the following information in the UK
TYPE = 01
DATE = 0124
TIME = 2203
NMBR=01234-123456
This is normally received by the modem in one string, not separated on to
separate lines as shown abobe. Unfortunately modem drivers cant interpret
the TYPE part of the caller id - because the TYPE is the first part of the
caller id, the modem then refuses to understand ALL of the incoming caller
id data.
In the INF file for the modem there is a section headed [CID] which contains
information on what to do with caller id information. For each of the
variables DATE, TIME, NMBR, NAME and MESG there is an entry similar to this:
HKR, Responses, "<cr><lf>DATE = ", 1, 93, 00, 00, 00, 00, 00, 00, 00, 00, 00
HKR, Responses, "TIME = ", 1, 94, 00, 00, 00, 00, 00, 00, 00, 00, 00
HKR, Responses, "NMBR = ", 1, 95, 00, 00, 00, 00, 00, 00, 00, 00, 00
HKR, Responses, "NAME = ", 1, 96, 00, 00, 00, 00, 00, 00, 00, 00, 00
HKR, Responses, "MESG = ", 1, 97, 00, 00, 00, 00, 00, 00, 00, 00, 00
This determines how the text srings are handled when they arrive at the
modem. Because there is no entry for TYPE, none of the variables gets
correctly interpreted.
To correct this, add a line as follows to the INF file
HKR, Responses, "<cr><lf>TYPE = 01", 1, 00, 00, 00, 00, 00, 00, 00, 00, 00,
00
Then uninstall the modem and reinstall. Alternatively if you don't want to
uninstall and reinstall the modem, you can edit the registry directly:
Locate the key:
HKLM\SOFTWARE\MICROSOFT\WINDOWS\CURRENTVERSION\UNIMODEM\DEVICESPECIFIC\yourmodemmodel\Responses
where "yourmodemmodel" will be the name of your modem.
On the word "Responses" right click and select New...Binary Value. Enter
the NAME as "<cr><lf>TYPE = 01" (without the quotes). Note: There MUST be
a space either side of the =.
When this has entered, double click on the entry just created and in the
value data section enter 01 followed by nine lots of 00. The last two 00
entries will automatically move on to the 2nd line. Then click OK. Exit the
registry and reboot.
Now, when a call comes in, the modem will treat the TYPE = 01 text as
informational and do nothing with it. BUT, becuase it has recognised this
as a valid string it will continue to interpret the remainder of the caller
id information and pass it to TAPI which in turn will enable TAPI enabled
software apps to read it.
WARNING: These changes are done at your own risk.
.
- Follow-Ups:
- Re: Modem, Caller ID and TAPI on BT Line
- From: Allan Gould
- Re: Modem, Caller ID and TAPI on BT Line
- Prev by Date: Re: CLIP no screening
- Next by Date: Re: CLIP no screening
- Previous by thread: CLIP no screening
- Next by thread: Re: Modem, Caller ID and TAPI on BT Line
- Index(es):
Relevant Pages
|
