Ascend Archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: (ASCEND) Analog Multilink PPP



Matt,

As Jeff pointed out, this thread is going to far off topic. The important
aspect this that async MP is support now in the "i" branch and will be
released in production code sometime soon.

I'll be glad to move this thread offline if that's more appropriate.

Charlie Clemmer

At 11:47 AM 5/23/97 -0700, Matt Holdrege wrote...
>If you read my email below, it says that we may not have checked the ED on
>analog calls. That can be called a bug if you are a purist, or just an
>unsupported feature of MP. But as I said below, we do support it in 5.0Aix.
>
>Code doesn't just fall out of the sky. Someone has to write the lines of
>code necessary to check incoming calls for ED and an MP header. Since
>Ascend code is so feature rich, we do all sorts of checking on inbound
>calls. We do far more than standards indicate and far more than other
>vendors support. This is because we are driven by our customers network
>design ideas. Our customers in the past have never asked us to support
>analog MP. Now they are asking for it and now we have added the code to
>check for MP and ED on types other than just ISDN data calls.
>
>
>At 01:35 PM 5/23/97 -0500, Charlie Clemmer wrote:
>>
>>Matt,
>>
>>What you describe is what I understood MP to be. The question that comes up
>>because of this then, is why would Livingston and maybe Ascend not support
>>MP over all types of links?
>>
>>I keep seeing mixed responses as to whether the Ascend box does support MP
>>over any kind of link, while I saw a response from a Livingston guy who
>>indicated that their box only supports MP on ISDN calls.
>>
>>Knowing that MP should not be related to the physical call type, why would
>>this limitation exist?
>>
>>Can we get a definitive answer from Ascend as to whether or not the Ascend
>>boxes share this limitation? Again, I would expect that it is supported,
>>for the reasons you mentioned.
>>
>>Charlie Clemmer
>>
>>At 08:41 AM 5/23/97 -0700, Matt Holdrege wrote:
>>>Folks, MP operates at a layer above the physical connection or media. You
>>>can combine any types of calls in any increment. I've seen NT call the Max
>>>with one analog call bundled with one ISDN call. Or two analog calls
>>>together. I've seen the Max call a Bay router with 23 channels of MP.
>>>
>>>All MP does is take (in one case) the endpoint discriminator and compare it
>>>with any other call it has, be it analog or MP or whatever. If there is a
>>>match, it bundles the two calls together. I haven't tested it on the Max
>>>5.0ap branch, but by the reports here I might assume that the Max code
>>>didn't check ED on analog calls. But the reports say that it does in the i
>>>branch.
>>
>>
>Matt Holdrege  -  http://www.ascend.com  -  matt@ascend.com
>++ Ascend Users Mailing List ++
>To unsubscribe:	send unsubscribe to ascend-users-request@bungi.com
>To get FAQ'd:	<http://www.shore.net/~dreaming/ascend-faq>
>or		<ftp://ftp.shore.net/members/dreaming/ascend-faq.txt>
>
++ Ascend Users Mailing List ++
To unsubscribe:	send unsubscribe to ascend-users-request@bungi.com
To get FAQ'd:	<http://www.shore.net/~dreaming/ascend-faq>
or		<ftp://ftp.shore.net/members/dreaming/ascend-faq.txt>