You are using this as a server and authenticate the remotes.
So please check the remote site (the caller) and do debugging on that end.
Check the timers too on the remote as Matt mentioned
> Date: Fri, 11 Dec 2009 09:33:04 +1100
> Subject: Re: [OSL | CCIE_RS] ISDN calls
> From: [email protected]
> To: [email protected]
> CC: [email protected]; [email protected]
>
> Sorry,
>
> Forgot:
>
> debug ppp neg
> debug ppp authen
>
> Cheers,
> Matt
>
> CCIE #22386
> CCSI #31207
>
> 2009/12/11 Matt Hill <[email protected]>:
> > He does... dialer-group 1...
> >
> > Although what is in dialer-list 1 (ie what does dialer-group 1 point
> > to)? If it is "dialer-list 1 protocol ip permit" then that should
> > work. Also, the dialer-list or the idle timeout at the other end may
> > be dropping it.
> >
> > Can we see:
> >
> > debug dialer events
> > debug isdn q931
> > show isdn status (are you getting L2 MULTIPLE_FRAME_ESTABLISHED?)
> >
> > Cheers,
> > Matt
> >
> > CCIE #22386
> > CCSI #31207
> >
> > 2009/12/11 pra pa <[email protected]>:
> >> Debur eigrp pacekts to find if that is doing it.
> >>
> >> Do you have access-list to define itneresting traffic?
> >>
> >>
> >>
> >> ________________________________
> >> Date: Thu, 10 Dec 2009 16:17:04 +0100
> >> From: [email protected]
> >> To: [email protected]
> >> Subject: [OSL | CCIE_RS] ISDN calls
> >>
> >> Hi
> >> Wonduring why this is happing have done same diging couldn't find anything
> >> any help or points .Thx
> >>
> >> Service ISDN Nas BU
> >>
> >> This CE router is having a large number of ISDN calls when in fact the
> >> site NOT down !!!
> >> ISDN is automatically weirly triggered somehow calls
> >>
> >> Thsis same logs and configs
> >>
> >> Dec 10 01:44:19: %LINK-3-UPDOWN: Interface BRI1/0:2, changed state to up
> >> Dec 10 01:44:19: %DIALER-6-BIND: Interface BR1/0:2 bound to profile Di1
> >> Dec 10 01:44:19: %ISDN-6-CONNECT: Interface BRI1/0:1 is now connected to
> >> 020708xxxx sita- nas
> >> Dec 10 01:44:19: %ISDN-6-CONNECT: Interface BRI1/0:2 is now connected
> >> to020708xxxx N/A
> >> Dec 10 01:44:20: %LINEPROTO-5-UPDOWN: Line protocol on Interface BRI1/0:2,
> >> changed state t o up
> >> Dec 10 01:44:21: %ISDN-6-CONNECT: Interface BRI1/1:2 is now connected
> >> to020708xxxx sita- nas
> >> Dec 10 01:44:25: %ISDN-6-CONNECT: Interface BRI1/0:2 is now connected to
> >> 020708xxxx sita- nas
> >> Dec 10 01:47:19: %ISDN-6-DISCONNECT: Interface BRI1/3:1 disconnected from
> >> 020708xxxx sit a-nas, call lasted 195 seconds
> >> Dec 10 01:47:19: %ISDN-6-DISCONNECT: Interface BRI1/2:1 disconnected from
> >> 0020708xxxx sit a-nas, call lasted 190 seconds
> >> Dec 10 01:47:19: %ISDN-6-DISCONNECT: Interface BRI1/3:2 disconnected from
> >> 020708xxxx sit a-nas, call lasted 192 seconds
> >> Dec 10 01:47:19: %ISDN-6-DISCONNECT: Interface BRI1/2:2 disconnected from
> >> 020708xxxx sit a-nas, call lasted 188 seconds
> >> Dec 10 01:47:19: %LINK-3-UPDOWN: Interface BRI1/3:1, changed state to down
> >> Dec 10 01:47:19: %DIALER-6-UNBIND: Interface BR1/3:1 unbound from profile
> >> Di1
> >> Dec 10 01:47:19: %LINK-3-UPDOWN: Interface BRI1/1:1, changed state to down
> >> Dec 10 01:47:19: %DIALER-6-UNBIND: Interface BR1/1:1 unbound from profile
> >> Di1
> >> Dec 10 01:47:19: %LINK-3-UPDOWN: Interface BRI1/2:1, changed state to down
> >> Dec 10 01:47:19: %DIALER-6-UNBIND: Interface BR1/2:1 unbound from profile
> >> Di1
> >> Dec 10 01:47:19: %LINK-3-UPDOWN: Interface BRI1/3:2, changed state to down
> >> Dec 10 01:47:19: %DIALER-6-UNBIND: Interface BR1/3:2 unbound from profile
> >> Di1
> >> Dec 10 01:47:19: %LINK-3-UPDOWN: Interface BRI1/0:2, changed state to down
> >> Dec 10 01:47:19: %DIALER-6-UNBIND: Interface BR1/0:2 unbound from profile
> >> Di1
> >> Dec 10 01:47:19: %LINK-3-UPDOWN: Interface BRI1/1:2, changed state to down
> >> Dec 10 01:47:19: %DIALER-6-UNBIND: Interface BR1/1:2 unbound from profile
> >> Di1
> >> Dec 10 01:47:19: %LINK-3-UPDOWN: Interface BRI1/2:2, changed state to down
> >> Dec 10 01:47:19: %DIALER-6-UNBIND: Interface BR1/2:2 unbound from profile
> >> Di1
> >> Dec 10 01:47:19: %LINK-3-UPDOWN: Interface BRI1/0:1, changed state to down
> >> Dec 10 01:47:19: %DIALER-6-UNBIND: Interface BR1/0:1 unbound from profile
> >> Di1
> >> Dec 10 01:47:20: %LINEPROTO-5-UPDOWN: Line protocol on Interface BRI1/3:1,
> >> changed state t o down
> >> Dec 10 01:47:20: %LINEPROTO-5-UPDOWN: Line protocol on Interface BRI1/3:2,
> >> changed state t o down
> >> Dec 10 01:47:20: %LINEPROTO-5-UPDOWN: Line protocol on Interface BRI1/2:1,
> >> changed state t o down
> >> Dec 10 01:47:20: %LINEPROTO-5-UPDOWN: Line protocol on Interface BRI1/2:2,
> >> changed state t o down
> >> Dec 10 01:47:20: %LINEPROTO-5-UPDOWN: Line protocol on Interface BRI1/1:1,
> >> changed state t o down
> >> Dec 10 01:47:20: %LINEPROTO-5-UPDOWN: Line protocol on Interface BRI1/1:2,
> >> changed state t o down
> >> Dec 10 01:47:20: %LINEPROTO-5-UPDOWN: Line protocol on Interface BRI1/0:1,
> >> changed state t o down
> >> Dec 10 01:47:20: %LINEPROTO-5-UPDOWN: Line protocol on Interface BRI1/0:2,
> >> changed state t o down
> >> Dec 10 01:52:27: %SEC-6-IPACCESSLOGP: list 101 denied udp 172.21.3.30(137)
> >> -> 192.168.1.3( 137), 3 packets
> >> Dec 10 02:04:27: %SEC-6-IPACCESSLOGP: list 101 denied udp 172.21.3.30(137)
> >> -> 192.168.1.3( 137), 3 packets
> >> Dec 10 02:16:27: %SEC-6-IPACCESSLOGP: list 101 denied udp 172.21.3.30(137)
> >> -> 192.168.1.3( 137), 3 packets
> >> Dec 10 02:29:27: %SEC-6-IPACCESSLOGP: list 101 denied udp 172.21.3.30(137)
> >> -> 192.168.1.3( 137), 3 packets
> >> Dec 10 02:41:27: %SEC-6-IPACCESSLOGP: list 101 denied udp 172.21.3.30(137)
> >> -> 192.168.1.3( 137), 3 packets
> >> Dec 10 02:53:27: %SEC-6-IPACCESSLOGP: list 101 denied udp 172.21.3.30(137)
> >> -> 192.168.1.3( 137), 3 packets
> >> Dec 10 03:05:27: %SEC-6-IPACCESSLOGP: list 101 denied udp 172.21.3.30(137)
> >> -> 192.168.1.3( 137), 3 packets
> >> Dec 10 03:18:27: %SEC-6-IPACCESSLOGP: list 101 denied udp 172.21.3.30(137)
> >> -> 192.168.1.3( 137), 3 packets
> >> Dec 10 08:32:27: %SEC-6-IPACCESSLOGP: list 101 denied udp 172.21.3.30(137)
> >> -> 192.168.1.3( 137), 3 packets
> >> Dec 10 08:44:27: %SEC-6-IPACCESSLOGP: list 101 denied udp 172.21.3.30(137)
> >> -> 192.168.1.3( 137), 3 packets
> >> Dec 10 08:57:27: %SEC-6-IPACCESSLOGP: list 101 denied udp 172.21.3.30(137)
> >> -> 192.168.1.3( 137), 3 packets
> >> Dec 10 09:09:27: %SEC-6-IPACCESSLOGP: list 101 denied udp 172.21.3.30(137)
> >> -> 192.168.1.3( 137), 3 packets
> >> Dec 10 09:21:27: %SEC-6-IPACCESSLOGP: list 101 denied udp 172.21.3.30(137)
> >> -> 192.168.1.3( 137), 3 packets
> >> Dec 10 09:33:27: %SEC-6-IPACCESSLOGP: list 101 denied udp 172.21.3.30(137)
> >> -> 192.168.1.3(
> >>
> >> pbbs000#sh dialer
> >>
> >> Dial String Successes Failures Last DNIS Last status
> >> 02070xxxx 10217 912 12:47:05 successful Default
> >>
> >>
> >> interface Dialer1
> >> description NAS-BACKUP: CAS PZHE001 PZHE002
> >> ip address 192.168.1.13 255.255.255.0
> >> ip access-group 52 out
> >> encapsulation ppp
> >> load-interval 30
> >> dialer pool 1
> >> dialer idle-timeout 180
> >> dialer enable-timeout 10
> >> dialer string 020708xxxx
> >> dialer string 08450xxxxx
> >> dialer load-threshold 2 either
> >> dialer-group 1
> >> no cdp enable
> >> ppp authentication chap callin
> >> ppp chap hostname pbbs000
> >> ppp chap password 7 xxxxxxxxx
> >> ppp pap refuse
> >> ppp multilink
> >> ppp multilink links maximum 8
> >> ppp multilink links minimum 8
> >> !
> >> router eigrp 1949
> >> passive-interface default
> >> no passive-interface Dialer1
> >> network 172.21.0.0
> >> network 192.168.1.0
> >> distribute-list 99 out Dialer1
> >> distribute-list NONE in Dialer1
> >> no auto-summary
> >> no eigrp log-neighbor-changes
> >>
> >> Cheers
> >>
> >> ________________________________
> >> Windows 7: Unclutter your desktop. Learn more.
> >> _______________________________________________
> >> For more information regarding industry leading CCIE Lab training, please
> >> visit www.ipexpert.com
> >>
> >>
> >
_________________________________________________________________
Hotmail: Free, trusted and rich email service.
http://clk.atdmt.com/GBL/go/171222984/direct/01/_______________________________________________
For more information regarding industry leading CCIE Lab training, please visit
www.ipexpert.com
