Properly Network MIC's with Point to Point PRI 4

[SysTool]

I am trying to connect (2) MICS Systems with a Point to Point PRI. Using Rad IP MUX-11's at each site acting as the LEC providing the PRI. MICS at one site is R6.1 and at the other is R7.0. PRI enabler codes are installed. I have sync lights on rad equipment and alarm lights are off. I have checked parameters to match, PRI, ESF, B8ZS etc..., The clocking is set to Primary on both [this may be my biggest reason why not working] I have set up a route, a dest code, target lines. I get a "no lines Free" message when attempting to dial. Anyone ever configure like this with or without the RAD Mux-11's?

 

[SysTool]

This does get a little more complicated wich I didn't want to post and be to complicated off the bat. I actually have 3 sites, 2 point to point T1 PRI's via the Rad MUX-11's (4) total Rad MUX 11's. (2) PRI (DTI) cards in the middle switch. I think I have to set one as Master and the other will automatically configure itself proper as primary or seconday. The remote sites I believe need to be primary and no clocking will be generated from the RAD Mux's. Any advise or similar config's would be appreciated. Thank You.

 

[Deweyhumbolt]

You need an MCDN keycode. That will then under SL-1 Protocol, give you the Master and Slave choices. It will not work with both at Primary.

"Arizona Cardinals NFC Champions!

 

[SysTool]

can I have MCDN with MIC's only or do I need them to be behind an Option 11? I thought I saw "Master" as an option when I was setting up the PRI's. I will check again when I get in front of the system. Thank You.

 

[hawks]

The MCDN gives you the SL1 Protocol needed to tie the 2 together in a network. If you saw a choice for SL1 or Master then you should have that code already installed in the system.

 

[jerryreeve]

even though the l"book" for 6.1 advises you that you can use MCDN keycode to open up the SL-1 protocol the installers guide for 7.0 states that all the MICS have to be at 7.0.

so it looks like you may have to upgrade the 6.1 to 7.0

----------------------------
Hill?? What hill??
I didn't see any $%@#(*$ Hill!!
----------------------------
JerryReeve
Communication Systems Int'l
com-sys.com

 

[hawks]

No you don't have to be 7 I have it running with 6.1

 

[jerryreeve]

I thought the 7.0 book might have been screwy on that.

----------------------------
Hill?? What hill??
I didn't see any $%@#(*$ Hill!!
----------------------------
JerryReeve
Communication Systems Int'l
com-sys.com

 

[hawks]

Jerry it may have been refering to the 3rd T1 card that 7.0 will let you add.

 

[SysTool]

So pretty much I do need to be at 7.0 on all switches to use the MCDN keycode and unlock the SL-1 protocol? Please tell me if you know if this is only to enable features that would allow a centralized voice mail. I can get by with only passing digits across to transfer to extensions because I have seperate voice mail at each location. however if the SL-1 is needed for the middle switch to pass a call from the 1st switch to the 3rd then i better get that keycode ????

 

[Deweyhumbolt]

You need the keycode.

"Arizona Cardinals NFC Champions!

 

[hawks]

No you do not have to be 7.0 the 6.1 will work.
If you do not care about any Caller ID and are just looking to dial and transfer calls then you can set these up as just standard T1 circuits. Just programm them as E&M with Auto Answer turned on and you can call and Transfer calls between the sites.

 

[RikRodgers]

For timing, you should have one set to Master, and the other set to "Primary" (Politically correct for Slave.).

 

[SysTool]

Thanks for the replies guys. I will try the standart T1 settings with E&M and auto answer. Not sure if the RAD IP MUX-11's will emulate a standard T1 E&M Circuit. I have a call into RAD Tech support as well. If I do care about the caler ID then will I have to get the MCDN Keycodes and use SL-1?

 

[fireeater]

if the systems are not to far away from each other and your just connecting them with copper you don't need a mux
i have 2 sites 2 km from each other and am connecting with 2 rad t1 to fiber converters and 2 km of fiber
setup with mcdn and centralizes voicemail works fine on 6.0


All Things Are Possible With Time And Lots And Lots of Money

mike

http://www.ics-on.ca

 

[SysTool]

fireeater that sounds like I could copy some of your set up as far as how your T1 cards are configured and the rad fiber to T1 converters are configured. I am actually using a 30 Meg wireless pipe with the RAD IP MUX-11's handing off a T1, the data side being seperate. Can you send me the set up of the RAD T1 to fiber converter and the T1 Card in the switch?

 

[fireeater]

well the mcdn code is put in and the pri enabler is put in the dti cards are set as standard pri . as per manual
the rad(manufacturer) t1 to fiber media converters has no programing just some dip switches for the distance used

the systems are setup (1 system 200 series the other system 300 series) with target lines to match the ext numbers

eg ext 221 has target line 245 which has the number 221 assigned to it (as per manual)

then the call pilot is set on system 1 ext 200 (also with target line)

the thing about centralized voice mail is the system the call pilot is connected to can use the feature codes f981 f980 ect. but the other system will need to dial the 200 to get messages

with all the quirkiness of the centralized v mail i would suggest 2 call pilots, 1 for each system


i have tried the wireless for this setup but found it unreliable as it kept lossing connection , not to bad for data but murder on a t1 link, the slightest hickup and the t1 reboots for the next 10 minutes
just a thought


All Things Are Possible With Time And Lots And Lots of Money

mike

http://www.ics-on.ca

 

[SysTool]

fireeater can you tell me what the clock source is set to on the DTI Cards? master, primary or secondary? thank you.

 

[RikRodgers]

The question is whether the ip hardware is generating clock, or just passing on all data as presented.

 

[hawks]

Ok if you are running PRI between the 2 sites
One side has to be Master and one side has to be the Slave

Clocking depends on if you have existing T1's in the system. If you do have a T1/PRI in the system connected to the outside world then it should be marked as Primary and the one tieing to the other system should be Secondary. Always use your best clock source as primary.

If you tie them together using standard T1 then you will not get the Master or Slave prombt for that circuit. But the Clock source will be the same as stated above.

Hope it makes since.

If each only have 1 T1/PRI then both systems clocks are Primary. Remember that setting is just telling the system where to go and sink it's clock to. The secondary only comes into play if you loose the Primary source.