<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Interface Technologies NW Blog &#187; all to patch panel</title>
	<atom:link href="http://www.interfacetechnw.com/blog/tag/all-to-patch-panel/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.interfacetechnw.com/blog</link>
	<description>Cabling Infrastructure, Meru Wireless Network, and Avaya VOIP Blog</description>
	<lastBuildDate>Fri, 05 Mar 2010 03:30:46 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>ITN’s approach to a AMP NetConnect cable plant and termination</title>
		<link>http://www.interfacetechnw.com/blog/itn%e2%80%99s-approach-to-a-amp-netconnect-cable-plant-and-termination/</link>
		<comments>http://www.interfacetechnw.com/blog/itn%e2%80%99s-approach-to-a-amp-netconnect-cable-plant-and-termination/#comments</comments>
		<pubDate>Fri, 12 Jun 2009 00:54:39 +0000</pubDate>
		<dc:creator>andy</dc:creator>
				<category><![CDATA[Structured Cabling Solutions from AMP & ITN]]></category>
		<category><![CDATA[all to patch panel]]></category>
		<category><![CDATA[AMP Cabling]]></category>
		<category><![CDATA[cabling in rack]]></category>
		<category><![CDATA[patch cabling]]></category>
		<category><![CDATA[structured cabling]]></category>
		<category><![CDATA[universal cabling]]></category>
		<category><![CDATA[universal style wiring]]></category>

		<guid isPermaLink="false">http://www.interfacetechnw.com/blog/?p=15</guid>
		<description><![CDATA[Since 2003 ITN has recommended to our clients that they install, or consider installing, an “all Cat 5e” or “all Cat 6” infrastructure.  Most folks call this style of structured cabling “Universal” and it allows any and every cable in the facility to be used for voice, data, video, scanner, network printer, fax, postage, IP [...]]]></description>
			<content:encoded><![CDATA[<p class="MsoNormal" style="margin: 0in 0in 10pt;"><span style="font-size: small;"><span style="font-family: Calibri;">Since 2003 ITN has recommended to our clients that they install, or consider installing, an “all Cat 5e” or “all Cat 6” infrastructure.<span style="mso-spacerun: yes;">  </span>Most folks call this style of structured cabling “Universal” and it allows any and every cable in the facility to be used for voice, data, video, scanner, network printer, fax, postage, IP camera, etc.. by simply moving a patch cord!<span style="mso-spacerun: yes;">  </span>And it doesn’t matter if you have a state of the art AVAYA VOIP Telephone system or a 15 year old key/PBX telephone system, with a couple of 25 pairs and an extra patch panel or two, your new structured cabling solution can accommodate any system.<span style="mso-spacerun: yes;">  </span>Having a Universal cabling system also allows a very simple transition to an AVAYA VOIP phone system (AVAYA IP Office) in the future.<span style="mso-spacerun: yes;">  </span>The alternative to this would be to continue to have your “voice cables” terminate to wall mounted 66 blocks or 110 blocks and your “data cables” terminate to patch panel.<span style="mso-spacerun: yes;">  </span>The way to look at this is that they are only data cables because they go to the patch panel and only voice cause they go to the wall field.<span style="mso-spacerun: yes;">  </span>If they were all AMP Netconnect Category 6 cables and they all ran to patch panel, you could utilize any cable for any type of connectivity now and in the future. <span style="mso-spacerun: yes;">  </span></span></span></p>
]]></content:encoded>
			<wfw:commentRss>http://www.interfacetechnw.com/blog/itn%e2%80%99s-approach-to-a-amp-netconnect-cable-plant-and-termination/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
