mike « The Midnight Engineer

COP iLink Status and Remote Command List

A Internal Command list For app_rpt (incomplete) More is added from time to time. Some,not all default assignments shown.

An important note that I’m going to repeat for those that stumbled on this page without having read the others:

It is important to “organize” your commands so that you do not partially “dupe” a command.

I suggest keeping them in numerical order so it can be easily seen. Here is a example:

8900=cop,24 ; cancel localplay stream +/- telemetry

8901=localplay,/var/lib/asterisk/sounds/wx/wxfc ;my custom wx script player example

8902=localplay,/var/lib/asterisk/sounds/wx/wxalert ;my custom wx alert script player example

90=cop,1 ;warm boot 91=cop,2 ; System enable – you should not comment these out in a live system 92=cop,3 ; System disable

99=cop,6 ; Remote sip/telephone PTT key command (# to unkey)

If I were to assign a command of *89 to anything, the above 4 digit 8901, 8902 would never execute. Unlike conventional controllers, asterisk […]

app_rpt COS and PTT through Parallel Port

This skinny direction set is only for the ACID distribution of app_rpt. (may be valid for other distros ?)

Using the Parallel port for radio COS / PTT is the cheapest and easiest route to go unless you want to hack-up a USB sound dongle that we will not talk about here. If you wish to do that see this link / PDF.

When using parallel port pins for any logic connections most especially experimental ones, I always suggest using something to buffer the lines in the printer/parallel port so that you do not do more damage than to just the port of your PC if higher voltage gets to one of the pins.

Parallel Port Breakout card with Opto-Coupled Transisters on output.

When I had built a DOS box repeater in the 90’s, I used a opto-coupled transistors to isolate the pins. Now-A-Days you can save yourself […]

EchoLink Configuration for app_rpt

As with all our “skinny” guides on app_rpt, we speak only of the ACID distribution.

In your /etc/asterisk directory you will find a echolink.conf file.

This is the only file you need to edit for a working system to enable echolink connections via one of your allstar defined (or private defined) nodes. You “can” configure this to a node that is not your repeater node. When you want echolink connectivity, just connect your node to it or use a startup macro to maintain it from startup. The reason one might want to do it this way is that you will have the ability to disconnect from echolink connectivity. It can be desirable in some situations. You can not disconnect it from the assigned node.

File contents:

[el0] ; echolink definition 1 (computer logic 0=1) confmode=yes ; enable conference mode yes or no – allows multi-connections call=YOURelCALL-r ; Your echolink callsign, […]

app_rpt Macro and Scheduler

First I should lightly define this for those that do not understand.

A MACRO is a single or multiple set of commands to be executed by a single simple command.

You could use it to have a user command that executes a string of commands making the entire function easy to preform for any user. An example would be to make several link connections with just a 4 digit macro command. It is all about what you put in the MACRO.

To my knowledge, you can not make a macro do anything you could not do with a command directly because you are entering actual commands to be executed. Need more… You can execute a system/asterisk command line that would make just about anything possible within a script file but it has to be defines as a command first. Use your macro to call that command

Set-up for these are […]

Doug Hall RBI-1 Remote Base Interface

The Doug Hall RBI-1 is a serial device but is NOT rs232. I made a program in a controller years ago (90’s) so I do understand how to talk to the interface as a programer but knowing it was already built in to the app_rpt software, I could not find it documented anywhere. If you have hooked this up to a traditional controller, you know it has a “serial data” line, “serial clock” line (sometimes called a strobe line) and a “reset line”. You will need to use the parallel port of your computer to talk to the RBI-1 That parallel port will need to be a built-in port or a add-on card but not a usb converted parallel port. They do not seem to support pin punching in Linux. Pin-2 is the data line Pin-3 is the clock/strobe Pin-4 is the reset line (not required but suggested) I had […]

Testing Our app_rpt config with Commands

If you got here from a search engine and want to start from the beginning CLICK HERE

I would advise that you do not change any command unless you have good reason and some experience with the system.

Also, Before proceeding, make sure you have printed a list of the commands from your rpt.conf file so your sure, if you changed anything, that your using the correct assigned command.

If you have created a sip/iax phone extension, or have radio connections, lets test things out !

From sip/iax phone:

First, call your extension (example 29283)

You will hear – 2,9,2,8,3, – This depends on what you placed in the [radio-control] context of extensions.conf. You could have it playback your callsign/repeater.

Your are now connected to your node and may issue it commands as if you were on the radio.

*99 will key the transmitter and your audio will pass.

# […]

The Midnight Engineer