Ascend Archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: (ASCEND) TNT 1.3Ap13
The burp is actually the result of a supposedly successful v.8 or v.8bis
handshake. It's the warble preceding the burp that is probably causing the
problem. It is most likely inducing some sort of response from the old
modems that is causing the new ones to think that it's handshaking with a
v.8 or v.8bis capable caller when in fact it should drop down to a v.32bis
annex A negotiation.
V.8, followed by v.8bis, have been around since v.34. If the v.8 is enabled
by default in your 33.6 cards, and it doesn't cause problems with older
modems, then it seems probable that the fault is with the v.8
implementation in the new cards.
The comma-induced pause is probably a valid work around for users
experiencing the problem as it will prevent those modems from responding to
the warble thereby causing your K56s to use the v.32 negotiation for its
handshake.
V.8 can be disabled through AT commands. A couple of years back, this would
have been a viable alternative. Not so, now. It's the v.8 that determines
exactly the capabilities/properties (not just speed) of the remote caller
and sets up the session enabling proper support of callers using such
equipment as cellular modems, etc.
At 05:44 PM 10/30/97 -0800, Kevin Smith wrote:
>At 09:13 PM 10/23/97 -0400, Jason Nealis wrote:
>>
>>
>>On Thu, 23 Oct 1997, Phillip Vandry wrote:
>>
>>> > TR# Description
>>> >
>---------------------------------------------------------------------------
>>> [...]
>>> > 2630 Some V.32bis modems had difficulty connecting to 56K modems
due to
>>> > V.8bis tone.
>>>
>>> I'm curious - how was this fixed? By removing the V.8bis tone?
>>
>> Interesting, This has been a major problem for us with the K56
>>cards, The older V.34 modems, (Mainly 14.4)
>
>I thought that was V.32(bis?).
>
>>have taken this V.8Bis
>>tone (I call it the K56 Burp Tone) they fail handshaking because of
>>this.
>
>Supposedly Rockwell claim this is a bug in the 14.4 modems....they
>should handle this tone....I wonder if there's anything in the V.xx
>specs that cover this....any modem guru's out there (so I don't
>have to bug the Rockwell guys again ;)
>
>> Ascends only solution as of 2 days ago was to have the user enter
>>in enought commas in the dial string to delay the modem enough so
>>it would get past the two tone burst.
>
>I believe that's going to be it for a while too.
>
>I wonder if the ITU-T spec will require the V.8bis tone...... ;)
>
>
>
>Kevin
>
>
>++ Ascend Users Mailing List ++
>To unsubscribe: send unsubscribe to ascend-users-request@bungi.com
>To get FAQ'd: <http://www.nealis.net/ascend/faq>
>
>
++ Ascend Users Mailing List ++
To unsubscribe: send unsubscribe to ascend-users-request@bungi.com
To get FAQ'd: <http://www.nealis.net/ascend/faq>
References: