Dial-in via PRI-interface on 3745

[matthiaseberle]

Hi,

we are trying to configure a Cisco 3745 with a 2port E1 PRI interface and 12 digital modems (NM-12DM) and 8 analog modems (NM-8AM) for remote access for telecommuters.

We didn't succeed so far.

Our config looks like:

version 12.3

service timestamps debug datetime msec

service timestamps log datetime msec

service password-encryption

!

hostname RASrouter

!

boot-start-marker

boot-end-marker

!

enable secret 5 *********

!

username test password 7 **********

aaa new-model

!

!

aaa session-id common

no ip subnet-zero

ip cef

!

!

!

no ip domain lookup

ip name-server 10.10.1.1

no ftp-server write-enable

isdn switch-type primary-net5

!

!

!

controller E1 1/0

pri-group timeslots 1-31

!

controller E1 1/1

shutdown

!

!

interface FastEthernet0/0

ip address 10.10.0.5 255.255.0.0

duplex auto

speed auto

!

interface FastEthernet0/1

no ip address

shutdown

duplex auto

speed auto

!

interface Serial1/0:15

ip address 10.100.0.1 255.255.0.0

encapsulation ppp

autodetect encapsulation ppp

isdn switch-type primary-net5

isdn incoming-voice modem

!

interface Group-Async0

no ip address

encapsulation ppp

async mode interactive

peer default ip address pool dialin_address_pool

group-range 65 76

!

ip local pool dialin_address_pool 10.100.4.1 10.100.4.254

ip classless

ip route 0.0.0.0 0.0.0.0 10.10.0.1

ip http server

!

radius-server host 10.30.1.1 auth-port 1645 acct-port 1646

radius-server key 7 *********

!

line con 0

password 7 **********

line 65 76

modem Dialin

autoselect ppp

line aux 0

line vty 0 4

exec-timeout 15 0

password 7 **********

!

end

We haven't started the configuration of RADIUS authentication so far, since our main problem is, that we can't connect via analog or isdn to the RAS-Router.

Any suggestions from you experts?

By the way, we are in Germany (is isdn switch-type primary-net5 correct)?

Regards, maeb3

[matthiaseberle]

The router just doesn't answer the call.

Any idea, what could be the problem?

[Kevin Dorrell]

Could you please post the results of show isdn status?

If that is all OK, please do a debug isdn events and debug dialer events and try the call again, and post the results. Don't forget the term mon if you are remote.

For even more detail, try with debug isdn q921 and debug isdn q931.

Kevin Dorrell

Luxembourg

[matthiaseberle]

The ISDN status is:

RASrouter#sho isdn status

Global ISDN Switchtype = primary-net5

ISDN Serial1/0:15 interface

dsl 0, interface ISDN Switchtype = primary-net5

Layer 1 Status:

DEACTIVATED

Layer 2 Status:

TEI = 0, Ces = 1, SAPI = 0, State = TEI_ASSIGNED

Layer 3 Status:

0 Active Layer 3 Call(s)

Active dsl 0 CCBs = 0

The Free Channel Mask: 0x00000000

Number of L2 Discards = 0, L2 Session ID = 1

Total Allocated ISDN CCBs = 0

RASrouter#

The telco provider says that the connection looks fine from his side.

[Kevin Dorrell · Accepted solution]

Sorry, but it doesn't look fine to me. On mine I have Layer 1 Status is ACTIVE, and Layer 2 Status is MULTIPLE_FRAME_ESTABLISHED. It looks like a physical problem to me. I think you would get the same result if you unplugged the cable completely. But I think your config looks OK. You might try debug isdn q921 but I doubt that will tell you much if the problem is layer 1.

Kevin Dorrell

Luxembourg

[matthiaseberle]

Thank you for this information.

You also have the ISDN signalling on the serial interface on channel 16 (which is showed as channel 15 in my isdn status output above)?

Matthias Eberle

[Kevin Dorrell]

Yes, that is correct. I think it is standard under net5. At least, it is that way in every net5 installation I have seen: signalling D-channel on :15 and B-channels on :0 to :14 and :16 to :30. Remembering always that :0 is actually timeslot 1.

Over the water, they do things differently, and bundle 24 channels with :23 as the D-channel. But we do not have to worry about that here.

Kevin Dorrell

Luxembourg

Kevin Dorrell

[matthiaseberle]

Thank you.

I will continue next week.

Have a nice weekend.

Matthias Eberle

[riz_432]

i 'm damn sure there is a problem with ur pri link either physically(unplugged/lose etc..) or may be at the telco end (can u make a test call from the pri).but it is a problem at the physical layer 1 only

[matthiaseberle]

We finally got it.

Two wires of our ("self-made") RJ45 Plug were interchanged.

Thank you again.

Matthias Eberle