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!

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

ISDN2e Problem between sites

Status
Not open for further replies.

mjhonline

IS-IT--Management
Dec 26, 2000
26
0
0
GB
Right, where to start..

Central site has Cisco 2620
2 x remote sites each have Cisco 1603-R

Central site can initiate an ISDN call to either site and once connected two way traffic is possible and all is well.

However, neither remote site can initiate the ISDN call, and if you type 'sh isdn his' from the 2620 it just shows loads of attempts from the remote sites lasting 0 seconds, in other words the line is raised but drops immediately, any ideas greatly appreciated.

one of the remote 1603 configs is below.

Mike.


!
version 12.0
service timestamps debug uptime
service timestamps log uptime
service password-encryption
!
hostname xxxxx
!
enable password 7 xxxxx
!
username xxxxx password 7 xxxxx
ip subnet-zero
isdn switch-type basic-net3
!
!
!
interface Ethernet0
ip address 192.0.110.1 255.255.255.0
no ip directed-broadcast
!
interface BRI0
no ip address
no ip directed-broadcast
encapsulation ppp
dialer pool-member 1
isdn switch-type basic-net3
isdn tei-negotiation first-call
isdn send-alerting
no fair-queue
no cdp enable
ppp authentication chap
ppp multilink
!
interface Dialer0
description ISDN Connection to xxxxx
ip unnumbered Ethernet0
no ip directed-broadcast
encapsulation ppp
dialer remote-name xxxxx
dialer string xxxxx
dialer load-threshold 200 outbound
dialer pool 1
dialer-group 1
no fair-queue
no cdp enable
ppp authentication chap
ppp multilink
!
no ip classless
ip route 0.0.0.0 0.0.0.0 Dialer0
ip route 192.0.100.0 255.255.255.0 Dialer0
ip route 192.0.120.0 255.255.255.0 Dialer0
!
dialer-list 1 protocol ip permit
!
line con 0
password 7 xxxxx
transport input none
line vty 0 4
exec-timeout 30 0
password 7 xxxxx
login
!
end



 
Give us the printout from this command:

debug isdn q921

This will give detailed info to exactly what is happening when the connection is started up for layer 2. There will be a code to why it's terminated.

If the debug of q921 comes up clean then move to layer 3 with this command:

debug isdn q931

Samething.. there will be detailed info for this command.

Find me at
"Take advantage of the enemy's unreadiness, make your way by unexpected routes, and attack unguarded spots."
Sun Tzu
 
Thanks for taking time to look at debug info below, I hope it means more to you than it does to me!

Mike.

Output of debug isdn q921:

3d05h: ISDN BR0: TX -> RRr sapi = 0 tei = 116 nr = 11
3d05h: %LINK-3-UPDOWN: Interface BRI0:1, changed state to up
3d05h: %DIALER-6-BIND: Interface BR0:1 bound to profile Di0
3d05h: %ISDN-6-CONNECT: Interface BRI0:1 is now connected to 01234567890
3d05h: ISDN BR0: TX -> INFOc sapi = 0 tei = 116 ns = 122 nr = 11 i = 0x0801
670F
3d05h: ISDN BR0: RX <- RRr sapi = 0 tei = 116 nr = 123
3d05h: ISDN BR0: RX <- INFOc sapi = 0 tei = 116 ns = 11 nr = 123 i = 0x0801
E74508028090
3d05h: ISDN BR0: TX -> RRr sapi = 0 tei = 116 nr = 12
3d05h: %LINK-3-UPDOWN: Interface BRI0:1, changed state to down
3d05h: %DIALER-6-UNBIND: Interface BR0:1 unbound from profile Di0
3d05h: ISDN BR0: TX -> INFOc sapi = 0 tei = 116 ns = 123 nr = 12 i = 0x0801
674D
3d05h: ISDN BR0: RX <- RRr sapi = 0 tei = 116 nr = 124
3d05h: ISDN BR0: RX <- INFOc sapi = 0 tei = 116 ns = 12 nr = 124 i = 0x0801
E75A
3d05h: ISDN BR0: TX -> RRr sapi = 0 tei = 116 nr = 13
3d05h: ISDN BR0: TX -> INFOc sapi = 0 tei = 116 ns = 124 nr = 13 i = 0x0801
680504028890180183700C803031343533353231303538
3d05h: ISDN BR0: RX <- RRr sapi = 0 tei = 116 nr = 125
3d05h: ISDN BR0: RX <- INFOc sapi = 0 tei = 116 ns = 13 nr = 125 i = 0x0801
E802180189
3d05h: ISDN BR0: TX -> RRr sapi = 0 tei = 116 nr = 14
3d05h: ISDN BR0: RX <- INFOc sapi = 0 tei = 116 ns = 14 nr = 125 i = 0x0801
E807
3d05h: ISDN BR0: TX -> RRr sapi = 0 tei = 116 nr = 15
3d05h: %LINK-3-UPDOWN: Interface BRI0:1, changed state to up
3d05h: %DIALER-6-BIND: Interface BR0:1 bound to profile Di0
3d05h: %ISDN-6-CONNECT: Interface BRI0:1 is now connected to 01234567890
3d05h: ISDN BR0: TX -> INFOc sapi = 0 tei = 116 ns = 125 nr = 15 i = 0x0801
680F
3d05h: ISDN BR0: RX <- RRr sapi = 0 tei = 116 nr = 126
3d05h: ISDN BR0: RX <- INFOc sapi = 0 tei = 116 ns = 15 nr = 126 i = 0x0801
E84508028090
3d05h: ISDN BR0: TX -> RRr sapi = 0 tei = 116 nr = 16
3d05h: %LINK-3-UPDOWN: Interface BRI0:1, changed state to down
3d05h: %DIALER-6-UNBIND: Interface BR0:1 unbound from profile Di0
3d05h: ISDN BR0: TX -> INFOc sapi = 0 tei = 116 ns = 126 nr = 16 i = 0x0801
684D
3d05h: ISDN BR0: RX <- RRr sapi = 0 tei = 116 nr = 127
3d05h: ISDN BR0: RX <- INFOc sapi = 0 tei = 116 ns = 16 nr = 127 i = 0x0801
E85A




output of debug isdn q931:
REMOTE_SITE#debug isdn q931
ISDN Q931 packets debugging is on
REMOTE_SITE#term mon
REMOTE_SITE#
3d05h: ISDN BR0: TX -> RRp sapi = 0 tei = 116 nr = 28
3d05h: ISDN BR0: RX <- RRf sapi = 0 tei = 116 nr = 9
3d05h: %DIALER-6-UNBIND: Interface Vi1 unbound from profile Di0
3d05h: %LINK-3-UPDOWN: Interface Virtual-Access1, changed state to down
3d05h: ISDN BR0: RX <- INFOc sapi = 0 tei = 116 ns = 28 nr = 9 i = 0x080101
4508028090
3d05h: DISCONNECT pd = 8 callref = 0x01
3d05h: Cause i = 0x8090 - Normal call clearing
3d05h: ISDN BR0: TX -> RRr sapi = 0 tei = 116 nr = 29
3d05h: %ISDN-6-DISCONNECT: Interface BRI0:1 disconnected from 01234567890 CENTR
AL_SITE, call lasted 297 seconds
3d05h: %LINK-3-UPDOWN: Interface BRI0:1, changed state to down
3d05h: %DIALER-6-UNBIND: Interface BR0:1 unbound from profile Di0
3d05h: ISDN BR0: TX -> INFOc sapi = 0 tei = 116 ns = 9 nr = 29 i = 0x080181
4D
3d05h: RELEASE pd = 8 callref = 0x81
3d05h: ISDN BR0: RX <- RRr sapi = 0 tei = 116 nr = 10
3d05h: ISDN BR0: RX <- INFOc sapi = 0 tei = 116 ns = 29 nr = 10 i = 0x08010
15A
3d05h: RELEASE_COMP pd = 8 callref = 0x01
3d05h: ISDN BR0: TX -> RRr sapi = 0 tei = 116 nr = 30
3d05h: %LINEPROTO-5-UPDOWN: Line protocol on Interface BRI0:1, changed state to
down
3d05h: %LINEPROTO-5-UPDOWN: Line protocol on Interface Virtual-Access1, changed
state to down
3d05h: ISDN BR0: TX -> RRp sapi = 0 tei = 116 nr = 30
3d05h: ISDN BR0: RX <- RRf sapi = 0 tei = 116 nr = 10
3d05h: ISDN BR0: TX -> RRp sapi = 0 tei = 116 nr = 30
3d05h: ISDN BR0: RX <- RRf sapi = 0 tei = 116 nr = 10
3d05h: ISDN BR0: RX <- UI sapi = 0 tei = 127 i = 0x08010105A104028890180189700
781373633383932
3d05h: SETUP pd = 8 callref = 0x01
3d05h: Sending Complete
3d05h: Bearer Capability i = 0x8890
3d05h: Channel ID i = 0x89
3d05h: Called Party Number i = 0x81, '763892'
3d05h: %DIALER-6-BIND: Interface BR0:1 bound to profile Di0
3d05h: %LINK-3-UPDOWN: Interface BRI0:1, changed state to up
3d05h: %ISDN-6-CONNECT: Interface BRI0:1 is now connected to 01234567890
3d05h: ISDN BR0: TX -> INFOc sapi = 0 tei = 116 ns = 10 nr = 30 i = 0x08018
101
3d05h: ALERTING pd = 8 callref = 0x81
3d05h: ISDN BR0: RX <- RRr sapi = 0 tei = 116 nr = 11
3d05h: ISDN BR0: TX -> INFOc sapi = 0 tei = 116 ns = 11 nr = 30 i = 0x08018
107
3d05h: CONNECT pd = 8 callref = 0x81
3d05h: ISDN BR0: RX <- RRr sapi = 0 tei = 116 nr = 12
3d05h: ISDN BR0: RX <- INFOc sapi = 0 tei = 116 ns = 30 nr = 12 i = 0x08010
10F

 
OK.. here is a clue from debug q931

::snip::
3d05h: DISCONNECT pd = 8 callref = 0x01
3d05h: Cause i = 0x8090 - Normal call clearing
::snip::

This is the diconnect message. The cause for the disconnect is 0x8090 and translates into this:

80 - cause code 80- from router
90 - normal cause clearing. This means that the connection was cleared *normally* so something higher in the chain triggered the clearing of the call. This could be an authentication error, PPP error etc..

try these next two steps:

DEBUG PPP NEGOTIATION
DEBUG PPP AUTHENTICATION

These will help verify that the PPP connection is not at fault.

MikeS

Find me at
&quot;Take advantage of the enemy's unreadiness, make your way by unexpected routes, and attack unguarded spots.&quot;
Sun Tzu
 
Right then, here's the output from debug ppp authentication.

Mike H.

For obvious reasons names & numbers changed:

CENTRAL_SITE - 01234567890

REMOTE_SITE - 123456

------------------
4d00h: RELEASE pd = 8 callref = 0x36
4d00h: ISDN BR0: RX <- RRr sapi = 0 tei = 116 nr = 39
4d00h: ISDN BR0: RX <- INFOc sapi = 0 tei = 116 ns = 89 nr = 39 i = 0x0801B
65A
4d00h: RELEASE_COMP pd = 8 callref = 0xB6
4d00h: ISDN BR0: TX -> RRr sapi = 0 tei = 116 nr = 90
4d00h: ISDN BR0: TX -> INFOc sapi = 0 tei = 116 ns = 39 nr = 90 i = 0x08013
70504028890180183700C803031343533353231303538
4d00h: SETUP pd = 8 callref = 0x37
4d00h: Bearer Capability i = 0x8890
4d00h: Channel ID i = 0x83
4d00h: Called Party Number i = 0x80, '01234567890'
4d00h: ISDN BR0: RX <- RRr sapi = 0 tei = 116 nr = 40
4d00h: ISDN BR0: RX <- INFOc sapi = 0 tei = 116 ns = 90 nr = 40 i = 0x0801B
702180189
4d00h: CALL_PROC pd = 8 callref = 0xB7
4d00h: Channel ID i = 0x89
4d00h: ISDN BR0: TX -> RRr sapi = 0 tei = 116 nr = 91
4d00h: ISDN BR0: RX <- INFOc sapi = 0 tei = 116 ns = 91 nr = 40 i = 0x0801B
707
4d00h: CONNECT pd = 8 callref = 0xB7
4d00h: ISDN BR0: TX -> RRr sapi = 0 tei = 116 nr = 92
4d00h: %LINK-3-UPDOWN: Interface BRI0:1, changed state to up
4d00h: %DIALER-6-BIND: Interface BR0:1 bound to profile Di0
4d00h: %ISDN-6-CONNECT: Interface BRI0:1 is now connected to 01234567890
4d00h: BR0:1 PPP: Treating connection as a callout
4d00h: ISDN BR0: TX -> INFOc sapi = 0 tei = 116 ns = 40 nr = 92 i = 0x08013
70F
4d00h: CONNECT_ACK pd = 8 callref = 0x37
4d00h: BR0:1 PPP: Phase is AUTHENTICATING, by both
4d00h: BR0:1 CHAP: O CHALLENGE id 98 len 27 from &quot;REMOTE_SITE&quot;
4d00h: ISDN BR0: RX <- RRr sapi = 0 tei = 116 nr = 41
4d00h: BR0:1 CHAP: I CHALLENGE id 185 len 27 from &quot;CENTRAL_SITE&quot;
4d00h: BR0:1 CHAP: O RESPONSE id 185 len 27 from &quot;REMOTE_SITE&quot;
4d00h: BR0:1 CHAP: I SUCCESS id 185 len 4
4d00h: ISDN BR0: RX <- INFOc sapi = 0 tei = 116 ns = 92 nr = 41 i = 0x0801B
74508028090
4d00h: DISCONNECT pd = 8 callref = 0xB7
4d00h: Cause i = 0x8090 - Normal call clearing
4d00h: ISDN BR0: TX -> RRr sapi = 0 tei = 116 nr = 93
4d00h: %LINK-3-UPDOWN: Interface BRI0:1, changed state to down
4d00h: %DIALER-6-UNBIND: Interface BR0:1 unbound from profile Di0
4d00h: ISDN BR0: TX -> INFOc sapi = 0 tei = 116 ns = 41 nr = 93 i = 0x08013
74D
4d00h: RELEASE pd = 8 callref = 0x37
4d00h: ISDN BR0: RX <- RRr sapi = 0 tei = 116 nr = 42
4d00h: ISDN BR0: RX <- INFOc sapi = 0 tei = 116 ns = 93 nr = 42 i = 0x0801B
75A
4d00h: RELEASE_COMP pd = 8 callref = 0xB7
4d00h: ISDN BR0: TX -> RRr sapi = 0 tei = 116 nr = 94
4d00h: ISDN BR0: TX -> INFOc sapi = 0 tei = 116 ns = 42 nr = 94 i = 0x08013
80504028890180183700C803031343533353231303538
4d00h: SETUP pd = 8 callref = 0x38
4d00h: Bearer Capability i = 0x8890
4d00h: Channel ID i = 0x83
4d00h: Called Party Number i = 0x80, '01234567890'
4d00h: ISDN BR0: RX <- RRr sapi = 0 tei = 116 nr = 43
4d00h: ISDN BR0: RX <- INFOc sapi = 0 tei = 116 ns = 94 nr = 43 i = 0x0801B
802180189
4d00h: CALL_PROC pd = 8 callref = 0xB8
4d00h: Channel ID i = 0x89
4d00h: ISDN BR0: TX -> RRr sapi = 0 tei = 116 nr = 95
4d00h: ISDN BR0: RX <- INFOc sapi = 0 tei = 116 ns = 95 nr = 43 i = 0x0801B
807
4d00h: CONNECT pd = 8 callref = 0xB8
4d00h: ISDN BR0: TX -> RRr sapi = 0 tei = 116 nr = 96
4d00h: %LINK-3-UPDOWN: Interface BRI0:1, changed state to up
4d00h: %DIALER-6-BIND: Interface BR0:1 bound to profile Di0
4d00h: %ISDN-6-CONNECT: Interface BRI0:1 is now connected to 01234567890
4d00h: BR0:1 PPP: Treating connection as a callout
4d00h: ISDN BR0: TX -> INFOc sapi = 0 tei = 116 ns = 43 nr = 96 i = 0x08013
80F
4d00h: CONNECT_ACK pd = 8 callref = 0x38
4d00h: BR0:1 PPP: Phase is AUTHENTICATING, by both
4d00h: BR0:1 CHAP: O CHALLENGE id 99 len 27 from &quot;REMOTE_SITE&quot;
4d00h: ISDN BR0: RX <- RRr sapi = 0 tei = 116 nr = 44
4d00h: BR0:1 CHAP: I CHALLENGE id 186 len 27 from &quot;CENTRAL_SITE&quot;
4d00h: BR0:1 CHAP: O RESPONSE id 186 len 27 from &quot;REMOTE_SITE&quot;
4d00h: BR0:1 CHAP: I SUCCESS id 186 len 4
4d00h: ISDN BR0: RX <- INFOc sapi = 0 tei = 116 ns = 96 nr = 44 i = 0x0801B
84508028090
4d00h: DISCONNECT pd = 8 callref = 0xB8
4d00h: Cause i = 0x8090 - Normal call clearing
4d00h: ISDN BR0: TX -> RRr sapi = 0 tei = 116 nr = 97
4d00h: %LINK-3-UPDOWN: Interface BRI0:1, changed state to down
4d00h: %DIALER-6-UNBIND: Interface BR0:1 unbound from profile Di0
4d00h: ISDN BR0: TX -> INFOc sapi = 0 tei = 116 ns = 44 nr = 97 i = 0x08013
84D
4d00h: RELEASE pd = 8 callref = 0x38
4d00h: ISDN BR0: RX <- RRr sapi = 0 tei = 116 nr = 45
4d00h: ISDN BR0: RX <- INFOc sapi = 0 tei = 116 ns = 97 nr = 45 i = 0x0801B
85A
4d00h: RELEASE_COMP pd = 8 callref = 0xB8
4d00h: ISDN BR0: TX -> RRr sapi = 0 tei = 116 nr = 98
4d00h: ISDN BR0: TX -> INFOc sapi = 0 tei = 116 ns = 45 nr = 98 i = 0x08013
90504028890180183700C803031343533353231303538
4d00h: SETUP pd = 8 callref = 0x39
4d00h: Bearer Capability i = 0x8890
4d00h: Channel ID i = 0x83
4d00h: Called Party Number i = 0x80, '01234567890'
4d00h: ISDN BR0: RX <- RRr sapi = 0 tei = 116 nr = 46
4d00h: ISDN BR0: RX <- INFOc sapi = 0 tei = 116 ns = 98 nr = 46 i = 0x0801B
902180189
4d00h: CALL_PROC pd = 8 callref = 0xB9
4d00h: Channel ID i = 0x89
4d00h: ISDN BR0: TX -> RRr sapi = 0 tei = 116 nr = 99
4d00h: ISDN BR0: RX <- INFOc sapi = 0 tei = 116 ns = 99 nr = 46 i = 0x0801B
907
4d00h: CONNECT pd = 8 callref = 0xB9
4d00h: ISDN BR0: TX -> RRr sapi = 0 tei = 116 nr = 100
4d00h: %LINK-3-UPDOWN: Interface BRI0:1, changed state to up
4d00h: %DIALER-6-BIND: Interface BR0:1 bound to profile Di0
4d00h: %ISDN-6-CONNECT: Interface BRI0:1 is now connected to 01234567890
4d00h: BR0:1 PPP: Treating connection as a callout
4d00h: ISDN BR0: TX -> INFOc sapi = 0 tei = 116 ns = 46 nr = 100 i = 0x0801
390F
4d00h: CONNECT_ACK pd = 8 callref = 0x39
4d00h: BR0:1 PPP: Phase is AUTHENTICATING, by both
4d00h: BR0:1 CHAP: O CHALLENGE id 100 len 27 from &quot;REMOTE_SITE&quot;
4d00h: ISDN BR0: RX <- RRr sapi = 0 tei = 116 nr = 47
4d00h: BR0:1 CHAP: I CHALLENGE id 187 len 27 from &quot;CENTRAL_SITE&quot;
4d00h: BR0:1 CHAP: O RESPONSE id 187 len 27 from &quot;REMOTE_SITE&quot;
4d00h: BR0:1 CHAP: I SUCCESS id 187 len 4
4d00h: ISDN BR0: RX <- INFOc sapi = 0 tei = 116 ns = 100 nr = 47 i = 0x0801
B94508028090
4d00h: DISCONNECT pd = 8 callref = 0xB9
4d00h: Cause i = 0x8090 - Normal call clearing
4d00h: ISDN BR0: TX -> RRr sapi = 0 tei = 116 nr = 101
4d00h: %LINK-3-UPDOWN: Interface BRI0:1, changed state to down
4d00h: %DIALER-6-UNBIND: Interface BR0:1 unbound from profile Di0
4d00h: ISDN BR0: TX -> INFOc sapi = 0 tei = 116 ns = 47 nr = 101 i = 0x0801
394D

 
9 times out of 10 its a CHAP issue. Attempt a connection again and try these commands:

undebug all ** clear out running debug commands
term mon ** if not already on
debug ppp authentication ** debug for chap authentication

Look for anything that points to chap failure. If so re-enter the username and password on both routers. Keep the password the same on both routers.

 
Apologies, I'll read the threads more carefully next time!

I can see your authentication is working, ISDN has a tei assigned within the correct range, i.e. BT's end looks okay.

Your config looks okay, at least there seems to be nothing that would prevent your remote-site performing outbound-dialling. Sometimes, ppp multilink can cause issues with some IOS. Try dialling out without these commands on, or with them but reload first.

What IOS version are you using? 'show version' command.
 
IOS 12.0(17a) on 1603's and 12.1(9) on th3 2620.

This is really confusing the heck out of me now!!

oh, I have tried without the ppp multilink with no luck.

To recap:

1603's connected to ISDN2e service

2620 connect to ISDN2e service with separate numbers for each 64K channel

Help!!!
 
I've been playing with the configs some more to no avail:

Latest versions of both are here:


!
version 12.1
service timestamps debug uptime
service timestamps log uptime
no service password-encryption
!
hostname CENTRAL
!
logging buffered 4096 debugging
enable password 7 password
!
username REMOTE_1 password 0 password
username REMOTE_2 password 0 password
!
!
!
!
ip subnet-zero
ip name-server 212.104.129.9
ip name-server 212.104.129.65
!
isdn switch-type basic-net3
isdn voice-call-failure 0
!
!
!
interface FastEthernet0/0
description Physical Connection to CENTRAL LAN
ip address 192.0.100.1 255.255.255.0
ip nat inside
no ip route-cache
no ip mroute-cache
no keepalive
duplex auto
speed auto
!
interface BRI0/0
description Physical Connection to REMOTE_1
no ip address
encapsulation ppp
dialer pool-member 1
isdn switch-type basic-net3
ppp authentication chap pap callin
!
interface BRI0/1
description Physical Connection to REMOTE_2
no ip address
encapsulation ppp
dialer pool-member 1
isdn switch-type basic-net3
ppp authentication chap pap callin
!
interface Dialer1
description Logical ISDN Connection to REMOTE_1
ip unnumbered FastEthernet0/0
ip nat inside
encapsulation ppp
dialer pool 1
dialer idle-timeout 300
dialer string xxxxxxxxxxx
dialer-group 1
no cdp enable
ppp authentication chap
!
interface Dialer2
description Logical ISDN Connection to REMOTE_2
ip unnumbered FastEthernet0/0
ip nat inside
encapsulation ppp
dialer pool 1
dialer idle-timeout 300
dialer string xxxxxxxxxxx
dialer load-threshold 200 either
dialer-group 1
no cdp enable
ppp authentication chap
ppp multilink
!
ip classless
ip route 0.0.0.0 0.0.0.0 192.0.100.9
ip route 192.0.110.0 255.255.255.0 Dialer1
ip route 192.0.120.0 255.255.255.0 Dialer2
no ip http server
!
access-list 1 permit 192.0.100.0 0.0.0.255
access-list 1 permit 192.0.110.0 0.0.0.255
access-list 1 permit 192.0.120.0 0.0.0.255
dialer-list 1 protocol ip permit
!
line con 0
exec-timeout 0 0
password 7 password
login
line aux 0
line vty 0 4
exec-timeout 30 0
password 7 password
login
!
end

---------------------------------------------------------


!
version 12.0
service timestamps debug uptime
service timestamps log uptime
no service password-encryption
!
hostname REMOTE_1
!
enable password 7 password
!
username CENTRAL password 0 password
ip subnet-zero
isdn switch-type basic-net3
!
!
!
interface Ethernet0
ip address 192.0.110.1 255.255.255.0
no ip directed-broadcast
!
interface BRI0
no ip address
no ip directed-broadcast
encapsulation ppp
dialer pool-member 1
isdn switch-type basic-net3
isdn send-alerting
ppp authentication chap
!
interface Dialer0
description ISDN Connection to CENTRAL
ip unnumbered Ethernet0
no ip directed-broadcast
encapsulation ppp
dialer remote-name CENTRAL
dialer string xxxxxxxxxxx
dialer pool 1
dialer-group 1
ppp authentication chap
!
no ip classless
ip route 0.0.0.0 0.0.0.0 Dialer0
ip route 192.0.100.0 255.255.255.0 Dialer0
ip route 192.0.120.0 255.255.255.0 Dialer0
!
dialer-list 1 protocol ip permit
!
line con 0
password 7 password
transport input none
line vty 0 4
exec-timeout 30 0
password 7 password
login
!
end
 
Correct me if I'm wrong, but should not the ISDN interface/ISDN dialer interface be NAT OUTSIDE.. not NAT INSIDE? You already have NAT INSIDE on the ethernet interface..which is correct but show NAT INSIDE on the ISDN dialer.

see this sample:

:::snip::
interface Ethernet0
description connected to EthernetLAN
ip address 192.168.46.3 255.255.255.0
ip nat inside
!
interface BRI0
description connected to Internet
no ip address
ip nat outside
encapsulation ppp
dialer rotary-group 1
isdn switch-type basic-net3
compress stac
no cdp enable
!
interface Dialer1
description connected to Internet
ip address negotiated
ip nat outside
ip access-group 121 in
encapsulation ppp
no ip split-horizon
dialer in-band
dialer idle-timeout 30
dialer string 96304900
dialer hold-queue 10
dialer-group 1
compress stac
no cdp enable
ppp authentication chap pap callin
ppp chap hostname 1201xxxxxxxx
ppp chap password 7 hemlinemli
ppp pap sent-username 1201xxxxxxxx password 7 hemlinemli
!
no router rip
::snip::


MikeS Find me at
&quot;Take advantage of the enemy's unreadiness, make your way by unexpected routes, and attack unguarded spots.&quot;
Sun Tzu
 
Everything dialed from the 2620 IS inside, the link to the internet is from 192.0.100.9

Mike.
 
Most likely a long distance carrier issue.

I'll beat dollars to donuts that the remote sites do not have a long distance carrier assigned but the main site does.

I had a problem very simular to this.

The main site could dial to the remote site and bring up a ppp session. But the remote site could not dial the main site.

LONG DISTANCE CARRIER, call your carrier and ask.

cheers



-Danny
dan@snoboarder.net






 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top