AS5300 PRIs - 24th call failing

Unanswered Question
Feb 13th, 2008

I have an AS5300 with 4 PRIs terminated into it configured with NFAS. The other end of these PRI is to a MetaSwitch. Dial-up users through the MetaSwitch down the PRIs are working fine untill all B-channels are full on the primary PRI. The next call (24th) gets a busy. I have disconnected the primary PRI and had the users come down the 2nd PRI and the problem follows. So the PRIs are operational, I just can't get that 24th call to roll to the next PRI. Debug as follows on the 24th call:


Feb 13 18:51:11: ISDN Se1:23: RX <- SETUP pd = 8 callref = 0x6701

Feb 13 18:51:11: Bearer Capability i = 0x8090A2

Feb 13 18:51:11: Channel ID i = 0xE9878301

Feb 13 18:51:11: Progress Ind i = 0x8481 - Call not end-to-end ISDN, may have in-band info

Feb 13 18:51:11: Called Party Number i = 0xC1, 'XXXXXXX', Plan:ISDN, Type:Subscriber(local)

Feb 13 18:51:11: Original Called Number i = 0x21000F81, 'XXXXXXXXXX'

Feb 13 18:51:11: ISDN Se1:23: TX -> RELEASE_COMP pd = 8 callref = 0xE701

Feb 13 18:51:11: Cause i = 0x80E418 - Invalid information element contents



  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
Paolo Bevilacqua Wed, 02/13/2008 - 11:48

Hi, what is the nfas config you have on the as5300 ? And how many d-channels you have ?

For example, if you have only one D-channel on the primary pri, bringing it down should make impossible to call, as there is no d-chan anymore.

In this sense it can be easier to just forget about nfas and just run regular pri over all circuits.


johnnywan Wed, 02/13/2008 - 11:53

I have a primary and secondary D channel that are functioning as expecting. I can bring the primary NFAS D channel down and the second takes over. No D channels on PRI 3 and 4 they are using pri and sec of PRI 1 and 2.

Paolo Bevilacqua Wed, 02/13/2008 - 12:01

Can you post nfas-relevant config for the 5300.

I haven't decoded the nfas channel id, but that's a track.

johnnywan Wed, 02/13/2008 - 12:04

!

controller T1 0

framing esf

clock source line primary

linecode b8zs

cablelength short 133

pri-group timeslots 1-24 nfas_d primary nfas_int 0 nfas_group 2

!

controller T1 1

framing esf

clock source line secondary 1

linecode b8zs

cablelength short 133

pri-group timeslots 1-24 nfas_d backup nfas_int 1 nfas_group 2

!

controller T1 2

framing esf

clock source line secondary 2

linecode b8zs

cablelength short 133

pri-group timeslots 1-24 nfas_d none nfas_int 2 nfas_group 2

!

controller T1 3

framing esf

clock source line secondary 3

linecode b8zs

cablelength short 133

pri-group timeslots 1-24 nfas_d none nfas_int 3 nfas_group 2

johnnywan Wed, 02/13/2008 - 12:07

So i only have ser0:23 configured and all other D channels inherit the 0:23 config. Do I need a dialer int to tie all the PRIs together?

Paolo Bevilacqua Wed, 02/13/2008 - 12:14

Yes, the interfaces should all go into the same dialer pool and the dialer has all the config.

johnnywan Wed, 02/13/2008 - 12:19

Here is the dialer i configured. i applied this to ser0:23 as follows


interface Dialer1

ip unnumbered FastEthernet0

encapsulation ppp

no ip mroute-cache

dialer in-band

dialer idle-timeout 3600

dialer-group 1

peer default ip address pool AS5300-1

no fair-queue

no cdp enable

ppp authentication pap callin

ppp multilink


interface Serial0:23

no ip address

encapsulation ppp

dialer rotary-group 1

dialer-group 1

isdn switch-type primary-dms100

isdn incoming-voice modem

no fair-queue

no cdp enable

Paolo Bevilacqua Wed, 02/13/2008 - 13:52

Hmm I think under dialer you need dialer pool 1 and under serial you need dialer pool-member, no need for dialer-group.

Actions

This Discussion