Can`t get access over V.110

[frank0815]

Hello,

i have problems with our configuration.

1. the configuration worked

2. view weeks later, the router crash

3. we changed the hardware

4. installed the old config

but we didn`t get an access over V.110

Debug:

Oct 14 13:41:35.075: %LINK-3-UPDOWN: Interface Serial1/0:0, changed state to down

bvrr02#

Oct 14 13:41:42.083: %LINK-3-UPDOWN: Interface Serial1/0:0, changed state to up

Oct 14 13:41:42.083: %ISDN-6-CONNECT: Interface Serial1/0:0 is now connected to xxxxxxxxxx N/A

bvrr02#

Oct 14 13:41:42.083: Se1/0:0 PPP: Using dialer call direction

Oct 14 13:41:42.083: Se1/0:0 PPP: Treating connection as a callin

Oct 14 13:41:42.083: Se1/0:0 PPP: Session handle[6100007F] Session id[36]

bvrr02#

Oct 14 13:41:44.059: Se1/0:0 PPP: Authorization required

bvrr02#

Oct 14 13:42:04.219: Se1/0:0 DDR: disconnecting call

Oct 14 13:42:04.219: %ISDN-6-DISCONNECT: Interface Serial1/0:0 disconnected from xxxxxxxxxx , call lasted 22 seconds

bvrr02#

Oct 14 13:42:04.351: %LINK-3-UPDOWN: Interface Serial1/0:0, changed state to down

bvrr02#

[Richard Burts]

Frank

I have looked at the information in the attachment. I do not yet see what is causing the problem. I see one of the messages in the log is:

Oct 14 13:41:44.059: Se1/0:0 PPP: Authorization required

but I do not see anything in the config that relates to authorization.

There are two things that occur to me that might need to be checked out:

- it may be that the authorization issue is caused by whatever is calling this router. Do you know what that device is and do you have access to its configuration?

- I note that the configuration information that you posted is from show configuration. This command looks to the stored (backup) config in NVRAM and not the active running config. Is it possible that some change was made in the active configuration that we are not seeing?

It might be helpful if you would run debug ppp negotiation and post the output when there is an attempt to call. This might help us understand what is causing the authorization issue.

HTH

Rick

[paul.werner]

I tend to agree with Rick's post. The culprit is likely an external client that is forcing an authentication method that is not configured on the router. This is classic for an MS dialup or VPN config (particularly on govt networks) to force MS CHAP or MS CHAP VII or no authetication at all. From the router perspective, it looks like an unsupportable negotiation in PPP. As Rick said, "debug ppp neg" should yield the likely protocol requested.

Rick, say hi to all the guys at Chesapeake; they are the best. All is well here. Paul

[Georg Pauwen]

Hello,

this is just a guess, but you might want to try and disable isdn v110 padding with the command 'no isdn v110 padding':

interface Serial1/0:15

no ip address

encapsulation ppp

dialer rotary-group 1

dialer-group 5

--> no isdn v110 padding

isdn switch-type primary-net5

isdn incoming-voice data

ppp authentication chap pap ms-chap ms-chap-v2 callin

ppp multilink

and see if that makes a difference...

Regards,

GP