Telco's use UnSheilded Twisted Pair (UTP) Jumpers for up to 8MBit Transmission (PDH & SHD), as long as you maintain the twist rate of your Jumpers you should not have a problem
you should use 110 blocks because you can
come right off the 110 block with a 110 to rj45 (568B)
patch cord and the cool thing if you are working
with a avaya stuff you can come right off the same block
with the same patch cord i just described and plug
it directly into the ksu! ck out icc's website
I'd simply terminate everything to Cat-5e jacks on the drop side, and a Cat-5e patch panel on the MDF/IDF side. From there, you can make a patch panel from your KSU ports... and use a patch cord from panel to panel to cross connect. A linecord will plug into a Cat-5e jack on the drop side no problem. That way you can wire it all the same, and cross connect as needed.
We terminate ALL our outlets on a data patch panel. We then bring 48 ports of the phone switch out to it's own patch block. simply running a patch cord from the phone panel to the outlet panel makes that port a phone. We use different colored cables for the phones so they are easier to see. Works great for us.
To interface with your phones you could also use your BIX 46D blocks. Run jumper wire from your phone system to the appropriate spot on the BIX 46D then use a CAT5e patch cable from the BIX 46D to your data panel.
Well, I'll go with the contrary position. I haven't yet been sold on the idea of integrating the voice and data fields into patch panels.
Now, my situation is a little different in that I'm in a campus environment, and have a centralized PBX, so in the individual buildings, I am only cross-connection from station cable to outside plant cable.
We have discussed moving the voice station cable to the rack and putting it on patch panels, for the above mentioned purpose of using "any jack for any service". Well, without moving the station cable we're doing that already, using the mentioned 110-RJ45 patch cords to go from the voice-110 field to a data switch. This is our typical situation. I don't think we've ever needed to use a data jack for a voice application. Plus, since the voice and data station is all Cat6 anyway (yes I know. Cat6 is way over kill for an analog phone) when VoIP happens, we don't have to change anything, save for pulling all the cross connect jumpers, and installing the Cat6 110-RJ45 cords.
My point boils down to, separate does not mean inflexible.
Justin T. Clausen
Physical Layer Implementation
California State University, Monterey Bay
The sites that I have been presenty installing are still looking for flexibility with their voice cable for adding a second phone or fax or a modem connection from their phone system for backup IP connection but want all cabling in their rack/cabinet.
What we have been doing is to install 3 CAT5e cables(they are not biting on the CAT6 yet).
1 cable is for voice split into 2 4cond 8 position jacks. They are terminated on 4 conductor 8 position patch panels.
The phone system is wired out with double ended amphenols to amphenol 2 position 8 conductor patch panels.
The other 2 cables are on CAT5e jacks terminated on CAT5e patch panels.
We just use a different color CAT5e patch cables (yes I know overkill) but the IT groups want CAT5e patch cables.
We lay out the rack with the Telco on top,WM,CO Patch Panels,WM,Voice cables, spacing,Data cables, WM, switches & accomplish most of the install with mostly 3 ft patch cables with less than 10% 5 ft
We also bring the CO's over to a 2 conductor patch panel & patch to the Trunk ports on the phone system by using 2 conductor 1 ft line cords for them. We also use 7 ft line cords for any direct CO line to a jack.
If you are adiment(sp?) on using something other than a patch panel they do make BIX & 110 blocks pinned out with 8 conductor jacks.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.