ISDN call keep activating

[nawas]

I have set up a DDR which should work only when it sees interesting traffice but looks like my bri interface sending packet to the remote bri which is activating ISDN call, I have pretty much blocked everything in my access-list but it still activate calls every 5 min for 1 min or so. Can someone tell me what I'm missing?

Thanks.

May 4 10:18:57.564: BR0/0 DDR: ip

(s=10.27.13.173, d=10.27.13.174), 56 bytes, outgoing interesting (list 199

Here is my access-list

access-list 199 deny udp any any eq tacacs

access-list 199 deny ip any host 224.0.0.10

access-list 199 deny eigrp any any

access-list 199 deny igrp any any

access-list 199 deny ospf any any

access-list 199 deny ip 224.0.0.0 0.0.0.255 any

access-list 199 deny ip any 224.0.0.0 0.0.0.255

access-list 199 deny ip any host 255.255.255.255

access-list 199 deny udp any any range netbios-ns netbios-dgm

access-list 199 deny udp any any eq ntp

access-list 199 deny udp any any eq rip

access-list 199 deny udp any any eq snmp

access-list 199 deny udp any any eq snmptrap

access-list 199 deny udp any any eq syslog

access-list 199 deny tcp any any eq tacacs

access-list 199 deny udp any any eq time

access-list 199 permit ip any any

dialer-list 1 protocol ip list 199

[b-ulrich]

Hi, is the snipit above from 'debug dialer'? Debug dialer is nice to trouble shoot this. Also 'sh dialer' will let you know why it triggered a dial and what IP address. You may need to deny 10.27.13.174 if this is something causing it to trigger a call.

[Michael Stuckey]

Get into the router, turn on term mon, run "debug dialer packet". This will give you all the interesting traffic. This will show IP only.

I would like to see the configuration of both routers.

To take this one step further you can run "debug ip packet 199 detail". This will give you more information.

Worst case scenario you may have to change the

last line

access-list 199 permit ip any any

to

access-list 199 permit tcp any any

access-list 199 permit udp any any

then run the last debug again.

Remember when done to do an "un all" to stop debug.

Rate if this helps.

Mike

[Fernando_Meza]

Adding to what has been said .. make sure you are not using your BRI interface on any dynamic routing protocol .. as this could also be trigering the calls as the routing protocol updates its table and sends helo messages

I hope it helps !!!

[cisand2002]

Hi

can you add this to your router config:

no ip domain lookup

if it does not help. Do a debug ip packet details on tcp/udp between source and destination.

Please let me know then

Regards,

cisand

[manish-young]

y dont you use your access list other way around,

Permit intersting traffic and dont use permit any at the end of acess list.

HTH

Manish

[cisand2002]

Hi Manish,

The acl seems to be blocking non interesting traffic such eigrp/ospf, netbios..

Can you explain?

Can Nawas confirm if he has answer and explain? thx

regards,

cisand