Algo 8180 Provisioning With ACF - Revision history

Zcrayfish: /* Overview */ Fixed dead link.

2023-08-30T18:44:56Z

Overview: Fixed dead link.

← Older revision		Revision as of 18:44, 30 August 2023
Line 1:		Line 1:
	{{Draft}}		{{Draft}}
	= Overview =		= Overview =
	This page describes how to provision [~~http~~://algosolutions.com/~~products/Audible-and-Visual-Alerting~~/8180-sip-audio-alerter~~.html~~ Algo 8180]~~{{dead link}}~~ devices using [[SIP Provisioning On Alpine Linux]] based upon the ACF web interface. It is supported starting with Alpine Linux 3.2.		This page describes how to provision [https://www.algosolutions.com/product/8180-sip-audio-alerter/ Algo 8180] devices using [[SIP Provisioning On Alpine Linux]] based upon the ACF web interface. It is supported starting with Alpine Linux 3.2.

	= Setup Procedure=		= Setup Procedure=

Zcrayfish: /* Overview */ Marked a dead link

2021-12-20T01:56:14Z

Overview: Marked a dead link

← Older revision		Revision as of 01:56, 20 December 2021
Line 1:		Line 1:
	{{Draft}}		{{Draft}}
	= Overview =		= Overview =
	This page describes how to provision [http://algosolutions.com/products/Audible-and-Visual-Alerting/8180-sip-audio-alerter.html Algo 8180] devices using [[SIP Provisioning On Alpine Linux]] based upon the ACF web interface. It is supported starting with Alpine Linux 3.2.		This page describes how to provision [http://algosolutions.com/products/Audible-and-Visual-Alerting/8180-sip-audio-alerter.html Algo 8180]{{dead link}} devices using [[SIP Provisioning On Alpine Linux]] based upon the ACF web interface. It is supported starting with Alpine Linux 3.2.

	= Setup Procedure=		= Setup Procedure=

Ttrask: Add ACF category

2016-07-26T23:27:00Z

Add ACF category

← Older revision		Revision as of 23:27, 26 July 2016
Line 22:		Line 22:
	**Config Download Path: Algo		**Config Download Path: Algo
	**Firmware Download Path: Algo		**Firmware Download Path: Algo

			[[Category:ACF]]

Ttrask: Manual firmware update is not necessary anymore

2015-06-09T19:13:25Z

Manual firmware update is not necessary anymore

← Older revision		Revision as of 19:13, 9 June 2015
Line 13:		Line 13:
	The Algo will override ALL parameters when it is provisioned. If parameters are not provided by the provisioning server, they will be reset to default. Since not all parameters are included in the provisioning database, they must be configured statically in ''/var/www/provisioning/htdocs/Algo/init.cfg''. You can use ''/var/www/provisioning/htdocs/Algo/init.cfg.sample'' as a starting point. You will probably need to modify the network configuration and provisioning server IP.		The Algo will override ALL parameters when it is provisioned. If parameters are not provided by the provisioning server, they will be reset to default. Since not all parameters are included in the provisioning database, they must be configured statically in ''/var/www/provisioning/htdocs/Algo/init.cfg''. You can use ''/var/www/provisioning/htdocs/Algo/init.cfg.sample'' as a starting point. You will probably need to modify the network configuration and provisioning server IP.
	cp /var/www/provisioning/htdocs/Algo/init.cfg.sample /var/www/provisioning/htdocs/Algo/init.cfg		cp /var/www/provisioning/htdocs/Algo/init.cfg.sample /var/www/provisioning/htdocs/Algo/init.cfg
	== 4~~. Update the Algo firmware ==~~		== 4. Configure the Algo 8180 to connect to the provisioning server ==
	~~Unfortunately, the Algo firmware update is a manual process:~~
	*MENU System > Maintenance > Upgrade to New Firmware
	**Method: From URL
	**Upgrade URL: http://<IP or FQDN of provisioning>/Algo/algo-8180-2.4.fw
	**Click Upgrade button
	~~== 5~~. Configure the Algo 8180 to connect to the provisioning server ==
	Unfortunately, the DHCP option 66 does not seem to work in our testing. So, you must manually configure the Algo to connect to the provisioning server. Once you get the Algo device connected to the network, follow these steps:		Unfortunately, the DHCP option 66 does not seem to work in our testing. So, you must manually configure the Algo to connect to the provisioning server. Once you get the Algo device connected to the network, follow these steps:
	*MENU Advanced Settings > Provisioning		*MENU Advanced Settings > Provisioning

Ttrask: Add manual firmware upgrade

2015-06-09T16:04:46Z

Add manual firmware upgrade

← Older revision		Revision as of 16:04, 9 June 2015
Line 13:		Line 13:
	The Algo will override ALL parameters when it is provisioned. If parameters are not provided by the provisioning server, they will be reset to default. Since not all parameters are included in the provisioning database, they must be configured statically in ''/var/www/provisioning/htdocs/Algo/init.cfg''. You can use ''/var/www/provisioning/htdocs/Algo/init.cfg.sample'' as a starting point. You will probably need to modify the network configuration and provisioning server IP.		The Algo will override ALL parameters when it is provisioned. If parameters are not provided by the provisioning server, they will be reset to default. Since not all parameters are included in the provisioning database, they must be configured statically in ''/var/www/provisioning/htdocs/Algo/init.cfg''. You can use ''/var/www/provisioning/htdocs/Algo/init.cfg.sample'' as a starting point. You will probably need to modify the network configuration and provisioning server IP.
	cp /var/www/provisioning/htdocs/Algo/init.cfg.sample /var/www/provisioning/htdocs/Algo/init.cfg		cp /var/www/provisioning/htdocs/Algo/init.cfg.sample /var/www/provisioning/htdocs/Algo/init.cfg
	== 4. Configure the Algo 8180 to connect to the provisioning server ==		== 4. Update the Algo firmware ==
			Unfortunately, the Algo firmware update is a manual process:
			*MENU System > Maintenance > Upgrade to New Firmware
			**Method: From URL
			**Upgrade URL: http://<IP or FQDN of provisioning>/Algo/algo-8180-2.4.fw
			**Click Upgrade button
			== 5. Configure the Algo 8180 to connect to the provisioning server ==
	Unfortunately, the DHCP option 66 does not seem to work in our testing. So, you must manually configure the Algo to connect to the provisioning server. Once you get the Algo device connected to the network, follow these steps:		Unfortunately, the DHCP option 66 does not seem to work in our testing. So, you must manually configure the Algo to connect to the provisioning server. Once you get the Algo device connected to the network, follow these steps:
	*MENU Advanced Settings > Provisioning		*MENU Advanced Settings > Provisioning

Ttrask: First cut

2015-06-09T14:04:20Z

First cut

New page

{{Draft}}
= Overview =
This page describes how to provision [http://algosolutions.com/products/Audible-and-Visual-Alerting/8180-sip-audio-alerter.html Algo 8180] devices using [[SIP Provisioning On Alpine Linux]] based upon the ACF web interface. It is supported starting with Alpine Linux 3.2.

= Setup Procedure=
== 1. Install provisioning server ==
First, install the provisioning server according to the instructions at [[SIP Provisioning On Alpine Linux | this page]].
== 2. Install firmware package ==
The latest supported firmware is included in a package:
apk add acf-provisioning-algo
{{Note|If you are running-from-RAM, it is recommended to mount /var/ to a hard disk to prevent data loss. If you do so, you should fetch the firmware packages, rather than install them. This way, the firmware will not take up RAM. You can use the following command: apk fetch --quiet --stdout acf-provisioning-algo | tar -C / -zvx}}
== 3. Configure init.cfg ==
The Algo will override ALL parameters when it is provisioned. If parameters are not provided by the provisioning server, they will be reset to default. Since not all parameters are included in the provisioning database, they must be configured statically in ''/var/www/provisioning/htdocs/Algo/init.cfg''. You can use ''/var/www/provisioning/htdocs/Algo/init.cfg.sample'' as a starting point. You will probably need to modify the network configuration and provisioning server IP.
cp /var/www/provisioning/htdocs/Algo/init.cfg.sample /var/www/provisioning/htdocs/Algo/init.cfg
== 4. Configure the Algo 8180 to connect to the provisioning server ==
Unfortunately, the DHCP option 66 does not seem to work in our testing. So, you must manually configure the Algo to connect to the provisioning server. Once you get the Algo device connected to the network, follow these steps:
*MENU Advanced Settings > Provisioning
**Provisioning Mode: Enabled
**Server Method: Static
**Static Server: Enter the IP address or FQDN of the provisioning server
**Download Method: HTTP
**Config Download Path: Algo
**Firmware Download Path: Algo