Difference between revisions of "Troubleshooting"
(Added troubleshooting page)
Latest revision as of 23:00, 20 January 2019
This section describes common problems, things to try, and hints to solve the problem.
- 1 Allstar Link registration fails when behind a NAT router
- 2 Breaking the keying loop between two simplex nodes
- 3 Cannot Receive Connections or Make Connections to Other Allstar Nodes
- 4 Cannot Receive Incoming Connections From Other Allstar Link Nodes
- 5 RTCM Choppy Audio
- 6 URI: TX Audio clipping using composite (tone and voice combined) on same output
- 7 URI: radio tune rxnoise fails
Allstar Link registration fails when behind a NAT router
Some NAT-routers do not honor source-port preservation. Registration (by default) requires that the source port be preserved. The URL register.allstarlink.org expects the source port to be 4569 by default. With some NAT routers, source-port preservation is not guaranteed. For example, the Dlink DI series is one such router which does not preserve source port numbers and there is a 100% chance that when the registration packet exits your router, it will use a different (high 60,000 range) port number.
There are two ways to resolve this issue:
1. Send an email to the list requesting your port number be forced to 4569, and one of the
network maintainers will do this for you.
2. Change the router to a brand which is known to preserve source port numbers.
Breaking the keying loop between two simplex nodes
Back and forth keying (aka as "Ping Ponging" or "Relay Racing") can occur when two simplex nodes are linked together. This is caused by COR or squelch noise glitches from certain types of radios. To fix,the COR must be ignored for a small amount of time after a simplex node releases PTT. To accommodate this, edit /etc/asterisk/usbradio.conf and add the following statement in the [usb] stanza or other port-specific stanza:
This will instruct the usbradio driver to ignore the COR line for a specified number of 20mSec intervals following the release of PTT.
Cannot Receive Connections or Make Connections to Other Allstar Nodes
|Hint||Thing(s) to try|
|Is Asterisk Running?||Type |
|Connectivity issues?||Try issuing a |
|Do you have a current rpt_extnodes file?||Check to see that rpt_extnodes exists in the /var/lib/asterisk directory. Change directories to /var/lib/asterisk: |
|Registration issues?||Does your node number show on a green background on allstarlink.org?. If not, your node may not be registering properly to register.allstarlink.org. Check the registration statement in /etc/asterisk/iax.conf and make sure the node number and password are correct|
Cannot Receive Incoming Connections From Other Allstar Link Nodes
|Hint||Thing(s) to Try|
|Do you have the correct port forwarding settings configured in your firewall?||Allstar Link requires that UDP traffic on port 4569 be forwarded from the public (WAN) IP address to the private (LAN) IP address running Limey Linux or ACID. Please check the settings in your router using its instruction manual to make sure port 4569 UDP is set up to be forwarded to the correct internal (private) IP address. If the port forwarding settings are correct in your router, please send a message to the app_rpt-users list requesting help, and we will check to see if your system is properly registering with our registration server. Please include your node number in the message A small number of NAT routers require that we force the port setting to port 4569 on the registration server. This is a manual process and requires intervention from one of the system administrations.|
RTCM Choppy Audio
The RTCM voter protocol is UDP which of course means packets can be dropped causing holes in the audio. Here are a couple of things to look for if the audio is choppy.
The server (chan_voter) sends a keep-alive packet to the RTCM once a second. Likewise, the RTCM sends a keep-alive packet to chan_voter once a second. Timeouts will occur if excessive packets are dropped.
- Start the asterisk console with verbose set to 3 (asterisk -rvvv) and watch for disconnect messages. -- Voter client nameOfClient disconnect (timeout) This means the chan_voter has missed 3 keep-alive packets in a row, or said another way, 3 seconds has passed since the last keep-alive was received.
- If the RTCM off-line fail over message is heard over the air (perhaps quickly followed by the on-line message) the RTCM has missed 6 keep-alive packets in a row. In other words 6 seconds has passed since the last keep-alive was received.
Either of these indicate a network problem that can not be compensated for with RTCM or voter.conf settings. The problem must be fixed using traditional network trouble shooting techniques, ie traceroute and ping. Try running a ping with a count of 100 or more to insure there is no packet loss.
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 help with finding the correct RTCM and voter.conf buffer settings. See Setting Voter Buffers and look at oos (out of sequence) and packet loss. Both should be zero. If not, adjusting the buffer size may reduce oos or packet loss.
URI: TX Audio clipping using composite (tone and voice combined) on same output
Ensure the sum of the SUM of txtone and txvoice should never exceed 1000. If more gain is needed, split the tone and voice outputs. To split the outputs use the follwing configuration in usbradio.conf:
; voice on left channel txmixa=voice ; tone on right channel txmixb=tone
URI: radio tune rxnoise fails
Ensure you have enough audio output from the receiver. Check with a AC voltmeter or scope. You need to have at least 100mV peak of audio for the rxnoise command to complete successfully.
Some radios do not produce enough high frequency noise (above 3kHz) to drive the noise detection DSP. In this case switching to simple usb is recommended.