Custom Node Announcements - Revision history

KM4NNO at 16:29, 1 January 2021

2021-01-01T16:29:13Z

Bryan: /* Important changes */

2020-06-04T20:08:25Z

Important changes

Bryan: /* Important changes */

2020-06-04T20:04:43Z

Important changes

Bryan at 20:03, 4 June 2020

2020-06-04T20:03:31Z

Bryan at 22:25, 7 December 2018

2018-12-07T22:25:34Z

Bryan at 22:20, 7 December 2018

2018-12-07T22:20:55Z

Bryan: Created page with "AllStar supports custom node announcements or node names. These will be played in place of the node number. The distribution of these is optional and each node will use rsyn..."

2018-12-07T22:19:19Z

Created page with "AllStar supports custom node announcements or node names. These will be played in place of the node number. The distribution of these is optional and each node will use rsyn..."

New page

AllStar supports custom node announcements or node names. These will be played in place of the node number.

The distribution of these is optional and each node will use rsync to download new ones about 2-3 times per day. This is done via the rc.updatenodelist script and requires '''rsync''' to be installed.

== Making custom announcements ==

Steve Rodgers has a PDF document on producing a file in the format required for any custom announcement in AllStar. [https://www.audacityteam.org/ Audacity] can be used to convert almost any sound file into the proper format.

[[File:RecordingSoundFiles.pdf]]

If you intend to make the announcement avialble network wide, please see the requirements for node names below

== Adding new announcements ==

AllStar requires the following for node announcements:

* ulaw 8 bit wave
* under 10 seconds
* under 100k in size

The file should be named $nodeNumber.ulaw and placed in /var/lib/asterisk/sounds/rpt/nodenames
This will add it to that local node. Should you want it to be used across all nodes, see the next section.

== Network Announcements ==

To enable the node announcements to propagate to the rest of the nodes, AllStarLink can add them to the main repository. Eventually this will be in the web portal, but for now must be done via a email.

The following applies to network announcements:
A networks announcement may consist of a reading of the node number, callsign, location or other short identification of the node. This should be inoffensive benign language; suitable for any audience. The ASL admin team will remove and ban users caught abusing this service.

Once you have the announcement working locally, please email it to [http://mailto:helpdesk@allstarlink.org helpdesk@allstarlink.org].

Our admin team will test it and then add it to the repository. Nodes will begin updating it, but it can take up to 24 hours for some nodes to update.

@@ Line 1: / Line 1: @@
-AllStar supports custom node announcements or node names.  These will be played in place of the node number.
+PTTLink supports custom node announcements or node names.  These will be played in place of the node number.
-The distribution of these is optional and each node will use rsync to download new ones about 2-3 times per day.  This is done via the rc.updatenodelist script in ASL 1.01 and before, or NodeNameUpdate.sh via cron in newer releases.  It requires '''rsync''' to be installed.
+The distribution of these is optional and each node will use rsync to download new ones about 2-3 times per day.  This is done via the rc.updatenodelist script in PTTLink 1.01 and before, or NodeNameUpdate.sh via cron in newer releases.  It requires '''rsync''' to be installed.
 == Important changes ==
-As of June 4, 2019 rsync://allstarlink.org no longer works.  This has moved to rsync.allstarlink.org.
+As of June 4, 2019 rsync://pttlink.org no longer works.  This has moved to rsync.pttlink.org.
-It is suggested you change the rc.updatenodelist file to use rsync.allstarlink.org.
+It is suggested you change the rc.updatenodelist file to use rsync.pttlink.org.
 The following sed command can make the change automatically for you.
-  sed -i 's/rsync:\/\/allstarlink.org\/connect-messages/rsync:\/\/rsync.allstarlink.org\/connect-messages/g' /usr/local/bin/rc.updatenodelist
+  sed -i 's/rsync:\/\/pttlink.org\/connect-messages/rsync:\/\/rsync.pttlink.org\/connect-messages/g' /usr/local/bin/rc.updatenodelist
 Be sure you reboot or kill the rc.updatenodelist process to have it respawn from init.
@@ Line 17: / Line 17: @@
 == Making custom announcements ==
-Steve Rodgers has a PDF document on producing a file in the format required for any custom announcement in AllStar.
+Steve Rodgers has a PDF document on producing a file in the format required for any custom announcement in PTTLink.
 [https://www.audacityteam.org/ Audacity] can be used to convert almost any sound file into the proper format.
@@ Line 27: / Line 27: @@
 == Adding new announcements ==
-AllStar requires the following for node announcements:
+PTTLink requires the following for node announcements:
 * ulaw 8 bit wave
@@ Line 39: / Line 39: @@
 == Network Announcements ==
-To enable the node announcements to propagate to the rest of the nodes, AllStarLink can add them to the main repository.  Eventually this will be in the web portal, but for now must be done via a email.
+To enable the node announcements to propagate to the rest of the nodes, PTTLink can add them to the main repository.  Eventually this will be in the web portal, but for now must be done via a email.
 The following applies to network announcements:
-<blockquote>A networks announcement may consist of a reading of the node number, callsign, location or other short identification of the node.  This should be inoffensive benign language; suitable for any audience.  The ASL admin team will remove and ban users caught abusing this service.</blockquote>Once you have the announcement working locally, please email it to [http://mailto:helpdesk@allstarlink.org helpdesk@allstarlink.org].
+<blockquote>A networks announcement may consist of a reading of the node number, callsign, location or other short identification of the node.  This should be inoffensive benign language; suitable for any audience.  The PTTLink admin team will remove and ban users caught abusing this service.</blockquote>Once you have the announcement working locally, please email it to [http://mailto:helpdesk@pttlink.org helpdesk@pttlink.org].
 Our admin team will test it and then add it to the repository.  Nodes will begin updating it, but it can take up to 24 hours for some nodes to update.
 [[Category:Node Configuration]]

← Older revision		Revision as of 20:08, 4 June 2020
Line 12:		Line 12:

	sed -i 's/rsync:\/\/allstarlink.org\/connect-messages/rsync:\/\/rsync.allstarlink.org\/connect-messages/g' /usr/local/bin/rc.updatenodelist		sed -i 's/rsync:\/\/allstarlink.org\/connect-messages/rsync:\/\/rsync.allstarlink.org\/connect-messages/g' /usr/local/bin/rc.updatenodelist
		+
		+	Be sure you reboot or kill the rc.updatenodelist process to have it respawn from init.

	== Making custom announcements ==		== Making custom announcements ==

@@ Line 5: / Line 5: @@
 == Important changes ==
-As of June 4, 2019 rsync://allstarlink.org no longer works.
+As of June 4, 2019 rsync://allstarlink.org no longer works.  This has moved to rsync.allstarlink.org.
-It is suggested you change the re.updatenodelist file to use rsync.allstarlink.org.
+It is suggested you change the rc.updatenodelist file to use rsync.allstarlink.org.
 The following sed command can make the change automatically for you.

← Older revision		Revision as of 22:25, 7 December 2018
Line 33:		Line 33:

	Our admin team will test it and then add it to the repository. Nodes will begin updating it, but it can take up to 24 hours for some nodes to update.		Our admin team will test it and then add it to the repository. Nodes will begin updating it, but it can take up to 24 hours for some nodes to update.
		+
		+	[[Category:Node Configuration]]

@@ Line 5: / Line 5: @@
 == Making custom announcements ==
-Steve Rodgers has a PDF document on producing a file in the format required for any custom announcement in AllStar.  [https://www.audacityteam.org/ Audacity] can be used to convert almost any sound file into the proper format.
+Steve Rodgers has a PDF document on producing a file in the format required for any custom announcement in AllStar.
 [[File:RecordingSoundFiles.pdf]]
@@ Line 19: / Line 21: @@
 * under 100k in size
-The file should be named $nodeNumber.ulaw and placed in /var/lib/asterisk/sounds/rpt/nodenames
+The file should be named ''$nodeNumber.ulaw'' and placed in /var/lib/asterisk/sounds/rpt/nodenames
 This will add it to that local node.  Should you want it to be used across all nodes, see the next section.
@@ Line 27: / Line 30: @@
 The following applies to network announcements:
-A networks announcement may consist of a reading of the node number, callsign, location or other short identification of the node.  This should be inoffensive benign language; suitable for any audience.  The ASL admin team will remove and ban users caught abusing this service.
+<blockquote>A networks announcement may consist of a reading of the node number, callsign, location or other short identification of the node.  This should be inoffensive benign language; suitable for any audience.  The ASL admin team will remove and ban users caught abusing this service.</blockquote>Once you have the announcement working locally, please email it to [http://mailto:helpdesk@allstarlink.org helpdesk@allstarlink.org].
 Our admin team will test it and then add it to the repository.  Nodes will begin updating it, but it can take up to 24 hours for some nodes to update.