[App_rpt-users] zaptel issues
AH2S
rob at ah2s.org
Fri Feb 7 03:04:12 UTC 2014
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 at guth.us
> Israel Direct: 077-950-9451
> USA Direct: +1-720-377-3840
> Skype: ericrguth
>
> -----Original Message-----
> From: app_rpt-users-bounces at ohnosec.org
> [mailto:app_rpt-users-bounces at 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 at ohnosec.org
>> <app_rpt-users-bounces at ohnosec.org> on behalf of AH2S <rob at 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 at 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 at 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 at 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 at 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 at 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 at 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 at 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 at 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.
More information about the App_rpt-users
mailing list