[App_rpt-users] FW: Asterisk reboots-Clocking error
Mark DuMoulin @ WB2ERS
wb2ers at metcom.com
Tue Nov 17 11:21:59 EST 2015
From: Mark DuMoulin
Sent: Tuesday, November 17, 2015 11:21 AM
To: 'Tim Sawyer' <tisawyer at gmail.com>; Mark DuMoulin @ WB2ERS <wb2ers at metcom.com>
Cc: app_rpt-users at ohnosec.org
Subject: RE: [App_rpt-users] Asterisk reboots-Clocking error
We put the macro in place.
Asterisk was reloaded and Hard booted.
Still no connection between the two “repeaters” in rpt.conf.
Is [node] supposed to be part of this?
From: Tim Sawyer [mailto:tisawyer at gmail.com]
Sent: Friday, November 13, 2015 6:53 PM
To: Mark DuMoulin @ WB2ERS <wb2ers at metcom.com<mailto:wb2ers at metcom.com>>
Cc: app_rpt-users at ohnosec.org<mailto:app_rpt-users at ohnosec.org>
Subject: Re: [App_rpt-users] Asterisk reboots-Clocking error
Reading you post again; if what you want to do is just have an RTCM and a URI you have to have two nodes. One for the URI and one for the RTCM.
duplex=2 # for repeater
# connect URI to RTCM at startup
duplex=2 #for repeater
SITE1 = passwrd1,transmit
SITE2 = passwrd2
SITE3 = passwrd3
buflen = 250
plfilter = y
On Fri, Nov 13, 2015 at 3:45 PM, Tim Sawyer <tisawyer at gmail.com<mailto:tisawyer at gmail.com>> wrote:
Not sure what you want to do, but assuming you want to tie a bunch of controllers together, replacing 420 links for example,
you don't need radbridge to bridge RTCMs. Just put all the RTCM under one node in voter.conf. The secret here is mixminus which stops a second repeat path back to the RTCM.
linktolink = yes
SITE1 = passwrd1,transmit,nodeemp,noplfilter
SITE2 = passwrd2,transmit,nodeemp,noplfilter
SITE3 = passwrd3,transmit,nodeemp,noplfilter
buflen = 250
mixminus = y
plfilter = n
On Fri, Nov 13, 2015 at 9:47 AM, Mark DuMoulin @ WB2ERS <wb2ers at metcom.com<mailto:wb2ers at metcom.com>> wrote:
I am running ACID with URI connected.
I also have repeaters using RTCM units.
When I attempt to use radbridge.conf to combine RTCM and URI as shown below:
instance1 = Voter/rtcm,Radio/usb
This is what happens:
[Nov 13 12:37:01] NOTICE: chan_usbradio.c:3273 usbradio_request: Already have a call (chan 0x91b4d18) on the usb channel
[Nov 13 12:37:03] NOTICE: app_rpt.c:22002 rpt_master: RPT thread restarted on 1448
[Nov 13 12:37:03] WARNING: app_rpt.c:22014 rpt_master: rpt_thread restarted on node 1448
-- Re-Loading config for repeater 1448
[Nov 13 12:37:03] NOTICE: chan_usbradio.c:3273 usbradio_request: Already have a call (chan 0x91b4d18) on the usb channel
[Nov 13 12:37:05] ERROR: app_rpt.c:21997 rpt_master: Continual RPT thread restarts, killing Asterisk
Does anyone have any thoughts as to why this is occurring or a different approach on combining the URI and RTCM end points?
Wb2ers at metcom.com<mailto:Wb2ers at metcom.com>
App_rpt-users mailing list
App_rpt-users at ohnosec.org<mailto:App_rpt-users at ohnosec.org>
To unsubscribe from this list please visit http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users and scroll down to the bottom of the page. Enter your email address and press the "Unsubscribe or edit options button"
You do not need a password to unsubscribe, you can do it via email confirmation. If you have trouble unsubscribing, please send a message to the list detailing the problem.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the App_rpt-users