Network setup AX - Revision history

Rickwhite: Chime.Center formatting

2026-01-23T18:40:23Z

Chime.Center formatting

Daveallen: /* Wireless */

2026-01-18T02:43:54Z

Wireless

← Older revision		Revision as of 02:43, 18 January 2026
Line 38:		Line 38:

	=== Wireless ===		=== Wireless ===
	These connections require the available wireless adapter antenna. Screw the two parts together and ~~powered~~ down the ringing system before plugging in the antenna. Keep the system level while the antenna is plugged in, as tipping the system can cause damage to the antenna or port connection.		These connections require the available wireless adapter antenna. Screw the two parts together and power down the ringing system before plugging in the antenna. Keep the system level while the antenna is plugged in, as tipping the system can cause damage to the antenna or port connection.

	==== WiFi network ====		==== WiFi network ====
	WiFi is trickier to set up, but has the advantage that it provides an air gap between the lightning prone outside components of your ringing system and your other wired network ~~equipment~~.		WiFi is trickier to set up, but has the advantage that it provides an air gap between the lightning prone outside components of your ringing system and your other wired network components.

	[[File:Wifi.jpg\|frameless\|right\|450px]]		[[File:Wifi.jpg\|frameless\|right\|450px]]

Rickwhite: /* Issues with firewalls */

2025-12-04T15:37:09Z

Issues with firewalls

← Older revision		Revision as of 15:37, 4 December 2025
Line 141:		Line 141:
	'''Verizon''' router/modem firewalls often default to closing connections to port 22. Check if your security settings is set to maximum. If so, manually add SSH 22.		'''Verizon''' router/modem firewalls often default to closing connections to port 22. Check if your security settings is set to maximum. If so, manually add SSH 22.

	Chime Center not support Deep Packet Inspection of SSH packets (DPI-SSH), typically encountered on '''SonicWall''' products. If your network must enable DPI-SSH (very rare circumstances), disable it for the ringing system's (static) IP or mac address to allow API tunneling. Otherwise, the chime.center server will detect your firewall as a man-in-the-middle attacker and drop the connection.		Chime Center does not support Deep Packet Inspection of SSH packets (DPI-SSH), typically encountered on '''SonicWall''' products. If your network must enable DPI-SSH (very rare circumstances), disable it for the ringing system's (static) IP or mac address to allow API tunneling. Otherwise, the chime.center server will detect your firewall as a man-in-the-middle attacker and drop the connection.

	==== Best Practices ====		==== Best Practices ====

Rickwhite: Verizon

2025-12-04T15:35:27Z

Verizon

← Older revision		Revision as of 15:35, 4 December 2025
Line 137:		Line 137:
	* '''TCP 7443''' (to *.chime.center - update systems with firmware < 1.4.20)		* '''TCP 7443''' (to *.chime.center - update systems with firmware < 1.4.20)
	* '''UDP 123''' (time sync)		* '''UDP 123''' (time sync)
	Chime Master ringing systems do not support Deep Packet Inspection of SSH packets (DPI-SSH), typically encountered on SonicWall products. If your network must enable DPI-SSH (very rare circumstances), disable it for the ringing system's (static) IP or mac address to allow API tunneling. Otherwise, the chime.center server will detect your firewall as a man-in-the-middle attacker and drop the connection.

	'''~~Best Practices~~'''		==== Issues with firewalls ====
			'''Verizon''' router/modem firewalls often default to closing connections to port 22. Check if your security settings is set to maximum. If so, manually add SSH 22.

			Chime Center not support Deep Packet Inspection of SSH packets (DPI-SSH), typically encountered on '''SonicWall''' products. If your network must enable DPI-SSH (very rare circumstances), disable it for the ringing system's (static) IP or mac address to allow API tunneling. Otherwise, the chime.center server will detect your firewall as a man-in-the-middle attacker and drop the connection.

			==== Best Practices ====
	* Use a strong WiFi password on your router or access point.		* Use a strong WiFi password on your router or access point.
	* Test your firewall for unneeded open inbound ports. Gibson Research provides the [https://www.grc.com/shieldsup Shields Up!] tool. After clicking the Proceed button, click the All Service Ports button to begin testing.		* Test your firewall for unneeded open inbound ports. Gibson Research provides the [https://www.grc.com/shieldsup Shields Up!] tool. After clicking the Proceed button, click the All Service Ports button to begin testing.

Daveallen: /* Check your connection */

2025-06-27T19:29:51Z

Check your connection

← Older revision		Revision as of 19:29, 27 June 2025
Line 23:		Line 23:
	* Status: '''Access Point Mode''' - System is in Access Point (AP) mode for local remote control.		* Status: '''Access Point Mode''' - System is in Access Point (AP) mode for local remote control.
	* Status: '''Not Connected''' - System is not making connections to any network. Check cabling and if using antenna, retry WiFi setup.		* Status: '''Not Connected''' - System is not making connections to any network. Check cabling and if using antenna, retry WiFi setup.
			=== System time ===
			The system will not be able to properly negotiate connections with our servers if the ringing system's time is incorrect. Go the the Settings - Date and Time screen to verify the correct date, time and time zone. Make sure the switches for DST and Automatic Time Sync are on.

	== Connection modes ==		== Connection modes ==

Rickwhite: added typical bandwidth specification

2025-06-09T17:14:10Z

added typical bandwidth specification

← Older revision		Revision as of 17:14, 9 June 2025
Line 111:		Line 111:

	* This site may need to be white-listed in firewall or DNS rules		* This site may need to be white-listed in firewall or DNS rules

			=== Bandwidth ===
			Typically you can expect around 50MB to 100MB per day (less than 3GB/month) of usage by the bell system, depending on the frequency of remote control and management usage.

	== Security ==		== Security ==

Rickwhite: /* Internet access requirements */

2025-05-29T01:44:39Z

Internet access requirements

← Older revision		Revision as of 01:44, 29 May 2025
Line 108:		Line 108:
	While connected only to your network (mobile data off), a test device (phone or PC) must be able to access		While connected only to your network (mobile data off), a test device (phone or PC) must be able to access
	'''https://chime.center'''		'''https://chime.center'''
			'''https://sf.chime.center'''

	* This site may need to be white-listed in firewall or DNS rules		* This site may need to be white-listed in firewall or DNS rules

Rickwhite: /* Your network */

2025-05-08T18:13:25Z

Your network

← Older revision		Revision as of 18:13, 8 May 2025
Line 129:		Line 129:
	* '''SSH 22''' (to *.sf.chime.center - remote tunnel for API and backups)		* '''SSH 22''' (to *.sf.chime.center - remote tunnel for API and backups)
	* '''TCP 443''' (to *.sf.chime.center - updates)		* '''TCP 443''' (to *.sf.chime.center - updates)
	* '''TCP 7443''' (to *~~.fe~~.chime.center - update systems with firmware < 1.4.20)		* '''TCP 7443''' (to *.chime.center - update systems with firmware < 1.4.20)
	* '''UDP 123''' (time sync)		* '''UDP 123''' (time sync)
	Chime Master ringing systems do not support Deep Packet Inspection of SSH packets (DPI-SSH), typically encountered on SonicWall products. If your network must enable DPI-SSH (very rare circumstances), disable it for the ringing system's (static) IP or mac address to allow API tunneling. Otherwise, the chime.center server will detect your firewall as a man-in-the-middle attacker and drop the connection.		Chime Master ringing systems do not support Deep Packet Inspection of SSH packets (DPI-SSH), typically encountered on SonicWall products. If your network must enable DPI-SSH (very rare circumstances), disable it for the ringing system's (static) IP or mac address to allow API tunneling. Otherwise, the chime.center server will detect your firewall as a man-in-the-middle attacker and drop the connection.

Rickwhite: /* Your network */

2025-05-08T18:12:58Z

Your network

← Older revision		Revision as of 18:12, 8 May 2025
Line 129:		Line 129:
	* '''SSH 22''' (to *.sf.chime.center - remote tunnel for API and backups)		* '''SSH 22''' (to *.sf.chime.center - remote tunnel for API and backups)
	* '''TCP 443''' (to *.sf.chime.center - updates)		* '''TCP 443''' (to *.sf.chime.center - updates)
	* '''TCP 7443''' (update systems with firmware < 1.4.20)		* '''TCP 7443''' (to *.fe.chime.center - update systems with firmware < 1.4.20)
	* '''UDP 123''' (time sync)		* '''UDP 123''' (time sync)
	Chime Master ringing systems do not support Deep Packet Inspection of SSH packets (DPI-SSH), typically encountered on SonicWall products. If your network must enable DPI-SSH (very rare circumstances), disable it for the ringing system's (static) IP or mac address to allow API tunneling. Otherwise, the chime.center server will detect your firewall as a man-in-the-middle attacker and drop the connection.		Chime Master ringing systems do not support Deep Packet Inspection of SSH packets (DPI-SSH), typically encountered on SonicWall products. If your network must enable DPI-SSH (very rare circumstances), disable it for the ringing system's (static) IP or mac address to allow API tunneling. Otherwise, the chime.center server will detect your firewall as a man-in-the-middle attacker and drop the connection.

Rickwhite: older system updates

2025-05-08T18:11:41Z

older system updates

← Older revision		Revision as of 18:11, 8 May 2025
Line 129:		Line 129:
	* '''SSH 22''' (to *.sf.chime.center - remote tunnel for API and backups)		* '''SSH 22''' (to *.sf.chime.center - remote tunnel for API and backups)
	* '''TCP 443''' (to *.sf.chime.center - updates)		* '''TCP 443''' (to *.sf.chime.center - updates)
			* '''TCP 7443''' (update systems with firmware < 1.4.20)
	* '''UDP 123''' (time sync)		* '''UDP 123''' (time sync)
	Chime Master ringing systems do not support Deep Packet Inspection of SSH packets (DPI-SSH), typically encountered on SonicWall products. If your network must enable DPI-SSH (very rare circumstances), disable it for the ringing system's (static) IP or mac address to allow API tunneling. Otherwise, the chime.center server will detect your firewall as a man-in-the-middle attacker and drop the connection.		Chime Master ringing systems do not support Deep Packet Inspection of SSH packets (DPI-SSH), typically encountered on SonicWall products. If your network must enable DPI-SSH (very rare circumstances), disable it for the ringing system's (static) IP or mac address to allow API tunneling. Otherwise, the chime.center server will detect your firewall as a man-in-the-middle attacker and drop the connection.

← Older revision		Revision as of 18:40, 23 January 2026
Line 8:		Line 8:
	* Continual time clock synchronization		* Continual time clock synchronization
	* [[Remote_AX\|Remote control]] experience is enhanced		* [[Remote_AX\|Remote control]] experience is enhanced
	* Advanced music, seasons and schedules using [[Using_Chime_Center\|Chime Center]]		* Advanced music, seasons and schedules using [[Using_Chime_Center\|Chime.Center]]
	* Automatic software and security updates		* Automatic software and security updates
	== Check your connection ==		== Check your connection ==
Line 14:		Line 14:
	You can tell if the system is connected to the Internet by checking the connection icon found on the PIN login screen at the top right corner, just below the system status icon. It will display one of the following states:		You can tell if the system is connected to the Internet by checking the connection icon found on the PIN login screen at the top right corner, just below the system status icon. It will display one of the following states:
	* Check mark on the globe - indicates the system has full Internet connectivity		* Check mark on the globe - indicates the system has full Internet connectivity
	* X mark on the globe - indicates the system is not able to reach the Chime Center server		* X mark on the globe - indicates the system is not able to reach the Chime.Center server
	* '''AP''' (no globe) - indicates the system is in Access Point (AP) mode for local remote control		* '''AP''' (no globe) - indicates the system is in Access Point (AP) mode for local remote control
	** Turn on Access Point mode whenever you cannot connect the ringing system to the Internet, even if you do not need the local remote control. This will turn off Internet services so that errors resulting from these missing connections will not degrade your ringing system's performance.		** Turn on Access Point mode whenever you cannot connect the ringing system to the Internet, even if you do not need the local remote control. This will turn off Internet services so that errors resulting from these missing connections will not degrade your ringing system's performance.
Line 78:		Line 78:
	* Leave the WiFi antenna plugged in only if you are ''not'' connecting using an Ethernet cable.		* Leave the WiFi antenna plugged in only if you are ''not'' connecting using an Ethernet cable.

	Restart the system as described below. When the system starts with the Access Point switch set to '''Normal''', update, backup and other Chime Center remote features are enabled.		Restart the system as described below. When the system starts with the Access Point switch set to '''Normal''', update, backup and other Chime.Center remote features are enabled.

	==== Verify connection and reset Remote ====		==== Verify connection and reset Remote ====
Line 84:		Line 84:
	* Return to the home page, then tap the Remote button.		* Return to the home page, then tap the Remote button.
	* After entering your PIN, the system will check its network connection status.		* After entering your PIN, the system will check its network connection status.
	* Above the QR code the system will indicate that this code is for the Chime Center Remote.		* Above the QR code the system will indicate that this code is for the Chime.Center Remote.
	* Make sure your phone has Internet access and scan the QR code with your phone’s camera or QR reader. Tap the link which is provided from the QR code to open the '''Chime Remote''' in your phone's browser.		* Make sure your phone has Internet access and scan the QR code with your phone’s camera or QR reader. Tap the link which is provided from the QR code to open the '''Chime Remote''' in your phone's browser.

Line 118:		Line 118:

	== Security ==		== Security ==
	AX ringing systems do not require static IP addresses or any special inbound port forwarding through your firewall. Chime Center's routing will make sure that only you have control of your bells. Best practices should be followed whenever connecting anything other than computers and printers to your network and the Internet. The following are a few suggestions that you should consider. The easiest are at the top and should be complied with first.		AX ringing systems do not require static IP addresses or any special inbound port forwarding through your firewall. Chime.Center's routing will make sure that only you have control of your bells. Best practices should be followed whenever connecting anything other than computers and printers to your network and the Internet. The following are a few suggestions that you should consider. The easiest are at the top and should be complied with first.

	=== Ringing system ===		=== Ringing system ===
	* [[User_profile_setup_AX\|Change the default login PIN number]] for the login screen. Users who have (or guess) this code can use the front panel remote screen to authenticate remote access. You can use up to 10 digits.		* [[User_profile_setup_AX\|Change the default login PIN number]] for the login screen. Users who have (or guess) this code can use the front panel remote screen to authenticate remote access. You can use up to 10 digits.
	* Use a strong password to login to Chime Center. Use a password manager to generate unique and strong passwords for each of your site logins. Never re-use your email password on other sites.		* Use a strong password to login to Chime.Center. Use a password manager to generate unique and strong passwords for each of your site logins. Never re-use your email password on other sites.
	* Do not attempt to simultaneously use the wired Ethernet connection and the WiFi antenna connection. Make sure the Access Point is set to '''Normal''' (see above) if you are connected to a network. Necessary services are inhibited by the Access Point mode such as:		* Do not attempt to simultaneously use the wired Ethernet connection and the WiFi antenna connection. Make sure the Access Point is set to '''Normal''' (see above) if you are connected to a network. Necessary services are inhibited by the Access Point mode such as:
	** Automatic clock synchronization		** Automatic clock synchronization
	** Software updates		** Software updates
	** Chime Center access		** Chime.Center access
	* Do not connect the ringing system directly to the Internet without a firewall (router based or dedicated).		* Do not connect the ringing system directly to the Internet without a firewall (router based or dedicated).

Line 141:		Line 141:
	'''Verizon''' router/modem firewalls often default to closing connections to port 22. Check if your security settings is set to maximum. If so, manually add SSH 22.		'''Verizon''' router/modem firewalls often default to closing connections to port 22. Check if your security settings is set to maximum. If so, manually add SSH 22.

	Chime Center does not support Deep Packet Inspection of SSH packets (DPI-SSH), typically encountered on '''SonicWall''' products. If your network must enable DPI-SSH (very rare circumstances), disable it for the ringing system's (static) IP or mac address to allow API tunneling. Otherwise, the ~~chime~~.~~center~~ server will detect your firewall as a man-in-the-middle attacker and drop the connection.		Chime.Center does not support Deep Packet Inspection of SSH packets (DPI-SSH), typically encountered on '''SonicWall''' products. If your network must enable DPI-SSH (very rare circumstances), disable it for the ringing system's (static) IP or mac address to allow API tunneling. Otherwise, the Chime.Center server will detect your firewall as a man-in-the-middle attacker and drop the connection.

	==== Best Practices ====		==== Best Practices ====