- App_rpt-users - lists.keekles.org

RPi DIAL DNS Declaration Location
by kk6ecm 20 Jan '16

20 Jan '16

I want to update my DNS. Where is the file in the RPI DIAL version? I'm having difficulty resolving Echolink servers, and suspect my DNS has an issue. It could be pointed outside my router and have an issue if our internet service is interrupted. Thanks, Bob kk6ecm Sent from iPad

2 5

Doug, WA3DSP on QSO Today Podcast
by Eric Guth 19 Jan '16

19 Jan '16

I interviewed Doug, WA3DSP, on my ham radio podcast, QSO Today, at www.qsotoday.com/podcasts/wa3dsp<http://www.qsotoday.com/podcasts/wa3dsp> . He speaks about Internet linking and Allstar during the Interview. I hope that you find it as interesting as I did. 73, Eric Guth 4Z1UG Allstar: 28422 QSO Today

1 0

recordings
by Ken 18 Jan '16

18 Jan '16

If the recordings sound muddy and Allison is OK, then I think it's obvious where the problem lies. Have a look at the frequency response of the recording you made using Audacity's "plot spectrum." If there is a lot of energy below 300 Hz, that will be largely wasted energy, as most radios filter out the low end because that is where the PL tones are. Yet when you set the level of the recording (using "normalize") that energy will help determine the gain that Audacity uses, so it will rob energy from the higher frequencies that actually do pass through the repeater/radio. So it will sound extra-muddy when it goes through your repeater/radio. You should run a high pass filter on your recordings before normalizing, to fix this (see the Effect menu). A corner frequency of 100 Hz works well. With a female voice, you can use up to 300 Hz without losing any intelligibility. In a similar way, too much high frequency energy will mess up your levels too. Due to the 8 kHz sampling used internally, Asterisk will completely eliminate any energy above 4 Khz (actually it's about zero at 3.8). If you set your levels using a recording that was made at (for example) 44.1 KHz, energy between 4 and 22 Khz will be part of the level setting, but will be completely gone when it gets down-sampled to 8 kHz. So, the minus 6 dB is correct. But that level-setting needs to be done to a recording that matches the passband of what is going to be passed through the radio. Set the minus 6 AFTER fixing up the frequency response of your recording. In a related matter - there is one well-known bulletin famous for putting a big peak in their recordings at about 3.5 kHz, so their audio will sound sharper when passed through an SSB filter (I suppose). This is annoying in Asterisk, since this is right near the top of the frequency range and will tend to be distorted if exaggerated. I usually run a notch filter at 3900 Hz with a Q of 0.95 to provide a sudden fall-off in response, right at the top, when I work with one of these bulletins. Lastly - if Allison sounds muddy, that is another story. In that case, you may have your transmit pre-emphasis configured wrong - off when it should be on (in usbradio.conf). 73 Ken

1 0

Recording tail messages
by Robert Newberry 18 Jan '16

18 Jan '16

I followed the directions on ohnosec for using audacity for recording audio files. I use them as tail messages and that works fine. The audio quality however is eh so-so and I feel it could be better. I know one thing the normalize feature called for -6 and I ended up bumping it to 0 db just so it could be more audible. Is there anyone willing to share their experiences? It seems from listening to traffic on allstar the quality of messages could be better. N1XBM Apparare Scientor Paratus Communicare Allstar Node # 27086, 41540, 41812, 42086, 42658 N1XBM Apparare Scientor Paratus Communicare Allstar Node # 27086, 41540, 41812, 42086, 42658

4 4

Talk-Through Tone
by Ramesh Dhami (VA3UV) 18 Jan '16

18 Jan '16

Hi All: Having setup DIAL on my RPI2 and 3 nodes (2 full-duplex and 1 simplex), I have configured my full-duplex repeater nodes with 'talk-through tone' (COP 58). This provides a very nice repeater system in that the squelch on the user's radio only opens when there is an RF user on the local repeater... i.e., telemetry messages, courtesy tones, squelch crashes, etc., are all inaudible to RF users. What I didn't realize, up until recently, is that this configuration also makes audio from remote systems and local links inaudible since the local repeater does not transmit tone. Is there anyway to enable tone for remote links yet keep all of the COP 58 semantics? Thanks! Ramesh.

1 0

Re: [App_rpt-users] Perform actions based on PL tone
by rhyolite 18 Jan '16

18 Jan '16

That would be quite useful. Why stop at two, have multiple local codes! Sent from Samsung tablet -------- Original message -------- From: Skyler F <electricity440(a)gmail.com> Date: 01/17/2016 6:48 PM (GMT-05:00) To: app_rpt-users(a)ohnosec.org Subject: [App_rpt-users] Perform actions based on PL tone Is there any way to perform certain actions based on the CTCSS tone used? It would be cool if I could have one PL tone for local repeat only and another tone for the global repeat through AllStar, although I bet thats pretty much impossible to do. Skyler KD0WHB

2 1

Perform actions based on PL tone
by Skyler F 17 Jan '16

17 Jan '16

Is there any way to perform certain actions based on the CTCSS tone used? It would be cool if I could have one PL tone for local repeat only and another tone for the global repeat through AllStar, although I bet thats pretty much impossible to do. Skyler KD0WHB

1 0

Repeated Errors Showing Up
by R. Wayne 12 Jan '16

12 Jan '16

I consistently get errors that I don’t know what they mean. We are still using ACID and cannot switch just yet to DIAL. Any hints? [Jan 12 08:30:40] WARNING[2348]: chan_iax2.c:921 jb_warning_output: Resyncing the jb. last_delay 3, this delay 131059, threshold 1018, new offset -131059 [Jan 12 08:32:27] WARNING[2352]: chan_iax2.c:921 jb_warning_output: Resyncing the jb. last_delay -8, this delay 65532, threshold 1020, new offset -196591 [Jan 12 08:34:37] WARNING[2350]: chan_iax2.c:921 jb_warning_output: Resyncing the jb. last_delay -11, this delay -196618, threshold 1020, new offset 27 -- Hungup 'Zap/pseudo-**********' -- Hungup 'Zap/pseudo-**********' [Jan 12 09:02:24] WARNING[2346]: chan_iax2.c:921 jb_warning_output: Resyncing the jb. last_delay -9, this delay 1638659, threshold 1020, new offset -1638632 -- Hungup 'Zap/pseudo-**********' When I run –V it just returns Asterisk so I can’t give you the version number.

3 2

Voter Remote Console - Authentication Bypass Bug
by Travis Giedratis 12 Jan '16

12 Jan '16

In the interest of full disclosure, this is final notification regarding an authentication bypass bug for the VOTER Remote Console running on the telnet service.. The specific method of authentication bypass along with other specific data has been scrubbed: root@pentest:~# telnet XX.XX.XX.XX Trying XX.XX.XX.XX... Connected to XX.XX.XX.XX. Escape character is '^]'. VOTER System Serial # XXXX Remote Console Access Login: *<redacted>* Logged in successfully, now joining console session... Select the following values to View/Modify: 1 - Serial # (XXXX) (which is MAC ADDR 00:XX:XX:XX:XX:XX) 2 - VOTER Server Address (FQDN) (XX.XX.XX.XX) 3 - VOTER Server Port (667), 4 - Local Port (Override) (0) 5 - Client Password (XXXX), 6 - Host Password (XXXX) 7 - Tx Buffer Length (3000) 8 - GPS Data Protocol (0=NMEA, 1=TSIP) (1) 9 - GPS Serial Polarity (0=Non-Inverted, 1=Inverted) (0) 10 - GPS PPS Polarity (0=Non-Inverted, 1=Inverted, 2=NONE) (0) 11 - GPS Baud Rate (9600) 12 - External CTCSS (0=Ignore, 1=Non-Inverted, 2=Inverted) (1) 13 - COR Type (0=Normal, 1=IGNORE COR, 2=No Receiver) (0) 14 - Debug Level (10) 15 - Alt. VOTER Server Address (FQDN) () 16 - Alt. VOTER Server Port (Override) (0) 17 - DSP/BEW Mode NOT SUPPORTED 18 - "Duplex Mode 3" (0=DISABLED, 1-255 Hang Time) (1/10 secs) (0) 19 - Simulcast Launch Delay (0) (approx 200 ns, 5 = 1us, > 0 to ENA SC) 97 - RX Level, 98 - Status, 99 - Save Values to EEPROM i - IP Parameters menu, o - Offline Mode Parameters menu q - Disconnect Remote Console Session, r - reboot system, d - diagnostics Enter Selection (1-27,97-99,r,q,d) : __ Isn't this 2016? Why are we still using the telnet service? Any interest in patching this? Travis Giedratis tgiedratis(a)gmx.com

3 2

VOTER Remote Console - Authentication Bypass
by Travis Giedratis 12 Jan '16

12 Jan '16

1 0