<?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>The NComm Idea Exchange</title>
	<atom:link href="http://ncomm.com/blog/?feed=rss2" rel="self" type="application/rss+xml" />
	<link>http://ncomm.com/blog</link>
	<description>A Telecom OAM Blog!</description>
	<lastBuildDate>Fri, 07 Oct 2011 19:54:07 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.4.2</generator>
		<item>
		<title>IEEE 1588-2008 Software &amp; Whitepaper</title>
		<link>http://ncomm.com/blog/?p=37</link>
		<comments>http://ncomm.com/blog/?p=37#comments</comments>
		<pubDate>Tue, 15 Mar 2011 17:28:15 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Ethernet]]></category>
		<category><![CDATA[Precision Timing Protocol]]></category>
		<category><![CDATA[IEEE 1588-2008 PTP Precision Timing Protocol]]></category>

		<guid isPermaLink="false">http://ncomm.com/blog/?p=37</guid>
		<description><![CDATA[In an environment of the traditional WAN hierarchical network, clock traceability is fairly straightforward, and at least logically manageable with respect to quality and source. However, now Ethernet is found in the wide area network, an environment for which it &#8230; <a href="http://ncomm.com/blog/?p=37">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>In an environment of the traditional WAN hierarchical network, clock  traceability is fairly straightforward, and at least logically  manageable with respect to quality and source. However, now Ethernet is  found in the wide area network, an environment for which it was not  originally designed. In the flat landscape of Ethernet networks, clock  traceability and synchronization are much more difficult; and, not only  are these new Ethernet networks flat, they also will tend to be owned by  many different providers.</p>
<p>To address this critical need, NComm’s IEEE 1588-2008 software provides  a standards compliant mechanism to both make clear of the quality and  traceability of the clock source, and to permit the network to  intelligently choose the best clock from those available should an issue  arise. NComm&#8217;s new IEEE 1588-2008 source code will accommodate any  Ethernet application provided that the hardware supports the function.</p>
<p>Download the whitepaper <a title="NComm IEEE 1588-2008 Whitepaper" href="http://ncomm.com/pdf/NCommIEEE1588.pdf" target="_blank">here</a>.</p>
]]></content:encoded>
			<wfw:commentRss>http://ncomm.com/blog/?feed=rss2&#038;p=37</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>NComm&#8217;s Communication Developer&#8217;s Handbook &#8211; 2011 Edition (Table Of Contents)</title>
		<link>http://ncomm.com/blog/?p=31</link>
		<comments>http://ncomm.com/blog/?p=31#comments</comments>
		<pubDate>Wed, 27 Oct 2010 12:31:18 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Equipment Design]]></category>
		<category><![CDATA[Ethernet Operations, Administration and Maintenance (OAM)]]></category>
		<category><![CDATA[Operations, Administration and Maintenance (OAM)]]></category>
		<category><![CDATA[Primary Rate ISDN]]></category>
		<category><![CDATA[Signaling]]></category>
		<category><![CDATA[T1/E1]]></category>
		<category><![CDATA[Wide Area Networking (WAN)]]></category>
		<category><![CDATA[PRI]]></category>
		<category><![CDATA[SONET]]></category>
		<category><![CDATA[telecom engineering]]></category>
		<category><![CDATA[telecommunications]]></category>

		<guid isPermaLink="false">http://ncomm.com/blog/?p=31</guid>
		<description><![CDATA[Following is the table of contents for NComm's Communication Developer's Handbook - 2011 Edition. If you would like complimentary copy of the pdf book for yourself, please use our request form here. <a href="http://ncomm.com/blog/?p=31">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>Following is the table of contents for NComm&#8217;s Communication Developer&#8217;s Handbook &#8211; 2011 Edition. If you would like complimentary copy of the pdf book for yourself, please use our request form <a title="NComm Communication Developer's Handbook Request Form" href="http://ncomm.com/oam/additionalinformation/book-request.html">here</a>.</p>
<p><strong>C</strong><strong>on</strong><strong>t</strong><strong>en</strong><strong>t</strong><strong>s</strong></p>
<p>Contributors &#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230; 1</p>
<p>Introduction &#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;. 2</p>
<p>Main Components of an Ethernet/WAN Access Project &#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230; 4</p>
<p>Hardware &#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;. 5</p>
<p>Processor &#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230; 5</p>
<p>Memory &#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230; 6</p>
<p>WAN Framer &#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;. 7</p>
<p>Vendor Equipment Application &#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;.. 11</p>
<p>Software &#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230; 12</p>
<p>Operating System &#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230; 13</p>
<p>Management of your WAN Access Trunks&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;.. 14</p>
<p>The Industry Standards, and the â€œReal Worldâ€ &#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230; 16</p>
<p>What is Trunk Management Software? &#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;.. 18</p>
<p>Main Components of Trunk Management Software &#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230; 20</p>
<p>Configuration Manager&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;.. 20</p>
<p>Alarm Manager&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;.. 21</p>
<p>Maintenance Manager &#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;.. 21</p>
<p>Signaling Manager for T1/E1&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;.. 22</p>
<p>Sync Status Messages and Clock Distribution Management&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;.. 23</p>
<p>Trunk Management and SNMP &#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;. 26</p>
<p>Automatic Protection Switching &#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;. 28</p>
<p>History &#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230; 28</p>
<p>Description &#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;.. 29</p>
<p>WarmStart Capability&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;.. 30</p>
<p>System Behavior with WarmStart&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;. 31</p>
<p>WarmStart Implementation Objectives &#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;.. 32</p>
<p>Framer and Transceiver Devices &#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;. 33</p>
<p>Designing for High Availability &#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230; 34</p>
<p>Ethernet in the Wide Area Network &#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;.. 35</p>
<p>Ethernet OAM Design Considerations &#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;.. 37</p>
<p>Specific Issues of Ethernet OAM for IEEE 802.1ag&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;.. 39</p>
<p>Specific Issues of Ethernet OAM for ITU Y.1731&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230; 41</p>
<p>Specific Issues of T1/E1 &#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230; 44</p>
<p>Overview of T1 &#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;.. 44</p>
<p>Alarms &#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230; 45</p>
<p>Framing &#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;. 46</p>
<p>In-band Loopback Activation and De-Activation &#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230; 50</p>
<p>Signaling &#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;.. 50</p>
<p>Overview of E1 &#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;.. 53</p>
<p>Framing &#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;. 54</p>
<p>Alarms &#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230; 59</p>
<p>Signaling &#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;.. 60</p>
<p>Standards Requirements &#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;.. 61</p>
<p>Software Architecture &#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;. 62</p>
<p>Specific Issues of T3/E3 &#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230; 63</p>
<p>Overview of T3 &#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;.. 63</p>
<p>G.747 &#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;. 72</p>
<p>Overview of E3 &#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;.. 74</p>
<p>G.751 Framing &#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;.. 74</p>
<p>G.832 Framing &#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;.. 77</p>
<p>Standards Requirements &#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;.. 81</p>
<p>Alarms and Configuration &#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;. 81</p>
<p>Performance Monitoring &#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230; 82</p>
<p>Software Architecture &#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;. 83</p>
<p>Specific Issues of SONET/SDH &#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;. 84</p>
<p>Overview of SONET &#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230; 84</p>
<p>Section Overhead &#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230; 86</p>
<p>Line Overhead&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230; 86</p>
<p>Path Overhead &#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;.. 87</p>
<p>Overview of SDH &#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;.. 88</p>
<p>Standards Requirements &#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;.. 94</p>
<p>Alarms and Configuration &#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;. 95</p>
<p>Performance Monitoring &#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230; 95</p>
<p>Japanese SDH &#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;.. 96</p>
<p>Handling Groups &#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;.. 98</p>
<p>Automatic Protection Switching &#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;. 99</p>
<p>Interoperability and NComm&#8217;s TMS&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;.. 101</p>
<p>Software Architecture &#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;.. 102</p>
<p>Testing Issues and Gotchaâ€™s &#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;. 103</p>
<p>Estimating the Development Time for a WAN Access Project&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;.. 109</p>
<p>Best Options for Development &#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;. 111</p>
<p>Using NCommâ€™s TMS for SNMP Management &#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;.. 112</p>
<p>The history of bus architecture &#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230; 112</p>
<p>PMC/PTMC &#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;.. 115</p>
<p>COMPACTPCI&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;. 117</p>
<p>The Future: PCI Express, ATCA, AMCâ€¦ &#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;.. 119</p>
<p>Growing Demand for VoIP &#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;. 120</p>
<p>The evolution of telecom equipment &#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;. 122</p>
<p>Outsourcing solutions that make â€œcentsâ€&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;. 122</p>
<p>Completing the System Design &#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;.. 123</p>
<p>Go to the experts &#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230; 124</p>
<p>Glossary &#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;. 125</p>
<p>About NCOMM &#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230; 133</p>
<p>About LSI Corporation &#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;&#8230;. 134</p>
]]></content:encoded>
			<wfw:commentRss>http://ncomm.com/blog/?feed=rss2&#038;p=31</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Going Green with WarmStart Drivers</title>
		<link>http://ncomm.com/blog/?p=22</link>
		<comments>http://ncomm.com/blog/?p=22#comments</comments>
		<pubDate>Mon, 04 Oct 2010 12:50:22 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Equipment Design]]></category>
		<category><![CDATA[Green Equipment Design]]></category>

		<guid isPermaLink="false">http://ncomm.com/blog/?p=22</guid>
		<description><![CDATA[If you are going to be selling into these markets, it makes sense to think about how to make your offerings a little more green or green ready. <a href="http://ncomm.com/blog/?p=22">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>Going green is not only a socially responsible thing to do. It may be required by local, state or federal law. Additionally, there are private sector firms that have instituted policies aimed at consuming less energy and other resources. The use of Passive Optical Networks for building distribution is but one example of strategies to cut power consumption along with recurring energy cost.</p>
<p>If you are going to be selling into these markets, it makes sense to think about how to make your offerings a little more green or green ready. One way to make your equipment offerings use a little less energy is to take advantage of NCommâ€™s warm-start drivers. These drivers were designed to allow you to update software without completely bringing down your box, and stopping voice and data traffic in the process. With a little creativity, these drivers can also be used to keep data traffic up while shutting down active processes like OAM and other management. Depending on the application, this may or may not be practical, but it is something to consider.</p>
<p>Take a look at our short paper on the subject <a href="../../pdf/Going%20Green%20with%20Warm_20100924.pdf">Going Green with Warm Start</a>.</p>
]]></content:encoded>
			<wfw:commentRss>http://ncomm.com/blog/?feed=rss2&#038;p=22</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>NComm Adds Hong Kong Support to Primary Rate ISDN Software Offering</title>
		<link>http://ncomm.com/blog/?p=19</link>
		<comments>http://ncomm.com/blog/?p=19#comments</comments>
		<pubDate>Tue, 28 Sep 2010 15:47:49 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Primary Rate ISDN]]></category>
		<category><![CDATA[T1/E1]]></category>

		<guid isPermaLink="false">http://ncomm.com/blog/?p=19</guid>
		<description><![CDATA[NComm, Inc. today announced support for an additional switch type in its Primary Rate ISDN (Integrated Services Digital Network) software suite <a href="http://ncomm.com/blog/?p=19">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p><em>New offering allows easy product extension into the Hong Kong market for equipment providers</em></p>
<p><em> </em></p>
<p>HAMPSTEAD, NH â€“ September 28, 2010 â€“ NComm, Inc. today announced support for an additional switch type in its Primary Rate ISDN (Integrated Services Digital Network) software suite. NComm software is used by a variety of communication equipment manufacturers to quickly add standard compliant telephony signaling capabilities to network and end-user offerings.</p>
<p>Read more <a title="Hong Kong PRI ISDN Software" href="http://ncomm.com/oam/pdf/PRI%20HongKong%20PR%2020100923_a.pdf" target="_blank">here</a>.</p>
]]></content:encoded>
			<wfw:commentRss>http://ncomm.com/blog/?feed=rss2&#038;p=19</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Where do you need OAM when you have layered WAN/Ethernet technologies?</title>
		<link>http://ncomm.com/blog/?p=14</link>
		<comments>http://ncomm.com/blog/?p=14#comments</comments>
		<pubDate>Mon, 27 Sep 2010 20:33:38 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Ethernet Operations, Administration and Maintenance (OAM)]]></category>
		<category><![CDATA[Operations, Administration and Maintenance (OAM)]]></category>

		<guid isPermaLink="false">http://ncomm.com/blog/?p=14</guid>
		<description><![CDATA[...where OAM (Operations, Administration &#038; Maintenance) capability is needed when you have multiple technologies... <a href="http://ncomm.com/blog/?p=14">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>We get asked periodically where OAM (Operations, Administration &amp; Maintenance) capability is needed when you have multiple technologies (like Ethernet over SONET) running through a single wire or fiber. Except for specialÂ  applications, the answer is you need OAM in each technology. We have a little paper you can download <a title="Layered Transport Technologies and OAM: What is needed?" href="http://www.ncomm.com/pdf/oam_layers_20100924.pdf" target="_blank">here</a> that discusses this issue further.</p>
<p>Have a great day!</p>
]]></content:encoded>
			<wfw:commentRss>http://ncomm.com/blog/?feed=rss2&#038;p=14</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>What is Ethernet OAM?</title>
		<link>http://ncomm.com/blog/?p=9</link>
		<comments>http://ncomm.com/blog/?p=9#comments</comments>
		<pubDate>Thu, 23 Sep 2010 10:00:15 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Ethernet Operations, Administration and Maintenance (OAM)]]></category>

		<guid isPermaLink="false">http://ncomm.com/blog/?p=9</guid>
		<description><![CDATA[Ethernet OAM comprises a number of standards providing tools for monitoring an Ethernet network. <a href="http://ncomm.com/blog/?p=9">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>Ethernet OAM (Operations, Administration, Maintenance) comprises a number of standards providing tools for monitoring an Ethernet network, being alerted to and isolating faults, detecting gradual degradations in quality for preemptive action, and determining network performance vs. Service Level Agreements, etc.</p>
]]></content:encoded>
			<wfw:commentRss>http://ncomm.com/blog/?feed=rss2&#038;p=9</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>What is â€œbit freezingâ€ in traditional telephony?</title>
		<link>http://ncomm.com/blog/?p=4</link>
		<comments>http://ncomm.com/blog/?p=4#comments</comments>
		<pubDate>Mon, 20 Sep 2010 18:15:46 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Signaling]]></category>
		<category><![CDATA[T1/E1]]></category>

		<guid isPermaLink="false">http://ncomm.com/blog/?p=4</guid>
		<description><![CDATA[â€œBit freezingâ€ freezes the last known good signaling bits and thus keeps the connection up unless and until the defect lasts the integration time and the line taken down. <a href="http://ncomm.com/blog/?p=4">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>In any digital transmission, momentary glitches can appear on the line. Such errors or defects are detected and if they persist long enough (the â€œintegration timeâ€ or 2.5 seconds per T1.231), an alarm condition is declared and the line brought down.</p>
<p>Since the line must weather defects lasting less than the integration time, in telephony robbed-bit signaling (RBS) or channel associated signaling (CSA) applications, an established call must also be maintained during the glitches. â€œBit freezingâ€ freezes the last known good signaling bits and thus keeps the connection up unless and until the defect lasts the integration time and the line taken down.</p>
]]></content:encoded>
			<wfw:commentRss>http://ncomm.com/blog/?feed=rss2&#038;p=4</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
	</channel>
</rss>
