Re: (ASCEND) no connect with older modems after upgrade

[Joseph@austintx.net (Joseph Bridgewater)]

At 01:06 PM 8/25/97 -0700, Kevin Smith wrote:
>At 04:58 PM 8/25/97 MEZ-1MESZ, Bernd Wagener wrote:
[snip]
>>an was surprised. If th Max goes off hook, then he sends a short 
>>beep an begins after a silent period of one second ore more to send 
>>his normal  signals. The short beep at the beginning seems to disturb 
>>the modems an no connection can be established.
[snip]
>This V.8bis tone was added to the K56Flex negotiations to interoperate with
>Lucent modems. When the K56Flex world was Rockwell/Rockwell it was not
>needed, but would not work with non_Rockwell K56 modems....

Couldn't anybody have convinced Lucent to not require something that would
completely wack-out a substantial number of modems already in use in the
field (and are GOING to be used for some time)?  

I guess that's rhetorical... but sheesh!  Intentionally introducing variant
behavior on an installed user base... not nice!  Leave it to AT&T spawn.


Joseph
++ Ascend Users Mailing List ++
To unsubscribe:	send unsubscribe to ascend-users-request@bungi.com
To get FAQ'd:	<http://www.nealis.net/ascend/faq>

---

• Prev by Date: (ASCEND) R5.0Ap20 : User "Modem" with Framed-Address = "0.0.0.0"
• Next by Date: Re: (ASCEND) Disconnect-Cause 185
• Prev by thread: (ASCEND) Lots of type 11 disconnect codes
• Next by thread: (ASCEND) no connect with older modems after upgrade
• Index(es):
  • Main
  • Thread