Path: utzoo!mnetor!uunet!cbmvax!grr
From: grr@cbmvax.UUCP (George Robbins)
Newsgroups: comp.dcom.modems
Subject: Re: Trailblazer Madness
Message-ID: <3445@cbmvax.UUCP>
Date: 9 Mar 88 16:38:20 GMT
References: <3362@cbmvax.UUCP> <1024@neoucom.UUCP> <589@nexus.UUCP>
Reply-To: grr@cbmvax.UUCP (George Robbins)
Distribution: comp
Organization: Commodore Technology, West Chester, PA
Lines: 19
Keywords: telebit trailblazer s50 carrier

In article <589@nexus.UUCP> edm@nexus.UUCP (Ed Morin) writes:
> I've noticed a lot of talk about switching the carrier detect sequence around
> on the 'Blazers (i.e. setting S92=1).  Have people experienced a lot of prob-
> lems with non-Blazer modems not connecting when it puts out the "Moose call"
> first rather than last?  I have tried several different 1200/2400 baud modems
> out and have never had a problem detecting carrier (eventually).  What about
> the rest of you folks out there?

In my case, it did confuse incoming calls from another site.  The key seems
to be whether the calling modem has "call progress detection" smarts.  If
all it listens for is the normal answer tone sequence, no problem.  If it
is trying to discriminate between ring / busy / voice responses to the call,
then the "moose call" or recognition / training sequence can cause the
smart modem to abort the call and return a "voice" or other response.

-- 
George Robbins - now working for,	uucp: {uunet|ihnp4|rutgers}!cbmvax!grr
but no way officially representing	arpa: cbmvax!grr@uunet.uu.net
Commodore, Engineering Department	fone: 215-431-9255 (only by moonlite)