Search results for query: *

Gents, we were able to bring the PRI up thanks to you guys.. Bravo.. The misleading TN , should indeed be loop and unit, so e.g. 100 1. You have to start with channel 1 instead of channel 0. Thats why the Tn 100 0 didn't work. it should have been 100 1 Cheers! Rev

Dear Gents, so what you all are saying is, to make a "dummy" network loop and bind it to the card using cequ. The TN used when making the channels would than be with what format ( l s c u ) or (l u ) we tried to make the channels earlier by using the (l u ) format, but is does not accept this...

The card is in the 1st slot in the 1st cabinet (shelf 0) The system (CS1000E release 7.5) is using large format TN (l s c u). The Loop is 4. So the card is in 4 0 1. The first unit is thus 4 0 1 0, the second is 4 0 1 1 Rev

yes,Unit 0 is the first on the card

the error is SCH0126 we can't do a TNB on the card.. it does not see it as TIE or anything else so far..

We took out the card and slided it back and got XMI002 4 0 1 PRI2 .. it does see it as a PRI2 card then right?

No there wasn't .. it's a new install.. i do see that when you make your PRI2 loop, the system will add 2 units on that card (4 0 1 0 and 4 0 1 1). They are however unequiped when you do a stat on LD36 (the system does see them as digital trunks somehow) Rev

Hi Villareal, yes, the slot is empty.. (physically it is in 1 slot, but was not programmed.. yet) should i take it out of the slot as well? Regards, Rev

We are trying to program TIE trunks for a PRI2 card on a CS1000E. I have already programmed the DDB, CEQU, DCH, Net data, and RDB. However, while attempting to program the 30 trunks in element manager or in LD 14, I receive err SCH0126: "Station type conflicts with existing card.For example: In...

Any solution to this issue.. we are having the same problem.. after installing a new CS1000E, we are not able to add the pri trunks.. we receive the sch0126 error. The loop is 4. The card sits in slot 1.. we tried to add tie trunks to TN 4 0 1 x but the system responded with the above error...