In the node configuration: ;remote = ft897 ; Set remote=y for dumb remote or ; remote=ft897 for Yaesu FT-897 or ; remote=rbi for Doug Hall RBI1 Mine looks like this: [9999] duplex=0 txchannel = Zap/95 rxchannel = Zap/96 ;remote=y functions = functions-repeater link_functions = functions-different tonezone = us context = cos1 callerid = "Repeater" <6128217300> idrecording = silence/1 accountcode=RADIO funcchar = * endchar = # hangtime=1000 totime=180000 idtime=300000 politeid=30000 idtalkover=|itest unlinkedct=ct2 Quoting Steve Rodgers <hwstar@rodgers.sdcoxmail.com>:
Shane,
Your last message has me confused. The remote keyword in the node configuration block does not take a 'y' or 'n' value. Did you mean the node entry in the [NODES] section: 1234=radio@somenode.org/1234,somenode.org,y?
Steve.
On Wednesday 26 July 2006 22:35, Shane Young KØSEY wrote:
I started playing some more with mine tonight. I have a couple of the ARIBs and CAC channel banks.
If I set a node to "remote=y" I am not able to dial into it using the "dumb" mode, I was only able to do that if I had "remote=n".
My paging project nearly working correctly. The only problem I have no way to prevent my end from transmitting when there is carrier on the radio. This is necessary for shared channel stuff.
My goal I think is similar to yours, but I think you are attacking it from a different perspective.
My project will (hopefully) function like this:
Dial a paging access number. enter the pager ID or CAP Code. Hear a beep Record your message Hang up
This will create a file in /var/spool/asterisk/outgoing which will "dial" app_rpt in "dumb" mode, send out the tones for the CAP code you entered and play the message back.
By doing it this way, the radio is never connected to the PSTN, this elimnating restrictions of some services.
Again, this is only going to work correctly if I can somehow determine that their is carrier and "wait" before transmitting.
It's hotter than hell here in Tropical Minnesota lately. My work area is not air conditioned, so I don't spend too much time working on this, but I got quite a bit closer tonight.
I don't remember if it was you or someone else who asked about cheap radios. Midland XTR's are fairly cheap on fleabay and I think I've figured out where to tap TX/RX audio and PTT/COR on the board.
Quoting Shane Burrell <shaneb@metrostat.net>:
An update. After digging into the Tk-880 I noticed that either you must use the internal or external speaker connector so I just bridged the output wire onto the internal speaker wire. Now when I dial 390 I can hear the Tk-880. Still don't have transmitting working.
-----Original Message----- From: app_rpt-bounces@lists.illiana.net [mailto:app_rpt-bounces@lists.illiana.net] On Behalf Of Shane Burrell Sent: Wednesday, July 26, 2006 11:12 AM To: 'Asterisk Repeater Controler' Subject: Re: [App_rpt] Getting app_rpt base node to work.
First thanks to everyone for all your help thus far. I have the DPO setting and now when I do dial the 390 I hear something but it's not understandable. Also I can't seem to get the TX light to come on with the DPO set. I think I may have a problem with the way the TK-880 is setup. I'm using the KCT-19 accessory adapter but the service manual has a few jumpers on it and no so clear documentation. I'm wandering about the PTT and also if the speaker out is working on the TK-880 they way I expect it to. Any experience with the TK-880? Also is there another cheap radio that would be easier to interface with?
Regards,
Shane
-----Original Message----- From: app_rpt-bounces@lists.illiana.net [mailto:app_rpt-bounces@lists.illiana.net] On Behalf Of Steve Rodgers Sent: Tuesday, July 25, 2006 10:04 PM To: Asterisk Repeater Controler Subject: Re: [App_rpt] Getting app_rpt base node to work.
Shane,
1. the red light is turning on, the radio should transmit, that is, unless:
The radio PTT interface is not correct. Most radios ley their transmitter when PTT is connected to ground. Check the manual for your radio to verify that this is the case before proceeding.
If you have verified that your radio needs to see a ground on PTT to transmit, then make sure JP4 is installed (to connect the other side of the PTT relay to ground), force the red TX light to light by plugging it in to your channel bank as you mentioned in the prior message.
If your radio still won't transmit when the red light is on, then turn off the radio and check the for continuity between pins 7 and 8 on the ARIB radio interface connector with a meter. There should be no continuity when the red
light is off, and continuity when the red light is on. Be sure you are measuring between pins 7 and 8 on the connector.
If the red light comes on and there is continuity between pins 7 and 8, your
radio should key its transmitter in this case. If it still doesn't, then you
need to go back and check your connections to the radio and/or verify that it is designed to key its transmitter when the PTT line is grounded.
2. Adtran TA750 needs to be set up for DPO not tandem(E&M). The E&M setting
is only intended to be set in the Asterisk configuration. Please refer to the TA 750 manual to configure it for DPO mode.
Steve.
On Tuesday 25 July 2006 11:13, Shane Burrell wrote:
I have setup the TA 750 for tandem(E&M) and verified all below. When I plug the RJ-11 into J1 the TX light illuminates. Radio is not
transmitting
at any time. Also when I key up from anther radio the base does cause the COR light to illimunate on the ARIB. When I dial the 390 extension to hit the base I get nothing but talk battery sound on the SIP phone and this in the asterisk log.
Jul 25 14:13:38 WARNING[6720]: chan_sip.c:2731 sip_indicate: Don't know
how
ndicate condition 13 Jul 25 14:13:38 WARNING[6720]: channel.c:2064 ast_indicate: Unable to handleication 13 for 'SIP/2-08166720' Jul 25 14:13:40 WARNING[6720]: chan_sip.c:2731 sip_indicate: Don't know
how
ndicate condition 13 Jul 25 14:13:40 WARNING[6720]: channel.c:2064 ast_indicate: Unable to handleication 13 for 'SIP/2-08166720'
-----Original Message----- From: app_rpt-bounces@lists.illiana.net [mailto:app_rpt-bounces@lists.illiana.net] On Behalf Of Steve Rodgers Sent: Monday, July 24, 2006 9:02 PM To: Asterisk Repeater Controler Subject: Re: [App_rpt] Getting app_rpt base node to work.
JP1 and JP2 need to be removed.
Steve.
On Monday 24 July 2006 11:13, Shane Burrell wrote:
Do I leave J1 jumpers connected for 2W?
-----Original Message----- From: app_rpt-bounces@lists.illiana.net [mailto:app_rpt-bounces@lists.illiana.net] On Behalf Of Steve Rodgers Sent: Friday, July 21, 2006 10:10 PM To: Asterisk Repeater Controler Subject: Re: [App_rpt] Getting app_rpt base node to work.
Shane,
Since you are running as a half duplex remote base please verify the following:
1. The ARIB card needs to have the 4W/2W switch set to 2W (2 wire).
2. Only one cable should be connected from the channelbank to the ARIB card.
This should go from the port on the channel bank equivalent to Zap/25 to
J1
on the ARIB card.
3. There should not be a txchannel defined in the nodes section of rpt.conf.
4. Since you are running as a remote base, you must add a 'y' argument
to
the end of the node definition, like this: 101 = radio@me.asterisk.net/101,y
5. /etc/asterisk/zapata.conf should have em_txrx for signalling on Zap/25.
6. /etc/zaptel.conf should have channel type for Zap/25 set to e&m
If after verifying the above items and you still have problems:
1. The Sangoma T1 card must be able to talk to the channel bank to control the DPO port operation. We have not tested the Sangoma T1 cards with app_rpt and
cannot confirm if they support DPO operation through Zaptel.
Steve.
On Friday 21 July 2006 16:20, Shane Burrell wrote:
It does light the red light.
-----Original Message----- From: app_rpt-bounces@lists.illiana.net [mailto:app_rpt-bounces@lists.illiana.net] On Behalf Of hwstar@rodgers.sdcoxmail.com Sent: Friday, July 21, 2006 6:29 PM To: Asterisk Repeater Controler Subject: Re: [App_rpt] Getting app_rpt base node to work.
Swap the jacks and tell me if you get a red tx light. Connecting the
RX
into the TX port on the ARIB should light the TX LED.
From what I can deduce, it looks like the modular cables from your
channel
bank are flipping the polarity of tip and ring. The ARIB is polarity sensitive and will do exactly what you have described if the polarity is wrong.
Make up a new set of modular cables which swap the red and green wires
in
the opposite manner to the cables you are currently using.
Steve.
From: "Shane Burrell" <shaneb@metrostat.net> Date: 2006/07/21 Fri PM 01:08:42 PDT To: "'Asterisk Repeater Controler'" <app_rpt@lists.illiana.net> Subject: Re: [App_rpt] Getting app_rpt base node to work.
Now that I have rpt loading I can't seem to figure out how to get
the
base to key up. I think I have a combo of problems with my config and ARIB interface.
I have a Sangoma A104D with second T1 channels 1 and two configured.
One
is
LS other is GS. The goto a TA 750 into the ARIB. I have set to 4W and jumpers 1 and 2 removed. The ARIB is connected to the KCT-19 pigtal
on
my Kenwood TK-880. I see the COR light come on when I receive a transmission. So far so good.
When I setup a exten to rpt|P it just gets dead air and doesn't
transmit.
I
assumed that at this point I could dial *X out of the function list
and
have
it do something but it doesn't. Also no audio occurs on the phone
if
the
radio is receiving but the COR light does work.
Any pointers or next step? I've dug thru the docs and most of what
I
see
is
for repeaters. I just want to hit a base and send some tones. Maybe
an
annoucment or two.
TIA,
SHane
-----Original Message----- From: app_rpt-bounces@lists.illiana.net [mailto:app_rpt-bounces@lists.illiana.net] On Behalf Of Shane
Burrell
Sent: Friday, July 21, 2006 1:48 PM To: 'Asterisk Repeater Controler' Subject: Re: [App_rpt] Getting app_rpt base node to work.
I figured out I have to restart asterisk. Now I get dial and get
blank
air.
My goal is to dial a number and have it send out some 2 tone. I would settle for DTMF. Is there a DTMF command I need to issue to take over/PTT the base?
-----Original Message----- From: app_rpt-bounces@lists.illiana.net [mailto:app_rpt-bounces@lists.illiana.net] On Behalf Of Jim Duuuude Sent: Friday, July 21, 2006 1:43 PM To: app_rpt@lists.illiana.net Subject: Re: [App_rpt] Getting app_rpt base node to work.
How about remote=y
It doesnt recognize remote=dump, and thinks it a node and wants an idrecording specified.
From: "Shane Burrell" <shaneb@metrostat.net> Reply-To: Asterisk Repeater Controler <app_rpt@lists.illiana.net> To: "'Asterisk Repeater Controler'" <app_rpt@lists.illiana.net> Subject: Re: [App_rpt] Getting app_rpt base node to work. Date: Fri, 21 Jul 2006 13:24:34 -0400 MIME-Version: 1.0 Received: from lists.illiana.net ([207.227.243.140]) by bay0-mc8-f19.bay0.hotmail.com with Microsoft
SMTPSVC(6.0.3790.2444);
Fri,
21 Jul 2006 10:24:41 -0700 Received: (qmail 3845 invoked from network); 21 Jul 2006 17:24:40 -0000 Received: from localhost (HELO ?127.0.0.1?) (127.0.0.1) by
0
with
SMTP;
21
Jul 2006 17:24:40 -0000 Received: (qmail 3828 invoked from network); 21 Jul 2006 17:24:37 -0000 Received: from mail.metrostat.net (HELO mx1.metrostat.net)
(152.53.16.15)by
0 with SMTP; 21 Jul 2006 17:24:37 -0000 Received: by mx1.metrostat.net (Postfix, from userid 1003)id
2FB4F26900CC;
Fri, 21 Jul 2006 13:24:20 -0400 (EDT) Received: from compmst (unknown [152.53.16.10])by mx1.metrostat.net (Postfix) with ESMTP id D42CD26900BBfor
<app_rpt@lists.illiana.net>;
Fri,
21 Jul 2006 13:24:16 -0400 (EDT) X-Message-Info: LsUYwwHHNt3NYSfb1sbees3Ik0t50SZpLw6VgEAXI2s= Return-Path: <shaneb@metrostat.net> Delivered-To: mailman-app_rpt@lists.illiana.net X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on mx1.metrostat.net X-Spam-Level: X-Spam-Status: No, score=0.0 required=5.5 tests=none autolearn=disabled version=3.1.0 X-Mailer: Microsoft Office Outlook 11 Thread-Index: Acas6IDNhxKN9qu6Qai9iAm0lrd/ggAAdqzw X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2869 X-BeenThere: app_rpt@lists.illiana.net X-Mailman-Version: 2.1.6 Precedence: list List-Id: Asterisk Repeater Controler <app_rpt.lists.illiana.net> List-Unsubscribe:
<http://lists.illiana.net/mailman/listinfo/app_rpt>,<mailto:app_rpt-requ es
t @lists.illiana.net?subject=unsubscribe>
List-Archive: <http://lists.illiana.net/pipermail/app_rpt> List-Post: <mailto:app_rpt@lists.illiana.net> List-Help: <mailto:app_rpt-request@lists.illiana.net?subject=help> List-Subscribe:
<http://lists.illiana.net/mailman/listinfo/app_rpt>,<mailto:app_rpt-requ es
t @lists.illiana.net?subject=subscribe>
Errors-To: app_rpt-bounces@lists.illiana.net X-OriginalArrivalTime: 21 Jul 2006 17:24:41.0409 (UTC) FILETIME=[8CF8FB10:01C6ACEA]
Still get rpt_exec: Cannot find specified system node 101. my rpt.conf
is
as follows:
[101] ; Node ID of remote base rxchannel = Zap/25 ; Rx audio/signalling
channel
txchannel = Zap/26 ; Tx audio/signalling
channel
functions = functions-remote remote = dumb ; Set remote=y for dumb
remote or
; remote=rbi for Doug Hall
RBI1
[functions-remote] 0=remote,1 ; Retrieve Memory 1=remote,2 ; Set freq. 2=remote,3 ; Set Rx PL tone. 40=remote,100 ; Rx PL off 41=remote,101 ; Rx PL on 42=remote,102 ; Tx PL off 43=remote,103 ; Tx PL on 44=remote,104 ; Low Pwr 45=remote,105 ; Med Pwr 46=remote,106 ; Hi Pwr 5=remote,5 ; Status
[telemetry]
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,2048) 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) remotetx=|t(2000,0,75,2048)(0,0,75,0)(1600,0,75,2048); remotemon=|t(1600,0,75,2048) cmdmode=|t(900,903,200,2048) functcomplete=|t(1000,0,100,2048)(0,0,100,0)(1000,0,100,2048)
[morse] speed=20 ; Approximate speed in WPM frequency=800 ; Morse Telemetry Frequency amplitude=4096 ; Morse Telemetry Amplitude idfrequency=330 ; Morse ID Frequency idamplitude=2048 ; Morse ID Amplitude
[nodes]
;000 = context_A@1.2.3.4/1234 101 = radio@me.asterisk.net/101
;of course, you can also specify these with domain names, but why
rely
;on DNS working unnecessarily?
[memory]
;; this example gives you 146.460, simplex, 100.0 HZ PL, hi-power,
transmit
PL 00 = 146.460,100.0,sht ;; this example gives you 146.940, minus offset, 100.0 HZ PL,
low-power,
no
PL 01 = 146.940,100.0,-l
; The format for these entries is: Receive-Freq,Receive-PL,Attrbutes ; Attributes: l=low power, m=medium power, h=high power, -=minus offset, ; s=simplex, +=plus offset, t=tx PL enable, r=rx PL enable
-----Original Message----- From: app_rpt-bounces@lists.illiana.net [mailto:app_rpt-bounces@lists.illiana.net] On Behalf Of hwstar@rodgers.sdcoxmail.com Sent: Friday, July 21, 2006 1:10 PM To: Asterisk Repeater Controler Subject: Re: [App_rpt] Getting app_rpt base node to work.
Shane,
1. Node numbers with leading zeroes are reserved. Try using 101
instead.
2. The node number needs to be defined in 2 places in the rpt.conf
file.
Once in the repeater section with square brackets e.g. [101] and once
in
the [NODES] section as an entry to connect to/from:
radio@127.0.0.1/101,127.0.0.1
Steve.
From: "Shane Burrell" <shaneb@metrostat.net> Date: 2006/07/21 Fri AM 10:04:30 PDT To: <app_rpt@lists.illiana.net> Subject: [App_rpt] Getting app_rpt base node to work.
I've tried to setup a base node using a kenwood TK-880 and
analog
radio
board. Asterisk reports that rpt_exec: Cannot find specified system
node
001. I have 001 defined using the example base node. Is there
something I
am missing. Does app-rpt require more than a reload to get its configuration?
Regards,
Shane
_______________________________________________ App_rpt mailing list App_rpt@lists.illiana.net http://lists.illiana.net/mailman/listinfo/app_rpt
_______________________________________________ App_rpt mailing list App_rpt@lists.illiana.net http://lists.illiana.net/mailman/listinfo/app_rpt
_______________________________________________ App_rpt mailing list App_rpt@lists.illiana.net http://lists.illiana.net/mailman/listinfo/app_rpt
_______________________________________________ App_rpt mailing list App_rpt@lists.illiana.net http://lists.illiana.net/mailman/listinfo/app_rpt
_______________________________________________ App_rpt mailing list App_rpt@lists.illiana.net http://lists.illiana.net/mailman/listinfo/app_rpt
_______________________________________________ App_rpt mailing list App_rpt@lists.illiana.net http://lists.illiana.net/mailman/listinfo/app_rpt
_______________________________________________ App_rpt mailing list App_rpt@lists.illiana.net http://lists.illiana.net/mailman/listinfo/app_rpt
_______________________________________________ App_rpt mailing list App_rpt@lists.illiana.net http://lists.illiana.net/mailman/listinfo/app_rpt
_______________________________________________ App_rpt mailing list App_rpt@lists.illiana.net http://lists.illiana.net/mailman/listinfo/app_rpt
_______________________________________________ App_rpt mailing list App_rpt@lists.illiana.net http://lists.illiana.net/mailman/listinfo/app_rpt
_______________________________________________ App_rpt mailing list App_rpt@lists.illiana.net http://lists.illiana.net/mailman/listinfo/app_rpt
_______________________________________________ App_rpt mailing list App_rpt@lists.illiana.net http://lists.illiana.net/mailman/listinfo/app_rpt
_______________________________________________ App_rpt mailing list App_rpt@lists.illiana.net http://lists.illiana.net/mailman/listinfo/app_rpt
---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program. _______________________________________________ App_rpt mailing list App_rpt@lists.illiana.net http://lists.illiana.net/mailman/listinfo/app_rpt
App_rpt mailing list App_rpt@lists.illiana.net http://lists.illiana.net/mailman/listinfo/app_rpt
---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program.