Thats a good question ?I have mine confiqured as DiD and they work both ways

Ramjet

I program my pri trunks as DID and 3vce, and it works very well.

jack

Depends what the design intent is. I've got a combination of Tie & DID's configured. Explain your requirements in more detail to recieve a better answer.

Jack

pbxn

The PRI is for a VRU type server. I tried using TIE, and I can get the B-CH's up but not the DCH. WHen I enabled the loop, the DCH comes back Disabled Reason 85 and 86, any thoughts? THis is one major PITA

pbxn

Well I have since tried programming it as a DID with VOD, and have seen the same result, the b-channels are up and idle, but the D-channel won't even try to establish, it keeps scrolling
DCH: 9 DISABLE INDICATION TIME: 19:15:26
REASON - **(00000086)
Any ideas, thanks for the help

keith

All of mine are prog as RDC.
never had any probs

slagburn

It almost seems more like a hardware problem or a hardware / software conflict since the DCH won't even stay enabled. From what I've seen in the past the DCH programming might not match the distant end but it won't disable it just won't establish. I can't find any info on the reason codes hopefully someone on here has a reference.

freddog

Slag's suspicions are correct. I've experienced the same exact problem with a D-channel (DCH: x DISABLE INDICATION TIME: hh:mm:ss
REASON - **(00000086)), on a newly built PRI, and it was some sort of harware/software problem with the MSDL card. In order to bring the D-channel up, I had to disable everything built on the MSDL card that the D-channel was on, disable the MSDL card and then reseat it. Once the MSDL card was enabled again, the D-channel came right up.

aldon

Not to be silly, but did you make sure the equipment on the other end is really expecting a D Channel? I set mine up as TIE, VCE