February 2014 - App_rpt-users - lists.keekles.org

Re: [App_rpt-users] App_rpt-users Digest, Vol 60, Issue 1
by Bradley Haney 01 Feb '14

01 Feb '14

How hard is it to add dstar dongle. To allstar.. wouldnlike to be able to dtmf from our allstar repeater to dstar On Feb 1, 2014 11:08 AM, <app_rpt-users-request(a)ohnosec.org> wrote: > Send App_rpt-users mailing list submissions to > app_rpt-users(a)ohnosec.org > > To subscribe or unsubscribe via the World Wide Web, visit > http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users > or, via email, send a message with subject or body 'help' to > app_rpt-users-request(a)ohnosec.org > > You can reach the person managing the list at > app_rpt-users-owner(a)ohnosec.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of App_rpt-users digest..." > > > Today's Topics: > > 1. DMR to Analog/app-rpt (K1IF) > 2. Re: RTCM Squelch Noise Gain Value = ? (41.2 Jim) > 3. Re: DMR to Analog/app-rpt (Keith Goobie) > 4. Re: DMR to Analog/app-rpt (Bryan D. Boyle) > 5. asterisk wont star properly (Pierre Martel) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Fri, 31 Jan 2014 11:28:14 -0600 > From: "K1IF" <k1if(a)k1if.com> > To: <app_rpt-users(a)ohnosec.org> > Subject: [App_rpt-users] DMR to Analog/app-rpt > Message-ID: <000001cf1ea9$d47ea690$7d7bf3b0$@com> > Content-Type: text/plain; charset="us-ascii" > > Travis KJ4NDP has successfully connected his DMR radio to asterisk by > utilizing the dstar channel driver in asterisk created by Scott Lawson > ki4lkf. > > > > --- > This email is free from viruses and malware because avast! Antivirus > protection is active. > http://www.avast.com >

3 2

asterisk wont star properly
by Pierre Martel 01 Feb '14

01 Feb '14

it seem like the computer at the repeater site crashed or lost power, when the system came back asterisk keep on diying on us.. here is the last few lines with some noticed before the service die [Feb 1 11:53:06] WARNING[3548]: chan_dahdi.c:928 dahdi_open: Unable to open '/dev/zap/pseudo': No such file or directory [Feb 1 11:53:06] ERROR[3548]: chan_dahdi.c:7906 chandup: Unable to dup channel: No such file or directory [Feb 1 11:53:08] NOTICE[3516]: app_rpt.c:21870 rpt_master: RPT thread restarted on 27821 [Feb 1 11:53:08] WARNING[3516]: app_rpt.c:21882 rpt_master: rpt_thread restarted on node 27821 [Feb 1 11:53:08] NOTICE[3516]: app_rpt.c:21870 rpt_master: RPT thread restarted on 28739 [Feb 1 11:53:08] WARNING[3516]: app_rpt.c:21882 rpt_master: rpt_thread restarted on node 28739 -- Re-Loading config for repeater 27821 -- rpt (Rx) initiating call to Radio/usb27821 on Radio/usb27821 [Feb 1 11:53:08] WARNING[3551]: chan_dahdi.c:928 dahdi_open: Unable to open '/dev/zap/pseudo': No such file or directory [Feb 1 11:53:08] ERROR[3551]: chan_dahdi.c:7906 chandup: Unable to dup channel: No such file or directory -- Re-Loading config for repeater 28739 -- rpt (Rx) initiating call to Radio/usb28739 on Radio/usb28739 [Feb 1 11:53:08] WARNING[3552]: chan_dahdi.c:928 dahdi_open: Unable to open '/dev/zap/pseudo': No such file or directory [Feb 1 11:53:08] ERROR[3552]: chan_dahdi.c:7906 chandup: Unable to dup channel: No such file or directory [Feb 1 11:53:10] NOTICE[3516]: app_rpt.c:21870 rpt_master: RPT thread restarted on 27821 [Feb 1 11:53:10] WARNING[3516]: app_rpt.c:21882 rpt_master: rpt_thread restarted on node 27821 [Feb 1 11:53:10] NOTICE[3516]: app_rpt.c:21870 rpt_master: RPT thread restarted on 28739 [Feb 1 11:53:10] WARNING[3516]: app_rpt.c:21882 rpt_master: rpt_thread restarted on node 28739 -- Re-Loading config for repeater 27821 -- rpt (Rx) initiating call to Radio/usb27821 on Radio/usb27821 [Feb 1 11:53:10] WARNING[3555]: chan_dahdi.c:928 dahdi_open: Unable to open '/dev/zap/pseudo': No such file or directory [Feb 1 11:53:10] ERROR[3555]: chan_dahdi.c:7906 chandup: Unable to dup channel: No such file or directory -- Re-Loading config for repeater 28739 -- rpt (Rx) initiating call to Radio/usb28739 on Radio/usb28739 [Feb 1 11:53:10] WARNING[3556]: chan_dahdi.c:928 dahdi_open: Unable to open '/dev/zap/pseudo': No such file or directory [Feb 1 11:53:10] ERROR[3556]: chan_dahdi.c:7906 chandup: Unable to dup channel: No such file or directory anyone have an idea what is happening

1 0

[App rpt-users] Problems update for Echolink
by Douglas Waugh 01 Feb '14

01 Feb '14

I have come up with a problem getting Echolink to see what I am connected to. The Echolink program can update the listing by doing this: Is your node not showing? You can control this in EchoLink. Go to Tools >> Preferences >> Connections and check the box "Update Location entry with status". How can we get Echolink.conf to do this for us?

2 1

Re: [App_rpt-users] App_rpt-users Digest, Vol 60, Issue 3
by Steve Wright 01 Feb '14

01 Feb '14

> > I think what he is asking is whether the weather the Rx and Tx streams > of the RTCM can be used on different nodes. In other words, at a > specific site with only a single RTCM, can the transmitter be part of > node A while the receiver is part of node B. Concisely; Two repeaters, a 6m repeater and a 2m repeater. Two repeater sites; Site "A" has 6m TX and 2m RX. Site "B" has 6m RX and 2m TX. *One* RTCM at each site. chan_voter will have to have it explained in excruciating detail. Call me cheap - two RTCM is cheaper than four RTCM, and duplexing 6/2 is a lot less complex than duplexing 6/6 and 2/2. ;) Steve > Looking at his message > again that may not actually be what he is looking for, though. > > Steve, as long as there is only one Asterisk node involved, meaning a > single repeater "system" although using multiple bands, a single RTCM > at a site will work. If configured this way all the 6m and 2m > receivers would link back and be voted into a single stream which > would then be sent out to all the 6m and 2m transmitters at the > different sites. When used like this as far as app_rpt is concerned it > behaves no differently than having a voted/simulcast system on a > single band. > > Brett KQ9N > > On Sat, Feb 1, 2014 at 6:20 PM, Tim Sawyer <tim.sawyer(a)mac.com> wrote: > > Of course each RTCM can transmit and receive. The receive only sites > don't have the transmit parameter in voter.conf. But you seem to be asking > a different question. If so, could you restate it? > > -- > > Tim > > :wq > > > > On Feb 1, 2014, at 10:23 AM, Steve Wright <stevewrightnz(a)gmail.com> > wrote: > > > >> Gurus! > >> > >> Can I operate arbitrary recievers and transmitters with the voter > boards, and separate them in config at chan_voter? > >> > >> Background: Our terrain does not lend itself to a few high-sited > duplexed repeaters (or rather we are not inclined to pay for it), so we are > taking the non-duplexed distributed approach of locating recievers and > transmitters at various sites on a non-contending basis and GPS locking > them all together. It seems to us that if we have a hole in some coverage, > that it would easy (read - cheap) to throw another GM300 at the problem.. > >> > >> That is, site A has either a 6M transmitter and other 2M receiver, or > otherwise non-contending combinations, and the corresponding pair for each > repeater receiver or transmitter is actually located on a nearby site > linked with 802.11an. > >> > >> SO! It looks at first glance that I must use a VOTER board for each rx > AND each tx, but perhaps I can use some clever config and halve the number > of VOTER boards I use. > >> > >> > >> Many thanks, > >> Steve > >> > >> > >> -- > >> Meshnetworks - Rangitaiki Plains Rural Broadband Internet Providers > >> +64 21 040 5067 > >> _______________________________________________ > >> App_rpt-users mailing list > >> App_rpt-users(a)ohnosec.org > >> http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users > >> > >> 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. > > > > _______________________________________________ > > App_rpt-users mailing list > > App_rpt-users(a)ohnosec.org > > http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users > > > > 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. > > > ------------------------------ > > Message: 6 > Date: Sat, 1 Feb 2014 21:54:41 -0500 > From: Lu Vencl <vencl(a)att.net> > To: "<app_rpt-users(a)ohnosec.org>" <app_rpt-users(a)ohnosec.org> > Subject: [App_rpt-users] MSF 5000 URI interface > Message-ID: <D9035249-1E4C-4EF8-AB58-75B4784784B4(a)att.net> > Content-Type: text/plain; charset=us-ascii > > Anyone have the diagram for URI interface to an MSF 5000? > > Sent from my iPhone, Lu Vencl > > > ------------------------------ > > _______________________________________________ > App_rpt-users mailing list > App_rpt-users(a)ohnosec.org > http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users > > > End of App_rpt-users Digest, Vol 60, Issue 3 > ******************************************** > -- Meshnetworks - Rangitaiki Plains Rural Broadband Internet Providers +64 21 040 5067

2 1