https://wiki.pttlink.org/api.php?action=feedcontributions&feedformat=atom&user=N8THN"PTTLink Wiki" - User contributions [en]2026-06-02T14:40:05ZUser contributionsMediaWiki 1.35.5https://wiki.pttlink.org/index.php?title=User_talk:KB7ACL&diff=1483User talk:KB7ACL2019-12-04T15:39:55Z<p>N8THN: Welcome!</p>
<hr />
<div>[]</div>N8THNhttps://wiki.pttlink.org/index.php?title=User:KB7ACL&diff=1482User:KB7ACL2019-12-04T15:39:55Z<p>N8THN: Creating user page for new user.</p>
<hr />
<div>I originally became a licensed operator through a High School class in 1990. I recently got back into the hobby and re-took my technician exam.</div>N8THNhttps://wiki.pttlink.org/index.php?title=User_talk:Kb8zgl&diff=1474User talk:Kb8zgl2019-11-29T20:49:03Z<p>N8THN: Welcome!</p>
<hr />
<div>[]</div>N8THNhttps://wiki.pttlink.org/index.php?title=User:Kb8zgl&diff=1473User:Kb8zgl2019-11-29T20:49:03Z<p>N8THN: Creating user page for new user.</p>
<hr />
<div>Amateur Radio Operator who helps with ASL</div>N8THNhttps://wiki.pttlink.org/index.php?title=User_talk:W8ENT&diff=1472User talk:W8ENT2019-11-29T20:47:45Z<p>N8THN: Welcome!</p>
<hr />
<div>[]</div>N8THNhttps://wiki.pttlink.org/index.php?title=User:W8ENT&diff=1471User:W8ENT2019-11-29T20:47:45Z<p>N8THN: Creating user page for new user.</p>
<hr />
<div>Amateur Radio Operator, Extra Class. Cascade, MI.</div>N8THNhttps://wiki.pttlink.org/index.php?title=Server_Provisioning&diff=1468Server Provisioning2019-10-22T21:35:40Z<p>N8THN: /* Ubuntu 18 Config */</p>
<hr />
<div>This is intended to be a reference for setting up a VM or Server for AllStatLink. <br />
<br />
= Server Overview = <br />
<br />
== Basic Requirements ==<br />
AllStarLink has standardized on Ubuntu 16.04 LTS for it's servers. <br />
<br />
The minimum configuration of any server will be 2 cores of 2 GHz or faster, 4 GiB of ram and 40 GiB of Disk. <br />
<br />
All new servers shall support IPv6, or have it available from the hosting provider.<br />
<br />
Reverse IP's shall be delegated via a CNAME to $NAME.PTR.allstarlink.org, where $NAME is the name of the server.<br />
<br />
All servers shall be partitioned to use / as the only partition unless a specific configuration is required. <br />
<br />
== Install guide == <br />
<br />
When provisioning a new server<br />
<br />
* check the VM is setup (cpu/mem/disk) as it should be, if not contact the provider<br />
<br />
cat /proc/cpuinfo |grep processor<br />
processor : 0<br />
processor : 1<br />
processor : 2<br />
processor : 3<br />
<br />
<br />
* on the server install python (apt-get install python). This is needed for the ansibile provisioning<br />
* setup the server in the infrastructure configs and push the users and keys to it. <br />
<br />
=== Mandatory Software ===<br />
<br />
All servers require this software<br />
<br />
apt-get install ntp ntpdate python vim screen ipsec-tools strongswan fail2ban snmp haveged libacl1-dev python3-dev libssl-dev gcc g++ fio pbzip2 ncdu<br />
<br />
=== Mandatory Configs ===<br />
<br />
==== Ubuntu 18 Config ====<br />
<br />
Ubuntu 18 uses the net netplan config. It's gay as fuck.<br />
<br />
First you need to disable the resolved service:<br />
<br />
sudo systemctl disable systemd-resolved.service<br />
sudo systemctl stop systemd-resolved<br />
rm /etc/resolv.conf <br />
sudo touch /etc/cloud/cloud-init.disabled<br />
sudo apt-get purge cloud-init<br />
<br />
echo "nameserver 1.1.1.1" > /etc/resolv.conf<br />
apt-get install ifupdown<br />
<br />
Configure /etc/network/interfaces<br />
<br />
systemctl unmask networking<br />
systemctl enable networking<br />
systemctl restart networking<br />
<br />
systemctl stop systemd-networkd.socket systemd-networkd networkd-dispatcher systemd-networkd-wait-online<br />
systemctl disable systemd-networkd.socket systemd-networkd networkd-dispatcher systemd-networkd-wait-online<br />
systemctl mask systemd-networkd.socket systemd-networkd networkd-dispatcher systemd-networkd-wait-online<br />
apt-get --assume-yes purge nplan netplan.io<br />
<br />
==== Network Config ====<br />
* The network should be configured to use /etc/network/interfaces, and add DNS and the firewall to it and search in the allstarlink.org domain<br />
<br />
# The primary network interface<br />
auto eth0<br />
iface eth0 inet6 static<br />
address 9805:0900:0340:1000::2600/64<br />
autoconf 0<br />
accept_ra 2 <br />
iface eth0 inet static<br />
address 44.103.0.49<br />
netmask 255.255.255.0<br />
network 44.103.0.0<br />
broadcast 44.103.0.255<br />
gateway 44.103.0.1 <br />
dns-nameservers 44.103.0.4 1.1.1.1<br />
dns-search allstarlink.org<br />
up /etc/network/firewall.sh<br />
<br />
* There is typically only one network interface, and it will be named dynamically. We must setup this using udev to be persistent<br />
<br />
root@server# ifconfig |grep HWaddr<br />
eth0 Link encap:Ethernet HWaddr 52:54:00:73:86:06 <br />
<br />
Now take this HWaddr and put it in the config file<br />
echo 'SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="52:54:00:73:86:06", ATTR{dev_id}=="0x0", ATTR{type}=="1", NAME="eth0"' >/etc/udev/rules.d/70-persistent-net.rules<br />
<br />
* configure screen to use the scroll back buffer<br />
vim /etc/screenrc<br />
uncomment "termcapinfo xterm|xterms|xs|rxvt ti@:te@"<br />
<br />
* configure bash completion for interactive shells<br />
vim /etc/bash.bashrc<br />
uncomment the stuff below <br />
# enable bash completion in interactive shells <br />
<br />
* set the host name<br />
echo "domain.allstarlink.org" >/etc/hostname<br />
<br />
* set the default editor<br />
update-alternatives --config editor <br />
Then select #3 vim.basic<br />
<br />
* setup a firewall as /etc/network/firewall.sh and chmod +x it. You'll need to edit this based on the machine. Note the stuff in tampa uses a firewall on the HV too.<br />
#!/bin/bash<br />
<br />
INET_IF=eth0<br />
<br />
#Flush and zero all tables<br />
modprobe ip_tables<br />
modprobe ipt_limit<br />
modprobe iptable_mangle<br />
modprobe ipt_state<br />
modprobe ipt_LOG<br />
modprobe iptable_filter<br />
<br />
iptables -F INPUT<br />
iptables -F FORWARD<br />
iptables -t nat -F POSTROUTING<br />
iptables -t nat -F PREROUTING<br />
<br />
#init the log-and-drop chain<br />
iptables -F log-and-drop<br />
iptables -X log-and-drop<br />
iptables -N log-and-drop<br />
#init log-and-reject<br />
iptables -F log-and-reject<br />
iptables -X log-and-reject<br />
iptables -N log-and-reject<br />
<br />
echo "all tables flushed and dropped"<br />
# Specific chain used for logging packets before blocking them<br />
iptables -A log-and-drop -j LOG --log-prefix "[IPTables] Drop "<br />
iptables -A log-and-drop -j DROP<br />
<br />
# Specific chain used for logging packets before blocking them<br />
iptables -A log-and-reject -j LOG --log-prefix "[IPTables] Reject "<br />
iptables -A log-and-reject -j REJECT<br />
echo "logging chains setup"<br />
<br />
# The packets having the TCP flags activated are dropped<br />
# and so for the ones with no flag at all (often used with Nmap scans)<br />
iptables -A FORWARD -p tcp --tcp-flags ALL ALL -j log-and-drop<br />
iptables -A FORWARD -p tcp --tcp-flags ALL NONE -j log-and-drop<br />
<br />
#Global blocks<br />
#iptables -t filter -A INPUT -j DROP -s 119.118.232.185/24<br />
<br />
# allow IPSEC from other boxes<br />
IPSECsrc='199.47.174.150,44.98.254.151,44.103.0.48,44.103.0.49,44.98.254.145,44.72.21.13,44.72.21.12'<br />
#Technically the next two are not needed as we have the policy<br />
iptables -A INPUT -i $INET_IF -p 50 -j ACCEPT --src "$IPSECsrc"<br />
iptables -A INPUT -i $INET_IF -p 51 -j ACCEPT --src "$IPSECsrc"<br />
iptables -A INPUT -i $INET_IF -p udp --dport 500 -j ACCEPT --src "$IPSECsrc"<br />
# this is needed to allow all ipsec packets when it's host to host<br />
iptables -A INPUT -m policy --dir in --pol ipsec -j ACCEPT --src "$IPSECsrc" <br />
<br />
# allow all ssh in<br />
iptables -t filter -A INPUT -j ACCEPT --protocol tcp --dport 22<br />
<br />
#allow http and https<br />
#iptables -t filter -A INPUT -j ACCEPT --protocol tcp --dport 80<br />
#iptables -t filter -A INPUT -j ACCEPT --protocol tcp --dport 443<br />
# allow asterisk 4569<br />
#iptables -t filter -A INPUT -j ACCEPT --protocol udp --dport 4569<br />
# allow DNS<br />
#iptables -t filter -A INPUT -j ACCEPT --protocol tcp --dport 53<br />
#iptables -t filter -A INPUT -j ACCEPT --protocol udp --dport 53<br />
<br />
echo "end of services"<br />
# allow ping at 2 per sec<br />
iptables -t filter -A INPUT -j ACCEPT --in-interface $INET_IF --protocol icmp --icmp-type echo-request --match limit --limit 4/s --limit-burst 3<br />
iptables -t filter -A INPUT -j log-and-drop --in-interface $INET_IF --protocol icmp --icmp-type echo-request<br />
# allow responces to local initated connections<br />
#iptables -A INPUT -i $INET_IF --match state --state NEW,INVALID -j log-and-drop<br />
#iptables -A FORWARD -i $INET_IF --match state --state NEW,INVALID -j log-and-drop<br />
iptables -t filter -A INPUT -j ACCEPT --match state --state RELATED,ESTABLISHED<br />
# Set rp_filter to 2<br />
for i in `find /proc/sys/net/ipv*/conf -name rp_filter`<br />
do<br />
echo "2" >$i<br />
done<br />
# setup a default deny rule for outside traffic<br />
iptables -t filter -A INPUT --in-interface $INET_IF -j log-and-drop<br />
<br />
* setup fail2ban for ssh and have it null route offenders. edit ignoreip as needed<br />
vi /etc/fail2ban/jail.conf<br />
ignoreip = 127.0.0.1/8 199.47.172.0/22 44.98.254.0/24 44.72.21.0/24 44.103.0.0/24<br />
bantime = 3600<br />
# A host is banned if it has generated "maxretry" during the last "findtime"<br />
# seconds.<br />
findtime = 3600<br />
# "maxretry" is the number of failures before a host get banned.<br />
maxretry = 2<br />
banaction = route<br />
<br />
* Set the TimeZone to UTC<br />
sudo timedatectl set-timezone UTC<br />
* Set the server up in forward and reverse DNS<br />
** for reverse have the provider do a CNAME in their reverse file pointing to $DOMAIN.PTR.allstarlink.org. In the allstarlink.org DNS zone add an entry <br />
example:<br />
stats IN PTR stats.allstarlink.org.<br />
This will do a lookup on 130.254.98.44.in-addr.arpa. and return a CNAME pointing to stats.PTR.allstarlink.org, which has a PTR record pointing to stats.allstarlink.org.<br />
<br />
=== Configure IPSEC ===<br />
AllStarLink servers use strong crypto using host to host IPSEC between them for protection of services. This is configured only between servers that need it, as we don't have dynamic tunneling enabled, and each server needs a config for each tunnel. This can quickly add up to lots of configrations.<br />
<br />
This example will show two servers, 1 and 2 with IP 44.1.1.1 and 44.2.2.2 respectively. <br />
<br />
==== Server 1 ====<br />
We need to provision the ipsec tools to know about the connections and configure a pre shared key (PSK). <br />
Note the left server is always the local server.<br />
<br />
/etc/ipsec.conf<br />
conn one-to-two<br />
authby=secret<br />
#auto=start enabled the tunnel to come up even if there is not traffic for it. <br />
auto=start<br />
keyexchange=ike<br />
left=4.1.1.1<br />
right=4.2.2.2<br />
leftikeport=500<br />
rightikeport=500 <br />
type=transport<br />
esp=aes128gcm16!<br />
dpddelay=5<br />
dpdtimeout=20<br />
dpdaction=restart<br />
<br />
vim /etc/ipsec.secrets<br />
44.1.1.1 44.2.2.2 : PSK "This is the AllStarLink PSK"<br />
Then do an 'ipsec restart' on the server.<br />
<br />
==== Server 2 ====<br />
<br />
/etc/ipsec.conf<br />
conn two-to-one<br />
authby=secret<br />
#auto=start enabled the tunnel to come up even if there is not traffic for it. <br />
auto=start<br />
keyexchange=ike<br />
left=4.2.2.2<br />
right=4.1.1.1<br />
leftikeport=500<br />
rightikeport=500 <br />
type=transport<br />
esp=aes128gcm16!<br />
dpddelay=5<br />
dpdtimeout=20<br />
dpdaction=restart<br />
<br />
vim /etc/ipsec.secrets<br />
44.2.2.2 44.1.1.1 : PSK "This is the AllStarLink PSK"<br />
Then do an 'ipsec restart' on the server.<br />
<br />
==== Verify IPsec ====<br />
<br />
The 'ipsec' command is used to verify the tunnel is up between the servers<br />
<br />
root@server# ipsec status<br />
two-to-one[839]: ESTABLISHED 98 minutes ago, 44.1.1.1[44.1.1.1]...44.2.2.2[44.2.2.2]<br />
two-to-one{13209}: INSTALLED, TRANSPORT, reqid 695, ESP SPIs: c824e4db_i c1e4bf5c_o<br />
two-to-one{13209}: 44.1.1.1/32 === 44.2.2.2/32<br />
If they are not up, check /var/log/syslog and restart ipsec on both servers. Some times a server can get in a bad status if there is a mis-config. Also it's worth noting that IPSEC is processed by iptables once it's decrypted, the <code>iptables -A INPUT -m policy --dir in --pol ipsec -j ACCEPT --src "$IPSECsrc" </code> line in the firewall allows all IPsec packets once decrypted to bypass the firewall. This is able to prevent traffic between unencrypted services on the servers (e.g. mysql will not connect if the ipsec is down).<br />
<br />
=== Configure Postfix ===<br />
<br />
Postfix is installed to forward mail for root to a smtp host.<br />
<br />
<code>apt-get install postfix mailutils</code><br />
<br />
This will run an installer with a curses interface and you must select '''Satallite System'''. Check the '''System mail''' name is the hostname of the server, and the '''SMTP relay host''' is ''morty.keekles.org''. '''Root and postmaster mail''' should be ''rootmail@allstarlink.org''.<br />
<br />
Should you need to reconfigure this use:<br />
<br />
<code> dpkg-reconfigure postfix </code><br />
<br />
other aliases are setup in /etc/aliases. You must run ''newaliases'' after this is updated for them to take effect.<br />
<br />
= Verification =<br />
<br />
It's important to verify the server provisiong before being put into production. <br />
<br />
== Items to check ==<br />
* reboot the server/vm, do all services start properly?<br />
* Is the IP address configured on the server on eth0?<br />
* Is the hostname set?<br />
* Is it configured in DNS both forward and reverse?<br />
* Is the firewall active (try netcat on a non-permitted port)<br />
* IPSEC is active <code>ipsec status</code>?<br />
* Does Screen work in an xterm with scroll back?<br />
* Is the time set via ntp <code>ntptime</code> and is the timezone set to UTC?<br />
* Is fail2ban working? Make a couple test connections and see if the IP is null routed <code>ip route show</code><br />
<br />
You may need to check your other services on this server now.<br />
<br />
= Network Monitoring = <br />
It's time to hand off the server to the NMS team. Please ensure SNMP is configured and an IPSEC tunnel is built to nms.allstarlink.org<br />
Logging will be sucked up by graylog.<br />
<br />
Please ensure it's being watched in librenms by asking on the admin list or in the slack.<br />
<br />
[[Category: Infrastructure]]</div>N8THNhttps://wiki.pttlink.org/index.php?title=Allmon2&diff=1467Allmon22019-10-20T03:05:51Z<p>N8THN: Overview added</p>
<hr />
<div>https://github.com/tsawyer/allmon2<br />
<br />
APT-GET Package pending for ASL1.10<br />
<br />
Allmon is a web site for managing one or more app_rpt (aka Allstar) nodes.<br />
Each managed local node shows a list of connected nodes. The list is<br />
sorted in reverse order of the most recently received node. So the last<br />
node to talk is always at the top of the list. Any node that is currently<br />
being received will be highlighted by a green background as well as moving<br />
to the top of the list. The node list is updated once a second giving near-<br />
real-time status.<br />
<br />
Nodes may be grouped together when configuring Allmon. Groups enable two<br />
or mode nodes to be displayed on the same page. This can be handy if you<br />
use devices with smaller screens or you want to see a couple of your nodes<br />
at the same time. Don't try to display more than a few per group as performance<br />
will suffer.<br />
<br />
Logged in users can perform connect and disconnects. Users are maintained<br />
with the Apache htpasswd utility. There is only one login level, admin.<br />
<br />
Allmon will also monitor VOTER clients. Each VOTER instance displays a list<br />
attached Radio Thin Client Modules (RTCM). The RSSI for each RTCM is displayed<br />
in bar graph style along with a color to indicate the currently voted RTCM.</div>N8THNhttps://wiki.pttlink.org/index.php?title=Due_Credit&diff=1394Due Credit2019-03-30T13:32:44Z<p>N8THN: drupal transfer to wiki documentation</p>
<hr />
<div>This site is mostly a cut and paste from the original ohnosec.org Drupal site. That site and the majority of its articles were developed by Steve Rogers WA6ZFT. Of course Jim Dixon WB6NIL and others have contributed to the original site over time.<br />
<br />
While the authorship of all the articles on this new Drupal site is mine (at this time) it should be noted that almost none of it actually is. The authorship got lost during the cut and paste operations. I apologize for this unfortunate side effect.<br />
[[File:ASL docs drupal to wiki.pdf|left|thumb|List of formal Drupal pages and corresponding wiki pages]]</div>N8THNhttps://wiki.pttlink.org/index.php?title=File:ASL_docs_drupal_to_wiki.pdf&diff=1393File:ASL docs drupal to wiki.pdf2019-03-30T13:30:49Z<p>N8THN: </p>
<hr />
<div>Spreadsheet printout documenting transfer of former Drupal site to WiKi.allstarlink.org</div>N8THNhttps://wiki.pttlink.org/index.php?title=Main_Page&diff=1348Main Page2019-01-29T01:52:07Z<p>N8THN: </p>
<hr />
<div>Welcome to the AllStarLink WiKi. AllStarLink is a world wide network of [https://en.wikipedia.org/wiki/Amateur_radio Amateur Radio] repeaters, remote base stations and hot spots accessible to each other via the Internet and/or private IP networks. AllStarLink runs on a dedicated Linux computer (including the Raspberry Pi) that you host at your home, radio site or computer center. It is based on the open source Asterisk PBX. The app_rpt module it makes a powerful radio/repeater controller. AllStarLink is open source GPL software free for anyone to use.<br />
<br />
Recently we've moved some things off of this front page. If you don't see what you are looking for look at the [[:Category:How to|How To's]] or use search located on the top of every page. We have completed moving the content from the docs site [http://docs.allstarlink.org docs.allstarlink.org]. <br />
<br />
__NOTOC__<br />
==Organization==<br />
*[[The Organization - AllStarLink Inc. ]] - Who is AllStarLink?<br />
*[[The Beginning - AllStarLink Inc]] - How AllStarLink came to be. <br />
<br />
==AllStarLink Menu==<br />
*[[Features]] - List of the many AllStarLink Features <br />
*[[Beginners Guide]] - Step by step instructions to create your account and AllStarLink node. <br />
*[[ASL FAQ]] - Questions and answers about the AllStarLink software distribution.<br />
*[[:Category:How to|How To's]] - A collection of AllStarLink how to's.<br />
*[[:Category:Node Configuration|Node Configuration]] - Detailed configuration settings.<br />
*[[:Category:Development|Development]] - Information regarding development of the AllStarLink software (i.e., contributing, etc).<br />
*[[Radio Connections]] - Instructions to Connect Radios, Repeaters and Other Devices to AllStar.<br />
*[[Troubleshooting]] - Troubleshooting common problems, things to try, and hints to solve the problem.<br />
<br />
==Downloads==<br />
* [https://github.com/AllStarLink/Asterisk/releases/tag/ASL-1.01 ASL AMD] Latest AllStarLink installer for x86/AMD (main site)<br />
* [http://dvswitch.org/files/ASL_Images/Intel-AMD/Stretch/ ASL AMD] Latest AllStarLink installer for x86/AMD (alternative site)<br />
* [http://dvswitch.org/files/ASL_Images/Raspberry_Pi/Stretch/ Pi] Latest AllStarLink image for the Raspberry Pi<br />
* [http://dvswitch.org/files/ASL_Images/ ASL Repo] AllStarLink Image Repository<br />
* [[ASL FAQ]] - Install ASL on your existing Debian box or VM<br />
<br />
Note: The ASL 1.01 installer is a Network installer and still uses the dvswitch.org site to download the .deb install files.<br />
<br />
==Related Links==<br />
* [https://allstarlink.org/ AllStarLink Portal] - If you are looking to set up your own AllStarLink node.<br />
* [https://web-tpa.allstarlink.org/ AllStarLink Portal - Beta] - Our beta portal site. Check out the searchable and sortable [https://web-tpa.allstarlink.org/nodelist/ Node List].<br />
* [http://stats.allstarlink.org/ AllStarLink Stats] - shows all the existing public nodes.<br />
* [http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users AllStarLink users mailing list]- This is the app_rpt mailing list for discussion, help and helping others.<br />
* [https://github.com/AllStarLink/ Source Code] - All of the source code for the AllStarLink Asterisk and app_rpt is available on GitHub.<br />
<br />
==History==<br />
* [[History]] from the Duuude, Jim Dixon WB6NIL SK 12/16/2016.<br />
* [[Thru-hole_Voter_Board|Thru-hole Voter Board]] from Jim Dixon</div>N8THNhttps://wiki.pttlink.org/index.php?title=Radio_Connections&diff=1347Radio Connections2019-01-28T16:54:16Z<p>N8THN: </p>
<hr />
<div>Instructions for connecting radios, repeaters and AllStarLink interfaces including the RTCM, GPS, URI/URI X and like devices. <br />
<br />
<br />
=GPS=<br />
* [[Media:RTCM 2 Trimble.pdf|Trimble RTCM Interface Cable]]<br />
* [[Media:RTCM 321 Cable.graffle.pdf|Trimble to Two RTCMs and Lady Heather Cable]]<br />
* [[Media:RTCM to BG7TBL Cable.pdf|BG7TBL GPS / RTCM Cable]]<br />
<br />
=Motorola=<br />
<br />
==CDM==<br />
CDMs make great nodes. This eBay reseller has very nice cables. Use to connect to URI or RTCM. <br />
<br />
[[Media:CDM Cable.pdf|CDM Cable from Kurt Meltzer]] ex-WB9KNX, now KC4NX - Cable 83 has only one output to use for either COS or CTCSS. Use another cable if you need both COS and CTCSS.<br />
<br />
==Maxtrac==<br />
The venerable Maxtrac is a radio that was very well built, apparently has very stable reference LO, and can take a beating. When aligned properly, and sufficient *vectored* cooling is made, this radio will last for a very long, time even under several hours with of transmitting per day.<br />
<br />
The radio will need to be aligned, and programmed to the frequenc(y/ies) you want to use. You will also need to program the Accessory Option for PL/DPL & CSQ Output.<br />
* Most URIs can accept active high or active low for valid RX signal detection, ie, open squelch. It is HIGHLY recommend in any situation COS is set to USB or active high. This will prevent issues. Too many to mention.<br />
* It is a good idea to program pin 8 on the Maxtrac/GM300 for PL/DPL & CSQ output, active high. This will cause the radio to emit a 5Vdc signal when the squelch is open, and go low when squelch is closed.<br />
<br />
===TX/RX audio, COS, and PTT connections===<br />
With the radio facing you in normal operating positing, volume knob on top left, and mic connection right below it, turn the radio over from the right side. The accessory connector is located on the rear, right top of the radio at this point. Starting from left to right, the pins on the top are / and the pins on the bottom are /. If you want to hear audio from the radios speaker, just a header jumper on the far right pins 15 and 16.<br />
<br />
<br />
This section is a work in progress. <br />
<br />
References:<br />
The GM300 section has the link for further reading; the Maxtrac and GM300, are relatively close in design.<br />
<br />
==MTR-2000==<br />
<br />
==Quantar==<br />
<br />
The Quantar can be tricky to interface as it's extremely programmable and you will need a wireline card for I/O connections. By default the I/O will not work unless the "wildcard" table is programed. This wildcard table is Boolean logic of interrupt states in the radio, is extremely flexible and frustrating to debug. It's a base station in it's own class.<br />
<br />
[[File:Front of quantar and controller.jpg|thumb|400px|right|Front of Quantar and controller]]<br />
<br />
* [[Media:QUANTAR-RTCM INTERFACE CABLE.pdf|Quantar/RTCM Interface Cable]]<br />
<br />
Note you will want to use [[RTCM_Client#DSP.2FBEW_Firmware_Version|BEW mode]] on the RTCM if using the RTCM do squelch.<br />
<br />
* [[Media:RTCM 2 Quantar.pdf|Another Quantar/RTCM Interface Cable]]<br />
* [[Media:RTCM to Astro-TAC Cable.pdf|Astro-TAC/RTCM Interface Cable]]<br />
* [http://wiki.w9cr.net/index.php/Allstar_and_P25_on_Quantar Interfacing to a Quantar with P25NX] - Bryan Fields W9CR has page on interfacing the Qunatar using simple USB into Allstar and P25NX linking at the same time. This is driven by programing on the Quantar Wildcard tables.<br />
*[[Media:Quantar URI Interface.jpg|Quantar/URI Cable]]<br />
*[[Media:QuantarMRTI2URI.jpg|Quantar MRTI/URI Cable]]<br />
<br />
==Syntor X==<br />
The Motorola Syntor X with an Xcat installed makes a great frequency agile remote base. For more information see this [http://wd6awp.net/xcat/ Syntor Xcat] page. <br />
<br />
==VRM-850==<br />
<br />
==GM300==<br />
These older radios are fairly common and easily to come by due to the narrow banding. Probably the hardest part is finding a computer and the RSS to program them. The Gm300 family has many different configurations, from low band VHF, to 800 Mhz. But the easiest variant of the GM300 is ones with the 16 pin connector.<br />
[http://www.repeater-builder.com/motorola/maxtrac/maxtrac-index.html All about GM300 Radios] <br />
<br />
Connections are fairly simple but can be hard to determine which is the correct one to use. This [http://www.repeater-builder.com/motorola/maxtrac/maxtrac-option-plug.html link] is a good place to start.<br />
<br />
=Kenwood=<br />
==TKR720/820==<br />
Connections to: PTT, COS, RX audio out and MIC audio in<br />
<br />
TX/RX board, MIC audio input, pins 4 & 5: floating ground, must not tie to any other ground! Some installations may require a 10dB, resistor L-network consisting of a 4.7k and 470 ohm resistors. The 470 ohm resistor connection across pins four and five, the 4.7k resistor is soldered to pin 5 to which your TX audio from the URI will connect to.<br />
<br />
The MIC audio gain, deviation, and balance adjustments are *very* sensitive! <br />
<br />
- RA-35 without TX adj. trimmer pots: Using a service monitor with deviation metering, start low and work your way up to 3KHz deviation with 1KHz tone, generated by simpleusb-tune-menu. If enabled, *904 turns this tone on and off by command, ie, no tone time-out as in simpleusb-tune-menu.<br />
<br />
== TKR750/850 ==<br />
[http://www.masterscommunications.com/products/radio-adapter/txt/tkr.txt Using the Masters Communications RA-35 or RA-40 radio adapters with the TKR750/850]<br />
<br />
=Repeater Controller=<br />
<br />
[[Media:RTCMwithController.pdf|An example of using RTCMs to replace 420 links]]<br />
<br />
=Spectra Engineering=<br />
* [http://wiki.w9cr.net/index.php/MX800#W9CR_alignment_procedure_and_setup_with_Allstar MX800 Base station] - Bryan Fields, W9CR has a complete setup guide for the MX800 Base station which includes fallback to the built in controller and an audio delay module.<br />
<br />
=Tait=<br />
<br />
=Beagle Board=<br />
The Beagle Board XM project.<br />
* [http://beagleboard.org/BeagleBoard-xM BeagleBoard-xM]<br />
<br />
=Lox board=<br />
The Level One eXpansion board.<br />
* [http://www.dmkeng.com/LOX_Order_Page.htm LOX Board] <br />
<br />
=URI / URI X=<br />
The URI is manufactured and sold by [http://dmkeng.com/URI_Order_Page.htm DMK Engineering]. <br />
*[[Media:URI Schematic.pdf|URI Schematic]]<br />
*[[Media:URIx Schematic.pdf|URI X Schematic]]<br />
<br />
=RA-40 / RA-35=<br />
The RA-40 is the latest version and is sold by W3KKC. The RA-40 includes audio output level control potentiometers and much more.<br />
*[http://www.masterscommunications.com/products/radio-adapter/ra40.html RA-40]<br />
*[http://www.masterscommunications.com/products/radio-adapter/ra35.html RA-35]<br />
<br />
=Vertex=<br />
* [[Media:RTCM 2 VRX-5000.pdf|VRX-5000 / RTCM Interface Cable]]<br />
<br />
=Quad Radio PCI card=<br />
*[[:File:Ft897 quadpci schematic.pdf|Yaesu FT-897 HF Radio(pdf)]]<br />
<br />
*[[:File:Ic706 quadpci schematic.pdf|Icom IC-706 HF Radio(pdf)]]<br />
<br />
*[[:File:Tmg707 quadpci schematic.pdf|Kenwood TMG-707 Dual Band FM mobile Radio(pdf)]]<br />
<br />
=Modified USB FOB=<br />
*[[:File:Usb2tmg707.pdf|Kenwood TMG-707 Dual Band FM mobile Radio(pdf)]]<br />
[[Category:How to]]</div>N8THNhttps://wiki.pttlink.org/index.php?title=Radio_Connections&diff=1346Radio Connections2019-01-28T16:51:59Z<p>N8THN: </p>
<hr />
<div>Instructions for connecting radios, repeaters and AllStarLink interfaces including the RTCM, GPS, URI/URI X and like devices. <br />
<br />
<br />
=GPS=<br />
* [[Media:RTCM 2 Trimble.pdf|Trimble RTCM Interface Cable]]<br />
* [[Media:RTCM 321 Cable.graffle.pdf|Trimble to Two RTCMs and Lady Heather Cable]]<br />
* [[Media:RTCM to BG7TBL Cable.pdf|BG7TBL GPS / RTCM Cable]]<br />
<br />
=Motorola=<br />
<br />
==CDM==<br />
CDMs make great nodes. This eBay reseller has very nice cables. Use to connect to URI or RTCM. <br />
<br />
[[Media:CDM Cable.pdf|CDM Cable from Kurt Meltzer]] ex-WB9KNX, now KC4NX - Cable 83 has only one output to use for either COS or CTCSS. Use another cable if you need both COS and CTCSS.<br />
<br />
==Maxtrac==<br />
The venerable Maxtrac is a radio that was very well built, apparently has very stable reference LO, and can take a beating. When aligned properly, and sufficient *vectored* cooling is made, this radio will last for a very long, time even under several hours with of transmitting per day.<br />
<br />
The radio will need to be aligned, and programmed to the frequenc(y/ies) you want to use. You will also need to program the Accessory Option for PL/DPL & CSQ Output.<br />
* Most URIs can accept active high or active low for valid RX signal detection, ie, open squelch. It is HIGHLY recommend in any situation COS is set to USB or active high. This will prevent issues. Too many to mention.<br />
* It is a good idea to program pin 8 on the Maxtrac/GM300 for PL/DPL & CSQ output, active high. This will cause the radio to emit a 5Vdc signal when the squelch is open, and go low when squelch is closed.<br />
<br />
===TX/RX audio, COS, and PTT connections===<br />
With the radio facing you in normal operating positing, volume knob on top left, and mic connection right below it, turn the radio over from the right side. The accessory connector is located on the rear, right top of the radio at this point. Starting from left to right, the pins on the top are / and the pins on the bottom are /. If you want to hear audio from the radios speaker, just a header jumper on the far right pins 15 and 16.<br />
<br />
<br />
This section is a work in progress. <br />
<br />
References:<br />
The GM300 section has the link for further reading; the Maxtrac and GM300, are relatively close in design.<br />
<br />
==MTR-2000==<br />
<br />
==Quantar==<br />
<br />
The Quantar can be tricky to interface as it's extremely programmable and you will need a wireline card for I/O connections. By default the I/O will not work unless the "wildcard" table is programed. This wildcard table is Boolean logic of interrupt states in the radio, is extremely flexible and frustrating to debug. It's a base station in it's own class.<br />
<br />
[[File:Front of quantar and controller.jpg|thumb|400px|right|Front of Quantar and controller]]<br />
<br />
* [[Media:QUANTAR-RTCM INTERFACE CABLE.pdf|Quantar/RTCM Interface Cable]]<br />
<br />
Note you will want to use [[RTCM_Client#DSP.2FBEW_Firmware_Version|BEW mode]] on the RTCM if using the RTCM do squelch.<br />
<br />
* [[Media:RTCM 2 Quantar.pdf|Another Quantar/RTCM Interface Cable]]<br />
* [[Media:RTCM to Astro-TAC Cable.pdf|Astro-TAC/RTCM Interface Cable]]<br />
* [http://wiki.w9cr.net/index.php/Allstar_and_P25_on_Quantar Interfacing to a Quantar with P25NX] - Bryan Fields W9CR has page on interfacing the Qunatar using simple USB into Allstar and P25NX linking at the same time. This is driven by programing on the Quantar Wildcard tables.<br />
*[[Media:Quantar URI Interface.jpg|Quantar/URI Cable]]<br />
*[[Media:QuantarMRTI2URI.jpg|Quantar MRTI/URI Cable]]<br />
<br />
==Syntor X==<br />
The Motorola Syntor X with an Xcat installed makes a great frequency agile remote base. For more information see this [http://wd6awp.net/xcat/ Syntor Xcat] page. <br />
<br />
==VRM-850==<br />
<br />
==GM300==<br />
These older radios are fairly common and easily to come by due to the narrow banding. Probably the hardest part is finding a computer and the RSS to program them. The Gm300 family has many different configurations, from low band VHF, to 800 Mhz. But the easiest variant of the GM300 is ones with the 16 pin connector.<br />
[http://www.repeater-builder.com/motorola/maxtrac/maxtrac-index.html All about GM300 Radios] <br />
<br />
Connections are fairly simple but can be hard to determine which is the correct one to use. This [http://www.repeater-builder.com/motorola/maxtrac/maxtrac-option-plug.html link] is a good place to start.<br />
<br />
=Kenwood=<br />
==TKR720/820==<br />
Connections to: PTT, COS, RX audio out and MIC audio in<br />
<br />
TX/RX board, MIC audio input, pins 4 & 5: floating ground, must not tie to any other ground! Some installations may require a 10dB, resistor L-network consisting of a 4.7k and 470 ohm resistors. The 470 ohm resistor connection across pins four and five, the 4.7k resistor is soldered to pin 5 to which your TX audio from the URI will connect to.<br />
<br />
The MIC audio gain, deviation, and balance adjustments are *very* sensitive! <br />
<br />
- RA-35 without TX adj. trimmer pots: Using a service monitor with deviation metering, start low and work your way up to 3KHz deviation with 1KHz tone, generated by simpleusb-tune-menu. If enabled, *904 turns this tone on and off by command, ie, no tone time-out as in simpleusb-tune-menu.<br />
<br />
== TKR750/850 ==<br />
[http://www.masterscommunications.com/products/radio-adapter/txt/tkr.txt Using the Masters Communications RA-35 or RA-40 radio adapters with the TKR750/850]<br />
<br />
=Repeater Controller=<br />
<br />
[[Media:RTCMwithController.pdf|An example of using RTCMs to replace 420 links]]<br />
<br />
=Spectra Engineering=<br />
* [http://wiki.w9cr.net/index.php/MX800#W9CR_alignment_procedure_and_setup_with_Allstar MX800 Base station] - Bryan Fields, W9CR has a complete setup guide for the MX800 Base station which includes fallback to the built in controller and an audio delay module.<br />
<br />
=Tait=<br />
<br />
=Beagle Board=<br />
The Beagle Board XM project.<br />
* [http://beagleboard.org/BeagleBoard-xM BeagleBoard-xM]<br />
<br />
=Lox board=<br />
The Level One eXpansion board.<br />
* [http://www.dmkeng.com/LOX_Order_Page.htm LOX Board] <br />
<br />
=URI / URI X=<br />
The URI is manufactured and sold by [http://dmkeng.com/URI_Order_Page.htm DMK Engineering]. <br />
*[[Media:URI Schematic.pdf|URI Schematic]]<br />
*[[Media:URIx Schematic.pdf|URI X Schematic]]<br />
<br />
=RA-40 / RA-35=<br />
The RA-40 is the latest version and is sold by W3KKC. The RA-40 includes audio output level control potentiometers and much more.<br />
*[http://www.masterscommunications.com/products/radio-adapter/ra40.html RA-40]<br />
*[http://www.masterscommunications.com/products/radio-adapter/ra35.html RA-35]<br />
<br />
=Vertex=<br />
* [[Media:RTCM 2 VRX-5000.pdf|VRX-5000 / RTCM Interface Cable]]<br />
<br />
== Quad Radio PCI card ==<br />
[[:File:Ft897 quadpci schematic.pdf|Yaesu FT-897 HF Radio(pdf)]]<br />
<br />
[[:File:Ic706 quadpci schematic.pdf|Icom IC-706 HF Radio(pdf)]]<br />
<br />
[[:File:Tmg707 quadpci schematic.pdf|Kenwood TMG-707 Dual Band FM mobile Radio(pdf)]]<br />
<br />
== Modified USB FOB ==<br />
[[:File:Usb2tmg707.pdf|Kenwood TMG-707 Dual Band FM mobile Radio(pdf)]]<br />
[[Category:How to]]</div>N8THNhttps://wiki.pttlink.org/index.php?title=File:Usb2tmg707.pdf&diff=1345File:Usb2tmg707.pdf2019-01-28T16:51:25Z<p>N8THN: </p>
<hr />
<div>USB FOB to TMG-707 schematic</div>N8THNhttps://wiki.pttlink.org/index.php?title=File:Tmg707_quadpci_schematic.pdf&diff=1344File:Tmg707 quadpci schematic.pdf2019-01-28T16:48:35Z<p>N8THN: </p>
<hr />
<div>TMG-707 Quad Radio PCI card schematic</div>N8THNhttps://wiki.pttlink.org/index.php?title=File:Ic706_quadpci_schematic.pdf&diff=1343File:Ic706 quadpci schematic.pdf2019-01-28T16:46:37Z<p>N8THN: </p>
<hr />
<div>IC706 Quad Radio PCI card schematic</div>N8THNhttps://wiki.pttlink.org/index.php?title=File:Ft897_quadpci_schematic.pdf&diff=1342File:Ft897 quadpci schematic.pdf2019-01-28T16:44:48Z<p>N8THN: </p>
<hr />
<div>FT897 to Quad Radio PCI card schematic</div>N8THNhttps://wiki.pttlink.org/index.php?title=RTCM_Firmware_upgrading&diff=1341RTCM Firmware upgrading2019-01-28T16:20:56Z<p>N8THN: edited hyperlinks</p>
<hr />
<div>[[Category:How to]]<br />
<br />
The RTCM tries to update it's firmware every time it boots as part of the bootloader process. The bootloader has it's own IP address which is set by menu 14 of the IP parameters menu. The default bootloader IP address is 192.168.1.11. If that address fits in your network you can leave it there for all the RTCMs on your LAN as it is active only during the bootloader process.<br />
<br />
If you are updating an RTCM which is behind a firewall you will need to port forward 16388 UDP to the bootloader IP address. If you leave all your bootloaders on the same IP address then you won't have to change the forwarding to update different RTCMs.<br />
<br />
The RTCM firmware is updated with a Windows program EBLEX C3 Programmer. Download from '''[https://github.com/AllStarLink/voter here]'''. Put both the exe and the ini file in a folder.<br />
<br />
Download the firmware '''[https://github.com/AllStarLink/voter here]'''. You probably want Voter-SMT.cry unless you built a thru-hole board or you need the dspbew version. Save the cry file in the folder with the exe and ini files.<br />
<br />
Run the EBLEX Programmer:<br />
* Fill in the target IP address with the public IP if your RTCM is behind a firewall otherwise fill in the target IP address with the bootloader IP address.<br />
* Load the cry file.<br />
* Click the Capture Target button.<br />
* Reboot the RTCM with telnet, power cycle or the reset button. In a moment you should see text come up on the programmer.<br />
* Click the Program button.<br />
* In a few minutes you will see some more messages including a program complete message.<br />
* Click the Reset LIA button. The RTCM will restart with the new firmware.<br />
Telnet into your RTCM and verify the new version is loaded with menu 98.</div>N8THNhttps://wiki.pttlink.org/index.php?title=RTCM_Firmware_upgrading&diff=1340RTCM Firmware upgrading2019-01-28T15:45:42Z<p>N8THN: </p>
<hr />
<div>[[Category:How to]]<br />
'''Download links need updated...'''<br />
<br />
The RTCM tries to update it's firmware every time it boots as part of the bootloader process. The bootloader has it's own IP address which is set by menu 14 of the IP parameters menu. The default bootloader IP address is 192.168.1.11. If that address fits in your network you can leave it there for all the RTCMs on your LAN as it is active only during the bootloader process.<br />
<br />
If you are updating an RTCM which is behind a firewall you will need to port forward 16388 UDP to the bootloader IP address. If you leave all your bootloaders on the same IP address then you won't have to change the forwarding to update different RTCMs.<br />
<br />
The RTCM firmware is updated with a Windows program EBLEX C3 Programmer. Download from '''here'''. Put both the exe and the ini file in a folder.<br />
<br />
Download the firmware '''here'''. You probably want Voter-SMT.cry unless you built a thru-hole board or you need the dspbew version. Save the cry file in the folder with the exe and ini files.<br />
<br />
Run the EBLEX Programmer:<br />
* Fill in the target IP address with the public IP if your RTCM is behind a firewall otherwise fill in the target IP address with the bootloader IP address.<br />
* Load the cry file.<br />
* Click the Capture Target button.<br />
* Reboot the RTCM with telnet, power cycle or the reset button. In a moment you should see text come up on the programmer.<br />
* Click the Program button.<br />
* In a few minutes you will see some more messages including a program complete message.<br />
* Click the Reset LIA button. The RTCM will restart with the new firmware.<br />
Telnet into your RTCM and verify the new version is loaded with menu 98.</div>N8THNhttps://wiki.pttlink.org/index.php?title=RTCM_Firmware_upgrading&diff=1339RTCM Firmware upgrading2019-01-28T15:43:02Z<p>N8THN: created</p>
<hr />
<div>[[Category:How to]]</div>N8THNhttps://wiki.pttlink.org/index.php?title=Transmitting_Tone_Sequences&diff=1338Transmitting Tone Sequences2019-01-28T15:42:08Z<p>N8THN: added the content</p>
<hr />
<div>=== COP function ===<br />
Cop function 48 is associated with transmitting arbitrary tone sequences. These tone sequences can be any combination of single tones, dual tones, and silence periods,<br />
<br />
These tone sequences are only heard on the repeater transmitter and not sent over the network.<br />
<br />
This function is available in app_rpt.c version 0.183 or later.<br />
<br />
=== Tone Sequences ===<br />
Tone sequences are specified as <code>!Tone_A+Tone_B/Duration_in_MS</code>. ToneB is optional and not specified, the + operator must be omitted.<br />
<br />
The exclamation point operator is required when specifying arbitrary tones.<br />
<br />
DTMF tones can be entered in shorthand fashion as as single digits separated by commas.<br />
<br />
=== Examples ===<br />
881=cop,48,1,2,3,4,# ; Send DTMF 1,2,3,4, and #<br />
882=cop,48,!399.8/1000,!339.6/2000 ; Send two tone paging sequence: Motorola codes 144,141<br />
883=cop,48,!1100+1700/100,!0/60,!700+900/60,!0/60,!700+1100/60,!0/60,!700+900/60,!0/60,!1500+1700/60 ; Send MF tone sequence KP121ST<br />
[[Category:How to]]</div>N8THNhttps://wiki.pttlink.org/index.php?title=Transmitting_Tone_Sequences&diff=1337Transmitting Tone Sequences2019-01-28T15:41:43Z<p>N8THN: created page</p>
<hr />
<div>[[Category:How to]]</div>N8THNhttps://wiki.pttlink.org/index.php?title=Setup_Autopatch&diff=1336Setup Autopatch2019-01-28T15:39:45Z<p>N8THN: /* Autopatch Options */</p>
<hr />
<div>[[Category:How to]]<br />
<br />
The autopatch feature in app_rpt allows users on the radio to interconnect with the public switched telephone network.<br />
<br />
=== Regulatory Issues ===<br />
{| class="wikitable"<br />
|Some countries which disallow third-party traffic do not allow autopatching or telephone interconnection on amateur radio frequencies. In addition, if a system is linked between one country which allows autopatching and one which doesn't, just the passing of the traffic itself across the link could be considered a violation of the rules in the prohibiting country. In countries which permit autopatching, users need be made aware of this and should take the node off-link before using the autopatch.<br />
|}<br />
<br />
=== Security Issues ===<br />
{| class="wikitable"<br />
|The examples provided here do not secure the autopatch against toll fraud. A lot can be done to prevent or reduce toll fraud, but the prevention measures vary by where you are located geographically. Most of the prevention measures will be in extensions.conf, as you can write contexts to reject certain number sequences. The asterisk book in the references section should be consulted to see how to do this, Before placing any autopatch in service, please make sure you have secured your system so that toll fraud does not become an issue.<br />
|}<br />
<br />
=== Selecting an ITSP ===<br />
Call termination into the public switched telephone network is a service offered by an Internet Telephone Service Provider (ITSP). This is a highly competitive business, and there are lots of ITSP's offering termination for Asterisk users. In the reference section is a link to a site which lists several ITSP's. Termination is usually provided using the SIP protocol, and IAX is also offered by a few providers.<br />
<br />
When selecting an ITSP, make sure they provide setup instructions with example configurations including usernames, and passwords. Quite a few ITSP's will automatically generate a custom SIP or IAX stanza for insertion into sip.conf, or iax.conf respectively.<br />
<br />
=== Configuration Files ===<br />
Three configuration files will be affected: rpt.conf, extensions.conf and iax.conf or sip.conf. The ITSP should provide a stanza for you to insert in iax.conf or sip.conf. The flow diagram below shows how each of these files are used when an outgoing autopatch call is made:<br />
<br />
In the rpt.conf configuration file, a context in extensions.conf is defined in a node stanza using the context key:<br />
[1234]<br />
.<br />
.<br />
.<br />
context=autopatch ; Aserisk context in which to place the call<br />
accountcode="MYACCT" ; optional ACCOUNTCODE for call on Asterisk<br />
callerid="5592557827" ; optional callerid to send for call<br />
.<br />
.<br />
.<br />
Also in the rpt.conf file, entries are added to the function table so that users can bring up or take down the autopatch:<br />
[functions]<br />
.<br />
.<br />
.<br />
6=autopatchup,noct=1,farenddisconnect=1,dialtime=20000 <br />
0=autopatchdn <br />
.<br />
.<br />
.<br />
In extensions.conf, a stanza for the autopatch context is added which refers to the peer stanza in iax.conf or sip.conf. For outbound IAX connections extensions.conf<br />
[autopatch] <br />
<br />
exten => _1NXXNXXXXXX,1,Dial,IAX2/peername/${EXTEN} <br />
exten => _1NXXNXXXXXX,2,Congestion <br />
For outbound SIP connections it should look like this:<br />
[autopatch] <br />
<br />
exten => _1NXXNXXXXXX,1,Dial,SIP/peername/${EXTEN} <br />
exten => _1NXXNXXXXXX,2,Congestion <br />
The peer stanza you insert in iax.conf or sip.conf should preferably be provided by your ITSP. You'll want to use the stanza they identify for performing outgoing connections. A nonoperational example of an iax2 peer stanza looks like this:<br />
[peername]<br />
type=peer <br />
host=127.0.0.1 <br />
secret=nunya<br />
auth=md5 <br />
disallow=all <br />
allow=gsm <br />
allow=ulaw<br />
<br />
=== Autopatch Options ===<br />
You may have noticed several options being passed in to the autopatchup command class.<br />
<br />
This table summarizes what they do:<br />
{| class="wikitable"<br />
!Autopatch Option<br />
!Description<br />
|-<br />
|context<br />
|Override the context specified for the autopatch in rpt.conf<br />
|-<br />
|dialtime<br />
|The maximum time to wait between DTMF digits when a telephone number is being dialed. The patch will automatically disconnect if this time is exceeded. The value is specified in milliseconds.<br />
|-<br />
|farenddisconnect<br />
|When set to 1, the patch will automatically disconnect when the called party hangs up. The default is send a circuit busy tone until the radio user brings the patch down.<br />
|-<br />
|noct<br />
|When this is set to 1 the courtesy tone during an autopatch call will be disabled. The default is to send the courtesy tone whenever the radio user unkeys.<br />
|-<br />
|quiet<br />
|When set to 1, Don't send dial tone, voice responses, just try to connect the call.<br />
|}<br />
<br />
== Simplex Autopatch ==<br />
For nodes with duplex set to 0 or 1, Simplex Autopatch operation is supported.<br />
<br />
This is accomplished by using a VOX on the audio coming from the telephone call,<br />
<br />
because of the half-duplex nature of the node. To avoid having audio from the<br />
<br />
telephone call keep the transmitter engaged for extended periods of time (if there<br />
<br />
is some source of continuous audio), there are two time-out values. One is the<br />
<br />
Vox timeout, which is the maximum amount of time that the VOX can hold the transmitter<br />
<br />
engaged, which by default is 10 seconds. The other one is the Vox recovery time, which<br />
<br />
is the amount of time that the Vox is disabled during times of continuous audio, after<br />
<br />
the Vox timeout, which is 2 seconds. So, during continuous audio, it transmits for<br />
<br />
10 seconds, then stops for 2 seconds (so that you can transmit to it and perhaps<br />
<br />
disconnect the call), then transmits for another 10 seconds, then stops for 2 seconds,<br />
<br />
and so on.<br />
<br />
Additionally, to prevent 'chop-off' of the first syllable or two of the audio from the<br />
<br />
telephone call, we delay the audio to allow for the transmitter to start transmitting<br />
<br />
and any CTCSS tones to be decoded. This delay is typically 500ms, but can be adjusted<br />
<br />
via the 'simplexpatchdelay' parameter. It is specified in units of 20 milliseconds.<br />
<br />
These time-out values may be overridden by using the following configuration parameters<br />
<br />
located in the [<node-number>] section of rpt.conf:<br />
<br />
[1999]<br />
<br />
.<br />
<br />
.<br />
<br />
.<br />
<br />
voxtimeout = 10000 ; vox timeout time in ms<br />
<br />
voxrecover = 2000 ; vox recover time in ms<br />
<br />
simplexpatchdelay = 25 ; Delay for transmit while in patch in 20ms increments<br />
<br />
.<br />
<br />
.<br />
<br />
.<br />
<br />
If not specified, it uses the default values as specified above.</div>N8THNhttps://wiki.pttlink.org/index.php?title=Setup_Autopatch&diff=1335Setup Autopatch2019-01-28T15:38:13Z<p>N8THN: added the content</p>
<hr />
<div>[[Category:How to]]<br />
<br />
The autopatch feature in app_rpt allows users on the radio to interconnect with the public switched telephone network.<br />
<br />
=== Regulatory Issues ===<br />
{| class="wikitable"<br />
|Some countries which disallow third-party traffic do not allow autopatching or telephone interconnection on amateur radio frequencies. In addition, if a system is linked between one country which allows autopatching and one which doesn't, just the passing of the traffic itself across the link could be considered a violation of the rules in the prohibiting country. In countries which permit autopatching, users need be made aware of this and should take the node off-link before using the autopatch.<br />
|}<br />
<br />
=== Security Issues ===<br />
{| class="wikitable"<br />
|The examples provided here do not secure the autopatch against toll fraud. A lot can be done to prevent or reduce toll fraud, but the prevention measures vary by where you are located geographically. Most of the prevention measures will be in extensions.conf, as you can write contexts to reject certain number sequences. The asterisk book in the references section should be consulted to see how to do this, Before placing any autopatch in service, please make sure you have secured your system so that toll fraud does not become an issue.<br />
|}<br />
<br />
=== Selecting an ITSP ===<br />
Call termination into the public switched telephone network is a service offered by an Internet Telephone Service Provider (ITSP). This is a highly competitive business, and there are lots of ITSP's offering termination for Asterisk users. In the reference section is a link to a site which lists several ITSP's. Termination is usually provided using the SIP protocol, and IAX is also offered by a few providers.<br />
<br />
When selecting an ITSP, make sure they provide setup instructions with example configurations including usernames, and passwords. Quite a few ITSP's will automatically generate a custom SIP or IAX stanza for insertion into sip.conf, or iax.conf respectively.<br />
<br />
=== Configuration Files ===<br />
Three configuration files will be affected: rpt.conf, extensions.conf and iax.conf or sip.conf. The ITSP should provide a stanza for you to insert in iax.conf or sip.conf. The flow diagram below shows how each of these files are used when an outgoing autopatch call is made:<br />
<br />
In the rpt.conf configuration file, a context in extensions.conf is defined in a node stanza using the context key:<br />
[1234]<br />
.<br />
.<br />
.<br />
context=autopatch ; Aserisk context in which to place the call<br />
accountcode="MYACCT" ; optional ACCOUNTCODE for call on Asterisk<br />
callerid="5592557827" ; optional callerid to send for call<br />
.<br />
.<br />
.<br />
Also in the rpt.conf file, entries are added to the function table so that users can bring up or take down the autopatch:<br />
[functions]<br />
.<br />
.<br />
.<br />
6=autopatchup,noct=1,farenddisconnect=1,dialtime=20000 <br />
0=autopatchdn <br />
.<br />
.<br />
.<br />
In extensions.conf, a stanza for the autopatch context is added which refers to the peer stanza in iax.conf or sip.conf. For outbound IAX connections extensions.conf<br />
[autopatch] <br />
<br />
exten => _1NXXNXXXXXX,1,Dial,IAX2/peername/${EXTEN} <br />
exten => _1NXXNXXXXXX,2,Congestion <br />
For outbound SIP connections it should look like this:<br />
[autopatch] <br />
<br />
exten => _1NXXNXXXXXX,1,Dial,SIP/peername/${EXTEN} <br />
exten => _1NXXNXXXXXX,2,Congestion <br />
The peer stanza you insert in iax.conf or sip.conf should preferably be provided by your ITSP. You'll want to use the stanza they identify for performing outgoing connections. A nonoperational example of an iax2 peer stanza looks like this:<br />
[peername]<br />
type=peer <br />
host=127.0.0.1 <br />
secret=nunya<br />
auth=md5 <br />
disallow=all <br />
allow=gsm <br />
allow=ulaw<br />
<br />
=== Autopatch Options ===<br />
You may have noticed several options being passed in to the autopatchup command class.<br />
<br />
This table summarizes what they do:<br />
{| class="wikitable"<br />
!Autopatch Option<br />
!Description<br />
|-<br />
|context<br />
|Override the context specified for the autopatch in rpt.conf<br />
|-<br />
|dialtime<br />
|The maximum time to wait between DTMF digits when a telephone number is being dialed. The patch will automatically disconnect if this time is exceeded. The value is specified in milliseconds.<br />
|-<br />
|farenddisconnect<br />
|When set to 1, the patch will automatically disconnect when the called party hangs up. The default is send a circuit busy tone until the radio user brings the patch down.<br />
|-<br />
|noct<br />
|When this is set to 1 the courtesy tone during an autopatch call will be disabled. The default is to send the courtesy tone whenever the radio user unkeys.<br />
|-<br />
|quiet<br />
|When set to 1, Don't send dial tone, voice responses, just try to connect the call.<br />
|}</div>N8THNhttps://wiki.pttlink.org/index.php?title=Setup_Autopatch&diff=1334Setup Autopatch2019-01-28T15:37:22Z<p>N8THN: created page</p>
<hr />
<div>[[Category:How to]]</div>N8THNhttps://wiki.pttlink.org/index.php?title=Radioless_Nodes&diff=1333Radioless Nodes2019-01-28T15:34:34Z<p>N8THN: added content</p>
<hr />
<div>[[Category:How to]]<br />
IAXRPT is a specialized soft phone program which allows users to connect from their PC's to an Allstar node. Setting up IAXRPT access is similar to seting up dial-in access, but a different command line switch is used in extensions.conf, and user autheorization is done in iax.conf.<br />
<br />
=== Security Issues ===<br />
{| class="wikitable"<br />
|Incoming IAXRPT connections need to be authorized by making sure the incoming IAX user stanza is protected with a secret. This is the case because incoming IAX calls are not checked against a nodes stanza.<br />
|}<br />
<br />
=== Setup ===<br />
First, a user stanza needs to added to iax.conf to allow incoming IAXRPT calls to be routed to a context in extensions.conf. A modified on the following stanza should be placed in iax.conf:<br />
[gui]<br />
type=user <br />
context=radio-gui <br />
auth=md5 <br />
secret=nunya ; *** Important! Change this!!!<br />
host=dynamic <br />
disallow=all<br />
allow=ulaw <br />
allow=gsm <br />
transfer=no<br />
Second, a context stanza is added to extensions.conf to transfer control to the Rpt application:<br />
[radio-gui] <br />
exten = 1234,1,Rpt,1234|X ; Change 1234 to your node number<br />
The X option passed to the Rpt application disables the normal security checks. Because incoming connections are validated in iax.conf, and we don't know where the user will be coming from in advance, the X option is required.</div>N8THNhttps://wiki.pttlink.org/index.php?title=Radioless_Nodes&diff=1332Radioless Nodes2019-01-28T15:33:50Z<p>N8THN: created page</p>
<hr />
<div>[[Category:How to]]</div>N8THNhttps://wiki.pttlink.org/index.php?title=Rpt.conf&diff=1330Rpt.conf2019-01-28T15:26:12Z<p>N8THN: /* Putting it all Together */</p>
<hr />
<div>Rpt.conf is where the majority of user-facing features, such as the node's CW and voice ID, DTMF commands and timers are set. There is a lot of capability here which can be difficult to grasp. Fortunately the default [https://github.com/AllStarLink/DIAL/blob/master/configs/rpt.conf DIAL rpt.conf] is well commented and will work fine for most node admins. <br />
<br />
=DTMF Commands=<br />
DTMF commands are placed in any one of three [[Structure of Config Files|named stanzas]]. Function stanzas control access to DTMF commands that a user can issue from various <br />
control points.<br />
* The [[#Functions Stanza|fuctions stanza]] - to decode DTMF from the node's local receiver.<br />
* The [[#Link Functions Stanza|link_functions stanza]] - to decode DTMF from linked nodes.<br />
* The [[#Phone Functions Stanza|phone_functions stanza]] - to decode DTMF from telephone connects.<br />
<br />
A function stanza key/value pair has the following format:<br />
<br />
dtmfcommand=functionclass,[functionmethod],[parameters]<br />
Where:<br />
* dtmfcommand is a DTMF digit sequence '''minus''' the [[#funcchar=|start character]] (usually *)<br />
* functionclass is a string which defines what class of command; link, status or COP<br />
* functionmethod defines the optional method number to use in the function class.<br />
* functionoptions are one or more optional comma separated parameters which further define a command.<br />
<br />
==Status Commands==<br />
Status commands (functioncalss 'status') provide general information about the node. <br />
<br />
Sample:<br />
<pre><br />
712 = status,12 ; Give Time of Day (local only)<br />
</pre><br />
<br />
{| class="wikitable"<br />
! Status !! Description<br />
|-<br />
| 1 || Force ID (global)<br />
|-<br />
| 2 || Give Time of Day (global)<br />
|-<br />
| 3 || Give software Version (global)<br />
|-<br />
| 4 || Give GPS location info<br />
|-<br />
| 5 || Speak the last (dtmf) user <br />
|-<br />
| 11 || Force ID (local only)<br />
|-<br />
| 12 || Give Time of Day (local only)<br />
|}<br />
<br />
==Link Commands==<br />
Link commands (functioncalss 'link') connect to, disconnect from, monitor (Rx only) other nodes and give link status. <br />
<br />
Sample:<br />
<pre><br />
3 = ilink,3 ; Connect specified link -- transceive<br />
</pre><br />
<br />
{| class="wikitable"<br />
! ilink !! Description<br />
|-<br />
| 1 || Disconnect specified link<br />
|-<br />
| 2 || Connect specified link -- monitor only<br />
|-<br />
| 3 || Connect specified link -- tranceive<br />
|-<br />
| 4 || Enter command mode on specified link<br />
|-<br />
| 5 || System status<br />
|-<br />
| 6 || Disconnect all links<br />
|-<br />
| 7 || Last Node to Key Up<br />
|-<br />
| 8 || Connect specified link -- local monitor only<br />
|-<br />
| 9 || Send Text Message (9,<destnodeno or 0 (for all)>,Message Text, etc.<br />
|-<br />
| 10 || Disconnect all RANGER links (except permalinks)<br />
|-<br />
| 11 || Disconnect a previously permanently connected link<br />
|-<br />
| 12 || Permanently connect specified link -- monitor only<br />
|-<br />
| 13 || Permanently connect specified link -- tranceive<br />
|-<br />
| 15 || Full system status (all nodes)<br />
|-<br />
| 16 || Reconnect links disconnected with "disconnect all links"<br />
|-<br />
| 17 || MDC test (for diag purposes)<br />
|-<br />
| 18 || Permanently Connect specified link -- local monitor only<br />
|}<br />
<br />
==COP Commands==<br />
Control operator (functionclass 'cop') commands are privileged commands. Node admins may provide some of these to their user community based on personal preference. <br />
<br />
Sample:<br />
<pre><br />
99 = cop,7 ; enable timeout timer<br />
</pre><br />
<br />
Some COP commands can take multiple parameters. For example this COP 48 would send #3#607 on command.<br />
<br />
<pre>900 = cop,48,#,3,#,6,0,7</pre> <br />
<br />
{| class="wikitable"<br />
|-<br />
! COP !! Description<br />
|-<br />
| 1 || System warm boot<br />
|-<br />
| 2 || System enable<br />
|-<br />
| 3 || System disable<br />
|-<br />
| 4 || Test Tone On/Off<br />
|-<br />
| 5 || Dump System Variables on Console (debug)<br />
|-<br />
| 6 || PTT (phone mode only)<br />
|-<br />
| 7 || Time out timer enable<br />
|-<br />
| 8 || Time out timer disable<br />
|-<br />
| 9 || Autopatch enable<br />
|-<br />
| 10 || Autopatch disable<br />
|-<br />
| 11 || Link enable<br />
|-<br />
| 12 || Link disable<br />
|-<br />
| 13 || Query System State<br />
|-<br />
| 14 || Change System State<br />
|-<br />
| 15 || Scheduler Enable<br />
|-<br />
|-<br />
| 16 || Scheduler Disable<br />
|-<br />
| 17 || User functions (time, id, etc) enable<br />
|-<br />
| 18 || User functions (time, id, etc) disable<br />
|-<br />
| 19 || Select alternate hang timer<br />
|-<br />
| 20 || Select standard hang timer <br />
|-<br />
| 21 || Enable Parrot Mode<br />
|-<br />
| 22 || Disable Parrot Mode<br />
|-<br />
| 23 || Birdbath (Current Parrot Cleanup/Flush)<br />
|-<br />
| 24 || Flush all telemetry<br />
|-<br />
| 25 || Query last node un-keyed<br />
|-<br />
| 26 || Query all nodes keyed/unkeyed<br />
|-<br />
| 27 || Reset DAQ minimum on a pin<br />
|-<br />
| 28 || Reset DAQ maximum on a pin<br />
|-<br />
| 30 || Recall Memory Setting in Attached Xcvr<br />
|-<br />
| 31 || Channel Selector for Parallel Programmed Xcvr<br />
|-<br />
| 32 || Touchtone pad test: command + Digit string + # to playback all digits pressed<br />
|-<br />
| 33 || Local Telemetry Output Enable<br />
|-<br />
| 34 || Local Telemetry Output Disable<br />
|-<br />
| 35 || Local Telemetry Output on Demand<br />
|-<br />
| 36 || Foreign Link Local Output Path Enable<br />
|-<br />
| 37 || Foreign Link Local Output Path Disable<br />
|-<br />
| 38 || Foreign Link Local Output Path Follows Local Telemetry<br />
|-<br />
| 39 || Foreign Link Local Output Path on Demand<br />
|-<br />
| 42 || Echolink announce node # only<br />
|-<br />
| 43 || Echolink announce node Callsign only<br />
|-<br />
| 44 || Echolink announce node # & Callsign<br />
|-<br />
| 45 || Link Activity timer enable<br />
|-<br />
| 46 || Link Activity timer disable<br />
|-<br />
| 47 || Reset "Link Config Changed" Flag <br />
|-<br />
| 48 || Send Page Tone (Tone specs separated by parenthesis)<br />
|-<br />
| 49 || Disable incoming connections (control state noice)<br />
|-<br />
| 50 || Enable incoming connections (control state noicd)<br />
|-<br />
| 51 || Enable sleep mode<br />
|-<br />
| 52 || Disable sleep mode<br />
|-<br />
| 53 || Wake up from sleep<br />
|-<br />
| 54 || Go to sleep<br />
|-<br />
| 55 || Parrot Once if parrot mode is disabled<br />
|-<br />
| 56 || Rx CTCSS Enable<br />
|-<br />
| 57 || Rx CTCSS Disable<br />
|-<br />
| 58 || Tx CTCSS On Input only Enable<br />
|-<br />
| 59 || Tx CTCSS On Input only Disable<br />
|-<br />
| 60 || Send MDC-1200 Burst (cop,60,type,UnitID[,DestID,SubCode])<br />
Type is 'I' for PttID, 'E' for Emergency, and 'C' for Call <br />
(SelCall or Alert), or 'SX' for STS (ststus), where X is 0-F.<br />
DestID and subcode are only specified for the 'C' type message.<br />
UnitID is the local systems UnitID. DestID is the MDC1200 ID of<br />
the radio being called, and the subcodes are as follows: <br />
Subcode '8205' is Voice Selective Call for Spectra ('Call')<br />
Subcode '8015' is Voice Selective Call for Maxtrac ('SC') or<br />
Astro-Saber('Call')<br />
Subcode '810D' is Call Alert (like Maxtrac 'CA')<br />
|-<br />
| 61 || Send Message to USB to control GPIO pins (cop,61,GPIO1=0[,GPIO4=1].....)<br />
|-<br />
| 62 || Send Message to USB to control GPIO pins, quietly (cop,62,GPIO1=0[,GPIO4=1].....)<br />
|-<br />
| 63 || Send pre-configred APRSTT notification (cop,63,CALL[,OVERLAYCHR])<br />
|-<br />
| 64 || Send pre-configred APRSTT notification, quietly (cop,64,CALL[,OVERLAYCHR]) <br />
|-<br />
| 65 || Send POCSAG page (equipped channel types only)<br />
|}<br />
<br />
==Remote Base Commands==<br />
Remote base commands (functionclass 'remote') provide remote base control. This stanza is [[Structure of Config Files#Settings to name other Stanzas|named by]] the remote base [[#Remote Base Functions=|Remote Base Functions]] key/value pair.<br />
<br />
{| class="wikitable"<br />
! remote !! Description<br />
|-<br />
| 1 || Retrieve Memory<br />
|-<br />
| 2 || Set freq.<br />
|-<br />
| 3 || Set tx PL tone<br />
|-<br />
| 4 || Set rx PL tone<br />
|-<br />
| 5 || Long status query<br />
|-<br />
| 99,CALLSIGN,LICENSETAG || Remote Base login<br />
|-<br />
| 100 || Rx PL off<br />
|-<br />
| 101 || Rx PL on<br />
|-<br />
| 102 || Tx PL off<br />
|-<br />
| 103 || Tx PL on<br />
|-<br />
| 104 || Low Power<br />
|-<br />
| 105 || Medium Power<br />
|-<br />
| 106 || High Power<br />
|-<br />
| 107 || Bump -20<br />
|-<br />
| 108 || Bump -100<br />
|-<br />
| 109 || Bump -500<br />
|-<br />
| 110 || Bump +20<br />
|-<br />
| 111 || Bump +100<br />
|-<br />
| 112 || Bump +500<br />
|-<br />
| 113 || Scan - slow<br />
|-<br />
| 114 || Scan - quick<br />
|-<br />
| 115 || Scan - fast<br />
|-<br />
| 116 || Scan + slow<br />
|-<br />
| 117 || Scan + quick<br />
|-<br />
| 118 || Scan + fast<br />
|-<br />
| 119 || Tune<br />
|-<br />
| 140 || Short status query<br />
|-<br />
| 210 || Send a *<br />
|-<br />
| 211 || Send a #<br />
|}<br />
<br />
Not all commands above are supported by all radios. For example radios which don't support SSB, would not be able to be placed in LSB or USB mode.<br />
<br />
===Remote Base Login===<br />
When [[#authlevel=|authlevel=]] is greater than zero, remote 99 is used to define a different dtmf sequence for each user authorized to use the remote base. The remote base will announce the callsign as access is granted.<br />
<br />
Sample:<br />
<pre><br />
9139583 = remote,99,WB6NIL,G ; grant access to Jim (general)<br />
9148351 = remote,99,WA6ZFT,E ; grant access to Steve (extra)<br />
</pre><br />
When the remote base is disconnected from the originating node, the<br />
user will be logged out. <br />
<br />
The LICENSETAG argument is used to enforce<br />
tx frequency limits. Need info [txlimits].<br />
<br />
= Settings to name other Stanzas =<br />
Within the node stanza, some key=value pairs point to other stanzas. This allows nodes on the same Asterisk/app_rpt server to have the same settings (without duplicate entries) or different settings in some cases. For example the phone patch command may be *6 on one node, yet *61 on another.<br />
<br />
For example:<br />
[1000]<br />
functions=functionsVHF<br />
<br />
[1001]<br />
functions=functionsVHF<br />
<br />
[1002]<br />
functions=functionsUHF<br />
<br />
[functionsVHF]<br />
; Two meter Autopatch up is *6<br />
6=autopatchup,noct=1,farenddisconnect=1,dialtime=20000 <br />
0=autopatchdn ; Autopatch down<br />
<br />
[functionsUHF]<br />
; 440 Autopatch up is *61<br />
61=autopatchup,noct=1,farenddisconnect=1,dialtime=20000 ; Autopatch up<br />
0=autopatchdn ; Autopatch down<br />
* controlstates=<br />
* functions=<br />
* link_functions=<br />
* macro=<br />
* phone_functions=<br />
* telemetry=<br />
* wait_times=<br />
<br />
=Node Number Stanza=<br />
The node number stanza is the first stanza in rpt.conf. <br />
<br />
<pre><br />
[1999] ; Replace with your assigned node number<br />
</pre><br />
<br />
The node number stanza contains the following key/value pairs. <br />
==althangtime===<br />
This controls the length of the repeater hang time when the alternate hang timer is selected with a control operator function. It is specified in milliseconds. <br />
<br />
Sample:<br />
<pre><br />
althangtime=4000 ; 4 seconds<br />
</pre><br />
==beaconing===<br />
When set to 1 will send the repeater ID at the idtime interval regardless of whether there was repeater activity or not. This feature appears to be required in the UK, but is probably illegal in the US.<br />
<br />
Sample:<br />
<pre><br />
beaconing=1 ;Set to 1 to beacon. Defaults to 0<br />
</pre><br />
==callerid===<br />
This setting allows the autopatch on the node to be identified with a specific caller ID. The default setting is as follows<br />
<br />
<pre><br />
callerid="Repeater" <0000000000><br />
</pre><br />
<br />
''Note'': The value in quotes is the name of the autopatch caller, and the numbers in angle brackets are the originating telephone number to use.<br />
<br />
==context===<br />
<br />
This setting directs the autopatch for the node to use a specific context in extensions.conf for outgoing autopatch calls. The default is to specify a context name of radio.<br />
<br />
<pre><br />
context=radio<br />
</pre><br />
<br />
==controlstates===<br />
This setting defines the name of the [[Structure of Config Files|variable named]] control state stanza. Control states are an optional feature which allows groups of control operator commands to be executed all at once. To use control states, define an entry in your node stanzas to point to a dedicated control state stanza like this:<br />
<pre><br />
controlstates = controlstates ; points to control state stanza<br />
<br />
<br />
[controlstates]<br />
0 = rptena,lnkena,apena,totena,ufena,noicd ; Normal operation <br />
1 = rptena,lnkena,apdis,totdis,ufena,noice ; Net and news operation <br />
2 = rptena,lnkdis,apdis,totena,ufdis,noice ; Repeater only operation<br />
</pre><br />
<br />
The [[#Control States Stanza|control state stanza]] describes these mnemonics.<br />
<br />
==duplex===<br />
The duplex key/value pairs sets the duplex mode for desired radio operation. Duplex mode 2 is the default if none specified.<br />
{| class="wikitable"<br />
! Duplex Mode !! Description <br />
|- <br />
| 0 || Half duplex with no telemetry tones or hang time. Special Case: Full duplex if linktolink is set to yes. This mode is preferred when interfacing with an external multiport repeater controller. Comment out idrecording and idtalkover to suppress IDs.<br />
|-<br />
| 1 || Half duplex with telemetry tones and hang time. Does not repeat audio. This mode is preferred when interfacing a simplex node.<br />
|-<br />
| 2 || Full Duplex with telemetry tones and hang time. This mode is preferred when interfacing a repeater. <br />
|- <br />
| 3 || Full Duplex with telemetry tones and hang time, but no repeated audio.<br />
|- <br />
| 4 || Full Duplex with telemetry tones and hang time. Repeated audio only when the autopatch is down.<br />
|}<br />
<br />
Sample:<br />
<pre><br />
duplex = 0 ; 0 = Half duplex with no telemetry tones or hang time.<br />
</pre><br />
<br />
==endchar===<br />
This setting allows the end character used by some control functions to be changed. By default this is a #. The endchar value must not be the same as the funcchar default or overridden value.<br />
<br />
==erxgain===<br />
Echolink receive gain adjustment in +/- db-volts. Used to balance Echolink recieve audio on an app_rpt node. <br />
<br />
<pre><br />
erxgain = -3<br />
</pre><br />
<br />
See [[:Category:How to|Echolink How to]]<br />
<br />
==etxgain===<br />
Echolink transmit gain adjustment in +/- db-volts. Used to balance Echolink transmit audio on an app_rpt node. <br />
<br />
<pre><br />
etxgain = 3<br />
</pre><br />
<br />
See [[:Category:How to|Echolink How to]]<br />
<br />
==funcchar===<br />
This setting can be used to change the default function starting character of * to something else. Please note that the new value chosen must not be the same as the default or overridden value for endchar=.<br />
<br />
==functions===<br />
This [[Structure of Config Files#Settings to name other Stanzas|names (points to)]] the [[#Functions Stanza|function stanza]].<br />
<br />
Sample:<br />
<pre><br />
functions = functionsUHF ; pointer to 440 repeater functions stanza<br />
</pre><br />
<br />
== GUI ==<br />
{| class="wikitable"<br />
!Key<br />
!Valid Values<br />
!Default<br />
|-<br />
|guilinkdefault<br />
|0 = telemetry output off, 1 = telemetry output on, 2 = timed telemetry output on command execution and for a short time thereafter, 3 = follow local telemetry mode<br />
|1<br />
|-<br />
|guilinkdynamic<br />
|0 = disallow users to change the gui telemetry setting with a COP command, 1 = Allow users to change the setting with a COP command<br />
|1<br />
|}<br />
<br />
= Function Classes =<br />
Function classes are names for categories of functions. There are several function classes defined. They are described in the table below:<br />
{| class="wikitable"<br />
!Class<br />
!Description<br />
|-<br />
|cop<br />
|Control operator commands<br />
|-<br />
|ilink<br />
|Internet linking commands<br />
|-<br />
|status<br />
|User Status Commands<br />
|-<br />
|autopatchup<br />
|Autopatch up commands<br />
|-<br />
|autopatchdn<br />
|Autopatch down commands<br />
|-<br />
|remote<br />
|Remote base commands<br />
|-<br />
|macro<br />
|Command Macros<br />
|}<br />
Most of the above command classes require a function method and possibly one or more additional command parameters. Function methods are discussed next.<br />
<br />
= Function Methods =<br />
Function methods are numbers which identify a specific function to execute within a function class. Function Methods are optional and in some cases should be omitted (Such as with the autopatchup method) A complete and up-to-date description of all functon methods can be found in the app_rpt.c source file. Some function methods are shown below as an example below:<br />
1 - Force ID (global)<br />
2 - Give Time of Day (global)<br />
3 - Give software Version (global)<br />
11 - Force ID (local only)<br />
12 - Give Time of Day (local only)<br />
<br />
= Function Options =<br />
Some Function Methods can take function options. These are specified after the Function Method separated with commas. Not all commands require or take Function options. An example of a method which can accept Function Options is the autopatchup method.<br />
<br />
= Putting it all Together =<br />
A small excerpt from the function stanza of rpt.conf is hown below.<br />
[functions]<br />
1=ilink,1 ; Specific link disconnect<br />
6=autopatchup,noct=1,farenddisconnect=1,dialtime=2000 ; Autopatch up<br />
The above example contains DTMF functions with all of the parameters discussed on previous pages.<br />
<br />
In the above example:<br />
* *1 followed by a node number disconnects a specific link. The function class is ''ilink'' and the function method is ''1''<br />
* *6 followed by a phone number brings up the autopatch with the function options specified. Note that there is no function method defined, but there are function options present.<br />
<br />
==hangtime===<br />
This controls the length of the repeater hang time. It is specified in milliseconds. <br />
<br />
Sample:<br />
<pre><br />
hangtime = 1000 ;Set hang time for 1 second<br />
</pre><br />
<br />
==holdofftelem===<br />
This node stanza configuration key forces all telemetry to be held off until a local user on the receiver or a remote user over a link unkeys. There is one exception to this behavior: When an ID needs to be sent and there is activity coming from a linked node.<br />
<br />
Sample:<br />
<pre><br />
holdofftelem = 1 ;Set to 1 to hold off. Default is 0<br />
</pre><br />
<br />
== telemdefault= ==<br />
<pre><br />
telemdefault = 0 = telemetry output off, 1 = telemetry output on, 2 = timed telemetry output on command execution and for a short time thereafter. Default is 1<br />
</pre><br />
<br />
== telemdynamic= ==<br />
<pre><br />
telemdynamic = 0 = disallow users to change the local telemetry setting with a COP command, 1 = Allow users to change the setting with a COP command. Default is 1<br />
</pre><br />
<br />
== phonelinkdefault= ==<br />
<pre><br />
phonelinkdefault = 0 = telemetry output off, 1 = telemetry output on, 2 = timed telemetry output on command execution and for a short time thereafter, 3 = follow local telemetry mode Default is 1<br />
</pre><br />
<br />
== phonelinkdynamic= ==<br />
<pre><br />
phonelinkdynamic = 0 = disallow users to change phone telemetry setting with a COP command, 1 = Allow users to change the setting with a COP command Default is 1<br />
</pre><br />
<br />
==idrecording===<br />
The identifier message is stored in the node stanza using the idrecording key. It can be changed to a different call sign by changing the value to something different. The value can be either a morse code identification string prefixed with |i, or the name of a sound file containing a voice identification message. When using a sound file, the default path for the sound file is /var/lib/asterisk/sounds. <br />
<br />
Sample:<br />
<pre><br />
idrecording = |iwa6zft/r ; Morse Code ID<br />
</pre><br />
or<br />
<pre><br />
idrecording = /var/lib/asterisk/sounds/myid ; Voice ID<br />
</pre><br />
''Note'': ID recording files must have extension gsm,ulaw,pcm, or wav. The extension is left off when it is defined as the example shows above. File extensions are used by Asterisk to determine how to decode the file. All ID recording files should be sampled at 8KHz. See [[Recording Audio Files|Recording audio files]]<br />
<br />
==idtalkover===<br />
The ID talkover message is stored in the node stanza using the idtalkover setting. The purpose of idtalkover is to specify an alternate ID to use when the ID must be sent over the top of a user transmission, This can be a shorter voice ID or an ID in morse code. The value can be either a morse code identification string prefixed with |i, or the name of a sound file containing a voice identification message. When using a sound file, the default path for the sound file is /var/lib/asterisk/sounds. Example usages are as follows:<br />
<br />
Sample:<br />
<pre><br />
idtalkover = |iwa6zft/r ; Morse Code ID<br />
</pre><br />
or<br />
<pre><br />
idtalkover = /var/lib/asterisk/sounds/myid ; Voice ID<br />
</pre><br />
''Note'': ID recording files must have extension gsm,ulaw,pcm, or wav. The extension is left off when it is defined as the example shows above. File extensions are used by Asterisk to determine how to decode the file. All ID recording files should be sampled at 8KHz. See [[Recording Audio Files|Recording audio files]]<br />
<br />
==inxlat===<br />
The inxlat setting allows complete remapping of the funcchar and endchar digits to different digits or digit sequences.<br />
inxlat acts on the digits received by the radio receiver on the node.<br />
<br />
Format: inxlat = funchars,endchars,passchars,dialtone<br />
<br />
where:<br />
<br />
* funcchars is the digit or digit sequence to replace funcchar<br />
* endchars is the digit or digit sequence to replace endchar<br />
* passchars are the digits to pass through (can be used to block certain digits)<br />
* dialtone is optional. Set to Y for dial tone on successful funcchars.<br />
<br />
Sample:<br />
<pre><br />
inxlat = #56,#57,0123456789ABCD ; string xlat from radio port to sys<br />
</pre><br />
<br />
==link_functions===<br />
This [[Structure of Config Files#Settings to name other Stanzas|names (points to)]] the link_functions stanza.<br />
<br />
The link_functions setting directs the node to use a particular function stanza for functions dialed by users accessing the node via a link from another node. The traditional default is to point it to a function stanza named "functions".<br />
<br />
Sample:<br />
<pre><br />
link_functions = functions ; pointer to the Link Function stanza<br />
</pre><br />
<br />
==linkmongain===<br />
Link Monitor Gain adjusts the audio level of monitored nodes when a signal from another node or the local receiver is received. If linkmongain is set to a negative number the monitored audio will decrease by the set amount in db. If linkmongain set to a positive number monitored audio will increase by the set amount in db. The value of linkmongain is in db. The default value is 0 db.<br />
<br />
Sample:<br />
<pre><br />
linkmongain = -20 ; reduce link volume 20dB<br />
</pre><br />
<br />
==linktolink===<br />
When operating in duplex mode 0, this forces the radio interface to operate in full duplex mode, but keeps all the other duplex mode 0 semantics. This is used when a radio interface is connected to a multiport analog repeater controller. The linktolink= key can take two values: yes or no.<br />
<br />
Sample:<br />
<pre><br />
linktolink = yes ; set to yes to enable. Default is no.<br />
</pre><br />
<br />
==linkunkeyct===<br />
The linkunkeyct setting selects the courtesy tone to send when a connected remote node unkeys. The default is no courtesy tone when a remote node unkeys.<br />
<br />
Sample:<br />
<pre><br />
linkunkeyct = ct8 ; use courtesy tone 8<br />
</pre><br />
<br />
==macro===<br />
The marco key/value points to by the [[#Macro Stanza|Macro Stanza]] key/value pair. Macros are DTMF shortcuts. <br />
<br />
Sample:<br />
<pre><br />
macro=macro ; use stanza names 'macros'<br />
<br />
[macro]<br />
1 = *32000*32001 ; connect to nodes 2000 and 2001<br />
</pre><br />
<br />
==nounkeyct===<br />
The nounkeyct node stanza key completely disables the courtesy tone. This is useful for eliminating TX time in applications using simplex uplinks to repeaters on the repeater pair itself. This practice is '''strongly''' discouraged.<br />
<br />
Sample:<br />
<pre><br />
nounkeyct = yes ; :(<br />
</pre><br />
<br />
==politeid===<br />
The politeid setting specified the number of milliseconds prior to the end of the id cycle where the controller will attempt to play the ID in the tail when a user unkeys. If the controller does not get a chance to send the ID in the tail, the ID will be played over the top of the user transmission. Optional, default 30000.<br />
<br />
Sample:<br />
<pre><br />
politeid = 30000 ; 30 seconds<br />
</pre><br />
<br />
==propagate_dtmf===<br />
Takes either yes or no. When set to yes, DTMF will be regenerated from out-of-band signalling or from from the receiver dtmf decoder whenever a function start character is NOT detected and command decoding has not begun. When set to no, no tones will be regenerated. The default for this setting is no.<br />
This setting is meant to be used in conjunction with linktolink, inxlat, and outxlat when interfacing a radio port to a multiport analog repeater controller on an RF-linked system.<br />
<br />
Sample:<br />
<pre><br />
propagate_dtmf = no<br />
</pre><br />
''Note'': There is a separate setting propagate_phonedtmf for use by dial-in (phone and dphone) users.<br />
<br />
==remotect===<br />
The remotect setting allows the selection of the remote linked courtesy tone so that the users can tell there is a [[:Category:Remote Base|remote base]] connected locally.<br />
<br />
Sample:<br />
<pre><br />
remotect = ct3 ; use courtesy tone 3<br />
</pre><br />
<br />
==rxburstfreq===<br />
If rx tone burst operation is desired, specify the frequency in hertz of the desired tone burst. Setting to 0 (or not specifying) indicates no tone burst operation.<br />
<br />
Sample:<br />
<pre><br />
rxburstfreq = 1000<br />
</pre><br />
<br />
==rxburstthreshold===<br />
In rx toneburst mode, specifies the minimum signal to noise ratio in db that qualifies a valid tone.<br />
Defaults to 16 (db).<br />
<br />
==rxbursttime===<br />
For rx toneburst operation, specifies minimum amount of time that tone needs to be valid for recognition (in milliseconds). Defaults to 250.<br />
<br />
==rxchannel===<br />
The rxchannel key/value pair selects the radio interface. There must be one (and only one) rxchannel per node. The selections are: <br />
<br />
{| class="wikitable"<br />
! Value !! Description <br />
|- <br />
| dahdi/pseudo || No radio, used for hubs<br />
|- <br />
| SimpleUSB/usb_1999 || [[Simpleusb.conf|SimpleUSB (limited DSP)]] <br />
|- <br />
| Radio/usb_1999 || [[Usbradio.conf|USBRadio (full DSP)]] <br />
|- <br />
| voter/1990 || [[Voter.conf|RTCM]] <br />
|- <br />
| Pi/1 || Raspberry Pi PiTA <br />
|- <br />
| Dahdi/1 || PCI Quad card <br />
|- <br />
| Beagle/1 || BeagleBoard <br />
|- <br />
| USRP/127.0.0.1:34001:32001 || GNU Radio interface USRP<br />
|}<br />
Sample:<br />
<pre><br />
rxchannel = dahdi/pseudo ; No radio (hub)<br />
</pre><br />
<br />
''Note'': This is selecting what is known as (in Asterisk terminology) the channel driver.<br />
<br />
==scheduler===<br />
This setting defines the scheduler stanza. The scheduler is used to execute commands at a particular time.<br />
<br />
Sample:<br />
<pre><br />
scheduler = schedule ; name scheduler to 'schedule'<br />
<br />
[schedule]<br />
...<br />
</pre><br />
<br />
==sleeptime===<br />
This sets the inactivity period in seconds for no signal on the repeater receiver before the system goes to sleep. <br />
<br />
Sample:<br />
<pre><br />
sleeptime = 300 ; go to sleep after 5 mins of no activity<br />
</pre><br />
<br />
==startup_macro===<br />
The startup_macro is executed once on system startup. Each node can have one startup macro defined in its node stanza.<br />
<br />
Sample:<br />
<pre><br />
startup_macro = *31000*31001*31002 ; Connect to 1000, 1001 and 1002 at startup<br />
</pre><br />
<br />
==tailmessagelist===<br />
The tailmessagelist setting allows a comma separated list of audio files to be specified for the tail message function. The tail messages will rotate from one to the next until the end of the list is reached at which point the first message in the list will be selected. If no absolute path name is specified, the directory var/lib/asterisk/sounds will be searched for the sound file. The file extension should be omitted.<br />
<br />
Sample:<br />
<pre><br />
tailmessagelist = welcome,clubmeeting,wx ; rotate 3 tail messages<br />
</pre><br />
<br />
''Note'': ID recording files must have extension gsm,ulaw,pcm, or wav. The extension is left off when it is defined as the example shows above. File extensions are used by Asterisk to determine how to decode the file. All ID recording files should be sampled at 8KHz. See [[Recording Audio Files|Recording audio files]]<br />
<br />
==tailmessagetime===<br />
This sets the amount of time in milliseconds between tail messages. Tail Messages are played when a user unkeys on the repeater input at the point where the hang timer expires after the courtesy tone is sent.<br />
<br />
Sample:<br />
<pre><br />
tailmessagetime = 900000 ; 15 minutes between tail messages<br />
</pre><br />
<br />
==tailsquashedtime===<br />
If a tail message is "squashed" by a user keying up over the top of it, a separate time value can be loaded to make the tail message be retried at a shorter time interval than the standard tailmessagetime= setting. The tailsquashedtime= setting takes a value in milliseconds.<br />
<br />
Sample:<br />
<pre><br />
tailsquashedtime = 300000 ; 5 minutes<br />
</pre><br />
<br />
==totime===<br />
This defines the time out timer interval. The value is in milliseconds.<br />
<br />
Sample:<br />
<pre><br />
totime = 180000 ; 3 minutes<br />
</pre><br />
<br />
==unlinkedct===<br />
The unlinkedct setting selects the courtesy tone to be used when the system has no remote nodes connected and is operating as a standalone repeater.<br />
<br />
Sample:<br />
<pre><br />
unlinkedct = ct2 ; use courtesy tone 2<br />
</pre><br />
<br />
==wait-times===<br />
Wait-times points to the [[#Wait Times Stanza|Wait Times Stanza]].<br />
<br />
Sample:<br />
<pre><br />
wait-times = wait-times ; name wait-times to 'wait-times'<br />
</pre><br />
<br />
=Functions Stanza=<br />
The functions stanza is a named stanza [[Structure of Config Files#Settings to name other Stanzas|pointed to]] by the [[#functions=|function=]] key/value pair. Functions within this stanza are used to decode DTMF commands when accessing the node from its receiver. This stanza is typically named 'functions'. <br />
<br />
Sample:<br />
<pre><br />
functions = functions ; name the functions stanza 'functions'<br />
<br />
[functions]<br />
...<br />
</pre><br />
See [[#DTMF Commands|DTMF Commands]] for the list of functions available.<br />
<br />
=Link Functions Stanza=<br />
The link functions stanza is a named stanza [[Structure of Config Files#Settings to name other Stanzas|pointed to]] by the [[#link_functions=|link_function=]] key/value pair. Functions within this stanza are used decode DTMF commands when accessing the node via a link from another node. The traditional usage is to point link_functions= to the same stanza as named by [[#functions=|functions=]] thereby having functions from a linked node and from the local node the same.<br />
<br />
Sample:<br />
<pre><br />
functions = functions ; name the functions stanza 'functions'<br />
link_functions = functions ; use the same stanza <br />
<br />
[functions]<br />
...<br />
</pre><br />
If a different set of either limited or more capable functions is desired:<br />
<pre><br />
functions = functions ; name the functions stanza 'functions'<br />
link_functions = my_link_functions ; use a different stanza<br />
<br />
[functions]<br />
...<br />
<br />
[my_link_functions]<br />
...<br />
</pre><br />
See [[#DTMF Commands|DTMF Commands]] for the list of functions available.<br />
<br />
=Phone Functions Stanza=<br />
The phone functions stanza is a named stanza [[Structure of Config Files#Settings to name other Stanzas|pointed to]] by the [[#phone_functions=|phone_function=]] key/value pair. Functions within this stanza are used decode DTMF commands when accessing the node from a telephone. The traditional usage is to point phone_functions= to the same stanza as named by [[#functions=|functions=]] thereby having functions from a phone and from the local node the same. <br />
<br />
Sample:<br />
<pre><br />
functions = functions ; name the functions stanza 'functions'<br />
phone_functions = functions ; use the same stanza <br />
<br />
[functions]<br />
...<br />
</pre><br />
If a different set of either limited or more capable functions is desired:<br />
<pre><br />
functions = functions ; name the functions stanza 'functions'<br />
phone_functions = my_phone_functions ; use a different stanza<br />
<br />
[functions]<br />
...<br />
<br />
[my_phone_functions]<br />
...<br />
</pre><br />
See [[#DTMF Commands|DTMF Commands]] for the list of functions available.<br />
<br />
=Macro Stanza=<br />
The marco stanza is named stanza pointed to by the [[#macro=|macro=]] key/value pair. Macros are DTMF shortcuts. <br />
<br />
Sample:<br />
<pre><br />
macro=macro ; use stanza names 'macros'<br />
<br />
[macro]<br />
1 = *32000*32001 ; connect to nodes 2000 and 2001<br />
</pre><br />
<br />
=Remote Base Stanza=<br />
Here are [[Structure of Config Files|key/value pairs]] required to configure a remote base.<br />
<br />
==authlevel===<br />
The authlevel= key is used to enable or disable login requirements for a remote base.<br />
<br />
* authlevel=0 Disables all access control (not recommended, unsecured)<br />
* authlevel=1 Enables access control, and waits for key up before prompting for the access code<br />
* authlevel=2 Enables access control, and prompts for the access code at the time of connection<br />
<br />
Sample:<br />
<pre><br />
autllevel = 0 ; allow all comers <br />
</pre><br />
<br />
==civaddr===<br />
civaddr= is used with ICOM band radios to set the CIV address. The value is a 2 digit hexadecimal number. If this key is not specified, then the CIV address will be set to the default of 88. <br />
<br />
Sample:<br />
<pre><br />
civaddr = 98 ; set CIV to 98<br />
</pre><br />
<br />
==Remote Base functions===<br />
functions= is a pointer to a remote base function stanza. <br />
<br />
Sample:<br />
<pre><br />
functions = functions-remote ; name the functions stanza 'functions-remote'<br />
<br />
[functions-remote]<br />
...<br />
</pre><br />
<br />
See [[#Remote Base Functions Stanza|Remote Base Functions Stanza]].<br />
<br />
==ioaddr===<br />
ioaddr= refers to a parallel port I/O address. It is specified as a hexadecimal number with a 0x prefix. The parallel port is used when the Doug Hall RBI-1 interface is employed.<br />
<br />
Sample:<br />
<pre><br />
ioaddr = 0x378 ; set RB-1 address<br />
</pre><br />
<br />
==ioport===<br />
ioport= sets the serial port. On Linux Systems, these are typically path names to special files in the /dev directory.<br />
<br />
Sample:<br />
<pre><br />
ioport = /dev/ttyS1 ; Linux com1<br />
</pre><br />
<br />
==Remote Base phone_functions===<br />
phone_functions= is a pointer to a remote base phone function stanza. It is equivalent to phone_functions in the [[#Phone Functions Stanza|Phone Functions Stanza]] but provides a separate set of commands. <br />
<br />
Sample:<br />
<pre><br />
phone_functions = functions-remote<br />
</pre><br />
<br />
==remote===<br />
remote= sets the type of radio. It also ensures that the node will be defined as a remote base node and not a standard node.<br />
<br />
Sample:<br />
<pre><br />
remote = xcat ; set xcat interface<br />
</pre><br />
<br />
{| class="wikitable"<br />
! Radio !! Value !! Comments<br />
|-<br />
| Dumb || y || Use for single channel remote base radios<br />
|-<br />
| FT-897 || ft897 || Must specify serial port using ioport=<br />
|-<br />
| TMG-707 || kenwood || Must specify serial port using ioport=<br />
|-<br />
| IC-706 || ic706 || Must specify serial port using ioport=. Must specify civaddr using civaddr=<br />
|-<br />
| TM-271 || tm271 || Must specify serial port using ioport=<br />
|-<br />
| Syntor Xcat || xcat || Must specify serial port using ioport=. Must specify civaddr using civaddr=<br />
|}<br />
<br />
==remote_inact_timeout===<br />
<br />
Specifies the amount of time without keying from the link. Set to 0 to disable timeout.<br />
<br />
Sample:<br />
<pre><br />
remote_inact_timeout = 0 ; do not time out<br />
</pre><br />
<br />
==remote_timeout===<br />
Session time out for remote base. Set to 0 to disable.<br />
<br />
Sample:<br />
<pre><br />
remote_timeout = 0 ; do not timeout<br />
</pre><br />
<br />
==remote_timeout_warning===<br />
<br />
==remote_timeout_freq===<br />
<br />
==Remote Base rxchannel===<br />
This should contain the name of a usb radio interface which has been defined in [[usbradio.conf]] or a zaptel interface number if using a Quad Radio PCI Card.<br />
<br />
Sample:<br />
<pre><br />
rxchannel = usbRadio/usb1<br />
</pre><br />
<br />
==Sample Remote Configuration==<br />
<pre><br />
[1234]<br />
; Rx audio/signaling channel <br />
rxchannel = Radio/usb<br />
<br />
; Serial port for control<br />
ioport = /dev/ttyS1<br />
<br />
; Radio Type <br />
remote = ft897 <br />
<br />
; Function list from link <br />
functions = functions-remote <br />
<br />
; Function list from phone <br />
phone_functions = functions-remote<br />
<br />
; Authorization level <br />
authlevel = 0 <br />
</pre><br />
<br />
=Nodes Stanza=<br />
The [nodes] stanza is a list of nodes, their IP addresses, port and "NONE" for non-remote base nodes. The nodes stanza is used to identify which node is mapped to which Internet call and to determine the destination to send the call to. If you are using automatic update for Allstar link (public) nodes, no Allstar link nodes should be defined here. Only place a definition for your local nodes, and private (off of allstar link) nodes or nodes behind the same NAT router here.<br />
<br />
Sample:<br />
<pre><br />
[nodes]<br />
1000 = radio@127.0.0.1/1000,NONE ; Private hub on this server<br />
1001 = radio@host.domain.com/1001,NONE ; Private node on another server<br />
2501 = radio@127.0.0.1/2501,NONE ; Public node on this server<br />
2502 = radio@127.0.0.1/2502,NONE ; Another public node on this server<br />
2503 = radio@192.168.1.20:4570/2503,NONE ; Public node behind the same NAT router<br />
</pre><br />
The [nodes] stanza performs a function similar to an OS hosts file. When looking up node information, app_rpt looks in the [nodes] stanza first then searches (what could be called the Allstar DNS) the /var/lib/asterisk/rpt_extnodes file.<br />
<br />
=Telemetry Stanza=<br />
This stanza is named by the telemetry= key/value pair. Telemetry entries can be shared across all nodes on the Asterisk/app_rpt server, or defined for each node. Can be a tone sequence, morse string, or a file as follows:<br />
<br />
* |t - Tone escape sequence:<br />
** Tone sequences consist of 1 or more 4-tuple entries (freq1, freq2, duration, amplitude). Single frequencies are created by setting freq1 or freq2 to zero.<br />
* |m - Morse escape sequence:<br />
**Sends Morse code at the '''telemetry amplitude and telemetry frequency''' as defined in the [morse] section. Follow with an alphanumeric string.<br />
* |i - Morse ID escape sequence:<br />
**Sends Morse code at the '''ID amplitude and ID frequency''' as defined in the [morse] section. Follow with an alphanumeric string.<br />
* Path to sound file:<br />
**Specify the path to a sound file on the server. Do not include file extension.<br />
<br />
Sample:<br />
<pre><br />
[telemetry]<br />
ct1=|t(350,0,100,2048)(500,0,100,2048)(660,0,100,2048)<br />
ct2=|t(660,880,150,2048) <br />
ct3=|t(440,0,150,4096) <br />
ct4=|t(550,0,150,2048)<br />
ct4=|t(2475,0,250,768)<br />
ct5=|t(660,0,150,2048)<br />
ct6=|t(880,0,150,2048)<br />
ct7=|t(660,440,150,2048)<br />
ct8=|t(700,1100,150,2048)<br />
ct9=|t(1633,0,50,1000)(0,0,30,0)(1209,0,50,1000); <br />
;remotetx=|t(1633,0,50,3000)(0,0,80,0)(1209,0,50,3000);<br />
remotetx=|t(880,0,150,2048) <br />
remotemon=|t(1209,0,50,2048) <br />
cmdmode=|t(900,903,200,2048)<br />
functcomplete=|t(1000,0,100,2048)(0,0,100,0)(1000,0,100,2048)<br />
patchup=rpt/callproceeding<br />
patchdown=rpt/callterminated<br />
<br />
What the numbers mean,<br />
(000,000,010,000)<br />
| | | |-------amplitude<br />
| | |-------------duration<br />
| |-------------------Tone 2<br />
|-------------------------Tone 1<br />
<br />
</pre><br />
<br />
=Morse Stanza=<br />
Morse code parameters, these are common to all nodes on a given Asterisk/app_rpt server.<br />
<br />
Sample:<br />
<pre><br />
[morse]<br />
speed = 20 ; Approximate speed in WPM<br />
frequency = 900 ; Morse Telemetry Frequency<br />
amplitude = 4096 ; Morse Telemetry Amplitude<br />
idfrequency = 746 ; Morse ID Frequency <br />
idamplitude = 768 ; Morse ID Amplitude<br />
</pre><br />
<br />
=Wait Times Stanza=<br />
This stanza is named by the [[#wait-times=|wait-times=]] key/value pair. The wait time stanza is used to set delay time between various node actions and their response. Values are in milliseconds.<br />
<br />
Sample:<br />
<pre><br />
wait-times = wait-times ; name the stanza 'wait-times'<br />
<br />
[wait-times] <br />
telemwait = 2000<br />
idwait = 500<br />
unkeywait = 2000<br />
calltermwait = 2000<br />
</pre><br />
<br />
=Remote Base Memory Stanza=<br />
Remote base memories are in the format of:<br />
<br />
memory = rxfreq,plfreq,txpower,offset,tone<br />
<br />
Sample:<br />
<pre><br />
[memory]<br />
00 = 146.580,100.0,m<br />
01 = 147.030,103.5,m+t<br />
02 = 147.240,103.5,m+t<br />
03 = 147.765,79.7,m-t<br />
04 = 146.460,100.0,m<br />
05 = 146.550,100.0,m<br />
</pre><br />
<br />
=Control States Stanza=<br />
<br />
There are several predefined nmemonics (keywords) used in the control state stanza to enable and disable the various features of the controller. These nmemonics correspond to the control operator command to be executed and most of these are the same groups of letters sent back when a single control operator command is executed on the controller.<br />
<br />
{| class="wikitable"<br />
! Nmemonic !! Description !! COP Method<br />
|-<br />
| rptena || Repeater Enable || 2<br />
|-<br />
| rptdis || Repeater Disable || 3<br />
|-<br />
| totena || Timeout Timer Enable || 7<br />
|-<br />
| totdis || Timeout Timer Disable || 8<br />
|-<br />
| apena || Autopatch Enable || 9<br />
|-<br />
| apdis || Autopatch Disable || 10<br />
|-<br />
| lnkena || Link Enable || 11<br />
|-<br />
| lnkdis || Link Disable || 12<br />
|-<br />
| skena || Scheduler Enable || 15<br />
|-<br />
| skdis || Scheduler Disable || 16<br />
|-<br />
| ufena || User Functions Enable || 17<br />
|-<br />
| ufdis || User Functions Disable || 18<br />
|-<br />
| atena || Alternate Hangtime Enable || 19<br />
|-<br />
| atdis || Alternate Hangtime Disable || 20<br />
|-<br />
| noice || No Incoming Connections Enable || 49<br />
|-<br />
| noicd || No Incoming Connections Disable || 50<br />
|-<br />
| slpen || Sleep Mode Enable || 51<br />
|-<br />
| slpds || Sleep Mode Disable || 52<br />
|}<br />
<br />
=Schedule Stanza=<br />
The scheduler can execute commands at certain times. For example for a net on Tuesday nights at 8 PM.<br />
<br />
Sample:<br />
<pre><br />
scheduler=schedule ; name the stanza 'schedule'<br />
<br />
[schedule] <br />
;dtmf_function = m h dom mon dow ; ala cron, star is implied <br />
2 = 00 00 * * * ; at midnight every day, execute macro 2.<br />
</pre><br />
<br />
=DAQ List Stanza=<br />
<br />
=Meter Faces Stanza=<br />
<br />
=Alarms Stanza=<br />
<br />
[[Category:Node Configuration]]<br />
[[Category:Config Files]]</div>N8THNhttps://wiki.pttlink.org/index.php?title=Rpt.conf&diff=1329Rpt.conf2019-01-28T15:20:37Z<p>N8THN: added telemdefault and telemdynamic</p>
<hr />
<div>Rpt.conf is where the majority of user-facing features, such as the node's CW and voice ID, DTMF commands and timers are set. There is a lot of capability here which can be difficult to grasp. Fortunately the default [https://github.com/AllStarLink/DIAL/blob/master/configs/rpt.conf DIAL rpt.conf] is well commented and will work fine for most node admins. <br />
<br />
=DTMF Commands=<br />
DTMF commands are placed in any one of three [[Structure of Config Files|named stanzas]]. Function stanzas control access to DTMF commands that a user can issue from various <br />
control points.<br />
* The [[#Functions Stanza|fuctions stanza]] - to decode DTMF from the node's local receiver.<br />
* The [[#Link Functions Stanza|link_functions stanza]] - to decode DTMF from linked nodes.<br />
* The [[#Phone Functions Stanza|phone_functions stanza]] - to decode DTMF from telephone connects.<br />
<br />
A function stanza key/value pair has the following format:<br />
<br />
dtmfcommand=functionclass,[functionmethod],[parameters]<br />
Where:<br />
* dtmfcommand is a DTMF digit sequence '''minus''' the [[#funcchar=|start character]] (usually *)<br />
* functionclass is a string which defines what class of command; link, status or COP<br />
* functionmethod defines the optional method number to use in the function class.<br />
* functionoptions are one or more optional comma separated parameters which further define a command.<br />
<br />
==Status Commands==<br />
Status commands (functioncalss 'status') provide general information about the node. <br />
<br />
Sample:<br />
<pre><br />
712 = status,12 ; Give Time of Day (local only)<br />
</pre><br />
<br />
{| class="wikitable"<br />
! Status !! Description<br />
|-<br />
| 1 || Force ID (global)<br />
|-<br />
| 2 || Give Time of Day (global)<br />
|-<br />
| 3 || Give software Version (global)<br />
|-<br />
| 4 || Give GPS location info<br />
|-<br />
| 5 || Speak the last (dtmf) user <br />
|-<br />
| 11 || Force ID (local only)<br />
|-<br />
| 12 || Give Time of Day (local only)<br />
|}<br />
<br />
==Link Commands==<br />
Link commands (functioncalss 'link') connect to, disconnect from, monitor (Rx only) other nodes and give link status. <br />
<br />
Sample:<br />
<pre><br />
3 = ilink,3 ; Connect specified link -- transceive<br />
</pre><br />
<br />
{| class="wikitable"<br />
! ilink !! Description<br />
|-<br />
| 1 || Disconnect specified link<br />
|-<br />
| 2 || Connect specified link -- monitor only<br />
|-<br />
| 3 || Connect specified link -- tranceive<br />
|-<br />
| 4 || Enter command mode on specified link<br />
|-<br />
| 5 || System status<br />
|-<br />
| 6 || Disconnect all links<br />
|-<br />
| 7 || Last Node to Key Up<br />
|-<br />
| 8 || Connect specified link -- local monitor only<br />
|-<br />
| 9 || Send Text Message (9,<destnodeno or 0 (for all)>,Message Text, etc.<br />
|-<br />
| 10 || Disconnect all RANGER links (except permalinks)<br />
|-<br />
| 11 || Disconnect a previously permanently connected link<br />
|-<br />
| 12 || Permanently connect specified link -- monitor only<br />
|-<br />
| 13 || Permanently connect specified link -- tranceive<br />
|-<br />
| 15 || Full system status (all nodes)<br />
|-<br />
| 16 || Reconnect links disconnected with "disconnect all links"<br />
|-<br />
| 17 || MDC test (for diag purposes)<br />
|-<br />
| 18 || Permanently Connect specified link -- local monitor only<br />
|}<br />
<br />
==COP Commands==<br />
Control operator (functionclass 'cop') commands are privileged commands. Node admins may provide some of these to their user community based on personal preference. <br />
<br />
Sample:<br />
<pre><br />
99 = cop,7 ; enable timeout timer<br />
</pre><br />
<br />
Some COP commands can take multiple parameters. For example this COP 48 would send #3#607 on command.<br />
<br />
<pre>900 = cop,48,#,3,#,6,0,7</pre> <br />
<br />
{| class="wikitable"<br />
|-<br />
! COP !! Description<br />
|-<br />
| 1 || System warm boot<br />
|-<br />
| 2 || System enable<br />
|-<br />
| 3 || System disable<br />
|-<br />
| 4 || Test Tone On/Off<br />
|-<br />
| 5 || Dump System Variables on Console (debug)<br />
|-<br />
| 6 || PTT (phone mode only)<br />
|-<br />
| 7 || Time out timer enable<br />
|-<br />
| 8 || Time out timer disable<br />
|-<br />
| 9 || Autopatch enable<br />
|-<br />
| 10 || Autopatch disable<br />
|-<br />
| 11 || Link enable<br />
|-<br />
| 12 || Link disable<br />
|-<br />
| 13 || Query System State<br />
|-<br />
| 14 || Change System State<br />
|-<br />
| 15 || Scheduler Enable<br />
|-<br />
|-<br />
| 16 || Scheduler Disable<br />
|-<br />
| 17 || User functions (time, id, etc) enable<br />
|-<br />
| 18 || User functions (time, id, etc) disable<br />
|-<br />
| 19 || Select alternate hang timer<br />
|-<br />
| 20 || Select standard hang timer <br />
|-<br />
| 21 || Enable Parrot Mode<br />
|-<br />
| 22 || Disable Parrot Mode<br />
|-<br />
| 23 || Birdbath (Current Parrot Cleanup/Flush)<br />
|-<br />
| 24 || Flush all telemetry<br />
|-<br />
| 25 || Query last node un-keyed<br />
|-<br />
| 26 || Query all nodes keyed/unkeyed<br />
|-<br />
| 27 || Reset DAQ minimum on a pin<br />
|-<br />
| 28 || Reset DAQ maximum on a pin<br />
|-<br />
| 30 || Recall Memory Setting in Attached Xcvr<br />
|-<br />
| 31 || Channel Selector for Parallel Programmed Xcvr<br />
|-<br />
| 32 || Touchtone pad test: command + Digit string + # to playback all digits pressed<br />
|-<br />
| 33 || Local Telemetry Output Enable<br />
|-<br />
| 34 || Local Telemetry Output Disable<br />
|-<br />
| 35 || Local Telemetry Output on Demand<br />
|-<br />
| 36 || Foreign Link Local Output Path Enable<br />
|-<br />
| 37 || Foreign Link Local Output Path Disable<br />
|-<br />
| 38 || Foreign Link Local Output Path Follows Local Telemetry<br />
|-<br />
| 39 || Foreign Link Local Output Path on Demand<br />
|-<br />
| 42 || Echolink announce node # only<br />
|-<br />
| 43 || Echolink announce node Callsign only<br />
|-<br />
| 44 || Echolink announce node # & Callsign<br />
|-<br />
| 45 || Link Activity timer enable<br />
|-<br />
| 46 || Link Activity timer disable<br />
|-<br />
| 47 || Reset "Link Config Changed" Flag <br />
|-<br />
| 48 || Send Page Tone (Tone specs separated by parenthesis)<br />
|-<br />
| 49 || Disable incoming connections (control state noice)<br />
|-<br />
| 50 || Enable incoming connections (control state noicd)<br />
|-<br />
| 51 || Enable sleep mode<br />
|-<br />
| 52 || Disable sleep mode<br />
|-<br />
| 53 || Wake up from sleep<br />
|-<br />
| 54 || Go to sleep<br />
|-<br />
| 55 || Parrot Once if parrot mode is disabled<br />
|-<br />
| 56 || Rx CTCSS Enable<br />
|-<br />
| 57 || Rx CTCSS Disable<br />
|-<br />
| 58 || Tx CTCSS On Input only Enable<br />
|-<br />
| 59 || Tx CTCSS On Input only Disable<br />
|-<br />
| 60 || Send MDC-1200 Burst (cop,60,type,UnitID[,DestID,SubCode])<br />
Type is 'I' for PttID, 'E' for Emergency, and 'C' for Call <br />
(SelCall or Alert), or 'SX' for STS (ststus), where X is 0-F.<br />
DestID and subcode are only specified for the 'C' type message.<br />
UnitID is the local systems UnitID. DestID is the MDC1200 ID of<br />
the radio being called, and the subcodes are as follows: <br />
Subcode '8205' is Voice Selective Call for Spectra ('Call')<br />
Subcode '8015' is Voice Selective Call for Maxtrac ('SC') or<br />
Astro-Saber('Call')<br />
Subcode '810D' is Call Alert (like Maxtrac 'CA')<br />
|-<br />
| 61 || Send Message to USB to control GPIO pins (cop,61,GPIO1=0[,GPIO4=1].....)<br />
|-<br />
| 62 || Send Message to USB to control GPIO pins, quietly (cop,62,GPIO1=0[,GPIO4=1].....)<br />
|-<br />
| 63 || Send pre-configred APRSTT notification (cop,63,CALL[,OVERLAYCHR])<br />
|-<br />
| 64 || Send pre-configred APRSTT notification, quietly (cop,64,CALL[,OVERLAYCHR]) <br />
|-<br />
| 65 || Send POCSAG page (equipped channel types only)<br />
|}<br />
<br />
==Remote Base Commands==<br />
Remote base commands (functionclass 'remote') provide remote base control. This stanza is [[Structure of Config Files#Settings to name other Stanzas|named by]] the remote base [[#Remote Base Functions=|Remote Base Functions]] key/value pair.<br />
<br />
{| class="wikitable"<br />
! remote !! Description<br />
|-<br />
| 1 || Retrieve Memory<br />
|-<br />
| 2 || Set freq.<br />
|-<br />
| 3 || Set tx PL tone<br />
|-<br />
| 4 || Set rx PL tone<br />
|-<br />
| 5 || Long status query<br />
|-<br />
| 99,CALLSIGN,LICENSETAG || Remote Base login<br />
|-<br />
| 100 || Rx PL off<br />
|-<br />
| 101 || Rx PL on<br />
|-<br />
| 102 || Tx PL off<br />
|-<br />
| 103 || Tx PL on<br />
|-<br />
| 104 || Low Power<br />
|-<br />
| 105 || Medium Power<br />
|-<br />
| 106 || High Power<br />
|-<br />
| 107 || Bump -20<br />
|-<br />
| 108 || Bump -100<br />
|-<br />
| 109 || Bump -500<br />
|-<br />
| 110 || Bump +20<br />
|-<br />
| 111 || Bump +100<br />
|-<br />
| 112 || Bump +500<br />
|-<br />
| 113 || Scan - slow<br />
|-<br />
| 114 || Scan - quick<br />
|-<br />
| 115 || Scan - fast<br />
|-<br />
| 116 || Scan + slow<br />
|-<br />
| 117 || Scan + quick<br />
|-<br />
| 118 || Scan + fast<br />
|-<br />
| 119 || Tune<br />
|-<br />
| 140 || Short status query<br />
|-<br />
| 210 || Send a *<br />
|-<br />
| 211 || Send a #<br />
|}<br />
<br />
Not all commands above are supported by all radios. For example radios which don't support SSB, would not be able to be placed in LSB or USB mode.<br />
<br />
===Remote Base Login===<br />
When [[#authlevel=|authlevel=]] is greater than zero, remote 99 is used to define a different dtmf sequence for each user authorized to use the remote base. The remote base will announce the callsign as access is granted.<br />
<br />
Sample:<br />
<pre><br />
9139583 = remote,99,WB6NIL,G ; grant access to Jim (general)<br />
9148351 = remote,99,WA6ZFT,E ; grant access to Steve (extra)<br />
</pre><br />
When the remote base is disconnected from the originating node, the<br />
user will be logged out. <br />
<br />
The LICENSETAG argument is used to enforce<br />
tx frequency limits. Need info [txlimits].<br />
<br />
= Settings to name other Stanzas =<br />
Within the node stanza, some key=value pairs point to other stanzas. This allows nodes on the same Asterisk/app_rpt server to have the same settings (without duplicate entries) or different settings in some cases. For example the phone patch command may be *6 on one node, yet *61 on another.<br />
<br />
For example:<br />
[1000]<br />
functions=functionsVHF<br />
<br />
[1001]<br />
functions=functionsVHF<br />
<br />
[1002]<br />
functions=functionsUHF<br />
<br />
[functionsVHF]<br />
; Two meter Autopatch up is *6<br />
6=autopatchup,noct=1,farenddisconnect=1,dialtime=20000 <br />
0=autopatchdn ; Autopatch down<br />
<br />
[functionsUHF]<br />
; 440 Autopatch up is *61<br />
61=autopatchup,noct=1,farenddisconnect=1,dialtime=20000 ; Autopatch up<br />
0=autopatchdn ; Autopatch down<br />
* controlstates=<br />
* functions=<br />
* link_functions=<br />
* macro=<br />
* phone_functions=<br />
* telemetry=<br />
* wait_times=<br />
<br />
=Node Number Stanza=<br />
The node number stanza is the first stanza in rpt.conf. <br />
<br />
<pre><br />
[1999] ; Replace with your assigned node number<br />
</pre><br />
<br />
The node number stanza contains the following key/value pairs. <br />
==althangtime===<br />
This controls the length of the repeater hang time when the alternate hang timer is selected with a control operator function. It is specified in milliseconds. <br />
<br />
Sample:<br />
<pre><br />
althangtime=4000 ; 4 seconds<br />
</pre><br />
==beaconing===<br />
When set to 1 will send the repeater ID at the idtime interval regardless of whether there was repeater activity or not. This feature appears to be required in the UK, but is probably illegal in the US.<br />
<br />
Sample:<br />
<pre><br />
beaconing=1 ;Set to 1 to beacon. Defaults to 0<br />
</pre><br />
==callerid===<br />
This setting allows the autopatch on the node to be identified with a specific caller ID. The default setting is as follows<br />
<br />
<pre><br />
callerid="Repeater" <0000000000><br />
</pre><br />
<br />
''Note'': The value in quotes is the name of the autopatch caller, and the numbers in angle brackets are the originating telephone number to use.<br />
<br />
==context===<br />
<br />
This setting directs the autopatch for the node to use a specific context in extensions.conf for outgoing autopatch calls. The default is to specify a context name of radio.<br />
<br />
<pre><br />
context=radio<br />
</pre><br />
<br />
==controlstates===<br />
This setting defines the name of the [[Structure of Config Files|variable named]] control state stanza. Control states are an optional feature which allows groups of control operator commands to be executed all at once. To use control states, define an entry in your node stanzas to point to a dedicated control state stanza like this:<br />
<pre><br />
controlstates = controlstates ; points to control state stanza<br />
<br />
<br />
[controlstates]<br />
0 = rptena,lnkena,apena,totena,ufena,noicd ; Normal operation <br />
1 = rptena,lnkena,apdis,totdis,ufena,noice ; Net and news operation <br />
2 = rptena,lnkdis,apdis,totena,ufdis,noice ; Repeater only operation<br />
</pre><br />
<br />
The [[#Control States Stanza|control state stanza]] describes these mnemonics.<br />
<br />
==duplex===<br />
The duplex key/value pairs sets the duplex mode for desired radio operation. Duplex mode 2 is the default if none specified.<br />
{| class="wikitable"<br />
! Duplex Mode !! Description <br />
|- <br />
| 0 || Half duplex with no telemetry tones or hang time. Special Case: Full duplex if linktolink is set to yes. This mode is preferred when interfacing with an external multiport repeater controller. Comment out idrecording and idtalkover to suppress IDs.<br />
|-<br />
| 1 || Half duplex with telemetry tones and hang time. Does not repeat audio. This mode is preferred when interfacing a simplex node.<br />
|-<br />
| 2 || Full Duplex with telemetry tones and hang time. This mode is preferred when interfacing a repeater. <br />
|- <br />
| 3 || Full Duplex with telemetry tones and hang time, but no repeated audio.<br />
|- <br />
| 4 || Full Duplex with telemetry tones and hang time. Repeated audio only when the autopatch is down.<br />
|}<br />
<br />
Sample:<br />
<pre><br />
duplex = 0 ; 0 = Half duplex with no telemetry tones or hang time.<br />
</pre><br />
<br />
==endchar===<br />
This setting allows the end character used by some control functions to be changed. By default this is a #. The endchar value must not be the same as the funcchar default or overridden value.<br />
<br />
==erxgain===<br />
Echolink receive gain adjustment in +/- db-volts. Used to balance Echolink recieve audio on an app_rpt node. <br />
<br />
<pre><br />
erxgain = -3<br />
</pre><br />
<br />
See [[:Category:How to|Echolink How to]]<br />
<br />
==etxgain===<br />
Echolink transmit gain adjustment in +/- db-volts. Used to balance Echolink transmit audio on an app_rpt node. <br />
<br />
<pre><br />
etxgain = 3<br />
</pre><br />
<br />
See [[:Category:How to|Echolink How to]]<br />
<br />
==funcchar===<br />
This setting can be used to change the default function starting character of * to something else. Please note that the new value chosen must not be the same as the default or overridden value for endchar=.<br />
<br />
==functions===<br />
This [[Structure of Config Files#Settings to name other Stanzas|names (points to)]] the [[#Functions Stanza|function stanza]].<br />
<br />
Sample:<br />
<pre><br />
functions = functionsUHF ; pointer to 440 repeater functions stanza<br />
</pre><br />
<br />
== GUI ==<br />
{| class="wikitable"<br />
!Key<br />
!Valid Values<br />
!Default<br />
|-<br />
|guilinkdefault<br />
|0 = telemetry output off, 1 = telemetry output on, 2 = timed telemetry output on command execution and for a short time thereafter, 3 = follow local telemetry mode<br />
|1<br />
|-<br />
|guilinkdynamic<br />
|0 = disallow users to change the gui telemetry setting with a COP command, 1 = Allow users to change the setting with a COP command<br />
|1<br />
|}<br />
<br />
= Function Classes =<br />
Function classes are names for categories of functions. There are several function classes defined. They are described in the table below:<br />
{| class="wikitable"<br />
!Class<br />
!Description<br />
|-<br />
|cop<br />
|Control operator commands<br />
|-<br />
|ilink<br />
|Internet linking commands<br />
|-<br />
|status<br />
|User Status Commands<br />
|-<br />
|autopatchup<br />
|Autopatch up commands<br />
|-<br />
|autopatchdn<br />
|Autopatch down commands<br />
|-<br />
|remote<br />
|Remote base commands<br />
|-<br />
|macro<br />
|Command Macros<br />
|}<br />
Most of the above command classes require a function method and possibly one or more additional command parameters. Function methods are discussed next.<br />
<br />
= Function Methods =<br />
Function methods are numbers which identify a specific function to execute within a function class. Function Methods are optional and in some cases should be omitted (Such as with the autopatchup method) A complete and up-to-date description of all functon methods can be found in the app_rpt.c source file. Some function methods are shown below as an example below:<br />
1 - Force ID (global)<br />
2 - Give Time of Day (global)<br />
3 - Give software Version (global)<br />
11 - Force ID (local only)<br />
12 - Give Time of Day (local only)<br />
<br />
= Function Options =<br />
Some Function Methods can take function options. These are specified after the Function Method separated with commas. Not all commands require or take Function options. An example of a method which can accept Function Options is the autopatchup method.<br />
<br />
= Putting it all Together =<br />
A small excerpt from the function stanza of rpt.conf is hown below.<br />
[functions]<br />
1=ilink,1 ; Specific link disconnect<br />
6=autopatchup,noct=1,farenddisconnect=1,dialtime=2000 ; Autopatch up<br />
The above example contains DTMF functions with all of the parameters discussed on previous pages.<br />
<br />
In the above example:<br />
* *1 followed by a node number disconnects a specific link. The function class is ''ilink'' and the function method is ''1''<br />
* *6 followed by a phone number brings up the autopatch with the function options specified. Note that there is no function method defined, but there are function options present.<br />
<br />
==hangtime===<br />
This controls the length of the repeater hang time. It is specified in milliseconds. <br />
<br />
Sample:<br />
<pre><br />
hangtime = 1000 ;Set hang time for 1 second<br />
</pre><br />
<br />
==holdofftelem===<br />
This node stanza configuration key forces all telemetry to be held off until a local user on the receiver or a remote user over a link unkeys. There is one exception to this behavior: When an ID needs to be sent and there is activity coming from a linked node.<br />
<br />
Sample:<br />
<pre><br />
holdofftelem = 1 ;Set to 1 to hold off. Default is 0<br />
</pre><br />
<br />
== telemdefault= ==<br />
<pre><br />
telemdefault = 0 = telemetry output off, 1 = telemetry output on, 2 = timed telemetry output on command execution and for a short time thereafter. Default is 1<br />
</pre><br />
<br />
== telemdynamic= ==<br />
<pre><br />
telemdynamic = 0 = disallow users to change the local telemetry setting with a COP command, 1 = Allow users to change the setting with a COP command. Default is 1<br />
</pre><br />
<br />
==idrecording===<br />
The identifier message is stored in the node stanza using the idrecording key. It can be changed to a different call sign by changing the value to something different. The value can be either a morse code identification string prefixed with |i, or the name of a sound file containing a voice identification message. When using a sound file, the default path for the sound file is /var/lib/asterisk/sounds. <br />
<br />
Sample:<br />
<pre><br />
idrecording = |iwa6zft/r ; Morse Code ID<br />
</pre><br />
or<br />
<pre><br />
idrecording = /var/lib/asterisk/sounds/myid ; Voice ID<br />
</pre><br />
''Note'': ID recording files must have extension gsm,ulaw,pcm, or wav. The extension is left off when it is defined as the example shows above. File extensions are used by Asterisk to determine how to decode the file. All ID recording files should be sampled at 8KHz. See [[Recording Audio Files|Recording audio files]]<br />
<br />
==idtalkover===<br />
The ID talkover message is stored in the node stanza using the idtalkover setting. The purpose of idtalkover is to specify an alternate ID to use when the ID must be sent over the top of a user transmission, This can be a shorter voice ID or an ID in morse code. The value can be either a morse code identification string prefixed with |i, or the name of a sound file containing a voice identification message. When using a sound file, the default path for the sound file is /var/lib/asterisk/sounds. Example usages are as follows:<br />
<br />
Sample:<br />
<pre><br />
idtalkover = |iwa6zft/r ; Morse Code ID<br />
</pre><br />
or<br />
<pre><br />
idtalkover = /var/lib/asterisk/sounds/myid ; Voice ID<br />
</pre><br />
''Note'': ID recording files must have extension gsm,ulaw,pcm, or wav. The extension is left off when it is defined as the example shows above. File extensions are used by Asterisk to determine how to decode the file. All ID recording files should be sampled at 8KHz. See [[Recording Audio Files|Recording audio files]]<br />
<br />
==inxlat===<br />
The inxlat setting allows complete remapping of the funcchar and endchar digits to different digits or digit sequences.<br />
inxlat acts on the digits received by the radio receiver on the node.<br />
<br />
Format: inxlat = funchars,endchars,passchars,dialtone<br />
<br />
where:<br />
<br />
* funcchars is the digit or digit sequence to replace funcchar<br />
* endchars is the digit or digit sequence to replace endchar<br />
* passchars are the digits to pass through (can be used to block certain digits)<br />
* dialtone is optional. Set to Y for dial tone on successful funcchars.<br />
<br />
Sample:<br />
<pre><br />
inxlat = #56,#57,0123456789ABCD ; string xlat from radio port to sys<br />
</pre><br />
<br />
==link_functions===<br />
This [[Structure of Config Files#Settings to name other Stanzas|names (points to)]] the link_functions stanza.<br />
<br />
The link_functions setting directs the node to use a particular function stanza for functions dialed by users accessing the node via a link from another node. The traditional default is to point it to a function stanza named "functions".<br />
<br />
Sample:<br />
<pre><br />
link_functions = functions ; pointer to the Link Function stanza<br />
</pre><br />
<br />
==linkmongain===<br />
Link Monitor Gain adjusts the audio level of monitored nodes when a signal from another node or the local receiver is received. If linkmongain is set to a negative number the monitored audio will decrease by the set amount in db. If linkmongain set to a positive number monitored audio will increase by the set amount in db. The value of linkmongain is in db. The default value is 0 db.<br />
<br />
Sample:<br />
<pre><br />
linkmongain = -20 ; reduce link volume 20dB<br />
</pre><br />
<br />
==linktolink===<br />
When operating in duplex mode 0, this forces the radio interface to operate in full duplex mode, but keeps all the other duplex mode 0 semantics. This is used when a radio interface is connected to a multiport analog repeater controller. The linktolink= key can take two values: yes or no.<br />
<br />
Sample:<br />
<pre><br />
linktolink = yes ; set to yes to enable. Default is no.<br />
</pre><br />
<br />
==linkunkeyct===<br />
The linkunkeyct setting selects the courtesy tone to send when a connected remote node unkeys. The default is no courtesy tone when a remote node unkeys.<br />
<br />
Sample:<br />
<pre><br />
linkunkeyct = ct8 ; use courtesy tone 8<br />
</pre><br />
<br />
==macro===<br />
The marco key/value points to by the [[#Macro Stanza|Macro Stanza]] key/value pair. Macros are DTMF shortcuts. <br />
<br />
Sample:<br />
<pre><br />
macro=macro ; use stanza names 'macros'<br />
<br />
[macro]<br />
1 = *32000*32001 ; connect to nodes 2000 and 2001<br />
</pre><br />
<br />
==nounkeyct===<br />
The nounkeyct node stanza key completely disables the courtesy tone. This is useful for eliminating TX time in applications using simplex uplinks to repeaters on the repeater pair itself. This practice is '''strongly''' discouraged.<br />
<br />
Sample:<br />
<pre><br />
nounkeyct = yes ; :(<br />
</pre><br />
<br />
==politeid===<br />
The politeid setting specified the number of milliseconds prior to the end of the id cycle where the controller will attempt to play the ID in the tail when a user unkeys. If the controller does not get a chance to send the ID in the tail, the ID will be played over the top of the user transmission. Optional, default 30000.<br />
<br />
Sample:<br />
<pre><br />
politeid = 30000 ; 30 seconds<br />
</pre><br />
<br />
==propagate_dtmf===<br />
Takes either yes or no. When set to yes, DTMF will be regenerated from out-of-band signalling or from from the receiver dtmf decoder whenever a function start character is NOT detected and command decoding has not begun. When set to no, no tones will be regenerated. The default for this setting is no.<br />
This setting is meant to be used in conjunction with linktolink, inxlat, and outxlat when interfacing a radio port to a multiport analog repeater controller on an RF-linked system.<br />
<br />
Sample:<br />
<pre><br />
propagate_dtmf = no<br />
</pre><br />
''Note'': There is a separate setting propagate_phonedtmf for use by dial-in (phone and dphone) users.<br />
<br />
==remotect===<br />
The remotect setting allows the selection of the remote linked courtesy tone so that the users can tell there is a [[:Category:Remote Base|remote base]] connected locally.<br />
<br />
Sample:<br />
<pre><br />
remotect = ct3 ; use courtesy tone 3<br />
</pre><br />
<br />
==rxburstfreq===<br />
If rx tone burst operation is desired, specify the frequency in hertz of the desired tone burst. Setting to 0 (or not specifying) indicates no tone burst operation.<br />
<br />
Sample:<br />
<pre><br />
rxburstfreq = 1000<br />
</pre><br />
<br />
==rxburstthreshold===<br />
In rx toneburst mode, specifies the minimum signal to noise ratio in db that qualifies a valid tone.<br />
Defaults to 16 (db).<br />
<br />
==rxbursttime===<br />
For rx toneburst operation, specifies minimum amount of time that tone needs to be valid for recognition (in milliseconds). Defaults to 250.<br />
<br />
==rxchannel===<br />
The rxchannel key/value pair selects the radio interface. There must be one (and only one) rxchannel per node. The selections are: <br />
<br />
{| class="wikitable"<br />
! Value !! Description <br />
|- <br />
| dahdi/pseudo || No radio, used for hubs<br />
|- <br />
| SimpleUSB/usb_1999 || [[Simpleusb.conf|SimpleUSB (limited DSP)]] <br />
|- <br />
| Radio/usb_1999 || [[Usbradio.conf|USBRadio (full DSP)]] <br />
|- <br />
| voter/1990 || [[Voter.conf|RTCM]] <br />
|- <br />
| Pi/1 || Raspberry Pi PiTA <br />
|- <br />
| Dahdi/1 || PCI Quad card <br />
|- <br />
| Beagle/1 || BeagleBoard <br />
|- <br />
| USRP/127.0.0.1:34001:32001 || GNU Radio interface USRP<br />
|}<br />
Sample:<br />
<pre><br />
rxchannel = dahdi/pseudo ; No radio (hub)<br />
</pre><br />
<br />
''Note'': This is selecting what is known as (in Asterisk terminology) the channel driver.<br />
<br />
==scheduler===<br />
This setting defines the scheduler stanza. The scheduler is used to execute commands at a particular time.<br />
<br />
Sample:<br />
<pre><br />
scheduler = schedule ; name scheduler to 'schedule'<br />
<br />
[schedule]<br />
...<br />
</pre><br />
<br />
==sleeptime===<br />
This sets the inactivity period in seconds for no signal on the repeater receiver before the system goes to sleep. <br />
<br />
Sample:<br />
<pre><br />
sleeptime = 300 ; go to sleep after 5 mins of no activity<br />
</pre><br />
<br />
==startup_macro===<br />
The startup_macro is executed once on system startup. Each node can have one startup macro defined in its node stanza.<br />
<br />
Sample:<br />
<pre><br />
startup_macro = *31000*31001*31002 ; Connect to 1000, 1001 and 1002 at startup<br />
</pre><br />
<br />
==tailmessagelist===<br />
The tailmessagelist setting allows a comma separated list of audio files to be specified for the tail message function. The tail messages will rotate from one to the next until the end of the list is reached at which point the first message in the list will be selected. If no absolute path name is specified, the directory var/lib/asterisk/sounds will be searched for the sound file. The file extension should be omitted.<br />
<br />
Sample:<br />
<pre><br />
tailmessagelist = welcome,clubmeeting,wx ; rotate 3 tail messages<br />
</pre><br />
<br />
''Note'': ID recording files must have extension gsm,ulaw,pcm, or wav. The extension is left off when it is defined as the example shows above. File extensions are used by Asterisk to determine how to decode the file. All ID recording files should be sampled at 8KHz. See [[Recording Audio Files|Recording audio files]]<br />
<br />
==tailmessagetime===<br />
This sets the amount of time in milliseconds between tail messages. Tail Messages are played when a user unkeys on the repeater input at the point where the hang timer expires after the courtesy tone is sent.<br />
<br />
Sample:<br />
<pre><br />
tailmessagetime = 900000 ; 15 minutes between tail messages<br />
</pre><br />
<br />
==tailsquashedtime===<br />
If a tail message is "squashed" by a user keying up over the top of it, a separate time value can be loaded to make the tail message be retried at a shorter time interval than the standard tailmessagetime= setting. The tailsquashedtime= setting takes a value in milliseconds.<br />
<br />
Sample:<br />
<pre><br />
tailsquashedtime = 300000 ; 5 minutes<br />
</pre><br />
<br />
==totime===<br />
This defines the time out timer interval. The value is in milliseconds.<br />
<br />
Sample:<br />
<pre><br />
totime = 180000 ; 3 minutes<br />
</pre><br />
<br />
==unlinkedct===<br />
The unlinkedct setting selects the courtesy tone to be used when the system has no remote nodes connected and is operating as a standalone repeater.<br />
<br />
Sample:<br />
<pre><br />
unlinkedct = ct2 ; use courtesy tone 2<br />
</pre><br />
<br />
==wait-times===<br />
Wait-times points to the [[#Wait Times Stanza|Wait Times Stanza]].<br />
<br />
Sample:<br />
<pre><br />
wait-times = wait-times ; name wait-times to 'wait-times'<br />
</pre><br />
<br />
=Functions Stanza=<br />
The functions stanza is a named stanza [[Structure of Config Files#Settings to name other Stanzas|pointed to]] by the [[#functions=|function=]] key/value pair. Functions within this stanza are used to decode DTMF commands when accessing the node from its receiver. This stanza is typically named 'functions'. <br />
<br />
Sample:<br />
<pre><br />
functions = functions ; name the functions stanza 'functions'<br />
<br />
[functions]<br />
...<br />
</pre><br />
See [[#DTMF Commands|DTMF Commands]] for the list of functions available.<br />
<br />
=Link Functions Stanza=<br />
The link functions stanza is a named stanza [[Structure of Config Files#Settings to name other Stanzas|pointed to]] by the [[#link_functions=|link_function=]] key/value pair. Functions within this stanza are used decode DTMF commands when accessing the node via a link from another node. The traditional usage is to point link_functions= to the same stanza as named by [[#functions=|functions=]] thereby having functions from a linked node and from the local node the same.<br />
<br />
Sample:<br />
<pre><br />
functions = functions ; name the functions stanza 'functions'<br />
link_functions = functions ; use the same stanza <br />
<br />
[functions]<br />
...<br />
</pre><br />
If a different set of either limited or more capable functions is desired:<br />
<pre><br />
functions = functions ; name the functions stanza 'functions'<br />
link_functions = my_link_functions ; use a different stanza<br />
<br />
[functions]<br />
...<br />
<br />
[my_link_functions]<br />
...<br />
</pre><br />
See [[#DTMF Commands|DTMF Commands]] for the list of functions available.<br />
<br />
=Phone Functions Stanza=<br />
The phone functions stanza is a named stanza [[Structure of Config Files#Settings to name other Stanzas|pointed to]] by the [[#phone_functions=|phone_function=]] key/value pair. Functions within this stanza are used decode DTMF commands when accessing the node from a telephone. The traditional usage is to point phone_functions= to the same stanza as named by [[#functions=|functions=]] thereby having functions from a phone and from the local node the same. <br />
<br />
Sample:<br />
<pre><br />
functions = functions ; name the functions stanza 'functions'<br />
phone_functions = functions ; use the same stanza <br />
<br />
[functions]<br />
...<br />
</pre><br />
If a different set of either limited or more capable functions is desired:<br />
<pre><br />
functions = functions ; name the functions stanza 'functions'<br />
phone_functions = my_phone_functions ; use a different stanza<br />
<br />
[functions]<br />
...<br />
<br />
[my_phone_functions]<br />
...<br />
</pre><br />
See [[#DTMF Commands|DTMF Commands]] for the list of functions available.<br />
<br />
=Macro Stanza=<br />
The marco stanza is named stanza pointed to by the [[#macro=|macro=]] key/value pair. Macros are DTMF shortcuts. <br />
<br />
Sample:<br />
<pre><br />
macro=macro ; use stanza names 'macros'<br />
<br />
[macro]<br />
1 = *32000*32001 ; connect to nodes 2000 and 2001<br />
</pre><br />
<br />
=Remote Base Stanza=<br />
Here are [[Structure of Config Files|key/value pairs]] required to configure a remote base.<br />
<br />
==authlevel===<br />
The authlevel= key is used to enable or disable login requirements for a remote base.<br />
<br />
* authlevel=0 Disables all access control (not recommended, unsecured)<br />
* authlevel=1 Enables access control, and waits for key up before prompting for the access code<br />
* authlevel=2 Enables access control, and prompts for the access code at the time of connection<br />
<br />
Sample:<br />
<pre><br />
autllevel = 0 ; allow all comers <br />
</pre><br />
<br />
==civaddr===<br />
civaddr= is used with ICOM band radios to set the CIV address. The value is a 2 digit hexadecimal number. If this key is not specified, then the CIV address will be set to the default of 88. <br />
<br />
Sample:<br />
<pre><br />
civaddr = 98 ; set CIV to 98<br />
</pre><br />
<br />
==Remote Base functions===<br />
functions= is a pointer to a remote base function stanza. <br />
<br />
Sample:<br />
<pre><br />
functions = functions-remote ; name the functions stanza 'functions-remote'<br />
<br />
[functions-remote]<br />
...<br />
</pre><br />
<br />
See [[#Remote Base Functions Stanza|Remote Base Functions Stanza]].<br />
<br />
==ioaddr===<br />
ioaddr= refers to a parallel port I/O address. It is specified as a hexadecimal number with a 0x prefix. The parallel port is used when the Doug Hall RBI-1 interface is employed.<br />
<br />
Sample:<br />
<pre><br />
ioaddr = 0x378 ; set RB-1 address<br />
</pre><br />
<br />
==ioport===<br />
ioport= sets the serial port. On Linux Systems, these are typically path names to special files in the /dev directory.<br />
<br />
Sample:<br />
<pre><br />
ioport = /dev/ttyS1 ; Linux com1<br />
</pre><br />
<br />
==Remote Base phone_functions===<br />
phone_functions= is a pointer to a remote base phone function stanza. It is equivalent to phone_functions in the [[#Phone Functions Stanza|Phone Functions Stanza]] but provides a separate set of commands. <br />
<br />
Sample:<br />
<pre><br />
phone_functions = functions-remote<br />
</pre><br />
<br />
==remote===<br />
remote= sets the type of radio. It also ensures that the node will be defined as a remote base node and not a standard node.<br />
<br />
Sample:<br />
<pre><br />
remote = xcat ; set xcat interface<br />
</pre><br />
<br />
{| class="wikitable"<br />
! Radio !! Value !! Comments<br />
|-<br />
| Dumb || y || Use for single channel remote base radios<br />
|-<br />
| FT-897 || ft897 || Must specify serial port using ioport=<br />
|-<br />
| TMG-707 || kenwood || Must specify serial port using ioport=<br />
|-<br />
| IC-706 || ic706 || Must specify serial port using ioport=. Must specify civaddr using civaddr=<br />
|-<br />
| TM-271 || tm271 || Must specify serial port using ioport=<br />
|-<br />
| Syntor Xcat || xcat || Must specify serial port using ioport=. Must specify civaddr using civaddr=<br />
|}<br />
<br />
==remote_inact_timeout===<br />
<br />
Specifies the amount of time without keying from the link. Set to 0 to disable timeout.<br />
<br />
Sample:<br />
<pre><br />
remote_inact_timeout = 0 ; do not time out<br />
</pre><br />
<br />
==remote_timeout===<br />
Session time out for remote base. Set to 0 to disable.<br />
<br />
Sample:<br />
<pre><br />
remote_timeout = 0 ; do not timeout<br />
</pre><br />
<br />
==remote_timeout_warning===<br />
<br />
==remote_timeout_freq===<br />
<br />
==Remote Base rxchannel===<br />
This should contain the name of a usb radio interface which has been defined in [[usbradio.conf]] or a zaptel interface number if using a Quad Radio PCI Card.<br />
<br />
Sample:<br />
<pre><br />
rxchannel = usbRadio/usb1<br />
</pre><br />
<br />
==Sample Remote Configuration==<br />
<pre><br />
[1234]<br />
; Rx audio/signaling channel <br />
rxchannel = Radio/usb<br />
<br />
; Serial port for control<br />
ioport = /dev/ttyS1<br />
<br />
; Radio Type <br />
remote = ft897 <br />
<br />
; Function list from link <br />
functions = functions-remote <br />
<br />
; Function list from phone <br />
phone_functions = functions-remote<br />
<br />
; Authorization level <br />
authlevel = 0 <br />
</pre><br />
<br />
=Nodes Stanza=<br />
The [nodes] stanza is a list of nodes, their IP addresses, port and "NONE" for non-remote base nodes. The nodes stanza is used to identify which node is mapped to which Internet call and to determine the destination to send the call to. If you are using automatic update for Allstar link (public) nodes, no Allstar link nodes should be defined here. Only place a definition for your local nodes, and private (off of allstar link) nodes or nodes behind the same NAT router here.<br />
<br />
Sample:<br />
<pre><br />
[nodes]<br />
1000 = radio@127.0.0.1/1000,NONE ; Private hub on this server<br />
1001 = radio@host.domain.com/1001,NONE ; Private node on another server<br />
2501 = radio@127.0.0.1/2501,NONE ; Public node on this server<br />
2502 = radio@127.0.0.1/2502,NONE ; Another public node on this server<br />
2503 = radio@192.168.1.20:4570/2503,NONE ; Public node behind the same NAT router<br />
</pre><br />
The [nodes] stanza performs a function similar to an OS hosts file. When looking up node information, app_rpt looks in the [nodes] stanza first then searches (what could be called the Allstar DNS) the /var/lib/asterisk/rpt_extnodes file.<br />
<br />
=Telemetry Stanza=<br />
This stanza is named by the telemetry= key/value pair. Telemetry entries can be shared across all nodes on the Asterisk/app_rpt server, or defined for each node. Can be a tone sequence, morse string, or a file as follows:<br />
<br />
* |t - Tone escape sequence:<br />
** Tone sequences consist of 1 or more 4-tuple entries (freq1, freq2, duration, amplitude). Single frequencies are created by setting freq1 or freq2 to zero.<br />
* |m - Morse escape sequence:<br />
**Sends Morse code at the '''telemetry amplitude and telemetry frequency''' as defined in the [morse] section. Follow with an alphanumeric string.<br />
* |i - Morse ID escape sequence:<br />
**Sends Morse code at the '''ID amplitude and ID frequency''' as defined in the [morse] section. Follow with an alphanumeric string.<br />
* Path to sound file:<br />
**Specify the path to a sound file on the server. Do not include file extension.<br />
<br />
Sample:<br />
<pre><br />
[telemetry]<br />
ct1=|t(350,0,100,2048)(500,0,100,2048)(660,0,100,2048)<br />
ct2=|t(660,880,150,2048) <br />
ct3=|t(440,0,150,4096) <br />
ct4=|t(550,0,150,2048)<br />
ct4=|t(2475,0,250,768)<br />
ct5=|t(660,0,150,2048)<br />
ct6=|t(880,0,150,2048)<br />
ct7=|t(660,440,150,2048)<br />
ct8=|t(700,1100,150,2048)<br />
ct9=|t(1633,0,50,1000)(0,0,30,0)(1209,0,50,1000); <br />
;remotetx=|t(1633,0,50,3000)(0,0,80,0)(1209,0,50,3000);<br />
remotetx=|t(880,0,150,2048) <br />
remotemon=|t(1209,0,50,2048) <br />
cmdmode=|t(900,903,200,2048)<br />
functcomplete=|t(1000,0,100,2048)(0,0,100,0)(1000,0,100,2048)<br />
patchup=rpt/callproceeding<br />
patchdown=rpt/callterminated<br />
<br />
What the numbers mean,<br />
(000,000,010,000)<br />
| | | |-------amplitude<br />
| | |-------------duration<br />
| |-------------------Tone 2<br />
|-------------------------Tone 1<br />
<br />
</pre><br />
<br />
=Morse Stanza=<br />
Morse code parameters, these are common to all nodes on a given Asterisk/app_rpt server.<br />
<br />
Sample:<br />
<pre><br />
[morse]<br />
speed = 20 ; Approximate speed in WPM<br />
frequency = 900 ; Morse Telemetry Frequency<br />
amplitude = 4096 ; Morse Telemetry Amplitude<br />
idfrequency = 746 ; Morse ID Frequency <br />
idamplitude = 768 ; Morse ID Amplitude<br />
</pre><br />
<br />
=Wait Times Stanza=<br />
This stanza is named by the [[#wait-times=|wait-times=]] key/value pair. The wait time stanza is used to set delay time between various node actions and their response. Values are in milliseconds.<br />
<br />
Sample:<br />
<pre><br />
wait-times = wait-times ; name the stanza 'wait-times'<br />
<br />
[wait-times] <br />
telemwait = 2000<br />
idwait = 500<br />
unkeywait = 2000<br />
calltermwait = 2000<br />
</pre><br />
<br />
=Remote Base Memory Stanza=<br />
Remote base memories are in the format of:<br />
<br />
memory = rxfreq,plfreq,txpower,offset,tone<br />
<br />
Sample:<br />
<pre><br />
[memory]<br />
00 = 146.580,100.0,m<br />
01 = 147.030,103.5,m+t<br />
02 = 147.240,103.5,m+t<br />
03 = 147.765,79.7,m-t<br />
04 = 146.460,100.0,m<br />
05 = 146.550,100.0,m<br />
</pre><br />
<br />
=Control States Stanza=<br />
<br />
There are several predefined nmemonics (keywords) used in the control state stanza to enable and disable the various features of the controller. These nmemonics correspond to the control operator command to be executed and most of these are the same groups of letters sent back when a single control operator command is executed on the controller.<br />
<br />
{| class="wikitable"<br />
! Nmemonic !! Description !! COP Method<br />
|-<br />
| rptena || Repeater Enable || 2<br />
|-<br />
| rptdis || Repeater Disable || 3<br />
|-<br />
| totena || Timeout Timer Enable || 7<br />
|-<br />
| totdis || Timeout Timer Disable || 8<br />
|-<br />
| apena || Autopatch Enable || 9<br />
|-<br />
| apdis || Autopatch Disable || 10<br />
|-<br />
| lnkena || Link Enable || 11<br />
|-<br />
| lnkdis || Link Disable || 12<br />
|-<br />
| skena || Scheduler Enable || 15<br />
|-<br />
| skdis || Scheduler Disable || 16<br />
|-<br />
| ufena || User Functions Enable || 17<br />
|-<br />
| ufdis || User Functions Disable || 18<br />
|-<br />
| atena || Alternate Hangtime Enable || 19<br />
|-<br />
| atdis || Alternate Hangtime Disable || 20<br />
|-<br />
| noice || No Incoming Connections Enable || 49<br />
|-<br />
| noicd || No Incoming Connections Disable || 50<br />
|-<br />
| slpen || Sleep Mode Enable || 51<br />
|-<br />
| slpds || Sleep Mode Disable || 52<br />
|}<br />
<br />
=Schedule Stanza=<br />
The scheduler can execute commands at certain times. For example for a net on Tuesday nights at 8 PM.<br />
<br />
Sample:<br />
<pre><br />
scheduler=schedule ; name the stanza 'schedule'<br />
<br />
[schedule] <br />
;dtmf_function = m h dom mon dow ; ala cron, star is implied <br />
2 = 00 00 * * * ; at midnight every day, execute macro 2.<br />
</pre><br />
<br />
=DAQ List Stanza=<br />
<br />
=Meter Faces Stanza=<br />
<br />
=Alarms Stanza=<br />
<br />
[[Category:Node Configuration]]<br />
[[Category:Config Files]]</div>N8THNhttps://wiki.pttlink.org/index.php?title=Rpt.conf&diff=1328Rpt.conf2019-01-28T15:14:42Z<p>N8THN: added guilinkdefault and guilinkdynamic</p>
<hr />
<div>Rpt.conf is where the majority of user-facing features, such as the node's CW and voice ID, DTMF commands and timers are set. There is a lot of capability here which can be difficult to grasp. Fortunately the default [https://github.com/AllStarLink/DIAL/blob/master/configs/rpt.conf DIAL rpt.conf] is well commented and will work fine for most node admins. <br />
<br />
=DTMF Commands=<br />
DTMF commands are placed in any one of three [[Structure of Config Files|named stanzas]]. Function stanzas control access to DTMF commands that a user can issue from various <br />
control points.<br />
* The [[#Functions Stanza|fuctions stanza]] - to decode DTMF from the node's local receiver.<br />
* The [[#Link Functions Stanza|link_functions stanza]] - to decode DTMF from linked nodes.<br />
* The [[#Phone Functions Stanza|phone_functions stanza]] - to decode DTMF from telephone connects.<br />
<br />
A function stanza key/value pair has the following format:<br />
<br />
dtmfcommand=functionclass,[functionmethod],[parameters]<br />
Where:<br />
* dtmfcommand is a DTMF digit sequence '''minus''' the [[#funcchar=|start character]] (usually *)<br />
* functionclass is a string which defines what class of command; link, status or COP<br />
* functionmethod defines the optional method number to use in the function class.<br />
* functionoptions are one or more optional comma separated parameters which further define a command.<br />
<br />
==Status Commands==<br />
Status commands (functioncalss 'status') provide general information about the node. <br />
<br />
Sample:<br />
<pre><br />
712 = status,12 ; Give Time of Day (local only)<br />
</pre><br />
<br />
{| class="wikitable"<br />
! Status !! Description<br />
|-<br />
| 1 || Force ID (global)<br />
|-<br />
| 2 || Give Time of Day (global)<br />
|-<br />
| 3 || Give software Version (global)<br />
|-<br />
| 4 || Give GPS location info<br />
|-<br />
| 5 || Speak the last (dtmf) user <br />
|-<br />
| 11 || Force ID (local only)<br />
|-<br />
| 12 || Give Time of Day (local only)<br />
|}<br />
<br />
==Link Commands==<br />
Link commands (functioncalss 'link') connect to, disconnect from, monitor (Rx only) other nodes and give link status. <br />
<br />
Sample:<br />
<pre><br />
3 = ilink,3 ; Connect specified link -- transceive<br />
</pre><br />
<br />
{| class="wikitable"<br />
! ilink !! Description<br />
|-<br />
| 1 || Disconnect specified link<br />
|-<br />
| 2 || Connect specified link -- monitor only<br />
|-<br />
| 3 || Connect specified link -- tranceive<br />
|-<br />
| 4 || Enter command mode on specified link<br />
|-<br />
| 5 || System status<br />
|-<br />
| 6 || Disconnect all links<br />
|-<br />
| 7 || Last Node to Key Up<br />
|-<br />
| 8 || Connect specified link -- local monitor only<br />
|-<br />
| 9 || Send Text Message (9,<destnodeno or 0 (for all)>,Message Text, etc.<br />
|-<br />
| 10 || Disconnect all RANGER links (except permalinks)<br />
|-<br />
| 11 || Disconnect a previously permanently connected link<br />
|-<br />
| 12 || Permanently connect specified link -- monitor only<br />
|-<br />
| 13 || Permanently connect specified link -- tranceive<br />
|-<br />
| 15 || Full system status (all nodes)<br />
|-<br />
| 16 || Reconnect links disconnected with "disconnect all links"<br />
|-<br />
| 17 || MDC test (for diag purposes)<br />
|-<br />
| 18 || Permanently Connect specified link -- local monitor only<br />
|}<br />
<br />
==COP Commands==<br />
Control operator (functionclass 'cop') commands are privileged commands. Node admins may provide some of these to their user community based on personal preference. <br />
<br />
Sample:<br />
<pre><br />
99 = cop,7 ; enable timeout timer<br />
</pre><br />
<br />
Some COP commands can take multiple parameters. For example this COP 48 would send #3#607 on command.<br />
<br />
<pre>900 = cop,48,#,3,#,6,0,7</pre> <br />
<br />
{| class="wikitable"<br />
|-<br />
! COP !! Description<br />
|-<br />
| 1 || System warm boot<br />
|-<br />
| 2 || System enable<br />
|-<br />
| 3 || System disable<br />
|-<br />
| 4 || Test Tone On/Off<br />
|-<br />
| 5 || Dump System Variables on Console (debug)<br />
|-<br />
| 6 || PTT (phone mode only)<br />
|-<br />
| 7 || Time out timer enable<br />
|-<br />
| 8 || Time out timer disable<br />
|-<br />
| 9 || Autopatch enable<br />
|-<br />
| 10 || Autopatch disable<br />
|-<br />
| 11 || Link enable<br />
|-<br />
| 12 || Link disable<br />
|-<br />
| 13 || Query System State<br />
|-<br />
| 14 || Change System State<br />
|-<br />
| 15 || Scheduler Enable<br />
|-<br />
|-<br />
| 16 || Scheduler Disable<br />
|-<br />
| 17 || User functions (time, id, etc) enable<br />
|-<br />
| 18 || User functions (time, id, etc) disable<br />
|-<br />
| 19 || Select alternate hang timer<br />
|-<br />
| 20 || Select standard hang timer <br />
|-<br />
| 21 || Enable Parrot Mode<br />
|-<br />
| 22 || Disable Parrot Mode<br />
|-<br />
| 23 || Birdbath (Current Parrot Cleanup/Flush)<br />
|-<br />
| 24 || Flush all telemetry<br />
|-<br />
| 25 || Query last node un-keyed<br />
|-<br />
| 26 || Query all nodes keyed/unkeyed<br />
|-<br />
| 27 || Reset DAQ minimum on a pin<br />
|-<br />
| 28 || Reset DAQ maximum on a pin<br />
|-<br />
| 30 || Recall Memory Setting in Attached Xcvr<br />
|-<br />
| 31 || Channel Selector for Parallel Programmed Xcvr<br />
|-<br />
| 32 || Touchtone pad test: command + Digit string + # to playback all digits pressed<br />
|-<br />
| 33 || Local Telemetry Output Enable<br />
|-<br />
| 34 || Local Telemetry Output Disable<br />
|-<br />
| 35 || Local Telemetry Output on Demand<br />
|-<br />
| 36 || Foreign Link Local Output Path Enable<br />
|-<br />
| 37 || Foreign Link Local Output Path Disable<br />
|-<br />
| 38 || Foreign Link Local Output Path Follows Local Telemetry<br />
|-<br />
| 39 || Foreign Link Local Output Path on Demand<br />
|-<br />
| 42 || Echolink announce node # only<br />
|-<br />
| 43 || Echolink announce node Callsign only<br />
|-<br />
| 44 || Echolink announce node # & Callsign<br />
|-<br />
| 45 || Link Activity timer enable<br />
|-<br />
| 46 || Link Activity timer disable<br />
|-<br />
| 47 || Reset "Link Config Changed" Flag <br />
|-<br />
| 48 || Send Page Tone (Tone specs separated by parenthesis)<br />
|-<br />
| 49 || Disable incoming connections (control state noice)<br />
|-<br />
| 50 || Enable incoming connections (control state noicd)<br />
|-<br />
| 51 || Enable sleep mode<br />
|-<br />
| 52 || Disable sleep mode<br />
|-<br />
| 53 || Wake up from sleep<br />
|-<br />
| 54 || Go to sleep<br />
|-<br />
| 55 || Parrot Once if parrot mode is disabled<br />
|-<br />
| 56 || Rx CTCSS Enable<br />
|-<br />
| 57 || Rx CTCSS Disable<br />
|-<br />
| 58 || Tx CTCSS On Input only Enable<br />
|-<br />
| 59 || Tx CTCSS On Input only Disable<br />
|-<br />
| 60 || Send MDC-1200 Burst (cop,60,type,UnitID[,DestID,SubCode])<br />
Type is 'I' for PttID, 'E' for Emergency, and 'C' for Call <br />
(SelCall or Alert), or 'SX' for STS (ststus), where X is 0-F.<br />
DestID and subcode are only specified for the 'C' type message.<br />
UnitID is the local systems UnitID. DestID is the MDC1200 ID of<br />
the radio being called, and the subcodes are as follows: <br />
Subcode '8205' is Voice Selective Call for Spectra ('Call')<br />
Subcode '8015' is Voice Selective Call for Maxtrac ('SC') or<br />
Astro-Saber('Call')<br />
Subcode '810D' is Call Alert (like Maxtrac 'CA')<br />
|-<br />
| 61 || Send Message to USB to control GPIO pins (cop,61,GPIO1=0[,GPIO4=1].....)<br />
|-<br />
| 62 || Send Message to USB to control GPIO pins, quietly (cop,62,GPIO1=0[,GPIO4=1].....)<br />
|-<br />
| 63 || Send pre-configred APRSTT notification (cop,63,CALL[,OVERLAYCHR])<br />
|-<br />
| 64 || Send pre-configred APRSTT notification, quietly (cop,64,CALL[,OVERLAYCHR]) <br />
|-<br />
| 65 || Send POCSAG page (equipped channel types only)<br />
|}<br />
<br />
==Remote Base Commands==<br />
Remote base commands (functionclass 'remote') provide remote base control. This stanza is [[Structure of Config Files#Settings to name other Stanzas|named by]] the remote base [[#Remote Base Functions=|Remote Base Functions]] key/value pair.<br />
<br />
{| class="wikitable"<br />
! remote !! Description<br />
|-<br />
| 1 || Retrieve Memory<br />
|-<br />
| 2 || Set freq.<br />
|-<br />
| 3 || Set tx PL tone<br />
|-<br />
| 4 || Set rx PL tone<br />
|-<br />
| 5 || Long status query<br />
|-<br />
| 99,CALLSIGN,LICENSETAG || Remote Base login<br />
|-<br />
| 100 || Rx PL off<br />
|-<br />
| 101 || Rx PL on<br />
|-<br />
| 102 || Tx PL off<br />
|-<br />
| 103 || Tx PL on<br />
|-<br />
| 104 || Low Power<br />
|-<br />
| 105 || Medium Power<br />
|-<br />
| 106 || High Power<br />
|-<br />
| 107 || Bump -20<br />
|-<br />
| 108 || Bump -100<br />
|-<br />
| 109 || Bump -500<br />
|-<br />
| 110 || Bump +20<br />
|-<br />
| 111 || Bump +100<br />
|-<br />
| 112 || Bump +500<br />
|-<br />
| 113 || Scan - slow<br />
|-<br />
| 114 || Scan - quick<br />
|-<br />
| 115 || Scan - fast<br />
|-<br />
| 116 || Scan + slow<br />
|-<br />
| 117 || Scan + quick<br />
|-<br />
| 118 || Scan + fast<br />
|-<br />
| 119 || Tune<br />
|-<br />
| 140 || Short status query<br />
|-<br />
| 210 || Send a *<br />
|-<br />
| 211 || Send a #<br />
|}<br />
<br />
Not all commands above are supported by all radios. For example radios which don't support SSB, would not be able to be placed in LSB or USB mode.<br />
<br />
===Remote Base Login===<br />
When [[#authlevel=|authlevel=]] is greater than zero, remote 99 is used to define a different dtmf sequence for each user authorized to use the remote base. The remote base will announce the callsign as access is granted.<br />
<br />
Sample:<br />
<pre><br />
9139583 = remote,99,WB6NIL,G ; grant access to Jim (general)<br />
9148351 = remote,99,WA6ZFT,E ; grant access to Steve (extra)<br />
</pre><br />
When the remote base is disconnected from the originating node, the<br />
user will be logged out. <br />
<br />
The LICENSETAG argument is used to enforce<br />
tx frequency limits. Need info [txlimits].<br />
<br />
= Settings to name other Stanzas =<br />
Within the node stanza, some key=value pairs point to other stanzas. This allows nodes on the same Asterisk/app_rpt server to have the same settings (without duplicate entries) or different settings in some cases. For example the phone patch command may be *6 on one node, yet *61 on another.<br />
<br />
For example:<br />
[1000]<br />
functions=functionsVHF<br />
<br />
[1001]<br />
functions=functionsVHF<br />
<br />
[1002]<br />
functions=functionsUHF<br />
<br />
[functionsVHF]<br />
; Two meter Autopatch up is *6<br />
6=autopatchup,noct=1,farenddisconnect=1,dialtime=20000 <br />
0=autopatchdn ; Autopatch down<br />
<br />
[functionsUHF]<br />
; 440 Autopatch up is *61<br />
61=autopatchup,noct=1,farenddisconnect=1,dialtime=20000 ; Autopatch up<br />
0=autopatchdn ; Autopatch down<br />
* controlstates=<br />
* functions=<br />
* link_functions=<br />
* macro=<br />
* phone_functions=<br />
* telemetry=<br />
* wait_times=<br />
<br />
=Node Number Stanza=<br />
The node number stanza is the first stanza in rpt.conf. <br />
<br />
<pre><br />
[1999] ; Replace with your assigned node number<br />
</pre><br />
<br />
The node number stanza contains the following key/value pairs. <br />
==althangtime===<br />
This controls the length of the repeater hang time when the alternate hang timer is selected with a control operator function. It is specified in milliseconds. <br />
<br />
Sample:<br />
<pre><br />
althangtime=4000 ; 4 seconds<br />
</pre><br />
==beaconing===<br />
When set to 1 will send the repeater ID at the idtime interval regardless of whether there was repeater activity or not. This feature appears to be required in the UK, but is probably illegal in the US.<br />
<br />
Sample:<br />
<pre><br />
beaconing=1 ;Set to 1 to beacon. Defaults to 0<br />
</pre><br />
==callerid===<br />
This setting allows the autopatch on the node to be identified with a specific caller ID. The default setting is as follows<br />
<br />
<pre><br />
callerid="Repeater" <0000000000><br />
</pre><br />
<br />
''Note'': The value in quotes is the name of the autopatch caller, and the numbers in angle brackets are the originating telephone number to use.<br />
<br />
==context===<br />
<br />
This setting directs the autopatch for the node to use a specific context in extensions.conf for outgoing autopatch calls. The default is to specify a context name of radio.<br />
<br />
<pre><br />
context=radio<br />
</pre><br />
<br />
==controlstates===<br />
This setting defines the name of the [[Structure of Config Files|variable named]] control state stanza. Control states are an optional feature which allows groups of control operator commands to be executed all at once. To use control states, define an entry in your node stanzas to point to a dedicated control state stanza like this:<br />
<pre><br />
controlstates = controlstates ; points to control state stanza<br />
<br />
<br />
[controlstates]<br />
0 = rptena,lnkena,apena,totena,ufena,noicd ; Normal operation <br />
1 = rptena,lnkena,apdis,totdis,ufena,noice ; Net and news operation <br />
2 = rptena,lnkdis,apdis,totena,ufdis,noice ; Repeater only operation<br />
</pre><br />
<br />
The [[#Control States Stanza|control state stanza]] describes these mnemonics.<br />
<br />
==duplex===<br />
The duplex key/value pairs sets the duplex mode for desired radio operation. Duplex mode 2 is the default if none specified.<br />
{| class="wikitable"<br />
! Duplex Mode !! Description <br />
|- <br />
| 0 || Half duplex with no telemetry tones or hang time. Special Case: Full duplex if linktolink is set to yes. This mode is preferred when interfacing with an external multiport repeater controller. Comment out idrecording and idtalkover to suppress IDs.<br />
|-<br />
| 1 || Half duplex with telemetry tones and hang time. Does not repeat audio. This mode is preferred when interfacing a simplex node.<br />
|-<br />
| 2 || Full Duplex with telemetry tones and hang time. This mode is preferred when interfacing a repeater. <br />
|- <br />
| 3 || Full Duplex with telemetry tones and hang time, but no repeated audio.<br />
|- <br />
| 4 || Full Duplex with telemetry tones and hang time. Repeated audio only when the autopatch is down.<br />
|}<br />
<br />
Sample:<br />
<pre><br />
duplex = 0 ; 0 = Half duplex with no telemetry tones or hang time.<br />
</pre><br />
<br />
==endchar===<br />
This setting allows the end character used by some control functions to be changed. By default this is a #. The endchar value must not be the same as the funcchar default or overridden value.<br />
<br />
==erxgain===<br />
Echolink receive gain adjustment in +/- db-volts. Used to balance Echolink recieve audio on an app_rpt node. <br />
<br />
<pre><br />
erxgain = -3<br />
</pre><br />
<br />
See [[:Category:How to|Echolink How to]]<br />
<br />
==etxgain===<br />
Echolink transmit gain adjustment in +/- db-volts. Used to balance Echolink transmit audio on an app_rpt node. <br />
<br />
<pre><br />
etxgain = 3<br />
</pre><br />
<br />
See [[:Category:How to|Echolink How to]]<br />
<br />
==funcchar===<br />
This setting can be used to change the default function starting character of * to something else. Please note that the new value chosen must not be the same as the default or overridden value for endchar=.<br />
<br />
==functions===<br />
This [[Structure of Config Files#Settings to name other Stanzas|names (points to)]] the [[#Functions Stanza|function stanza]].<br />
<br />
Sample:<br />
<pre><br />
functions = functionsUHF ; pointer to 440 repeater functions stanza<br />
</pre><br />
<br />
== GUI ==<br />
{| class="wikitable"<br />
!Key<br />
!Valid Values<br />
!Default<br />
|-<br />
|guilinkdefault<br />
|0 = telemetry output off, 1 = telemetry output on, 2 = timed telemetry output on command execution and for a short time thereafter, 3 = follow local telemetry mode<br />
|1<br />
|-<br />
|guilinkdynamic<br />
|0 = disallow users to change the gui telemetry setting with a COP command, 1 = Allow users to change the setting with a COP command<br />
|1<br />
|}<br />
<br />
= Function Classes =<br />
Function classes are names for categories of functions. There are several function classes defined. They are described in the table below:<br />
{| class="wikitable"<br />
!Class<br />
!Description<br />
|-<br />
|cop<br />
|Control operator commands<br />
|-<br />
|ilink<br />
|Internet linking commands<br />
|-<br />
|status<br />
|User Status Commands<br />
|-<br />
|autopatchup<br />
|Autopatch up commands<br />
|-<br />
|autopatchdn<br />
|Autopatch down commands<br />
|-<br />
|remote<br />
|Remote base commands<br />
|-<br />
|macro<br />
|Command Macros<br />
|}<br />
Most of the above command classes require a function method and possibly one or more additional command parameters. Function methods are discussed next.<br />
<br />
= Function Methods =<br />
Function methods are numbers which identify a specific function to execute within a function class. Function Methods are optional and in some cases should be omitted (Such as with the autopatchup method) A complete and up-to-date description of all functon methods can be found in the app_rpt.c source file. Some function methods are shown below as an example below:<br />
1 - Force ID (global)<br />
2 - Give Time of Day (global)<br />
3 - Give software Version (global)<br />
11 - Force ID (local only)<br />
12 - Give Time of Day (local only)<br />
<br />
= Function Options =<br />
Some Function Methods can take function options. These are specified after the Function Method separated with commas. Not all commands require or take Function options. An example of a method which can accept Function Options is the autopatchup method.<br />
<br />
= Putting it all Together =<br />
A small excerpt from the function stanza of rpt.conf is hown below.<br />
[functions]<br />
1=ilink,1 ; Specific link disconnect<br />
6=autopatchup,noct=1,farenddisconnect=1,dialtime=2000 ; Autopatch up<br />
The above example contains DTMF functions with all of the parameters discussed on previous pages.<br />
<br />
In the above example:<br />
* *1 followed by a node number disconnects a specific link. The function class is ''ilink'' and the function method is ''1''<br />
* *6 followed by a phone number brings up the autopatch with the function options specified. Note that there is no function method defined, but there are function options present.<br />
<br />
==hangtime===<br />
This controls the length of the repeater hang time. It is specified in milliseconds. <br />
<br />
Sample:<br />
<pre><br />
hangtime = 1000 ;Set hang time for 1 second<br />
</pre><br />
<br />
==holdofftelem===<br />
This node stanza configuration key forces all telemetry to be held off until a local user on the receiver or a remote user over a link unkeys. There is one exception to this behavior: When an ID needs to be sent and there is activity coming from a linked node.<br />
<br />
Sample:<br />
<pre><br />
holdofftelem = 1 ;Set to 1 to hold off. Default is 0<br />
</pre><br />
<br />
==idrecording===<br />
The identifier message is stored in the node stanza using the idrecording key. It can be changed to a different call sign by changing the value to something different. The value can be either a morse code identification string prefixed with |i, or the name of a sound file containing a voice identification message. When using a sound file, the default path for the sound file is /var/lib/asterisk/sounds. <br />
<br />
Sample:<br />
<pre><br />
idrecording = |iwa6zft/r ; Morse Code ID<br />
</pre><br />
or<br />
<pre><br />
idrecording = /var/lib/asterisk/sounds/myid ; Voice ID<br />
</pre><br />
''Note'': ID recording files must have extension gsm,ulaw,pcm, or wav. The extension is left off when it is defined as the example shows above. File extensions are used by Asterisk to determine how to decode the file. All ID recording files should be sampled at 8KHz. See [[Recording Audio Files|Recording audio files]]<br />
<br />
==idtalkover===<br />
The ID talkover message is stored in the node stanza using the idtalkover setting. The purpose of idtalkover is to specify an alternate ID to use when the ID must be sent over the top of a user transmission, This can be a shorter voice ID or an ID in morse code. The value can be either a morse code identification string prefixed with |i, or the name of a sound file containing a voice identification message. When using a sound file, the default path for the sound file is /var/lib/asterisk/sounds. Example usages are as follows:<br />
<br />
Sample:<br />
<pre><br />
idtalkover = |iwa6zft/r ; Morse Code ID<br />
</pre><br />
or<br />
<pre><br />
idtalkover = /var/lib/asterisk/sounds/myid ; Voice ID<br />
</pre><br />
''Note'': ID recording files must have extension gsm,ulaw,pcm, or wav. The extension is left off when it is defined as the example shows above. File extensions are used by Asterisk to determine how to decode the file. All ID recording files should be sampled at 8KHz. See [[Recording Audio Files|Recording audio files]]<br />
<br />
==inxlat===<br />
The inxlat setting allows complete remapping of the funcchar and endchar digits to different digits or digit sequences.<br />
inxlat acts on the digits received by the radio receiver on the node.<br />
<br />
Format: inxlat = funchars,endchars,passchars,dialtone<br />
<br />
where:<br />
<br />
* funcchars is the digit or digit sequence to replace funcchar<br />
* endchars is the digit or digit sequence to replace endchar<br />
* passchars are the digits to pass through (can be used to block certain digits)<br />
* dialtone is optional. Set to Y for dial tone on successful funcchars.<br />
<br />
Sample:<br />
<pre><br />
inxlat = #56,#57,0123456789ABCD ; string xlat from radio port to sys<br />
</pre><br />
<br />
==link_functions===<br />
This [[Structure of Config Files#Settings to name other Stanzas|names (points to)]] the link_functions stanza.<br />
<br />
The link_functions setting directs the node to use a particular function stanza for functions dialed by users accessing the node via a link from another node. The traditional default is to point it to a function stanza named "functions".<br />
<br />
Sample:<br />
<pre><br />
link_functions = functions ; pointer to the Link Function stanza<br />
</pre><br />
<br />
==linkmongain===<br />
Link Monitor Gain adjusts the audio level of monitored nodes when a signal from another node or the local receiver is received. If linkmongain is set to a negative number the monitored audio will decrease by the set amount in db. If linkmongain set to a positive number monitored audio will increase by the set amount in db. The value of linkmongain is in db. The default value is 0 db.<br />
<br />
Sample:<br />
<pre><br />
linkmongain = -20 ; reduce link volume 20dB<br />
</pre><br />
<br />
==linktolink===<br />
When operating in duplex mode 0, this forces the radio interface to operate in full duplex mode, but keeps all the other duplex mode 0 semantics. This is used when a radio interface is connected to a multiport analog repeater controller. The linktolink= key can take two values: yes or no.<br />
<br />
Sample:<br />
<pre><br />
linktolink = yes ; set to yes to enable. Default is no.<br />
</pre><br />
<br />
==linkunkeyct===<br />
The linkunkeyct setting selects the courtesy tone to send when a connected remote node unkeys. The default is no courtesy tone when a remote node unkeys.<br />
<br />
Sample:<br />
<pre><br />
linkunkeyct = ct8 ; use courtesy tone 8<br />
</pre><br />
<br />
==macro===<br />
The marco key/value points to by the [[#Macro Stanza|Macro Stanza]] key/value pair. Macros are DTMF shortcuts. <br />
<br />
Sample:<br />
<pre><br />
macro=macro ; use stanza names 'macros'<br />
<br />
[macro]<br />
1 = *32000*32001 ; connect to nodes 2000 and 2001<br />
</pre><br />
<br />
==nounkeyct===<br />
The nounkeyct node stanza key completely disables the courtesy tone. This is useful for eliminating TX time in applications using simplex uplinks to repeaters on the repeater pair itself. This practice is '''strongly''' discouraged.<br />
<br />
Sample:<br />
<pre><br />
nounkeyct = yes ; :(<br />
</pre><br />
<br />
==politeid===<br />
The politeid setting specified the number of milliseconds prior to the end of the id cycle where the controller will attempt to play the ID in the tail when a user unkeys. If the controller does not get a chance to send the ID in the tail, the ID will be played over the top of the user transmission. Optional, default 30000.<br />
<br />
Sample:<br />
<pre><br />
politeid = 30000 ; 30 seconds<br />
</pre><br />
<br />
==propagate_dtmf===<br />
Takes either yes or no. When set to yes, DTMF will be regenerated from out-of-band signalling or from from the receiver dtmf decoder whenever a function start character is NOT detected and command decoding has not begun. When set to no, no tones will be regenerated. The default for this setting is no.<br />
This setting is meant to be used in conjunction with linktolink, inxlat, and outxlat when interfacing a radio port to a multiport analog repeater controller on an RF-linked system.<br />
<br />
Sample:<br />
<pre><br />
propagate_dtmf = no<br />
</pre><br />
''Note'': There is a separate setting propagate_phonedtmf for use by dial-in (phone and dphone) users.<br />
<br />
==remotect===<br />
The remotect setting allows the selection of the remote linked courtesy tone so that the users can tell there is a [[:Category:Remote Base|remote base]] connected locally.<br />
<br />
Sample:<br />
<pre><br />
remotect = ct3 ; use courtesy tone 3<br />
</pre><br />
<br />
==rxburstfreq===<br />
If rx tone burst operation is desired, specify the frequency in hertz of the desired tone burst. Setting to 0 (or not specifying) indicates no tone burst operation.<br />
<br />
Sample:<br />
<pre><br />
rxburstfreq = 1000<br />
</pre><br />
<br />
==rxburstthreshold===<br />
In rx toneburst mode, specifies the minimum signal to noise ratio in db that qualifies a valid tone.<br />
Defaults to 16 (db).<br />
<br />
==rxbursttime===<br />
For rx toneburst operation, specifies minimum amount of time that tone needs to be valid for recognition (in milliseconds). Defaults to 250.<br />
<br />
==rxchannel===<br />
The rxchannel key/value pair selects the radio interface. There must be one (and only one) rxchannel per node. The selections are: <br />
<br />
{| class="wikitable"<br />
! Value !! Description <br />
|- <br />
| dahdi/pseudo || No radio, used for hubs<br />
|- <br />
| SimpleUSB/usb_1999 || [[Simpleusb.conf|SimpleUSB (limited DSP)]] <br />
|- <br />
| Radio/usb_1999 || [[Usbradio.conf|USBRadio (full DSP)]] <br />
|- <br />
| voter/1990 || [[Voter.conf|RTCM]] <br />
|- <br />
| Pi/1 || Raspberry Pi PiTA <br />
|- <br />
| Dahdi/1 || PCI Quad card <br />
|- <br />
| Beagle/1 || BeagleBoard <br />
|- <br />
| USRP/127.0.0.1:34001:32001 || GNU Radio interface USRP<br />
|}<br />
Sample:<br />
<pre><br />
rxchannel = dahdi/pseudo ; No radio (hub)<br />
</pre><br />
<br />
''Note'': This is selecting what is known as (in Asterisk terminology) the channel driver.<br />
<br />
==scheduler===<br />
This setting defines the scheduler stanza. The scheduler is used to execute commands at a particular time.<br />
<br />
Sample:<br />
<pre><br />
scheduler = schedule ; name scheduler to 'schedule'<br />
<br />
[schedule]<br />
...<br />
</pre><br />
<br />
==sleeptime===<br />
This sets the inactivity period in seconds for no signal on the repeater receiver before the system goes to sleep. <br />
<br />
Sample:<br />
<pre><br />
sleeptime = 300 ; go to sleep after 5 mins of no activity<br />
</pre><br />
<br />
==startup_macro===<br />
The startup_macro is executed once on system startup. Each node can have one startup macro defined in its node stanza.<br />
<br />
Sample:<br />
<pre><br />
startup_macro = *31000*31001*31002 ; Connect to 1000, 1001 and 1002 at startup<br />
</pre><br />
<br />
==tailmessagelist===<br />
The tailmessagelist setting allows a comma separated list of audio files to be specified for the tail message function. The tail messages will rotate from one to the next until the end of the list is reached at which point the first message in the list will be selected. If no absolute path name is specified, the directory var/lib/asterisk/sounds will be searched for the sound file. The file extension should be omitted.<br />
<br />
Sample:<br />
<pre><br />
tailmessagelist = welcome,clubmeeting,wx ; rotate 3 tail messages<br />
</pre><br />
<br />
''Note'': ID recording files must have extension gsm,ulaw,pcm, or wav. The extension is left off when it is defined as the example shows above. File extensions are used by Asterisk to determine how to decode the file. All ID recording files should be sampled at 8KHz. See [[Recording Audio Files|Recording audio files]]<br />
<br />
==tailmessagetime===<br />
This sets the amount of time in milliseconds between tail messages. Tail Messages are played when a user unkeys on the repeater input at the point where the hang timer expires after the courtesy tone is sent.<br />
<br />
Sample:<br />
<pre><br />
tailmessagetime = 900000 ; 15 minutes between tail messages<br />
</pre><br />
<br />
==tailsquashedtime===<br />
If a tail message is "squashed" by a user keying up over the top of it, a separate time value can be loaded to make the tail message be retried at a shorter time interval than the standard tailmessagetime= setting. The tailsquashedtime= setting takes a value in milliseconds.<br />
<br />
Sample:<br />
<pre><br />
tailsquashedtime = 300000 ; 5 minutes<br />
</pre><br />
<br />
==totime===<br />
This defines the time out timer interval. The value is in milliseconds.<br />
<br />
Sample:<br />
<pre><br />
totime = 180000 ; 3 minutes<br />
</pre><br />
<br />
==unlinkedct===<br />
The unlinkedct setting selects the courtesy tone to be used when the system has no remote nodes connected and is operating as a standalone repeater.<br />
<br />
Sample:<br />
<pre><br />
unlinkedct = ct2 ; use courtesy tone 2<br />
</pre><br />
<br />
==wait-times===<br />
Wait-times points to the [[#Wait Times Stanza|Wait Times Stanza]].<br />
<br />
Sample:<br />
<pre><br />
wait-times = wait-times ; name wait-times to 'wait-times'<br />
</pre><br />
<br />
=Functions Stanza=<br />
The functions stanza is a named stanza [[Structure of Config Files#Settings to name other Stanzas|pointed to]] by the [[#functions=|function=]] key/value pair. Functions within this stanza are used to decode DTMF commands when accessing the node from its receiver. This stanza is typically named 'functions'. <br />
<br />
Sample:<br />
<pre><br />
functions = functions ; name the functions stanza 'functions'<br />
<br />
[functions]<br />
...<br />
</pre><br />
See [[#DTMF Commands|DTMF Commands]] for the list of functions available.<br />
<br />
=Link Functions Stanza=<br />
The link functions stanza is a named stanza [[Structure of Config Files#Settings to name other Stanzas|pointed to]] by the [[#link_functions=|link_function=]] key/value pair. Functions within this stanza are used decode DTMF commands when accessing the node via a link from another node. The traditional usage is to point link_functions= to the same stanza as named by [[#functions=|functions=]] thereby having functions from a linked node and from the local node the same.<br />
<br />
Sample:<br />
<pre><br />
functions = functions ; name the functions stanza 'functions'<br />
link_functions = functions ; use the same stanza <br />
<br />
[functions]<br />
...<br />
</pre><br />
If a different set of either limited or more capable functions is desired:<br />
<pre><br />
functions = functions ; name the functions stanza 'functions'<br />
link_functions = my_link_functions ; use a different stanza<br />
<br />
[functions]<br />
...<br />
<br />
[my_link_functions]<br />
...<br />
</pre><br />
See [[#DTMF Commands|DTMF Commands]] for the list of functions available.<br />
<br />
=Phone Functions Stanza=<br />
The phone functions stanza is a named stanza [[Structure of Config Files#Settings to name other Stanzas|pointed to]] by the [[#phone_functions=|phone_function=]] key/value pair. Functions within this stanza are used decode DTMF commands when accessing the node from a telephone. The traditional usage is to point phone_functions= to the same stanza as named by [[#functions=|functions=]] thereby having functions from a phone and from the local node the same. <br />
<br />
Sample:<br />
<pre><br />
functions = functions ; name the functions stanza 'functions'<br />
phone_functions = functions ; use the same stanza <br />
<br />
[functions]<br />
...<br />
</pre><br />
If a different set of either limited or more capable functions is desired:<br />
<pre><br />
functions = functions ; name the functions stanza 'functions'<br />
phone_functions = my_phone_functions ; use a different stanza<br />
<br />
[functions]<br />
...<br />
<br />
[my_phone_functions]<br />
...<br />
</pre><br />
See [[#DTMF Commands|DTMF Commands]] for the list of functions available.<br />
<br />
=Macro Stanza=<br />
The marco stanza is named stanza pointed to by the [[#macro=|macro=]] key/value pair. Macros are DTMF shortcuts. <br />
<br />
Sample:<br />
<pre><br />
macro=macro ; use stanza names 'macros'<br />
<br />
[macro]<br />
1 = *32000*32001 ; connect to nodes 2000 and 2001<br />
</pre><br />
<br />
=Remote Base Stanza=<br />
Here are [[Structure of Config Files|key/value pairs]] required to configure a remote base.<br />
<br />
==authlevel===<br />
The authlevel= key is used to enable or disable login requirements for a remote base.<br />
<br />
* authlevel=0 Disables all access control (not recommended, unsecured)<br />
* authlevel=1 Enables access control, and waits for key up before prompting for the access code<br />
* authlevel=2 Enables access control, and prompts for the access code at the time of connection<br />
<br />
Sample:<br />
<pre><br />
autllevel = 0 ; allow all comers <br />
</pre><br />
<br />
==civaddr===<br />
civaddr= is used with ICOM band radios to set the CIV address. The value is a 2 digit hexadecimal number. If this key is not specified, then the CIV address will be set to the default of 88. <br />
<br />
Sample:<br />
<pre><br />
civaddr = 98 ; set CIV to 98<br />
</pre><br />
<br />
==Remote Base functions===<br />
functions= is a pointer to a remote base function stanza. <br />
<br />
Sample:<br />
<pre><br />
functions = functions-remote ; name the functions stanza 'functions-remote'<br />
<br />
[functions-remote]<br />
...<br />
</pre><br />
<br />
See [[#Remote Base Functions Stanza|Remote Base Functions Stanza]].<br />
<br />
==ioaddr===<br />
ioaddr= refers to a parallel port I/O address. It is specified as a hexadecimal number with a 0x prefix. The parallel port is used when the Doug Hall RBI-1 interface is employed.<br />
<br />
Sample:<br />
<pre><br />
ioaddr = 0x378 ; set RB-1 address<br />
</pre><br />
<br />
==ioport===<br />
ioport= sets the serial port. On Linux Systems, these are typically path names to special files in the /dev directory.<br />
<br />
Sample:<br />
<pre><br />
ioport = /dev/ttyS1 ; Linux com1<br />
</pre><br />
<br />
==Remote Base phone_functions===<br />
phone_functions= is a pointer to a remote base phone function stanza. It is equivalent to phone_functions in the [[#Phone Functions Stanza|Phone Functions Stanza]] but provides a separate set of commands. <br />
<br />
Sample:<br />
<pre><br />
phone_functions = functions-remote<br />
</pre><br />
<br />
==remote===<br />
remote= sets the type of radio. It also ensures that the node will be defined as a remote base node and not a standard node.<br />
<br />
Sample:<br />
<pre><br />
remote = xcat ; set xcat interface<br />
</pre><br />
<br />
{| class="wikitable"<br />
! Radio !! Value !! Comments<br />
|-<br />
| Dumb || y || Use for single channel remote base radios<br />
|-<br />
| FT-897 || ft897 || Must specify serial port using ioport=<br />
|-<br />
| TMG-707 || kenwood || Must specify serial port using ioport=<br />
|-<br />
| IC-706 || ic706 || Must specify serial port using ioport=. Must specify civaddr using civaddr=<br />
|-<br />
| TM-271 || tm271 || Must specify serial port using ioport=<br />
|-<br />
| Syntor Xcat || xcat || Must specify serial port using ioport=. Must specify civaddr using civaddr=<br />
|}<br />
<br />
==remote_inact_timeout===<br />
<br />
Specifies the amount of time without keying from the link. Set to 0 to disable timeout.<br />
<br />
Sample:<br />
<pre><br />
remote_inact_timeout = 0 ; do not time out<br />
</pre><br />
<br />
==remote_timeout===<br />
Session time out for remote base. Set to 0 to disable.<br />
<br />
Sample:<br />
<pre><br />
remote_timeout = 0 ; do not timeout<br />
</pre><br />
<br />
==remote_timeout_warning===<br />
<br />
==remote_timeout_freq===<br />
<br />
==Remote Base rxchannel===<br />
This should contain the name of a usb radio interface which has been defined in [[usbradio.conf]] or a zaptel interface number if using a Quad Radio PCI Card.<br />
<br />
Sample:<br />
<pre><br />
rxchannel = usbRadio/usb1<br />
</pre><br />
<br />
==Sample Remote Configuration==<br />
<pre><br />
[1234]<br />
; Rx audio/signaling channel <br />
rxchannel = Radio/usb<br />
<br />
; Serial port for control<br />
ioport = /dev/ttyS1<br />
<br />
; Radio Type <br />
remote = ft897 <br />
<br />
; Function list from link <br />
functions = functions-remote <br />
<br />
; Function list from phone <br />
phone_functions = functions-remote<br />
<br />
; Authorization level <br />
authlevel = 0 <br />
</pre><br />
<br />
=Nodes Stanza=<br />
The [nodes] stanza is a list of nodes, their IP addresses, port and "NONE" for non-remote base nodes. The nodes stanza is used to identify which node is mapped to which Internet call and to determine the destination to send the call to. If you are using automatic update for Allstar link (public) nodes, no Allstar link nodes should be defined here. Only place a definition for your local nodes, and private (off of allstar link) nodes or nodes behind the same NAT router here.<br />
<br />
Sample:<br />
<pre><br />
[nodes]<br />
1000 = radio@127.0.0.1/1000,NONE ; Private hub on this server<br />
1001 = radio@host.domain.com/1001,NONE ; Private node on another server<br />
2501 = radio@127.0.0.1/2501,NONE ; Public node on this server<br />
2502 = radio@127.0.0.1/2502,NONE ; Another public node on this server<br />
2503 = radio@192.168.1.20:4570/2503,NONE ; Public node behind the same NAT router<br />
</pre><br />
The [nodes] stanza performs a function similar to an OS hosts file. When looking up node information, app_rpt looks in the [nodes] stanza first then searches (what could be called the Allstar DNS) the /var/lib/asterisk/rpt_extnodes file.<br />
<br />
=Telemetry Stanza=<br />
This stanza is named by the telemetry= key/value pair. Telemetry entries can be shared across all nodes on the Asterisk/app_rpt server, or defined for each node. Can be a tone sequence, morse string, or a file as follows:<br />
<br />
* |t - Tone escape sequence:<br />
** Tone sequences consist of 1 or more 4-tuple entries (freq1, freq2, duration, amplitude). Single frequencies are created by setting freq1 or freq2 to zero.<br />
* |m - Morse escape sequence:<br />
**Sends Morse code at the '''telemetry amplitude and telemetry frequency''' as defined in the [morse] section. Follow with an alphanumeric string.<br />
* |i - Morse ID escape sequence:<br />
**Sends Morse code at the '''ID amplitude and ID frequency''' as defined in the [morse] section. Follow with an alphanumeric string.<br />
* Path to sound file:<br />
**Specify the path to a sound file on the server. Do not include file extension.<br />
<br />
Sample:<br />
<pre><br />
[telemetry]<br />
ct1=|t(350,0,100,2048)(500,0,100,2048)(660,0,100,2048)<br />
ct2=|t(660,880,150,2048) <br />
ct3=|t(440,0,150,4096) <br />
ct4=|t(550,0,150,2048)<br />
ct4=|t(2475,0,250,768)<br />
ct5=|t(660,0,150,2048)<br />
ct6=|t(880,0,150,2048)<br />
ct7=|t(660,440,150,2048)<br />
ct8=|t(700,1100,150,2048)<br />
ct9=|t(1633,0,50,1000)(0,0,30,0)(1209,0,50,1000); <br />
;remotetx=|t(1633,0,50,3000)(0,0,80,0)(1209,0,50,3000);<br />
remotetx=|t(880,0,150,2048) <br />
remotemon=|t(1209,0,50,2048) <br />
cmdmode=|t(900,903,200,2048)<br />
functcomplete=|t(1000,0,100,2048)(0,0,100,0)(1000,0,100,2048)<br />
patchup=rpt/callproceeding<br />
patchdown=rpt/callterminated<br />
<br />
What the numbers mean,<br />
(000,000,010,000)<br />
| | | |-------amplitude<br />
| | |-------------duration<br />
| |-------------------Tone 2<br />
|-------------------------Tone 1<br />
<br />
</pre><br />
<br />
=Morse Stanza=<br />
Morse code parameters, these are common to all nodes on a given Asterisk/app_rpt server.<br />
<br />
Sample:<br />
<pre><br />
[morse]<br />
speed = 20 ; Approximate speed in WPM<br />
frequency = 900 ; Morse Telemetry Frequency<br />
amplitude = 4096 ; Morse Telemetry Amplitude<br />
idfrequency = 746 ; Morse ID Frequency <br />
idamplitude = 768 ; Morse ID Amplitude<br />
</pre><br />
<br />
=Wait Times Stanza=<br />
This stanza is named by the [[#wait-times=|wait-times=]] key/value pair. The wait time stanza is used to set delay time between various node actions and their response. Values are in milliseconds.<br />
<br />
Sample:<br />
<pre><br />
wait-times = wait-times ; name the stanza 'wait-times'<br />
<br />
[wait-times] <br />
telemwait = 2000<br />
idwait = 500<br />
unkeywait = 2000<br />
calltermwait = 2000<br />
</pre><br />
<br />
=Remote Base Memory Stanza=<br />
Remote base memories are in the format of:<br />
<br />
memory = rxfreq,plfreq,txpower,offset,tone<br />
<br />
Sample:<br />
<pre><br />
[memory]<br />
00 = 146.580,100.0,m<br />
01 = 147.030,103.5,m+t<br />
02 = 147.240,103.5,m+t<br />
03 = 147.765,79.7,m-t<br />
04 = 146.460,100.0,m<br />
05 = 146.550,100.0,m<br />
</pre><br />
<br />
=Control States Stanza=<br />
<br />
There are several predefined nmemonics (keywords) used in the control state stanza to enable and disable the various features of the controller. These nmemonics correspond to the control operator command to be executed and most of these are the same groups of letters sent back when a single control operator command is executed on the controller.<br />
<br />
{| class="wikitable"<br />
! Nmemonic !! Description !! COP Method<br />
|-<br />
| rptena || Repeater Enable || 2<br />
|-<br />
| rptdis || Repeater Disable || 3<br />
|-<br />
| totena || Timeout Timer Enable || 7<br />
|-<br />
| totdis || Timeout Timer Disable || 8<br />
|-<br />
| apena || Autopatch Enable || 9<br />
|-<br />
| apdis || Autopatch Disable || 10<br />
|-<br />
| lnkena || Link Enable || 11<br />
|-<br />
| lnkdis || Link Disable || 12<br />
|-<br />
| skena || Scheduler Enable || 15<br />
|-<br />
| skdis || Scheduler Disable || 16<br />
|-<br />
| ufena || User Functions Enable || 17<br />
|-<br />
| ufdis || User Functions Disable || 18<br />
|-<br />
| atena || Alternate Hangtime Enable || 19<br />
|-<br />
| atdis || Alternate Hangtime Disable || 20<br />
|-<br />
| noice || No Incoming Connections Enable || 49<br />
|-<br />
| noicd || No Incoming Connections Disable || 50<br />
|-<br />
| slpen || Sleep Mode Enable || 51<br />
|-<br />
| slpds || Sleep Mode Disable || 52<br />
|}<br />
<br />
=Schedule Stanza=<br />
The scheduler can execute commands at certain times. For example for a net on Tuesday nights at 8 PM.<br />
<br />
Sample:<br />
<pre><br />
scheduler=schedule ; name the stanza 'schedule'<br />
<br />
[schedule] <br />
;dtmf_function = m h dom mon dow ; ala cron, star is implied <br />
2 = 00 00 * * * ; at midnight every day, execute macro 2.<br />
</pre><br />
<br />
=DAQ List Stanza=<br />
<br />
=Meter Faces Stanza=<br />
<br />
=Alarms Stanza=<br />
<br />
[[Category:Node Configuration]]<br />
[[Category:Config Files]]</div>N8THNhttps://wiki.pttlink.org/index.php?title=Echolink_Channel_Driver&diff=1327Echolink Channel Driver2019-01-28T15:07:18Z<p>N8THN: added Node stanza section from drupal site</p>
<hr />
<div>The chan_echolink channel driver allows AllStar nodes to register on and communicate with the EchoLink network. The following information is originally from [http://docs.allstarlink.org/drupal/node/12 echolink.conf].<br />
<br />
=echolink.conf=<br />
With the addition of the chan_echolink Asterisk channel driver direct connections to and from echolink to Asterisk/app_rpt are now supported. No other programs (e.g. rtpDir, or the link box) are required. With chan_echolink, EchoLink nodes become part of the AllStar link number space.<br />
<br />
From an app_rpt/Allstar node, Echolink connections look just like Allstar/App_rpt connections except the Echolink node numbers have been prefixed with a 3 and padded out to 7 digits with leading zeroes. For instance, if you want to connect to Echolink node 1234 on your app_rpt system you would dial *3 followed by 3001234. If you have a 6 digit Echolink node number 123456, you would dial *3 followed by 3123456. As you can see we have reserved Allstar node numbers with a leading 3 for the Echolink number space.<br />
<br />
For users originating from an Echolink node using Echolink supplied software, nothing changes for them, they just dial the 4 or 6 digit Echolink node number assigned to your app_rpt system and they get connected!<br />
<br />
==Setup==<br />
First, if you are behind a NAT router, please make sure the ports for Echolink service are correctly forwarded to your asterisk system. <br />
<br />
{| class="wikitable"<br />
! Port To Forward !! Service<br />
|-<br />
| 5198 || UDP<br />
|-<br />
| 5199 || UDP<br />
|-<br />
| 5200 || TCP<br />
|}<br />
<br />
Additionally, if you are running a firewall and not a consumer grade router which is configured to limit outbound access to a specific number of ports, you must enable UDP outbound access for 5198, and 5199, and TCP outbound access for port 5200. <br />
<br />
Current documentation on what ports need to be forwarded can be found on echolink.org in the [http://echolink.org/firewall-friendly.htm EchoLink, Firewalls, and Routers] section.<br />
<br />
To activate the Echolink channel driver, all that's required is a properly formatted configuration file. A base configuration file has been included with Both ACID and Limey Linux and is located in /usr/src/configs/examples/echolink. Copy this file to /etc/asterisk, and edit it to match your callsign, password and node number assignment from Echolink.org. The sample echolink.conf file is as follows:<br />
<br />
<pre><br />
[el0]<br />
confmode=no ; Conference mode<br />
call=W6ABC-R ; Change this to your callsign!<br />
pwd=XXXXX ; Change this to your password!<br />
name=echolinkusername ; Change this to your real name!<br />
qth=echolink-location ; Change this to your actual QTH!<br />
email=foo@bar.com ; Change this to your echolink registered email!<br />
maxstns=20 ; The maximum 'at-once' connections allowed/supported (see ** below)<br />
node=123456 ; Change this to the assigned 'ECHOLINK' node# <br />
astnode=2345 ; Change this to your active Allstar node number!<br />
context=radio-secure ; The allstar context (leave the default unless you have good reason to change)<br />
server1=server1.echolink.org<br />
server2=server2.echolink.org <br />
server3=server3.echolink.org<br />
rtcptimeout=10<br />
recfile=/tmp/recorded.gsm<br />
freq=145.000 ; Freq in MHz<br />
tone=100.0 ; CTCSS Tone (0 for none)<br />
lat=34.74978 ; Latitude in decimal degrees<br />
lon=-92.27666 ; Longitude in decimal degrees<br />
power=0 ; 0=0W, 1=1W, 2=4W, 3=9W, 4=16W, 5=25W, 6=36W, 7=49W, 8=64W, 9=81W (Power in Watts)<br />
height=0 ; 0=10' ,1=20',2=40',3=80' ,4=160' ,5=320' ,6=640' ,7=1280',8=2560',9=5120' (AMSL in Feet)<br />
gain=7 ; Gain in db (0-9)<br />
dir=0 ; 0=omni, 1=45deg, 2=90deg, 3=135deg, 4=180deg, 5=225deg, 6=270deg, 7=315deg, 8=360deg (Direction)<br />
</pre><br />
<br />
** How many stations will your node support ? The 2 most particular factors will be how much CPU/Memory power you have<br />
AND how much bandwidth you have available. So you should not expect a bunch from cpu's under 1ghz or from memory below 1gb.<br />
<br />
Once you have made the changes, restart Asterisk, and within a few minutes time, the node should show up on the echolink.org website under [http://echolink.org Current Logins].<br />
<br />
== Node Stanza Keys ==<br />
{| class="wikitable"<br />
!Key<br />
!Valid Values<br />
!Default<br />
|-<br />
|eannmode<br />
|0 = do not announce Echolink nodes at all, 1 = announce only the node number (Allstar-translated), 2 = announce only the call of the echolink station, 3 = announce both<br />
|1<br />
|-<br />
|echolinkdefault<br />
|0 = telemetry output off, 1 = telemetry output on, 2 = timed telemetry output on command execution and for a short time thereafter, 3 = follow local telemetry mode<br />
|2<br />
|-<br />
|echolinkdynamic<br />
|0 = disallow users to change current echolink telemetry setting with a COP command, 1 = Allow users to change the setting with a COP command<br />
|1<br />
|}<br />
<br />
[[Category:Node Configuration]]<br />
[[Category:Config Files]]<br />
<br />
==Controlling Access==<br />
Echolink connections may be denied on a per-callsign basis. This is done by using the deny and permit key values in the above [el0] stanza. The default is to allow all connections if the permit and deny keywords are not present. If a permit is specified, then only the callsigns specified in the permit statement will be allowed to connect. If deny is specified, then the callsign(s) specified will be denied access and the connection will be terminated. Commas are used to delimit multiple callsigns for permit and deny keys. Wildcards are supported so that whole classes of connections can be rejected. Examples:<br />
<br />
Examples:<br />
<br />
To deny w6xxx you would add the statement: '''deny=w6xxx'''<br />
<br />
To prohibit computer-based connections you would write: '''permit=*-*'''<br />
<br />
To allow access to only a select group of callsigns: '''permit=w6abc,w6def,...'''<br />
<br />
==Setting Audio Levels==<br />
The audio gain going to and coming from the Echolink system may be set from within a Node Stanza as follows:<br />
<br />
<pre><br />
erxgain=-3.0 ; defaults to -3.0 db<br />
etxgain=3.0 ; defaults to 3.0 db.<br />
</pre><br />
<br />
=Debugging=<br />
The chan_echolink driver supports debugging output. <br />
<br />
Debugging can be a activated with the command '''echolink debug level x''' (Where x = 0-7. 0=off). With debugging turned on, chan_echolink will output various messages to the terminal related to connecting to nodes, etc.<br />
<br />
In addition to turning on debugging, you can use the following commands to query your node's copy of the EchoLink database:<br />
{| class="wikitable"<br />
! Description !! Command<br />
|-<br />
| Dump EchoLink database || echolink dbdump<br />
|-<br />
| Query EchoLink station by callsign || echolink dbget callsign <EchoLink Callsign> (i.e., KG7QIN-R)<br />
|-<br />
| Query EchoLink station by nodename || echolink dbget nodename <EchoLink node number> (i.e., 407301)<br />
|-<br />
| Query EchoLink station by ip address || echolink dbget ip <EchoLink node ip address><br />
|}<br />
=Miscellaneous=<br />
==Connectivity Issues==<br />
When debugging EchoLink connectivity issues with your AllStar node, remember the following:<br />
*Never run the EchoLink application from your mobile device (cell phone/tablet/etc) using the '''same network''' as your AllStar node. This will lead to problems with one or the other not being able to connect to/register/use the EchoLink servers or other EchoLink nodes. (This also applies to running the Windows application on the same network as your AllStar node).<br />
*If using the EchoLink application on your mobile device (cell phone/tablet/etc), make sure that the EchoLink application is '''not set to run/is not running in the background'''. Having the application running in the background can cause problems with your AllStar node not being able to connect to/register/use the EchoLink servers or other EchoLink nodes.<br />
<br />
<pre><br />
Note: Same network refers to the the Public IP address that both your AllStar node AND the device running the EchoLink application are using -- even if they are on different subnets internally. The Public IP is what the EchoLink servers/network sees and uses when communicating with your node/device.<br />
</pre><br />
<br />
==Caveats==<br />
The chan_echolink driver currently:<br />
<br />
* Does not send its station info.<br />
* Does not process chat text.<br />
* Only recognizes a few remote text commands.<br />
* Does not have a busy, deaf or mute feature.<br />
* Does not have capacity limits.<br />
* Does not have a banned or private station list. ''(Access controls are rudimentary and on a per station basis. See [[Echolink_Channel_Driver#Controlling_Access|Controlling Access]])''<br />
* Does not have an admin list, only local 127.0.0.1 access.<br />
* Does not have a customizable welcome text message.<br />
* Does not support login or connect timeouts.<br />
* Does not have a max TX time limit.<br />
* Does not support activity reporting.<br />
* Does not have event notifications.<br />
* Does not have any stats.<br />
* Does not have any callsign prefix restrictions.<br />
* Does not announce on connects/disconnects. ''(Connect/disconnect announcements come from app_rpt's telemetry using the 3xxxxxx node number format)''<br />
* Does not have any loop detection.<br />
* Allows "doubles" (newer version of the software are preventing this. Work in progress)<br />
<br />
==Remote Commands==<br />
The following '''''remote text commands''''' can be sent to the chan_echolink driver running on your AllStar link node using ''netcat'':<br />
<br />
{| class="wikitable"<br />
! Command !! Function<br />
|-<br />
| o.conip <IPaddress> || Request a connect<br />
|-<br />
| o.dconip <IPaddress> || Request a disconnect<br />
|-<br />
| o.rec || Turn on/off recording<br />
|}<br />
<br />
[[Category:Node Configuration]]</div>N8THNhttps://wiki.pttlink.org/index.php?title=Standard_Node_vs_Remote_Base&diff=1326Standard Node vs Remote Base2019-01-28T14:30:27Z<p>N8THN: added content</p>
<hr />
<div>=== Specifying a Standard Node and a Remote Base Node in rpt.conf ===<br />
In the '''nodes stanza''', a remote base node is denoted when it is suffixed with a y option:<br />
[nodes] <br />
1234 = radio@127.0.0.1/1234,NONE,y ; Remote base node <br />
5678 = radio@127.0.0.1/5678,NONE ; Standard node<br />
In the above example node 1234 is a remote base node, and node 5678 is a standard node.<br />
[[Category:How to]]</div>N8THNhttps://wiki.pttlink.org/index.php?title=Standard_Node_vs_Remote_Base&diff=1325Standard Node vs Remote Base2019-01-28T14:29:25Z<p>N8THN: created page</p>
<hr />
<div>[[Category:How to]]</div>N8THNhttps://wiki.pttlink.org/index.php?title=Whats_Required&diff=1324Whats Required2019-01-28T14:16:11Z<p>N8THN: </p>
<hr />
<div>[[Category:How to]]<br />
In order to deploy a remote base node, the following items will be required:<br />
# An assigned dedicated node number (e.g. allstarlink.org)<br />
# A radio interface<br />
# A radio interface cable<br />
# A supported radio<br />
# A new or existing PC host computer<br />
<br />
=== Requesting an Allstar Node Number for a Remote Base ===<br />
Remote base nodes must be specifically requested from <nowiki>http://allstarlink.org</nowiki>. When requesting a remote base node, check the box Rem. Base, and if the remote base is frequency agile, check the box Freq. Agile.<br />
<br />
=== Radio Interface ===<br />
A free port on a radio interface such as the Quad Radio PCI card, or the URI adapter must be made available for use by the remote base<br />
<br />
=== Radio Interface Cable ===<br />
A radio Interface cable must be constructed to interface the Radio to the Radio Interface. Links to schematics for a few of these cables are at the end of this book.<br />
<br />
=== Supported Radios ===<br />
This is a list of remote base radios which are currently supported in app_rpt:<br />
# Dumb (Any radio, with no remote tuning capability)<br />
# Kenwood TMG-707A<br />
# Kenwoood TM-271<br />
# Yaesu FT-897D<br />
# Icom IC-706<br />
<br />
=== Host Computer ===<br />
Any PC running ACID or Limey Linux with a spare PCI Slot for the Quad Radio PCI card, or a spare USB port for the URI.<br />
[[Category:Obsolete]]</div>N8THNhttps://wiki.pttlink.org/index.php?title=Whats_Required&diff=1323Whats Required2019-01-28T14:15:26Z<p>N8THN: created page</p>
<hr />
<div>[[Category:How to]]</div>N8THNhttps://wiki.pttlink.org/index.php?title=RTCM_Client&diff=1322RTCM Client2019-01-28T14:11:39Z<p>N8THN: Added Voter Buffer section</p>
<hr />
<div>The Radio Thin Client Module (RTCM) is commercially available hardware for interfacing radios to an AllStarLink computer.<br />
<br />
The Micro-Node RTCM and VOTER interfaces are typically used with AllStar in voting/simulcast applications. They MAY be used for ANY repeater interface application, through the chan_voter channel driver. The VOTER is the original through-hole board designed by Jim Dixon for this application. It is open-source, and the relevant Gerber files and BoM to build it are available. The [http://www.micro-node.com/thin-m1.shtml Micro-Node Radio Thin Client Module (RTCM)] is the commercial version of the VOTER. It uses surface mount parts (SMT), but is functionally equivalent to the original VOTER. In general, the two terms (RTCM/VOTER) are used interchangeably, as they operate the same, and use the same firmware (mostly, see below).<br />
<br />
This page will highlight some of the operational concerns, quirks, bugs, and other items of interest that relate to these interfaces. Much of the information has been gleaned off the AllStar mail list, comes from personal experience, or comes from notes in the firmware source code.<br />
<br />
=Testing=<br />
RTCM's come preconfigured to login to [http://voter-demo-allstarlink.org voter-demo-allstarlink.org] for out of the box testing.<br />
<br />
=Factory Reset=<br />
A factory reset can be performed by setting SW 1 down and then applying power to the RTCM. Wait for the green LED to stop blinking, power off and set SW 1 back up. <br />
<br />
=Firmware=<br />
The firmware in the RTCM and VOTER is the same, except it is compiled for the specific dsPIC that is installed in each. As such, the firmware is specific to the VOTER or the RTCM, and is NOT interchangeable (it won't boot in the wrong device). Firmware for the RTCM is denoted by "smt" in the filename.<br />
<br />
<br />
The VOTER uses a dsPIC33FJ128GP802 and the RTCM uses a dsPIC33FJ128GP804.<br />
<br />
<br />
There are '''two parts''' to the firmware, a bootloader, and then the actual firmware file. The bootloader starts when power is applied, and allows you to talk to the dsPIC and load new firmware files over ethernet. If the bootloader is not intercepted by the loading tool, it will continue to boot the current firmware file.<br />
<br />
<br />
All new boards will need to have the bootloader installed first, followed by a firmware file. You '''can''' load a firmware file directly (.hex) in to the dsPIC, but then you will not have any of the bootloader remote loading features.<br />
<br />
<br />
The current bootloader (.cof file) is available here: https://github.com/AllStarLink/voter/tree/master/voter-bootloader (the -smt file is for the RTCM). It needs to be loaded with a PICKit programmer.<br />
<br />
<br />
Current firmware (.cry file) is available here: https://github.com/AllStarLink/voter/tree/master/board-firmware . They are loaded with the EBLEX C30 Programmer.<br />
<br />
<br />
There are multiple "flavors" of firmware available. See below for further explanation of what all the options mean.<br />
<br />
<br />
The DSPBEW versions have Jim's DSP/BEW feature enabled. Note that due to the size of this feature, the diagnostics menu is NOT available in this version.<br />
<br />
<br />
The CHUCK versions have Chuck Henderson's RSSI and Squelch modifications enabled. This is probably the version that most user's will want to use in production.<br />
<br />
<br />
==Compiling Environment==<br />
If you look in the [https://github.com/AllStarLink/voter/blob/master/votersystem.pdf votersystem.pdf], you will find a procedure to modify and load the bootloader in to the dsPIC of a VOTER board. <br />
<br />
<br />
Unfortunately, there is an important step '''missing''' in that procedure, which is covered below.<br />
<br />
<br />
In addition, the old links for the MPLAB software are dead, so let's update this info and get you going.<br />
<br />
<br />
Currently (Feb 2017), you can get the required software from:<br />
:http://www.microchip.com/development-tools/downloads-archive<br />
<br />
<br />
Download MPLAB IDE 32-bit Windows v8.66:<br />
:http://ww1.microchip.com/downloads/en/DeviceDoc/MPLAB_IDE_v8_66.zip<br />
:http://dvswitch.org/files/AllStarLink/Voter/MPLAB_IDE_v8_66.zip<br />
<br />
<br />
Download MPLAB C Compiler for PIC24 and dsPIC DSCs v3.31 '''NOT v.3.25''':<br />
:http://ww1.microchip.com/downloads/en/DeviceDoc/mplabc30-v3_31-windows-installer.exe<br />
:http://dvswitch.org/files/AllStarLink/Voter/mplabc30-v3_31-windows-installer.exe<br />
<br />
<br />
Optionally, install Windows Virtual PC and XP Mode. This is getting to be pretty old software, so running it under XP Mode may be a good idea, so we can keep it isolated (install it in a virtual machine). It does run fine in Windows 7.<br />
<br />
<br />
To setup the compile/build environment, follow these steps:<br />
*Run the MPLAB IDE installer. You don't need to install the HI-TECH C Compiler at the end (click no)<br />
*Run the MPLAB C Compiler installer<br />
*Select Legacy Directory Name<br />
*'''Select Lite Compiler'''<br />
*Go to: https://github.com/AllStarLink<br />
*Follow the links to: voter --> Clone or Download --> Download Zip. That will get you voter-master.zip which is a download of the whole VOTER tree from GitHub.<br />
*Extract it somewhere (ie. in the XP Mode Virtual PC)<br />
*Launch the MPLAB IDE<br />
*Go to Configure --> Settings --> Projects and de-select one-to-one project mode.<br />
<br />
<br />
==Bootloader==<br />
If you need to load the bootloader in to a fresh board, you will need to follow these steps:<br />
*Go to Project --> Open --> voter-bootloader.mcp --> Open (it is in the voter-bootloader folder of the GitHub source)<br />
*Go to File --> Import --> voter-bootloader --> ENC_C30.cof --> Open '''This step is missing from the original procedure.'''<br />
*Remove JP7 on the VOTER Board. This is necessary to allow programming by the PICKit2/PICKit3 device.<br />
*Attach the PICKIT2/PICKit3 device to J1 on the VOTER board. Note that Pin 1 is closest to the power supply modules (as indicated on the board).<br />
*If you have not already selected a programming device, go to Programmer --> Select Device and choose PICKit3 (or PICKit2, depending on what you are using).<br />
*Go to Programmer --> Program. This will program the bootloader firmware into the PIC device on the board.<br />
<br />
<br />
If you want to change the default IP address from 192.168.1.11 in the bootloader:<br />
*Select View --> Program Memory (from the top menu bar)<br />
*Hit Control-F (to "find") and search for the digits "00A8C0".<br />
*These should be found at memory address "03018".<br />
<br />
<br />
The "A8C0" at 03018 represents the hex digits C0 (192) and A8 (168) which are the first two octets of the IP address. The six digits to enter are 00 then the SECOND octet of the IP address in hex then the FIRST octet of the IP address in hex.<br />
<br />
<br />
The "0B01" at 0301A represents the hex digits 0B (11) and 01 (1) which are the second two octets of the IP address. The six digits to enter are 00 then the FOURTH octet of the IP address in hex then the THIRD octet of the IP address in hex.<br />
<br />
<br />
Once you have modified the address to your desired IP, follow the programming procedure (above).<br />
<br />
<br />
==Firmware==<br />
To compile the firmware (if you want to make custom changes):<br />
*Go to Project --> Open --> navigate to board-firmware and open the .mcp file for the flavor of firmware you want to compile. They are in the board-firmware folder of the GitHub source.<br />
*'''NOTE''': the .mcp files with the "smt" suffix are for the RTCM (built with SMT parts). The non-smt files are for the ORIGINAL through-hole VOTER boards. The difference is that the VOTER uses a dsPIC33FJ128GP802 and the RTCM uses a dsPIC33FJ128GP804.<br />
*Go to Project --> Build Configuration and select "Release". This may not be necessary (I don't believe that option is used in the firmware), but it removes the compiler option of __DEBUG being passed, so theoretically it would build "normal" firmware.<br />
*Go to Configure --> Select Device and choose the appropriate device for your board from the Device list. If you don't select the right one, the board will not boot. Select dsPIC33FJ128GP802 for the VOTER, and dsPIC33FJ128GP804 for the RTCM.<br />
*Now, if you go to Project --> Build All it should compile everything and show you "Build Succeeded".<br />
<br />
<br />
A .cry file should be in the board-firmware folder. You can load this with the ENC Loader.<br />
<br />
<br />
There is also a .hex file in there that you could load with a programmer... but that would wipe the bootloader... so don't do that.<br />
<br />
<br />
==Chuck Squelch==<br />
If you want to enable "Chuck Squelch", open the HardwareProfile.h and un-comment #define CHUCK. <br />
<br />
<br />
You may also want to go down to Line 291 in Voter.c (right click on the window, go to Properties --> "C" File Types --> Line Numbers) and tack on CHUCK after 1.60 (the current version number) so that when you load this firmware, the version will be shown as 1.51CHUCK, and you'll know that Chuck Squelch is compiled in. We should probably make that more automagic in the future...<br />
<br />
<br />
==DSP/BEW==<br />
If you want to compile the DSPBEW version, open the DSPBEW project file instead.<br />
<br />
<br />
=DSP/BEW Firmware Version=<br />
DSP BEW Firmware is mutually exclusive with the diagnostic menu. There is not enough space for both, if you load the DSP/BEW firmware, you will '''NOT''' have a diag menu.<br />
<br />
<br />
BEW stands for Baseband Examination Window.<br />
<br />
Typically, the discriminator of an FM communications receiver produces results containing audio spectrum from the "sub-audible" range (typically < 100 Hz) to well above frequencies able to be produced by modulating audio. These higher frequencies can be utilized to determine signal quality, since they can only contain noise (or no noise, if a sufficiently strong signal is present).<br />
<br />
<br />
For receivers (such as the Motorola Quantar, etc) that do not provide sufficient spectral content at these "noise" frequencies (for various reasons), The "DSP/BEW (Digital Signal Processor / Baseband Examination Window)" feature of the RTCM firmware may be utilized. <br />
<br />
<br />
These receivers are perfectly capable of providing valid "noise" signal with no modulation on the input of the receiver, but with strong modulation (high frequency audio and high deviation), it severely interferes with proper analysis of signal strength.<br />
<br />
<br />
This feature provides a means by which a "Window" of baseband (normal audio range) signal is examined by a DSP and a determination of whether or not sufficient audio is present to cause interference of proper signal strength is made. During the VERY brief periods of time when it is determined that sufficient audio is present to cause interference, the signal strength value is "held" (the last valid value previous to the time of interference) until such time that the interfering audio is no longer present. <br />
<br />
<br />
The DSP/BEW feature is selectable, and '''should not''' be used for a receiver that does not need it.<br />
<br />
<br />
A note on the Motorola SLR5700 per VE7FET. DSP/BEW definitely makes a difference on what AllMon reports for the signal strength of received signals. It is less reactive when DSP/BEW = 1 than with it set to 0. We'll have to see what the real world trials show. It might be better to leave it off.<br />
<br />
<br />
=Chuck Squelch=<br />
"Chuck Squelch" are a couple firmware changes made by Chuck Henderson, WB9UUS.<br />
<br />
<br />
Pre-compiled firmware versions including this option are available on [https://github.com/AllStarLink/voter/tree/master/board-firmware GitHub]. See above on how it is enabled/compiled, if you are rolling your own firmware modifications.<br />
<br />
<br />
One of the changes fixes an issue with weak signals producing RSSI readings all over the place. It is caused by a 16 bit value that was overflowing (it is the RSSI change in the firmware). It results in rock-solid RSSI values being reported, even on barely or non-readable signals. '''This change will likely be rolled in to a permanent fix in a future firmware release.'''<br />
<br />
<br />
The other firmware change changes how the squelch responds (looks at the noise in the last two audio samples) and makes the "Micor squelch" action work better.<br />
<br />
<br />
You may also want to consider the following changes in [[Voter.conf|/etc/asterisk/voter.conf]]:<br />
<pre><br />
;Comment out:<br />
;thresholds =<br />
<br />
;and set:<br />
linger = 0<br />
</pre><br />
<br />
=Squelch Issues=<br />
*If anyone is off frequency a little bit, that will make the voice talk off worse. Double check that the repeater and the users are all on frequency.<br />
*Don't use narrow bandwidth on the repeater receiver. <br />
*Make sure that the discriminator audio is not rolled off even a little bit at the high end. There should not be resistors in series or capacitors to ground between the discriminator chip output pin and the voter board input, for best results.<br />
<br />
<br />
==Motorola Quantar==<br />
Some things to consider:<br />
*Install JP1 on the Quantar's RTCM. The squelch should calibrate at around 4 blinks rather than the 12 blinks or so without JP1.<br />
*Be sure you've done the diode and squelch calibration with the actual attached radio (no antenna). <br />
*The Quantar firmware should be 20.14.48 as later versions have better noise output. <br />
*Try the "Chuck Squelch" RTCM version.<br />
*Each RTCM should have 3 to 5 turns past threshold to prevent the squelch form being too loose. Somewhere around the 350 level seems about right. Chuck Squelch seems to need fewer turns but YMMV.<br />
*Don't "and" CTCSS with squelch. That may override the RTCM's squelch detection. Compare with CTCSS on and off to see effect if any.<br />
<br />
<br />
=RTCM/VOTER LED's=<br />
RX LED on the RTCM/VOTER will flash (same rate as ACT LED) if you have External CTCSS enabled, and the received signal has the wrong (or no) valid PL.<br />
<br />
<br />
=Menus=<br />
==Main Menu==<br />
This is what a typical Main Menu looks like:<br />
<br />
<pre><br />
Select the following values to View/Modify:<br />
<br />
1 - Serial # (0000) (which is MAC ADDR 00:04:A3:00:00:00)<br />
2 - VOTER Server Address (FQDN) (44.128.1.1)<br />
3 - VOTER Server Port (667), 4 - Local Port (Override) (0)<br />
5 - Client Password (password1), 6 - Host Password (hostpass1)<br />
7 - Tx Buffer Length (800)<br />
8 - GPS Data Protocol (0=NMEA, 1=TSIP) (1)<br />
9 - GPS Serial Polarity (0=Non-Inverted, 1=Inverted) (1)<br />
10 - GPS PPS Polarity (0=Non-Inverted, 1=Inverted, 2=NONE) (0)<br />
11 - GPS Baud Rate (9600)<br />
12 - External CTCSS (0=Ignore, 1=Non-Inverted, 2=Inverted) (0)<br />
13 - COR Type (0=Normal, 1=IGNORE COR, 2=No Receiver) (0)<br />
14 - Debug Level (0)<br />
15 - Alt. VOTER Server Address (FQDN) ()<br />
16 - Alt. VOTER Server Port (Override) (0)<br />
17 - DSP/BEW Mode (0)<br />
18 - "Duplex Mode 3" (0=DISABLED, 1-255 Hang Time) (1/10 secs) (0)<br />
19 - Simulcast Launch Delay (0) (approx 200 ns, 5 = 1us, > 0 to ENA SC)<br />
97 - RX Level, 98 - Status, 99 - Save Values to EEPROM<br />
i - IP Parameters menu, o - Offline Mode Parameters menu<br />
q - Disconnect Remote Console Session, r - reboot system, d - diagnostics<br />
<br />
Enter Selection (1-27,97-99,r,q,d) :<br />
</pre><br />
<br />
==IP Parameters Menu==<br />
This is what a typical IP Parameters Menu looks like:<br />
<br />
<pre><br />
IP Parameters Menu<br />
<br />
Select the following values to View/Modify:<br />
<br />
1 - (Static) IP Address (44.128.1.2)<br />
2 - (Static) Netmask (255.255.255.0)<br />
3 - (Static) Gateway (44.128.1.254)<br />
4 - (Static) Primary DNS Server (44.128.1.254)<br />
5 - (Static) Secondary DNS Server (0.0.0.0)<br />
6 - DHCP Enable (0)<br />
7 - Telnet Port (23)<br />
8 - Telnet Username (admin)<br />
9 - Telnet Password (radios)<br />
10 - DynDNS Enable (0)<br />
11 - DynDNS Username (wb6nil)<br />
12 - DynDNS Password (radios42)<br />
13 - DynDNS Host (voter-test.dyndns.org)<br />
14 - BootLoader IP Address (192.168.1.10) (OK)<br />
15 - Ethernet Duplex (0=Half, 1=Full) (1)<br />
99 - Save Values to EEPROM<br />
x - Exit IP Parameters Menu (back to main menu)<br />
q - Disconnect Remote Console Session, r - reboot system<br />
<br />
Enter Selection (1-14,99,c,x,q,r) :<br />
</pre><br />
<br />
==Offline Parameters Menu==<br />
This is what a typical Offline Parameters Menu looks like:<br />
<br />
<pre><br />
OffLine Mode Parameters Menu<br />
<br />
Select the following values to View/Modify:<br />
<br />
1 - Offline Mode (0=NONE, 1=Simplex, 2=Simplex w/Trigger, 3=Repeater) (3)<br />
2 - CW Speed (400) (1/8000 secs)<br />
3 - Pre-CW Delay (4000) (1/8000 secs)<br />
4 - Post-CW Delay (4000) (1/8000 secs)<br />
5 - CW "Offline" (ID) String (WB6NIL)<br />
6 - CW "Online" String (OK)<br />
7 - "Offline" (CW ID) Period Time (6000) (1/10 secs)<br />
8 - Offline Repeat Hang Time (15) (1/10 secs)<br />
9 - Offline CTCSS Tone (0.0) Hz<br />
10 - Offline CTCSS Level (0-32767) (3000)<br />
11 - Offline De-Emphasis Override (0=NORMAL, 1=OVERRIDE) (0)<br />
99 - Save Values to EEPROM<br />
x - Exit OffLine Mode Parameter Menu (back to main menu)<br />
q - Disconnect Remote Console Session, r - reboot system<br />
<br />
Enter Selection (1-9,99,c,x,q,r) :<br />
</pre><br />
<br />
=Configuration Options=<br />
==Main Menu Options==<br />
===Serial #===<br />
Sets the serial number for the RTCM/VOTER.<br />
*This sets the MAC address of the unit.<br />
*Each unit must have a unique serial number on your network segment.<br />
<br />
===VOTER Server Address (FQDN)===<br />
This is the DNS name or IP address of the Asterisk server you are connecting to.<br />
<br />
===VOTER Server Port===<br />
This is the UDP port that the Asterisk server is listening on for clients.<br />
*Typically it is left at the default of port 667.<br />
*'''MUST''' match the ''port'' directive in ''voter.conf''.<br />
<br />
===Local Port (Override)===<br />
Sets the local unit UDP port to be something different.<br />
*This is typically not used and left at default (0).<br />
<br />
===Client Password===<br />
This is the '''unique''' password for this unit.<br />
*Every unit '''must''' have a '''unique''' password.<br />
*'''MUST''' match the password on the client configuration line in ''voter.conf''.<br />
<br />
===Host Password===<br />
This is the password of the Asterisk server.<br />
*Configured with the ''password'' directive in ''voter.conf''.<br />
<br />
===Tx Buffer Length===<br />
This is the size of the TX buffer from the RTCM/VOTER to the Asterisk server.<br />
*Tuned parameter, set via the tuning instructions based on network configuration.<br />
<br />
===GPS Data Protocol (0=NMEA, 1=TSIP)===<br />
Type of GPS connected.<br />
*NMEA for all non-Trimble GPS units.<br />
*TSIP to use with Trimble GPS that use Trimble Serial Interface Protocol (TSIP).<br />
<br />
===GPS Serial Polarity (0=Non-Inverted, 1=Inverted)===<br />
GPS dependent setting. <br />
*Depends on if you are sending TTL or RS-232 data, adjust as needed.<br />
<br />
===GPS PPS Polarity (0=Non-Inverted, 1=Inverted, 2=NONE)===<br />
GPS dependent setting. <br />
*Depends on if you are sending TTL or RS-232 data for the PPS signal, adjust as needed.<br />
*If not using GPS or configuring as a mixed client, set to 2 (None).<br />
<br />
===GPS Baud Rate===<br />
Communication speed for the GPS, default is 9600.<br />
<br />
===External CTCSS (0=Ignore, 1=Non-Inverted, 2=Inverted)===<br />
If you are using the CTCSS input from an external CTCSS decoder, adjust this for your logic polarity, or set to 0 (ignore) if not used.<br />
<br />
===COR Type (0=Normal, 1=IGNORE COR, 2=No Receiver)===<br />
Typically, this is left at Normal. <br />
*Set to 1 (Ignore COR), if you are using the External CTCSS input.<br />
<br />
===Debug Level===<br />
Set the Debug Level, if needed, based on the [[#Debug Options | Debug Options]] below.<br />
<br />
===Alt. VOTER Server Address (FQDN)===<br />
If you are using redundant Asterisk servers, set the IP/DNS address of the redundant server here.<br />
<br />
===Alt. VOTER Server Port (Override)===<br />
If the redundant Asterisk server UDP port is not 667, set it here.<br />
<br />
===DSP/BEW Mode===<br />
If the firmware supports DSP/BEW Mode, set this to 1 to enable it, if desired.<br />
*DSP/BEW firmware versions use extra firmware space and will make the diagnostic menu unavailable.<br />
<br />
==="Duplex Mode 3" (0=DISABLED, 1-255 Hang Time) (1/10 secs)===<br />
If you are using Duplex Mode 3, set the hang time here to enable the option. Most users leave this disabled.<br />
<br />
===Simulcast Launch Delay===<br />
If you are using Simulcast, set your launch delay here.<br />
<br />
===RX Level===<br />
This opens the RX Level tuning screen to adjust the receive audio level from the repeater.<br />
<br />
===Status===<br />
This opens the status menu, showing some of the current operating parameters.<br />
<br />
===Save Values to EEPROM===<br />
Save all the options to non-volatile EEPROM.<br />
*Make sure to save after you make any changes.<br />
<br />
===IP Parameters menu===<br />
Open the IP Parameters Menu.<br />
<br />
===Offline Mode Parameters menu===<br />
Open the Offline Mode Parameters Menu.<br />
<br />
===Disconnect Remote Console Session===<br />
If you are connected via Telnet, this will exit your session.<br />
<br />
===Reboot System===<br />
Reboot the VOTER/RTCM.<br />
*This should be done after making configuration changes.<br />
*Some setting changes require a reboot to become effective.<br />
<br />
===Diagnostics===<br />
Open the Diagnostics Menu.<br />
*Diagnostics are unavailable if you are using DSP/BEW firmware.<br />
<br />
<br />
=Network Information=<br />
==RTCM/VOTER Bandwidth==<br />
Assuming ulaw... The RTCM will require approximately 80kbps of bandwidth for continual usage.<br />
<br />
<br />
==Network Quality==<br />
Your IP Network quality is important. You may wish to add a rule in your routers to prioritize traffic on UDP port 667 so that RTCM audio is given priority over other <br />
traffic. Also see the [[#Debug Options]] below for notes on how to tag your packets with ToS.<br />
<br />
<br />
==RX/TX Buffers are NOT Both Millisecond Values== <br />
You might assume an RX buffer (in voter.conf) of 120ms would be equivalent of a TX buffer (in the RTCM) of 120ms. That is not the case.<br />
<br />
<br />
The TX buffer is a number of 125 '''microsecond''' intervals, where the RX buffer is in milliseconds. <br />
<br />
<br />
If you follow the buffer setting instructions, you should be fine, in most cases. <br />
<br />
<br />
=Debug Options=<br />
The VOTER/RTCM firmware supports some additional debugging information that can be turned on.<br />
<br />
<br />
From the source code, the different Debug Options are listed as:<br />
<pre><br />
1 - Alt/Main Host change notifications<br />
2 - Ignore HWlock (GGPS only)<br />
4 - GPS/PPS Failure simulation (GGPS only)<br />
8 - POCSAG H/W output disable (GGPS only)<br />
16 - IP TOS Class for Ubiquiti<br />
32 - GPS Debug<br />
64 - Fix GPS 1 second off<br />
128 - Fix GPS 1 month off (WTF,O??)<br />
</pre><br />
<br />
<br />
Not sure what they all do, but that is what they are. Here are the most common ones used:<br />
*"Alt/Main Host change notifications" <br />
**shows when the connection to the Asterisk server changes state.<br />
*"IP TOS Class for Ubiquity" <br />
**marks the IP headers from the RTCM/VOTER '''TO''' the network with ToS C0/DSCP 48 (UBNT shows this as 802.1p Class 6 (Voice <10mS latency). Other sources show this as a Network Control TOS.) If you enable this, you also will want to have "utos=y" in your voter.conf to mark the packets from the network '''TO''' the RTCM/VOTER. We will probably change this option to mark the packets by default in a future version.<br />
*"GPS Debug" <br />
**will print NMEA or TSIP debug strings from the connected GPS.<br />
*"Fix GPS 1 second off"<br />
**this is for NMEA GPS '''only'''. It will add one second to the time.<br />
*"Fix GPS 1 month off (WTF,O??)"<br />
**this is for TSIP GPS '''only'''. It will effectively add a month to the date. The mktime function normally needs one month subtracted from the raw month it converts to a time/date string. Maybe there are some GPS out there that do that automatically? <br />
<br />
<br />
The way this works is you add together the options you want to enable.<br />
<br />
<br />
Want to enable GPS Debug and IP ToS, set debug to 48.<br />
<br />
<br />
Just want to turn on GPS Debug, set debug to 32.<br />
<br />
<br />
Just want ToS turned on, set debug to 16.<br />
<br />
<br />
=Un-documented Menus/Features=<br />
*Menu 96 - If firmware compiled with DUMPENCREGS enabled, Menu 96 looks like it dumps the registers from the ENC (Ethernet) chip?<br />
<br />
*Menu 111 - show the "hidden" option values (normally they should all be 0).<br />
<br />
*Menu 11780 - set the "Elkes" value. Developed for Pete Elkes, this is for solar type sites. It shuts off the Tx after a period of no Rx activity.<br />
<br />
*Menu 1103 - set the "Glaser" timer value? No idea what this does.<br />
<br />
*Menu 1170 - set "Sawyer Mode". Developed for Tim Sawyer use on Yaesu VXR5000 repeater. It modifies de-ephasis behavior when on/off line. <br />
<br />
<br />
=Audio=<br />
The RTCM/VOTER is totally flexible regarding emphasis. Although the way it is set is completely obscure. It tries to automatically do the right thing for you, which is great most of the time. But when it’s not, it's hard to know what is going on. <br />
<br />
If you are changing the COR Type settings, or nodeemp in voter.conf, make sure you save/reboot the RTCM/VOTER every time you make a change... changes are '''not''' effective until the RTCM/VOTER reboots!<br />
<br />
<br />
==Voting==<br />
Before we get in to the different ways audio is routed, there is an important consideration you need to make if you are using the RTCM/VOTER for voting. <br />
<br />
The way the voting process works, it needs '''discriminator audio''' to determine the signal to noise level from each satellite receiver. As such, you will need to be feeding discriminator audio in to the RX audio pin, so that the hardware/software can vote properly. That means you also need to let the hardware/software do the squelch action.<br />
<br />
If you need RX CTCSS, you'll need to feed logic from an external CTCSS decoder in to the CTCSS input pin.<br />
<br />
Also, don't disable COR in the RTCM/VOTER... it will cause it to disable the squelch and it will report an RSSI of 255 (full quieting) for all received signals.<br />
<br />
<br />
==Receiver De-emphasis==<br />
On the RX side the COR Type setting in the RTCM/VOTER determines whether the de-emphasis filter is used for RX audio. 0=Normal means the RTCM/VOTER squelch circuit is in use and it is expecting discriminator audio on the RX pin (to be able to do the squelch action), and therefore it '''will''' provide de-emphasis (audio is routed THROUGH the de-emphasis RC filter circuit) to the receiver audio. COR Type 1=IGNORE COR uses the CTCSS input pin for COR or CTCSS ''logic'' and it then expects de-emphasized receive (line) audio on the RX pin, and therefore will '''not''' provide de-emphasis to the received audio (the RC filter is switched '''out''' and audio passes straight through). <br />
<br />
<br />
Most of the time, you do NOT need to override the automatic filter selection. However, if you do, and you are sure you have a good reason to, you CAN switch the de-emphasis filter '''out''' of the circuit so that audio passes straight through to the encoder. You would do this by setting the nodeemp=1 option in voter.conf. When you set nodeemp=1, the ''VOTER Protocol'' tells the RTCM/VOTER to switch the filter '''out''', so audio is passed straight through.<br />
<br />
<br />
==Transmitter Pre-emhpasis==<br />
On the TX side, the RTCM/VOTER expects the repeater to accept ''mic audio''. In other words, the '''repeater''' is providing the pre-emphasis, not the RTCM/VOTER (you are '''not''' directly modulating the TX). This can be overridden by setting CTCSS tone in voter.conf. If a CTCSS tone is defined, the RTCM '''will''' provide pre-emphasis to the audio, and expects that you will be connecting to your repeater's flat audio input (direct modulation). <br />
<br />
<br />
If you don’t want TX CTCSS tone but '''do''' need pre-emphasis, set an arbitrary (any) CTCSS tone in voter.conf, and set the level to 0. This will force the RTCM/VOTER to pre-emphasize the audio it generates on the TX pin, but it won't actually mix in a CTCSS tone. <br />
<br />
<br />
==Level Setting==<br />
Setting the audio levels for the RTCM/VOTER is pretty straight forward. Just follow these steps:<br />
*Ensure you have a connection to your host Asterisk server/chan_voter instance<br />
*Send a 1kHz@3kHz on-channel, full-quieting signal in to the repeater's RX<br />
*Set the RX up so it reads 3kHz deviation on the RTCM's built in console meter<br />
*Now set the TX level '''pot''' to get 3kHz out of the transmitter (No PL)<br />
<br />
<br />
Now change the modulation from 1kHz tone to 800Hz followed by 1.8kHz and verify that the deviation level doesn't change as the tone frequency changes. '''Changing levels indicates a pre/de-emphasis issue.''' You will want to read the above sections on how audio is handled, and figure out where your issue is.<br />
<br />
<br />
If using PL you have to account for that deviation, unless you filter it out with your IFR (test set). <br />
<br />
<br />
That's it!<br />
<br />
<br />
Optionally, if you are using the built-in "offline repeat" functions, fail the connection to the host Asterisk server, and make sure your repeat audio performs the same as above.<br />
<br />
==== Resolution issues when setting levels using built VOTER boards ====<br />
Sometimes, depending on what radio is being used getting a good enough resolution with R61 when setting levels is a problem. You move a small amount on the pot and it jumps several hundred KHz of deviation. Inserting a 4:1 voltage divider between the VOTER board and transmitter helps with this. Something such as a 1K and 330 ohm resistor will work. This allows for much finer adjustment on the transmit audio (R61).<br />
<br />
==Crappy Transmit Audio==<br />
<br />
Does your repeated audio sounded really bassy, muffled, and not very understandable? <br />
<br />
<br />
There was a situation where, compared to a typical simplex radio-to-radio transmission, the audio through the repeater (RTCM and Asterisk) was unacceptable. What was discovered was that the RTCM has an internal pre-emphasis function that was disabled. The user had intentionally disabled "txctcss" and "txctcsslevel" in voter.conf because he didn't <br />
want the RTCM transmitting CTCSS (the Quantar was doing that already). He ultimately found a post on the mail list explaining the settings above that said enabling txctcss = some valid tone (114.8 in his case) and setting txctcsslevel = 0 would turn on the pre-emphasis function in the RTCM without transmitting CTCSS tones. <br />
<br />
<br />
He did, and it worked like a charm! Audio now had more treble and was less bassy/muffled. So, future RTCM users, be sure not to comment out txctcss and txctcsslevel in voter.conf!<br />
<br />
<br />
Just enable and set the level to 0. You'll thank me later. <br />
<br />
== Pulse Noise on Transmit Audio ==<br />
It has been noticed sometimes on built VOTER boards that it has low level DAC noise which sometimes is apparent as a pulsing noise on the audio output. Adding a 4:1 voltage divider inline between the transmitter and VOTER board helps reduce or eliminate this as described above in Level setting. <br />
<br />
=GPS=<br />
The RTCM/VOTER will work with most GPS available. It requires either NMEA or Trimble TSIP binary data. It only receives data '''from''' the GPS (GPS TX), it does not send anything '''to''' the GPS.<br />
<br />
<br />
The firmware is specifically written to talk to Trimble Thunderbolt receivers using Trimble's TSIP binary data interface, however, other Trimbles GPS receivers that talk TSIP are generally compatible.<br />
<br />
<br />
==NMEA Sentences==<br />
If you are using an NMEA GPS (as opposed to a Trimble using the TSIP binary interface), the RTCM/VOTER is looking for the following NMEA sentences:<br />
<br />
<pre><br />
$GPGGA<br />
$GPGSV<br />
$GPRMC<br />
</pre><br />
<br />
<br />
==GPS Lock==<br />
The GPS led will go solid regardless of the connection LED. That '''has''' to happen or it won't connect to the Asterisk server. <br />
<br />
<br />
It is not unusual for it to take up to 20 mins to get a GPS lock LED (ie. using a Trimble Thunderbolt) after any reboot. <br />
<br />
<br />
==GPS De-sense==<br />
If you are having odd loss of lock issues, consider you may have interference to your GPS antenna from strong RF nearby. A note from Jesse Lloyd:<br />
<br />
<pre><br />
I also had crazy problems with poor signal on my GPS when I set it up sitting in a window, and once installed at site I had the GPS antenna maybe 6 ft from the VHF antenna, and after some troubleshooting found it was getting swamped with RF and loosing lock. <br />
<br />
I found the debug setting of 32 useful in the RTCM, you can see a hex output of the GPS status. <br />
</pre><br />
<br />
<br />
==GPS Issues==<br />
===Trimble Thunderbolt===<br />
You may find your Trimble Thunderbolt is showing the incorrect date at the moment. It could be showing the year as 1997. This is due to the date in the Thunderbolt being reported incorrectly.<br />
<br />
<br />
'''This can cause some of your voting receivers to not connect, if they are used with other GPS in your system.''' If you have '''ALL''' Thunderbolts, or '''NO''' Thunderbolts, you are probably fine. If you have '''ALL''' Thunderbolts, the date/time is probably wrong, but they will ALL be wrong, so they will connect.<br />
<br />
<br />
GPS Time is a continuous counting time scale beginning at the January 5, 1980 to January 6, 1980 midnight. It is split into two parts: a time of week measured in seconds from midnight Sat/Sun and a week number. The time of week is transmitted in an unambiguous manner by the satellites, but only the bottom 10 bits of the week number are transmitted. This means that a receiver will see a week number count that goes up steadily until it reaches 1023 after which it will “roll over” back to zero, before steadily going up again. Such a week rollover will occur approx. every 20 years. The last week rollover occurred in 1999 and the next one will be in 2019.<br />
<br />
<br />
The Thunderbolt manual states:<br />
<pre><br />
The ThunderBolt adjusts for this week rollover by adding 1024 to any week number reported by GPS which is less than week number 936 which began on December 14, 1997. With this technique, the ThunderBolt will provide an accurate translation of GPS week number and TOW to time and date until July 30, 2017.<br />
</pre><br />
<br />
<br />
As such, the Trimble Thunderbolt has a firmware issue with the GPS Week rollover that manifested itself on July 30, 2017, causing the date to become incorrect. The Thunderbolt thinks the week changed from 935 to 936 (actual week 1959-1024=935), so it stopped adding 1024 to the week.<br />
<br />
<br />
We have added a brute-force fix starting in RTCM/VOTER firmware >=1.51. This fix adds 619315200 seconds (1024 weeks) to the time reported by the GPS. It fixes the Thunderbolts, we have not done extensive testing to see how it affects other TSIP receivers.<br />
<br />
===Garmin===<br />
====Garmin 18x LVC Wiring Issues====<br />
If you have issues with your GPS 18x LVC not talking to the RTCM/VOTER, it may not be hooked up to the RTCM correctly. <br />
<br />
<br />
The Garmin pin labeling is backwards to what you may think. See below. You probably need to swap pins 6 and 14.<br />
<br />
<pre><br />
RTCM GPS 18x LVC <br />
6 GRX <-- Rx Data 6 Green <br />
7 GPPS <-- Pulse Output 1 Yellow <br />
8 GND Ground 3 Black <br />
8 GND Ground 5 Black <br />
13 +5V -->Vin 2 Red <br />
14 GTX --> TX Data 4 White<br />
</pre><br />
<br />
<br />
Log into the RTCM and do 98 and you should see something like this:<br />
<br />
<pre><br />
Current Time: Sun Apr 20, 2014 04:37:02.820<br />
Last Rx Pkt System time: 04/20/2014 03:55:35.580, diff: 2487260 msec<br />
Last Rx Pkt Timestamp time: 04/20/2014 03:55:32.064, diff: 3515 msec<br />
Last Rx Pkt index: 160, inbounds: 1<br />
</pre><br />
<br />
<br />
====Garmin and the RTCM====<br />
Beware when buying newer Garmin GPS's to use with the Micro-Node RTCM.<br />
<br />
<br />
The RTCM expects a 5V PPS signal.<br />
<br />
<br />
Newer Garmin's (GPS 18X, 18X LVC, etc.) MAY NOT output 5V, and can cause issues. '''Check the Garmin datasheet'''.<br />
<br />
<br />
The VOTER is designed to accept both 3.3V or 5V signals, and ''should'' work fine.<br />
<br />
* Some of the Garmin GPS's come with 4800 baud set as default. If you are getting a "Warning: GPS Data time period elapsed" error on your RTCM, change both the GPS and RTCM to use 9600 baud. To do this, interface the GPS to a DB9 connector as per page 8 of the [http://wiki.allstarlink.org/w/images/4/41/GPS_18x_Tech_Specs.pdf manual] (remembering to ONLY use 5V as the power source *facepalm*). Once done, download, extract and open [http://www8.garmin.com/support/download_details.jsp?id=4053 SNSRXCFG_330.exe] and run.<br />
# Select your GPS (in most cases GPS 18x PC/LVC). Press F10 to switch to NMEA mode (Config > Switch to NMEA Mode)<br />
# Select Config > Setup and choose the COM port your GPS is connected too. Leave baud rate as auto for now, OK.<br />
# Select Comm > Connect to connect to the GPS. <br />
# Go to Config > Get Configuration from GPS to download it's current configuration<br />
# Click File > Save to save the current configuration<br />
# In Config > Sensor Configuration change the Baud Rate to 9600. You can also check to make sure 1PPS is enabled here too. Click OK. <br />
# Hitting F7 when in the main window of the software also brings up the GPS sentences to output if that is of interest.<br />
# File > Save to a different file than step 5. <br />
# Press F9 or Config > Send Configuration to GPS. This will then send all the changes you made to the GPS unit (including baud rate so a reconnect may be needed)<br />
<br />
<br />
==No GPS/Mixed Mode==<br />
You do not need a timing source to use an RTCM if you don’t want to vote. That’s called Mix Mode.<br />
<br />
<br />
Having the PPS Polarity set to 2 tells the RTCM you do not have a GPS. That forces the RTCM to become a mix (non-voting) client. Turn it on, save it, and restart. A simple voter.conf would look like this:<br />
<br />
<pre><br />
[general]<br />
port = 667<br />
password = BLAH<br />
<br />
[1000]<br />
Site1 = pswrd1,master,transmit<br />
Site2 = pswrd2,transmit<br />
</pre><br />
<br />
<br />
==Mixed Client Error==<br />
"I am getting this error in Asterisk":<br />
<pre><br />
WARNING[2368]: chan_voter.c:4511 voter_reader: Voter client master timing source mobile1 attempting to authenticate as mix client!!<br />
</pre><br />
<br />
<br />
A mixed client error means the voter.conf file is expecting an RTCM to try and connect with a GPS IP packet (ie. has '''master''' in it in voter.conf), but the RTCM isn't <br />
sending a GPS IP packet. So its a mismatch between voter.conf and Option 10 in the RTCM. <br />
<br />
<br />
If you want to use a mix client (non-voted), make sure that receiver's configuration line in voter.conf '''does not''' have the '''master''' option set.<br />
<br />
<br />
==Mix Clients with Voted Client Issues==<br />
<br />
Situation...<br />
"I have a private node with 6 voted receivers using RTCMs. I'd like to add a 7th RTCM to this node that is always mixed in rather than voted. I'm able to make this RTCM work as a 7th voted receiver with no problem. Everything I've read seems to indicate that if I change GPS PPS polarity to "none" this will achieve my desired results, however I am unable to get audio out of my transmit RTCM from this 7th site. It does change color to cyan in Allmon indicating it is non voted input but I do not get any indication or audio when that units COR goes active."<br />
<br />
"Setting voter debug level 3 in Asterisk and I'm seeing the following message repeatedly scrolling by in a blur when the mix client detects COR (COR is active). Sequence numbers are continually incrementing by 1. I'm running software version 1.47 on all my clients:"<br />
<br />
<pre><br />
mix client (Mulaw) my_client index:0 their seq:629 our seq:629<br />
mix client my_client outa bounds, resetting!!<br />
</pre><br />
<br />
If you have a similar situation to the above... check your buflen in voter.conf. Make sure it is at >=160 and see if that fixes it.<br />
<br />
<br />
==GPS Debug==<br />
To turn on GPS Debugging, set the Debug Option Level in the RTCM/VOTER to 32.<br />
<br />
<br />
See [[#Debug Options]] levels for more information on how this works.<br />
<br />
<br />
==Trimble Debug Status Decoding==<br />
The VOTER/RTCM when in TSIP mode (Trimble), assumes it is a Trimble Thunderbolt and is looking for two packets:<br />
*0x8F-AB - Primary Timing Packet<br />
*0x8F-AC - Supplemental Timing Packet<br />
<br />
<br />
Grab a copy of the Thunderbolt User Guide: http://leapsecond.com/pages/tbolt/Thunderbolt-2012-02.pdf<br />
<br />
<br />
Pages 78-83 are the important ones.<br />
<br />
<br />
Packet 0x8F-AB is what grabs the timing information, and packet 0x8F-AC is what it looks at for everything else (including debug).<br />
<br />
<br />
The debug string that the VOTER/RTCM reports:<br />
<br />
<pre><br />
printf("GPS-DEBUG: TSIP: ok %d, 9 - 14: %02x %02x %02x %02x %02x %02x\n",<br />
happy,gps_buf[9],gps_buf[10],gps_buf[11],gps_buf[12],gps_buf[13],gps_buf[14]);<br />
</pre><br />
<br />
<br />
So, the 1 after ok is the "happy gps" flag. The other 5 bytes are supposed to be bytes 9-14 from the packet... sort of. They are bytes 9-14 of the buffer, but they are actually bytes 8-13 of the binary message.<br />
<br />
<br />
Looking at the message structure, bytes 8-13 are:<br />
*8-9 Critical Alarms<br />
*10-11 Minor Alarms<br />
*12 GPS Decoding Status<br />
*13 Disciplining Activity<br />
<br />
<br />
Therefore, the messages you are seeing break down as follows:<br />
<br />
<pre><br />
GPS-DEBUG: TSIP: ok 1, 9 - 14: 00 00 00 00 00 00 - everything is good in the 'hood, Doing Fixes, Phase Locking<br />
<br />
GPS-DEBUG: TSIP: ok 0, 9 - 14: 00 00 00 18 08 06 - not happy, Not Tracking Satellites, Not Disciplining Oscillator (0x18 --> 0b000000011000), No Usable Sats, Inactive<br />
<br />
GPS-DEBUG: TSIP: ok 0, 9 - 14: 00 00 00 08 08 05 - not happy, Not Tracking Satellites, No Useable Sats, Compensating OXCO (holdover)<br />
<br />
GPS-DEBUG: TSIP: ok 0, 9 - 14: 00 00 00 00 00 05 - not happy, Compensating OXCO (holdover)<br />
<br />
GPS-DEBUG: TSIP: ok 1, 9 - 14: 00 00 00 00 00 08 - happy, Recovery Mode<br />
<br />
GPS-DEBUG: TSIP: ok 0, 9 - 14: 00 00 00 00 00 04 - not happy, Initializing Loop Filter<br />
</pre><br />
<br />
<br />
The GPS is flagged as NOT HAPPY in TSIP mode if ANY of the following are TRUE:<br />
*If GPS Decoding Status is anything other than "Doing Fixes".<br />
*If Disciplining Activity is not Phase Locking or Recovery Mode.<br />
*Any Critical Alarms.<br />
*Any Minor Alarms.<br />
<br />
<br />
=Ubiquity ToS=<br />
See https://help.ubnt.com/hc/en-us/articles/205231750-airMAX-How-is-QoS-and-prioritization-handled-by-airMAX-<br />
<br />
<br />
So, if we set ToS/DSCP in the header to C0, then Ubiquity (and other gear watching ToS) ''should'' prioritize the packets. This sets the DSCP to 110 000 aka 48. UBNT shows this as 802.1p Class 6 (Voice <10mS latency). Other sources show this as a Network Control TOS.<br />
<br />
<br />
There is an option in voter.conf to turn this on (utos=y). However, this only controls packets being sent from Asterisk '''TO''' the RTCM. <br />
<br />
<br />
If you want to tag packets from the RTCM '''TO''' Asterisk, you need to set the RTCM debug option level to 16 (see [[#Debug Options]] for how this works).<br />
<br />
<br />
At some point we should probably change the default behaviour of the RTCM firmware to mark the packets and use the debug setting to '''disable''' ToS. That change (if you wanted to compile your own firmware) would be:<br />
<br />
<pre><br />
Change line 90 in IP.c<br />
<br />
From:<br />
#define IP_SERVICE ((AppConfig.DebugLevel & 16) ? 0xc0 : (IP_SERVICE_ROUTINE | IP_SERVICE_N_DELAY))<br />
<br />
To:<br />
#define IP_SERVICE ((AppConfig.DebugLevel & 16) ? (IP_SERVICE_ROUTINE | IP_SERVICE_N_DELAY) : 0xc0)<br />
</pre><br />
<br />
<br />
This changes the conditional expression from if the debug level is 16 to mark the packets with DSCP 48 to if the debug level is 16, mark the packets routine (DSCP 0).<br />
<br />
<br />
=RTCM Simulcasting=<br />
The RTCM/VOTER boards do support simulcasting, however, there are a bunch of quirks that one needs to be aware of.<br />
<br />
<br />
==Radio Hardware==<br />
For best results, you should use all identical RF equipment between your voting RX sites and simulcast TX sites. If you don't, you can end up with strange audio artifacts when different receivers are used, and other strange audio issues when different transmitters are used. The most important thing when setting your levels is that ALL the RX and TX levels match from radio to radio. The best way this is achieved is using a "master" radio and reference from that - all radios might be identical models, but may not have identical audio characteristics so check those levels! Also check CTCSS and audio levels separately to make sure they all match.<br />
<br />
<br />
==9.6MHz Oscillator==<br />
If you want reliable simulcast with an acceptable level of overlap warble, you MUST inject a GPS-disciplined or OXCO 9.6MHz signal to the clock of the RTCM's, in lieu of their stock internal crystal. <br />
<br />
<br />
Otherwise, the inherent internal clock jitter of the RTCM's will cause CTCSS warble, etc. in areas where your transmitters overlap. The 1 PPS feed that you normally feed the RTCM's is acceptable for voting, but naturally, a typical crystal-driven clock will slightly drift in between the pulses every second due to inherent jitter, etc., and that ain't to good for situations like simulcast which demand sample-accurate performance.<br />
<br />
<br />
Here are some comments from Joe, KC2IRV, on the subject. He has also created his own wiki, specific to simulcast issues, you can find it at: http://rtcmsimulcast.wikifoundry.com/ <br />
<br />
:I felt I needed to let those on this mailing list know my findings with simulcasting with the RTCM units since I have received a great deal of help and information from people on this list.<br />
<br />
:For the past week I have had a two (2) site simulcast system up and running on UHF using the RTCM units. I have done a great deal of testing and proving on the bench and it is so far working beautifully. <br />
<br />
:The one issue that was made apparent to me early on was that in order for the RTCM's to be suitable for simulcast, the processor inside it needed to be clocked to a more accurate source. This source is supposed to be the Programmable Clock Generator Module in order to produce a GPS locked 9.6 MHz reference for the processor. Unfortunately this unit is not currently available.<br />
<br />
:Knowing this, I started to go down the road of possibly designing my own, but stumbled upon a cheap, plentiful supply of Symmetricom 9.6 MHz sinewave OCXO's. I took a chance and ordered a few to experiment with to see if the RTCM would be able to use this in place of the supplied crystal for a clock. I found they did, with that I decided to modify the RTCM with an SMA connector just above the audio adjustment pots and use this OCXO. I trimmed the frequency on the units to match each other and used them to produce the processor clock.<br />
<br />
:After a week of testing, I have found the results in the overlap areas to be exactly as I would expect them on a public safety/commercial simulcast system. While in an overlap region where both transmitters are within 3dB of one another, to the ear you hear no audio phase wandering. Of course , this has only been a week of testing so I wouldn't call it case closed yet.<br />
<br />
:I will say that if this system remains this way after testing for 6 months to a year than using a 9.6 MHz OXCO is a viable alternative to achieve the needed precision and accuracy needed for the processor clock to make it suitable for simulcast.<br />
<br />
<br />
Comments from Jim Dixon on the issue:<br />
<br />
:You have to use '''something''' that will take the precise 10MHz (or whatever it is) from the GPSDO and PLL (phase-locked) convert it to 9.6MHz (square wave at 3.3V for the CPU clock).<br />
<br />
:We had to use 9.6MHz mainly because of the DAC in the dsPIC instead of 10MHz. The options for various divide/clock radios in the part are RATHER limited. As I recall, there wasn't even a way of getting the necessary 16kb/s sample rate on the ADC from 10MHZ, either.<br />
<br />
<br />
=Micro-Node RTCM Clock Issue=<br />
James, KI0KN, had some strange-ness with some of his RTCM's when used for voting. As soon as he changed menu item 10 on the RTCM to either a (1) or a (0) instead of (2), he '''instantly''' got this on the RTCM console:<br />
<br />
<pre><br />
04/05/2016 18:44:13.660 Lost GPS Time synchronization<br />
04/05/2016 18:44:13.660 Host Connection Lost (Pri) (10.16.1.240)<br />
</pre><br />
<br />
<br />
And it sits there forever and never re-establishes connection to the host. The issue was finally traced to a bad batch of 9.6MHz crystals that affected a small run of the RTCM's. The issue was eventually resolved by Micro-Node, but we'll document it here just for record keeping.<br />
<br />
<br />
James comments to the list:<br />
<br />
:Well, after many of you offered your time and thoughts on my voter problem, Jim, WB6NIL, graciously donated a couple of hours of his time to remotely help me and he uncovered the problem.<br />
<br />
:All 5 of my RTCMs were purchased within the last 6 months, and I suspect all 5 have the same problem (will verify that today). The problem is that the microprocessor crystal is running too fast! There is 9.6Mhz crystal that drives the MPU, on the particular unit that Jim helped me diagnose, it's running 2.5 khz too fast. <br />
<br />
:There is a sanity check in the firmware that makes sure the correct number of samples were taken in the last second (it's supposed to be 8000) and fails if the sample is incorrectly sized (mine is taking 8003 samples). Jim helped adjust the code to be more tolerant of the sampling error and my whole system instantly worked.<br />
<br />
:I have since tested it with ALL my GPSs (they all work great!). So I now have everything working, including the voting.<br />
<br />
:I haven't contact Micro-Node about it yet. Jim told me that voting should work fine but this clock error would probably not be acceptable for Simulcast (something we have no plans on doing as of now). Since mine are deployed at mountain top sites, I'll probably pursue a crystal that is running at the correct frequency and use "standard" firmware so that if the decision is ever made to play with simulcast, I won't be right back in this same boat.<br />
<br />
:Thanks to all that helped out, and a HUGE thanks to Jim for taking the time to troubleshoot this.<br />
<br />
:BTW- This clock error will NOT effect the RTCM in mix client mode, it only affects it in voting or simulcast mode!<br />
<br />
:In voter.c, the stock line is:<br />
<pre><br />
if ((samplecnt >= 7999) && (samplecnt <= 8001))<br />
<br />
it needs to be changed to something like:<br />
<br />
if ((samplecnt >= 7999) && (samplecnt <= 8003 ))<br />
</pre><br />
<br />
:That was just enough to make my first RTCM work. I've had a chance now to check a few more of my RTCMs on the bench this morning and the crystal frequencies are kind of all over. The next one I had on the bench was 5.2Khz fast. The above code was still not enough to fix it (as would be expected) so it looks like the quality control on whatever manufacturer that crystal is, isn't very good (or a low tolerance crystal is being used). I am going to pursue crystal replacement to get a highly accurate, stable, on-frequency crystal in there as my first choice. Changing the firmware 5 different times doesn't seem like the right answer.<br />
<br />
:Jim put that sanity check in there for a reason. Working around it '''may''' allow the device to work, but to me, it seems getting the hardware operating the way it was supposed to originally is the better answer. I will follow up with Micro-node and let you all know how it goes.<br />
<br />
<br />
After following up with Micro-Node:<br />
:They were all off, some were off a LOT. I talked to Mark @ Micronode. He told me there were 25 units that made it out the door with a crystal from an unapproved source and that was quite likely the reason for the problem. He gladly sent me 5 new crystals to replace (he offered to replace them himself if I sent the units in, but I am comfortable doing it myself to save the time and postage). <br />
<br />
:I haven't received them in the mail yet to show that the problem is fixed, but I will post here when that happens. He was great to work with and had no issue getting things set straight. If you are having the same issue and your RTCMs were bought about the same time, I'd suggest you contact him and have him help you resolve the issue!<br />
<br />
<br />
=Duplex Mode 3=<br />
Does delayed repeat audio bug you? Tired of hearing a bit of yourself after you unkey? Wish you could talk full duplex? Hate the echo chamber effect? Then we have the answer for you.<br />
<br />
<br />
Duplex Mode 3 in app_rpt allows for "in-cabinet repeat" (where the radio hardware provides repeat audio) and app_rpt adds the hang time, courtesy tones, linking - all the <br />
things apt_rpt does sans repeat audio. Therefore no repeat audio delay. Cool, eh? This duplex mode has been in app_rpt for a while. Problem has been how to implement it in the RTCM environment. <br />
<br />
<br />
Duplex Mode 3 support in the RTCM provides in-cabinet repeat functionality. Repeat audio loops through the RTCM and has almost zero delay because it does not have to traverse the network. The delay is not quite zero but it's plenty short enough to eliminate all of the above mentioned annoyances. <br />
<br />
<br />
Of course Duplex Mode 3 support can't be used with voting or simulcast. You also loose Touch Tone muting, Time Out Timer and Repeater Disable functions because the repeat path is not through app_rpt.<br />
<br />
= Setting Voter Buffers =<br />
Voter ping is useful for end-to-end network evaluation when ICMP ping is turned off and/or the RTCM is behind a firewall and is not ICMP reachable. It can also help with finding the correct RTCM and voter.conf buffer settings.<br />
<br />
=== Voter Ping Usage ===<br />
The voter ping asterisk CLI syntax is:<br />
*CLI>voter ping nameOfClient [packetCount]<br />
If packetCount is not specified 8 pings will be sent. Use packetCount of 0 to stop an in progress voter ping. Set packetCount to at least 100 when evaluating link quality.<br />
<br />
The result will be similar to:<br />
...<br />
PING (nameOfClient): Packets tx: 100, rx: 100, oos: 0, Avg.: 26.710 ms<br />
PING (nameOfClient): Worst: 38 ms, Best: 22 ms, 100.0% Packets successfully received (0.0% loss)<br />
The output above is self evident except for oos which is a count of out of sequence packets. Voter ping requires RTCM firmware 1.23 or newer and chan_voter 2013-08-04 or newer.<br />
<br />
=== RX Buffer Size ===<br />
Ping all the receiver sites and look for the worst response of the worst client. As a rough rule of thumb the buflen setting in voter.conf should be set to the worst response + 40ms or 120 whichever is greater. Using the above case the buflen should be set to 120 (38+40<br />
<br />
=== TX Buffer Size ===<br />
Ping all the transmitter sites and look for the worst response of the worst client. The RTCM TX Buffer Length should be set to (worst response + 40ms) * 8 or 480 whichever is greater. Using the above case the RTCM TX Buffer Length should be set to 624 ((38+40)*8).<br />
<br />
=== Assumptions ===<br />
* The minimum TX buffer size is 480 (60ms) and the minimum RX buffer is 120ms. These were derived by testing on a LAN segment with chan_voter 2013-08-04 and RTCM 1.26.<br />
* The ping times are not round trip times but they are in fact round trip times. Therefore the worst response could (should?) be divided by 2. Ie RX buffer = 38/2+40=59 and TX buffer = (38/2 + 40) * 8 = 472. Minimums still apply.<br />
* The internet path to and from the RTCM under test is symmetrical.<br />
* The added 40ms pad is an estimate of buffer ingress and egress.<br />
As always your milage may vary. Some trial and error may be required to find the optimum settings.<br />
<br />
=== Setup ===<br />
The RX buffer is set with buflen=120 in /etc/asterisk/voter.conf. The value is in milliseconds. The TX buffer is set in the RTCM with menu item 7. The value is in 125 microsecond increments. To match the size of the TX to the RX buffer, use the RX buffer * 8 to get the TX buffer size.<br />
[[Category:How to]]<br />
[[Category:Node Configuration]]</div>N8THNhttps://wiki.pttlink.org/index.php?title=RX_Toneburst&diff=1321RX Toneburst2019-01-28T14:06:17Z<p>N8THN: </p>
<hr />
<div>= Setting Up Receive Toneburst Access (Europe mainly) =<br />
[[Category:How to]]<br />
<br />
If you wish to set up a node to require receive toneburst (typically 1750 Hz, in Europe), you must, at least specify the toneburst frequency:<br />
<br />
(The following parameters go into rpt.conf in the section for the desired node)<br />
<br />
rxburstfreq=1750<br />
<br />
If you wish to change the minimum duration of the tone:<br />
<br />
rxbursttime=500 ;this would set the minimum time to 500ms<br />
<br />
If you wish to change the minimum signal/noise ratio for the tone:<br />
<br />
rxburstthreshold=10 ;this would set the minimum s/n quality to 10db</div>N8THNhttps://wiki.pttlink.org/index.php?title=RX_Toneburst&diff=1320RX Toneburst2019-01-28T14:05:36Z<p>N8THN: created page</p>
<hr />
<div>[[Category:How to]]</div>N8THNhttps://wiki.pttlink.org/index.php?title=WebTransceiver_on_MAC&diff=1319WebTransceiver on MAC2019-01-28T14:04:03Z<p>N8THN: </p>
<hr />
<div>[[Category:How to]]<br />
The WebTransceiver the AllStar Link PORTAL works fine on the Mac. This howto shows you the setting you need to make to get it working. These instructions are for Mavericks (OS 10.9). In Safari preferences click the Security icon, then Manage Website Settings, then Java, then allstarlink.org. Select Run in Unsafe Mode from the drop down, then click Done and exit preferences. See the attached screenshot.<br />
[[Category:Obsolete]]</div>N8THNhttps://wiki.pttlink.org/index.php?title=WebTransceiver_on_MAC&diff=1318WebTransceiver on MAC2019-01-28T14:02:34Z<p>N8THN: created page</p>
<hr />
<div>[[Category:How to]]</div>N8THNhttps://wiki.pttlink.org/index.php?title=Event_Management&diff=1317Event Management2019-01-28T14:00:36Z<p>N8THN: Corrected broken page link</p>
<hr />
<div>[[Category:How to]]<br />
As of app_rpt version 0.259, 10/9/2010, there exists a method by which a user can specify actions to be taken when certain events occur, such as transitions in receive and transmit keying, presence and modes of links, and external inputs, such as GPIO pins on the URI (or similar USB devices).<br />
<br />
Bear in mind, this now also includes the ability to set the condition of external devices, such<br />
<br />
as output pins on a URI (or similar USB devices), or a Parallel Printer Port. <br />
<br />
'''[[Manipulating GPIO|Manipulating GPIO (and Parallel Printer Port) signals within chan_usbradio and chan_simpleusb.]]''' <br />
<br />
The actions to be taken, and methods and steps required for doing so are specified in the rpt.conf<br />
<br />
file under the [events] section (or other named section, settable with events=sectionname under the<br />
<br />
node number section also in rpt.conf).<br />
<br />
This subsystem utilizes Asterisk channel variables (or global variables if you dare) to indicate the<br />
<br />
state of various signals and modes and are named as such:<br />
RPT_RXKEYED -- Set to 1 when the node's main (RF) receiver is receiving a valid signal<br />
RPT_TXKEYED -- Set to 1 when the node's main (RF) transmitter is transmitting<br />
RPT_NUMLINKS -- Count of links currently connected to node<br />
RPT_LINKS -- List of Node numbers currently linked to this node and their mode and receive keying<br />
status, as follows:<br />
<br />
<NUMLINKS>,<MODE><NODEMUM>[,<MODE><NODEMUM>...]<br />
<br />
For example: 2,T2000,R2001 would indicate that there are 2 nodes linked currently,<br />
first one is node 2000 in Transceive mode, and the second one is node 2001 in Receive-Only<br />
(monitor) mode.<br />
<br />
RPT_NUMALINKS -- Count of adjacent links currently connected to node<br />
RPT_ALINKS -- List of Node numbers currently linked adjacent to this node and their mode and receive<br />
keying status, as follows:<br />
<br />
<NUMALINKS>,<NODEMUM><MODE><RXKEYED&gt[,<NODEMUM><MODE><RXKEYED>...]<br />
<br />
For example: 2,2000TU,2001RK would indicate that there are 2 adjacent nodes linked currently,<br />
first one is node 2000 in Transceive mode, and is not presently sending a keying<br />
signal towards this node, and the second one is node 2001 in Receive-Only (monitor)<br />
mode, and is presently sending a keying signal towards this node.<br />
<br />
Adjacent nodes are ones that are directly connected to this node. This differs from the RPT_LINKS<br />
in that the RPT_LINKS is a list of all nodes, whether connected directly, or connected through<br />
a node that is connected directly. The keying information is not given with the RPT_LINKS because<br />
in that context it is meaningless.<br />
There may also be others included from external devices/sources, such as the URI (or similar USB<br />
<br />
devices), or a Parallel Printer Port that will appear if so configured (within the configuration<br />
<br />
for that particular device),<br />
<br />
such as:<br />
RPT_URI_GPIO1 -- This would be the GPIO 1 pin, if configured as an input.<br />
RPT_URI_GPIO4 -- This would be the GPIO 4 pin, if configured as an input.<br />
RPT_PP12 -- This would be the Parallel Printer Port, pin 12 (input)<br />
<br />
These are set to "0" or "1" (the state of the input pin).<br />
Each line of the [events] section is specified as follows:<br />
<action-spec> = <action>|<type>|&ltvar-spec><br />
<br />
If action is 'V' (for "setting variable"), then action-spec is the variable being set.<br />
If action is 'G' (for "setting global variable"), then action-spec is the global variable being set.<br />
If action is 'F' (for "function"), then action-spec is a DTMF function to be executed (if result is 1).<br />
If action is 'C' (for "rpt command"), then action-spec is a raw rpt command to be executed (if <br />
result is 1).<br />
If action is 'S' (for "shell command"), then action-spec is a shell command to be executed (if <br />
result is 1).<br />
<br />
If type is 'E' (for "evaluate statement" (or perhaps "equals") ) then the var-spec is a full statement<br />
containing expressions, variables and operators per the expression evaluation built into Asterisk.<br />
If type is 'T' (for "going True"), var-spec is a single (already-defined) variable name, and the result<br />
will be 1 if the varible has just gone from 0 to 1.<br />
If type is 'F' (for "going False"), var-spec is a single (already-defined) variable name, and the<br />
result will be 1 if the varible has just gone from 1 to 0.<br />
If type is 'N' (for "no change"), var-spec is a single (already-defined) variable name, and the result<br />
will be 1 if the varible has not changed.<br />
Examples:<br />
<br />
Set the channel variable 'MYVAR' true if main receiver has valid signal and transmitter is<br />
<br />
not transmitting. Presumable this variable will be used in a later statement for something.<br />
MYVAR = v|e|${RPT_RXKEYED} & !${RPT_TXKEYED}<br />
Have the system give the time of day after all links are disconnected. This performs the<br />
<br />
specified rpt command when the 'RPT_NUMLINKS' variable goes from true to false, and therefore<br />
<br />
happens when all links are disconnected (if and only if some were connected previously).<br />
status,2 = c|f|RPT_NUMLINKS<br />
<br />
Note: although 'RPT_NUMLINKS' ''is'' an Integer count of links, it can also be treated as a<br />
boolean, since non-zero values evaluate to the same as '1'.<br />
Execute the DTMF command '*1234' (whatever the heck that is) when node 2000 connects to this node.<br />
TEMPVAR = v|e|${RPT_LINKS} =~ "\",2000.\""<br />
*1234 = f|t|TEMPVAR<br />
<br />
Note: We are interested in executing the function ONLY when the node connects. Therefore, you must<br />
define a variable the meets the condition you are looking for in general (in this case, node 2000<br />
being connected, then you have to execute the desired function when that variable goes from 1 to 0<br />
(changes to false).<br />
<br />
Any time you are using regex to look for a node number int the 'RPT_LINKS' variable, you must<br />
put a comma in front of the qualifying string to make sure that it does not match some other<br />
node number that has the desired information (in this case, the digits '2000') within a longer<br />
node number.<br />
Get a detailed directory listing of the '/tmp' directory, and put its output into the file<br />
<br />
'/tmp/example.txt' every time node 2001 is connected to, and stops indicating keying towards our node<br />
<br />
(not that anyone would ever really want to do that... its just an example).<br />
TEMPVAR = v|e|${RPT_ALINKS} =~ "\",2001[TRC]K\""<br />
ls -l /tmp > /tmp/example.txt = s|f|TEMPVAR<br />
If you wish to set channel variable(s) for a node from the CLI, you may use the following command:<br />
*CLI> rpt setvar <nodenum> <name=value> [<name=value>...]<br />
For Example, this would set the "MYVAR" variable to "1" for node 2000:<br />
*CLI> rpt setvar 2000 MYVAR=1<br />
If you wish to display all the variables for a node, use the following command:<br />
*CLI> rpt showvars <nodenum><br />
Also, a channel variable for a node may be set from the Asterisk Dialplan as follows:<br />
rpt(<nodenum&gt,V,<name=value>)<br />
For example, for extension 1234 priority 5, set variable 'MYVAR' to '0' for node 2000:<br />
exten => 1234,5,rpt(2000,V,MYVAR=0)<br />
Granted, there may very well be some things (such as interesting information that can be expressed<br />
<br />
within this subsystem) that has been overlooked, and any suggestions and/or comments regarding this<br />
<br />
whole thing would be much appreciated.<br />
<br />
This also opens a completely new avenue of customization and individual creativity for each system<br />
<br />
implementer. There are many innovative things that can be done with this. Also there are many just plain<br />
<br />
silly ones, such as connecting your doorbell to one the input pins on the URI, and having the system<br />
<br />
connect to your favorite Echolink node or something when someone rings the doorbell.<br />
<br />
At some point there should be a contest to see who can come up with the most utterly ludicrous<br />
<br />
appication of this subsystem. There are many possibilities to explore in this area. Hint: you will<br />
<br />
get '''major''' extra bonus points if it involves the script re-writing itself (self-modifying<br />
<br />
code, that exhibits at least plausibility of long-term stability (going to poo-poo in less then<br />
<br />
1000 iterations is ''just'' not acceptible)).<br />
<br />
In any case, please contribute whatever wonderful configurations you come up with so that all users<br />
<br />
may have the benefits of all the wonderful ideas everyone comes up with.</div>N8THNhttps://wiki.pttlink.org/index.php?title=Manipulating_GPIO&diff=1316Manipulating GPIO2019-01-28T13:59:34Z<p>N8THN: </p>
<hr />
<div>[[Category:How to]]<br />
The GPIO (general-purpose I/O) pins on a URI (or similar USB device) may be individually used as<br />
<br />
either input or output pins. Currently the URI (because of the CM108-AH chip) only supports 2<br />
<br />
usable GPIO pins (GPIO 1 and GPIO 4), plus one pin (labeled GPIO2, but is actually the 'HOOK' signal<br />
<br />
on the CM-108AH chip) that may be used only for input. The old version of the URI and some other<br />
<br />
devices that use the original CM-108A chip, have full access to the GPIO 2 signal also.<br />
<br />
The upside to the CM-108AH is that if you are monitoring an external contact closure, the GPIO2 (HOOK)<br />
<br />
input is internally pulled-up and de-bounced, so its perfect for such applications.<br />
<br />
Chan_usbradio and chan_simpleusb supports configuration of the GPIO pins in the following manner<br />
<br />
(from within the section of usbradio.conf that is for the desired device):<br />
<br />
gpio1 = in ; in, out0 or out1<br />
<br />
gpio4 = out0 ; in, out0 or out1<br />
<br />
When you configure a GPIO pin, you can either designate it as 'in' (input), 'out0' (output with a default state of 'off'), or 'out1' (output with a default state of 'on').<br />
<br />
It also supports configuration of pins 2-9 (output) and pins 10-13 and 15 (inputs) on a Parallel<br />
<br />
Printer Port (if you happen to have one) in the following manner:<br />
<br />
pp2 = out1 ; out0, out1 or ptt<br />
<br />
pp10 = in ; in, cor or ctcss<br />
<br />
When you configure an input pin (10,11,12,13 or 15), you can either designate it as 'in' (input),<br />
<br />
'cor' (use as the 'cor' input), or 'ctcss' (use as the 'ctcss') input. If you choose 'cor' or<br />
<br />
'ctcss', you also need to set the associated 'carrierfrom' or 'ctcssfrom' to either 'pp' (use the<br />
<br />
associated input pin non-inverted) or 'ppinvert' (use the associated input pin inverted).<br />
<br />
When you configure an output pin (2-9), you can either designate it as 'out0' (output with a default<br />
<br />
state of 'off'), 'out1' (output with a default state of 'on'), or 'ptt' makes the PTT signal present<br />
<br />
on it either non-inverted or inverted, depending on the 'invertptt' setting.<br />
<br />
Pins 18-25 are ground, and all other pins are to be treated as no connection.<br />
<br />
The condition of the input pins are made available via channel variables (e.g. RPT_URI_GPIO1,<br />
<br />
RPT_URI_GPIO4, RPT_PP12, etc.) used by the Event Management Subsystem.<br />
<br />
The output pins may be manipulated via the 'cop,61' (or 'cop,62') command (directly or through a DTMF<br />
<br />
command) as follows:<br />
<br />
61 - Send Message to USB to control GPIO pins (cop,61,GPIO1=0[,PP4=1].....)<br />
<br />
62 - Same as above, without generating the 'complete' telemetry.<br />
<br />
Use 0 or 1 to set the specified output to 0 or 1, or a number greater then 1 to specify how<br />
<br />
many milliseconds minus 1 to invert its current state. For example, to pulse the bit for 500ms you<br />
<br />
would use the value '501'(currently, specified time only significant in increments of 50ms). The<br />
<br />
use of specifying a value of N+1 to indicate N milliseconds was done so that if, in the future,<br />
<br />
the granulatity increases down to the millisecond level, a value of 1 ms could be specified.<br />
<br />
For example, if you wanted to have a DTMF function (in this example *1234) that turned GPIO 1<br />
<br />
on, you would specify the following in the [functions] section of the rpt.conf file:<br />
<br />
1234 = cop,61,GPIO1=1 ; Turn on GPIO 1<br />
<br />
Note: You must have app_rpt version 0.259 10/9/2010, and chan_usbradio also released at<br />
<br />
that time, and for Parallel Printer Port support, you must have app_rpt version 0.267<br />
<br />
10/23/2010, and chan_usbradio also released at that time.</div>N8THNhttps://wiki.pttlink.org/index.php?title=Manipulating_GPIO&diff=1315Manipulating GPIO2019-01-28T13:59:01Z<p>N8THN: created page</p>
<hr />
<div>[[Category:How to]]</div>N8THNhttps://wiki.pttlink.org/index.php?title=Event_Management&diff=1314Event Management2019-01-28T13:57:59Z<p>N8THN: </p>
<hr />
<div>[[Category:How to]]<br />
As of app_rpt version 0.259, 10/9/2010, there exists a method by which a user can specify actions to be taken when certain events occur, such as transitions in receive and transmit keying, presence and modes of links, and external inputs, such as GPIO pins on the URI (or similar USB devices).<br />
<br />
Bear in mind, this now also includes the ability to set the condition of external devices, such<br />
<br />
as output pins on a URI (or similar USB devices), or a Parallel Printer Port. <br />
<br />
'''Manipulating GPIO (and Parallel Printer Port) signals within chan_usbradio and chan_simpleusb.''' <br />
<br />
The actions to be taken, and methods and steps required for doing so are specified in the rpt.conf<br />
<br />
file under the [events] section (or other named section, settable with events=sectionname under the<br />
<br />
node number section also in rpt.conf).<br />
<br />
This subsystem utilizes Asterisk channel variables (or global variables if you dare) to indicate the<br />
<br />
state of various signals and modes and are named as such:<br />
RPT_RXKEYED -- Set to 1 when the node's main (RF) receiver is receiving a valid signal<br />
RPT_TXKEYED -- Set to 1 when the node's main (RF) transmitter is transmitting<br />
RPT_NUMLINKS -- Count of links currently connected to node<br />
RPT_LINKS -- List of Node numbers currently linked to this node and their mode and receive keying<br />
status, as follows:<br />
<br />
<NUMLINKS>,<MODE><NODEMUM>[,<MODE><NODEMUM>...]<br />
<br />
For example: 2,T2000,R2001 would indicate that there are 2 nodes linked currently,<br />
first one is node 2000 in Transceive mode, and the second one is node 2001 in Receive-Only<br />
(monitor) mode.<br />
<br />
RPT_NUMALINKS -- Count of adjacent links currently connected to node<br />
RPT_ALINKS -- List of Node numbers currently linked adjacent to this node and their mode and receive<br />
keying status, as follows:<br />
<br />
<NUMALINKS>,<NODEMUM><MODE><RXKEYED&gt[,<NODEMUM><MODE><RXKEYED>...]<br />
<br />
For example: 2,2000TU,2001RK would indicate that there are 2 adjacent nodes linked currently,<br />
first one is node 2000 in Transceive mode, and is not presently sending a keying<br />
signal towards this node, and the second one is node 2001 in Receive-Only (monitor)<br />
mode, and is presently sending a keying signal towards this node.<br />
<br />
Adjacent nodes are ones that are directly connected to this node. This differs from the RPT_LINKS<br />
in that the RPT_LINKS is a list of all nodes, whether connected directly, or connected through<br />
a node that is connected directly. The keying information is not given with the RPT_LINKS because<br />
in that context it is meaningless.<br />
There may also be others included from external devices/sources, such as the URI (or similar USB<br />
<br />
devices), or a Parallel Printer Port that will appear if so configured (within the configuration<br />
<br />
for that particular device),<br />
<br />
such as:<br />
RPT_URI_GPIO1 -- This would be the GPIO 1 pin, if configured as an input.<br />
RPT_URI_GPIO4 -- This would be the GPIO 4 pin, if configured as an input.<br />
RPT_PP12 -- This would be the Parallel Printer Port, pin 12 (input)<br />
<br />
These are set to "0" or "1" (the state of the input pin).<br />
Each line of the [events] section is specified as follows:<br />
<action-spec> = <action>|<type>|&ltvar-spec><br />
<br />
If action is 'V' (for "setting variable"), then action-spec is the variable being set.<br />
If action is 'G' (for "setting global variable"), then action-spec is the global variable being set.<br />
If action is 'F' (for "function"), then action-spec is a DTMF function to be executed (if result is 1).<br />
If action is 'C' (for "rpt command"), then action-spec is a raw rpt command to be executed (if <br />
result is 1).<br />
If action is 'S' (for "shell command"), then action-spec is a shell command to be executed (if <br />
result is 1).<br />
<br />
If type is 'E' (for "evaluate statement" (or perhaps "equals") ) then the var-spec is a full statement<br />
containing expressions, variables and operators per the expression evaluation built into Asterisk.<br />
If type is 'T' (for "going True"), var-spec is a single (already-defined) variable name, and the result<br />
will be 1 if the varible has just gone from 0 to 1.<br />
If type is 'F' (for "going False"), var-spec is a single (already-defined) variable name, and the<br />
result will be 1 if the varible has just gone from 1 to 0.<br />
If type is 'N' (for "no change"), var-spec is a single (already-defined) variable name, and the result<br />
will be 1 if the varible has not changed.<br />
Examples:<br />
<br />
Set the channel variable 'MYVAR' true if main receiver has valid signal and transmitter is<br />
<br />
not transmitting. Presumable this variable will be used in a later statement for something.<br />
MYVAR = v|e|${RPT_RXKEYED} & !${RPT_TXKEYED}<br />
Have the system give the time of day after all links are disconnected. This performs the<br />
<br />
specified rpt command when the 'RPT_NUMLINKS' variable goes from true to false, and therefore<br />
<br />
happens when all links are disconnected (if and only if some were connected previously).<br />
status,2 = c|f|RPT_NUMLINKS<br />
<br />
Note: although 'RPT_NUMLINKS' ''is'' an Integer count of links, it can also be treated as a<br />
boolean, since non-zero values evaluate to the same as '1'.<br />
Execute the DTMF command '*1234' (whatever the heck that is) when node 2000 connects to this node.<br />
TEMPVAR = v|e|${RPT_LINKS} =~ "\",2000.\""<br />
*1234 = f|t|TEMPVAR<br />
<br />
Note: We are interested in executing the function ONLY when the node connects. Therefore, you must<br />
define a variable the meets the condition you are looking for in general (in this case, node 2000<br />
being connected, then you have to execute the desired function when that variable goes from 1 to 0<br />
(changes to false).<br />
<br />
Any time you are using regex to look for a node number int the 'RPT_LINKS' variable, you must<br />
put a comma in front of the qualifying string to make sure that it does not match some other<br />
node number that has the desired information (in this case, the digits '2000') within a longer<br />
node number.<br />
Get a detailed directory listing of the '/tmp' directory, and put its output into the file<br />
<br />
'/tmp/example.txt' every time node 2001 is connected to, and stops indicating keying towards our node<br />
<br />
(not that anyone would ever really want to do that... its just an example).<br />
TEMPVAR = v|e|${RPT_ALINKS} =~ "\",2001[TRC]K\""<br />
ls -l /tmp > /tmp/example.txt = s|f|TEMPVAR<br />
If you wish to set channel variable(s) for a node from the CLI, you may use the following command:<br />
*CLI> rpt setvar <nodenum> <name=value> [<name=value>...]<br />
For Example, this would set the "MYVAR" variable to "1" for node 2000:<br />
*CLI> rpt setvar 2000 MYVAR=1<br />
If you wish to display all the variables for a node, use the following command:<br />
*CLI> rpt showvars <nodenum><br />
Also, a channel variable for a node may be set from the Asterisk Dialplan as follows:<br />
rpt(<nodenum&gt,V,<name=value>)<br />
For example, for extension 1234 priority 5, set variable 'MYVAR' to '0' for node 2000:<br />
exten => 1234,5,rpt(2000,V,MYVAR=0)<br />
Granted, there may very well be some things (such as interesting information that can be expressed<br />
<br />
within this subsystem) that has been overlooked, and any suggestions and/or comments regarding this<br />
<br />
whole thing would be much appreciated.<br />
<br />
This also opens a completely new avenue of customization and individual creativity for each system<br />
<br />
implementer. There are many innovative things that can be done with this. Also there are many just plain<br />
<br />
silly ones, such as connecting your doorbell to one the input pins on the URI, and having the system<br />
<br />
connect to your favorite Echolink node or something when someone rings the doorbell.<br />
<br />
At some point there should be a contest to see who can come up with the most utterly ludicrous<br />
<br />
appication of this subsystem. There are many possibilities to explore in this area. Hint: you will<br />
<br />
get '''major''' extra bonus points if it involves the script re-writing itself (self-modifying<br />
<br />
code, that exhibits at least plausibility of long-term stability (going to poo-poo in less then<br />
<br />
1000 iterations is ''just'' not acceptible)).<br />
<br />
In any case, please contribute whatever wonderful configurations you come up with so that all users<br />
<br />
may have the benefits of all the wonderful ideas everyone comes up with.</div>N8THNhttps://wiki.pttlink.org/index.php?title=Event_Management&diff=1313Event Management2019-01-28T13:52:00Z<p>N8THN: </p>
<hr />
<div>[[Category:How to]]<br />
As of app_rpt version 0.259, 10/9/2010, there exists a method by which a user can specify actions to be taken when certain events occur, such as transitions in receive and transmit keying, presence and modes of links, and external inputs, such as GPIO pins on the URI (or similar USB devices).<br />
<br />
Bear in mind, this now also includes the ability to set the condition of external devices, such<br />
<br />
as output pins on a URI (or similar USB devices), or a Parallel Printer Port. <br />
<br />
The actions to be taken, and methods and steps required for doing so are specified in the rpt.conf<br />
<br />
file under the [events] section (or other named section, settable with events=sectionname under the<br />
<br />
node number section also in rpt.conf).<br />
<br />
This subsystem utilizes Asterisk channel variables (or global variables if you dare) to indicate the<br />
<br />
state of various signals and modes and are named as such:<br />
RPT_RXKEYED -- Set to 1 when the node's main (RF) receiver is receiving a valid signal<br />
RPT_TXKEYED -- Set to 1 when the node's main (RF) transmitter is transmitting<br />
RPT_NUMLINKS -- Count of links currently connected to node<br />
RPT_LINKS -- List of Node numbers currently linked to this node and their mode and receive keying<br />
status, as follows:<br />
<br />
<NUMLINKS>,<MODE><NODEMUM>[,<MODE><NODEMUM>...]<br />
<br />
For example: 2,T2000,R2001 would indicate that there are 2 nodes linked currently,<br />
first one is node 2000 in Transceive mode, and the second one is node 2001 in Receive-Only<br />
(monitor) mode.<br />
<br />
RPT_NUMALINKS -- Count of adjacent links currently connected to node<br />
RPT_ALINKS -- List of Node numbers currently linked adjacent to this node and their mode and receive<br />
keying status, as follows:<br />
<br />
<NUMALINKS>,<NODEMUM><MODE><RXKEYED&gt[,<NODEMUM><MODE><RXKEYED>...]<br />
<br />
For example: 2,2000TU,2001RK would indicate that there are 2 adjacent nodes linked currently,<br />
first one is node 2000 in Transceive mode, and is not presently sending a keying<br />
signal towards this node, and the second one is node 2001 in Receive-Only (monitor)<br />
mode, and is presently sending a keying signal towards this node.<br />
<br />
Adjacent nodes are ones that are directly connected to this node. This differs from the RPT_LINKS<br />
in that the RPT_LINKS is a list of all nodes, whether connected directly, or connected through<br />
a node that is connected directly. The keying information is not given with the RPT_LINKS because<br />
in that context it is meaningless.<br />
There may also be others included from external devices/sources, such as the URI (or similar USB<br />
<br />
devices), or a Parallel Printer Port that will appear if so configured (within the configuration<br />
<br />
for that particular device),<br />
<br />
such as:<br />
RPT_URI_GPIO1 -- This would be the GPIO 1 pin, if configured as an input.<br />
RPT_URI_GPIO4 -- This would be the GPIO 4 pin, if configured as an input.<br />
RPT_PP12 -- This would be the Parallel Printer Port, pin 12 (input)<br />
<br />
These are set to "0" or "1" (the state of the input pin).<br />
Each line of the [events] section is specified as follows:<br />
<action-spec> = <action>|<type>|&ltvar-spec><br />
<br />
If action is 'V' (for "setting variable"), then action-spec is the variable being set.<br />
If action is 'G' (for "setting global variable"), then action-spec is the global variable being set.<br />
If action is 'F' (for "function"), then action-spec is a DTMF function to be executed (if result is 1).<br />
If action is 'C' (for "rpt command"), then action-spec is a raw rpt command to be executed (if <br />
result is 1).<br />
If action is 'S' (for "shell command"), then action-spec is a shell command to be executed (if <br />
result is 1).<br />
<br />
If type is 'E' (for "evaluate statement" (or perhaps "equals") ) then the var-spec is a full statement<br />
containing expressions, variables and operators per the expression evaluation built into Asterisk.<br />
If type is 'T' (for "going True"), var-spec is a single (already-defined) variable name, and the result<br />
will be 1 if the varible has just gone from 0 to 1.<br />
If type is 'F' (for "going False"), var-spec is a single (already-defined) variable name, and the<br />
result will be 1 if the varible has just gone from 1 to 0.<br />
If type is 'N' (for "no change"), var-spec is a single (already-defined) variable name, and the result<br />
will be 1 if the varible has not changed.<br />
Examples:<br />
<br />
Set the channel variable 'MYVAR' true if main receiver has valid signal and transmitter is<br />
<br />
not transmitting. Presumable this variable will be used in a later statement for something.<br />
MYVAR = v|e|${RPT_RXKEYED} & !${RPT_TXKEYED}<br />
Have the system give the time of day after all links are disconnected. This performs the<br />
<br />
specified rpt command when the 'RPT_NUMLINKS' variable goes from true to false, and therefore<br />
<br />
happens when all links are disconnected (if and only if some were connected previously).<br />
status,2 = c|f|RPT_NUMLINKS<br />
<br />
Note: although 'RPT_NUMLINKS' ''is'' an Integer count of links, it can also be treated as a<br />
boolean, since non-zero values evaluate to the same as '1'.<br />
Execute the DTMF command '*1234' (whatever the heck that is) when node 2000 connects to this node.<br />
TEMPVAR = v|e|${RPT_LINKS} =~ "\",2000.\""<br />
*1234 = f|t|TEMPVAR<br />
<br />
Note: We are interested in executing the function ONLY when the node connects. Therefore, you must<br />
define a variable the meets the condition you are looking for in general (in this case, node 2000<br />
being connected, then you have to execute the desired function when that variable goes from 1 to 0<br />
(changes to false).<br />
<br />
Any time you are using regex to look for a node number int the 'RPT_LINKS' variable, you must<br />
put a comma in front of the qualifying string to make sure that it does not match some other<br />
node number that has the desired information (in this case, the digits '2000') within a longer<br />
node number.<br />
Get a detailed directory listing of the '/tmp' directory, and put its output into the file<br />
<br />
'/tmp/example.txt' every time node 2001 is connected to, and stops indicating keying towards our node<br />
<br />
(not that anyone would ever really want to do that... its just an example).<br />
TEMPVAR = v|e|${RPT_ALINKS} =~ "\",2001[TRC]K\""<br />
ls -l /tmp > /tmp/example.txt = s|f|TEMPVAR<br />
If you wish to set channel variable(s) for a node from the CLI, you may use the following command:<br />
*CLI> rpt setvar <nodenum> <name=value> [<name=value>...]<br />
For Example, this would set the "MYVAR" variable to "1" for node 2000:<br />
*CLI> rpt setvar 2000 MYVAR=1<br />
If you wish to display all the variables for a node, use the following command:<br />
*CLI> rpt showvars <nodenum><br />
Also, a channel variable for a node may be set from the Asterisk Dialplan as follows:<br />
rpt(<nodenum&gt,V,<name=value>)<br />
For example, for extension 1234 priority 5, set variable 'MYVAR' to '0' for node 2000:<br />
exten => 1234,5,rpt(2000,V,MYVAR=0)<br />
Granted, there may very well be some things (such as interesting information that can be expressed<br />
<br />
within this subsystem) that has been overlooked, and any suggestions and/or comments regarding this<br />
<br />
whole thing would be much appreciated.<br />
<br />
This also opens a completely new avenue of customization and individual creativity for each system<br />
<br />
implementer. There are many innovative things that can be done with this. Also there are many just plain<br />
<br />
silly ones, such as connecting your doorbell to one the input pins on the URI, and having the system<br />
<br />
connect to your favorite Echolink node or something when someone rings the doorbell.<br />
<br />
At some point there should be a contest to see who can come up with the most utterly ludicrous<br />
<br />
appication of this subsystem. There are many possibilities to explore in this area. Hint: you will<br />
<br />
get '''major''' extra bonus points if it involves the script re-writing itself (self-modifying<br />
<br />
code, that exhibits at least plausibility of long-term stability (going to poo-poo in less then<br />
<br />
1000 iterations is ''just'' not acceptible)).<br />
<br />
In any case, please contribute whatever wonderful configurations you come up with so that all users<br />
<br />
may have the benefits of all the wonderful ideas everyone comes up with.</div>N8THNhttps://wiki.pttlink.org/index.php?title=Event_Management&diff=1312Event Management2019-01-28T13:49:48Z<p>N8THN: created page</p>
<hr />
<div>[[Category:How to]]</div>N8THNhttps://wiki.pttlink.org/index.php?title=European_Repeater_Operation&diff=1311European Repeater Operation2019-01-28T13:36:33Z<p>N8THN: </p>
<hr />
<div>[[Category:How to]]<br />
<br />
We realize that there are different requirements for repeater operation in different parts of the world. Until recently, we have not dealt much with these, not out of insensitivity, but out of unfamiliarity.<br />
<br />
Two things have been brought to our attention that we have added functionality to support.<br />
<br />
In the UK, it is necessary for a repeater to identify on a periodic basis regardless of activity.<br />
<br />
To enable this feature:<br />
<br />
The following are parameters in the [node] section of rpt.conf:<br />
beaconing=yes<br />
Also, many countries still require access to the repeater be with a toneburst (generally 1750 Hz).<br />
<br />
To enable this feature:<br />
rxburstfreq=1750 ; set burst frequency to 1750 Hz (or whatever freq you desire)<br />
<br />
Also, optionally:<br />
<br />
rxbursttime=500 ; set minimum decode time to 500Hz<br />
rxburstthreshold=10 ; set minimum s/n ratio for decode</div>N8THNhttps://wiki.pttlink.org/index.php?title=European_Repeater_Operation&diff=1310European Repeater Operation2019-01-28T13:35:45Z<p>N8THN: created page</p>
<hr />
<div>[[Category:How to]]</div>N8THNhttps://wiki.pttlink.org/index.php?title=Update_from_SVN&diff=1309Update from SVN2019-01-28T13:28:48Z<p>N8THN: </p>
<hr />
<div>[[Category:How to]]<br />
[[Category:Obsolete]]<br />
As we fix bugs and add additional features, new source code is posted to SVN (and available from the viewvc interface) from time to time. New installs do not get the latest updates as what is in SVN is considered experimental. However, 99.99% of the time you'll want/need the latest. The update procedure is documented on the Allstar site. It is reproduced here for your convenience.<br />
<br />
<code>cd /usr/src</code><br />
<br />
<code>rm -rf astsrc</code><br />
<br />
<code>wget <nowiki>http://x.allstarlink.org/svn-trunk.tar.gz</nowiki> -O- | tar xzv</code><br />
<br />
<code>mv trunk astsrc</code><br />
<br />
<code>cd astsrc</code><br />
<br />
<code>make upgrade-acid</code><br />
<br />
This procedure can take over an hour on slow computers or under 10 minutes on fast ones. Restart asterisk when complete.</div>N8THNhttps://wiki.pttlink.org/index.php?title=Update_from_SVN&diff=1308Update from SVN2019-01-28T13:28:00Z<p>N8THN: created page</p>
<hr />
<div>[[Category:How to]]<br />
[[Category:Obsolete]]</div>N8THN