.send_text in chan_echolink (local function el_text) is being called multiple times, once for each of any currently connected echolink nodes.

To check this, I put a LOG_NOTICE at the beginning of the method,
I also put a LOG_NOTICE listing all nodes passed to the function

here is the output for one cycle, I have Allstar node 2000 connected, and also echolink node 9999 and echolink node 428425 :

[Aug 26 19:40:11] NOTICE[2291]: chan_echolink.c:1166 el_text: el_text CALLED
[Aug 26 19:40:11] NOTICE[2291]: chan_echolink.c:1206 el_text: R2000
[Aug 26 19:40:11] NOTICE[2291]: chan_echolink.c:1206 el_text: T3009999
[Aug 26 19:40:11] NOTICE[2291]: chan_echolink.c:1166 el_text: el_text CALLED
[Aug 26 19:40:11] NOTICE[2291]: chan_echolink.c:1206 el_text: R2000
[Aug 26 19:40:11] NOTICE[2291]: chan_echolink.c:1206 el_text: T3428425

As RTCM nodes are connected to my hub upwards of 500 hours the connect time display becomes negative. Soon thereafter Asterisk begins to behave erratically and eventually crashes or requires a restart. Disconnecting and reconnecting a RTCM node to prevent exceeding that time prevents related crashes. Guessing this would be a chan_voter issue.

ahp = ast_gethostbyname(EL_APRS_SERVER,&ah);
if (!ahp) {
ast_log(LOG_ERROR, "Unable to resolve echolink APRS server IP address\n");
close(instp->ctrl_sock); instp->ctrl_sock = -1;
close(instp->audio_sock); instp->audio_sock = -1;
return -1;
}

#define EL_APRS_SERVER "aprs.echolink.org"

Apply patches and fixes needed to build asterisk for ASL on Debian. Will also clean out unneeded files and directories.

My nodes crash way too often. A couple of weeks up time is about the best I generally get. A random (non scientific) survey of the stats page reveals similar up times for many nodes. I've had a theory that poor IAX connections have something to do with that. But it was hard to prove, until I found out there is a way to simulate poor network connectivity with the *CLI> iax2 test losspct .

I set up a test bench with three nodes, one acting as a hub for the other two. After connecting with permanent connections I introduced packet loss with the above iax2 CLI. This would generally crash one of the nodes fairly quickly. This would lead one to believe that there is an issue with reconnects.

To test that, I set up a couple of scripts to repeatedly perform regular (not permanent) connects and disconnects. This too will crash a node in rather short order, say within 30 minutes or so. This will cause a crash even without introduced packet loss.

I am fairly convinced there is something, perhaps some connection routine not cleaning up properly, that is causing app_rpt to be much less stable than Asterisk itself. I hope this helps you smart programmers find and solve this up time issue.

Typing "quit" preserves Asterisk CLI history. I would like to see CNTL-C (to exit) do the same. Newer versions of Asterisk do this.

Having problems with core dumps when multiple large hubs connect together.

Same issue as https://community.allstarlink.org/t/asterisk-core-dumps/16050

https://github.com/AllStarLink/Asterisk/blob/2a50097040b89c05312ec0c025d9073003f140df/asterisk/apps/app_rpt.c#L23122

This appears to be relevant output from echo bt | sudo gdb /usr/sbin/asterisk /core

Core was generated by /usr/sbin/asterisk -g -f -C /etc/asterisk/asterisk.conf'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0 0x00007f27b5eb8db6 in rpt_exec (chan=0x7f2788012630, data=) at app_rpt.c:23122

23122 if ((!strncasecmp(l->chan->name,"echolink",8)) ||
[Current thread is 1 (Thread 0x7f277a8b6700 (LWP 5539))]
(gdb) #0 0x00007f27b5eb8db6 in rpt_exec (chan=0x7f2788012630, data=) at app_rpt.c:23122
#1 0x0000000000489173 in pbx_exec (data=0x7f277a8b1cd0, app=0xd70930, c=0x7f2788012630) at pbx.c:537
#2 pbx_extension_helper (c=c@entry=0x7f2788012630, context=context@entry=0x7f2788012880 "radio-secure", exten=exten@entry=0x7f27880128d0 "2560", priority=1, label=label@entry=0x0,
callerid=, action=action@entry=E_SPAWN, con=0x0) at pbx.c:1862
#3 0x00000000004908fc in ast_spawn_extension (callerid=, priority=, exten=0x7f27880128d0 "2560", context=0x7f2788012880 "radio-secure", c=0x7f2788012630) at pbx.c:2317
#4 __ast_pbx_run (c=c@entry=0x7f2788012630) at pbx.c:2406
#5 0x0000000000491499 in pbx_thread (data=data@entry=0x7f2788012630) at pbx.c:2621
#6 0x00000000004c0169 in dummy_start (data=) at utils.c:925
#7 0x00007f27c51f14a4 in start_thread (arg=0x7f277a8b6700) at pthread_create.c:456
#8 0x00007f27c47eed0f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:97
(gdb) quit
`

When the command module unload is executed on chan_echolink, the entire asterisk system crashes.

Multiple occurrences of referring to usbradio where it should be simpleusb. Some in simple messages and some in actual code.

CD=Channel Driver

Steve N4IRS

Hi.

It would be useful if Allstarlink had chan_alsaradio

https://github.com/KR4DIO/chan_alsaradio/blob/master/yu3iio_blog.md

https://github.com/KR4DIO/chan_alsaradio

Generate and detect DCS in DSP based channel drivers.

When we use echolink Android application to connect echolink node running on Allstarlink always in status node ASL display wrong number echolink node connected to ASL. For example, my echolink node is 926515 and when I connect to my ASL echolink node in status "Node currently connected to us" is showed number 3437911. When I look at http://echolink.org/logins.jsp I found that echolink number node 437911 belongs to KO4AVA. When I disconnect and connect again to ASL the my number EL was changed to another 3876316 and when I check on EL status page I found that the number belongs to DV2EVE.

But when I use the software PC version echolink the number my echolink node in status ASL is correct 3926515.

Does it look like bug ASL which not properly get information about connected number EL node with the station who uses EL Android application?

Would be nice to have MDC1200 encode/decode capabilities as well as the notch filter feature uncommented and enabled by default in app_rpt.c

With the changes that have been merged into the master and develop branches recently, I was wondering at what point these would be re-synched? Master seems to have some commits that develop does not.

Please consider adding a kerchunk filter (i.e. kerchunk_timer and kerchunk_timeout parameters) to the rx channel drivers. This would work like what is found on many repeater controllers such as those from LinkComm. That is, it takes a user defined period (i.e. kerchunk_timer) of receiver activity (COR+CTCSS) to first activate the receiver. Thereafter the activation would be zero (or rxondelay) as long as there is receiver activity. After a user defined period of inactivity (i.e. kerchunk_timeout), receiver activation would revert to kerchunk_timer activation.

Need to add information to the readme and remove dated information.

Constantly getting following error when many nodes are connected.
[May 13 00:56:15] WARNING[16669]: app_rpt.c:4303 linkcount: maximum number of links exceeds 32 in rpt_do_stats()!

Need to change
#define MAX_STAT_LINKS 32
in app_rpt.c to
#define MAX_STAT_LINKS 128

I have had a few requests to increase the size of the the permit and deny list in EchoLink.
It is currently defined at 30. I propose we increase it to 60 or above. the value is set at:
#define EL_MAX_CALL_LIST 30

Steve N4IRS

Add custom audio filters
Implement feature for usbradio to:

• rxlpf: Receiver Audio Low Pass Filter
• rxhpf: Receiver Audio High Pass Filter
• txlpf: Transmitter Audio Low Pass Filter
• txhpf: Transmitter Audio High Pass Filter

Add the ability for simpleUSB and USBradio to use a serial port for COS/CTCSS/PTT. Example would be to use DTR for PTT and DSR for COS. Would still require external buffer hardware.