Sounds like you do not have interesting traffic defined. Interesting traffic is to not only used bring up the interface but it is also used to keep the interface up. Interesting traffic is what resets the dialer idle-timeout. Please make sure that you have interesting traffic defined using the dialer-group and dialer-list commands. If you have these difined then while the interface is up you can run the following debug to determine whether interesting traffic is hitting the interface or not.
"debug dialer packet"
Please be careful with that command because it could cause your router to lock up if there is too much traffic going across that interface.
Thanks for your replay. I have discover in the meantime that 12.1 on the 1003 the problem is. The interesting traffic suggestion from you was correct but already in place in my configuration. Unfortunately I have to downgrade the IOS to 12.0 to make it all work again.
The new challenge will than be to make netmeeting work! Anyway thanks again.
[toc:faq]The ProblemOn traditional switches whenever we have a trunk
interface we use the VLAN tag to demultiplex the VLANs. The switch needs
to determine which MAC Address table to look in for a forwarding
decision. To do this we require the switch to do...
[toc:faq]Introduction:Netdr is a tool available on a RSP720, Sup720 or
Sup32 that allows one to capture packets on the RP or SP inband. The
netdr command can be used to capture both Tx and Rx packets in the
software switching path. This is not a substitut...
IntroductionOSPF, being a link-state protocol, allows for every router
in the network to know of every link and OSPF speaker in the entire
network. From this picture each router independently runs the Shortest
Path First (SPF) algorithm to determine the b...