The main problems the older Hayes modems have are polarity sensitivity
and insufficent sensitivity to the Caller ID signal. Increasing the gain
on the line may help, and Hayes can tweak the hardware if you're desperate,
but there are no guarantees it will work. It is also worth disconnecting
the bellwire - Ken Williams
found that this was essential for his Hayes 5670GB to detect Caller ID.
These problems have been compounded by complete confusion over which modems
are meant to have Caller ID capability and which not - the boxes are not
wholly reliable on this.
As I understand it, the the Caller ID abilities of Hayes Europe modems
are as follows :
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Since the Zoom takeover, no internal claim to have Caller ID, but the
Accura 56K external #08-02990 does - this is not confirmed.
Please let me know of other models that work, or any mistakes I've
made on this - I don't have any of these modems.
It's a good idea to make sure you have the latest firmware and drivers.
Apparently the .inf file specifies "CALR" instead of "NMBR", which may
confuse some programs - TAPI seems to handle this OK though. If you're
still having problems, try reading some of the following posts from "Mike"
:
From ???@0x00000B72 Tue Apr 14 22:10:31 1998
Path: news.u-net.com!peer.news.zetnet.net!dispose.news.demon.net!demon!cpk-news-hub1.bbnplanet.com!
news.bbnplanet.com!newsfeed.internetmci.com!152.163.199.19!portc03.blue.aol.com!audrey01.news.aol.com!not-for-mail
From: b254168@aol.com (B254168)
Newsgroups: uk.telecom
Subject: Re: Caller ID on modems
Date: 5 Oct 1997 23:34:49 GMT
Message-ID: <19971005233401.TAA09508@ladder01.news.aol.com>
NNTP-Posting-Host: ladder01.news.aol.com
X-Admin: news@aol.com
References: <01bcd1b3$21768d60$575295c1@paul>
Organization: AOL, http://www.aol.co.uk
X-Newsreader: AOL Offline Reader
Lines: 51
Xref: news.u-net.com uk.telecom:806
Status: N
In article <01bcd1b3$21768d60$575295c1@paul>, "Paul Glenton"
<paulglenton@dial.pipex.com> writes:
>Subject: Re: Caller ID on modems
>From: "Paul Glenton" <paulglenton@dial.pipex.com>
>Date: 5 Oct 1997 17:19:35 GMT
>> > still waiting for Hayes to return my Accura 336 which *is supposed*
>> > to do BT CLI but doesn't on mine. Wonder what's hap to it.
>I just bought a hayes accura modem which supports caller ID. At the
start
>it wansn't very reliable but reversing the polarity of my line seemed
to
>sort things out and it works fine now!!
Hi Paul,
My first Accuara 56K SpeakerPhone had bust CLID, but the replacement modem does BT CLID: sometimes :((((
That 'Line-Phase/Polarity Reversal' tip was something I read from Supra (USA) when folk over there were having problems with CLID, and yet it was something I'd forgotten, so I'll try that (after that, I'll ask BT to "Up-The-Gain" of the CLID signal on my line, but only if this is absolutely necessary, as it may 'muck-up' high-speed Comms. tasks).
Are you using SmartCon software (as supplied) with it, or another software package and, if so, which package.
SmartCon's not bad, but (when the Caller ID actually works: yes, I'm still having problems even though Haze have given me a replacement modem) it does not attempt to match the Calling Number with those in the Phone Book entries. It would be nice if a matching entry "flashed-up" when the phone is ringing.
The other thing about SmartCon is that, when sending a fax, you can only attach one file to the darn thing. I quite often send out faxes made up of about 20 documents or so, hence SmartCon is no good for this purpose.
I don't know what SuperVoice is like, but I might try that unless there's any ShareWare stuff floating about.
The internal microphone, in my 56K External, is absolutely terrible: I can't speak through it (even when holding the modem up to my gob) or record out-going announcements through it [I have to go up the pub and use the PayPhone up there to record my announcements, then convert to WAV and Import that as a message :)))]. The recorded messages (when using the 'beat-in' microphone) have a terrible 'buzzing' noise :(((
Mike
From ???@0x00000E3D Tue Apr 14 22:10:31 1998
Path: news.u-net.com!peer.news.zetnet.net!dispose.news.demon.net!demon!news.idt.net!ais.net!newsfeed.internetmci.com!
152.163.199.19!portc03.blue.aol.com!audrey01.news.aol.com!not-for-mail
From: b254168@aol.com (B254168)
Newsgroups: uk.telecom
Subject: Re: Caller ID on modems
Date: 11 Oct 1997 11:06:58 GMT
Message-ID: <19971011110601.HAA25538@ladder01.news.aol.com>
NNTP-Posting-Host: ladder01.news.aol.com
X-Admin: news@aol.com
References: <01bcd1b3$21768d60$575295c1@paul>
Organization: AOL, http://www.aol.co.uk
X-Newsreader: AOL Offline Reader
Lines: 76
Xref: news.u-net.com uk.telecom:1516
Status: N
In article <01bcd1b3$21768d60$575295c1@paul>, "Paul Glenton" <paulglenton@dial.pipex.com> writes:
>Subject: Re: Caller ID on modems
>From: "Paul Glenton" <paulglenton@dial.pipex.com>
>Date: 5 Oct 1997 17:19:35 GMT
>I just bought a hayes accura modem which supports caller ID. At the
start it wansn't very reliable but reversing the polarity of my >line seemed
to sort things out and it works fine now!!
>
>Paul
Hi Paul,
This is most strange.
I've just conducted a test with my Hayes Accura K56 flex SpeakerPhone modem (which does UK CLID) and BT Caller Display 50 Unit.
By reversing the polarity of the line neither worked at all (in displaying calling numbers).
The Hayes Accura has been very selective in deciding whether it would return CLID info. back up the serial port. But I think I may know why this is:
My SetUp is that I have three extensions coming off of my master socket.
Extension 1 has a normal telephone attached.
Extension 2 has the BT CD50 unit.
Extension 3 has the Hayes Accura modem.
The BT CD50 is 100% reliable in displaying (reporting) Calling Number info.
The Hayes Accura picks-up the CLID sometimes. I have noticed that, by picking-up my telephone (Extension 1) and making a call to someone that, afterwards, the Hayes no longer returns CLID info. back upto the software. Strange ?
I think what is happening is this. The Hayes is monitoring the line for a polarity reversal (it will then be ready to receive the alert burst followed by the CLID info. from the exchange). By making a phone call (without the Accura knowing about it) when my (outgoing) call connects the polarity (on the line) is reversed (and I start to get charged by BT!). I reckon that this is throwing the poor little Accura into a state of confusion.
After that, the next incoming call will not display CLID. But, provided I do not pick-up the telephone in the meantime, it will pick-up the 2nd incoming call CLID info. This is because the SmartCon software (supplied) resets the modem after it has received a call (whether answered or not).
I want to do some further tests on this, but this time by plugging the telephone into the back of the Hayes Accura. The only snag with this is that the telephone will no longer "ring" on incoming calls, but I have noticed that the Accura acknowledges when a phone (that is plugged-into the back of it) is "off-hook". It also knows when the phone is back "on-hook". The advantage to this method is that the Accura will always be reset (and re-initialised) after making each call (if using SmartCon).
You know, just when I could do with an "arsenal" of incoming calls, I've received very few in the last few weeks and have had to do the tests manually by using local phone boxes to get some CLID info. sent :)))
Your experiences of Accura CLID failure would be very much appreciated (as my theory may be completely wrong).
All the best,
Mike
From ???@0x00002859 Tue Apr 14 22:10:31 1998
Path: ews.u-net.com!peer.news.zetnet.net!btnet-feed1!news-peer.bt.net!btnet!newsfeed.internetmci.com!
152.163.199.19!portc03.blue.aol.com!audrey01.news.aol.com!not-for-mail
From: b254168@aol.com (B254168)
Newsgroups: uk.telecom
Subject: Re: Caller ID on modems
Date: 24 Oct 1997 05:35:13 GMT
Lines: 223
Message-ID: <19971024053501.BAA04702@ladder01.news.aol.com>
NNTP-Posting-Host: ladder01.news.aol.com
X-Admin: news@aol.com
References: <01bcd63c$6d28bf20$2521ea9e@UKP013613.logica.co.uk>
Organization: AOL, http://www.aol.co.uk
X-Newsreader: AOL Offline Reader
Xref: news.u-net.com uk.telecom:3093
Status: N
Hi Richard, and apologies for the belated reply (due to Accura CLID testing):
In article <01bcd63c$6d28bf20$2521ea9e@UKP013613.logica.co.uk>, "Richard M Willis" <Willis@rmlogicaperiodcommercial> writes:
>Subject: Re: Caller ID on modems
>From: "Richard M Willis" <Willis@rmlogicaperiodcommercial>
>Date:11 Oct 1997 11:54:32 GMT
>
>B254168 <b254168@aol.com> wrote in article
>> I think what is happening is this. The Hayes is monitoring the line
for a polarity reversal (it will then be ready to receive the alert >>
burst followed
>..
>> reckon that this is throwing the poor little Accura into a state
of confusion.
>
>If my understanding is correct, then, irrespective of whether the
modem "knows" whether something else has caused a reversal, it
>should still be able to detect it, from whatever polarity it started
off with.
I've since dis-covered that each time the command <AT#CID=1> is issued to the modem, the CLID detection is re-set and all should be fine (but see later).
>> but I have noticed that the Accura acknowledges when a phone (that
is plugged-into the back of it) is "off-hook". It also
>> knows when the phone is back "on-hook". The advantage to this method
is that the Accura will always be reset (and
>> re-initialised) after making each call (if using SmartCon).
>
>Good so far. BTW, how does the modem signal that there is a phone
connected. I've never heard of a modem giving a serial
>connection to a connected phone before. Have to see if my accura 336
Ex does this as well.
The command, AT#CLS=8, will let the modem know if anything connected to the back of it goes "off-hook". Try this for yourself in your favourite Terminal program (with a phone connected to the back of the Accura).
Issue the command, AT#CLS=8, and after OK is returned (this may take a second, rather than be instant) lift-up your phone for around 5 seconds, then put it back "On-Hook". Notice the terminal characters returned? SmartCon uses this to reset the modem when a phone (plugged into the back) goes off-hook.
>> You know, just when I could do with an "arsenal" of incoming calls,
I've received very few in the last few weeks and have
>> had to do the tests manually by using local phone boxes to get some
CLID info. sent :)))
>
>You could always borrow a friend's mobile telephone or use 174/175/17070
to generate such calls. These would get you
> either "WITHHELD" or "1234567890" but that is sufficient to test
the datalink layer out.
I've just had a busy two days worth of incoming calls. All, but one, of the CLID's were picked-up ok. Reason for the missed CLID was that somebody phoned my number, heard the AnswerPhone cut-in, Hanged- Up immediately (it was one of them WITHHELD calls) and then (speed) re-dialed. The poor little Accura did not have time to re-initialise the modem before the first RING and this is why the CLID was missed.
To date, I've found the following factors will "Vandalise" the Accura's CLID detection:
1) Telephone appratus is used on the same phone line as the Accura, but is not connected through the Telephone Port on the back of the Accura modem.
What's happening here is that the phone line state is being changed, without the Accura knowing about it. Fix? Connect all phone equipment through the Telephone Port on the back of the Accura.
Exception: Caller ID units *will* co-exist ok on a different extension.
2) You open up SmartCom Message Centre (you know, the program where you can view received faxes, and play back recorded message) but *do not* play back any messages. What happens here is that SMC sends comands to the modem when you enter it. But it does not re-initialise the modem when you Exit. Fix? Always play-back a message each time that you enter SMC. That way, the Accura will always be re-initialised when you're done.
3) After a phone call has been completed (either outgoing or incoming: it does not matter) the phone starts ringing (ie. you get an incoming call) within 8 to 10 seconds of hanging up. What's happening here is that the Accura is not getting enough time to re-initialise before the first RING, and hence the CLID detection will not happen. Not much of a fix for this one, I'm afraid.
4) When left on overnight, and the BT Routiner test occurs on the line, then the next incoming call's CLID will not be detected. Fix? Either pick-up your phone for about 10 seconds, and then replace, first thing in the morning, or arrange to send "yourself" a fax at around 6am-7am each morning. This will ensure that the Accura is re-initialised ready for the busy day ahead.
No doubt there will be some other factors that "vandalise" the CLID detection, and I will post these in due course.
In the meantime, don't take my word for it - conduct these tests for yourself, the results of which should support my theory above and give you a better knowledge of Accura CLID detection failure:
I've been doing some tests (the results I'll publish as "The Hayes
CLI Experience"). Anyway, if you are using a telephone, or any
other phone appratus, on the same line as your Haze, make sure
you connect it to the back of the modem. You may need to make-up
a lead to do this (I did, my Haze has US RJ-11 sockets on it). Otherwise,
use an old (or temporarily borrow off a freind) RJ-11 to BT plug lead.
Make sure that you can make a call off of it. Your phone will not ring,
however, when connected to the rear of the Accura :((
This is vital because, once your Accura is initialised with the
Caller ID command "AT#CID=1" it will only be active for the next
call and that is provided no other activity has taken place on
your phone line (like BT's, damn, ROUTINER Test (the thing that
makes your phones tinkle in the night!). If you use the line
for anything else, in the meantime, like making a call, then the
Accura needs to be re-initialised in order to 'pick-up' the next
call.
To test your CLI, follows these instructions precisely:
1) Go into a Terminal program (launch it, with manual commands available). Type ATZ (and return) to make the Accura is re-set.
2) Type AT#CID=1. Make sure that the Accura is returning OK to this command!
3) Pick-up your handset and dial 17070. On answer, press 1 immediately (no need to listen to all that other drivel)
4) Put your phone down when the lady say "RingBack Test".
5) A few seconds later your phone will start ringing, and you will see RING messages coming up from the modem, but no CLI information :(((((
You can repeat this as many times as you like, but the Accura CLI will still appear to be bust.
Now, let's re-do the test, but this time transform steps 2) and 4) above (ie. do Step 3), Step 4) and then Step 2)). Make sure you have replaced your handset before doing Step 2) ! ! ! !
Just to make sure that you got that last bit, replace your Handset, and *then* enter AT#CID=1.
Now, during Step 5) above you should see this, after 2 RINGs:
RING
TYPE = VOICE
DATE = mmdd
; ie. 2-digit month and 2-digit day number
TIME = hhmm
; ie. 2-digit hour and 2-digit minute(S)
NAME = WITHHELD
NMBR = P
RING
If you run SmartCon, and connect your handset into the back of your Accura, you will notice that it 'realises' when you pick up your handset. It also knows when you've replaced it. It then re-initialises the modem! (select Display then Modem Exchanges to see what is being sent to the modem). This assumes that you have activated AnswerPhone Recorder.
What this little exercise demonstrates is that the Haze implementation of UK caller ID relies on the start-up state of the line polarity when you enter AT#CID=1. If the line polarity changes (which is what happens when you make a call) then the Accura gets well confused.
If you cannot perform this test with a Terminal Program, then you can do it with SmartCon:
1) Set SmartCon to Fax Reception (Options, Receive, Fax). Wait for SmartCon to re-initialise your modem!
2) Click on the AnswerPhone Recorder Icon. Wait for SmartCon to re-initialise your modem!
3) With your telephone plugged into the back of the Accura (this test will fail if it is not so connected!) dial 17070.
SmartCon should display a box saying something like "Voice Communication". As soon as it does this, click on the "AnswerPhone Off" icon. You will notice, at this stage, that the modem is not being re-initialised. Don't worry about this!
4) By this time, the 17070 service should have read out the number you are calling from and invited you to press 1 for RingBack Test or 2 for Quiet Line Test.
Press 1 and Hangup.
5) On hanging up, you will see the "Voice Communication" box dis-appear, and the modem will be re-initialised with the new AT commands, just for Fax reception. It takes less time to re-initialise for Fax reception, and it should (just about) do this before your phone starts ringing.
6) When your phone starts ringing, and after the second ring, you should
see the CLI info. as above with the terminal software test.
This test (ie. using SmartCon) even works with 174/175 test as well, which I couldn't get to work with my terminal program. However, 174/175 can start ringing you a slight second too early, before the Accura is re-initialised, and this of course 'vandalises' the CLI function.
Hope this helps,
Mike