Mitel Forums - The Unofficial Source

Mitel Forums => Mitel MiVoice Business/MCD/3300 => Topic started by: jcnick on April 03, 2014, 11:47:23 AM

Title: 3300 ICp to Sx2000 MSDN
Post by: jcnick on April 03, 2014, 11:47:23 AM

Hey guys, could use some help on this
Several years ago we installed a MX controller, with a per node, and set up MSDN to their main Campus, a SX2000. About 5 years ago we informed the customer that the 2K
was dead product. He got pissed and wouldn't talk to us. Fast forward to last week. Their mx hard drive died and they had no backups and we couldn't find one either
I replaced the drive and rebuilt the database, but I'm having problems with the MSDN with the trunks stuck at "Not Seizable" on both sides.The link is up and  I was able to reference the 2k so my
A or B settings are correct. B8ZS setting are yes and ESF is no for both. I even found a icp 6. install guide saying the D channel needed to be inverted, but that didn't help.

I have jacked with the descriptor setting and just can't get the B channels to go Idle. I'm stuck, any suggestions would be great

Forgot to say the T1 is on an embedded module
 

Title: Re: 3300 ICp to Sx2000 MSDN
Post by: lundah on April 03, 2014, 01:13:06 PM

Can you post your settings for both the "Link Descriptor Assignment" and "MSDN-DPNSS-DASSII Trunk Circuit Descriptor" forms on both ends?

Title: Re: 3300 ICp to Sx2000 MSDN
Post by: ralph on April 03, 2014, 01:16:19 PM

Start by doing a DTS REad <plid> to see if it's synced.
Is it possible that the T1 cable is straight through?
You may have to change the interface type.


Ralph

Title: Re: 3300 ICp to Sx2000 MSDN
Post by: Mattmayn on April 03, 2014, 02:57:34 PM

I have a site like this and I want to say that we set it up as a PRI and it works fine. I can get to the 3300 remotely, but the 2K is not accessable remotely.

Title: Re: 3300 ICp to Sx2000 MSDN
Post by: lundah on April 03, 2014, 04:56:17 PM

I have a feeling if the circuit greens up but the channels are still OOS, the issue is probably the trunk circuit descriptor instead of the link descriptor, but without being able to see what's configured now it's just a stab in the dark.

Title: Re: 3300 ICp to Sx2000 MSDN
Post by: jcnick on April 07, 2014, 08:35:04 AM

Sorry for the delay. I'm trying to get remote access since the site is about 60 miles away. The T1 is passed thru a AT&T router and broken out for the voice.We are trying to get AT&T to check the settings for the 2K side since the 3300 side appears to be correct.  The 2K can only handle super frame and I'm concerned that the configuration might have been changed. Sound crazy, but i have had these changed on me more than once