From: balaji.balakrishnan (balaji.balakrishnan@swift.com)
Date: Wed Feb 19 2003 - 11:34:28 GMT-3
Hi Aaron,
Thanks for your reply. Few more clarifications,
> Answer: The host will drop call if no interesting traffic from remote,
Do dilaer-list configured on the NAS router will monitor the interesting traffic coming across ISDN link ( inbound) from remote or
traffic going outbound to remote ???
> Why would the PC continue to try and initiate a call?
I think we found the solution.
That is the application behavior. The Server application ( behind the NAS) will try to send keepalives and expecting acknowledge
from the remote client every 2 min and that may keep the line up always. However, we can configure that traffic as non-interesting
in the host. Once the host drop the line, these keepalives will not reach the client and the client don't need to send ack and
there by keep the link down.
Rgds,
Bala.
Aaron Woody wrote:
> Bala,
>
> 1. I understand that if you configure idle-timeout and dialer-list without
> dialer string at host site, we can control non-interesting
> traffic from keeping the line up. But, I wonder what would be the
> configuration at the client site which initiating the call.
>
> Answer: Same config but with Dial string
>
> 2. If so, say for example, NAS router kicks the idle time-out and client
> accidentally again triggers the call. What the NAS router will do ? Does it
> again wait till the idle time-out to drop the line? Does there any way to
> better control from the NAS router?
>
> Answer: The host will drop call if no interesting traffic from remote,
> however if remote sees interesting traffic link will stay up regardless of
> what hosts thinks. If you don't set interesting traffic at host it will drop
> call at end of dialer idle-timeout regardless of what remote is sending.
>
> I recommend setting interesting traffic at host too, this way call is not
> ended prematurely because of timeout.
>
> 3. Also, the client side could be a simple PC also with ISDN TA to initiate
> the call. In such case, I can not define anything like dialer-list and all
> the traffic will try to initiate the call. So even if NAS router kicks the
> idle- timeout, the client ( PC ) will again start initiating the call. Do
> we have any solution on this case?
>
> Why would the PC continue to try and initiate a call?
>
> Aaron
>
> -----Original Message-----
> From: balaji.balakrishnan [mailto:balaji.balakrishnan@swift.com]
> Sent: Tuesday, February 18, 2003 10:22 AM
> To: awoody@columbus.rr.com
> Cc: ccielab@groupstudy.com; ccie8776@rochester.rr.com;
> tschaffran@cconlinelabs.com; wkchan01@mingpao.com;
> ychen@houston.sns.slb.com; peter@cyscoexpert.com
> Subject: Re: Dialer idel timeout in NAS router
>
> Hi Aaron,
>
> Thanks for your reply.
> I understand that if you configure idle-timout and dialer-list without
> dialer string at host site, we can control non-interesting
> traffic from keeping the line up. But, I wonder what would be the
> configuration at the client site which initiating the call. Don't
> we still need to configure the dialer-list to define the interesting traffic
> which can trigger the call. If so, say for example, NAS
> router kicks the idle time-out and client accidentally again triggers the
> call. What the NAS router will do ? Does it again wait
> till the idle time-out to drop the line? Does there any way to better
> control from the NAS router ?
>
> Also, the client side could be a simple PC also with ISDN TA to initiate the
> call. In such case, I can not define anything like
> dialer-list and all the traffic will try to initiate the call. So even if
> NAS router kicks the idle- timout, the client ( PC ) will
> again start initiating the call. Do we have any solution on this case?
>
> Thanks,
> Rgds,
> Bala.
>
> Aaron Woody wrote:
>
> > You can setup dialer-list to define interesting traffic with dialer-group
> at
> > host site and set dialer idle-timeout to the value to want. Since you
> don't
> > have any dial strings setup at host this setup will not initiate a call
> from
> > host, however, will allow host to hang-up when no interesting traffic is
> > coming across ISDN link.
> >
> > Aaron
> >
> > -----Original Message-----
> > From: nobody@groupstudy.com [mailto:nobody@groupstudy.com]On Behalf Of
> > balaji.balakrishnan
> > Sent: Friday, February 14, 2003 10:07 AM
> > To: ccielab@groupstudy.com
> > Cc: ccie8776@rochester.rr.com; tschaffran@cconlinelabs.com;
> > wkchan01@mingpao.com; ychen@houston.sns.slb.com; peter@cyscoexpert.com
> > Subject: Dialer idel timeout in NAS router
> >
> > Hi Group,
> >
> > I have a specific configuration requirement . The setup is like many baby
> > ISDN routers ( Cisco 800/1600 with BRI) calling NAS
> > router ( 3600/AS5200 with PRI). Call will always initiated from baby ISDN
> > routers. Usually we setup dialer list and idle time in the
> > baby router to drop the line when there is no interesting traffic.
> > But, I need to configure NAS routers to do that function. I like to
> > configure in such a way that the baby router will initiate the
> > calls and NAS router should monitor the interesting traffic and should
> drop
> > the line after the idle time-out. Note that the all the
> > baby routers will have same kind of traffic and dialer-list configuration
> > in NAS router should be generic to be applied for all
> > incoming ISDN calls. Does anyone has any idea ???
> >
> > Rgds,
> > Bala.
This archive was generated by hypermail 2.1.4 : Sat Mar 01 2003 - 11:06:31 GMT-3