Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

Register Log in
  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

ISDN dial-up Not working correctly

Status
Not open for further replies.
nichols

nichols

Technical User
May 24, 2001
92
GB




Hi Nichols here again, struggling again with ISDN dail up as it is the bain of my life.

I am configuring a cisco 4000 series router to use ISDN dial up to connect to a cisco 800 series router on another site.

I have configured the bri1 port as below:

interface BRI1
description isdn dial up connection to Leeds
ip address 192.110.96.1 255.255.255.0
encapsulation ppp
bandwidth 64
dialer map ip 192.110.96.2 name leeds xxxxxxxxxxx
dialer-group 1
isdn switch-type basic-net3
ppp authentication chap pap
ppp chap hostname hayroute3
ppp chap password 7 1101181C051D1E180179
ppp multilink
!

I have configured a dialer-list command as below:

dialer-list 1 protocol ip permit

When I try to ping leeds i don't get a connection. I have debuged dialer events and get the following error message:

Password:
hayroute3>en
Password:
hayroute3#debug dialer events
Dial on demand events debugging is on
hayroute3#terminal monitor
hayroute3#ping 192.110.26.1

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.110.26.1, timeout is 2 seconds:

5d05h: BRI1: Dialing cause ip (s=192.110.96.1, d=192.110.26.1)
5d05h: BRI1: No dialer string, dialing cannot occur.
5d05h: BRI1: Dialing cause ip (s=192.110.96.1, d=192.110.26.1)
5d05h: BRI1: No dialer string, dialing cannot occur.
5d05h: BRI1: Dialing cause ip (s=192.110.96.1, d=192.110.26.1)
5d05h: BRI1: No dialer string, dialing cannot occur.
5d05h: BRI1: Dialing cause ip (s=192.110.96.1, d=192.110.26.1)
5d05h: BRI1: No dialer string, dialing cannot occur.
5d05h: BRI1: Dialing cause ip (s=192.110.96.1, d=192.110.26.1)
5d05h: BRI1: No dialer string, dialing cannot occur.
Success rate is 0 percent (0/5)
hayroute3#


because of this I changed the dialer map command to a dialer string command as shown below:

interface BRI1
description isdn dial up connection to Leeds
ip address 192.110.96.1 255.255.255.0
encapsulation ppp
bandwidth 64
dialer string xxxxxxxxxxx
dialer-group 1
isdn switch-type basic-net3
ppp authentication chap pap
ppp chap hostname hayroute3
ppp chap password 7 1101181C051D1E180179
ppp multilink

This time the line works and repeatedly goes up and down and gives the following error message:

5d03h: BRI1:1: disconnecting call
5d03h: BRI1: Dialing cause ip (s=192.110.96.1, d=224.0.0.10)
5d03h: BRI1: Attempting to dial xxxxxxxxxxx
5d03h: %LINK-3-UPDOWN: Interface BRI1:1, changed state to up
5d03h: %LINK-3-UPDOWN: Interface BRI1:1, changed state to down
5d03h: BR1:1 VP: Cleaning already proceeding
5d03h: BRI1:1: disconnecting call
hayroute3#termina
5d03h: BRI1: Dialing cause ip (s=192.110.96.1, d=224.0.0.10)
5d03h: BRI1: Attempting to dial xxxxxxxxxxx
5d03h: %LINK-3-UPDOWN: Interface BRI1:1, changed state to up
5d03h: %LINK-3-UPDOWN: Interface BRI1:1, changed state to downl no

even when this happens I still cannot get a ping from the remote server.

Please help as I am banging my head against a brick wall with this one!!!

Cheers
Nichols
 
Sort by date Sort by votes
You need to run some debugs to get more details.

Do a show isdn status and see what it says

Do a show dialer and see what is logged

Run a debug on ISDN events
q931
ppp negotiation

The clues will be there.. we just have to ferret them out.

Here is a link that might prove to be useful


About half way down is a link for troubleshooting ISDN from Cisco.

MikeS
Find me at
"Diplomacy; the art of saying 'nice doggie' till you can find a rock" Wynn Catlin
 
Upvote 0 Downvote
cheers

I have done the debugs suggested on the packet attack web site the only one that seems to give any indication of a problem is debug dialer events which gives the following problems.Dial on demand events debugging is on
hayroute3#ping 192.110.26.1

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.110.26.1, timeout is 2 seconds:

5d22h: BRI1: Dialing cause ip (s=192.110.96.1, d=192.110.26.1)
5d22h: BRI1: No dialer string, dialing cannot occur.
5d22h: BRI1: Dialing cause ip (s=192.110.96.1, d=192.110.26.1)
5d22h: BRI1: No dialer string, dialing cannot occur.
5d22h: BRI1: Dialing cause ip (s=192.110.96.1, d=192.110.26.1)
5d22h: BRI1: No dialer string, dialing cannot occur.
5d22h: BRI1: Dialing cause ip (s=192.110.96.1, d=192.110.26.1)
5d22h: BRI1: No dialer string, dialing cannot occur.
5d22h: BRI1: Dialing cause ip (s=192.110.96.1, d=192.110.26.1)
5d22h: BRI1: No dialer string, dialing cannot occur.
Success rate is 0 percent (0/5)
hayroute3#

I have checked the dialer map, dialer group and dialer list statements and they all seem to be correct. There are also no access lists on this router so this cannot be stopping the ip packets bringing up the line.

The only thing that will work at the moment is if I swap the dialer map statement for a dialer string statement but that then leads to the line repeatedly going up and down. Does anyone know if I have missed a command or anything else that is required to bring an ISDN line up.

I have tried the debug ISDN q921 command and it gives the following output:

hayroute3#terminal monitor
hayroute3#
5d23h: ISDN BR1: RX <- RRp sapi = 0 tei = 114 nr = 125
5d23h: ISDN BR1: TX -> RRf sapi = 0 tei = 114 nr = 39
5d23h: ISDN BR1: RX <- RRp sapi = 0 tei = 114 nr = 125
5d23h: ISDN BR1: TX -> RRf sapi = 0 tei = 114 nr = 39
5d23h: ISDN BR1: RX <- RRp sapi = 0 tei = 114 nr = 125
5d23h: ISDN BR1: TX -> RRf sapi = 0 tei = 114 nr = 39
5d23h: ISDN BR1: RX <- RRp sapi = 0 tei = 114 nr = 125
5d23h: ISDN BR1: TX -> RRf sapi = 0 tei = 114 nr = 39
hayroute3#
hayroute3#
5d23h: ISDN BR1: RX <- RRp sapi = 0 tei = 114 nr = 125
5d23h: ISDN BR1: TX -> RRf sapi = 0 tei = 114 nr = 39
hayroute3#
hayroute3#terminal no monitor

However I do not understand this output


if any one can shed any light it would be much appreciated.

Nichols

 
Upvote 0 Downvote
Here is a sample ISDN dial out that works. Notice that the interface has a SPID number. You need the SPID( really a phone number plus a command) for the ISDN circuit to connect to the ISDN switch. I do not see any SPID in your configuration.

MikeS



!
!
version 12.0
service timestamps debug uptime
service timestamps log uptime
service password-encryption
!
hostname router-a
!
!
username router-b password 7 02050D480809; password is cisco
ip subnet-zero
isdn switch-type basic-dms100
!
!
!
interface Serial0
no ip address
no ip directed-broadcast
no ip mroute-cache
shutdown
no fair-queue
!
interface Serial1
no ip address
no ip directed-broadcast
shutdown
!
interface TokenRing0
no ip address
no ip directed-broadcast
shutdown

!
interface BRI0
ip address 192.168.1.1 255.255.255.0
no ip directed-broadcast
encapsulation ppp
no ip mroute-cache
dialer idle-timeout 2147483
dialer map ip 192.168.1.2 name router-b 666666
dialer load-threshold 5 either
dialer-group 1
isdn switch-type basic-dms100
********isdn spid1 5555550101*******
compress stac
ppp authentication chap
!
no ip classless
ip route 0.0.0.0 0.0.0.0 BRI0
!
dialer-list 1 protocol ip permit
!
line con 0
transport input none
line aux 0
line vty 0 4
login
!
end
Find me at
&quot;Diplomacy; the art of saying 'nice doggie' till you can find a rock&quot; Wynn Catlin
 
Upvote 0 Downvote
Hi,

Just a couple of things I've noticed from reading through your config and subsequent debugs.

Your dialer map is pointing to an address of 192.110.96.2 and yet you're pinging 192.110.26.1 - is .1 the router at the remote end and the dialer map pointing to another host on that subnet ?

When you changed it to a dialer string the line is sending out connections to a multicast address (224) which I certainly wouldn't expect to happen....

How are you actually routing packets to this remote site ? Static ? Snapshot routing ? Does the router know how to actually send packets to the remote site or is it using a 0.0.0.0 last resort ?

I'd recommend a debug ip packet, then a ping and see if the packets are not getting encapsulated or are being determind as unroutable....it will give you some useful info.

SPIDs don't need to be declared in this country, you don't need to provide a SPID on a net-3 circuit.

Not a huge amount of insight there but I hope it helps some !
 
Upvote 0 Downvote
Which country? I was not aware that Net3 did not require a SPID... learn something new each day :)

MikeS Find me at
&quot;Diplomacy; the art of saying 'nice doggie' till you can find a rock&quot; Wynn Catlin
 
Upvote 0 Downvote
Net3 is the UK, we don't get the same choice of carriers as everywhere else in the world but at least we can forget about the SPIDs

Can't be bad ;-)

 
Upvote 0 Downvote
Hey... SPIDs are your friend ;-) poor little SPID.. nobody loves him/her

Here across the pond, you get to be good friends with Mr. SPID.. and the telco who likes to give you the incorrect SPID for the setup.. grrr..

MikeS Find me at
&quot;Diplomacy; the art of saying 'nice doggie' till you can find a rock&quot; Wynn Catlin
 
Upvote 0 Downvote
I have debugged ip packets and got the output below:

6d21h: IP: s=192.110.1.2 (FastEthernet0), d=224.0.0.10, len 60, rcvd 2
6d21h: IP: s=192.110.1.140 (FastEthernet0), d=192.110.1.255 (FastEthernet0), len
78, rcvd 3
6d21h: IP: s=169.254.75.109 (FastEthernet0), d=255.255.255.255, len 229, rcvd 2
6d21h: IP: s=192.110.96.1 (local), d=224.0.0.10 (BRI1), len 60, sending broad/mu
lticast
6d21h: IP: s=192.110.96.1 (local), d=224.0.0.10 (BRI1), len 60, encapsulation fa
iled
6d21h: IP: s=192.110.1.140 (FastEthernet0), d=192.110.1.255 (FastEthernet0), len
78, rcvd 3
6d21h: IP: s=192.110.1.1 (FastEthernet0), d=224.0.0.10, len 60, rcvd 2
6d21h: IP: s=192.110.1.25 (FastEthernet0), d=192.110.1.255 (FastEthernet0), len
64, rcvd 3
6d21h: IP: s=192.110.1.222 (FastEthernet0), d=224.0.0.10, len 60, rcvd 2
6d21h: IP: s=192.110.1.4 (FastEthernet0), d=224.0.0.10, len 60, rcvd 2
6d21h: IP: s=192.110.1.3 (local), d=224.0.0.10 (FastEthernet0), len 60, sending
broad/multicast
6d21h: IP: s=192.110.1.2 (FastEthernet0), d=224.0.0.10, len 60, rcvd 2
6d21h: IP: s=192.110.96.1 (local), d=224.0.0.10 (BRI1), len 60, sending broad/mu
lticast
6d21h: IP: s=192.110.96.1 (local), d=224.0.0.10 (BRI1), len 60, encapsulation fa
iled
6d21h: IP: s=169.254.115.7 (FastEthernet0), d=255.255.255.255, len 229, rcvd 2
6d21h: IP: s=192.110.1.1 (FastEthernet0), d=224.0.0.10, len 60, rcvd 2
6d21h: IP: s=192.110.1.222 (FastEthernet0), d=224.0.0.10, len 60, rcvd 2
6d21h: IP: s=192.110.1.4 (FastEthernet0), d=224.0.0.10, len 60, rcvd 2
6d21h: IP: s=192.110.1.3 (local), d=224.0.0.10 (FastEthernet0), len 60, sending
broad/multicast
6d21h: IP: s=192.110.1.2 (FastEthernet0), d=224.0.0.10, len 60, rcvd 2
6d21h: IP: s=192.110.96.1 (local), d=224.0.0.10 (BRI1), len 60, sending broad/mu
lticast
6d21h: IP: s=192.110.96.1 (local), d=224.0.0.10 (BRI1), len 60, encapsulation fa
iled
6d21h: IP: s=192.110.1.1 (FastEthernet0), d=224.0.0.10, len 60, rcvd 2
6d21h: IP: s=192.110.1.222 (FastEthernet0), d=224.0.0.10, len 60, rcvd 2
6d21h: IP: s=192.110.1.4 (FastEthernet0), d=224.0.0.10, len 60, rcvd 2
6d21h: IP: s=192.110.1.25 (FastEthernet0), d=192.110.1.255 (FastEthernet0), len
49, rcvd 3
6d21h: IP: s=192.110.1.3 (local), d=224.0.0.10 (FastEthernet0), len 60, sending
broad/multicast
6d21h: IP: s=192.110.1.2 (FastEthernet0), d=224.0.0.10, len 60, rcvd 2
6d21h: IP: s=192.110.96.1 (local), d=224.0.0.10 (BRI1), len 60, sending broad/mu
lticast
6d21h: IP: s=192.110.96.1 (local), d=224.0.0.10 (BRI1), len 60, encapsulation fa
iled
6d21h: IP: s=192.110.1.222 (FastEthernet0), d=224.0.0.10, len 60, rcvd 2


I assume that the reason it is using the multicast address because it is using EIGRP which has some link state properties and only sends triggered routing updates but I may be wrong there.

The 192.110.26.1 ip address that I am pinging is assigned to the ethernet port of the remote router and the 192.110.96.2 ip address is the BRI0 port on the remote router.

I only want the line to be brought up when something from 192.110.1.0 tries to connect to 192.110.26.1.

I can not put the default route to bri0 because the router is at the central site and any unknown packets are forwarded out to the internet throught the firewall.

please help

cheers

nichols
 
Upvote 0 Downvote
I'm a bit clearer on how your central router is configured now.

The fact that the encapsulation is failing to the remote router on the ping would *usually* indicate that the central site knows which interface to send the packets out of, but doesn't know how to route the packets.

If that makes sense ! ;-)

Have a look at the arp table on the central router to see if there are any incomplete MAC addresses corresponding to the .1 address.

I'm assuming that because you use EIGRP you're not fond of having static routes on the central site. However, you could create a static route for the remote site and redistribute it into EIGRP if that would be acceptable.

What networks does EIGRP advertise ?
 
Upvote 0 Downvote
The original error was *no dialer string, dialing can not occur* which points to a misconfig on the dialer, dialer map or dialer group.

How does failed encapsulation relate to that other then with a failed link, encapsulation is sure to fail.

The first debug of q921 says that the router and switch are talking correctly at that level. A debug of q931 I think would be very telling as it will give an exact error code to why the call was torn down. Or at least point to either the remote or local router as the source of the call termination.

For more debug info, look at this link:

This is becoming interesting ;-)

MikeS Find me at
&quot;Diplomacy; the art of saying 'nice doggie' till you can find a rock&quot; Wynn Catlin
 
Upvote 0 Downvote
Here is the output from debug isdn q931:

hayroute3#debug isdn q931
ISDN Q931 packets debugging is on
hayroute3#terminal monitor
hayroute3#ping 192.110.26.1

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.110.26.1, timeout is 2 seconds:

2d21h: ISDN BR1: TX -> SETUP pd = 8 callref = 0x2A
2d21h: Bearer Capability i = 0x8890
2d21h: Channel ID i = 0x83
2d21h: Called Party Number i = 0x80, '01942273369'
2d21h: ISDN BR1: RX <- CALL_PROC pd = 8 callref = 0xAA
2d21h: Channel ID i = 0x89
2d21h: ISDN BR1: RX <- CONNECT pd = 8 callref = 0xAA
2d21h: %LINK-3-UPDOWN: Interface BRI1:1, changed state to up
2d21h: ISDN BR1: TX -> CONNECT_ACK pd = 8 callref = 0x2A
2d21h: ISDN BR1: RX <- DISCONNECT pd = 8 callref = 0xAA
2d21h: Cause i = 0x8090 - Normal call clearing
2d21h: %LINK-3-UPDOWN: Interface BRI1:1, changed state to down.
2d21h: ISDN BR1: TX -> RELEASE pd = 8 callref = 0x2A
2d21h: ISDN BR1: RX <- RELEASE_COMP pd = 8 callref = 0xAA
2d21h: ISDN BR1: TX -> SETUP pd = 8 callref = 0x2B
2d21h: Bearer Capability i = 0x8890
2d21h: Channel ID i = 0x83
2d21h: Called Party Number i = 0x80, '01942273369'
2d21h: ISDN BR1: RX <- CALL_PROC pd = 8 callref = 0xAB
2d21h: Channel ID i = 0x89
2d21h: ISDN BR1: RX <- CONNECT pd = 8 callref = 0xAB
2d21h: %LINK-3-UPDOWN: Interface BRI1:1, changed state to up
2d21h: ISDN BR1: TX -> CONNECT_ACK pd = 8 callref = 0x2B
2d21h: ISDN BR1: RX <- DISCONNECT pd = 8 callref = 0xAB
2d21h: Cause i = 0x8090 - Normal call clearing
2d21h: %LINK-3-UPDOWN: Interface BRI1:1, changed state to down.
2d21h: ISDN BR1: TX -> RELEASE pd = 8 callref = 0x2B
2d21h: ISDN BR1: RX <- RELEASE_COMP pd = 8 callref = 0xAB
2d21h: ISDN BR1: TX -> SETUP pd = 8 callref = 0x2C
2d21h: Bearer Capability i = 0x8890
2d21h: Channel ID i = 0x83
2d21h: Called Party Number i = 0x80, '01942273369'
2d21h: ISDN BR1: RX <- CALL_PROC pd = 8 callref = 0xAC
2d21h: Channel ID i = 0x89
2d21h: ISDN BR1: RX <- CONNECT pd = 8 callref = 0xAC
2d21h: %LINK-3-UPDOWN: Interface BRI1:1, changed state to up
2d21h: ISDN BR1: TX -> CONNECT_ACK pd = 8 callref = 0x2C
2d21h: ISDN BR1: RX <- DISCONNECT pd = 8 callref = 0xAC
2d21h: Cause i = 0x8090 - Normal call clearing
2d21h: %LINK-3-UPDOWN: Interface BRI1:1, changed state to down.
2d21h: ISDN BR1: TX -> RELEASE pd = 8 callref = 0x2C
2d21h: ISDN BR1: RX <- RELEASE_COMP pd = 8 callref = 0xAC
2d21h: ISDN BR1: TX -> SETUP pd = 8 callref = 0x2D
2d21h: Bearer Capability i = 0x8890
2d21h: Channel ID i = 0x83
2d21h: Called Party Number i = 0x80, '01942273369'
2d21h: ISDN BR1: RX <- CALL_PROC pd = 8 callref = 0xAD
2d21h: Channel ID i = 0x89
2d21h: ISDN BR1: RX <- CONNECT pd = 8 callref = 0xAD
2d21h: %LINK-3-UPDOWN: Interface BRI1:1, changed state to up
2d21h: ISDN BR1: TX -> CONNECT_ACK pd = 8 callref = 0x2D
2d21h: ISDN BR1: RX <- DISCONNECT pd = 8 callref = 0xAD
2d21h: Cause i = 0x8090 - Normal call clearing
2d21h: %LINK-3-UPDOWN: Interface BRI1:1, changed state to down.
2d21h: ISDN BR1: TX -> RELEASE pd = 8 callref = 0x2D
2d21h: ISDN BR1: RX <- RELEASE_COMP pd = 8 callref = 0xAD
2d21h: ISDN BR1: TX -> SETUP pd = 8 callref = 0x2E
2d21h: Bearer Capability i = 0x8890
2d21h: Channel ID i = 0x83
2d21h: Called Party Number i = 0x80, '01942273369'
2d21h: ISDN BR1: RX <- CALL_PROC pd = 8 callref = 0xAE
2d21h: Channel ID i = 0x89
2d21h: ISDN BR1: RX <- CONNECT pd = 8 callref = 0xAE
2d21h: %LINK-3-UPDOWN: Interface BRI1:1, changed state to up
2d21h: ISDN BR1: TX -> CONNECT_ACK pd = 8 callref = 0x2E
2d21h: ISDN BR1: RX <- DISCONNECT pd = 8 callref = 0xAE
2d21h: Cause i = 0x8090 - Normal call clearing
2d21h: %LINK-3-UPDOWN: Interface BRI1:1, changed state to down.
Success rate is 0 percent (0/5)
hayroute3#
2d21h: ISDN BR1: TX -> RELEASE pd = 8 callref = 0x2E
2d21h: ISDN BR1: RX <- RELEASE_COMP pd = 8 callref = 0xAE

The strange thing is that from the remote site the router (Cisco 800 series) brings the line up ok. It is almost as if the central router (cisco 4000 series) does not support isdn dialup.

Do you know what this output says as it is a mystery to me!

cheers

Nichols

very frustrated with this now!!

 
Upvote 0 Downvote
If I remember q931 debugging properly an 8090 points to the call being disconnected by your router (80) due to an error with PPP setup or authentication. It's not actually an error with the ISDN - the line is being cleared because the router's not happy about something.

It's sulking ;-)

Have a look at debugging ppp negotiation, error and authentication. Not all at once though !
 
Upvote 0 Downvote
Here is a config for using Net3 ISDN... the one difference I see is this:

:::snip::
ppp authentication pap callin
ppp pap sent-username Username password Password
:::snip::


MikeS



ISDN (2503)

Current configuration:
!
version 12.0
service timestamps debug datetime
service timestamps log datetime
service password-encryption
!
hostname Router
!
!
!
ip subnet-zero
!
no ip finger
isdn switch-type basic-net3
isdn tei-negotiation first-call
!
!
!
interface Ethernet0
ip address 172.16.129.253 255.255.0.0
no ip directed-broadcast
ip nat inside
!
interface BRI0
no ip address
no ip directed-broadcast
ip nat outside
encapsulation ppp
dialer rotary-group 0
isdn switch-type basic-net3
compress stac
no cdp enable
!
interface Dialer0
ip address negotiated
no ip directed-broadcast
ip nat outside
encapsulation ppp
no ip mroute-cache
dialer in-band
dialer idle-timeout 300
dialer string 08452030458
dialer hold-queue 10
dialer load-threshold 200 either
dialer-group 1
compress stac
no cdp enable
ppp authentication pap callin
ppp pap sent-username Username password Password
ppp multilink
!
ip nat translation timeout 1800
ip nat inside source list 1 interface Dialer0 overload
no ip http server
ip classless
ip route 0.0.0.0 0.0.0.0 Dialer0
!
access-list 1 permit 172.16.0.0 0.0.255.255
dialer-list 1 protocol ip permit
!
line con 0
transport input none
stopbits 1
line vty 0 4
login
!
end

Find me at
&quot;Diplomacy; the art of saying 'nice doggie' till you can find a rock&quot; Wynn Catlin
 
Upvote 0 Downvote

I have visited the physical location of the ISDN line and central router and the cable was plugged into the second port of the ISDN2 box I have now moved this to the first port (from the left) and now the line is brought up by the dialer but it is failing to ping. However it appears that ppp authentication is taking place. below is the results of debug ppp negotiation:


23:25:18: BRI1: Dialing cause ip (s=192.110.96.1, d=192.110.26.1)
23:25:18: BRI1: Attempting to dial 01942273369
23:25:18: %LINK-3-UPDOWN: Interface BRI1:1, changed state to up
23:25:18: BR1:1 PPP: Treating connection as a callout
23:25:18: BR1:1 PPP: Phase is ESTABLISHING, Active Open
23:25:18: BR1:1 LCP: O CONFREQ [Closed] id 66 len 31
23:25:18: BR1:1 LCP: AuthProto CHAP (0x0305C22305)
23:25:18: BR1:1 LCP: MagicNumber 0xD5C294EB (0x0506D5C294EB)
23:25:18: BR1:1 LCP: MRRU 1524 (0x110405F4)
23:25:18: BR1:1 LCP: EndpointDisc 1 Local (0x130C01686179726F75746533)
23:25:18: BR1:1 LCP: I CONFREQ [REQsent] id 81 len 27
23:25:18: BR1:1 LCP: AuthProto CHAP (0x0305C22305)
23:25:18: BR1:1 LCP: MagicNumber 0x071E4816 (0x0506071E4816)
23:25:18: BR1:1 LCP: MRRU 1524 (0x110405F4)
23:25:18: BR1:1 LCP: EndpointDisc 1 Local (0x1308016C65656473)
23:25:18: BR1:1 LCP: O CONFACK [REQsent] id 81 len 27
23:25:18: BR1:1 LCP: AuthProto CHAP (0x0305C22305)
23:25:18: BR1:1 LCP: MagicNumber 0x071E4816 (0x0506071E4816)
23:25:18: BR1:1 LCP: MRRU 1524 (0x110405F4)
23:25:18: BR1:1 LCP: EndpointDisc 1 Local (0x1308016C65656473)
23:25:18: BR1:1 LCP: I CONFACK [ACKsent] id 66 len 31
23:25:18: BR1:1 LCP: AuthProto CHAP (0x0305C22305)
23:25:18: BR1:1 LCP: MagicNumber 0xD5C294EB (0x0506D5C294EB)
23:25:18: BR1:1 LCP: MRRU 1524 (0x110405F4)
23:25:18: BR1:1 LCP: EndpointDisc 1 Local (0x130C01686179726F75746533)
23:25:18: BR1:1 LCP: State is Open
23:25:18: BR1:1 PPP: Phase is AUTHENTICATING, by both
23:25:18: BR1:1 CHAP: O CHALLENGE id 66 len 30 from &quot;hayroute3&quot;
23:25:18: BR1:1 CHAP: I CHALLENGE id 66 len 26 from &quot;leeds&quot;
23:25:18: BR1:1 CHAP: O RESPONSE id 66 len 30 from &quot;hayroute3&quot;
23:25:18: BR1:1 CHAP: I SUCCESS id 66 len 4
23:25:18: %LINK-3-UPDOWN: Interface BRI1:1, changed state to down.
23:25:18: BR1:1 PPP: Phase is TERMINATING
23:25:18: BR1:1 LCP: State is Closed
23:25:18: BR1:1 PPP: Phase is DOWN
23:25:18: BR1:1 VP: Cleaning already proceeding
23:25:18: BRI1:1: disconnecting call
23:25:20: BRI1: Dialing cause ip (s=192.110.96.1, d=192.110.26.1)
23:25:20: BRI1: Attempting to dial 01942273369
23:25:20: %LINK-3-UPDOWN: Interface BRI1:1, changed state to up
23:25:20: BR1:1 PPP: Treating connection as a callout
23:25:20: BR1:1 PPP: Phase is ESTABLISHING, Active Open
23:25:20: BR1:1 LCP: O CONFREQ [Closed] id 67 len 31
23:25:20: BR1:1 LCP: AuthProto CHAP (0x0305C22305)
23:25:20: BR1:1 LCP: MagicNumber 0xD5C29CC8 (0x0506D5C29CC8)
23:25:20: BR1:1 LCP: MRRU 1524 (0x110405F4)
23:25:20: BR1:1 LCP: EndpointDisc 1 Local (0x130C01686179726F75746533)
23:25:20: BR1:1 LCP: I CONFREQ [REQsent] id 82 len 27
23:25:20: BR1:1 LCP: AuthProto CHAP (0x0305C22305)
23:25:20: BR1:1 LCP: MagicNumber 0x071E4FF0 (0x0506071E4FF0)
23:25:20: BR1:1 LCP: MRRU 1524 (0x110405F4)
23:25:20: BR1:1 LCP: EndpointDisc 1 Local (0x1308016C65656473)
23:25:20: BR1:1 LCP: O CONFACK [REQsent] id 82 len 27
23:25:20: BR1:1 LCP: AuthProto CHAP (0x0305C22305)
23:25:20: BR1:1 LCP: MagicNumber 0x071E4FF0 (0x0506071E4FF0)
23:25:20: BR1:1 LCP: MRRU 1524 (0x110405F4)
23:25:20: BR1:1 LCP: EndpointDisc 1 Local (0x1308016C65656473)
23:25:20: BR1:1 LCP: I CONFACK [ACKsent] id 67 len 31
23:25:20: BR1:1 LCP: AuthProto CHAP (0x0305C22305)
23:25:20: BR1:1 LCP: MagicNumber 0xD5C29CC8 (0x0506D5C29CC8)
23:25:20: BR1:1 LCP: MRRU 1524 (0x110405F4)
23:25:20: BR1:1 LCP: EndpointDisc 1 Local (0x130C01686179726F75746533)
23:25:20: BR1:1 LCP: State is Open
23:25:20: BR1:1 PPP: Phase is AUTHENTICATING, by both
23:25:20: BR1:1 CHAP: O CHALLENGE id 67 len 30 from &quot;hayroute3&quot;
23:25:20: BR1:1 CHAP: I CHALLENGE id 67 len 26 from &quot;leeds&quot;
23:25:20: BR1:1 CHAP: O RESPONSE id 67 len 30 from &quot;hayroute3&quot;
23:25:20: BR1:1 CHAP: I SUCCESS id 67 len 4
23:25:20: %LINK-3-UPDOWN: Interface BRI1:1, changed state to down.
23:25:20: BR1:1 PPP: Phase is TERMINATING
23:25:20: BR1:1 LCP: State is Closed
23:25:20: BR1:1 PPP: Phase is DOWN
23:25:20: BR1:1 VP: Cleaning already proceeding
23:25:20: BRI1:1: disconnecting call
23:25:22: BRI1: Dialing cause ip (s=192.110.96.1, d=192.110.26.1)
23:25:22: BRI1: Attempting to dial 01942273369
23:25:22: %LINK-3-UPDOWN: Interface BRI1:1, changed state to up
23:25:22: BR1:1 PPP: Treating connection as a callout
23:25:22: BR1:1 PPP: Phase is ESTABLISHING, Active Open
23:25:22: BR1:1 LCP: O CONFREQ [Closed] id 68 len 31
23:25:22: BR1:1 LCP: AuthProto CHAP (0x0305C22305)
23:25:22: BR1:1 LCP: MagicNumber 0xD5C2A49E (0x0506D5C2A49E)
23:25:22: BR1:1 LCP: MRRU 1524 (0x110405F4)
23:25:22: BR1:1 LCP: EndpointDisc 1 Local (0x130C01686179726F75746533)
23:25:22: BR1:1 LCP: I CONFREQ [REQsent] id 83 len 27
23:25:22: BR1:1 LCP: AuthProto CHAP (0x0305C22305)
23:25:22: BR1:1 LCP: MagicNumber 0x071E57CB (0x0506071E57CB)
23:25:22: BR1:1 LCP: MRRU 1524 (0x110405F4)
23:25:22: BR1:1 LCP: EndpointDisc 1 Local (0x1308016C65656473)
23:25:22: BR1:1 LCP: O CONFACK [REQsent] id 83 len 27
23:25:22: BR1:1 LCP: AuthProto CHAP (0x0305C22305)
23:25:22: BR1:1 LCP: MagicNumber 0x071E57CB (0x0506071E57CB)
23:25:22: BR1:1 LCP: MRRU 1524 (0x110405F4)
23:25:22: BR1:1 LCP: EndpointDisc 1 Local (0x1308016C65656473)
23:25:22: BR1:1 LCP: I CONFACK [ACKsent] id 68 len 31
23:25:22: BR1:1 LCP: AuthProto CHAP (0x0305C22305)
23:25:22: BR1:1 LCP: MagicNumber 0xD5C2A49E (0x0506D5C2A49E)
23:25:22: BR1:1 LCP: MRRU 1524 (0x110405F4)
23:25:22: BR1:1 LCP: EndpointDisc 1 Local (0x130C01686179726F75746533)
23:25:22: BR1:1 LCP: State is Open
23:25:22: BR1:1 PPP: Phase is AUTHENTICATING, by both
23:25:22: BR1:1 CHAP: O CHALLENGE id 68 len 30 from &quot;hayroute3&quot;
23:25:22: BR1:1 CHAP: I CHALLENGE id 68 len 26 from &quot;leeds&quot;
23:25:22: BR1:1 CHAP: O RESPONSE id 68 len 30 from &quot;hayroute3&quot;
23:25:22: BR1:1 CHAP: I SUCCESS id 68 len 4
23:25:22: %LINK-3-UPDOWN: Interface BRI1:1, changed state to down.
23:25:22: BR1:1 PPP: Phase is TERMINATING
23:25:22: BR1:1 LCP: State is Closed
23:25:22: BR1:1 PPP: Phase is DOWN
23:25:22: BR1:1 VP: Cleaning already proceeding
23:25:22: BRI1:1: disconnecting call
23:25:24: BRI1: Dialing cause ip (s=192.110.96.1, d=192.110.26.1)
23:25:24: BRI1: Attempting to dial 01942273369
23:25:24: %LINK-3-UPDOWN: Interface BRI1:1, changed state to up
23:25:24: BR1:1 PPP: Treating connection as a callout
23:25:24: BR1:1 PPP: Phase is ESTABLISHING, Active Open
23:25:24: BR1:1 LCP: O CONFREQ [Closed] id 69 len 31
23:25:24: BR1:1 LCP: AuthProto CHAP (0x0305C22305)
23:25:24: BR1:1 LCP: MagicNumber 0xD5C2AC67 (0x0506D5C2AC67)
23:25:24: BR1:1 LCP: MRRU 1524 (0x110405F4)
23:25:24: BR1:1 LCP: EndpointDisc 1 Local (0x130C01686179726F75746533)
23:25:24: BR1:1 LCP: I CONFREQ [REQsent] id 84 len 27
23:25:24: BR1:1 LCP: AuthProto CHAP (0x0305C22305)
23:25:24: BR1:1 LCP: MagicNumber 0x071E5F91 (0x0506071E5F91)
23:25:24: BR1:1 LCP: MRRU 1524 (0x110405F4)
23:25:24: BR1:1 LCP: EndpointDisc 1 Local (0x1308016C65656473)
23:25:24: BR1:1 LCP: O CONFACK [REQsent] id 84 len 27
23:25:24: BR1:1 LCP: AuthProto CHAP (0x0305C22305)
23:25:24: BR1:1 LCP: MagicNumber 0x071E5F91 (0x0506071E5F91)
23:25:24: BR1:1 LCP: MRRU 1524 (0x110405F4)
23:25:24: BR1:1 LCP: EndpointDisc 1 Local (0x1308016C65656473)
23:25:24: BR1:1 LCP: I CONFACK [ACKsent] id 69 len 31
23:25:24: BR1:1 LCP: AuthProto CHAP (0x0305C22305)
23:25:24: BR1:1 LCP: MagicNumber 0xD5C2AC67 (0x0506D5C2AC67)
23:25:24: BR1:1 LCP: MRRU 1524 (0x110405F4)
23:25:24: BR1:1 LCP: EndpointDisc 1 Local (0x130C01686179726F75746533)
23:25:24: BR1:1 LCP: State is Open
23:25:24: BR1:1 PPP: Phase is AUTHENTICATING, by both
23:25:24: BR1:1 CHAP: O CHALLENGE id 69 len 30 from &quot;hayroute3&quot;
23:25:24: BR1:1 CHAP: I CHALLENGE id 69 len 26 from &quot;leeds&quot;
23:25:24: BR1:1 CHAP: O RESPONSE id 69 len 30 from &quot;hayroute3&quot;
23:25:24: BR1:1 CHAP: I SUCCESS id 69 len 4
23:25:24: %LINK-3-UPDOWN: Interface BRI1:1, changed state to down.
23:25:24: BR1:1 PPP: Phase is TERMINATING
23:25:24: BR1:1 LCP: State is Closed
23:25:24: BR1:1 PPP: Phase is DOWN
23:25:24: BR1:1 VP: Cleaning already proceeding
23:25:24: BRI1:1: disconnecting call
23:25:26: BRI1: Dialing cause ip (s=192.110.96.1, d=192.110.26.1)
23:25:26: BRI1: Attempting to dial 01942273369
23:25:26: %LINK-3-UPDOWN: Interface BRI1:1, changed state to up
23:25:26: BR1:1 PPP: Treating connection as a callout
23:25:26: BR1:1 PPP: Phase is ESTABLISHING, Active Open
23:25:26: BR1:1 LCP: O CONFREQ [Closed] id 70 len 31
23:25:26: BR1:1 LCP: AuthProto CHAP (0x0305C22305)
23:25:26: BR1:1 LCP: MagicNumber 0xD5C2B42D (0x0506D5C2B42D)
23:25:26: BR1:1 LCP: MRRU 1524 (0x110405F4)
23:25:26: BR1:1 LCP: EndpointDisc 1 Local (0x130C01686179726F75746533)
23:25:26: BR1:1 LCP: I CONFREQ [REQsent] id 85 len 27
23:25:26: BR1:1 LCP: AuthProto CHAP (0x0305C22305)
23:25:26: BR1:1 LCP: MagicNumber 0x071E675C (0x0506071E675C)
23:25:26: BR1:1 LCP: MRRU 1524 (0x110405F4)
23:25:26: BR1:1 LCP: EndpointDisc 1 Local (0x1308016C65656473)
23:25:26: BR1:1 LCP: O CONFACK [REQsent] id 85 len 27
23:25:26: BR1:1 LCP: AuthProto CHAP (0x0305C22305)
23:25:26: BR1:1 LCP: MagicNumber 0x071E675C (0x0506071E675C)
23:25:26: BR1:1 LCP: MRRU 1524 (0x110405F4)
23:25:26: BR1:1 LCP: EndpointDisc 1 Local (0x1308016C65656473)
23:25:26: BR1:1 LCP: I CONFACK [ACKsent] id 70 len 31
23:25:26: BR1:1 LCP: AuthProto CHAP (0x0305C22305)
23:25:26: BR1:1 LCP: MagicNumber 0xD5C2B42D (0x0506D5C2B42D)
23:25:26: BR1:1 LCP: MRRU 1524 (0x110405F4)
23:25:26: BR1:1 LCP: EndpointDisc 1 Local (0x130C01686179726F75746533)
23:25:26: BR1:1 LCP: State is Open
23:25:26: BR1:1 PPP: Phase is AUTHENTICATING, by both
23:25:26: BR1:1 CHAP: O CHALLENGE id 70 len 30 from &quot;hayroute3&quot;
23:25:26: BR1:1 CHAP: I CHALLENGE id 70 len 26 from &quot;leeds&quot;
23:25:26: BR1:1 CHAP: O RESPONSE id 70 len 30 from &quot;hayroute3&quot;
23:25:26: BR1:1 CHAP: I SUCCESS id 70 len 4
23:25:26: %LINK-3-UPDOWN: Interface BRI1:1, changed state to down.
Success rate is 0 percent (0/5)
hayroute3#
23:25:26: BR1:1 PPP: Phase is TERMINATING
23:25:26: BR1:1 LCP: State is Closed
23:25:26: BR1:1 PPP: Phase is DOWN
23:25:26: BR1:1 VP: Cleaning already proceeding
23:25:26: BRI1:1: disconnecting call


It appears when I debug ppp chap that the handshake is taking place ok and is successfull but something is dropping the line and leading the ping to be unsucessful.

hayroute3#debug ppp chap
PPP authentication debugging is on
hayroute3#ping 192.110.26.1

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.110.26.1, timeout is 2 seconds:

23:32:03: %LINK-3-UPDOWN: Interface BRI1:1, changed state to up
23:32:03: BR1:1 PPP: Treating connection as a callout
23:32:03: BR1:1 PPP: Phase is AUTHENTICATING, by both
23:32:03: BR1:1 CHAP: O CHALLENGE id 71 len 30 from &quot;hayroute3&quot;
23:32:03: BR1:1 CHAP: I CHALLENGE id 71 len 26 from &quot;leeds&quot;
23:32:03: BR1:1 CHAP: O RESPONSE id 71 len 30 from &quot;hayroute3&quot;
23:32:03: BR1:1 CHAP: I SUCCESS id 71 len 4.
23:32:03: %LINK-3-UPDOWN: Interface BRI1:1, changed state to down
23:32:05: %LINK-3-UPDOWN: Interface BRI1:1, changed state to up
23:32:05: BR1:1 PPP: Treating connection as a callout
23:32:05: BR1:1 PPP: Phase is AUTHENTICATING, by both
23:32:05: BR1:1 CHAP: O CHALLENGE id 72 len 30 from &quot;hayroute3&quot;
23:32:05: BR1:1 CHAP: I CHALLENGE id 72 len 26 from &quot;leeds&quot;
23:32:05: BR1:1 CHAP: O RESPONSE id 72 len 30 from &quot;hayroute3&quot;
23:32:05: BR1:1 CHAP: I SUCCESS id 72 len 4.
23:32:05: %LINK-3-UPDOWN: Interface BRI1:1, changed state to down
23:32:07: %LINK-3-UPDOWN: Interface BRI1:1, changed state to up
23:32:07: BR1:1 PPP: Treating connection as a callout
23:32:07: BR1:1 PPP: Phase is AUTHENTICATING, by both
23:32:07: BR1:1 CHAP: O CHALLENGE id 73 len 30 from &quot;hayroute3&quot;
23:32:07: BR1:1 CHAP: I CHALLENGE id 73 len 26 from &quot;leeds&quot;
23:32:07: BR1:1 CHAP: O RESPONSE id 73 len 30 from &quot;hayroute3&quot;
23:32:07: BR1:1 CHAP: I SUCCESS id 73 len 4.
23:32:07: %LINK-3-UPDOWN: Interface BRI1:1, changed state to down
23:32:09: %LINK-3-UPDOWN: Interface BRI1:1, changed state to up
23:32:09: BR1:1 PPP: Treating connection as a callout
23:32:09: BR1:1 PPP: Phase is AUTHENTICATING, by both
23:32:09: BR1:1 CHAP: O CHALLENGE id 74 len 30 from &quot;hayroute3&quot;
23:32:09: BR1:1 CHAP: I CHALLENGE id 74 len 26 from &quot;leeds&quot;
23:32:09: BR1:1 CHAP: O RESPONSE id 74 len 30 from &quot;hayroute3&quot;
23:32:09: BR1:1 CHAP: I SUCCESS id 74 len 4.
23:32:09: %LINK-3-UPDOWN: Interface BRI1:1, changed state to down
23:32:11: %LINK-3-UPDOWN: Interface BRI1:1, changed state to up
23:32:11: BR1:1 PPP: Treating connection as a callout
23:32:11: BR1:1 PPP: Phase is AUTHENTICATING, by both
23:32:11: BR1:1 CHAP: O CHALLENGE id 75 len 30 from &quot;hayroute3&quot;
23:32:11: BR1:1 CHAP: I CHALLENGE id 75 len 26 from &quot;leeds&quot;
23:32:11: BR1:1 CHAP: O RESPONSE id 75 len 30 from &quot;hayroute3&quot;
23:32:11: BR1:1 CHAP: I SUCCESS id 75 len 4.
Success rate is 0 percent (0/5)
hayroute3#
23:32:11: %LINK-3-UPDOWN: Interface BRI1:1, changed state to down


please help as this is really doing my head in now!!!!
 
Upvote 0 Downvote
The remote sites config is as below:

leeds#show run
Building configuration...

Current configuration : 1486 bytes
!
! Last configuration change at 17:01:09 UTC Fri Nov 16 2001 by leeds
! NVRAM config last updated at 16:39:14 UTC Fri Nov 16 2001 by leeds
!
version 12.1
no service pad
service timestamps debug uptime
service timestamps log uptime
service password-encryption
!
hostname leeds
!
logging buffered 8192 debugging
enable secret 5 $XXXXXXXXXXXXXXXXXXXXXXXX
!
username leeds password 7 071F205F5D1E161713
!
!
!
!
!
ip subnet-zero
no ip source-route
!
isdn switch-type basic-net3
!
!
!
interface Ethernet0
ip address 192.110.26.1 255.255.255.0
no ip proxy-arp
!
interface BRI0
ip address 192.110.96.2 255.255.255.0
encapsulation ppp
dialer pool-member 1
isdn switch-type basic-net3
ppp authentication chap pap callin
ppp multilink
!
interface Dialer1
description ISP
ip address negotiated
no ip proxy-arp
ip nat outside
encapsulation ppp
no ip split-horizon
dialer pool 1
dialer remote-name Cisco1
dialer idle-timeout 360
dialer string xxxxxxxxxxx class DialClass
dialer hold-queue 10
dialer load-threshold 20 either
dialer-group 1
ppp authentication chap pap callin
ppp chap hostname leeds
ppp chap password 7 060A0A24485D
ppp pap sent-username leeds password 7 141B170E0817
ppp multilink
!
ip http server
ip classless
ip route 0.0.0.0 0.0.0.0 Dialer1
!
!
map-class dialer DialClass
dialer-list 1 protocol ip permit
!
line con 0
exec-timeout 120 0
stopbits 1
line vty 0 4
exec-timeout 0 0
login local
!
time-range TIME
periodic daily 0:00 to 23:59
!
end

leeds#





The Central sites config is below this is the side that will not dial to the remote site. This is the side that we require to dial Leeds.We are using BRI1 to dial up Leeds:




hayroute3#show run
Building configuration...

Current configuration:
!
version 11.3
service timestamps debug uptime
service timestamps log uptime
no service password-encryption
!
hostname hayroute3
!
enable secret 5 $1xxxxxxxxxxxxxxxxxxxxxxxxxxx
enable password xxxxxxxxxxx
!
username leeds password 0 leeds
no ip domain-lookup
ipx routing 00d0.bbfa.fb62
isdn switch-type basic-net3
!
!
!
interface Serial0
description Kilostream link to Stone Cross (VSD)
ip address 192.110.11.1 255.255.255.0
bandwidth 2048
shutdown
no fair-queue
compress stac
!
interface Serial1
no ip address
shutdown
no fair-queue
compress stac
!
interface Serial2
no ip address
shutdown
no fair-queue
compress stac
!
interface Serial3
no ip address
shutdown
no fair-queue
compress stac
!
interface BRI0
description ISDN dial up connection to Leeds
ip address 192.110.96.1 255.255.255.0
encapsulation ppp
shutdown
dialer map ip 192.110.96.2 name leeds xxxxxxxxxxx
dialer-group 1
isdn switch-type basic-net3
no fair-queue
ppp authentication chap pap
ppp chap hostname hayroute3
ppp chap password 7 151E0E090039
ppp multilink
!
interface BRI1
ip address 192.110.96.1 255.255.255.0
encapsulation ppp
dialer idle-timeout 2147483
dialer map ip 192.110.96.2 name leeds xxxxxxxxxxx
dialer-group 1
isdn switch-type basic-net3
ppp authentication chap
ppp multilink
!
interface BRI2
no ip address
no ip route-cache
no ip mroute-cache
shutdown
dialer-group 1
isdn switch-type basic-net3
no fair-queue
!
interface BRI3
no ip address
shutdown
isdn switch-type basic-net3
!
interface FastEthernet0
description Ethernet i/f @ Haydock
ip address 192.110.1.3 255.255.255.0
no mop enabled
!
router eigrp 100
redistribute static
network 192.110.1.0
network 192.110.11.0
network 192.110.96.0
no auto-summary
!
no ip classless
ip route 0.0.0.0 0.0.0.0 192.110.1.253
ip route 192.110.17.0 255.255.255.0 192.110.1.1
ip route 192.110.20.0 255.255.255.0 192.110.1.2
ip route 192.110.24.0 255.255.255.0 192.110.1.2
ip route 192.110.26.0 255.255.255.0 192.110.96.2
!
dialer-list 1 protocol ip permit
snmp-server community public RO
snmp-server enable traps snmp
snmp-server enable traps isdn call-information
snmp-server enable traps config
snmp-server enable traps bgp
snmp-server enable traps frame-relay
!
!
!
alias exec stockpack telnet 192.110.6.1
alias exec haydock2 telnet 192.110.1.2
!
line con 0
exec-timeout 0 0
line aux 0
line vty 0 4
password password
login
!
end

hayroute3#
 
Upvote 0 Downvote
From config of router Leeds, you have defined a ip addr in the inter bri 0 but you are also defined 'easy ip/NAT ' in inter dialer 1 ???
From cisco standard config , the ip addr should be in dialer interface.
So,
inter bri 0
no ip addr
inter dialer 1
ip addr x.x.x.x
no ip nat
dialer remote-name hayroute 3

From router hayroute3
inter bri 1
ppp chap callin

Hope this will help, if still need any further action, I would like to see 'debug isdn q931, debug ppp chap, debug ppp neg' for both ends
 
Upvote 0 Downvote
Hi Nichols,
When you are configuring ISDN using CHAP authentication you have to give in your central router,remote end router's user name and password and in the remote side the central router's user name and password (in the username command).This shud solve your probs.
 
Upvote 0 Downvote
I've finally solved it thank god!!!!!!


It was that the on the remote router (Leeds) the dialer 1 interface was configured with a statement saying:

dialer remote-name leeds (which was itself)

it should have been:

dialer remote-name hayroute3 (which is the name of the router which is trying to dial in.)

This was the reason why the connection was being brought up and being dropped every time. It is always something that is under your nose typical.

Cheers for all those who have helped and given advice.

until I have to configure another ISDN router (Hopefully not in the next century or so!!!!)

Later

Nichols
 
Upvote 0 Downvote
Status
Not open for further replies.

Similar threads

bfordz
  • Locked
  • Question
new help on setting up third party VoIP phones through Catalyst 2960x switch
Replies
0
Views
101
bfordz
bfordz
telemarksman
  • Locked
  • Question
ATA Cisco SPA122 not triggering single line courtesy phone ringer
Replies
0
Views
86
telemarksman
telemarksman
quazimotto
  • Locked
  • Question
Cisco ASA_5505 VPN to Juniper_SRX210 VPN IS UP_ No Traffic!!!!!!
Replies
0
Views
65
quazimotto
quazimotto
msk69
  • Locked
  • Question
CISCO 7942 Phone Upgrading to SIP
Replies
0
Views
90
msk69
msk69
serge9
  • Locked
  • Question
Cisco GUI on cme stop working
Replies
2
Views
138
serge9
serge9

Part and Inventory Search

Sponsor

Back
Top