Embedded Quad BRI

[JamesFearn]

Hi all,

This is probably a question for the UK based chaps as I believe Basic Rate ISDN 2 isn't as popular in the US but all input is most welcome.

I have a 3300 MXeII on MCD 4.1 with an Embedded Quad BRI card I am struggling to configure. I have followed the programming instructions on the 3300 help files but still have no joy in connecting them to our ISDN2 circuit.

With all the programming complete as per the help guide when I connect the ISDN the log files show "ISDN D Channel Forced DOWN" and I am unable to dial in or out (obviously). When dialling and perfoming a CCS Trace I am getting a congested route error (again I assume because of no D Channel).

Is anyone an ISDN2 guru? Can anyone point me in the right direction please?

The ISDN circuit is fine, I have a Siemens OpenOffice that I used to use on it and she works well.

Thanks all, Jimmy.

 

[tlpeter]

Hi Jimmy, it is a long time ago for me but can you post the settings?
I really cannot recall any of those settings at the moment but maybe i know it again after i see it

BAZINGA!

I'm not insane, my mother had me tested!

 

[bobcheese]

if you run ccs trace do you see incomming calls hit the switch before being rejected?

 

[JamesFearn]

Thanks for your responses guys.

The following are the settins for my trunks. I have included an outgoing trace. Incoming traces don't see the call so I am guessing the ISDN settings are incorrect.

Thanks

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

Outgoing Trace:

CCS Tracing is enabled for continuous output display
12:02:33 RO101 DPN 23 ISRM_I ;10;*1#*50*1000#*100*J.Fearn*1#*19*Z#
12:02:33 RO101 DPN 2D SSRM_I *58*CW*{M|k@@@@@@@ZzP#*58*C6*001#*58*C4*4*1#
12:02:33 RO101 DPN 4 SSRM_C 123
12:02:33 RI101 DPN 7 NIM *51*3#
12:02:40 RI101 DPN 6 CRM/CIM ;7;*58#

 

[Jakt99]

When I have experienced issues implementing BRIs, generally its to do with ISDN protocol form (your gutt feeling), with setting of point to point or point to multi-point.

If you service is has an indial facility, it nust be set to point to point (Meaning only one device attached to the ST bus).

Where no in-dial service it can be either, depending on telco and exchange equipment.

If you change above make sure you reload the quad bri module at the maint command prompt. "reload plid number". This will ensure the config is loaded cleanly (the module will be out of service for a short period)

 

[JamesFearn]

Thanks Jakt99,

I have been playing with the point-to-point / multi-point and no joy so far although I do think I will wipe the slate clean and start the trunk configuration from scratch.

I'll let you know how I get on.

Thanks

 

[Supernova99]

you need to set manual TEI to yes

Share what you know - Learn what you don't

 

[JamesFearn]

Supernova99 - Many thanks, changed the TEI value to yes and all is fine.

Thanks for all your help guys.

Jimmy