Telemetry - Revision history

Kg7qin at 02:43, 15 March 2021

2021-03-15T02:43:28Z

Kg7qin at 02:43, 15 March 2021

2021-03-15T02:43:06Z

Wd6awp at 20:24, 10 October 2017

2017-10-10T20:24:28Z

Wd6awp at 16:48, 9 October 2017

2017-10-09T16:48:22Z

Wd6awp at 16:47, 9 October 2017

2017-10-09T16:47:26Z

Wd6awp at 16:37, 9 October 2017

2017-10-09T16:37:36Z

Wd6awp at 16:35, 9 October 2017

2017-10-09T16:35:45Z

Wd6awp at 16:20, 9 October 2017

2017-10-09T16:20:40Z

Wd6awp at 16:18, 9 October 2017

2017-10-09T16:18:56Z

Wd6awp: Created page with " Telemetry is the message you hear when connecting to or disconnecting from another node and when another node connects or disconnects to your node. Asterisk/app_rpt sends..."

2017-10-09T16:17:22Z

Created page with " Telemetry is the message you hear when connecting to or disconnecting from another node and when another node connects or disconnects to your node. Asterisk/app_rpt sends..."

New page

Telemetry is the message you hear when connecting to or disconnecting from another node and when another node connects or disconnects to your node.

Asterisk/app_rpt sends its telemetry information to all other connected systems through digital (out-of-band, non-audio)
data over the VoIP connection. It is purely up to each local system to decide what to do with this
information. It can announce it, ignore it or even change the message. The node owner/admin determines what is appropriate for their individual node.

The configuration options mentioned below only apply to what is heard on a specific channel type;
out-of-band telemetry is silently forwarded to all other compatible nodes connected in transceive mode.

There are configuration and mode options allowing all telemetry (both local and obtained from other nodes)
to be:
* Always announced
never announced, or announced only when a function is executed and
for short time thereafter.

Note: These features document the operation of app_rpt.c version 0.186 or later.

There are 5 telemetry channels which can be individually managed:

@@ Line 1: / Line 1: @@
 [[Category: How to]]
-[[Category:Node configuration]]
+[[Category:Node Configuration]]
 Telemetry is a data message that is sent between nodes when connecting to or disconnecting from another node. Telemetry is silently sent to all other connected nodes through digital (out-of-band, non-audio) data over the VoIP connection. It is purely up to each local system to decide what to do with this information. It can announce it, ignore it or even change the message. The node owner/admin determines what is appropriate for their individual node.

@@ Line 1: / Line 1: @@
+[[Category: How to]]
 Telemetry is a data message that is sent between nodes when connecting to or disconnecting from another node. Telemetry is silently sent to all other connected nodes through digital (out-of-band, non-audio) data over the VoIP connection. It is purely up to each local system to decide what to do with this information. It can announce it, ignore it or even change the message. The node owner/admin determines what is appropriate for their individual node.
@@ Line 15: / Line 16: @@
 ''Note'': Requires app_rpt.c version 0.186 or later.

@@ Line 6: / Line 6: @@
 * Never announced
 * Announced only when a function is locally executed and for short time thereafter
 There are 5 telemetry channels which can be individually managed:
@@ Line 16: / Line 14: @@
 * GUI - IAXrpt, SIP phone display, VoIP clients
 [[Category: How to]]

← Older revision		Revision as of 16:48, 9 October 2017
Line 17:		Line 17:


−	[[Category: How To]]	+	[[Category: How to]]

← Older revision		Revision as of 16:47, 9 October 2017
Line 10:		Line 10:

	There are 5 telemetry channels which can be individually managed:		There are 5 telemetry channels which can be individually managed:
		+	* Local Node - This node
		+	* Foreign Node - A connected node
		+	* Phone - Autopatch, phone portal
		+	* Echolink - Echolink connections
		+	* GUI - IAXrpt, SIP phone display, VoIP clients
		+
		+
		+	[[Category: How To]]

← Older revision		Revision as of 16:37, 9 October 2017
Line 1:		Line 1:

−	Telemetry is a data message that is sent between nodes when connecting to or disconnecting from another node. Telemetry is silently sent to all other connected ~~systems~~ through digital (out-of-band, non-audio) data over the VoIP connection. It is purely up to each local system to decide what to do with this information. It can announce it, ignore it or even change the message. The node owner/admin determines what is appropriate for their individual node.	+	Telemetry is a data message that is sent between nodes when connecting to or disconnecting from another node. Telemetry is silently sent to all other connected nodes through digital (out-of-band, non-audio) data over the VoIP connection. It is purely up to each local system to decide what to do with this information. It can announce it, ignore it or even change the message. The node owner/admin determines what is appropriate for their individual node.

	There are configuration and mode options allowing all telemetry (both local and obtained from other nodes) to be:		There are configuration and mode options allowing all telemetry (both local and obtained from other nodes) to be:

@@ Line 1: / Line 1: @@
-Telemetry is the message you hear when connecting to or disconnecting from another node and when another node connects or disconnects to your node.
+Telemetry is a data message that is sent between nodes when connecting to or disconnecting from another node. Telemetry is silently sent to all other connected systems through digital (out-of-band, non-audio) data over the VoIP connection. It is purely up to each local system to decide what to do with this information. It can announce it, ignore it or even change the message. The node owner/admin determines what is appropriate for their individual node.
 There are configuration and mode options allowing all telemetry (both local and obtained from other nodes) to be:
@@ Line 12: / Line 8: @@
 Note: These features document the operation of app_rpt.c version 0.186 or later.
 There are 5 telemetry channels which can be individually managed: