ISDN-BRI configuration

[EPalle]

Hi all,

I have the problem that calls over the BRI trunks are dropped (in random order).
When an Avaya Call (call made from Avaya station) is dropped we only see "idle station xxxx" in the trace.
When an Office Communicator call is dropped we see a denial event "2307: TDM resource blockage D1=0xb1 D2=0x0".

I have 2 sites using BRI trunks and they have the same issue.
I have 1 site that has a PRI and that works well.

Please find below the configuration of the BRI trunk:

Group Number: 5 Group Type: isdn CDR Reports: y
Group Name: Belgacom Mechelen COR: 7 TN: 1 TAC: 9005
Direction: two-way Outgoing Display? n Carrier Medium: PRI/BRI
Dial Access? y 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


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: a Digit Handling (in/out): enbloc/enbloc

Trunk Hunt: cyclical
Digital Loss Group: 13
Incoming Calling Number - Delete: Insert: Format: intl-pub
Bit Rate: 1200 Synchronization: async Duplex: full
Disconnect Supervision - In? y Out? n
Answer Supervision Timeout: 0
Administer Timers? n CONNECT Reliable When Call Leaves ISDN? n


TRUNK FEATURES
ACA Assignment? n Measured: internal Wideband Support? n
Maintenance Tests? y
Data Restriction? n NCA-TSC Trunk Member:
Send Name: n 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? n
Replace Unavailable Numbers? n
Send Connected Number: n
Network Call Redirection: none Hold/Unhold Notifications? n
Send UUI IE? y Modify Tandem Calling Number? n
Send UCID? n
Send Codeset 6/7 LAI IE? y Ds1 Echo Cancellation? n

Apply Local Ringback? n US NI Delayed Calling Name Update? 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/13
GROUP MEMBER ASSIGNMENTS Total Administered Members: 10

Port Code Sfx Name Night Sig Grp
1: 003V701 MM720
2: 003V702 MM720
3: 003V703 MM720
4: 003V704 MM720
5: 003V705 MM720
6:
7:
8:
9: 003V717 MM720
10: 003V718 MM720
11: 003V719 MM720
12: 003V720 MM720
13: 003V721 MM720
14:
15:


And the BRI trunk board config:
ISDN-BRI TRUNK CIRCUIT PACK

Location: 003V7 Name: BC-Mecelen
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 Layer 1 Detect
Protocol Protocol CCBS Stable? Slips?
1: user etsi 0 none y n
2: user etsi 0 none y n
3: user etsi 0 none y n
4: user etsi 0 none y n
5: user etsi 0 none y n
6: user etsi 0 none y n
7: 0 none y n
8: 0 none 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:


For the good order:
Country: Belgium
Provider: Belgacom
CM: 5.1.2
CPU: S8300C with 3 G450 gateways (2 are remote)

Is there something that is faulty??
I don't think it is a line problem as both sites have the same issue (both sites are miles away from each other and in a different zone).

Thanks,
Erik

 

[Smovk]

Hi,

Have you resolved this issue, because one of our customers is having the same issue. They gave CM 5.2.1 G700 S8300 on main location and G350 s8300lsp on remote location.

Regards,
Smovk

 

[EPalle]

Hi Smovk,

Yes, we found the issue...... network.
The network was not configured as should (although the network guys always said that everything was OK).
Once that was changed the system started working as expected (make sure all ports are dedicated 100Mb Full duplex on both sides - PBX and switch - stay away from AutoSense).

Not sure it will help you.

Regards,
E.

 

[Rudman]

Hi
I have got the same problem with the BRI ports did you come right with your fault?
Mark Rudman

 

[EPalle]

Hi Rudman,

Yes, it did. We changed the port settings of the Avaya Gateways (local and remote), the WAN router (both end) and basically every port that had a voice server connected to it.
Make sure they their speed is fixed on the port (in our case "100 Mbps Full Duplex").

If some ports are in AutoSense it is possible that they are in half duplex while the Avaya device is in Full Duplex mode. And that gives ofcourse issues. Plus that you have no idea on what speed the port is actually running at. All Avaya servers/gateways are set fixed to 100/Full Duplex. So best is to make sure the ports on the switch are running in that mode as well.

Again, don't know if this will fix your issue but maybe something to look at.

Regards,
Erik