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: <<A HREF="http://www.nealis.net/ascend/faq">http://www.nealis.net/ascend/faq</A>> > > ++ Ascend Users Mailing List ++ To unsubscribe: send unsubscribe to ascend-users-request@bungi.com To get FAQ'd: <<A HREF="http://www.nealis.net/ascend/faq">http://www.nealis.net/ascend/faq</A>> </PRE> <!--X-MsgBody-End--> <!--X-Follow-Ups--> <!--X-Follow-Ups-End--> <!--X-References--> <HR> <STRONG>References</STRONG>: <UL> <LI><STRONG><A HREF="msg09992.html">Re: (ASCEND) TNT 1.3Ap13</A></STRONG></LI> <UL> <LI><EM>From</EM>: Phillip Vandry <vandry@Mlink.NET></LI> </UL> <LI><STRONG><A HREF="msg10284.html">Re: (ASCEND) TNT 1.3Ap13</A></STRONG></LI> <UL> <LI><EM>From</EM>: Kevin Smith <kevin@ascend.com></LI> </UL> </UL> <!--X-References-End--> <!--X-BotPNI--> <HR> <UL> <LI>Prev by Date: <STRONG><A HREF="msg10299.html">Re: (ASCEND) Ap33 Warnings</A></STRONG> </LI> <LI>Next by Date: <STRONG><A HREF="msg10297.html">Re: (ASCEND) Potential purchaser of Ascend 4060</A></STRONG> </LI> <LI>Prev by thread: <STRONG><A HREF="msg10284.html">Re: (ASCEND) TNT 1.3Ap13</A></STRONG> </LI> <LI>Next by thread: <STRONG><A HREF="msg10309.html">Re: (ASCEND) TNT 1.3Ap13</A></STRONG> </LI> <LI>Index(es): <UL> <LI><A HREF="maillist.html#10298"><STRONG>Main</STRONG></A></LI> <LI><A HREF="thrd214.html#10298"><STRONG>Thread</STRONG></A></LI> </UL> </LI> </UL> <!--X-BotPNI-End--> <!--X-User-Footer--> <!--X-User-Footer-End--> </BODY> </HTML>