<?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>Undecided &#187; VoIP</title>
	<atom:link href="http://www.datarave.net/zfh/category/work/voip/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.datarave.net/zfh</link>
	<description>An open notebook</description>
	<lastBuildDate>Tue, 15 Jun 2010 15:29:05 +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>Project Diary: Xtools [3]</title>
		<link>http://www.datarave.net/zfh/2008/09/05/project-diary-xtools-3/</link>
		<comments>http://www.datarave.net/zfh/2008/09/05/project-diary-xtools-3/#comments</comments>
		<pubDate>Fri, 05 Sep 2008 15:18:45 +0000</pubDate>
		<dc:creator>John Williams</dc:creator>
				<category><![CDATA[Nortel]]></category>
		<category><![CDATA[VoIP]]></category>
		<category><![CDATA[WebDev]]></category>

		<guid isPermaLink="false">http://www.datarave.net/zfh/?p=526</guid>
		<description><![CDATA[
Completed converting one parse utility from previous scripting language to PHP, currently debugging.  Parse utilities will run as cron jobs to control CPU load.
Began writing file upload code, reading up on how files get uploaded via PHP and how to protect the server when permitting file uploads.  I&#8217;m currently thinking that I&#8217;ll upload to a [...]]]></description>
			<content:encoded><![CDATA[<ul>
<li>Completed converting one parse utility from previous scripting language to PHP, currently debugging.  Parse utilities will run as cron jobs to control CPU load.</li>
<li>Began writing file upload code, reading up on how files get uploaded via PHP and how to protect the server when permitting file uploads.  I&#8217;m currently thinking that I&#8217;ll upload to a folder that is not reachable/browsable to prevent scripts/hacks/code from being uploaded.  Retard uploads to prevent non-approved extensions, and then do a file-type check prior to running a cron job against the file to weed out any attempts to upload mis-named JPGs to the parse application.  Not to mention, I need to add a bit to the parse cron job to check if the file is valid or not and ban the user/ip from accessing Xtools again if they attempt such an action.</li>
</ul>
]]></content:encoded>
			<wfw:commentRss>http://www.datarave.net/zfh/2008/09/05/project-diary-xtools-3/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Project Diary: XTools [2]</title>
		<link>http://www.datarave.net/zfh/2008/07/22/project-diary-xtools-2/</link>
		<comments>http://www.datarave.net/zfh/2008/07/22/project-diary-xtools-2/#comments</comments>
		<pubDate>Wed, 23 Jul 2008 00:13:22 +0000</pubDate>
		<dc:creator>John Williams</dc:creator>
				<category><![CDATA[Nortel]]></category>
		<category><![CDATA[Telecom]]></category>
		<category><![CDATA[VoIP]]></category>
		<category><![CDATA[WebDev]]></category>

		<guid isPermaLink="false">http://www.datarave.net/zfh/?p=233</guid>
		<description><![CDATA[Status update:

Expanded code documentation (comments)
Added Site module to project with basic functionality intact.

]]></description>
			<content:encoded><![CDATA[<p>Status update:</p>
<ul>
<li>Expanded code documentation (comments)</li>
<li>Added Site module to project with basic functionality intact.</li>
</ul>
]]></content:encoded>
			<wfw:commentRss>http://www.datarave.net/zfh/2008/07/22/project-diary-xtools-2/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Nortel IP Phone, reset to factory defaults</title>
		<link>http://www.datarave.net/zfh/2008/07/17/nortel-ip-phone-reset-to-factory-defaults/</link>
		<comments>http://www.datarave.net/zfh/2008/07/17/nortel-ip-phone-reset-to-factory-defaults/#comments</comments>
		<pubDate>Thu, 17 Jul 2008 14:00:32 +0000</pubDate>
		<dc:creator>John Williams</dc:creator>
				<category><![CDATA[Nortel]]></category>
		<category><![CDATA[Telecom]]></category>
		<category><![CDATA[VoIP]]></category>

		<guid isPermaLink="false">http://www.datarave.net/zfh/?p=193</guid>
		<description><![CDATA[Resetting a Nortel IP phone just became a lot easier.  Nortel has announced in their Unistim 3.0 documentation the ability to reset a Nortel IP phone to factory default settings.  The following code is required to reset to factory default:

**RENEW[mac]#

Where [mac] is replaced by your MAC address.  Example: If your MAC address is 00:11:22:33:44:55, then [...]]]></description>
			<content:encoded><![CDATA[<p>Resetting a Nortel IP phone just became a lot easier.  Nortel has announced in their Unistim 3.0 documentation the ability to reset a Nortel IP phone to factory default settings.  The following code is required to reset to factory default:</p>
<ul>
<li>**RENEW[mac]#</li>
</ul>
<p>Where [mac] is replaced by your MAC address.  Example: If your MAC address is 00:11:22:33:44:55, then your reset code would be:</p>
<ul>
<li>**73639001122334455#</li>
</ul>
<p>For more information on what the factory default settings are, refer to the Unistim 3.0 Revision 1 product bulletin located on Nortel&#8217;s <a href="http://www.nortel.com/pic" target="_blank">Partner Information Center</a> webpage.</p>
<table border="0">
<tbody>
<tr valign="middle">
<td align="center">
<table style="height: 40px;" border="0" width="80">
<tbody>
<tr>
<td style="background-color: #0000ff; color: #ffffff; font-weight: bold;">NOTE</td>
</tr>
</tbody>
</table>
</td>
<td>You must have valid Nortel Partner credentials to access this bulletin.</td>
</tr>
</tbody>
</table>
]]></content:encoded>
			<wfw:commentRss>http://www.datarave.net/zfh/2008/07/17/nortel-ip-phone-reset-to-factory-defaults/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
