MCD 5.1 on CX II Controller to Touchstar Dialer PRI

[vlevalois]

Trying to get a Touchstar Predictive Dialer (Noble Systems) Dialogic PRI card in NI2 mode (confirmed, but that's all we know as of now) to use the 3300 PRI card as a C.O. connection to dial out other trunks...

The Touchstar was connected to a PRI directly to the C.O. and we're trying to simulate that on the 3300. So far, we've tried multiple combinations with no luck. Thinking that the Touchstar was in NT mode (as connected to the C.O.), we set the 3300 to LT with "A" message control in Digital Link Descriptors and programmed the Trunk Circuit Descriptors to Local Office (although also tried Toll Office). Programmed the Digital Trunks as needed, etc. ISDN set to NI2/5ESS

We get sync (blinking green light) on the link but no D channel. No matter what Digital Link Descriptor settings we've tried using (NT/LT, A/B, etc), in combination with multiple Trunk Circuit Descriptors, we can't get the D channel to link up. STATE shows all channels NOT SEIZABLE.

Any ideas?

DIGITAL LINK DESCRIPTORS

Number 1
Address for Message Control A
BER - Maintenance Limit, 10**-n 4
BER - Service Limit, 10**-n 3
Data Call Alternate Digit Inversion No
Framing Losses in 24 hrs - Maintenance Limit 255
Framing Losses in 24 hrs - Service Limit 9000
Integrated Digital Access ISDN NODE
Vendor Inter-working Type
Satellite Link Delay No
Slip Rate - Maintenance Limit (slips/24hr.) 5000
Slip Rate - Service Limit (slips/24hr.) 7000
Alarm Debounce Timer - Service Limit (millisec.) 500
Voice Encoding Nil
Data Encoding Nil
QSIG Private Network Access No
Digital Link Fault Delay Timer (sec.) 240
Termination Mode NT
Send Malicious Call Indication to PSTN for Tagged Calls No
Inhibit sending Mitel Specific Info No
T1 Only:
B8ZS Zero Code Suppression Yes
Operation Mode CSU
CSU Tx Line Build-Out (dB.) 7.5
DSX-1 Line Length (Ft.) 0-133
Extended Super Frame Yes
Inverted D channel ( DPNSS only ) No
T1-619a Signalling ( MLPP only ) No
E1 Only:
CRC-4 Enabled Yes
E1 Line Length (Ft.) 0-133
E1 Impedance (Ohms) 120

DIGITAL LINKS
Interface Type UNIVERSAL T1

TRUNK CIRCUIT DESCRIPTORS
Csrd Type: UNIVERSAL T1
Dual Seizure Priority: Incoming
Far end Connection: Local Office (have also tried Toll Office)
Signaling Protocol: MSDN-DPNSS

ISDN Protocol:
NI2/5ESS

 

[kwbMitel]

You havent mentioned making a crossover cable

Some people mistakenly use Ethernet crossover cables which flip pairs 2 and 3

You will probably need a voice crossover cable which flips pairs 1 and 3

Normal cable
-- Wht/grn
-- grn/wht
-- wht/ora
-- blu/wht
-- wht/blu
-- ora/wht
-- wht/brn
-- brn/wht

Voice Crossover
-- wht/blu
-- blu/wht
-- dont care
-- grn/wht
-- wht/grn
-- dont care
-- dont care
-- dont care


**********************************************
What's most important is that you realise ... There is no spoon.

 

[vlevalois]

It wasn't a cross-over cable issue in the end or anything to do with the PRI settings really... it was the "Dial In Trunks Incoming Digit Modification - Absorb" field in the Trunk Attributes form. It was not set to any value and it must be set, otherwise the digits received by the MCD will not go back out correctly. We set it to 0 and it started working.

 

[kwbMitel]

That'll Cause issues for sure, but I think your description was off. I doubt that field would prevent D-Channel Sync.

**********************************************
What's most important is that you realise ... There is no spoon.

 

[vlevalois]

Possibly. We tried so many different options, I can't recall which stuck in the end between the dialer and the MCD. However, it was that setting that finally resolved it. Neat application, we have vMCD in Mitel's IaaS connected to SIP trunks. MPLS from the IaaS to the customer prem with a CX hooked up to the dialer via T1/PRI simulating the C.O. When the dialer calls out it's going through the MPLS and out through SIP trunks.