Help - Are the ASL3 Courtesy Tones or RC210?

I'm trying to figure out where these tones are coming from. I'm trying to do this so I can set a different custom courtesy tone, but I can't seem to get rid of them so only my custom courtesy tone plays.

I'm just getting my feet wet with ASL3, and I'm probably missing something along the way.

System architecture:
Raspberry Pi 4B with Repeater Builder RIM Lite connected to Repeater Builder RC210R port 2. Port 1 of the RC210 is connected to a Bridgecom BCR-40U.
BCR-40u courtesy tones and IDs are disabled.
All RC210 courtesy tones and IDs are disabled, as I want to use the ASL3 for all IDs and CTs.

Unknown origin courtesy tone 1 - https://files.catbox.moe/dca95o.mp3
Unknown origin courtesy tone 2 - https://files.catbox.moe/wl5nwf.mp3

My friend insists these are not ASL3 and that the RC210 is injecting these tones, but I've gone through the RC210 and turned off all CT. I've also turned off all BCR-40U courtesy tones as well.

Do you recognize these as ASL3 CTs? If so, where are they enabled in the ASL3 configuration so I can disable them?

Thank you and 73's!!!

Karl, K0EG

Version info:
OS : Debian GNU/Linux 13 (trixie)
OS Kernel : 6.18.39+rpt-rpi-v8

Asterisk : 22.9.0+asl3-3.9.3-1.deb13
ASL [app_rpt] : 3.9.3

Installed ASL packages :

Package Version
============================== ==============================
allmon3 1.9.1-1.deb13
asl3 3.18.2-2.deb13
asl3-appliance 2.1.0-2.deb13
asl3-appliance-pi 2.1.0-2.deb13
asl3-asterisk 2:22.9.0+asl3-3.9.3-1.deb13
asl3-asterisk-config 2:22.9.0+asl3-3.9.3-1.deb13
asl3-asterisk-modules 2:22.9.0+asl3-3.9.3-1.deb13
asl3-menu 1.18-1.deb13
asl3-update-nodelist 2.0.0-1.deb13
asl-apt-repos 2.0-1.deb13
cockpit 337-1+deb13u2
cockpit-bridge 337-1+deb13u2
cockpit-networkmanager 337-1+deb13u2
cockpit-packagekit 337-1+deb13u2
cockpit-sosreport 337-1+deb13u2
cockpit-storaged 337-1+deb13u2
cockpit-system 337-1+deb13u2
cockpit-wifimanager 1.2.0-1.deb13
cockpit-ws 337-1+deb13u2
dahdi 1:3.1.0-2.1
dahdi-linux 1:3.4.0-11.asl.deb13

The tones are located in the rpt.conf file. I have never messed with them. They are in the telemetry-main stanza. It will look like this.
ct1 = |t(350,0,100,2048)(500,0,100,2048)(660,0,100,2048)
ct2 = |t(660,880,150,2048)
ct3 = |t(440,0,150,4096)
ct4 = |t(550,0,150,2048)
ct5 = |t(660,0,150,2048)
ct6 = |t(880,0,150,2048)
ct7 = |t(660,440,150,2048)
ct8 = |t(700,1100,150,2048)

I am not sure if you could point these to your customer tones or not. So for example unlinkedct = ct2 you could change ct2 like so
ct2 = |t(660,880,150,2048) to ct2 = |/folder/nameoftone.mp3 ...or whatever extension you use. Maybe someone who has fiddled with them more could chime in some.

Or if that don't work you could disable them all together with ; at the beginning and see what that does.
;ct1 = |t(350,0,100,2048)(500,0,100,2048)(660,0,100,2048)
;ct2 = |t(660,880,150,2048)
;ct3 = |t(440,0,150,4096)
;ct4 = |t(550,0,150,2048)
;ct5 = |t(660,0,150,2048)
;ct6 = |t(880,0,150,2048)
;ct7 = |t(660,440,150,2048)
;ct8 = |t(700,1100,150,2048)

The first tone sounds exactly like the standard ASL CT for when you're connected to other nodes (or your hardware controller has recreated the exact same courtesy tone). Can't help you the second one.

Why don't you go into the telemetry generator on the web portal and play around with the tones?

Help & Tools->Telemetry Generator

I used that to modify my courtesy tone so it sounds like a standard Motorola tone remote. So coool...

(MEE-nip!)

Did some playing around because I was literally waiting for paint to dry but for the dca950.mp3 i think it will be

|t(1633,0,50,3000)(0,0,80,0)(1209,0,50,3000)

and for the file wl5nfw.mp3 it might be

|t(2170,0,75,3000)(0,0,80,0)(1650,0,50,3000)

It might be close though

AllStarLink | Telemetry Builder Try it out for yourself