Appreciate if you could post the config for further help

Ahmad

Assuming that you have not disabled the inactivity timer then if the ISDN is still staying connected then there is still some "interesting" traffic. You need to identify the interesting traffic and do something about it.

If you have problems figuring out what the interesting traffic is then running debug dialer may be helpful.

As the previous posteer points out it might be helpful if you post the configs.

HTH

Rick

hi Rburts,

In a similar case of mine, everything works fine as per the access list configured, whenever a traffic is initiated from the LAN.

But when i do a tracert from the router itself, when primary link is active. I noticed that isdn is also fired out. A debug dialer showed the cause S=primary link ip address and D= 255.255.255.255

Is this normal. As in practice nobody will be doing the tracert from the router so often.

Any suggestion?

Thks.

I would think that it is unusual for a tracert to send out broadcast packets (which seems to be what your show dialer is indicating). Perhaps if you post the output of the tracert and post the output of show ip route from the router we might be able to figure what is going on.

HTH

Rick

dear all,

i don't think it is relate to the broadcast, since i do additiona testing which is as follow:

i make the dial only from the head office: isdn stilla active :)

i make the dial from the branch only: the isdn still active :)

i do no cdp enable on both the dialer and bri interface : isdn still active :)

so what do you think is the problem.

if you think it is broadcast, so why the head office dial the branch.

really amazing situation

any new idea or simillar case

B.R

Ahmed

Hi ,

please paste the config of the router..

Thanks,

satish