Remote control from anywhere - Revision history

Rickwhite: EOL removed dead linnks

2025-05-02T18:05:26Z

EOL removed dead linnks

← Older revision		Revision as of 18:05, 2 May 2025
Line 4:		Line 4:

	This page pertains to legacy USB connected systems only!		This page pertains to legacy USB connected systems only!

	The information on this page assumes that you have the [[Remote control mobile app setup\|Church Bell Remote app installed]] on your phone or tablet, [[Install Management Suite\|Management Suite installed]] on a PC connected to your Chime Master bell system, and you are able to remote control the bells from inside your facility using the local WiFi network.

	== Making your bell system available on the public internet ==		== Making your bell system available on the public internet ==
Line 41:		Line 39:
	Another way of setting up a secure dedicated network for IoT devices if you have an older unused router available is to configure a [https://www.grc.com/nat/nats.htm Multi-NAT router network] as described by security guru Steve Gibson.		Another way of setting up a secure dedicated network for IoT devices if you have an older unused router available is to configure a [https://www.grc.com/nat/nats.htm Multi-NAT router network] as described by security guru Steve Gibson.

	Unfortunately, by putting the Management Suite host PC on a VLAN or other isolated subnet, you lock yourself out of being able to use a simple remote desktop to operate the Management Suite from your office PC. ~~[https://www.teamviewer.com/en/ TeamViewer]~~ will allow you to use the Management Suite (even from home).		Unfortunately, by putting the Management Suite host PC on a VLAN or other isolated subnet, you lock yourself out of being able to use a simple remote desktop to operate the Management Suite from your office PC. A remote desktop application will allow you to use the Management Suite (even from home).

	=== Setup ===		=== Setup ===

Daveallen: update

2021-10-28T21:11:57Z

update

← Older revision		Revision as of 21:11, 28 October 2021
Line 12:		Line 12:
	We always think more than twice about connecting lights, cameras and other Internet of Things (IoT) devices to our own network. So we understand your reluctance to it too. Realistically now, what is the worst case scenario? It is unlikely, but some kid might figure out your user name (your real name?) and password (the church phone number?) and make your bells ring. All night.		We always think more than twice about connecting lights, cameras and other Internet of Things (IoT) devices to our own network. So we understand your reluctance to it too. Realistically now, what is the worst case scenario? It is unlikely, but some kid might figure out your user name (your real name?) and password (the church phone number?) and make your bells ring. All night.

	Search the Internet for more information regarding IoT risk management. James Andrew Lewis in his ''[https://csis-prod.s3.amazonaws.com/s3fs-public/legacy_files/files/publication/160217_Lewis_ManagingRiskIoT_Web_Redated.pdf Managing Risk for the Internet of Things]'', says, "Being risk averse makes us poorer, not safer. There is risk in every technology we use. Hold IoT captive to our fears and we will sacrifice opportunity."		Search the Internet for more information regarding IoT risk management.

	~~Chime Master continues~~ to ~~develop~~ new ~~products using the latest technologies~~ that ~~will~~ balance ease of use with the highest security practices.		Consider upgrading your system to one of our new '''[https://www.chimemaster.com/digital-carillons Advanced eXperience]''' systems that balance ease of use with the highest security practices.

	=== Use Best Practices ===		=== Use Best Practices ===

Daveallen: legacy page

2021-10-28T20:55:38Z

legacy page

← Older revision		Revision as of 20:55, 28 October 2021
Line 1:		Line 1:
	<div style="font-size:84%">'''[http://www.ChimeMaster.com Home] > [[Chime_Master_Help\|Help]] > [[Installation_documentation\|Installation]] > [[Installation_documentation#Software\|Software]]'''</div><br />		<div style="font-size:84%">'''[http://www.ChimeMaster.com Home] > [[Chime_Master_Help\|Help]] > [[Installation_documentation\|Installation]] > [[Installation_documentation#Software\|Software]]'''</div><br />
	~~This is an~~ ''~~Advanced Topic~~''
			Current model remote setup for AX Touchscreen systems: '''[[Remote_AX\|Remote AX]]'''

			This page pertains to legacy USB connected systems only!

	The information on this page assumes that you have the [[Remote control mobile app setup\|Church Bell Remote app installed]] on your phone or tablet, [[Install Management Suite\|Management Suite installed]] on a PC connected to your Chime Master bell system, and you are able to remote control the bells from inside your facility using the local WiFi network.		The information on this page assumes that you have the [[Remote control mobile app setup\|Church Bell Remote app installed]] on your phone or tablet, [[Install Management Suite\|Management Suite installed]] on a PC connected to your Chime Master bell system, and you are able to remote control the bells from inside your facility using the local WiFi network.
Line 86:		Line 89:

	[[Category:Troubleshooting]]		[[Category:Troubleshooting]]
	[[Category:~~Manual~~]]		[[Category:Legacy Products]]

Daveallen: Troubleshooting

2018-01-25T22:06:50Z

Troubleshooting

← Older revision		Revision as of 22:06, 25 January 2018
Line 76:		Line 76:
	You will select this host when you are away from the church. When you are at church, you can either disable WiFi on the phone and continue to use the public host connection, or enable WiFi on the phone and and select the WiFi host connection in the Hosts menu of the app. Unless your router supports NAT reflection, the public host connection will not work when you are connected to WiFi because the router only redirects access from outside the LAN.		You will select this host when you are away from the church. When you are at church, you can either disable WiFi on the phone and continue to use the public host connection, or enable WiFi on the phone and and select the WiFi host connection in the Hosts menu of the app. Unless your router supports NAT reflection, the public host connection will not work when you are connected to WiFi because the router only redirects access from outside the LAN.

			== Troubleshooting ==

			* Make sure Management Suite can see the bell system. Use the Management Suite Remote panel to verify the display is the same.
			* Check the mobile Remote Control app [[Church_Bell_Remote#Error_Messages\|error messages]]
			* Try accessing the Management Suite host port from another PC browser.
			** Begin with another browser on the same local network Enter the URL as IPaddress:Port (example: http://192.168.20.62:6777 the IP will be different for you)
			** Try a mobile browser with WiFi turned off, using the public IP for your facility (Google ''What is my IP'')
			** You should see a screen from the Millennium Suite server. If not, troubleshoot the network and firewalls.

			[[Category:Troubleshooting]]
	[[Category:Manual]]		[[Category:Manual]]

Daveallen: /* Setup */

2018-01-25T21:25:12Z

Setup

← Older revision		Revision as of 21:25, 25 January 2018
Line 42:		Line 42:
	=== Setup ===		=== Setup ===

	==== Management Suite PC ~~====~~		==== Use a static IP address on the Management Suite PC ====

	~~===== Set a static IP =~~====

	Every device on the network needs to have a unique IP address. By default, Windows PCs will get their IP addresses from the DHCP server on the network. This may be your Windows file server, or it may be the Internet Router. Typically the DHCP server will be set to provide a range of addresses dynamically. Outside this block of dynamic addresses will be static IP addresses that are reserved for file servers, printers and any other devices that are always connected.		Every device on the network needs to have a unique IP address. By default, Windows PCs will get their IP addresses from the DHCP server on the network. This may be your Windows file server, or it may be the Internet Router. Typically the DHCP server will be set to provide a range of addresses dynamically. Outside this block of dynamic addresses will be static IP addresses that are reserved for file servers, printers and any other devices that are always connected.
Line 50:		Line 48:
	It is more convenient for us to connect to the bell system if it doesn't move as dynamic IP leases expire. Before you set a static address on the PC, you need to know which addresses are already used. After setting it, you should document or inform others that manage the network which address you have taken.		It is more convenient for us to connect to the bell system if it doesn't move as dynamic IP leases expire. Before you set a static address on the PC, you need to know which addresses are already used. After setting it, you should document or inform others that manage the network which address you have taken.

	==== Port Forwarding ====		==== Port Forwarding incoming remote commands to the PC ====

	If you have your tablet or phone already controlling the bell system on an internal network we can add it to the public network by forwarding the port of the bell system's server (the Management Suite host PC) out through the router's firewall. The port we want to forward is 6777 and the address we want to limit access of this port to is the PC hosting the Management Suite remote control server.		If you have your tablet or phone already controlling the bell system on an internal network we can add it to the public network by forwarding the port of the bell system's server (the Management Suite host PC) out through the router's firewall. The port we want to forward is 6777 and the address we want to limit access of this port to is the IP address of the PC hosting the Management Suite remote control server.

	You will set this up either on your firewall appliance if you have one or the Internet connected router if you don't. The menu items for this will vary for different devices. The pfSense firewall appliance put this under Firewall > NAT > PortForward. The following parameters (similar prompts will be available on other firewalls) will be entered to create a new Port Forward:		You will set this up either on your firewall appliance if you have one or the Internet connected router if you don't. The menu items for this will vary for different devices. The pfSense firewall appliance put this under Firewall > NAT > PortForward. The following parameters (similar prompts will be available on other firewalls) will be entered to create a new Port Forward:

Daveallen: /* Management Suite PC */

2018-01-25T21:22:44Z

Management Suite PC

← Older revision		Revision as of 21:22, 25 January 2018
Line 43:		Line 43:

	==== Management Suite PC ====		==== Management Suite PC ====

			===== Set a static IP =====

	Every device on the network needs to have a unique IP address. By default, Windows PCs will get their IP addresses from the DHCP server on the network. This may be your Windows file server, or it may be the Internet Router. Typically the DHCP server will be set to provide a range of addresses dynamically. Outside this block of dynamic addresses will be static IP addresses that are reserved for file servers, printers and any other devices that are always connected.		Every device on the network needs to have a unique IP address. By default, Windows PCs will get their IP addresses from the DHCP server on the network. This may be your Windows file server, or it may be the Internet Router. Typically the DHCP server will be set to provide a range of addresses dynamically. Outside this block of dynamic addresses will be static IP addresses that are reserved for file servers, printers and any other devices that are always connected.

Daveallen: /* Advanced security */

2017-07-11T21:56:26Z

Advanced security

← Older revision		Revision as of 21:56, 11 July 2017
Line 38:		Line 38:
	Another way of setting up a secure dedicated network for IoT devices if you have an older unused router available is to configure a [https://www.grc.com/nat/nats.htm Multi-NAT router network] as described by security guru Steve Gibson.		Another way of setting up a secure dedicated network for IoT devices if you have an older unused router available is to configure a [https://www.grc.com/nat/nats.htm Multi-NAT router network] as described by security guru Steve Gibson.

	Unfortunately, by putting the Management Suite host PC on a VLAN or other isolated subnet, you lock yourself out of being able to use a simple remote desktop to operate the Management Suite from your office PC. ~~LogMeIn or GoToMyPC~~ will allow you to use the ~~Mangement~~ Suite (even from home).		Unfortunately, by putting the Management Suite host PC on a VLAN or other isolated subnet, you lock yourself out of being able to use a simple remote desktop to operate the Management Suite from your office PC. [https://www.teamviewer.com/en/ TeamViewer] will allow you to use the Management Suite (even from home).

	=== Setup ===		=== Setup ===

Rickwhite: bc

2017-01-14T16:53:26Z

← Older revision		Revision as of 16:53, 14 January 2017
Line 1:		Line 1:
	''Advanced Topic''		<div style="font-size:84%">'''[http://www.ChimeMaster.com Home] > [[Chime_Master_Help\|Help]] > [[Installation_documentation\|Installation]] > [[Installation_documentation#Software\|Software]]'''</div><br />
			This is an ''Advanced Topic''

	The information on this page assumes that you have the [[Remote control mobile app setup\|Church Bell Remote app installed]] on your phone or tablet, [[Install Management Suite\|Management Suite installed]] on a PC connected to your Chime Master bell system, and you are able to remote control the bells from inside your facility using the local WiFi network.		The information on this page assumes that you have the [[Remote control mobile app setup\|Church Bell Remote app installed]] on your phone or tablet, [[Install Management Suite\|Management Suite installed]] on a PC connected to your Chime Master bell system, and you are able to remote control the bells from inside your facility using the local WiFi network.

Rickwhite: /* Don't make hacking easy */

2016-12-19T18:41:10Z

Don't make hacking easy

← Older revision		Revision as of 18:41, 19 December 2016
Line 27:		Line 27:
	Do not use the port number our products assign the remote control by default. Make up your own and make sure all settings from the host software through firewalls (both software and hardware) and routers as well as the host setting on the phone app are set to the same port.		Do not use the port number our products assign the remote control by default. Make up your own and make sure all settings from the host software through firewalls (both software and hardware) and routers as well as the host setting on the phone app are set to the same port.

	If you do not need to access the bells for awhile, use the mobile app Settings menu to Log Out. No one can control the bells without re-authenticating.		If you do not need to access the bells for awhile, use the mobile app Settings menu to Log Out. No one can control the bells without re-authenticating. Logging back in will not require your password using your phone, it is encrypted and stored both on your phone and on the bell system itself (end to end encryption).

	==== Advanced security ====		==== Advanced security ====

Rickwhite: /* Making your bell system available on the public internet - restructured

2016-12-19T18:35:34Z

/* Making your bell system available on the public internet - restructured

← Older revision		Revision as of 18:35, 19 December 2016
Line 5:		Line 5:
	== Making your bell system available on the public internet ==		== Making your bell system available on the public internet ==

	=== ~~Risks~~ ===		=== Understand the risks ===
	We always think more than twice about connecting lights, cameras and other Internet of Things (IoT) devices to our own network. So we understand your reluctance to it too. Realistically now, what is the worst case scenario? It is unlikely, but some kid might figure out your user name (your real name?) and password (the church phone number?) and make your bells ring. All night.		We always think more than twice about connecting lights, cameras and other Internet of Things (IoT) devices to our own network. So we understand your reluctance to it too. Realistically now, what is the worst case scenario? It is unlikely, but some kid might figure out your user name (your real name?) and password (the church phone number?) and make your bells ring. All night.

Line 12:		Line 12:
	Chime Master continues to develop new products using the latest technologies that will balance ease of use with the highest security practices.		Chime Master continues to develop new products using the latest technologies that will balance ease of use with the highest security practices.

	==== Best Practices ====		=== Use Best Practices ===
	Don't network your bells unless you really need to control them when you are away.
			==== Do you need it? ====
			Don't network your bells unless you really need to control them when you are away. Most remote control needs are met using local secure WiFi behind your public facing firewall.

			==== Common sense security ====

	Keep your Windows, phones, tablets, software and firmware up to date. We are not fans of third party anti virus software. Windows 10 comes with all of the security you should reasonably need. Always add Microsoft Security Essentials to Windows 7. Don't use any other version of Windows than these two. Don't visit nasty websites. Don't respond to email asking for personal information or taking you to web pages that do the same. Don't run with scissors.		Keep your Windows, phones, tablets, software and firmware up to date. We are not fans of third party anti virus software. Windows 10 comes with all of the security you should reasonably need. Always add Microsoft Security Essentials to Windows 7. Don't use any other version of Windows than these two. Don't visit nasty websites. Don't respond to email asking for personal information or taking you to web pages that do the same. Don't run with scissors.

			==== Don't make hacking easy ====

	The system requires user authentication before accepting commands from the remote control. This authentication process is only as strong as your user name and password that you have created in Management Suite. You should also lock the Management Suite host computer with a good username and password to prevent unauthorized users from changing the authorized users of the bell system. Use a nickname no one knows they called you in 4th grade. The password should be as long and as random as possible. The app will remember it, but you will need it again if you update your phone. Store it in a secure note using a password manager like LastPass.		The system requires user authentication before accepting commands from the remote control. This authentication process is only as strong as your user name and password that you have created in Management Suite. You should also lock the Management Suite host computer with a good username and password to prevent unauthorized users from changing the authorized users of the bell system. Use a nickname no one knows they called you in 4th grade. The password should be as long and as random as possible. The app will remember it, but you will need it again if you update your phone. Store it in a secure note using a password manager like LastPass.
Line 22:		Line 28:

	If you do not need to access the bells for awhile, use the mobile app Settings menu to Log Out. No one can control the bells without re-authenticating.		If you do not need to access the bells for awhile, use the mobile app Settings menu to Log Out. No one can control the bells without re-authenticating.

			==== Advanced security ====

	Modern routers have firewalls built in, but many IT professionals will add a dedicated firewall appliance between the incoming internet router or modem and their internal network. In the absence of a dedicated firewall, install a router that includes as many of the items on this [http://routersecurity.org/checklist.php Router Security Checklist] as you can.		Modern routers have firewalls built in, but many IT professionals will add a dedicated firewall appliance between the incoming internet router or modem and their internal network. In the absence of a dedicated firewall, install a router that includes as many of the items on this [http://routersecurity.org/checklist.php Router Security Checklist] as you can.