Re: (ASCEND) MAX 4000 Callback problem

[Kevin Smith <kevin@ascend.com>]

>From the TAC escalation group:

>Hi Kevin,
>
>I think you're probably right in that this is caused by a Network delay in
>propagating the disconnect back to the MAX.
>
>The idea of Ascend-Expect-Callback is to prevent the MAX from making
>additonal
>outgoing calls to a remote side while it's waiting for the callback from
>the remote router.
>But, if we don't see a disconnect coming from the other side, the original
>outgoing call
>will still be active, so we won't allow the incoming call to establish a
>session.
>
>>And does that feature *rely* on authentication to complete before the MAX
>>will drop the call ??
>
>As far as I can see, the initial call has to be dropped by the Pipeline not
> the MAX.
>Putting in Expect-Callback doesn't change that.  The call from the MAX has
>to be
>authenticated on the pipeline before the parameter settings in the
>connection profile
>take affect.  So on the Pipeline, I think you'll see  Lan Session Up ,  Lan
> Session Down,
>Callback Pending, Outgoing Call, Lan Session Up.  The MAX will only drop
>the call
>after the Disconnect has been propagated from the Network to the MAX.


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>

---

• Prev by Date: Re: (ASCEND) 5.0Ap36, is this normal?
• Next by Date: Re: (ASCEND) AMI to B8ZS conversion?
• Prev by thread: Re: (ASCEND) MAX 4000 Callback problem
• Next by thread: (ASCEND) Max 1600 - unenhanced HDLC channel maximum?
• Index(es):
  • Main
  • Thread