[App_rpt-users] OMG - I think it works!

[Stephen - K1LNX]

Bravo Alan! Did you happen to take detailed notes for this install, I'd like to duplicate your efforts ;)


Ok, one quick question… The *only * notice I get on bootup is something about  a zap(tel) timer and using ztdummy instead…. Is that normal?

Yes, zaptel needs a timing source and can use ztdummy if you do not have a digium or equivalent card to provide it so it's actually critical that this module is loaded.

Glad you got it working!!!

73
Stephen
K1LNX

Sent from my iPad

On May 22, 2012, at 20:32, "Alan Adamson" <adamson_alan at hotmail.com<mailto:adamson_alan at hotmail.com>> wrote:


So I hope you all will appreciate a little yelling and screaming!!!

Here is what I did today..

I took a brand new DN2800MT Atom MB.  Added 2G of ram, and 60G SSD drive and put that in an M350 case.   I then took the Debian *64bit* net install, the latest - 6.0.5 and I used a tool to put it on a USB stick.  From there, I booted from the usb stick and I installed Debian.  I had been to this point prior so I knew how to get here.

Next I knew I needed to get new drivers for the ALSA support.  So I went to Realtek and downloaded their linux kernel modules.. Built and installed them - this meant I also had to put a development environment on the debian install through apt-get.  Ok, so far so good.

I had seen this as my motivation to get this working on Debian…

http://kriskirkland.com/?p=143

I took this install script and modified it a little.  Also because I can't get to the dl.allstarlink.org<http://dl.allstarlink.org> site directly (DNS issues), I got the files I needed through my cell connection and used them locally.

During the install, you build the entire source for everything.  This was my first challenge, there were errors in the source that I had to fix.  As it turns out, it was just include files that needed to be added due to the recent kernel that I'm running.  I also had to fix the udev rules for zaptel, they were basically wrong for the version of udev that is running, nothing dramatic, just some "="'s that needed to be "==" due to a change in the udev syntax.

Next I added the ixaRPT setup and rebooted.  Wow, a clean reboot.  Nothing wrong and everything seems to be working… I was using the allstarlink node list to determine if I was up or not and I've since found out that I've got one little issue to work through.  On a reboot,  the system is functional, but I don't show as registered in the list.  If I manually stop and start asterisk, I show up correctly.

So… Bottom line, I seem to be functional and on the allstar link network with node 28578 - now before you all start connecting to me… There are no radios attached just yet. :)… I'm waiting on my URI's and I've got an RTCM setting here that I need to look at in the coming days.

But thanks to everyone that helped with suggestions and ideas… And thanks to Bryan Boyle for connecting to me and letting me know that audio was working both way, at least from my windows machine via the iaxRpt client…

I also have the X-Lite client configured to connect to the sip.allstarlink site, but I don't know how to make PTT work with it :)… I'll figure that out next.

Bottom line, a pristine Debian install, with a Debianish ACID like install, on a very late model Atom MB…. Most would say 3 strikes, but man does it feel good when it works!

Ok, one quick question… The *only * notice I get on bootup is something about  a zap(tel) timer and using ztdummy instead…. Is that normal?

Alan

_______________________________________________
App_rpt-users mailing list
App_rpt-users at ohnosec.org<mailto:App_rpt-users at ohnosec.org>
http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.keekles.org/pipermail/app_rpt-users/attachments/20120523/e5eec379/attachment.html>