Training:Install Preparation - Revision history

Tyler at 22:01, 17 May 2023

2023-05-17T22:01:26Z

← Older revision		Revision as of 22:01, 17 May 2023
Line 1:		Line 1:
	~~Prior~~ to ~~install you should either determine which~~ data switch ~~is to~~ be used, or ~~which are installed already~~ at the site. ~~It is preferred that this be~~ a ~~level~~ 2 managed switch ~~so that QOS can be used to assure~~ high-priority voice traffic ~~handling~~. The ~~Switch that~~ you ~~use~~ is ~~the primary~~ backbone ~~piece for the network~~.		Before proceeding with the installation, it is crucial to identify the data switch that will be used, or recognize the existing switches at the site. We recommend utilizing a Level 2 managed switch, as it supports Quality of Service (QoS). Implementing QoS assures high-priority handling of voice traffic, thus improving call quality and overall performance. The switch you deploy is a fundamental component of your network's backbone.

	~~Considerations should be given to~~ the ~~network in terms of~~ configuration and layout. ~~It is common for technicians to make~~ errors in network ~~layout~~, ~~and in so doing create~~ unnecessary ~~network bottle necks~~. ~~An example being~~, if you have 20 phones ~~and they are all plugged into~~ a 24 port switch~~. It~~ would be ~~most advantageous~~ to ~~plug~~ the PBX ~~into~~ this switch ~~instead of some other piece of gear as this would keep~~ all ~~packets regarding the~~ voice network on the same ~~piece of equipment~~.		When mapping out your network, consider the configuration and layout critically. Technicians often commit errors in network design, inadvertently creating unnecessary bottlenecks. For instance, if you have 20 phones connected to a 24-port switch, it would be optimal to connect the IPitomy PBX to this same switch. This setup ensures all voice network packets remain within the same hardware, optimizing network efficiency.

	~~ ~~		Another key consideration is the Power over Ethernet (PoE) option. PoE technology allows for the transmission of electrical power, along with data, over Ethernet cabling in a safe manner. The IEEE standard for PoE mandates Category 5 cable or above for high power levels, but Category 3 cable can suffice for lower power levels. Power is delivered in common mode over two or more of the differential pairs of wires found in Ethernet cables, sourced either from a power supply within a PoE-enabled networking device like an Ethernet switch or injected into a cable run with a midspan power supply.

	~~ [[File:NetworkTopology~~.~~gif\|none]]~~

	~~ ~~		The initial IEEE 802.3af-2003 PoE standard can provide up to 15.4 W of DC power (minimum 44 V DC and 350 mA) to each device, with 12.95 W guaranteed to be available at the powered device as some power loss occurs in the cable.

	~~Consideration should~~ also ~~be given~~ to ~~the POE option. Power over Ethernet~~ or PoE ~~technology describes a system~~ to ~~pass electrical~~ power ~~safely, along with data, on Ethernet cabling~~. ~~The IEEE~~ standard for ~~PoE requires Category 5 cable or higher for high~~ power ~~levels~~, ~~but can operate~~ with ~~category 3 cable for low~~ power ~~levels. Power is supplied in common mode~~ over ~~two or more of the differential~~ pairs ~~of wires found~~ in the ~~Ethernet cables and comes from a power supply within a PoE-enabled networking device such as an Ethernet switch or can be injected into a~~ cable ~~run with a midspan power supply~~.		The subsequent IEEE 802.3at-2009 PoE standard, also referred to as PoE+ or PoE plus, can supply up to 25.5 W of power. This standard prevents a powered device from using all four pairs for power. However, some vendors have developed products claiming compatibility with the 802.3at standard, offering up to 51 W of power over a single cable by leveraging all four pairs in the Category 5 cable.

	~~The original IEEE 802.3af-2003 PoE standard provides up to 15.4 W~~ of DC power ~~(minimum 44 V DC and 350 mA) to each device. Only 12.95 W is assured to be available at the powered device as some power is dissipated in the cable~~.		IPitomy telephones typically consume 7 watts of power or less, making them highly compatible with these PoE standards.

	~~The updated IEEE 802.3at~~-~~2009 PoE~~ standard ~~also known as PoE+ or PoE plus, provides up~~ to ~~25.5 W of power. The 2009 standard prohibits a powered device from using all four pairs for~~ power. Some ~~vendors have announced products that claim~~ to ~~be compatible with the 802.3at standard~~ and ~~offer up to 51 W of power over a single cable by utilizing all four pairs in the Category 5 cable~~.		Before the standardization of PoE, various non-standard schemes were employed to deliver power over Ethernet cabling. Some of these schemes are still in use today, although adherence to IEEE standards is typically recommended for compatibility and safety reasons.

	~~IPitomy telephones consume approximately 7 WATTS of power or less~~.		[[File:NetworkTopology.gif\|none]]

	~~Numerous non-standard schemes had been used prior to PoE standardization to provide power over Ethernet cabling. Some are still in active use.~~

	{\| border="1" cellpadding="0" cellspacing="0"		{\| border="1" cellpadding="0" cellspacing="0"

Mike Lunn at 16:28, 8 December 2021

2021-12-08T16:28:28Z

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


		[[Category:Training]]

Paul Falanga: Created page with "Prior to install you should either determine which data switch is to be used, or which are installed already at the site. It is preferred that this be a level 2 managed switch..."

2012-09-13T21:09:31Z

Created page with "Prior to install you should either determine which data switch is to be used, or which are installed already at the site. It is preferred that this be a level 2 managed switch..."

New page

Prior to install you should either determine which data switch is to be used, or which are installed already at the site. It is preferred that this be a level 2 managed switch so that QOS can be used to assure high-priority voice traffic handling. The Switch that you use is the primary backbone piece for the network.

Considerations should be given to the network in terms of configuration and layout. It is common for technicians to make errors in network layout, and in so doing create unnecessary network bottle necks. An example being, if you have 20 phones and they are all plugged into a 24 port switch. It would be most advantageous to plug the PBX into this switch instead of some other piece of gear as this would keep all packets regarding the voice network on the same piece of equipment.

 

 [[File:NetworkTopology.gif|none]]

 

Consideration should also be given to the POE option. Power over Ethernet or PoE technology describes a system to pass electrical power safely, along with data, on Ethernet cabling. The IEEE standard for PoE requires Category 5 cable or higher for high power levels, but can operate with category 3 cable for low power levels. Power is supplied in common mode over two or more of the differential pairs of wires found in the Ethernet cables and comes from a power supply within a PoE-enabled networking device such as an Ethernet switch or can be injected into a cable run with a midspan power supply.

The original IEEE 802.3af-2003 PoE standard provides up to 15.4 W of DC power (minimum 44 V DC and 350 mA) to each device. Only 12.95 W is assured to be available at the powered device as some power is dissipated in the cable.

The updated IEEE 802.3at-2009 PoE standard also known as PoE+ or PoE plus, provides up to 25.5 W of power. The 2009 standard prohibits a powered device from using all four pairs for power. Some vendors have announced products that claim to be compatible with the 802.3at standard and offer up to 51 W of power over a single cable by utilizing all four pairs in the Category 5 cable.

IPitomy telephones consume approximately 7 WATTS of power or less.

Numerous non-standard schemes had been used prior to PoE standardization to provide power over Ethernet cabling. Some are still in active use.

{| border="1" cellpadding="0" cellspacing="0"
|-
| style="height:56px" |
'''Speed [Mbit/s]'''

| style="height:56px" |
'''Distance [m]'''

| style="height:56px" |
'''Name'''

| style="height:56px" |
'''Standard / Year'''

| style="height:56px" |
'''Description'''

|-
| style="height:96px" |
1

| style="height:96px" |
100 (nominally)

| style="height:96px" |
[http://en.wikipedia.org/wiki/StarLAN StarLAN]

| style="height:96px" |
802.3e 1986[http://en.wikipedia.org/wiki/Ethernet_over_twisted_pair#cite_note-9 [9]]

| style="height:96px" |
Runs over four wires (two [http://en.wikipedia.org/wiki/Twisted_pair twisted pairs]) on telephone twisted pair or [http://en.wikipedia.org/wiki/Category_3_cable Category 3] cable. An active [http://en.wikipedia.org/wiki/Ethernet_hub hub] sits in the middle and has a port for each node. [http://en.wikipedia.org/wiki/Manchester_code Manchester coded] signaling.

|-
| style="height:96px" |
10

| style="height:96px" |
100 (nominally)

| style="height:96px" |
[http://en.wikipedia.org/wiki/LattisNet LattisNet]

| style="height:96px" |
(pre) 802.3i 1987

| style="height:96px" |
Runs over AT&T Premises Distribution System (PDS) wiring or four wires (two [http://en.wikipedia.org/wiki/Twisted_pair twisted pairs]) on telephone twisted pair or [http://en.wikipedia.org/wiki/Category_3_cable Category 3 cable].[http://en.wikipedia.org/wiki/Ethernet_over_twisted_pair#cite_note-syn-3 [3]][http://en.wikipedia.org/wiki/Ethernet_over_twisted_pair#cite_note-10 [10]]

|-
| style="height:144px" |
10

| style="height:144px" |
100 (nominally)[http://en.wikipedia.org/wiki/Ethernet_over_twisted_pair#cite_note-11 [11]]

| style="height:144px" |
10BASE-T

| style="height:144px" |
802.3i 1990

| style="height:144px" |
Runs over four wires (two [http://en.wikipedia.org/wiki/Twisted_pair twisted pairs]) on a [http://en.wikipedia.org/wiki/Category_3_cable Category 3] or [http://en.wikipedia.org/wiki/Category_5_cable Category 5 cable]. Star topology with an active [http://en.wikipedia.org/wiki/Ethernet_hub hub] or [http://en.wikipedia.org/wiki/Ethernet_switch switch] sits in the middle and has a port for each node. This is also the configuration used for 100BASE-T and gigabit Ethernet. [http://en.wikipedia.org/wiki/Manchester_code Manchester coded] signaling.

|-
| style="height:58px" |
100

| style="height:58px" |
100

| style="height:58px" |
[http://en.wikipedia.org/wiki/100BASE-TX 100BASE-TX]

| style="height:58px" |
802.3u 1995

| style="height:58px" |
[http://en.wikipedia.org/wiki/4B5B 4B5B] [http://en.wikipedia.org/wiki/MLT-3 MLT-3] coded signaling, [http://en.wikipedia.org/wiki/Category_5_cable CAT5] copper cabling with two twisted pairs.

|-
|
1000

|
100

|
[http://en.wikipedia.org/wiki/1000BASE%E2%80%91T 1000BASE‑T]

|
802.3ab 1999

|
[http://en.wikipedia.org/wiki/Pulse-amplitude_modulation PAM-5] coded signaling, At least [http://en.wikipedia.org/wiki/Category_5_cable Category 5 cable], with [http://en.wikipedia.org/wiki/Category_5e Category 5e] strongly recommended copper cabling with four twisted pairs. Each pair is used in both directions simultaneously.

|-
| style="height:58px" |
10 000

| style="height:58px" |
100

| style="height:58px" |
[http://en.wikipedia.org/wiki/10GBASE-T 10GBASE‑T]

| style="height:58px" |
802.3an 2006

| style="height:58px" |
Uses [http://en.wikipedia.org/wiki/Category_6a category 6a] cable.

|}

 

Installation:

When installing the system it is best to use the following outline:

*Create Extensions
**Import – extensions are created by importing a CSV file
**Auto Discovery  - PBX used to discover all phones on the network
**Auto Provision – PBX pairing function to install extensions
**Data Entry - one at a time
*Create Groups
**No limit to Groups
**Use for Department calling patterns
**Ring Strategies to be used
**Queue handling
*Create Menus
**Unlimited Menus
**Use for instructions/announcements
**Use for call routing
*Create Trunks
**SIP – Provider and SIP Configuration known and in-hand
**Hardware
***T-1, PRI
****DID destination
****Default Answering Destination
***Internal Gateway (PBX board for PSTN)
****Default Answering Destination
*Inbound Routing
** 
*Outbound Routing

Test as you go

*configure two phones and then test the connectivity, call between phones and voicemail to test
*configure the balance of the extensions
*When configuring a trunk, set it up and then test prior to full implementation.
**On SIP trunks, configure the trunk and then test inbound and outbound.
**On a PRI to check DID and make sure it is delivered correctly and only then program the balance of the DID’s.

 

When installing remote phones this method is also advantageous. To verify prior to rollout of all remote phones a single phone should be installed and tested to verify that the port configuration is all accurate.

 

Once all elements are configured and test correctly then you should proceed with the remainder of the install.