Bad idea. There are some significant problems with using MP on a Pipeline box when
connecting to Livingston. I've had problems like connection lockups, connection
drops after exactly 1 minute, and not reconnecting properly after a disconnect.
Setting the Ascend to MPP solves all problems. Ascend basically said to use MPP
if it works. Yes, I know MPP should be the same as MP when connecting to something
that doesn't support the proprietary extentions, like Livingston.
There are also some issues with the compression on Ascend-Livingston connections.
Connections will freeze when the Ascend is set to STAC-9 and certain types of
data are passed - our office staff found a specific web page that will hang the
P50 in our office every time if compression is on. It seems to be worse on
underpowered boxes like the P25. Of course, there are none of these problems
between two Ascend boxes - or two Livingston boxes, presumably.
I havn't had the time to sit down and report the problems properly. Resolving
interoperability issues is usually a serious pain in the ass; it usually ends
up turning into a finger pointing exercise between the two companies, with me
stuck in the middle trying to coordinate things. Extremely time consuming.
--
/// Stefan Hudson <hudson@mbay.net>
__ /// Senior Network Administrator - Monterey Bay Internet
\\\/// http://www.mbay.net/ - Email: info@mbay.net
\XX/ Voice: 408-642-6100 Fax: 408-642-6101 Modem: 408-642-6102
-
To unsubscribe, email 'majordomo@livingston.com' with
'unsubscribe portmaster-users' in the body of the message.