Training:Verify Network - Revision history

Tyler: /* Optimizing the Network for Voice Traffic: A Comprehensive Guide */

2023-11-13T17:33:47Z

Optimizing the Network for Voice Traffic: A Comprehensive Guide

← Older revision		Revision as of 17:33, 13 November 2023
Line 1:		Line 1:
	== Optimizing the Network for Voice Traffic: ~~A Comprehensive Guide~~ ==		== Optimizing the Network for Voice Traffic: ==

	==== Introduction ====		==== Introduction ====

Tyler: /* Confirming the network is optimized for voice */

2023-11-13T17:15:03Z

Confirming the network is optimized for voice

← Older revision		Revision as of 17:15, 13 November 2023
Line 1:		Line 1:
	== ~~Confirming~~ the ~~network is optimized~~ for ~~voice<br/>~~ ==		== Optimizing the Network for Voice Traffic: A Comprehensive Guide ==

	Voice over IP ~~is already widespread in~~ enterprise ~~networks~~ and ~~is growing in~~ public switched voice networks ~~as carriers migrate from TDM~~ to ~~VoIP~~.		==== Introduction ====
			As Voice over IP (VoIP) technology increasingly permeates enterprise and public switched voice networks, the importance of a network optimized for voice cannot be overstated. While non-voice networks may appear to function adequately, latent issues often come to light only when the more demanding requirements of voice packet transmission are introduced.

	A network that appears to function adequately without voice can give the impression that there are no underlying network problems. Users become accustomed to using what they have and assume that the network is functioning well. In reality there can be issues that are unknown until packet transmission of voice is introduced. For instance if an email arrives a few seconds late it is not obvious to users that there is a delay in the network. However a few seconds in a voice transmission is unacceptable. It stands to reason that the cause of the delay in email may go unresolved without raising any noticeable performance lag to users. However, such a condition must be resolved in a voice network.		==== Understanding Network Performance for Voice ====

	Quality of Service (~~QOS~~) is ~~a mechanism to assure that~~ voice packets ~~have priority~~ over other data ~~packets~~.		* Latency and Packet Transmission: Unlike data packets, voice packets are extremely sensitive to delays. A delay that is imperceptible in email transmission can be detrimental in voice communication.
			* Quality of Service (QoS): Implementing QoS is critical. It prioritizes voice packets over other types of data, ensuring smooth and uninterrupted voice communication.

	~~There are basic steps that should be taken~~ to ~~optimize~~ a ~~network~~ for ~~voice traffic.~~		==== Steps to Optimize a Network for Voice ====

	#~~The~~ Switches ~~should be~~ managed switches that support ~~QOS~~. ~~Recommendations:~~		# Managed Switches with QoS: Employ managed switches that support Quality of Service.
	#~~#QOS capable data~~ switches ~~(QOS settings~~ are configured ~~in the Smart Switch)~~		#* QoS Capable Switches: Ensure switches are configured for optimal QoS.
	#~~#POE data~~ switches are ~~highly~~ recommended in VoIP applications		#* Power Over Ethernet (PoE) Switches: PoE switches are recommended for VoIP applications.
	##UPS ~~is highly recommended<br/>Note~~: ~~backing up the POE extends power to telephones~~ during a power ~~outage~~.		#* Uninterruptible Power Supply (UPS): A UPS ensures continuity during power outages, maintaining telephone connectivity.
	#The ~~entire~~ network ~~infrastructure~~ should be at minimum Certified CAT 5e		# Network Infrastructure: The network should be at minimum Certified CAT 5e.
	#If ~~item 2 is not met upon inspection~~, ~~you should consider~~ to ~~be prepared to quote for~~ wiring and equipment ~~to get the infrastructure of the network to this status~~.		#* If the current infrastructure doesn't meet this standard, prepare to upgrade the wiring and equipment.
	#~~Make certain that your quote covers your~~ costs ~~and~~ expenses and labor~~. It is always best to do this before any new IP PBX is placed on the network so that you can be confident of the network and its ability to carry voice traffic~~.		#* Include all costs, expenses, and labor in your quote.
	#~~Consider~~ a network analysis to ~~analyze the Network for possible pitfalls~~. MicroConvergent ~~is a good option~~.		# Network Analysis: Conduct a thorough network analysis to identify potential issues. Consider using services like MicroConvergent for this task.
	#~~If you are not the manager of this DATA network then you should develop~~ a good relationship with the IT management team ~~for this network as their assistance will prove invaluable to you.~~		# Collaboration with IT Management: Foster a good relationship with the IT management team, especially if you are not managing the data network.
	~~#After the network is certified for voice~~, you ~~should test it.~~
	~~##Certified Category 5 cabling~~
	~~##Smart Data Switches with QOS enabled and configured~~
	~~##Recommended use of POE~~
	~~##For applications for Remote Phones~~ the Router must be capable of supporting multiple NAT sessions (see IPitomy’s list of known performing routers)<br/>[http://www.ipitomy.com/webrelease/IPitomy/Router%20Compatibility%20Guide.pdf http://www.ipitomy.com/webrelease/IPitomy/Router%20Compatibility%20Guide.pdf]
	#It is also recommended that you certify the bandwidth is appropriate for what is required for remote users and SIP Trunks. Technically using the standard G.711 CODEC each voice conversation uses 64kbs send 64kbs receive. With SIP overhead this is increased to approximately 80kbs. To simplify calculations we recommend using a round number of 200Kb (kilo bits) of symmetrical bandwidth for each concurrent voice call. (100Kb Send/100Kb Receive)
	~~##Most~~ data connections are asymmetrical – meaning that there is a difference in speed upload versus download. Usually expressed as 10Dn/5Up… the VoIP connection can be no greater than the lesser bandwidth rate.
	~~##Keep in mind that some connections fluctuate at times during the day and your connection will only ever be as good as the weakest link.~~
	~~##Always recommend proper equipment for the job to avoid the pitfalls and traps of old existing Networks with aging performance issues.~~
	##If the DATA Network is managed by another team you should provide them with a checklist and a proof of assurance document that they may sign off on which provides you with verification that your requirements for the Voice network ~~are in fact being met. Any changes to meet the requirements must be completed before the day of installation without incurring additional labors costs~~.

	~~Checklist:~~		==== Testing and Certification ====

	~~#IP Address of~~ the ~~IP PBX~~ is ~~identified and verified available (Ping IP PBX IP Address to assure that no device is using the address~~.)		* Ensure the network is certified for voice traffic. This includes:
	~~#Establish IP Address range for DHCP use~~		** Certified Category 5 cabling.
	~~#Disclose any Static IP Addresses currently in use~~.		** Smart Data Switches with configured QoS.
	~~#POE capable, QOS capable Switch(es)~~		** PoE implementation.
	#For applications ~~with Remote Phones - Router capable of~~ multiple NAT sessions ~~(use)~~.		* For remote phone applications, ensure the router supports multiple NAT sessions. Refer to IPitomy's router compatibility guide.
	~~#Ports in~~ router ~~forwarded to PBX for remote phones (5060, 10,000 – 20,000)~~		* Verify adequate bandwidth for remote users and SIP Trunks. A standard guideline is 200Kb of symmetrical bandwidth for each concurrent voice call (G.711 CODEC).
	~~#Ports in router forwarded to the PBX~~ for remote ~~maintenance (Port 80)~~
	~~#Ports in router forwarded to the PBX~~ for ~~Branch Office use~~ (~~Port 4569)~~
	~~#Ports in router forwarded to the PBX for Factory support access (Port 22~~)

	~~The prior analysis provided~~ in the ~~outline above will best assure~~ that you ~~have~~ a successful ~~and prosperous~~ IPitomy install~~. It also outlines a means of successful integration~~ and a ~~continuing good working~~ relationship with existing IT personnel.		==== Bandwidth Considerations ====

			* Most data connections are asymmetrical. Ensure the VoIP connection aligns with the lesser bandwidth rate.
			* Account for fluctuations in connection speeds throughout the day.

			==== Equipment and Collaboration ====

			* Always recommend appropriate equipment to avoid issues with outdated networks.
			* If the data network is managed by another team, provide a checklist and a proof of assurance document for them to sign off on. This verifies that your voice network requirements are being met.

			==== Checklist for Network Readiness ====

			* Verify the IP address of the IP PBX.
			* Establish the IP address range for DHCP use.
			* Disclose any static IP addresses in use.
			* Ensure switches are PoE capable and QoS enabled.
			* For remote phones, confirm the router's capability for multiple NAT sessions.
			* Set up necessary port forwarding to the PBX (ports 5060, 10000-20000 for remote phones, port 80 for remote maintenance, port 4569 for branch office use, and port 22 for factory support access).

			==== Conclusion ====
			By following the guidelines and checklist provided, you can ensure a successful IPitomy install and foster a positive, ongoing relationship with existing IT personnel. This comprehensive approach is key to integrating VoIP into your network effectively and maintaining high performance standards.
	[[Category:Training]]		[[Category:Training]]

Mike Lunn at 16:28, 8 December 2021

2021-12-08T16:28:19Z

← Older revision		Revision as of 16:28, 8 December 2021
Line 42:		Line 42:

	The prior analysis provided in the outline above will best assure that you have a successful and prosperous IPitomy install. It also outlines a means of successful integration and a continuing good working relationship with existing IT personnel.		The prior analysis provided in the outline above will best assure that you have a successful and prosperous IPitomy install. It also outlines a means of successful integration and a continuing good working relationship with existing IT personnel.
			[[Category:Training]]

Paul Falanga at 21:16, 2 November 2012

2012-11-02T21:16:05Z

← Older revision		Revision as of 21:16, 2 November 2012
Line 10:		Line 10:

	#The Switches should be managed switches that support QOS. Recommendations:		#The Switches should be managed switches that support QOS. Recommendations:
			##QOS capable data switches (QOS settings are configured in the Smart Switch)
	*QOS capable data switches (QOS settings are configured in the Smart Switch)		##POE data switches are highly recommended in VoIP applications
	*POE data switches are highly recommended in VoIP applications		##UPS is highly recommended<br/>Note: backing up the POE extends power to telephones during a power outage.
	*UPS is highly recommended<br/>Note: backing up the POE extends power to telephones during a power outage.

	#The entire network infrastructure should be at minimum Certified CAT 5e		#The entire network infrastructure should be at minimum Certified CAT 5e
	#If item 2 is not met upon inspection, you should consider to be prepared to quote for wiring and equipment to get the infrastructure of the network to this status.		#If item 2 is not met upon inspection, you should consider to be prepared to quote for wiring and equipment to get the infrastructure of the network to this status.
Line 21:		Line 19:
	#If you are not the manager of this DATA network then you should develop a good relationship with the IT management team for this network as their assistance will prove invaluable to you.		#If you are not the manager of this DATA network then you should develop a good relationship with the IT management team for this network as their assistance will prove invaluable to you.
	#After the network is certified for voice, you should test it.		#After the network is certified for voice, you should test it.
			##Certified Category 5 cabling
			##Smart Data Switches with QOS enabled and configured
			##Recommended use of POE
			##For applications for Remote Phones the Router must be capable of supporting multiple NAT sessions (see IPitomy’s list of known performing routers)<br/>[http://www.ipitomy.com/webrelease/IPitomy/Router%20Compatibility%20Guide.pdf http://www.ipitomy.com/webrelease/IPitomy/Router%20Compatibility%20Guide.pdf]
			#It is also recommended that you certify the bandwidth is appropriate for what is required for remote users and SIP Trunks. Technically using the standard G.711 CODEC each voice conversation uses 64kbs send 64kbs receive. With SIP overhead this is increased to approximately 80kbs. To simplify calculations we recommend using a round number of 200Kb (kilo bits) of symmetrical bandwidth for each concurrent voice call. (100Kb Send/100Kb Receive)
			##Most data connections are asymmetrical – meaning that there is a difference in speed upload versus download. Usually expressed as 10Dn/5Up… the VoIP connection can be no greater than the lesser bandwidth rate.
			##Keep in mind that some connections fluctuate at times during the day and your connection will only ever be as good as the weakest link.
			##Always recommend proper equipment for the job to avoid the pitfalls and traps of old existing Networks with aging performance issues.
			##If the DATA Network is managed by another team you should provide them with a checklist and a proof of assurance document that they may sign off on which provides you with verification that your requirements for the Voice network are in fact being met. Any changes to meet the requirements must be completed before the day of installation without incurring additional labors costs.

	*Certified Category 5 cabling		Checklist:
	*Smart Data Switches with QOS enabled and configured

	*Recommended use of POE

	*For applications for Remote Phones the Router must be capable of supporting multiple NAT sessions (see IPitomy’s list of known performing routers)<br/>[http://www.ipitomy.com/webrelease/IPitomy/Router%20Compatibility%20Guide.pdf http://www.ipitomy.com/webrelease/IPitomy/Router%20Compatibility%20Guide.pdf]

	#It is also recommended that you certify the bandwidth is appropriate for what is required for remote users and SIP Trunks. Technically using the standard G.711 CODEC each voice conversation uses 64kbs send 64kbs receive. With SIP overhead this is increased to approximately 80kbs. To simplify calculations we recommend using a round number of 200Kb (kilo bits) of symmetrical bandwidth for each concurrent voice call. (100Kb Send/100Kb Receive)<ol style="list-style-type:lower-alpha;">
	~~</ol></ol>~~

	*Most data connections are asymmetrical – meaning that there is a difference in speed upload versus download. Usually expressed as 10Dn/5Up… the VoIP connection can be no greater than the lesser bandwidth rate.
	*Keep in mind that some connections fluctuate at times during the day and your connection will only ever be as good as the weakest link.
	*Always recommend proper equipment for the job to avoid the pitfalls and traps of old existing Networks with aging performance issues.<br/></li>
	*If the DATA Network is managed by another team you should provide them with a checklist and a proof of assurance document that they may sign off on which provides you with verification that your requirements for the Voice network are in fact being met. Any changes to meet the requirements must be completed before the day of installation without incurring additional labors costs.<ol style="list-style-type:lower-alpha;">
	~~</ol></ul>~~

	*Checklist:

	**IP Address of the IP PBX is identified and verified available (Ping IP PBX IP Address to assure that no device is using the address.)		#IP Address of the IP PBX is identified and verified available (Ping IP PBX IP Address to assure that no device is using the address.)
	**Establish IP Address range for DHCP use		#Establish IP Address range for DHCP use
	**Disclose any Static IP Addresses currently in use.		#Disclose any Static IP Addresses currently in use.
	**POE capable, QOS capable Switch(es)		#POE capable, QOS capable Switch(es)
	**For applications with Remote Phones - Router capable of multiple NAT sessions (use).		#For applications with Remote Phones - Router capable of multiple NAT sessions (use).
	~~***~~Ports in router forwarded to PBX for remote phones~~<br/>~~(5060, 10,000 – 20,000)		#Ports in router forwarded to PBX for remote phones (5060, 10,000 – 20,000)
	**Ports in router forwarded to the PBX for remote maintenance~~<br/>~~(Port 80)		#Ports in router forwarded to the PBX for remote maintenance (Port 80)
	**Ports in router forwarded to the PBX for Branch Office use~~<br/>~~(Port 4569)		#Ports in router forwarded to the PBX for Branch Office use (Port 4569)
	**Ports in router forwarded to the PBX for Factory support access~~<br/>~~(Port 22)		#Ports in router forwarded to the PBX for Factory support access (Port 22)

	The prior analysis provided in the outline above will best assure that you have a successful and prosperous IPitomy install. It also outlines a means of successful integration and a continuing good working relationship with existing IT personnel.		The prior analysis provided in the outline above will best assure that you have a successful and prosperous IPitomy install. It also outlines a means of successful integration and a continuing good working relationship with existing IT personnel.

Nick Branica at 18:36, 25 September 2012

2012-09-25T18:36:52Z

← Older revision		Revision as of 18:36, 25 September 2012
Line 36:		Line 36:
	*Always recommend proper equipment for the job to avoid the pitfalls and traps of old existing Networks with aging performance issues.<br/></li>		*Always recommend proper equipment for the job to avoid the pitfalls and traps of old existing Networks with aging performance issues.<br/></li>
	*If the DATA Network is managed by another team you should provide them with a checklist and a proof of assurance document that they may sign off on which provides you with verification that your requirements for the Voice network are in fact being met. Any changes to meet the requirements must be completed before the day of installation without incurring additional labors costs.<ol style="list-style-type:lower-alpha;">		*If the DATA Network is managed by another team you should provide them with a checklist and a proof of assurance document that they may sign off on which provides you with verification that your requirements for the Voice network are in fact being met. Any changes to meet the requirements must be completed before the day of installation without incurring additional labors costs.<ol style="list-style-type:lower-alpha;">
	<li>~~Checklist:~~</li>		</ol></ul>
	~~</ol></li>~~
	~~</ol>~~		*Checklist:

	**IP Address of the IP PBX is identified and verified available (Ping IP PBX IP Address to assure that no device is using the address.)		**IP Address of the IP PBX is identified and verified available (Ping IP PBX IP Address to assure that no device is using the address.)
Line 49:		Line 49:
	**Ports in router forwarded to the PBX for Branch Office use<br/>(Port 4569)		**Ports in router forwarded to the PBX for Branch Office use<br/>(Port 4569)
	**Ports in router forwarded to the PBX for Factory support access<br/>(Port 22)		**Ports in router forwarded to the PBX for Factory support access<br/>(Port 22)

	The prior analysis provided in the outline above will best assure that you have a successful and prosperous IPitomy install. It also outlines a means of successful integration and a continuing good working relationship with existing IT personnel.		The prior analysis provided in the outline above will best assure that you have a successful and prosperous IPitomy install. It also outlines a means of successful integration and a continuing good working relationship with existing IT personnel.

	~~Questions:~~

	*#What is the basic network requirement to optimize a network for VoIP?
	*#What type of data switch should be used in a voice network?
	*#What is the approximate bandwidth requirement for a G.711 coded voice call?
	*#What is the primary advantage of using POE?
	*#What is the network component where QOS is setup?

Paul Falanga at 20:34, 13 September 2012

2012-09-13T20:34:15Z

← Older revision		Revision as of 20:34, 13 September 2012
Line 1:		Line 1:
	= Confirming the network is optimized for voice<br/> =		== Confirming the network is optimized for voice<br/> ==

	Voice over IP is already widespread in enterprise networks and is growing in public switched voice networks as carriers migrate from TDM to VoIP.		Voice over IP is already widespread in enterprise networks and is growing in public switched voice networks as carriers migrate from TDM to VoIP.
Line 30:		Line 30:

	#It is also recommended that you certify the bandwidth is appropriate for what is required for remote users and SIP Trunks. Technically using the standard G.711 CODEC each voice conversation uses 64kbs send 64kbs receive. With SIP overhead this is increased to approximately 80kbs. To simplify calculations we recommend using a round number of 200Kb (kilo bits) of symmetrical bandwidth for each concurrent voice call. (100Kb Send/100Kb Receive)<ol style="list-style-type:lower-alpha;">		#It is also recommended that you certify the bandwidth is appropriate for what is required for remote users and SIP Trunks. Technically using the standard G.711 CODEC each voice conversation uses 64kbs send 64kbs receive. With SIP overhead this is increased to approximately 80kbs. To simplify calculations we recommend using a round number of 200Kb (kilo bits) of symmetrical bandwidth for each concurrent voice call. (100Kb Send/100Kb Receive)<ol style="list-style-type:lower-alpha;">
	<li>Most data connections are asymmetrical – meaning that there is a difference in speed upload versus download. Usually expressed as 10Dn/5Up… the VoIP connection can be no greater than the lesser bandwidth rate.~~</li>~~		</ol></ol>
	~~<li>~~Keep in mind that some connections fluctuate at times during the day and your connection will only ever be as good as the weakest link.~~<br/></li>~~
	~~</ol><li>~~Always recommend proper equipment for the job to avoid the pitfalls and traps of old existing Networks with aging performance issues.<br/></li>		*Most data connections are asymmetrical – meaning that there is a difference in speed upload versus download. Usually expressed as 10Dn/5Up… the VoIP connection can be no greater than the lesser bandwidth rate.
	~~<li>~~If the DATA Network is managed by another team you should provide them with a checklist and a proof of assurance document that they may sign off on which provides you with verification that your requirements for the Voice network are in fact being met. Any changes to meet the requirements must be completed before the day of installation without incurring additional labors costs.~~<br/>~~<ol style="list-style-type:lower-alpha;">		*Keep in mind that some connections fluctuate at times during the day and your connection will only ever be as good as the weakest link.
			*Always recommend proper equipment for the job to avoid the pitfalls and traps of old existing Networks with aging performance issues.<br/></li>
			*If the DATA Network is managed by another team you should provide them with a checklist and a proof of assurance document that they may sign off on which provides you with verification that your requirements for the Voice network are in fact being met. Any changes to meet the requirements must be completed before the day of installation without incurring additional labors costs.<ol style="list-style-type:lower-alpha;">
	<li>Checklist:</li>		<li>Checklist:</li>
	</ol></li>		</ol></li>
	</ol>		</ol>

	*IP Address of the IP PBX is identified and verified available (Ping IP PBX IP Address to assure that no device is using the address.)
	*Establish IP Address range for DHCP use
	*Disclose any Static IP Addresses currently in use.
	*POE capable, QOS capable Switch(es)
	*For applications with Remote Phones - Router capable of multiple NAT sessions (use).
	**Ports in router forwarded to PBX for remote phones<br/>(5060, 10,000 – 20,000)
	*Ports in router forwarded to the PBX for remote maintenance<br/>(Port 80)
	*Ports in router forwarded to the PBX for Branch Office use<br/>(Port 4569)
	*Ports in router forwarded to the PBX for Factory support access<br/>(Port 22)

			**IP Address of the IP PBX is identified and verified available (Ping IP PBX IP Address to assure that no device is using the address.)
			**Establish IP Address range for DHCP use
			**Disclose any Static IP Addresses currently in use.
			**POE capable, QOS capable Switch(es)
			**For applications with Remote Phones - Router capable of multiple NAT sessions (use).
			***Ports in router forwarded to PBX for remote phones<br/>(5060, 10,000 – 20,000)
			**Ports in router forwarded to the PBX for remote maintenance<br/>(Port 80)
			**Ports in router forwarded to the PBX for Branch Office use<br/>(Port 4569)
			**Ports in router forwarded to the PBX for Factory support access<br/>(Port 22)
	The prior analysis provided in the outline above will best assure that you have a successful and prosperous IPitomy install. It also outlines a means of successful integration and a continuing good working relationship with existing IT personnel.		The prior analysis provided in the outline above will best assure that you have a successful and prosperous IPitomy install. It also outlines a means of successful integration and a continuing good working relationship with existing IT personnel.

	Questions:		Questions:

	#What is the basic network requirement to optimize a network for VoIP?		*#What is the basic network requirement to optimize a network for VoIP?
	#What type of data switch should be used in a voice network?		*#What type of data switch should be used in a voice network?
	#What is the approximate bandwidth requirement for a G.711 coded voice call?		*#What is the approximate bandwidth requirement for a G.711 coded voice call?
	#What is the primary advantage of using POE?		*#What is the primary advantage of using POE?
	#What is the network component where QOS is setup?		*#What is the network component where QOS is setup?

Paul Falanga: Created page with "= Confirming the network is optimized for voice
= Voice over IP is already widespread in enterprise networks and is growing in public switched voice networks as carriers..."

2012-09-13T20:33:07Z

Created page with "= Confirming the network is optimized for voice = Voice over IP is already widespread in enterprise networks and is growing in public switched voice networks as carriers..."

New page

= Confirming the network is optimized for voice =

Voice over IP is already widespread in enterprise networks and is growing in public switched voice networks as carriers migrate from TDM to VoIP.

A network that appears to function adequately without voice can give the impression that there are no underlying network problems. Users become accustomed to using what they have and assume that the network is functioning well. In reality there can be issues that are unknown until packet transmission of voice is introduced. For instance if an email arrives a few seconds late it is not obvious to users that there is a delay in the network. However a few seconds in a voice transmission is unacceptable. It stands to reason that the cause of the delay in email may go unresolved without raising any noticeable performance lag to users. However, such a condition must be resolved in a voice network.

Quality of Service (QOS) is a mechanism to assure that voice packets have priority over other data packets.

There are basic steps that should be taken to optimize a network for voice traffic.

#The Switches should be managed switches that support QOS. Recommendations:

*QOS capable data switches (QOS settings are configured in the Smart Switch)
*POE data switches are highly recommended in VoIP applications
*UPS is highly recommended Note: backing up the POE extends power to telephones during a power outage.

#The entire network infrastructure should be at minimum Certified CAT 5e
#If item 2 is not met upon inspection, you should consider to be prepared to quote for wiring and equipment to get the infrastructure of the network to this status.
#Make certain that your quote covers your costs and expenses and labor. It is always best to do this before any new IP PBX is placed on the network so that you can be confident of the network and its ability to carry voice traffic.
#Consider a network analysis to analyze the Network for possible pitfalls. MicroConvergent is a good option.
#If you are not the manager of this DATA network then you should develop a good relationship with the IT management team for this network as their assistance will prove invaluable to you.
#After the network is certified for voice, you should test it.

*Certified Category 5 cabling
*Smart Data Switches with QOS enabled and configured

*Recommended use of POE

*For applications for Remote Phones the Router must be capable of supporting multiple NAT sessions (see IPitomy’s list of known performing routers) [http://www.ipitomy.com/webrelease/IPitomy/Router%20Compatibility%20Guide.pdf http://www.ipitomy.com/webrelease/IPitomy/Router%20Compatibility%20Guide.pdf]

#It is also recommended that you certify the bandwidth is appropriate for what is required for remote users and SIP Trunks. Technically using the standard G.711 CODEC each voice conversation uses 64kbs send 64kbs receive. With SIP overhead this is increased to approximately 80kbs. To simplify calculations we recommend using a round number of 200Kb (kilo bits) of symmetrical bandwidth for each concurrent voice call. (100Kb Send/100Kb Receive)<ol style="list-style-type:lower-alpha;">
<li>Most data connections are asymmetrical – meaning that there is a difference in speed upload versus download. Usually expressed as 10Dn/5Up… the VoIP connection can be no greater than the lesser bandwidth rate.</li>
<li>Keep in mind that some connections fluctuate at times during the day and your connection will only ever be as good as the weakest link. </li>
</ol><li>Always recommend proper equipment for the job to avoid the pitfalls and traps of old existing Networks with aging performance issues. </li>
<li>If the DATA Network is managed by another team you should provide them with a checklist and a proof of assurance document that they may sign off on which provides you with verification that your requirements for the Voice network are in fact being met. Any changes to meet the requirements must be completed before the day of installation without incurring additional labors costs. <ol style="list-style-type:lower-alpha;">
<li>Checklist:</li>
</ol></li>
</ol>

*IP Address of the IP PBX is identified and verified available (Ping IP PBX IP Address to assure that no device is using the address.)
*Establish IP Address range for DHCP use
*Disclose any Static IP Addresses currently in use.
*POE capable, QOS capable Switch(es)
*For applications with Remote Phones - Router capable of multiple NAT sessions (use).
**Ports in router forwarded to PBX for remote phones (5060, 10,000 – 20,000)
*Ports in router forwarded to the PBX for remote maintenance (Port 80)
*Ports in router forwarded to the PBX for Branch Office use (Port 4569)
*Ports in router forwarded to the PBX for Factory support access (Port 22)

The prior analysis provided in the outline above will best assure that you have a successful and prosperous IPitomy install. It also outlines a means of successful integration and a continuing good working relationship with existing IT personnel.

Questions:

#What is the basic network requirement to optimize a network for VoIP?
#What type of data switch should be used in a voice network?
#What is the approximate bandwidth requirement for a G.711 coded voice call?
#What is the primary advantage of using POE?
#What is the network component where QOS is setup?