<?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>AdamJobbins.com &#187; Technology</title>
	<atom:link href="http://www.adamjobbins.com/category/technology/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.adamjobbins.com</link>
	<description>Official Homepage of Adam Jobbins, Wellington, NZ</description>
	<lastBuildDate>Tue, 07 Sep 2010 21:23:17 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
		<item>
		<title>Number Plans for your VoIP PBX in New Zealand</title>
		<link>http://www.adamjobbins.com/number-plans-for-your-voip-pbx-in-new-zealand/</link>
		<comments>http://www.adamjobbins.com/number-plans-for-your-voip-pbx-in-new-zealand/#comments</comments>
		<pubDate>Mon, 20 Jul 2009 01:11:56 +0000</pubDate>
		<dc:creator>Adam Jobbins</dc:creator>
				<category><![CDATA[Technology]]></category>
		<category><![CDATA[VoIP]]></category>
		<category><![CDATA[Voice]]></category>
		<category><![CDATA[Asterisk]]></category>
		<category><![CDATA[dialplan]]></category>
		<category><![CDATA[SIP]]></category>
		<category><![CDATA[trixbox]]></category>

		<guid isPermaLink="false">http://www.adamjobbins.com/blog/?p=38</guid>
		<description><![CDATA[IP PBX systems, such as those based on Asterisk provide a great deal of flexability and configurability. Gone are the days where we need to program these systems to need a number dialled to access an outside line. In this post I will go over some of my recommendations for how to number and set]]></description>
			<content:encoded><![CDATA[<p>IP PBX systems, such as those based on Asterisk provide a great deal of flexability and configurability. Gone are the days where we need to program these systems to need a number dialled to access an outside line. In this post I will go over some of my recommendations for how to number and set our your internal extenstions and destinations, to simplfy both internal and external dialing for your users.</p>
<p>This post applies to New Zealand systems only, as the recommendations are based on the current New Zealand <a title="NAD" href="http://www.nad.org.nz/">Number Administration Deed</a></p>
<p><span id="more-38"></span><strong>Recommendation &#8211; Dial &#8217;7&#8242; for internal</strong></p>
<p>I have found that &#8217;7&#8242; seems to be the least common start digit for local NZ Number (The exceptions being a couple of regions in the 03 and 06 calling ranges &#8211; see caveat below)</p>
<p>It is my suggestion that you use &#8217;7&#8242; to lead all of your internal number on your system. The reason for this is with nothing else in this range external to your organisation, it is an easy way for you to destinguish internal and external calls at the dialplan level, speeding up dialing at the endpoint, and eliminating the need for a number to access an &#8216;outside line&#8217;.</p>
<p>Use &#8217;7&#8242; for all of your internal destinations, not just extension numbering, but any other dialable numbers like ring groups, hunt groups, PBX Features like Voicemail, Directory etc., IVRs and anything else dialable. Plan your numbering in advance and keep it <span style="font-size: small;">Consistant </span>(Same number of digits).</p>
<p>As a guide, assume that you may need up to 2x the numbering space as you expect to have users. This includes remote users or users who share desks. Use headcount rather than desk count here. Plan ahead &#8211; Don&#8217;t create extension space for 50 users if you know (Or even imagine) the organisation could have 500, or even 5000 users some time in the future. You don&#8217;t want to have to re-number every extension in the organisation at some point in the future.</p>
<p>The below table should give you an idea of the lenth you should make your numbering ranges, based on how many users you expect at peak</p>
<p><!--[if gte mso 9]><xml> <w :WordDocument> </w><w :View>Normal</w> <w :Zoom>0</w> <w :PunctuationKerning /> <w :ValidateAgainstSchemas /> <w :SaveIfXMLInvalid>false</w> <w :IgnoreMixedContent>false</w> <w :AlwaysShowPlaceholderText>false</w> <w :Compatibility> <w :BreakWrappedTables /> <w :SnapToGridInCell /> <w :WrapTextWithPunct /> <w :UseAsianBreakRules /> <w :DontGrowAutofit /> </w> <w :BrowserLevel>MicrosoftInternetExplorer4</w> </xml>< ![endif]--><!--[if gte mso 9]><xml> <w :LatentStyles DefLockedState="false" LatentStyleCount="156"> </w> </xml>< ![endif]--><!--  /* Style Definitions */  p.MsoNormal, li.MsoNormal, div.MsoNormal 	{mso-style-parent:""; 	margin:0cm; 	margin-bottom:.0001pt; 	mso-pagination:widow-orphan; 	font-size:12.0pt; 	font-family:"Times New Roman"; 	mso-fareast-font-family:"Times New Roman";} @page Section1 	{size:612.0pt 792.0pt; 	margin:72.0pt 90.0pt 72.0pt 90.0pt; 	mso-header-margin:36.0pt; 	mso-footer-margin:36.0pt; 	mso-paper-source:0;} div.Section1 	{page:Section1;} --><!--[if gte mso 10]> <mce :style>< !   /* Style Definitions */  table.MsoNormalTable 	{mso-style-name:"Table Normal"; 	mso-tstyle-rowband-size:0; 	mso-tstyle-colband-size:0; 	mso-style-noshow:yes; 	mso-style-parent:""; 	mso-padding-alt:0cm 5.4pt 0cm 5.4pt; 	mso-para-margin:0cm; 	mso-para-margin-bottom:.0001pt; 	mso-pagination:widow-orphan; 	font-size:10.0pt; 	font-family:"Times New Roman"; 	mso-ansi-language:#0400; 	mso-fareast-language:#0400; 	mso-bidi-language:#0400;} table.MsoTableGrid 	{mso-style-name:"Table Grid"; 	mso-tstyle-rowband-size:0; 	mso-tstyle-colband-size:0; 	border:solid windowtext 1.0pt; 	mso-border-alt:solid windowtext .5pt; 	mso-padding-alt:0cm 5.4pt 0cm 5.4pt; 	mso-border-insideh:.5pt solid windowtext; 	mso-border-insidev:.5pt solid windowtext; 	mso-para-margin:0cm; 	mso-para-margin-bottom:.0001pt; 	mso-pagination:widow-orphan; 	font-size:10.0pt; 	font-family:"Times New Roman"; 	mso-ansi-language:#0400; 	mso-fareast-language:#0400; 	mso-bidi-language:#0400;} --> <!--[endif]--></p>
<table class="MsoTableGrid" style="border: medium none ; border-collapse: collapse;" border="1" cellspacing="0" cellpadding="0">
<tbody>
<tr>
<td style="border: 1pt solid windowtext; padding: 0cm 5.4pt; width: 147.6pt;" width="197" valign="top">
<p class="MsoNormal"><strong>Number of Users</strong></p>
</td>
<td style="padding: 0cm 5.4pt; width: 147.6pt;" width="197" valign="top">
<p class="MsoNormal"><strong>Number of Digits</strong></p>
</td>
</tr>
<tr>
<td style="padding: 0cm 5.4pt; width: 147.6pt;" width="197" valign="top">
<p class="MsoNormal">1-5</p>
</td>
<td style="padding: 0cm 5.4pt; width: 147.6pt;" width="197" valign="top">
<p class="MsoNormal">2</p>
</td>
</tr>
<tr>
<td style="padding: 0cm 5.4pt; width: 147.6pt;" width="197" valign="top">
<p class="MsoNormal">6-50</p>
</td>
<td style="padding: 0cm 5.4pt; width: 147.6pt;" width="197" valign="top">
<p class="MsoNormal">3</p>
</td>
</tr>
<tr>
<td style="padding: 0cm 5.4pt; width: 147.6pt;" width="197" valign="top">
<p class="MsoNormal">51-500</p>
</td>
<td style="padding: 0cm 5.4pt; width: 147.6pt;" width="197" valign="top">
<p class="MsoNormal">4</p>
</td>
</tr>
<tr>
<td style="padding: 0cm 5.4pt; width: 147.6pt;" width="197" valign="top">
<p class="MsoNormal">501-5,000</p>
</td>
<td style="padding: 0cm 5.4pt; width: 147.6pt;" width="197" valign="top">
<p class="MsoNormal">5</p>
</td>
</tr>
<tr>
<td style="padding: 0cm 5.4pt; width: 147.6pt;" width="197" valign="top">
<p class="MsoNormal">5,001-50,000</p>
</td>
<td style="padding: 0cm 5.4pt; width: 147.6pt;" width="197" valign="top">
<p class="MsoNormal">6</p>
</td>
</tr>
</tbody>
</table>
<p><em>Caveat: </em>If you are in one of the few local calling area where there are local numbers starting with 7 you will need to modify this strategy. My recommendation would be to either A) Require area code dialing on all calls, local included or B) Modify your dial plan to allow for the additional digits required to have local and extension numbers in the same rule. This would mean, depending on your setup, you may need a timeout to start dialing on the shorter extension numbers, or if your device allows it, press # or &#8216;Dial&#8217; to proceed the call.</mce></p>
]]></content:encoded>
			<wfw:commentRss>http://www.adamjobbins.com/number-plans-for-your-voip-pbx-in-new-zealand/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Productivity gains to business of deploying Blackberry</title>
		<link>http://www.adamjobbins.com/productivity-gains-to-business-of-deploying-blackberry/</link>
		<comments>http://www.adamjobbins.com/productivity-gains-to-business-of-deploying-blackberry/#comments</comments>
		<pubDate>Sun, 14 Jun 2009 00:54:30 +0000</pubDate>
		<dc:creator>Adam Jobbins</dc:creator>
				<category><![CDATA[Mobile]]></category>
		<category><![CDATA[Technology]]></category>
		<category><![CDATA[Voice]]></category>
		<category><![CDATA[Blackberry]]></category>
		<category><![CDATA[Study]]></category>

		<guid isPermaLink="false">http://www.adamjobbins.com/blog/?p=24</guid>
		<description><![CDATA[I came across an article earlier today analyzing the return on investment of deploying a Blackberry solution in an enterprise. The study is published on the Blackberry website (here) so should probably be taken with a grain of salt for obvious reasons, however I find it&#8217;s results quite interesting. The report suggests that &#8220;typical (median)]]></description>
			<content:encoded><![CDATA[<p>I came across an article earlier today analyzing the return on investment of deploying a Blackberry solution in an enterprise.</p>
<p>The study is published on the Blackberry website (<a href="http://www.blackberry.com/downloads/wes_presentation/Analyzing_ROI_of_a_BlackBerry_Deployment-2007.pdf" target="_blank">here</a>) so should probably be taken with a grain of salt for obvious reasons, however I find it&#8217;s results quite interesting.</p>
<p>The report suggests that &#8220;typical (median) end user converts 60 minutes of downtime into productive time per day&#8221; &#8211; That is one hour per day that the average user would be being paid for where they are not not productive into productive time &#8211; And the survey states they have taken a conservative approach.</p>
<p>For a person on a $40,000 salary, this equates to $5,000 per year of recovered productivity!</p>
<p>There are issues that the analysis does not cover, such as the social impacts of a constant connection to work, but from a business point of view the numbers sure do seem to stack up.</p>
<p>The survey puts the TCO at about $1,325 PA, so if the number are correct, that is a huge benifit to business.</p>
<p>I don&#8217;t use a Blackberry myself, any out of office email I do for work is done on a Laptop over a VPN connection. For those of you who DO use one, do you agree with the finding above?</p>
]]></content:encoded>
			<wfw:commentRss>http://www.adamjobbins.com/productivity-gains-to-business-of-deploying-blackberry/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
	</channel>
</rss>
