<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
		>
<channel>
	<title>Comments on: CCIE Voice 3.0 ProctorLabs Hardware Update</title>
	<atom:link href="http://blog.ipexpert.com/2008/12/03/ccie-voice-30-proctorlabs-hardware-update/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.ipexpert.com/2008/12/03/ccie-voice-30-proctorlabs-hardware-update/</link>
	<description>CCIE Candidates blog for all technical overviews relating to CCIE R&#38;S, CCIE Voice, CCIE Security &#38; CCIE SP</description>
	<lastBuildDate>Thu, 09 Feb 2012 17:07:01 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1.2</generator>
	<item>
		<title>By: The IPexpert Blog &#187; CCIE 3.0 – The Transitional Study Path for Voice Candidates</title>
		<link>http://blog.ipexpert.com/2008/12/03/ccie-voice-30-proctorlabs-hardware-update/comment-page-1/#comment-341</link>
		<dc:creator>The IPexpert Blog &#187; CCIE 3.0 – The Transitional Study Path for Voice Candidates</dc:creator>
		<pubDate>Fri, 19 Dec 2008 21:55:14 +0000</pubDate>
		<guid isPermaLink="false">http://ipexpert.ccieblog.com/?p=340#comment-341</guid>
		<description>[...] has been a few weeks since the big announcement was released and we’ve all had time to digest where we stand, where we are going and what we need to [...]</description>
		<content:encoded><![CDATA[<p>[...] has been a few weeks since the big announcement was released and we’ve all had time to digest where we stand, where we are going and what we need to [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: The IPexpert Blog &#187; CCIE 3.0 – The Transitional Study Path for Voice Candidates</title>
		<link>http://blog.ipexpert.com/2008/12/03/ccie-voice-30-proctorlabs-hardware-update/comment-page-1/#comment-3364</link>
		<dc:creator>The IPexpert Blog &#187; CCIE 3.0 – The Transitional Study Path for Voice Candidates</dc:creator>
		<pubDate>Fri, 19 Dec 2008 21:55:14 +0000</pubDate>
		<guid isPermaLink="false">http://ipexpert.ccieblog.com/?p=340#comment-3364</guid>
		<description>[...] has been a few weeks since the big announcement was released and we’ve all had time to digest where we stand, where we are going and what we need to [...]</description>
		<content:encoded><![CDATA[<p>[...] has been a few weeks since the big announcement was released and we’ve all had time to digest where we stand, where we are going and what we need to [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mark Snow</title>
		<link>http://blog.ipexpert.com/2008/12/03/ccie-voice-30-proctorlabs-hardware-update/comment-page-1/#comment-340</link>
		<dc:creator>Mark Snow</dc:creator>
		<pubDate>Fri, 12 Dec 2008 02:02:57 +0000</pubDate>
		<guid isPermaLink="false">http://ipexpert.ccieblog.com/?p=340#comment-340</guid>
		<description>Ok Steve - you stole our thunder on one of our enhancements. So here it is for everyone.
We first thought about having a drop-down on our vRack page to allow you to pick the dial-plan to go with a particular lab. But then we thought - &quot;why should they have to do one more thing when getting ready for their lab practice?&quot;. Instead we are going to have different dial plans for many of the labs (maybe not a different one for every single lab - but probably a different one for every 2) and they will always be loaded - and they won&#039;t vary per pod. Even though there will be different dial-plans, every pod will be able to test the same labs with with same dial plans. No more need to look at a bunch of tables to differentiate what pod uses what VLANs or dial plans or anything.
But that&#039;s just one anouncement ;-)</description>
		<content:encoded><![CDATA[<p>Ok Steve &#8211; you stole our thunder on one of our enhancements. So here it is for everyone.<br />
We first thought about having a drop-down on our vRack page to allow you to pick the dial-plan to go with a particular lab. But then we thought &#8211; &#8220;why should they have to do one more thing when getting ready for their lab practice?&#8221;. Instead we are going to have different dial plans for many of the labs (maybe not a different one for every single lab &#8211; but probably a different one for every 2) and they will always be loaded &#8211; and they won&#8217;t vary per pod. Even though there will be different dial-plans, every pod will be able to test the same labs with with same dial plans. No more need to look at a bunch of tables to differentiate what pod uses what VLANs or dial plans or anything.<br />
But that&#8217;s just one anouncement ;-)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mark Snow</title>
		<link>http://blog.ipexpert.com/2008/12/03/ccie-voice-30-proctorlabs-hardware-update/comment-page-1/#comment-3363</link>
		<dc:creator>Mark Snow</dc:creator>
		<pubDate>Fri, 12 Dec 2008 02:02:57 +0000</pubDate>
		<guid isPermaLink="false">http://ipexpert.ccieblog.com/?p=340#comment-3363</guid>
		<description>Ok Steve - you stole our thunder on one of our enhancements. So here it is for everyone.
We first thought about having a drop-down on our vRack page to allow you to pick the dial-plan to go with a particular lab. But then we thought - &quot;why should they have to do one more thing when getting ready for their lab practice?&quot;. Instead we are going to have different dial plans for many of the labs (maybe not a different one for every single lab - but probably a different one for every 2) and they will always be loaded - and they won&#039;t vary per pod. Even though there will be different dial-plans, every pod will be able to test the same labs with with same dial plans. No more need to look at a bunch of tables to differentiate what pod uses what VLANs or dial plans or anything.
But that&#039;s just one anouncement ;-)</description>
		<content:encoded><![CDATA[<p>Ok Steve &#8211; you stole our thunder on one of our enhancements. So here it is for everyone.<br />
We first thought about having a drop-down on our vRack page to allow you to pick the dial-plan to go with a particular lab. But then we thought &#8211; &#8220;why should they have to do one more thing when getting ready for their lab practice?&#8221;. Instead we are going to have different dial plans for many of the labs (maybe not a different one for every single lab &#8211; but probably a different one for every 2) and they will always be loaded &#8211; and they won&#8217;t vary per pod. Even though there will be different dial-plans, every pod will be able to test the same labs with with same dial plans. No more need to look at a bunch of tables to differentiate what pod uses what VLANs or dial plans or anything.<br />
But that&#8217;s just one anouncement ;-)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Steve</title>
		<link>http://blog.ipexpert.com/2008/12/03/ccie-voice-30-proctorlabs-hardware-update/comment-page-1/#comment-339</link>
		<dc:creator>Steve</dc:creator>
		<pubDate>Thu, 11 Dec 2008 07:18:13 +0000</pubDate>
		<guid isPermaLink="false">http://ipexpert.ccieblog.com/?p=340#comment-339</guid>
		<description>Now you&#039;re talking! Updates to the PSTN would be a huge step in the evolution of your labs. I was thinking of designing s system which lets people input their own entire PSTN dial plan, through a web interface and save it for future use. I did mention this to Vik some time back. This way when you have been to the real lab you can make use of the $1400 you have coughed up and practice on an what is perhaps a significant stumbling block for many. Look forward to seeing the results.</description>
		<content:encoded><![CDATA[<p>Now you&#8217;re talking! Updates to the PSTN would be a huge step in the evolution of your labs. I was thinking of designing s system which lets people input their own entire PSTN dial plan, through a web interface and save it for future use. I did mention this to Vik some time back. This way when you have been to the real lab you can make use of the $1400 you have coughed up and practice on an what is perhaps a significant stumbling block for many. Look forward to seeing the results.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Steve</title>
		<link>http://blog.ipexpert.com/2008/12/03/ccie-voice-30-proctorlabs-hardware-update/comment-page-1/#comment-3362</link>
		<dc:creator>Steve</dc:creator>
		<pubDate>Thu, 11 Dec 2008 07:18:13 +0000</pubDate>
		<guid isPermaLink="false">http://ipexpert.ccieblog.com/?p=340#comment-3362</guid>
		<description>Now you&#039;re talking! Updates to the PSTN would be a huge step in the evolution of your labs. I was thinking of designing s system which lets people input their own entire PSTN dial plan, through a web interface and save it for future use. I did mention this to Vik some time back. This way when you have been to the real lab you can make use of the $1400 you have coughed up and practice on an what is perhaps a significant stumbling block for many. Look forward to seeing the results.</description>
		<content:encoded><![CDATA[<p>Now you&#8217;re talking! Updates to the PSTN would be a huge step in the evolution of your labs. I was thinking of designing s system which lets people input their own entire PSTN dial plan, through a web interface and save it for future use. I did mention this to Vik some time back. This way when you have been to the real lab you can make use of the $1400 you have coughed up and practice on an what is perhaps a significant stumbling block for many. Look forward to seeing the results.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mark Snow</title>
		<link>http://blog.ipexpert.com/2008/12/03/ccie-voice-30-proctorlabs-hardware-update/comment-page-1/#comment-338</link>
		<dc:creator>Mark Snow</dc:creator>
		<pubDate>Wed, 10 Dec 2008 21:51:34 +0000</pubDate>
		<guid isPermaLink="false">http://ipexpert.ccieblog.com/?p=340#comment-338</guid>
		<description>@Matt,

Thanks for the kind words. I only wish some of these features were in fact around when you were studying with us. We&#039;re doing some more really exciting things with the PSTN (ok - I must admit I am certainly a geek - and my wife thinks so too - when I get &quot;excited&quot; about what we are doing in our PSTN) that will make studying a whole lot more challenging - but also much more like a real lab environment.</description>
		<content:encoded><![CDATA[<p>@Matt,</p>
<p>Thanks for the kind words. I only wish some of these features were in fact around when you were studying with us. We&#8217;re doing some more really exciting things with the PSTN (ok &#8211; I must admit I am certainly a geek &#8211; and my wife thinks so too &#8211; when I get &#8220;excited&#8221; about what we are doing in our PSTN) that will make studying a whole lot more challenging &#8211; but also much more like a real lab environment.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mark Snow</title>
		<link>http://blog.ipexpert.com/2008/12/03/ccie-voice-30-proctorlabs-hardware-update/comment-page-1/#comment-3361</link>
		<dc:creator>Mark Snow</dc:creator>
		<pubDate>Wed, 10 Dec 2008 21:51:34 +0000</pubDate>
		<guid isPermaLink="false">http://ipexpert.ccieblog.com/?p=340#comment-3361</guid>
		<description>@Matt,

Thanks for the kind words. I only wish some of these features were in fact around when you were studying with us. We&#039;re doing some more really exciting things with the PSTN (ok - I must admit I am certainly a geek - and my wife thinks so too - when I get &quot;excited&quot; about what we are doing in our PSTN) that will make studying a whole lot more challenging - but also much more like a real lab environment.</description>
		<content:encoded><![CDATA[<p>@Matt,</p>
<p>Thanks for the kind words. I only wish some of these features were in fact around when you were studying with us. We&#8217;re doing some more really exciting things with the PSTN (ok &#8211; I must admit I am certainly a geek &#8211; and my wife thinks so too &#8211; when I get &#8220;excited&#8221; about what we are doing in our PSTN) that will make studying a whole lot more challenging &#8211; but also much more like a real lab environment.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mark Snow</title>
		<link>http://blog.ipexpert.com/2008/12/03/ccie-voice-30-proctorlabs-hardware-update/comment-page-1/#comment-337</link>
		<dc:creator>Mark Snow</dc:creator>
		<pubDate>Wed, 10 Dec 2008 20:39:18 +0000</pubDate>
		<guid isPermaLink="false">http://ipexpert.ccieblog.com/?p=340#comment-337</guid>
		<description>@Daryl,
When we release the Volumes that do come with VoD walkthroughs - we will probably release the lab and solutions first, to get them to you quicker, and then follow each lab up with the VoD for that lab. So Lab1 with Solutions, then Lab1 VoD, then Lab2, etc.</description>
		<content:encoded><![CDATA[<p>@Daryl,<br />
When we release the Volumes that do come with VoD walkthroughs &#8211; we will probably release the lab and solutions first, to get them to you quicker, and then follow each lab up with the VoD for that lab. So Lab1 with Solutions, then Lab1 VoD, then Lab2, etc.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mark Snow</title>
		<link>http://blog.ipexpert.com/2008/12/03/ccie-voice-30-proctorlabs-hardware-update/comment-page-1/#comment-3360</link>
		<dc:creator>Mark Snow</dc:creator>
		<pubDate>Wed, 10 Dec 2008 20:39:18 +0000</pubDate>
		<guid isPermaLink="false">http://ipexpert.ccieblog.com/?p=340#comment-3360</guid>
		<description>@Daryl,
When we release the Volumes that do come with VoD walkthroughs - we will probably release the lab and solutions first, to get them to you quicker, and then follow each lab up with the VoD for that lab. So Lab1 with Solutions, then Lab1 VoD, then Lab2, etc.</description>
		<content:encoded><![CDATA[<p>@Daryl,<br />
When we release the Volumes that do come with VoD walkthroughs &#8211; we will probably release the lab and solutions first, to get them to you quicker, and then follow each lab up with the VoD for that lab. So Lab1 with Solutions, then Lab1 VoD, then Lab2, etc.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

