Difference between revisions of "Training:Process Review"

From IPitomy Wiki
Jump to navigation Jump to search
(Created page with "<span style="font-size:larger">'''Process Review'''</span>  Being prepared before heading onsite to install the PBX is going to remove stress and make the install go mor...")
 
(6 intermediate revisions by 2 users not shown)
Line 1: Line 1:
−
<span style="font-size:larger">'''Process Review'''</span>
 
  
−
&nbsp;Being prepared before heading onsite to install the PBX is going to remove stress and make the install go more smoothly.&nbsp; Installing and testing a basic install of the major components is going to alleviate stress and ensure that everything is working as expected, as well as ensure your time is being used efficiently.
 
  
−
&nbsp;'''Pre-Install –''' As mentioned in previous modules, being prepared is a key component of a successful install.
+
'''Process Review'''
  
−
**Be sure to have your Site Survey and IPitomy Setup Worksheet completed, as well as contact information for key players like the ISP, IT Dept, Trunk Providers, etc.
+
Preparation is critical before heading onsite to install a PBX, either for a cloud or on-premise IPitomy solution. It reduces stress and ensures a smoother, more efficient installation. This involves installing and testing a basic setup of the major components to make sure everything works as expected.
−
**If possible, build as much as you can in the PBX before heading onsite.&nbsp; While we do not recommend registering the phones just yet as the IP address of the PBX may change, having your extensions, groups, menus, schedules, etc built ahead of time will decrease the time spent onsite when doing the install.
 
  
−
*'''Matching the LAN –''' Getting the PBX IP addresses configured to communicate on the network is the first step of your installation.&nbsp; If the network subnet is not 192.168.1.x you will first have to configure the PBX so it can communicate with the network. There are two ways to configure the PBX IP address to match the subnet of the LAN.&nbsp; Once set, it is advised to reboot the PBX.
+
'''Pre-Install'''
−
**Keyboard and Monitor – With a keyboard and monitor connected you can press CTRL-ALT-F7.&nbsp; This brings you to a screen that allows you to set your Static IP, Subnet Mask, Gateway, and DNS.&nbsp; Once all the values have been set, be sure to select S to save.
 
−
**PC and Simple Network – By default the PBX can be accessed via 192.168.1.249/ippbx.&nbsp; With your PC and PBX connected to a simple network (only a switch is needed between the two devices) and your PC set statically to 192.168.1.50 you can log into the default IP address of the PBX.&nbsp; Once logged in, you would navigate to System=>Networking and make your change to Static IP, Subnet Mask, Gateway, and DNS.
 
  
−
*'''Connecting to the Network –''' Once the PBX is configured with the correct IP addresses you are ready to connect it to the customer network.&nbsp; Be sure to connect the PBX to the switch that will host the majority of the phones.&nbsp; You do not want to make the mistake of connecting the PBX to their router as you will be creating an unnecessary bottleneck for traffic that can cause issues down the road.
+
Thorough preparation is a key component of a successful install. Your Site Survey and IPitomy Setup Worksheet should be completed, with the contact information for key parties like the ISP, IT Dept, Trunk Providers, etc. If possible, set up as much as you can in the PBX before heading onsite. While it's not advisable to register the phones just yet (since the IP address of the PBX may change), having your extensions, groups, menus, schedules, etc. pre-configured will reduce the time spent onsite during the installation.
  
−
&nbsp;'''SIP Localnet and External IP– '''The Localnet defines what network is considered to Local in terms of SIP communication.&nbsp; You can find this setting under PBX Setup=>SIP.&nbsp; If the Localnet does not match the LAN, the phones will not be able to communicate to the PBX.&nbsp; The Localnet will follow the pattern xxx.yyy.zzz.0 with x, y, and z matching the PBX IP address, the last octet will always be zero.&nbsp; The subnet mask for the Localnet will typically be 255.255.255.0.&nbsp; If the install will have any remote SIP (Provider or Phones) I would also enter the public IP address for the site in the External IP field at this time.
+
'''Matching the LAN'''
  
−
&nbsp;'''Access Control List –''' Once the Localnet is set, we advise to set the ACL.&nbsp; Found under System=>Access Contol=>Access Control List, we advise you click the Load Recommended Defaults button.&nbsp; This will configure the basic ACL services (SIP, Call Manager, Local Manager, and TFTP) in a way that allows devices within the Localnet to communicate to the PBX.&nbsp; If you are using a SIP provider, add &lt;SIPTrunkIP&gt;/32 as a rule to the SIP service in the ACL at this time.&nbsp; If remote phones will have static IP addresses, enter those as well.&nbsp; If there will be remote phones on none static IP addresses, delete the entire SIP ACL Service and enable Log Watch & Ban.&nbsp;
+
The first step of your installation is configuring the PBX IP addresses to communicate on the network. If the network subnet isn't 192.168.1.x, you'll first need to adjust the PBX to communicate with the network. You can configure the PBX IP address to match the subnet of the LAN in two ways. After setting it up, it's recommended to reboot the PBX.
  
−
*'''Register Two Extensions –''' We advise to register two extensions to start.&nbsp; After they are registered make some test calls as this will give you an idea if things are working correctly.
+
'''Keyboard and Monitor'''
−
**Can each phone call the other?
 
−
**Is there two way audio?
 
−
**Are there any issues with call quality?
 
  
−
&nbsp;'''Remote SIP –''' If the site plans to use any remote phones or SIP trunks, we advise to install a remote phone next as a means to test that the router is handling NAT correctly.&nbsp; Often times a 3<sup>rd</sup> party (IT Dept, Off-site IT, etc) will need to be contacted to make changes to the router so it is best to find out at the start of the install as opposed to the end.&nbsp; If an off-site IT needs time to get to the site to make changes you can start working on other sections of the install, but at least the ball is rolling.
+
With a keyboard and monitor connected, you can press ALT-F7. This will bring you to a screen that allows you to set your Static IP, Subnet Mask, Gateway, and DNS. Once all the values are set, select 'S' to save.
  
−
**Softphone – An easy way to test would be to have a SIP softphone on your cell.&nbsp; Register this as a WAN extension to the PBX and test.
+
'''PC and Simple Network'''
−
**Hardware Phone – If you have other employees at your office you can have them register a physical SIP phone to a WAN extension on the PBX and test.
 
  
−
&nbsp;'''Trunks –''' Configuring the trunks next and testing them will allow the Provider time to resolve possible issues while you work on the rest of the install.&nbsp; Waiting until the end to configure the trunks may extend the time taken to cut-over.
+
By default, the PBX can be accessed via 192.168.1.249/ippbx. With your PC and PBX connected to a simple network (only a switch is needed between the two devices), and your PC set statically to 192.168.1.50, you can log into the default IP address of the PBX. Once logged in, navigate to System => Networking and change to Static IP, Subnet Mask, Gateway, and DNS.
  
−
**Add only one DID at this time to ensure the provider is sending the right number of digits.
+
'''Connecting to the Network'''
  
−
&nbsp;'''Test –''' We cannot stress enough how important it is to test your basic install before implementing everything.&nbsp; With a few local extensions, remote extensions, and trunks built you can get a good idea how everything is working.
+
Once the PBX is configured with the correct IP addresses, connect it to the customer network. Be sure to connect the PBX to the switch that will host the majority of the phones. Avoid connecting the PBX to their router as this could create an unnecessary traffic bottleneck that could lead to issues down the line.
  
−
**Can the LAN phones make and receive calls?
+
'''SIP Localnet and External IP'''
−
**Does DTMF work?
 
−
**Can Remote Phones make and receive calls?
 
−
**Can you make and receive calls via the Trunks?
 
−
**Two way audio for LAN phones, WAN phones, and Trunks?
 
−
**Are DIDs routing correctly?
 
  
−
*'''Configure the Rest –''' Once the basic install has been tested and found to be functional, register the remaining phones to the PBX, add and configure the remaining DIDs, and test the complete functionality.
+
The Localnet defines what network is considered to be Local in terms of SIP communication. This setting can be found under PBX Setup => SIP. If the Localnet doesn't match the LAN, the phones won't be able to communicate with the PBX. The Localnet follows the pattern xxx.yyy.zzz.0, with x, y, and z matching the PBX IP address, and the last octet always being zero. The subnet mask for the Localnet will typically be 255.255.255.0. If the install involves any remote SIP (Provider or Phones), it's also advised to enter the public IP address for the site in the External IP field at this time.
−
**Do Ring Group calls function as desired?
 
−
**Do the Menus route the callers to the desired destinations?
 
  
−
*'''Training –''' Once the system is installed and working as expected, the task of training the end user begins.&nbsp; While many of the features work exactly like their old system did, there are a number of new things to learn.&nbsp; Ensuring the end user is up to speed on how to use their phones and PBX will result in a happier customer.
+
'''Access Control List'''
 +
 
 +
Once the Localnet is set, it's recommended to set the ACL. This can be found under System => Access Control => Access Control List. Click the 'Load Recommended Defaults' button. This will configure the basic ACL services (SIP, Call Manager, Local Manager, and TFTP) to allow devices within the Localnet to communicate with the PBX. If you are using a SIP provider, add <SIPTrunkIP>/32 as a rule to the SIP service in the ACL. If there will be remote phones with static IP addresses, add those as well. For remote phones on non-static IP addresses, delete the entire SIP ACL Service and enable 'Log Watch & Ban'.
 +
 
 +
'''Register Two Extensions'''
 +
 
 +
Start by registering two extensions. After they're registered, make some test calls. This will help determine if everything is working correctly. Can each phone call the other? Is there two-way audio? Are there any issues with call quality?
 +
 
 +
'''Remote SIP'''
 +
 
 +
If the site plans to use any remote phones or SIP trunks, install a remote phone next to test if the router is handling NAT correctly. It's best to identify this at the start of the install instead of the end, as changes to the router might need to be made by a third party (like an IT Dept, Off-site IT, etc).
 +
 
 +
'''Softphone'''
 +
 
 +
One easy way to test would be to have a SIP softphone on your cell. Register this as a WAN extension to the PBX and test.
 +
 
 +
'''Hardware Phone'''
 +
 
 +
If you have other employees at your office, you can have them register a physical SIP phone to a WAN extension on the PBX and test.
 +
 
 +
'''Trunks'''
 +
 
 +
Configuring the trunks next and testing them will allow the Provider time to resolve possible issues while you work on the rest of the install. Waiting until the end to configure the trunks may prolong the cut-over time.
 +
 
 +
Add only one DID at this time to ensure the provider is sending the right number of digits.
 +
 
 +
'''Test'''
 +
 
 +
Thorough testing is vital. With a few local extensions, remote extensions, and trunks set up, you can get a good idea of how everything is working.
 +
 
 +
Can the LAN phones make and receive calls? Does DTMF work? Can Remote Phones make and receive calls? Can you make and receive calls via the Trunks? Is there two-way audio for LAN phones, WAN phones, and Trunks? Are DIDs routing correctly?
 +
 
 +
'''Configure the Rest'''
 +
 
 +
Once the basic install has been tested and is functional, register the remaining phones to the PBX, add and configure the remaining DIDs, and test the complete functionality. Do Ring Group calls function as desired? Do the Menus route the callers to the desired destinations?
 +
 
 +
'''Training'''
 +
 
 +
Once the system is installed and functioning as expected, the task of training the end user begins. Many features will work exactly like their old system did, but there will also be new things to learn. Ensuring the end user is up to speed on how to use their phones and PBX will result in a happier customer
 +
[[Category:Training]]

Revision as of 22:08, 17 May 2023


Process Review

Preparation is critical before heading onsite to install a PBX, either for a cloud or on-premise IPitomy solution. It reduces stress and ensures a smoother, more efficient installation. This involves installing and testing a basic setup of the major components to make sure everything works as expected.

Pre-Install

Thorough preparation is a key component of a successful install. Your Site Survey and IPitomy Setup Worksheet should be completed, with the contact information for key parties like the ISP, IT Dept, Trunk Providers, etc. If possible, set up as much as you can in the PBX before heading onsite. While it's not advisable to register the phones just yet (since the IP address of the PBX may change), having your extensions, groups, menus, schedules, etc. pre-configured will reduce the time spent onsite during the installation.

Matching the LAN

The first step of your installation is configuring the PBX IP addresses to communicate on the network. If the network subnet isn't 192.168.1.x, you'll first need to adjust the PBX to communicate with the network. You can configure the PBX IP address to match the subnet of the LAN in two ways. After setting it up, it's recommended to reboot the PBX.

Keyboard and Monitor

With a keyboard and monitor connected, you can press ALT-F7. This will bring you to a screen that allows you to set your Static IP, Subnet Mask, Gateway, and DNS. Once all the values are set, select 'S' to save.

PC and Simple Network

By default, the PBX can be accessed via 192.168.1.249/ippbx. With your PC and PBX connected to a simple network (only a switch is needed between the two devices), and your PC set statically to 192.168.1.50, you can log into the default IP address of the PBX. Once logged in, navigate to System => Networking and change to Static IP, Subnet Mask, Gateway, and DNS.

Connecting to the Network

Once the PBX is configured with the correct IP addresses, connect it to the customer network. Be sure to connect the PBX to the switch that will host the majority of the phones. Avoid connecting the PBX to their router as this could create an unnecessary traffic bottleneck that could lead to issues down the line.

SIP Localnet and External IP

The Localnet defines what network is considered to be Local in terms of SIP communication. This setting can be found under PBX Setup => SIP. If the Localnet doesn't match the LAN, the phones won't be able to communicate with the PBX. The Localnet follows the pattern xxx.yyy.zzz.0, with x, y, and z matching the PBX IP address, and the last octet always being zero. The subnet mask for the Localnet will typically be 255.255.255.0. If the install involves any remote SIP (Provider or Phones), it's also advised to enter the public IP address for the site in the External IP field at this time.

Access Control List

Once the Localnet is set, it's recommended to set the ACL. This can be found under System => Access Control => Access Control List. Click the 'Load Recommended Defaults' button. This will configure the basic ACL services (SIP, Call Manager, Local Manager, and TFTP) to allow devices within the Localnet to communicate with the PBX. If you are using a SIP provider, add <SIPTrunkIP>/32 as a rule to the SIP service in the ACL. If there will be remote phones with static IP addresses, add those as well. For remote phones on non-static IP addresses, delete the entire SIP ACL Service and enable 'Log Watch & Ban'.

Register Two Extensions

Start by registering two extensions. After they're registered, make some test calls. This will help determine if everything is working correctly. Can each phone call the other? Is there two-way audio? Are there any issues with call quality?

Remote SIP

If the site plans to use any remote phones or SIP trunks, install a remote phone next to test if the router is handling NAT correctly. It's best to identify this at the start of the install instead of the end, as changes to the router might need to be made by a third party (like an IT Dept, Off-site IT, etc).

Softphone

One easy way to test would be to have a SIP softphone on your cell. Register this as a WAN extension to the PBX and test.

Hardware Phone

If you have other employees at your office, you can have them register a physical SIP phone to a WAN extension on the PBX and test.

Trunks

Configuring the trunks next and testing them will allow the Provider time to resolve possible issues while you work on the rest of the install. Waiting until the end to configure the trunks may prolong the cut-over time.

Add only one DID at this time to ensure the provider is sending the right number of digits.

Test

Thorough testing is vital. With a few local extensions, remote extensions, and trunks set up, you can get a good idea of how everything is working.

Can the LAN phones make and receive calls? Does DTMF work? Can Remote Phones make and receive calls? Can you make and receive calls via the Trunks? Is there two-way audio for LAN phones, WAN phones, and Trunks? Are DIDs routing correctly?

Configure the Rest

Once the basic install has been tested and is functional, register the remaining phones to the PBX, add and configure the remaining DIDs, and test the complete functionality. Do Ring Group calls function as desired? Do the Menus route the callers to the desired destinations?

Training

Once the system is installed and functioning as expected, the task of training the end user begins. Many features will work exactly like their old system did, but there will also be new things to learn. Ensuring the end user is up to speed on how to use their phones and PBX will result in a happier customer

Retrieved from "http://wiki.ipitomy.com/index.php?title=Training:Process_Review&oldid=5008"