<?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>VoIP for Business &#187; VoIP Implementation</title>
	<atom:link href="http://www.voipforbusiness.biz/category/voip-implementation/feed" rel="self" type="application/rss+xml" />
	<link>http://www.voipforbusiness.biz</link>
	<description>Business grade voip solutions explained.</description>
	<lastBuildDate>Mon, 06 Feb 2012 07:07:40 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>VoIP Implementation Today</title>
		<link>http://www.voipforbusiness.biz/voip-implementation/voip-implemenation-today.html</link>
		<comments>http://www.voipforbusiness.biz/voip-implementation/voip-implemenation-today.html#comments</comments>
		<pubDate>Mon, 24 May 2010 17:36:34 +0000</pubDate>
		<dc:creator>Admin</dc:creator>
				<category><![CDATA[VoIP Implementation]]></category>

		<guid isPermaLink="false">http://www.voipforbusiness.biz/?p=23</guid>
		<description><![CDATA[Implementing a VoIP network is often a relatively straightforward exercise, though it is important to know which areas need to be considered. We would suggest the following key areas are looked into- Network capacity Network devices (routers, switches, etc) have the capacity and QoS features required for voice traffic LAN and WAN utilisation Interaction with, [...]
No related posts.

Related posts brought to you by <a href='http://yarpp.org'>Yet Another Related Posts Plugin</a>.]]></description>
			<content:encoded><![CDATA[<p>Implementing a VoIP network is often a relatively straightforward exercise, though it is important to know which areas need to be considered. We would suggest the following key areas are looked into-</p>
<p>Network capacity<br />
Network devices (routers, switches, etc) have the capacity and QoS features required for voice traffic<br />
LAN and WAN utilisation<br />
Interaction with, and affect on, data applications<br />
Effectiveness of network-optimisation tools to maximize utilization through compression and latency-reduction techniques</p>
<p>Disaster recovery<br />
Duplication of major PBX nodes (dependin on your chosen VoIp solution)<br />
Fallback to POTS (Plain Old Telephone System) at all or strategic locations<br />
Protection against loss of power and power spikes<br />
Emergency use mobile phones (which could be pay-as-you-go)<br />
Emergency facilities with pre-provisioned network connections<br />
Re-routing via the public internet</p>
<p>Security (also outlined as a seperate link)<br />
Denial of Service (DOS). Attacks via a weakly protected VoIP element could flood the network disabling data applications, or conversely a DOS attack on a data application could inhibit voice traffic.<br />
Hackers making free use of the telephone system, for example by fooled billing (making the call appear to terminate internally when, in fact, it continues externally).<br />
Snooping on network traffic, soft phones and voicemail by various devices, or by call hijacking (routing a call to a different destination).</p>
<p>Standards<br />
H.323 (Packet-based multimedia communications systems) issued by the ITU<br />
SIP (Session Initiation Protocol) issued by the IETF</p>
<p>There are also other, proprietary protocols in use, for example Skype.</p>
<p>No related posts.</p>
<p>Related posts brought to you by <a href='http://yarpp.org'>Yet Another Related Posts Plugin</a>.</p>]]></content:encoded>
			<wfw:commentRss>http://www.voipforbusiness.biz/voip-implementation/voip-implemenation-today.html/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

