Rpt()
Synopsis
Rpt(NODE) -OR-Rpt(Options)
Options are as follows:
Not specifying an option and specifying a node puts it in normal endpoint mode (where source IP and nodename are verified).
Rannounce-string[|timeout[|timeout-destination]] - Amateur Radio
Reverse Autopatch. Caller is put on hold, and announcement (as
specified by the 'announce-string') is played on radio system.
Users of radio system can access autopatch, dial specified
code, and pick up call. Announce-string is list of names of
recordings, or \"PARKED\" to substitute code for un-parking,
or \"NODE\" to substitute node number.
P - Phone Control mode. This allows a regular phone user to have
full control and audio access to the radio system. For the
user to have DTMF control, the 'phone_functions' parameter
must be specified for the node in 'rpt.conf'. An additional
function (cop,6) must be listed so that PTT control is available.
D - Dumb Phone Control mode. This allows a regular phone user to
have full control and audio access to the radio system. In
this mode, the PTT is activated for the entire length of the call.
For the user to have DTMF control (not generally recomended in
this mode), the 'dphone_functions' parameter must be specified
for the node in 'rpt.conf'. Otherwise no DTMF control will be
available to the phone user.
Rannounce-string[|timeout[|timeout-destination]] - Amateur Radio
Reverse Autopatch. Caller is put on hold, and announcement (as
specified by the 'announce-string') is played on radio system.
Users of radio system can access autopatch, dial specified
code, and pick up call. Announce-string is list of names of
recordings, or \"PARKED\" to substitute code for un-parking,
or \"NODE\" to substitute node number.
P - Phone Control mode. This allows a regular phone user to have
full control and audio access to the radio system. For the
user to have DTMF control, the 'phone_functions' parameter
must be specified for the node in 'rpt.conf'. An additional
function (cop,6) must be listed so that PTT control is available.
D - Dumb Phone Control mode. This allows a regular phone user to
have full control and audio access to the radio system. In
this mode, the PTT is activated for the entire length of the call.
For the user to have DTMF control (not generally recomended in
this mode), the 'dphone_functions' parameter must be specified
for the node in 'rpt.conf'. Otherwise no DTMF control will be
available to the phone user.
Return values
N/A
Description
This module enables Asterisk to connect Amateur Radio or Commercial 2-way repeater systems together. The application is distributed in the Asterisk source package as app_rpt.c. There are 3 different hardware interfaces supported by app_rpt:
- FXS interfaces with modified signalling and an Analog Radio Interface Board (ARIB). http://qrvc.com/radiocards.html
- Quad Radio PCI card. http://qrvc.com/radiocards.html
- A modified USB sound fob which uses a CM108 chip. This requires the chan_usbradio.c channel driver be compiled and configured. http://app-rpt.qrvc.com/usbsoundfob.html
Some of its features include:
- Autopatch via VOIP or PSTN, with 2 Reverse Autopatch modes.
- Autonomous VHF and HF remote base. Works independently from repeaters at the same site.
- Supervisory control via dial-in over inbound VOIP connection or phone line
- May be used with our Windows and Linux GUI program iaxrpt for PC-based dispatch.
- Support for ISP's using Static and Dynamic IP addresses.
- Multiple repeaters can be concurrently controlled with app_rpt and one Asterisk box.
- All linking is done in full duplex using IAX2.
- Designed to be a fully functional repeater controller, not as an adjunct like IRLP and Echolink.
- No reflectors are required. Each node has full conferencing capability.
- NAT-Friendly. Only one port for IAX2 (4569) needs to be opened on your firewall.
- The system owner decides which systems can link to to his repeater (and who doesn't). Authentication is not centralized or controlled by any entity.
- The system owner decides on the security scheme. All IAX2 security methods are available (MD5 and RSA) . IP addresses can be looked up in DNS and matched against a symbolic Internet address (FQDN)
- Linked systems are immune to lockup if looped. All DTMF control information is sent out-of-band over the VOIP links.
- Only 2 Audio level adjustments per-node are necessary (RX and TX audio at each node).
- Programmable tail messages
- Selectable Full Duplex or Half-duplex operation on repeater ports.
See also
- Asterisk config rpt.conf: The RPT config file
- Radio: Radio & Voice over IP linkages
Further instructions on the adapter board hardware design, and latest news on the software development of app_rpt.c, click on the following: http://app-rpt.qrvc.com/index.html
Asterisk | Applications | Functions | Variables | Expressions | Asterisk FAQ
Comments
333
333rpt.conf link seems to be broken
http://www.voip-info.org/wiki/view/Asterisk+config+rpt.conf
333
1. There are too many sound cards out there to support them all
2. Not all sound cards are full duplex. App_rpt needs a full duplex interface, as it is a repeater controller.
3. Sound cards have lousy 3.5mm plugs which fail in an intermittent manner.
4. The guts of app_rpt are designed to work with zaptel devices. A rewrite to support a non-zaptel device would be a major undertaking.
5. The soft volume controls in the sound card mixing software can be easily disturbed.
6. Parallal ports and serial ports are going away on newer PC's and will not be avialable in the future.
333Asterisk & IRLP for Ham Radio?
I have IRLP hardware, and that also runs on Linux. Wouldn't it be nice if there was an application that would provide the inter-operability in much the same manor we have added support for Echolink?
Many repeaters already analog phone lines to tie in remote receive sites and so on... Just a thought. I'm not sure what would all be involved, but I would like to get a clearer picture of that.
References:
http://groups.yahoo.com/group/irlp/
http://groups.yahoo.com/group/EchoIRLP/
http://groups.yahoo.com/group/asterisk_radio/
http://www.irlp.net/
333Why not a soundcard?
I'm totally blown away that this is not being done with a soundcard and PTT via serial port or parallel port pins.
In the spirit of ham radio, saving cost and doing this with inexpensive items on hand....
But no... you need to spend several $100's on a radio interface board and TWO FXS ports just to support a radio port.
I'm confused.
Sure that's great to use higher quality 'telco' equipent as it is stated but I would like a simple port to my home radio
remote base.
What would be involved in getting app_rpt to work the same way but with tx/rx audio on sound card and PTT and COR on serial/LPT port? instead?
I do not program in C so I need some help in getting this done.
Many would use this if someone would write it as an option or add on for app_rpt.
SG
333Using the Dingotel Adapter
333FRS GMRS Interfaces ?
http://www.voip-info.org/tiki-index.php?page=Asterisk%20cmd%20Rpt
does anyone know of an open source effort the allows a VoIP SIP, IAX h323 client to interface to a simple frs/gmrs handset like
Motorola t7400 or the uniden GMR1088-2CK
in a similar manner to the the dingotel.com usb - radio mic
http://www.dingotel.com/2way/about2way.asp
333hamlib?