Timing setup/options

[MyHeadHurts]

I just setup a drop & insert app in an Option 61C for a video/wideband audio application. There is a local service provider PRI that provides the DID's for the app, as well as it's present use of user DID's. Certain DID's are sent to another PRI in the 61C via Steering Codes that drop these calls out to a PRI/BRI IAD.

What I need to do is take the timing on the Local PRI
(LOOP 2), and pass this timing onto the PRI/BRI IAD through the drop & insert PRI (LOOP 3).

I'm rusty on setting timing options up in this switch, so an LD's and command syntax would be helpful.

Thanks

 

[NTOldTimer]

LD 73
PRT
DDB

This will show your primary and secondary reference T1s for clocking. The secondary is used when you have trouble with the primary. Just making loop 2 the primary reference source with software is not enough. The clock controller cable(s) must be conncected to Loop 2 as well. Once it's set up then the clocking from loop 2 will be passed on to all the other T1s in the Option 61.

 

[BMiles2000]

If I understand you correctly you want to clock off loop 2 and send clock to loop 3. There are a couple of different options. If the equipment attached to loop 3 supports Nortels SL1 proprietary signaling then this is simple. Just setup Loop 3 as NET for SIDE instead of USER under your DCH parameters. If your equipment does not support SL1 signaling then you will have to build them with QSIG as ESIG or ISIG. This is not hard but you have to make sure you have the right SW packages to do this. As for setting your Primary to Loop 2 follow what NTOldTimer pointed out. I beleive this is correct. I have only set this up once or twice. Good Luck!

 

[MyHeadHurts]

Thanks for the info NTOldTimer. I just looked up my present timing options, and it just so happens that my primary clock is LOOP 2. That's a good start. One less thing to have to do.

BMiles2000, I asked the person handling the PRI/BRI IAD what protocols it can support, and he said that it does not have a specific option for Meridian SL1, but it does support D100 which he said might and might not work since SL1 is a derivative of D100. As a test, I'll option the D-chnl for SL1 for this drop loop and do as you said and make SIDE NET instead of USER for LOOP 3 and see what happens with the Meridian being set for SL1 and the IAD for D100.

A couple more questions along this line. Let's say that the SL1 to D100 does not work out (as is my personal opinion), could you explain some things to do with ESIG and ISIG.

1. I do not understand QSIG. I see ESIG and ISIG as D-chnl protocol options under IFC in LD 17 with it mentioning to QSIG in the book, but where do you actually build QSIG to allow for the use of ESIG/ISIG?

2. What packages do I need to support to build QSIG?

3. It also states in I/O Guide that both ESIG and ISIG are "only allowed if the new D-chnl is configured on the MSDL card." What is meant by this?

Thanks in advance