Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Community Member

ISDN dial problem from Cisco Router 1751V to 2620-XM

Pls see below scenario

One Cisco 2620-XM router with IOS 12.2T & Cisco 1751V router with IOS 12.3T.

Now Cisco 2620 router is dialing BRI interface of Cisco 1751 Router & call is perfectly established & Data is processed in both way. But if dialer string is removed from 2620 router & dial happens through 1751. Call doesn't establish even after many trys it appears in ISDN history as called failed. Could you suggest what?s wrong here? Awaiting reply

you can look the command below on both Cisco 2620 & Cisco 1751V routers.

Cisco 2620-XM

!

Interface BRI 1/1

ip address 172.17.1.1 255.255.255.252

encapsulation ppp

dialer string 0145234569

dialer idle-timeout 1500

dialer-group 1

!

Cisco 1751V

!

Interface BRI 0/0

ip address 172.17.1.2 255.255.255.252

encapsulation ppp

dialer string 01122965748

dialer idle-timeout 1500

dialer-group 1

!

3 REPLIES

Re: ISDN dial problem from Cisco Router 1751V to 2620-XM

Is the 1751 router really making an outgoing call?

Can you see that the incoming call is received on the 2620?

If not, you most like have an incorrect phone number.

There is too little info in your post to verify other configuration issues.

Regards,

Leo

Community Member

Re: ISDN dial problem from Cisco Router 1751V to 2620-XM

Router 1751 is not able to make outgoing call. That?s my main concern. Phone number is perfectly correct. It?s the same Phone no that dials Cisco 1751 & make successful data cal. So could you give any other suggestion Can it be IOS issue of 2620? Waiting reply.

Re: ISDN dial problem from Cisco Router 1751V to 2620-XM

You can use the "debug dialer" command to see if a call attempt is made. Appearently this is not happening in one direction.

In that case, you should check your dialer group & dialer list. This must contain the destination ip adress?

You should also check for correct ip routing via the dialer.

Do you have any ppp authentication running?

When you are using pap, this could also be the problem but a call attempt is then made so this is less likely.

Regards,

Leo

146
Views
0
Helpful
3
Replies
CreatePlease to create content