3300 MXe2 Quad BRI

[Jimmy Fearn]

Hello all, first time I've used the forum so I'd better introduce myself.

I'm Jimmy. I work for a comms company over in the UK and specialise mostly in networking (Cisco and HP). My background was mostly TDM telephone systems (Samsung and Siemens) but recently I have been pushed into the Mitel world which I am enjoying very much.....until today!

I have a Mitel MXe2 running MCD 4.1SP2. Active software load 10.1.2.16.

I am struggling with the installation of an Embedded Quad BRI. I have read through the online help files and, as far as I am aware, configured the card correctly. When I patch in to the BRI Interface I get green light on constant. Basically the error I am getting is that whenever I dial out I am getting a busy notification. I have done a CCS trace and am getting the following (123 being the speaking clock in the UK).

11:17:17 RO100 DPN 23 ISRM_I  ;10;*1#*50*1000#*100*J.Fearn*1#*19*Z#             
11:17:17 RO100 DPN 2D SSRM_I  *58*CW*{M|k@@@@@@Dsa@#*58*C6*001#*58*C4*4*1#     
11:17:17 RO100 DPN 4  SSRM_C  123                                               
11:17:17 RI100 DPN 7  NIM     *51*3#                                           
11:17:23 RI100 DPN 6  CRM/CIM ;7;*58#                                           

Incoming calls are cutting off before getting to the system. I have noticed in the logs that the D Channel is forced down also which is obviosly why I can't get a trunk.

Can anyone point me in the right direction as to a possible cause?

The ISDN circuit is fine as I can put another system (Siemens HiPath Open Office) on and it works fine.

Thanks all,

Jimmy

[MitelUK2010]

Green is busy, I had same issue. I assumed green would be idle. It should be red until processing calls

[bobcheese]

system must be seing the ISDN as it is trying to send out to line (if circuits where down then you wouldnt see it on CCS trace). What happens on ICC? do you see on CCS trace? Maybe something to do with the protocol used, as the BRI trunks P-P or P-MP?

[Jimmy Fearn]

Hi chaps, thanks for your input.

Green being busy makes sense from what I am seeing. For ICC's there is no information present in CCS Trace diagnostics.

Config of the system is as follows:

Programming as per Mitel System Admin Tool Help:

Hardware and Trunk Config:
Controller Module Configuration form has Quad BRI Programmed

Framers / Quad BRI Framers form is programmed as "Unit 2"

Digital Link Descriptors form programmed Number 1, Address for Message Control B, BER Maintenance 4, BER Service 3, Integrated Digital Access BRI NODE

Digital Links form Controller Module 3 Ports 1&2 using Digital Link Descriptor 1

MSDN-DPNSS-DASSII Trunk form programmed as Number 1, Card Type BRI, Far End Connection Local Office

Trunk Attributes form programmed as Trunk Service Number 1, COS 96 (COS Programmed for Access via DPNSS and Public Trunk), Digit Absorb 0 (all other settings as default).

Digital Trunks form Cab 2 Shelf 1 Slot 2 Circuit 1 and 2 have trunk numbers 101 and 102 with Trunk Service Number 1, Circuit Descriptor Number 1, Interconnect Number 1 and Tennant Number 1

Trunk Group form Trunk Group Number 1 with members 101 and 102

ISDN Protocol form left default (I have a feeling if there is a configuration problem it will be here!)

ARS configured to use Trunk Group 1

Is there any documentation on what UK BRI settings should be for the 3300?

Thanks again.

[Jimmy Fearn]

Hi all,

Just an update on this. The solution to this lies in the ISDN Protocol section. For BRI you need to set the Manual TEI Value to yes. The values themselves can remain at 0. Once this is done the trunks work fine. Hope this can be of help to someone in the future!

Jimmy