ppp won't re-auto connect

[sbrooks011]

I have a 867VAE router on a customer site and ppp will not re-auto connect, the DSL link light is on, as is the DSL act light, we use the same router and config on over 600 hundred sites for the same customer without any problems.

I have changed the router, filter and filter cable 3 times.

BT have carried out a D side, E side and a lift and shift at the exchange, they have also had a rein engineer in without any success

interface Dialer0
 ip address xx.xxx.xx.xxx xxx.xxx.xxx.xxx
 ip mtu 1452
 ip nat outside
 ip virtual-reassembly in
 encapsulation ppp
 dialer pool 1
 ppp chap hostname 
 ppp chap password 0 
 ppp pap sent-username
 no cdp enable

[Vasilii Mikhailovskii]

Hello.

Is this the full configuration of the interface (as I don't see dialer persistent command)?

Have you tried to debug PPP negotiation?

[sbrooks011]

Hi,

Yes, that is the dialer 0 Config we use on all sites, without any probs. If I added dialer persistent to the dialer, which would I use?

Delay - Specify a delay for nailing up a connection

or use max-attempts - specify the maximum number of retries to nail up a connection

[Vasilii Mikhailovskii]

You may configure "dialer persistent".

Once you see PPP is not coming up - please collect debugs (debug ppp error and debug ppp nego; debug ppp packets could be optional).

[sbrooks011]

So I just enter dialer persistent in to the dialer 0 Config? and collect the debug

[Vasilii Mikhailovskii]

Once you see PPP is not coming up - please collect debugs.

[sbrooks011]

Okay. Thanks

[sbrooks011]

By adding dialer persistent seems to have had an effect. Do I need to remove anything from the dialer Config? or should this be okay

interface Dialer0
 ip address xx.xxx.xx.xxx xxx.xxx.xxx.xxx
 ip mtu 1452
 ip nat outside
 ip virtual-reassembly in
 encapsulation ppp
 dialer pool 1
 dialer idle-timeout 0
 dialer persistent
 ppp chap hostname 
 ppp chap password 0 
 ppp pap sent-username 
 no cdp enable

[sbrooks011]

After one week of working the router is now offline again! Could it be interference from another cause?