BG> Yeah, I'm not familiar with how the Viper has been coded to function in 
BG> adaptive answer mode, so that's quite possible, although if that's what's 
BG> happening, it's certainly not standard fax/modem behaviour.  Ordinarily, 
BG> the modem should only issue fax tones if it hears CNG tones from the 
BG> remote.

BG> What does the Viper manual have to say about that?

I don't think you want to know...

These are the problems I experienced with the Spirit Viper.
I had the modem on trial (for a second time!) for 2 days
on 1996-02-26.  On the whole, I don't have much to report
problemwise!  Third time trial started on 1996-05-03.

Problems with the Spirit Viper

1. A USR Sportster V34 is connecting to me at 28800 but without
EC.  Replacing the Viper with a Courier makes the problem go
away, which means the problem is fixable in the Viper.

2. A Netcomm M34F got a 26400 connect to me, whilst when I put
an M34F online, it connects at 28800 all the time.

3. ATW2 is documented in the manual as being the default.  It
isn't, ATW0 is.

4. ATW0 is documented in the manual as reporting only the DTE
speed.  It doesn't, it reports PROTOCOL etc.

5. S95 is documented in the manual as having a default value of 1.
It isn't, it's 46.

6. S2 says the range is "0-255 seconds".  It shouldn't have 
seconds.  It should possibly have instead that values >127 
disable the escape character.

7. S31 is documented as having a default value of 194.  This is
correct.  It is documented as having bit 2 = 1 as the default.
This is not correct with a value of 194.

8. Page 58 of the manual says that +FAA controls adaptive answer,
then shows AT+FA=1.  The list on the previous page shows +FAE
as controlling adaptive answer.

9. When I try to put either of these commands into binkley.cfg,
to answer the phone with adaptive answer...
Answer AT+FCLASS=2;+FAE=1;+FCR=1;A|
Answer AT+FCLASS=2;+FAA=1;+FCR=1;A|
it fails to recognize a data call.  In other words, adaptive answer
does not appear to work as "documented".

10. Using AT+FAA=1;A as the answer string succeeds in adaptive 
answering to a variety of data calls, but failed on a Banksia.
@EOT:

---