<?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>World IPv6 Launch Day: Interoperability Lab</title>
	<atom:link href="http://interoplab.dmci.hva.nl/feed/" rel="self" type="application/rss+xml" />
	<link>http://interoplab.dmci.hva.nl</link>
	<description></description>
	<lastBuildDate>Wed, 06 Jun 2012 12:10:20 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
		<item>
		<title>Virtual lab</title>
		<link>http://interoplab.dmci.hva.nl/virtual-lab/</link>
		<comments>http://interoplab.dmci.hva.nl/virtual-lab/#comments</comments>
		<pubDate>Sat, 02 Jun 2012 13:11:03 +0000</pubDate>
		<dc:creator>hvainterop</dc:creator>
				<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://interoplab.dmci.hva.nl/?p=436</guid>
		<description><![CDATA[At the moment we are creating a virtual lab. Our Game Design and Game Technology team is working very hard to realize this virtual lab. This virtual lab will be shown during the IPv6 launch day on a 60&#8243; touch &#8230; <a href="http://interoplab.dmci.hva.nl/virtual-lab/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p><a href="http://interoplab.dmci.hva.nl/wp-content/uploads/2012/06/voorproefje.jpg"><img class="aligncenter size-full wp-image-439" title="voorproefje" src="http://interoplab.dmci.hva.nl/wp-content/uploads/2012/06/voorproefje.jpg" alt="" width="2414" height="761" /></a>At the moment we are creating a virtual lab. Our Game Design and Game Technology team is working very hard to realize this virtual lab.</p>
<p>This virtual lab will be shown during the IPv6 launch day on a 60&#8243; touch screen.</p>
]]></content:encoded>
			<wfw:commentRss>http://interoplab.dmci.hva.nl/virtual-lab/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Testing the VoIP phones</title>
		<link>http://interoplab.dmci.hva.nl/testing-the-voip-phones/</link>
		<comments>http://interoplab.dmci.hva.nl/testing-the-voip-phones/#comments</comments>
		<pubDate>Sat, 02 Jun 2012 11:03:31 +0000</pubDate>
		<dc:creator>hvainterop</dc:creator>
				<category><![CDATA[VoIP]]></category>

		<guid isPermaLink="false">http://interoplab.dmci.hva.nl/?p=429</guid>
		<description><![CDATA[The phones from Yealink and Tandberg where able to call each other on a network which included the phones themselves and a switch from Juniper/Cisco. Telephones tested 1x Yealtek T20P 1x Yealtek T22P 1x Yealtek T24P 1x Yealtek T28P 2x &#8230; <a href="http://interoplab.dmci.hva.nl/testing-the-voip-phones/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>The phones from Yealink and Tandberg where able to call each other on a network which included the phones themselves and a switch from Juniper/Cisco.</p>
<p>Telephones tested</p>
<p>1x Yealtek T20P<br />
1x Yealtek T22P<br />
1x Yealtek T24P<br />
1x Yealtek T28P<br />
2x Tandberg E20<br />
In combination with:</p>
<p>1x Juniper EX3200 Switch<br />
1x Cisco Catalyst 3562 V2 switch<br />
Tandberg Phones<br />
At the beginning we started with the Tandberg Phones. Tandberg has been bought by Cisco whom customized the original firmware which was able to function on IPv6 protocol to a version of their own. This new version didn’t support the IPv6 protocol.<br />
The first thing we did to get the phones working op IPv6 was replace the (newer) firmware with the (older) Tandberg firmware that does support IPv6 and IPv4 technology. After the installation of the original Tandberg firmware the phones were working pretty well. We connected the phones to the switch and started to configure the accounts we made on the SIP server for VoIP communication. The phones where not to difficult to configure with the firmware of Tandberg and after configuration the phones had been registered on the server and where standing by for their first phone call in our Interoperability lab. We picked up the phone and called the other phone. The phone instantly started to ring. We had a success; the phones work on IPv6.</p>
<p>Yealink Phones<br />
The Yealink phones which where provided by Tiptel came in by mail. We unpacked them and started to connect them to the switch, thus connecting them the IPv6 network of the Interoperability Lab. The phones worked like a charm, even though the configuration of the phones didn’t go that easily. The phones had to be configured through the “advanced settings” menu. The configuration progress was literally going from static IPv6 address definition to the account number and password. After completing this phones were fully operational and they where able to call the Tandberg phones as well.</p>
]]></content:encoded>
			<wfw:commentRss>http://interoplab.dmci.hva.nl/testing-the-voip-phones/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Load Balancer progress 1</title>
		<link>http://interoplab.dmci.hva.nl/load-balancer-progress-1/</link>
		<comments>http://interoplab.dmci.hva.nl/load-balancer-progress-1/#comments</comments>
		<pubDate>Sat, 02 Jun 2012 08:47:10 +0000</pubDate>
		<dc:creator>hvainterop</dc:creator>
				<category><![CDATA[Load Balancers]]></category>

		<guid isPermaLink="false">http://interoplab.dmci.hva.nl/?p=427</guid>
		<description><![CDATA[Our load balancer is up and running, it successfully balances FTP and HTTP traffic with an IPv6 configuration. The web servers that are connected to the load balancer are synchronized so no conflicted copies can occur. There is one problem &#8230; <a href="http://interoplab.dmci.hva.nl/load-balancer-progress-1/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>Our load balancer is up and running, it successfully balances FTP and HTTP traffic with an IPv6 configuration.<br />
The web servers that are connected to the load balancer are synchronized so no conflicted copies can occur.<br />
There is one problem at this point, which concerns our monitoring server. We have concluded that Cacti and Zimbax aren&#8217;t really compatible with IPv6 addresses, we are busy looking for alternatives and solutions but with no results so far.</p>
]]></content:encoded>
			<wfw:commentRss>http://interoplab.dmci.hva.nl/load-balancer-progress-1/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Core Network 1</title>
		<link>http://interoplab.dmci.hva.nl/core-network-1/</link>
		<comments>http://interoplab.dmci.hva.nl/core-network-1/#comments</comments>
		<pubDate>Thu, 31 May 2012 14:59:08 +0000</pubDate>
		<dc:creator>hvainterop</dc:creator>
				<category><![CDATA[Core Network]]></category>

		<guid isPermaLink="false">http://interoplab.dmci.hva.nl/?p=412</guid>
		<description><![CDATA[At the moment the team is in the progress of connecting a couple of tests on the core routers. The team is also busy with testing connectivity between the core routers and the tests, and making sure the tests are &#8230; <a href="http://interoplab.dmci.hva.nl/core-network-1/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>At the moment the team is in the progress of connecting a couple of tests on the core routers. The team is also busy with testing connectivity between the core routers and the tests, and making sure the tests are working on a core router, instead of as a standalone test. In this regard, we also want to make sure inter-testing between multiple core routers is possible.  What left to be done is the connectivity of the BYOD and Firewalls test, core network VLAN testing and configuration, labeling and documenting each cable that is in use, and creating the uplink between the UvA network at the Science Park and the core network.  </p>
]]></content:encoded>
			<wfw:commentRss>http://interoplab.dmci.hva.nl/core-network-1/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>VoIP progress 2</title>
		<link>http://interoplab.dmci.hva.nl/voip-progress-2/</link>
		<comments>http://interoplab.dmci.hva.nl/voip-progress-2/#comments</comments>
		<pubDate>Thu, 31 May 2012 14:57:27 +0000</pubDate>
		<dc:creator>hvainterop</dc:creator>
				<category><![CDATA[VoIP]]></category>

		<guid isPermaLink="false">http://interoplab.dmci.hva.nl/?p=409</guid>
		<description><![CDATA[We are configuring VoIP phones in order to make them work with SIP over an IPv6 network. All the phones we received from the different vendors worked like a charm in the first test. At this point there was one &#8230; <a href="http://interoplab.dmci.hva.nl/voip-progress-2/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>We are configuring VoIP phones in order to make them work with SIP over an IPv6 network. All the phones we received from the different vendors worked like a charm in the first test. At this point there was one central network where the SIP server and the VoIP phones were connected to. In the second test we used different switches and routers. All routers which are also used in the core network test are compatible with the VoIP phones and we didn’t experience any problems. During our third test we found a bug with a specific VoIP phone vendor. At this moment the vendor is aware of the bug and the test team is in close contact with the vendor in order to resolve this bug. At this moment we can’t give any details about the problems end-users may experience when using this phone over IPv6. In the third test we have two different networks (different types of routers and switches which are connected to each other). The SIP server is located in one network and the VoIP telephone in another network. This is a simulation of two offices that will contact each other using one SIP server.</p>
]]></content:encoded>
			<wfw:commentRss>http://interoplab.dmci.hva.nl/voip-progress-2/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>VoIP progress 1</title>
		<link>http://interoplab.dmci.hva.nl/voip-progress/</link>
		<comments>http://interoplab.dmci.hva.nl/voip-progress/#comments</comments>
		<pubDate>Wed, 30 May 2012 09:09:49 +0000</pubDate>
		<dc:creator>hvainterop</dc:creator>
				<category><![CDATA[Blog]]></category>
		<category><![CDATA[VoIP]]></category>

		<guid isPermaLink="false">http://interoplab.dmci.hva.nl/?p=353</guid>
		<description><![CDATA[The VoIP servers are running and the Yealtek phones ringing. The Tandberg phones are installed and with the right firmware. The communication is now at its best. The next step is to use the core network so the VoIp test &#8230; <a href="http://interoplab.dmci.hva.nl/voip-progress/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p><center><img src="http://interoplab.dmci.hva.nl/wp-content/uploads/2012/05/VoIP-progress.png" alt="" title="VoIP progress" width="394" height="226" class='ngg-singlepic ngg-none'/></center><br />
The VoIP servers are running and the Yealtek phones ringing. The Tandberg phones are installed and with the right firmware. The communication is now at its best. The next step is to use the core network so the VoIp test can run alongside the other tests.</p>
]]></content:encoded>
			<wfw:commentRss>http://interoplab.dmci.hva.nl/voip-progress/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
