BRI Trunk Bouncing

[danparrish]

Hi, I wonder if anyone can point me in the right direction, I have a 2x BRI lines on 2 different trunks, and they are constantly bouncing, when I monitor the BRI's via the gateway, I see link up on all, then at exactly the same time, both BRI's see "Recovery" on the D-Channel and then drop.

the Strange thing is, if I establish a call over one of the BRI's the line remains open and never drops, but the other BRI does drop.

I have swapped reset and swapped the BRI card that they are connected to, and have had multiple configurations on the BRI and trunk, but cannot seem to work this out, I am hoping that the call being established that holds keeps the BRI line open will somehow help investigate.


------------------------------------------
Self Taught Genius!!

 

[danparrish]

Hoping some has managed to check this.

As an update, the same BRI's were connected to a Cisco router and it seemed they remained stable....

BRI Board;
ISDN-BRI TRUNK CIRCUIT PACK

Location: 003V6 Name: Milano RFPD
Interface Companding: a-law DCP/Analog Bearer Capability: 3.1kHz
T3 Timer Length (sec): 15 Termination Type: TE

Port Interface Side Cntry/Peer TEI TSC SS ETSI Synch Layer 1 Detect
Protocol Protocol CCBS Source? Stable? Slips?
1: user etsi 0 none n y n
2: user etsi 0 none n y n
3: 0 none n y n
4: 0 none n y n
5: 0 none n y n
6: 0 none n y n
7: 0 none n y n
8: 0 none n y n


ISDN-BRI TRUNK CIRCUIT PACK

Port Interwork XID Endpt SPID Endpt SPID Endpt Max
Message Test? Init? ID ID NCA TSC
1: PROGress n n 0
2: PROGress n n 0
3: PROGress n n 0
4: PROGress n n 0
5: PROGress n n 0
6: PROGress n n 0
7: PROGress n n 0
8: PROGress n n 0


Port Directory Directory Port Directory Directory
Number Number Number Number
1: 5:
2: 6:
3: 7:
4: 8:

Trunk Group

display trunk-group 1009 Page 1 of 21
TRUNK GROUP

Group Number: 1009 Group Type: isdn CDR Reports: y
Group Name: BRI-Main RFPD COR: 95 TN: 24 TAC: *828
Direction: two-way Outgoing Display? y Carrier Medium: PRI/BRI
Dial Access? n Busy Threshold: 255 Night Service:
Queue Length: 0
Service Type: public-ntwrk Auth Code? n TestCall ITC: rest
Far End Test Line No:
TestCall BCC: 4


Group Type: isdn

TRUNK PARAMETERS
Codeset to Send Display: 6 Codeset to Send National IEs: 6
Max Message Size to Send: 260 Charge Advice: none
Supplementary Service Protocol: c Digit Handling (in/out): overlap/overlap
Digit Treatment: insertion Digits: 0*
Trunk Hunt: cyclical
Digital Loss Group: 13
Incoming Calling Number - Delete: Insert: 0 Format:
Bit Rate: 1200 Synchronization: async Duplex: full
Disconnect Supervision - In? y Out? y
Answer Supervision Timeout: 0
Administer Timers? n CONNECT Reliable When Call Leaves ISDN? n
XOIP Treatment: auto Delay Call Setup When Accessed Via IGAR? n
CPN to Send for Redirected Calls: calling





TRUNK FEATURES
ACA Assignment? n Measured: none Wideband Support? n
Maintenance Tests? y
Data Restriction? n NCA-TSC Trunk Member:
Send Name: y Send Calling Number: y
Used for DCS? n Send EMU Visitor CPN? n
Suppress # Outpulsing? n Format: public
Outgoing Channel ID Encoding: preferred UUI IE Treatment: service-provider

Replace Restricted Numbers? y
Replace Unavailable Numbers? y
Send Connected Number: y
Network Call Redirection: none Hold/Unhold Notifications? n
Send UUI IE? y Modify Tandem Calling Number: no
Send UCID? n
Send Codeset 6/7 LAI IE? y Ds1 Echo Cancellation? n

Apply Local Ringback? n
Show ANSWERED BY on Display? y
Network (Japan) Needs Connect Before Disconnect? n

QSIG TRUNK GROUP OPTIONS









SBS? n


QSIG Value-Added? n






TRUNK GROUP
Administered Members (min/max): 1/2
GROUP MEMBER ASSIGNMENTS Total Administered Members: 2

Port Code Sfx Name Night Sig Grp
1: 003V602 MM720 X
2: 003V618 MM720 X
3:













------------------------------------------
Self Taught Genius!!

 

[smokinjoe2938]

turn off maintenance test and see if this resolves the issue

acss sme acis sme acss cm 5.2.1 acss cm and cmm acss aura messaging.

 

[danparrish]

unfortunately, the problem remains;


LOCATION TERMINATION ID TYPE LINK ID DLCI SIDE STATE
--------- -------------- ------- ---------- ---------- ----- ------------
v6 0x000000002820 BRI_BC 0x002003 0x00007F A Link Up
v6 0x000000002820 BRI_BC 0x004003 0x001FFF A Link Up
v6 0x000000002820 BRI_TRK 0x00000C 0x000048 A Recovery
v6 0x000000002821 BRI_BC 0x002004 0x00007F A Link Up
v6 0x000000002821 BRI_BC 0x004004 0x001FFF A Link Up
v6 0x000000002821 BRI_TRK 0x00000D 0x00006C A Recovery



------------------------------------------
Self Taught Genius!!

 

[danparrish]

The solution was to switch of Layer One Stability on the BRI config. All working good now.


------------------------------------------
Self Taught Genius!!