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

RTCM single shot voting (without GPS)
by motorula＠gmail.com 07 Feb '14

07 Feb '14

Hi! Is it possible to run RTCMs in voting mode without GPS? It seems that GPS is not needed for single shot voting, if not needed to mix signals continuosly. If not, then it would be nice to have that feature, for indoor applications, for example, where is not easy/expensive to provide gps signal or 1 pps.

2 1

Re: [App_rpt-users] zaptel issues
by AH2S 07 Feb '14

07 Feb '14

All mine are in fixed locations on full-blown repeater systems although there's no reason one couldn't interface a RTCM to an air card of some sort and go mobile with it. I have used one over a WiFi connection just to see and it worked just fine. If you're looking for an AllStar mobile solution, hang tight for a few months and you'll see what the Micro-node guys have been up to! They have some truly awesome products about to be released for both the AllStar and IRLP platforms. I think the Dayton Hamvention is where they are planning to introduce them! :) --- Rob Pectol - AH2S AllStar Node 2147 On 2014-02-07 20:22, Eric Guth wrote: > Thanks for your reply, Rob. > > Do you have the RTCM in the car on a mobile node, or do you put up a > base or repeater to use with the nodes? > > 73, > > Eric > 4Z1UG / WA6IGR > Allstar Node: 28422 > 4Z1UG(a)guth.us > Israel Direct: 077-950-9451 > USA Direct: +1-720-377-3840 > Skype: ericrguth > > > -----Original Message----- > From: app_rpt-users-bounces(a)ohnosec.org > [mailto:app_rpt-users-bounces@ohnosec.org] On Behalf Of AH2S > Sent: Friday, February 07, 2014 5:04 AM > To: App_rpt Users > Subject: Re: [App_rpt-users] zaptel issues > > Hi Eric, > > Rob here. Yes, I live in Guam and I do stop by the WIN System from > time to time. I use RTCMs exclusively for my nodes here. The idea is > to point them back to my server in the States and do away with the > server here but for now, I'm running a server here. I have 2 more > RTCM nodes that are Stateside which will be tying in as well. Having > everything tie back to a well connected server with plenty of > bandwidth is the idea. > > --- > Rob Pectol - AH2S > AllStar Node 2147 > > On 2014-02-07 05:27, Eric Guth wrote: >> Dear Chris, >> >> I think I have heard you on the WinSystem from Guam. Are you using an >> RTCM in Guam to the server hosted in the states? >> >> 73, >> >> Eric >> 4Z1UG / WA6IGR >> Allstar Node: 28422 >> 4Z1UG(a)guth.us >> Israel Direct: 077-950-9451 >> USA Direct: +1-720-377-3840 >> Skype: ericrguth >> >> -----Original Message----- >> From: app_rpt-users-bounces(a)ohnosec.org >> [mailto:app_rpt-users-bounces@ohnosec.org] On Behalf Of AH2S >> Sent: Thursday, February 06, 2014 5:22 AM >> To: App_rpt Users >> Subject: Re: [App_rpt-users] zaptel issues >> >> Thanks to all for your comments/suggestions. I think it's pretty >> clear I'm going to have to get my colocation provider to do a >> reinstall. >> Moving to 64-bit CentOS will probably the path I take but I'm going to >> need Jim's help with it. I'll contact him off list. >> >> Chris, >> >> Yes, my old call sign was KK7AV and I used to live in Utah several >> years ago. I'm currently living on the island of Guam and my server >> is at a colocation facility in Indiana. Thanks for the offer though. >> 73! >> >> --- >> Rob Pectol - AH2S >> AllStar Node 2147 >> >> On 2014-02-06 08:09, Chris Andrist wrote: >>> Rob, >>> >>> Your server doesn't happen to be in Utah does it? If so, I live in >>> Utah and would be willing to help you out with it. I only ask, >>> because your name sounded very familiar. I remember your old call >>> KK7AV. >>> >>> Regards, >>> >>> Chris Andrist, KC7WSU >>> ________________________________________ >>> From: app_rpt-users-bounces(a)ohnosec.org >>> <app_rpt-users-bounces(a)ohnosec.org> on behalf of AH2S <rob(a)ah2s.org> >>> Sent: Wednesday, February 05, 2014 8:40 AM >>> To: App_rpt Users >>> Subject: Re: [App_rpt-users] zaptel issues >>> >>> Hi Chris, >>> >>> Thanks for the response. The, "old" server is a dual core i3 running >>> at >>> 3.3 GHz. Its actually a desktop PC. The new one is running at a >>> co-location facility on dedicated server hardware. It is NOT running >>> virtualized or anything like that. Since my last post, I've tried >>> downgrading the kernel and build environment with the same results. >>> Everything compiles just fine and appears to be functional until I >>> try to start Asterisk. I'm currently running kernel: >>> >>> [root@allstar zaptel]# uname -r >>> 2.6.18-274.el5PAE >>> >>> But I've tried several later kernels. I even tried a non PAE kernel >>> with the same result. There's something about that zaptel driver >>> that isn't working on this install. I wish I could reload it and >>> start over with perhaps another distro but it's not that easy since >>> it's on the other side of the planet from me! I'd really like to be >>> able to salvage this ACID install otherwise it will just have to sit >>> there in a server >>> 10,000 miles away from me (it's one of 4 server nodes in a single >>> chassis) doing nothing! I can't believe it's this hard to get it to >>> work! >>> >>> --- >>> Rob Pectol - AH2S >>> AllStar Node 2147 >>> >>> On 2014-02-06 02:04, Chris Andrist wrote: >>>> Rob, >>>> >>>> What speed computer was your node on before? >>>> >>>> ACID works best on a Pentium 4 Computer. >>>> >>>> Xipar is a better Distro for faster computers >>>> >>>> Regards, >>>> >>>> Chris Andrist, KC7WSU >>>> >>>>> On Feb 5, 2014, at 1:47 AM, "AH2S" <rob(a)ah2s.org> wrote: >>>>> >>>>> Hello group, >>>>> >>>>> I just loaded up a new server with the official ACID distro from >>>>> the AllStarLink Website but I cannot get Asterisk to start. I >>>>> copied all my configuration files located in /etc/asterisk from my >>>>> working server to the new one so I hoped the transition would be >>>>> smooth. >>>>> When Asterisk bombs out, the log file fills up with the following: >>>>> >>>>> [Feb 4 22:48:10] ERROR[14787] asterisk.c: Asterisk has detected a >>>>> problem with your Zaptel configuration and will shutdown for your >>>>> protection. You have options: >>>>> 1. You only have to compile Zaptel support into Asterisk if you >>>>> need it. One option is to recompile without Zaptel support. >>>>> 2. You only have to load Zaptel drivers if you want to take >>>>> advantage of Zaptel services. One option is to unload zaptel >>>>> modules if you don't need them. >>>>> 3. If you need Zaptel services, you must correctly configure >>>>> Zaptel. >>>>> >>>>> >>>>> This led me to look into the zaptel driver. After many changes to >>>>> its config file in /etc/sysconfig/zaptel and trying over and over >>>>> again, I finally reverted back to the original config and began >>>>> looking at the build process itself thinking that maybe I could >>>>> find some clues. >>>>> The >>>>> zaptel driver compiles without issue and loads the kernel module(s) >>>>> just fine. Everything appears to be functional. Here's what I get >>>>> when I load the driver after having compiled a fresh zaptel: >>>>> >>>>> [root@allstar zaptel]# /etc/init.d/zaptel start >>>>> Loading zaptel framework: [ OK ] >>>>> Waiting for zap to come online...OK Loading zaptel hardware >>>>> modules: wct1xxp. >>>>> wcte11xp. >>>>> wctdm24xxp. >>>>> wcfxo. >>>>> wctdm. >>>>> No hardware timing source found in /proc/zaptel, loading ztdummy >>>>> Running ztcfg: [ OK ] >>>>> >>>>> Again, everything looks fine. The device nodes in /dev/zap are >>>>> there (channel, ctl, pseudo, and timer). So I kept reading and I >>>>> found a thread that said this command: >>>>> od -c /dev/zap/pseudo >>>>> >>>>> should produce this: >>>>> 0000000 177 177 177 177 177 177 177 177 177 177 177 177 177 177 177 >>>>> 177 >>>>> * >>>>> >>>>> It does produce that output, but only the first time. After >>>>> issuing the command and getting the strings back the first time, I >>>>> CTRL-C and get back to a prompt. When I issue the command again, I >>>>> get nothing back. It just sits there waiting for me to interrupt >>>>> it again with a CTRL-C. On a working box when I issue that >>>>> command, I get those strings back immediately, every time. I >>>>> believe this difference is what is causing my problems. >>>>> Unfortunately that is as deep as I've gotten with it. My kernel >>>>> is: >>>>> >>>>> [root@allstar etc]# uname -r >>>>> 2.6.18-371.4.1.el5PAE >>>>> >>>>> and it's running on a Intel dual quad-core xeon with 8 GB of RAM. >>>>> I'm >>>>> not sure how to proceed from here so any advice would be >>>>> appreciated. >>>>> Thanks in advance... >>>>> >>>>> -- >>>>> Rob Pectol - AH2S >>>>> AllStar Node 2147 >>>>> _______________________________________________ >>>>> 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. >>> _______________________________________________ >>> 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. > _______________________________________________ > 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.

1 0

Re: [App_rpt-users] zaptel issues
by AH2S 07 Feb '14

07 Feb '14

Hi Eric, Rob here. Yes, I live in Guam and I do stop by the WIN System from time to time. I use RTCMs exclusively for my nodes here. The idea is to point them back to my server in the States and do away with the server here but for now, I'm running a server here. I have 2 more RTCM nodes that are Stateside which will be tying in as well. Having everything tie back to a well connected server with plenty of bandwidth is the idea. --- Rob Pectol - AH2S AllStar Node 2147 On 2014-02-07 05:27, Eric Guth wrote: > Dear Chris, > > I think I have heard you on the WinSystem from Guam. Are you using an > RTCM in Guam to the server hosted in the states? > > 73, > > Eric > 4Z1UG / WA6IGR > Allstar Node: 28422 > 4Z1UG(a)guth.us > Israel Direct: 077-950-9451 > USA Direct: +1-720-377-3840 > Skype: ericrguth > > -----Original Message----- > From: app_rpt-users-bounces(a)ohnosec.org > [mailto:app_rpt-users-bounces@ohnosec.org] On Behalf Of AH2S > Sent: Thursday, February 06, 2014 5:22 AM > To: App_rpt Users > Subject: Re: [App_rpt-users] zaptel issues > > Thanks to all for your comments/suggestions. I think it's pretty > clear I'm going to have to get my colocation provider to do a > reinstall. > Moving to 64-bit CentOS will probably the path I take but I'm going to > need Jim's help with it. I'll contact him off list. > > Chris, > > Yes, my old call sign was KK7AV and I used to live in Utah several > years ago. I'm currently living on the island of Guam and my server > is at a colocation facility in Indiana. Thanks for the offer though. > 73! > > --- > Rob Pectol - AH2S > AllStar Node 2147 > > On 2014-02-06 08:09, Chris Andrist wrote: >> Rob, >> >> Your server doesn't happen to be in Utah does it? If so, I live in >> Utah and would be willing to help you out with it. I only ask, because >> your name sounded very familiar. I remember your old call KK7AV. >> >> Regards, >> >> Chris Andrist, KC7WSU >> ________________________________________ >> From: app_rpt-users-bounces(a)ohnosec.org >> <app_rpt-users-bounces(a)ohnosec.org> on behalf of AH2S <rob(a)ah2s.org> >> Sent: Wednesday, February 05, 2014 8:40 AM >> To: App_rpt Users >> Subject: Re: [App_rpt-users] zaptel issues >> >> Hi Chris, >> >> Thanks for the response. The, "old" server is a dual core i3 running >> at >> 3.3 GHz. Its actually a desktop PC. The new one is running at a >> co-location facility on dedicated server hardware. It is NOT running >> virtualized or anything like that. Since my last post, I've tried >> downgrading the kernel and build environment with the same results. >> Everything compiles just fine and appears to be functional until I try >> to start Asterisk. I'm currently running kernel: >> >> [root@allstar zaptel]# uname -r >> 2.6.18-274.el5PAE >> >> But I've tried several later kernels. I even tried a non PAE kernel >> with the same result. There's something about that zaptel driver that >> isn't working on this install. I wish I could reload it and start >> over with perhaps another distro but it's not that easy since it's on >> the other side of the planet from me! I'd really like to be able to >> salvage this ACID install otherwise it will just have to sit there in >> a server >> 10,000 miles away from me (it's one of 4 server nodes in a single >> chassis) doing nothing! I can't believe it's this hard to get it to >> work! >> >> --- >> Rob Pectol - AH2S >> AllStar Node 2147 >> >> On 2014-02-06 02:04, Chris Andrist wrote: >>> Rob, >>> >>> What speed computer was your node on before? >>> >>> ACID works best on a Pentium 4 Computer. >>> >>> Xipar is a better Distro for faster computers >>> >>> Regards, >>> >>> Chris Andrist, KC7WSU >>> >>>> On Feb 5, 2014, at 1:47 AM, "AH2S" <rob(a)ah2s.org> wrote: >>>> >>>> Hello group, >>>> >>>> I just loaded up a new server with the official ACID distro from the >>>> AllStarLink Website but I cannot get Asterisk to start. I copied >>>> all my configuration files located in /etc/asterisk from my working >>>> server to the new one so I hoped the transition would be smooth. >>>> When Asterisk bombs out, the log file fills up with the following: >>>> >>>> [Feb 4 22:48:10] ERROR[14787] asterisk.c: Asterisk has detected a >>>> problem with your Zaptel configuration and will shutdown for your >>>> protection. You have options: >>>> 1. You only have to compile Zaptel support into Asterisk if you >>>> need it. One option is to recompile without Zaptel support. >>>> 2. You only have to load Zaptel drivers if you want to take >>>> advantage of Zaptel services. One option is to unload zaptel >>>> modules if you don't need them. >>>> 3. If you need Zaptel services, you must correctly configure >>>> Zaptel. >>>> >>>> >>>> This led me to look into the zaptel driver. After many changes to >>>> its config file in /etc/sysconfig/zaptel and trying over and over >>>> again, I finally reverted back to the original config and began >>>> looking at the build process itself thinking that maybe I could find >>>> some clues. >>>> The >>>> zaptel driver compiles without issue and loads the kernel module(s) >>>> just fine. Everything appears to be functional. Here's what I get >>>> when I load the driver after having compiled a fresh zaptel: >>>> >>>> [root@allstar zaptel]# /etc/init.d/zaptel start >>>> Loading zaptel framework: [ OK ] >>>> Waiting for zap to come online...OK >>>> Loading zaptel hardware modules: wct1xxp. >>>> wcte11xp. >>>> wctdm24xxp. >>>> wcfxo. >>>> wctdm. >>>> No hardware timing source found in /proc/zaptel, loading ztdummy >>>> Running ztcfg: [ OK ] >>>> >>>> Again, everything looks fine. The device nodes in /dev/zap are >>>> there (channel, ctl, pseudo, and timer). So I kept reading and I >>>> found a thread that said this command: >>>> od -c /dev/zap/pseudo >>>> >>>> should produce this: >>>> 0000000 177 177 177 177 177 177 177 177 177 177 177 177 177 177 177 >>>> 177 >>>> * >>>> >>>> It does produce that output, but only the first time. After issuing >>>> the command and getting the strings back the first time, I CTRL-C >>>> and get back to a prompt. When I issue the command again, I get >>>> nothing back. It just sits there waiting for me to interrupt it >>>> again with a CTRL-C. On a working box when I issue that command, I >>>> get those strings back immediately, every time. I believe this >>>> difference is what is causing my problems. Unfortunately that is as >>>> deep as I've gotten with it. My kernel is: >>>> >>>> [root@allstar etc]# uname -r >>>> 2.6.18-371.4.1.el5PAE >>>> >>>> and it's running on a Intel dual quad-core xeon with 8 GB of RAM. >>>> I'm >>>> not sure how to proceed from here so any advice would be >>>> appreciated. >>>> Thanks in advance... >>>> >>>> -- >>>> Rob Pectol - AH2S >>>> AllStar Node 2147 >>>> _______________________________________________ >>>> 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. >> _______________________________________________ >> 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.

1 0

Re: [App_rpt-users] zaptel issues
by AH2S 06 Feb '14

06 Feb '14

Thanks to all for your comments/suggestions. I think it's pretty clear I'm going to have to get my colocation provider to do a reinstall. Moving to 64-bit CentOS will probably the path I take but I'm going to need Jim's help with it. I'll contact him off list. Chris, Yes, my old call sign was KK7AV and I used to live in Utah several years ago. I'm currently living on the island of Guam and my server is at a colocation facility in Indiana. Thanks for the offer though. 73! --- Rob Pectol - AH2S AllStar Node 2147 On 2014-02-06 08:09, Chris Andrist wrote: > Rob, > > Your server doesn't happen to be in Utah does it? If so, I live in > Utah and would be willing to help you out with it. I only ask, because > your name sounded very familiar. I remember your old call KK7AV. > > Regards, > > Chris Andrist, KC7WSU > ________________________________________ > From: app_rpt-users-bounces(a)ohnosec.org > <app_rpt-users-bounces(a)ohnosec.org> on behalf of AH2S <rob(a)ah2s.org> > Sent: Wednesday, February 05, 2014 8:40 AM > To: App_rpt Users > Subject: Re: [App_rpt-users] zaptel issues > > Hi Chris, > > Thanks for the response. The, "old" server is a dual core i3 running > at > 3.3 GHz. Its actually a desktop PC. The new one is running at a > co-location facility on dedicated server hardware. It is NOT running > virtualized or anything like that. Since my last post, I've tried > downgrading the kernel and build environment with the same results. > Everything compiles just fine and appears to be functional until I try > to start Asterisk. I'm currently running kernel: > > [root@allstar zaptel]# uname -r > 2.6.18-274.el5PAE > > But I've tried several later kernels. I even tried a non PAE kernel > with the same result. There's something about that zaptel driver that > isn't working on this install. I wish I could reload it and start over > with perhaps another distro but it's not that easy since it's on the > other side of the planet from me! I'd really like to be able to > salvage > this ACID install otherwise it will just have to sit there in a server > 10,000 miles away from me (it's one of 4 server nodes in a single > chassis) doing nothing! I can't believe it's this hard to get it to > work! > > --- > Rob Pectol - AH2S > AllStar Node 2147 > > On 2014-02-06 02:04, Chris Andrist wrote: >> Rob, >> >> What speed computer was your node on before? >> >> ACID works best on a Pentium 4 Computer. >> >> Xipar is a better Distro for faster computers >> >> Regards, >> >> Chris Andrist, KC7WSU >> >>> On Feb 5, 2014, at 1:47 AM, "AH2S" <rob(a)ah2s.org> wrote: >>> >>> Hello group, >>> >>> I just loaded up a new server with the official ACID distro from the >>> AllStarLink Website but I cannot get Asterisk to start. I copied all >>> my configuration files located in /etc/asterisk from my working >>> server >>> to the new one so I hoped the transition would be smooth. When >>> Asterisk bombs out, the log file fills up with the following: >>> >>> [Feb 4 22:48:10] ERROR[14787] asterisk.c: Asterisk has detected a >>> problem with your Zaptel configuration and will shutdown for your >>> protection. You have options: >>> 1. You only have to compile Zaptel support into Asterisk if you >>> need it. One option is to recompile without Zaptel support. >>> 2. You only have to load Zaptel drivers if you want to take >>> advantage of Zaptel services. One option is to unload zaptel modules >>> if you don't need them. >>> 3. If you need Zaptel services, you must correctly configure >>> Zaptel. >>> >>> >>> This led me to look into the zaptel driver. After many changes to >>> its >>> config file in /etc/sysconfig/zaptel and trying over and over again, >>> I >>> finally reverted back to the original config and began looking at the >>> build process itself thinking that maybe I could find some clues. >>> The >>> zaptel driver compiles without issue and loads the kernel module(s) >>> just fine. Everything appears to be functional. Here's what I get >>> when I load the driver after having compiled a fresh zaptel: >>> >>> [root@allstar zaptel]# /etc/init.d/zaptel start >>> Loading zaptel framework: [ OK ] >>> Waiting for zap to come online...OK >>> Loading zaptel hardware modules: wct1xxp. >>> wcte11xp. >>> wctdm24xxp. >>> wcfxo. >>> wctdm. >>> No hardware timing source found in /proc/zaptel, loading ztdummy >>> Running ztcfg: [ OK ] >>> >>> Again, everything looks fine. The device nodes in /dev/zap are there >>> (channel, ctl, pseudo, and timer). So I kept reading and I found a >>> thread that said this command: >>> od -c /dev/zap/pseudo >>> >>> should produce this: >>> 0000000 177 177 177 177 177 177 177 177 177 177 177 177 177 177 177 >>> 177 >>> * >>> >>> It does produce that output, but only the first time. After issuing >>> the command and getting the strings back the first time, I CTRL-C and >>> get back to a prompt. When I issue the command again, I get nothing >>> back. It just sits there waiting for me to interrupt it again with a >>> CTRL-C. On a working box when I issue that command, I get those >>> strings back immediately, every time. I believe this difference is >>> what is causing my problems. Unfortunately that is as deep as I've >>> gotten with it. My kernel is: >>> >>> [root@allstar etc]# uname -r >>> 2.6.18-371.4.1.el5PAE >>> >>> and it's running on a Intel dual quad-core xeon with 8 GB of RAM. >>> I'm >>> not sure how to proceed from here so any advice would be appreciated. >>> Thanks in advance... >>> >>> -- >>> Rob Pectol - AH2S >>> AllStar Node 2147 >>> _______________________________________________ >>> 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. > _______________________________________________ > 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.

1 0

zaptel issues
by AH2S 05 Feb '14

05 Feb '14

Hello group, I just loaded up a new server with the official ACID distro from the AllStarLink Website but I cannot get Asterisk to start. I copied all my configuration files located in /etc/asterisk from my working server to the new one so I hoped the transition would be smooth. When Asterisk bombs out, the log file fills up with the following: [Feb 4 22:48:10] ERROR[14787] asterisk.c: Asterisk has detected a problem with your Zaptel configuration and will shutdown for your protection. You have options: 1. You only have to compile Zaptel support into Asterisk if you need it. One option is to recompile without Zaptel support. 2. You only have to load Zaptel drivers if you want to take advantage of Zaptel services. One option is to unload zaptel modules if you don't need them. 3. If you need Zaptel services, you must correctly configure Zaptel. This led me to look into the zaptel driver. After many changes to its config file in /etc/sysconfig/zaptel and trying over and over again, I finally reverted back to the original config and began looking at the build process itself thinking that maybe I could find some clues. The zaptel driver compiles without issue and loads the kernel module(s) just fine. Everything appears to be functional. Here's what I get when I load the driver after having compiled a fresh zaptel: [root@allstar zaptel]# /etc/init.d/zaptel start Loading zaptel framework: [ OK ] Waiting for zap to come online...OK Loading zaptel hardware modules: wct1xxp. wcte11xp. wctdm24xxp. wcfxo. wctdm. No hardware timing source found in /proc/zaptel, loading ztdummy Running ztcfg: [ OK ] Again, everything looks fine. The device nodes in /dev/zap are there (channel, ctl, pseudo, and timer). So I kept reading and I found a thread that said this command: od -c /dev/zap/pseudo should produce this: 0000000 177 177 177 177 177 177 177 177 177 177 177 177 177 177 177 177 * It does produce that output, but only the first time. After issuing the command and getting the strings back the first time, I CTRL-C and get back to a prompt. When I issue the command again, I get nothing back. It just sits there waiting for me to interrupt it again with a CTRL-C. On a working box when I issue that command, I get those strings back immediately, every time. I believe this difference is what is causing my problems. Unfortunately that is as deep as I've gotten with it. My kernel is: [root@allstar etc]# uname -r 2.6.18-371.4.1.el5PAE and it's running on a Intel dual quad-core xeon with 8 GB of RAM. I'm not sure how to proceed from here so any advice would be appreciated. Thanks in advance... -- Rob Pectol - AH2S AllStar Node 2147

4 5

CODEC inquiry?
by KJ6KO 05 Feb '14

05 Feb '14

Is there a command to check which CODEC my allstar system is using? Thanks... __________ Information from ESET NOD32 Antivirus, version of virus signature database 9382 (20140204) __________ The message was checked by ESET NOD32 Antivirus. http://www.eset.com

4 3

TKR-840 issue
by Chris Bunting 04 Feb '14

04 Feb '14

Was setting up the master site for my simulcast system over the weekend, but ran into a roadblock, any help would be appreciated. When feeding flat Audio into "transmit data" input , the repeater maxes out at 2k deviation, no matter how much audio I feed it. I could use the transmit audio input, but then I can't feed PL among other things into it, along with many other reasons not to use tx audio. Anyone experience this with the kenwood highline series repeaters? What is everyone out there using? I'm ready to auction my 2 kenwood's off and buy something else if this can't be overcome. The reason I went with the 840 and 830 is it had a 10 meg input for the clock. Thanks, Chris Bunting Lancaster Networks, LLC | Lancaster Towers, LLC 717-459-4321

3 3

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

04 Feb '14

I do not believe it is possible to only use a single RTCM > at a site that contains both a 6m RF device and 2m RF device. Because > they are 2 separate repeater systems each is a separate node in > Asterisk and an RTCM can only be associated with a single node. > > Ok, buggar. Thanks Brett. S

3 2

Re: [App_rpt-users] App_rpt-users Digest, Vol 60, Issue 7
by Brett Friermood 03 Feb '14

03 Feb '14

In that case I do not believe it is possible to only use a single RTCM at a site that contains both a 6m RF device and 2m RF device. Because they are 2 separate repeater systems each is a separate node in Asterisk and an RTCM can only be associated with a single node. Brett On Mon, Feb 3, 2014 at 11:10 AM, Steve Wright <stevewrightnz(a)gmail.com> wrote: > Scuse the top posting; > > There is a 2m voter simulcast system. It can be expanded upon by adding > more GPSDO transmitters, and more voting receivers - just as any voter > simulcast system would be. > > And there is a 6m voter simulcast system. It can be expanded upon by adding > more GPSDO transmitters, and more voting receivers - just as any voter > simulcast system would be. > > The 2m and 6m simulcast systems are NOT connected so they function as a > cross-band talk-through repeater. > > The 2m node AND SEPARATELY the 6m node are independent repeaters in their > own right. To the ordinary joe ham radio operator, the only thing in common > is that you can dial (via asterisk) one from the other in common use. > > The only confusing thing about the 2m and the 6m repeaters from the > technical point of view as noted, is that one physically shares the others' > site and controller. > > So, each, they are not simplex remote bases, but full simulcast repeater > systems. > > Steve > > > On Mon, Feb 3, 2014 at 2:30 PM, Brett Friermood <brett.friermood(a)gmail.com> > wrote: >> >> The remote base way won't scale beyond two sites while still keeping >> only a single RTCM per site and keeping the repeaters separate. As >> soon as another transmitter on the other band is plugged in it will >> transmit no matter what receiver is receiving. >> >> Yes, the terms can get a little confusing when you start messing with >> non-standard configurations. I generally use the following: >> >> A site is a physical location on a map, usually holding a collection >> of RF hardware, or otherwise defined as where an RTCM(s) sits. >> >> A node is a virtual resource existing only within the Asterisk >> framework and is used to do things including linking to others. >> >> A repeater is an RF resource consisting of a transmitter and receiver, >> which may involve different bands or locations (sites), but function >> simultaneously. >> >> A system consists of multiple pieces of something. Adding links >> between otherwise standalone repeaters creates a system. I would >> define multiple sites using voted receivers and simulcast transmitters >> as a voted/simulcast repeater system. The individual sites do not >> necessarily contain a repeater because other parts of the system are >> needed to function. The entire system, however, is a repeater. >> >> I understand what you are trying to do as far as the distributed sites >> to provide the required coverage and reduce duplexer costs. The one >> thing we have yet to pin you down on is whether the 2m repeater and 6m >> repeater should exist separately on RF or if they are really just one >> system? In other words, should a 2m only radio be able to talk to a 6m >> only radio a) all the time, b) never, or c) only when linked? >> >> Brett KQ9N >> >> On Sun, Feb 2, 2014 at 6:13 PM, Steve Wright <stevewrightnz(a)gmail.com> >> wrote: >> >> >> >> The first way to setup the unlinked configuration is to use four >> >> RTCMs. These would then link back to two separate nodes. This would >> >> allow the ability to link the two repeaters when needed/wanted. Of >> >> course this is what you don't want because of excess RTCMs. >> > >> > >> > Yes, exactly. >> > >> > >> >> >> >> >> >> The "new" way that Mike (W5JR) [...] Cactus Intertie [..] uses this >> >> configuration. [...] in-band repeaters [where] the receiver audio is >> >> linked >> >> to the rest of the [same band voting] system and not repeated through >> >> the >> >> local [non band] transmitter [that is part of an identical and linkable >> >> node]. >> >> >> >> [...] two nodes would need to be created. One node for the Site "A" >> >> RTCM >> >> and the second for >> >> the Site "B" RTCM. Then link these through Asterisk. When the A >> >> receiver picks up a signal the audio would be sent back and sent to >> >> the B transmitter. Similarly any signal picked up by the B receiver >> >> would be sent to the A transmitter. Both appearing independent of each >> >> other. >> > >> > >> > Yes indeedy! >> > >> >> Setting duplex=1 will not repeat the audio from receiver to [the same >> >> site] >> >> transmitter, but uses half duplex operation for simplex nodes. >> > >> > >> > Thanks Brett, that's perfect! >> > >> > If we do this, will our split-site (but same-band) repeater still have >> > talk-through? >> > >> > Also can I arbitrarily add other TX and RX sites to this "repeater" >> > "node"? >> > >> > I add the "", because with split-site operation the definition of "node" >> > is >> > not particularly clear with respect to the site. >> > >> > So in summary, we are looking at multiple-site voted systems due to not >> > having good access to one high site, and the few (expensive) high sites >> > leave some pretty big holes anyway. We are looking at using the >> > split-tx/rx >> > approach as above to avoid the expensive and complicated duplexing. >> > >> > Steve >> > >> > >> > _______________________________________________ >> > 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. > > > > > -- > Meshnetworks - Rangitaiki Plains Rural Broadband Internet Providers > +64 21 040 5067

1 0

ZAP folder gone after yum update
by KJ6KO 03 Feb '14

03 Feb '14

OK, Did a yum update...probably shouldn't have? My zap folder is now missing. Any fix or complete reload? In the future, is a yum update bad? What others can I run to do updates? Thanks.. Greg __________ Information from ESET NOD32 Antivirus, version of virus signature database 9372 (20140202) __________ The message was checked by ESET NOD32 Antivirus. http://www.eset.com

3 2