Hi Folks, new here.. Did a lot of looking around, but didnt see the answer to this. I want to use app_rpt as my repeater controler and support P25 + NBFM. I see a rx-to-asterisk app here, but not a corresponding asterisk-to-tx app. I saw a repeater app but didnt appear to support asterisk. Am I missing something or does it not exist? Thanks!
There are apps for use with asterisk app_rpt - for both directions, tx and rx. The app the handles tx currently doesn't support NBFM, only p25. The addition of NBFM tx is perhaps non trivial. Nonetheless the asterisk-to-tx app is named repeater/src/python/usrp_tx.py. At this time we are looking for experimenters interested in using the TX chain with hardware NBFM transmitters (no USRP required). In this mode the user's FM transmitter is driven by a C4FM signal that has been software-generated in Gnu radio, and applied to the TX via a soundcard line-out port... 73 Max ________________________________ From: n4dav <n4dav@verizon.net> To: op25-dev@yahoogroups.com Sent: Saturday, February 23, 2013 6:43 PM Subject: [op25-dev] Full asterisk support? Hi Folks, new here.. Did a lot of looking around, but didnt see the answer to this. I want to use app_rpt as my repeater controler and support P25 + NBFM. I see a rx-to-asterisk app here, but not a corresponding asterisk-to-tx app. I saw a repeater app but didnt appear to support asterisk. Am I missing something or does it not exist? Thanks!
I thought the USRP_TX app was only for that hardware. I want to use a conventional radio, just as you described, for both P25 and NBFM. So sign me up as as experimenter wanting to try that! --- In op25-dev@yahoogroups.com, ikjtel <ikj1234i@...> wrote:
There are apps for use with asterisk app_rpt - for both directions, tx and rx.
The app the handles tx currently doesn't support NBFM, only p25. The addition of NBFM tx is perhaps non trivial.
Nonetheless the asterisk-to-tx app is named repeater/src/python/usrp_tx.py.
At this time we are looking for experimenters interested in using the TX chain with hardware NBFM transmitters (no USRP required). In this mode the user's FM transmitter is driven by a C4FM signal that has been software-generated in Gnu radio, and applied to the TX via a soundcard line-out port...
73
Max
________________________________ From: n4dav <n4dav@...> To: op25-dev@yahoogroups.com Sent: Saturday, February 23, 2013 6:43 PM Subject: [op25-dev] Full asterisk support?
 Hi Folks, new here.. Did a lot of looking around, but didnt see the answer to this. I want to use app_rpt as my repeater controler and support P25 + NBFM. I see a rx-to-asterisk app here, but not a corresponding asterisk-to-tx app. I saw a repeater app but didnt appear to support asterisk. Am I missing something or does it not exist? Thanks!
Thinking about this some more, why couldn't you just split the audio from the RX and TX into two usb sound fobs.. One would handle analog though the normal app_rpt methods, and one would handle P25 though these new apps. The analog side wouldnt do anything with the P25 data when it came though, as there would be no PL on it to activate the regular RX app. Seems like it might work. --- In op25-dev@yahoogroups.com, "n4dav" <n4dav@...> wrote:
I thought the USRP_TX app was only for that hardware. I want to use a conventional radio, just as you described, for both P25 and NBFM. So sign me up as as experimenter wanting to try that!
--- In op25-dev@yahoogroups.com, ikjtel <ikj1234i@> wrote:
There are apps for use with asterisk app_rpt - for both directions, tx and rx.
The app the handles tx currently doesn't support NBFM, only p25. The addition of NBFM tx is perhaps non trivial.
Nonetheless the asterisk-to-tx app is named repeater/src/python/usrp_tx.py.
At this time we are looking for experimenters interested in using the TX chain with hardware NBFM transmitters (no USRP required). In this mode the user's FM transmitter is driven by a C4FM signal that has been software-generated in Gnu radio, and applied to the TX via a soundcard line-out port...
73
Max
________________________________ From: n4dav <n4dav@> To: op25-dev@yahoogroups.com Sent: Saturday, February 23, 2013 6:43 PM Subject: [op25-dev] Full asterisk support?
 Hi Folks, new here.. Did a lot of looking around, but didnt see the answer to this. I want to use app_rpt as my repeater controler and support P25 + NBFM. I see a rx-to-asterisk app here, but not a corresponding asterisk-to-tx app. I saw a repeater app but didnt appear to support asterisk. Am I missing something or does it not exist? Thanks!
Thinking about this some more, why couldn't you just split the audio from the RX and TX into two
Yeah, asterisk app_rpt transmitting analog FM voice over standard FM radio hardware is already a fully solved problem having no need for a USRP. Our software stack can receive analog NBFM in addition to P25, for one thing because the software support to do so was not difficult to add.
I thought the USRP_TX app was only for that hardware. I want to use a conventional radio, just as you described, for both P25 and NBFM. So sign me up as as experimenter wanting to try that! OK -excellent. For starters could we try first to get python/op25_audio_tx.py working - that app does not support asterisk / app_rpt but will establish a baseline. The results of that test would direct the next step of the experiment.
op25_audio_tx takes input analog voice either from a sound card or from a disk file (8,000 samples/sec, short signed int16 format). It generates audio at the soundcard audio line-out port (which should be connected directly to the modulator stage of the FM TX). You might be able to use the same sound card for both lines, if the card supports full duplex and if it allows different rates for record and playback. If not the next best thing might be to use canned test audio files [use the -i option and place the audio test file in baseband-0.dat]. The biggest problem so far has been group delay distortion. It's also critical to get the proper audio signal levels going into the TX such that the FM deviation is correct. That should be it - let me know of next step(s) 73 Max
I've got some work to do , need to build all this up and get the basics working first. What method do you use to measure the correct deviation of the C4FM signal? --- In op25-dev@yahoogroups.com, ikjtel <ikj1234i@...> wrote:
Â
Thinking about this some more, why couldn't you just split the audio from the RX and TX into two
Yeah, asterisk app_rpt transmitting analog FM voice over standard FM radio hardware is already a fully solved problem having no need for a USRP. Our software stack can receive analog NBFM in addition to P25, for one thing because the software support to do so was not difficult to add.
I thought the USRP_TX app was only for that hardware. I want to use a conventional radio, just as you described, for both P25 and NBFM. So sign me up as as experimenter wanting to try that! OK -excellent. For starters could we try first to get python/op25_audio_tx.py working - that app does not support asterisk / app_rpt but will establish a baseline. The results of that test would direct the next step of the experiment.Â
op25_audio_tx takes input analog voice either from a sound card or from a disk file (8,000 samples/sec, short signed int16 format). It generates audio at the soundcard audio line-out port (which should be connected directly to the modulator stage of the FM TX). You might be able to use the same sound card for both lines, if the card supports full duplex and if it allows different rates for record and playback. If not the next best thing might be to use canned test audio files [use the -i option and place the audio test file in baseband-0.dat].
The biggest problem so far has been group delay distortion. It's also critical to get the proper audio signal levels going into the TX such that the FM deviation is correct. That should be it - let me know of next step(s)
73 Max
What method do you use to measure the correct deviation of the C4FM signal?
hmm - apols if I've guessed wrong, but sounds like you haven't yet RTFM - based both on this question and the questions about the repeater. Have a look at http://op25.osmocom.org/wiki/wiki/HardwarePage http://op25.osmocom.org/wiki/wiki/RepeaterPage http://op25.osmocom.org/wiki/wiki/SignalScopePage - in particular the Hardware page has a method for setting the deviation - or you could spend $ on a store-bought FMD meter : ) 73 de KA1RBI
Actually I had RTFM but there's so much there I forgot about that page. I put a lot of time into this yesterday, trying to build all the parts. I'm using CentOS as that is what the ACID distro is built on for Allstar, and it works well. But trying to get this stuff built is a major exercise in frustration. Every package I tried to build was missing some other dependency, which was missing some other dependency, it was a chain of missing things. I never got anything built. One make complained about python not being at least 2.5, (I had 2.4), so I installed 2.6, verified it with python-V, and still couldn't run the make file. It still thought I had 2.4, and I have no idea how to fix that. I'll probably go back to it after I pull my fist out of the wall but so far it has not been fun. --- In op25-dev@yahoogroups.com, ikjtel <ikj1234i@...> wrote:
 What method do you use to measure the correct deviation of the C4FM signal?
hmm - apols if I've guessed wrong, but sounds like you haven't yet RTFM - based both on this question and the questions about the repeater.
Have a look atÂ
http://op25.osmocom.org/wiki/wiki/HardwarePage
http://op25.osmocom.org/wiki/wiki/RepeaterPage
http://op25.osmocom.org/wiki/wiki/SignalScopePage
- in particular the Hardware page has a method for setting the deviation - or you could spend $ on a store-bought FMD meter : )
73 de KA1RBI
I too was building or more specifically started over on rebuilding on Ubuntu 10.04 LTS. My build went successfully but not sure about how I can build Allstar Into that J I figured I wanted to try to get SOME documented version to build then figure out how to get it working in the environment I want ( which would be over a ACID build also ) . I was able to get GNU Radio to compile with no major errors ( read as program stops J ) , to get op25 svn imported, the three op25 modules to compile and install I *THINK* without major errors. Tonight I will go through the build logs and see if I missed anything important. I had errors regarding port audio missing on my Debian build but they did not go bang on Ububtu 10.04 LTS. I am not trying to steal your thread here, just comparing results along the way and maybe sharing stumbles Did you start with an Acid build??? I am thinking in the *production* edition I will need to do that .. I have no confidence it all built correctly yet but the installs at least completed Doug KD8B From: op25-dev@yahoogroups.com [mailto:op25-dev@yahoogroups.com] On Behalf Of n4dav Sent: Tuesday, February 26, 2013 7:24 AM To: op25-dev@yahoogroups.com Subject: [op25-dev] Re: Full asterisk support? Actually I had RTFM but there's so much there I forgot about that page. I put a lot of time into this yesterday, trying to build all the parts. I'm using CentOS as that is what the ACID distro is built on for Allstar, and it works well. But trying to get this stuff built is a major exercise in frustration. Every package I tried to build was missing some other dependency, which was missing some other dependency, it was a chain of missing things. I never got anything built. One make complained about python not being at least 2.5, (I had 2.4), so I installed 2.6, verified it with python-V, and still couldn't run the make file. It still thought I had 2.4, and I have no idea how to fix that. I'll probably go back to it after I pull my fist out of the wall but so far it has not been fun. --- In op25-dev@yahoogroups.com <mailto:op25-dev%40yahoogroups.com> , ikjtel wrote:
 What method do you use to measure the correct deviation of the C4FM
signal?
hmm - apols if I've guessed wrong, but sounds like you haven't yet RTFM -
based both on this question and the questions about the repeater.
Have a look atÂ
http://op25.osmocom.org/wiki/wiki/HardwarePage
http://op25.osmocom.org/wiki/wiki/RepeaterPage
http://op25.osmocom.org/wiki/wiki/SignalScopePage
- in particular the Hardware page has a method for setting the deviation -
or you could spend $ on a store-bought FMD meter : )
73 de KA1RBI
I started with ACID, figuring it has to work there, so... If we want this to work with the most popular Allstar distro, someone has to get it built on there and then publish how. While not quite a novice, I am not experienced enough to get it working. I also find that people that write instructions for building things on linux tend to assume their audience already knows how to build it! --- In op25-dev@yahoogroups.com, "Doug Bade" <kd8b@...> wrote:
I too was building or more specifically started over on rebuilding on Ubuntu 10.04 LTS. My build went successfully but not sure about how I can build Allstar Into that J I figured I wanted to try to get SOME documented version to build then figure out how to get it working in the environment I want ( which would be over a ACID build also ) .
I was able to get GNU Radio to compile with no major errors ( read as program stops J ) , to get op25 svn imported, the three op25 modules to compile and install I *THINK* without major errors. Tonight I will go through the build logs and see if I missed anything important. I had errors regarding port audio missing on my Debian build but they did not go bang on Ububtu 10.04 LTS.
I am not trying to steal your thread here, just comparing results along the way and maybe sharing stumbles
Did you start with an Acid build??? I am thinking in the *production* edition I will need to do that ..
I have no confidence it all built correctly yet but the installs at least completed
Doug
KD8B
From: op25-dev@yahoogroups.com [mailto:op25-dev@yahoogroups.com] On Behalf Of n4dav Sent: Tuesday, February 26, 2013 7:24 AM To: op25-dev@yahoogroups.com Subject: [op25-dev] Re: Full asterisk support?
Actually I had RTFM but there's so much there I forgot about that page.
I put a lot of time into this yesterday, trying to build all the parts. I'm using CentOS as that is what the ACID distro is built on for Allstar, and it works well. But trying to get this stuff built is a major exercise in frustration. Every package I tried to build was missing some other dependency, which was missing some other dependency, it was a chain of missing things. I never got anything built. One make complained about python not being at least 2.5, (I had 2.4), so I installed 2.6, verified it with python-V, and still couldn't run the make file. It still thought I had 2.4, and I have no idea how to fix that. I'll probably go back to it after I pull my fist out of the wall but so far it has not been fun.
--- In op25-dev@yahoogroups.com <mailto:op25-dev%40yahoogroups.com> , ikjtel wrote:
 What method do you use to measure the correct deviation of the C4FM
signal?
hmm - apols if I've guessed wrong, but sounds like you haven't yet RTFM -
based both on this question and the questions about the repeater.
Have a look atÂ
http://op25.osmocom.org/wiki/wiki/HardwarePage
http://op25.osmocom.org/wiki/wiki/RepeaterPage
http://op25.osmocom.org/wiki/wiki/SignalScopePage
- in particular the Hardware page has a method for setting the deviation -
or you could spend $ on a store-bought FMD meter : )
73 de KA1RBI
I started on a second computer last evening to try Centos/Allstar as a base. I used the Acid disk. I was able to get a lot of the prerequisites installed but a few are eluding me. I added the repoforge repository to my machine which houses a bunch of the general linux program parts that are needed. Most were able to be installed with yum. I ran out of time so still have more to build. I am keeping notes on what was in Acid and what I had to add I am scraping build information from a couple places. CentOS without a GUI does make it more difficult to build some of this but in the long run will probably be a better more compact build. I saw that ACID has a python 2.4 directory as you noted I will be running into the same issue I am sure. What the answer is I found notes about making a symbolic link to point the machine path to the correct python directory ( kind of an alias thing) so it can find the correct version. The notes were relative to python 3. Something relative to newer builds on Arch Linux which is a bleeding edge version of RHEL of which CentOS is a clone. I do agree that the build docs need some updating and more concise details if versions are an issue.. I see they are circa 2009-2010 ish so makes for some stumbling along the way. Doug KD8B From: op25-dev@yahoogroups.com [mailto:op25-dev@yahoogroups.com] On Behalf Of n4dav Sent: Wednesday, February 27, 2013 7:20 AM To: op25-dev@yahoogroups.com Subject: [op25-dev] Re: Full asterisk support? I started with ACID, figuring it has to work there, so... If we want this to work with the most popular Allstar distro, someone has to get it built on there and then publish how. While not quite a novice, I am not experienced enough to get it working. I also find that people that write instructions for building things on linux tend to assume their audience already knows how to build it! --- In op25-dev@yahoogroups.com <mailto:op25-dev%40yahoogroups.com> , "Doug Bade" wrote:
I too was building or more specifically started over on rebuilding on
10.04 LTS. My build went successfully but not sure about how I can build Allstar Into that J I figured I wanted to try to get SOME documented version to build then figure out how to get it working in the environment I want ( which would be over a ACID build also ) .
I was able to get GNU Radio to compile with no major errors ( read as program stops J ) , to get op25 svn imported, the three op25 modules to compile and install I *THINK* without major errors. Tonight I will go through the build logs and see if I missed anything important. I had errors regarding port audio missing on my Debian build but they did not go bang on Ububtu 10.04 LTS.
I am not trying to steal your thread here, just comparing results along the way and maybe sharing stumbles
Did you start with an Acid build??? I am thinking in the *production* edition I will need to do that ..
I have no confidence it all built correctly yet but the installs at least completed
Doug
KD8B
From: op25-dev@yahoogroups.com <mailto:op25-dev%40yahoogroups.com> [mailto:op25-dev@yahoogroups.com <mailto:op25-dev%40yahoogroups.com> ] On Behalf Of n4dav Sent: Tuesday, February 26, 2013 7:24 AM To: op25-dev@yahoogroups.com <mailto:op25-dev%40yahoogroups.com> Subject: [op25-dev] Re: Full asterisk support?
Actually I had RTFM but there's so much there I forgot about that page.
I put a lot of time into this yesterday, trying to build all the parts. I'm using CentOS as that is what the ACID distro is built on for Allstar, and it works well. But trying to get this stuff built is a major exercise in frustration. Every package I tried to build was missing some other dependency, which was missing some other dependency, it was a chain of missing things. I never got anything built. One make complained about python not being at least 2.5, (I had 2.4), so I installed 2.6, verified it with python-V, and still couldn't run the make file. It still thought I had 2.4, and I have no idea how to fix that. I'll probably go back to it after I pull my fist out of the wall but so far it has not been fun.
--- In op25-dev@yahoogroups.com <mailto:op25-dev%40yahoogroups.com> , ikjtel wrote:
 What method do you use to measure the correct deviation of the C4FM
signal?
hmm - apols if I've guessed wrong, but sounds like you haven't yet RTFM
based both on this question and the questions about the repeater.
Have a look atÂ
http://op25.osmocom.org/wiki/wiki/HardwarePage
http://op25.osmocom.org/wiki/wiki/RepeaterPage
http://op25.osmocom.org/wiki/wiki/SignalScopePage
- in particular the Hardware page has a method for setting the deviation
Ubuntu - -
or you could spend $ on a store-bought FMD meter : )
73 de KA1RBI
Doug, glad you are doing that.. I also found the symbolic link info, and set it up and verified it with python -V. It showed 2.6, which to me means if you run python from anywhere, you get 2.6....except you don't from the makefile, apparently. --- In op25-dev@yahoogroups.com, "Doug Bade" <kd8b@...> wrote:
I started on a second computer last evening to try Centos/Allstar as a base. I used the Acid disk. I was able to get a lot of the prerequisites installed but a few are eluding me. I added the repoforge repository to my machine which houses a bunch of the general linux program parts that are needed. Most were able to be installed with yum.
I ran out of time so still have more to build. I am keeping notes on what was in Acid and what I had to add I am scraping build information from a couple places. CentOS without a GUI does make it more difficult to build some of this but in the long run will probably be a better more compact build.
I saw that ACID has a python 2.4 directory as you noted I will be running into the same issue I am sure. What the answer is I found notes about making a symbolic link to point the machine path to the correct python directory ( kind of an alias thing) so it can find the correct version. The notes were relative to python 3. Something relative to newer builds on Arch Linux which is a bleeding edge version of RHEL of which CentOS is a clone.
I do agree that the build docs need some updating and more concise details if versions are an issue.. I see they are circa 2009-2010 ish so makes for some stumbling along the way.
Doug
KD8B
From: op25-dev@yahoogroups.com [mailto:op25-dev@yahoogroups.com] On Behalf Of n4dav Sent: Wednesday, February 27, 2013 7:20 AM To: op25-dev@yahoogroups.com Subject: [op25-dev] Re: Full asterisk support?
I started with ACID, figuring it has to work there, so...
If we want this to work with the most popular Allstar distro, someone has to get it built on there and then publish how. While not quite a novice, I am not experienced enough to get it working. I also find that people that write instructions for building things on linux tend to assume their audience already knows how to build it!
--- In op25-dev@yahoogroups.com <mailto:op25-dev%40yahoogroups.com> , "Doug Bade" wrote:
I too was building or more specifically started over on rebuilding on
10.04 LTS. My build went successfully but not sure about how I can build Allstar Into that J I figured I wanted to try to get SOME documented version to build then figure out how to get it working in the environment I want ( which would be over a ACID build also ) .
I was able to get GNU Radio to compile with no major errors ( read as program stops J ) , to get op25 svn imported, the three op25 modules to compile and install I *THINK* without major errors. Tonight I will go through the build logs and see if I missed anything important. I had errors regarding port audio missing on my Debian build but they did not go bang on Ububtu 10.04 LTS.
I am not trying to steal your thread here, just comparing results along the way and maybe sharing stumbles
Did you start with an Acid build??? I am thinking in the *production* edition I will need to do that ..
I have no confidence it all built correctly yet but the installs at least completed
Doug
KD8B
From: op25-dev@yahoogroups.com <mailto:op25-dev%40yahoogroups.com> [mailto:op25-dev@yahoogroups.com <mailto:op25-dev%40yahoogroups.com> ] On Behalf Of n4dav Sent: Tuesday, February 26, 2013 7:24 AM To: op25-dev@yahoogroups.com <mailto:op25-dev%40yahoogroups.com> Subject: [op25-dev] Re: Full asterisk support?
Actually I had RTFM but there's so much there I forgot about that page.
I put a lot of time into this yesterday, trying to build all the parts. I'm using CentOS as that is what the ACID distro is built on for Allstar, and it works well. But trying to get this stuff built is a major exercise in frustration. Every package I tried to build was missing some other dependency, which was missing some other dependency, it was a chain of missing things. I never got anything built. One make complained about python not being at least 2.5, (I had 2.4), so I installed 2.6, verified it with python-V, and still couldn't run the make file. It still thought I had 2.4, and I have no idea how to fix that. I'll probably go back to it after I pull my fist out of the wall but so far it has not been fun.
--- In op25-dev@yahoogroups.com <mailto:op25-dev%40yahoogroups.com> , ikjtel wrote:
 What method do you use to measure the correct deviation of the C4FM
signal?
hmm - apols if I've guessed wrong, but sounds like you haven't yet RTFM
based both on this question and the questions about the repeater.
Have a look atÂ
http://op25.osmocom.org/wiki/wiki/HardwarePage
http://op25.osmocom.org/wiki/wiki/RepeaterPage
http://op25.osmocom.org/wiki/wiki/SignalScopePage
- in particular the Hardware page has a method for setting the deviation
Ubuntu - -
or you could spend $ on a store-bought FMD meter : )
73 de KA1RBI
Well I did not get real far . Acid is built on Centos 5.x and I was trying to root up the GNURadio prerequisites and finding that rpm support for them stopped well before the desired versions in the RHEL5.x platform. As Allstar seems to be in a repository format I am thinking it may be easier to build it over something newer that has RPM support for the newer version of the pre-requisites than source building everything over the older versions of 5.x So I started on a basic Desktop install of CentOS 6.x and am trying to get the GNU parts in. Most seem to be in new enough RPM form and many are in the base CentOS repository at 6.x platform. One of the issues I see with ACID build is lack of GUI and GUI parts which seem to hook into the GNURadio and/or op25 stuff. So I am going to see how far I get that way If I can build the GNURadio pre-requisites and compile it, I will then attack app_rpt next.. if both of those fly, last will be op25. We have a chicken/egg thing as ACID wants to be the core system and GNURadio/op25 want to be the core system parts built in a GUI. One path or the other is going to work but as no one else is chiming in here I am guessing no one has a better CURRENT solution than the 2010-ish publishings. Building all the modules from source means stepping through a mine field so I would rather use rpms when I can that are made for the versions we are trying to use. BTW CentOS 6.x is default installed with Python 2.6.x already Doug From: op25-dev@yahoogroups.com [mailto:op25-dev@yahoogroups.com] On Behalf Of n4dav Sent: Thursday, February 28, 2013 7:17 AM To: op25-dev@yahoogroups.com Subject: [op25-dev] Re: Full asterisk support? Doug, glad you are doing that.. I also found the symbolic link info, and set it up and verified it with python -V. It showed 2.6, which to me means if you run python from anywhere, you get 2.6....except you don't from the makefile, apparently. --- In op25-dev@yahoogroups.com <mailto:op25-dev%40yahoogroups.com> , "Doug Bade" wrote:
I started on a second computer last evening to try Centos/Allstar as a
base.
I used the Acid disk. I was able to get a lot of the prerequisites installed but a few are eluding me. I added the repoforge repository to my machine which houses a bunch of the general linux program parts that are needed. Most were able to be installed with yum.
I ran out of time so still have more to build. I am keeping notes on what was in Acid and what I had to add I am scraping build information from a couple places. CentOS without a GUI does make it more difficult to build some of this but in the long run will probably be a better more compact build.
I saw that ACID has a python 2.4 directory as you noted I will be running into the same issue I am sure. What the answer is I found notes about making a symbolic link to point the machine path to the correct python directory ( kind of an alias thing) so it can find the correct version. The notes were relative to python 3. Something relative to newer builds on Arch Linux which is a bleeding edge version of RHEL of which CentOS is a clone.
I do agree that the build docs need some updating and more concise details if versions are an issue.. I see they are circa 2009-2010 ish so makes for some stumbling along the way.
Doug
KD8B
From: op25-dev@yahoogroups.com <mailto:op25-dev%40yahoogroups.com> [mailto:op25-dev@yahoogroups.com <mailto:op25-dev%40yahoogroups.com> ] On Behalf Of n4dav Sent: Wednesday, February 27, 2013 7:20 AM To: op25-dev@yahoogroups.com <mailto:op25-dev%40yahoogroups.com> Subject: [op25-dev] Re: Full asterisk support?
I started with ACID, figuring it has to work there, so...
If we want this to work with the most popular Allstar distro, someone has to get it built on there and then publish how. While not quite a novice, I am not experienced enough to get it working. I also find that people that write instructions for building things on linux tend to assume their audience already knows how to build it!
--- In op25-dev@yahoogroups.com <mailto:op25-dev%40yahoogroups.com> , "Doug Bade" wrote:
I too was building or more specifically started over on rebuilding on
10.04 LTS. My build went successfully but not sure about how I can build Allstar Into that J I figured I wanted to try to get SOME documented version to build then figure out how to get it working in the environment I want ( which would be over a ACID build also ) .
I was able to get GNU Radio to compile with no major errors ( read as program stops J ) , to get op25 svn imported, the three op25 modules to compile and install I *THINK* without major errors. Tonight I will go through the build logs and see if I missed anything important. I had errors regarding port audio missing on my Debian build but they did not go bang on Ububtu 10.04 LTS.
I am not trying to steal your thread here, just comparing results along the way and maybe sharing stumbles
Did you start with an Acid build??? I am thinking in the *production* edition I will need to do that ..
I have no confidence it all built correctly yet but the installs at least completed
Doug
KD8B
From: op25-dev@yahoogroups.com <mailto:op25-dev%40yahoogroups.com> [mailto:op25-dev@yahoogroups.com <mailto:op25-dev%40yahoogroups.com> ] On Behalf Of n4dav Sent: Tuesday, February 26, 2013 7:24 AM To: op25-dev@yahoogroups.com <mailto:op25-dev%40yahoogroups.com> Subject: [op25-dev] Re: Full asterisk support?
Actually I had RTFM but there's so much there I forgot about that page.
I put a lot of time into this yesterday, trying to build all the parts. I'm using CentOS as that is what the ACID distro is built on for Allstar, and it works well. But trying to get this stuff built is a major exercise in frustration. Every package I tried to build was missing some other dependency, which was missing some other dependency, it was a chain of missing things. I never got anything built. One make complained about python not being at least 2.5, (I had 2.4), so I installed 2.6, verified it with python-V, and still couldn't run the make file. It still thought I had 2.4, and I have no idea how to fix that. I'll probably go back to it after I pull my fist out of the wall but so far it has not been fun.
--- In op25-dev@yahoogroups.com <mailto:op25-dev%40yahoogroups.com> , ikjtel wrote:
 What method do you use to measure the correct deviation of the C4FM
signal?
hmm - apols if I've guessed wrong, but sounds like you haven't yet
RTFM
based both on this question and the questions about the repeater.
Have a look atÂ
http://op25.osmocom.org/wiki/wiki/HardwarePage
http://op25.osmocom.org/wiki/wiki/RepeaterPage
http://op25.osmocom.org/wiki/wiki/SignalScopePage
- in particular the Hardware page has a method for setting the
deviation
Ubuntu - -
or you could spend $ on a store-bought FMD meter : )
73 de KA1RBI
strange unprintable characters in this email - it's a fun day --- In op25-dev@yahoogroups.com, "Doug Bade" <kd8b@...> wrote:
Well I did not get real far�. Acid is built on Centos 5.x and I was trying to root up the GNURadio prerequisites and finding that rpm support for them stopped well before the desired versions in the RHEL5.x platform.
Is ACID a pre-built distro of asterisk or something? I didn't use ACID, I found it easier to build the Jim Dixon app_rpt version of asterisk from sources - there shouldn't be a lot of pre-reqs. [http://ohnosec.org/drupal/node/6] Once the directory is unpacked, just do the usual ./configure && make && sudo make install first from the zaptel directory then from the asterisk directory. This will give you a solid command-line (no gui) version of asterisk with the latest app_rpt, you can also do "sudo make samples" from the asterisk directory to install the sample * config files. Most folks I know who've tried them don't like the various * gui's (ymmv). Before doing this you just need to copy the two "USRP" channel driver files (chan_usrp.c and chan_usrp.h) from the op25 source tree to the proper * directory (as described in the repeater wiki page).
As Allstar seems to be in a repository format I am thinking it may be easier to build it over something newer that has RPM support for the newer version of the pre-requisites than source building everything over the older versions of 5.x
So I started on a basic Desktop install of CentOS 6.x and am trying to get the GNU parts in. Most seem to be in new enough RPM form and many are in the base CentOS repository at 6.x platform.
One of the issues I see with ACID build is lack of GUI and GUI parts which seem to hook into the GNURadio and/or op25 stuff.
The hook is that the driver modules must be installed before building asterisk app_rpt (see above and RTFM the wiki)
So I am going to see how far I get that way�
If I can build the GNURadio pre-requisites and compile it, I will then attack app_rpt next.. if both of those fly, last will be op25.
We have a chicken/egg thing as ACID wants to be the core system and GNURadio/op25 want to be the core system parts built in a GUI.
There really isn't any conflict here - even assuming for argument's sake you wanted to use the * GUI (which I've chosen not to). If you run asterisk/app_rpt under a GUI it gives you a window through which you can "manage" asterisk. When you run, say, the soundcard_tx app from the op25 side in order to drive the soundcard TX in P25 mode, there is an (optional) GUI window that the soundcard app furnishes - consisting of the "C4FM" oscilloscope and a "File"->"Exit" button. Both of these would simply sit on your desktop - each in its own window. There is no fight over primacy - both are completely separate apps. In fact these two apps (asterisk/app_rpt and soundcard_tx) might run on completely separate machines. Regardless of whether they're on the same machine or not, they use UDP ports for communication...
One path or the other is going to work but as no one else is chiming in here I am guessing no one has a better CURRENT solution than the 2010-ish publishing�s.
Building all the modules from source means stepping through a mine field so I would rather use rpm�s when I can that are made for the versions we are trying to use.
BTW CentOS 6.x is default installed with Python 2.6.x already�
Generally speaking I suspect life would be a lot easier when using python 2.6 than 2.4
Doug
73 Max
I am going to throw my hat in too as a test site... I have been copying the mail on this group for a while but had not really caught the fact that the project was repeater capable. I have a station that I can direct FM down pretty much to DC... ( Mastr III) ex-edacs station. It has modulation ports I have been using for GMSK for D-Star to date using sound FOBS. I am going to try to build all this but have a steep learning curve as I have not even ever built the GNU radio parts.. So maybe I can also be a test bed. I do have a P25 analyzer for setup. ( I maintain P25 systems (among other things)for a living ) I have some dedicated Atom rack mount servers for building on.. When I built pre-re4quisits last night I had errors on SDCC and SDCC-libraries on a fresh Debian build. Is the system particular about versions of those? or just go get what I can find?? My Debian box was building GNU radio stuff when I went to bed.. so I will get back to it tonight.. I never really introduced myself here just been lurking... I am an LMR systems engineer for a living and work on public safety P25 systems.. but am an extra ham who likes to tinker.. P25 has always been a goal, as P25 cards upgrades for my Mastr III station would run about $8000.00 if I did it the Harris way :-) Doug KD8B -
I guess another important question is if I am going to use asterisk, do I want to start with an asterisk build first?? Or add it to this Debian box?? The build information does not really seems to mention where asterisk enters in.. ( I have experience with Allstar Link and Asterisk PBX's for phone). Doug KD8B From: op25-dev@yahoogroups.com [mailto:op25-dev@yahoogroups.com] On Behalf Of Doug Bade Sent: Monday, February 25, 2013 9:43 AM To: op25-dev@yahoogroups.com Subject: [op25-dev] Re: Full asterisk support? I am going to throw my hat in too as a test site... I have been copying the mail on this group for a while but had not really caught the fact that the project was repeater capable. I have a station that I can direct FM down pretty much to DC... ( Mastr III) ex-edacs station. It has modulation ports I have been using for GMSK for D-Star to date using sound FOBS. I am going to try to build all this but have a steep learning curve as I have not even ever built the GNU radio parts.. So maybe I can also be a test bed. I do have a P25 analyzer for setup. ( I maintain P25 systems (among other things)for a living ) I have some dedicated Atom rack mount servers for building on.. When I built pre-re4quisits last night I had errors on SDCC and SDCC-libraries on a fresh Debian build. Is the system particular about versions of those? or just go get what I can find?? My Debian box was building GNU radio stuff when I went to bed.. so I will get back to it tonight.. I never really introduced myself here just been lurking... I am an LMR systems engineer for a living and work on public safety P25 systems.. but am an extra ham who likes to tinker.. P25 has always been a goal, as P25 cards upgrades for my Mastr III station would run about $8000.00 if I did it the Harris way :-) Doug KD8B -
The build sequence (asterisk vs. gnuradio) is not important. The folks who produce app_rpt have their own forked version of asterisk, which was the one that I used. Everything is coupled so loosely that there should not be much problem to mix & match this stuff - although of course ymmv : ) The integration with asterisk is intended to be pretty extensible - currently the examples all use app_rpt in its "dumb" mode. I'm sure that's a good starting point but that a lot more could be done with some imagination. The choice of app_rpt was mainly because that already provides almost the perfect set of semantics for what we want, and was pretty mature in terms of capability. However the link to asterisk should be viewed as a generalized "VOIP" bridge to OP25 not limited to repeaters in the conventional sense... (think "ROIP") There are some places where the existing asterisk app_rpt metaphor works less than perfectly. The first is the app_rpt model in which audio that's been received over the RX leg of a FDX link must first be demodulated and re-converted back to analog before feeding through the app_rpt main path. This is Not Good due to the highly lossy IMBE codec. A true digital P25 repeater would just regenerate the signal digitally before retransmission. Unfortunately however this would cut app_rpt out of the picture completely. A direct digital repeater is being looked at (with very slow progress). Another problem is that DTMF tones (used heavily within asterisk and app_rpt) are verboten in P25 (P25 has replacements in the form of packets that are defined in the protocol for the purpose of sending dial digits). At this stage in time I don't view the extra digital/analog/digital reconversion steps as a problem. That would presuppose that the FDX links were working fully end to end. Before that can happen we must first debug the individual legs, which is much easier to do separately... Looking forward to getting feedback from experimenters - it will help to guide the development! 73 Max --- In op25-dev@yahoogroups.com, "Doug Bade" <kd8b@...> wrote:
I guess another important question is if I am going to use asterisk, do I want to start with an asterisk build first?? Or add it to this Debian box?? The build information does not really seems to mention where asterisk enters in.. ( I have experience with Allstar Link and Asterisk PBX's for phone).
Doug
KD8B
From: op25-dev@yahoogroups.com [mailto:op25-dev@yahoogroups.com] On Behalf Of Doug Bade Sent: Monday, February 25, 2013 9:43 AM To: op25-dev@yahoogroups.com Subject: [op25-dev] Re: Full asterisk support?
I am going to throw my hat in too as a test site...
I have been copying the mail on this group for a while but had not really caught the fact that the project was repeater capable. I have a station that I can direct FM down pretty much to DC... ( Mastr III) ex-edacs station. It has modulation ports I have been using for GMSK for D-Star to date using sound FOBS. I am going to try to build all this but have a steep learning curve as I have not even ever built the GNU radio parts.. So maybe I can also be a test bed. I do have a P25 analyzer for setup. ( I maintain P25 systems (among other things)for a living ) I have some dedicated Atom rack mount servers for building on.. When I built pre-re4quisits last night I had errors on SDCC and SDCC-libraries on a fresh Debian build. Is the system particular about versions of those? or just go get what I can find?? My Debian box was building GNU radio stuff when I went to bed.. so I will get back to it tonight..
I never really introduced myself here just been lurking... I am an LMR systems engineer for a living and work on public safety P25 systems.. but am an extra ham who likes to tinker.. P25 has always been a goal, as P25 cards upgrades for my Mastr III station would run about $8000.00 if I did it the Harris way :-)
Doug KD8B
-
--- In op25-dev@yahoogroups.com, "Doug Bade" <kd8b@...> wrote:
errors on SDCC and SDCC-libraries on a fresh Debian build. Is the system particular about versions of those?
We don't use SDCC in op25 at all (AFAIK). The requirement comes from gnuradio itself and (again, IIRC) is used to build some stuff for the 8051 chip needed by the USRP layers... It's probably kosher to get a standard version of SDCC, but not sure... Max
Max; Thanks! It was in the pre-requisites so I had to ask, I am unable to find both the sdcc and sdcc -libraries in the same revision number so not sure if it is going to be an issue. Not planning on using USRP at this point so I guess if GNURadio builds ok, it is probably moot. I have a bunch of usb sound fobs from D-Star stuff that have high resolution DACS so hope they will work OK. We ran into trouble in GMSK with crosstalk in them when trying to use one for TX and RX so ended up splitting up to use 2 separate ones for TX and RX. I will continue compiling tonight and see what happens.. Is the IT++ stuff need for USRP only too??? I am having trouble searching it++ in messages as it gives me everything with "it" in it .. Doug KD8B From: op25-dev@yahoogroups.com [mailto:op25-dev@yahoogroups.com] On Behalf Of ikj1234i Sent: Monday, February 25, 2013 9:55 AM To: op25-dev@yahoogroups.com Subject: [op25-dev] Re: Full asterisk support? --- In op25-dev@yahoogroups.com <mailto:op25-dev%40yahoogroups.com> , "Doug Bade" wrote:
errors on SDCC and SDCC-libraries on a fresh Debian build. Is the system particular about versions of those?
We don't use SDCC in op25 at all (AFAIK). The requirement comes from gnuradio itself and (again, IIRC) is used to build some stuff for the 8051 chip needed by the USRP layers... It's probably kosher to get a standard version of SDCC, but not sure... Max
--- In op25-dev@yahoogroups.com, "Doug Bade" <kd8b@...> wrote:
Is the IT++ stuff need for USRP only too???
IIRC the IT++ stuff is not used directly by any of the code in the repeater branch of the project. However repeater may depend on the code in the blocks directory, which directly requires IT++.... Max
Thanks! I will hunt it down, the link on the build instructions wiki page seems to be broken. But a google search was valid. Doug KD8B From: op25-dev@yahoogroups.com [mailto:op25-dev@yahoogroups.com] On Behalf Of ikj1234i Sent: Monday, February 25, 2013 10:32 AM To: op25-dev@yahoogroups.com Subject: [op25-dev] Re: Full asterisk support? --- In op25-dev@yahoogroups.com <mailto:op25-dev%40yahoogroups.com> , "Doug Bade" wrote:
Is the IT++ stuff need for USRP only too???
IIRC the IT++ stuff is not used directly by any of the code in the repeater branch of the project. However repeater may depend on the code in the blocks directory, which directly requires IT++.... Max
--- In op25-dev@yahoogroups.com, "n4dav" <n4dav@...> wrote:
I thought the USRP_TX app was only for that hardware. I want to use a conventional radio, just as you described, for both P25 and NBFM. So sign me up as as experimenter wanting to try that!
Right. I've just pushed a new app - soundcard_tx.py for exactly that purpose. The wiki page for the repeater has been updated at the end of the page to add info about the soundcard TX app. Right now there still are the older apps for doing soundcard P25 TX (but lacking asterisk integration). These older apps use a more conservative method for generating the modulation waveforms, and the soundcard TX app uses a trickier method. Accordingly the former apps should be the first ones selected for testing if unsure. As for the issue about using the same radio to tx both analog NBFM and P25 (but obviously not at the same time) the first question that would need to be resolved is how to choose the mode and how to identify it to the software. The actual choice should probably be made somewhere in the asterisk world - but I'm not at all sure about that... Comments please... In the actual implementation it probably won't hard to add analog FM support to soundcard_tx.py (how to choose which mode is the tough part). I think the developers of app_rpt *hate* soundcards - not sure if that's because they also sell the analog repeater/adapter/controller boards for app_rpt use. The USRP and friends will one day put that entire class of hardware into the same bin as the horse and buggy... 73 Max
Actually, they dont sell cards anymore. The usb sound fob is the preferred method, and you can get one for about 12 bucks. --- In op25-dev@yahoogroups.com, "ikj1234i" <ikj1234i@...> wrote:
--- In op25-dev@yahoogroups.com, "n4dav" <n4dav@> wrote:
I thought the USRP_TX app was only for that hardware. I want to use a conventional radio, just as you described, for both P25 and NBFM. So sign me up as as experimenter wanting to try that!
Right. I've just pushed a new app - soundcard_tx.py for exactly that purpose. The wiki page for the repeater has been updated at the end of the page to add info about the soundcard TX app.
Right now there still are the older apps for doing soundcard P25 TX (but lacking asterisk integration). These older apps use a more conservative method for generating the modulation waveforms, and the soundcard TX app uses a trickier method. Accordingly the former apps should be the first ones selected for testing if unsure.
As for the issue about using the same radio to tx both analog NBFM and P25 (but obviously not at the same time) the first question that would need to be resolved is how to choose the mode and how to identify it to the software. The actual choice should probably be made somewhere in the asterisk world - but I'm not at all sure about that... Comments please... In the actual implementation it probably won't hard to add analog FM support to soundcard_tx.py (how to choose which mode is the tough part).
I think the developers of app_rpt *hate* soundcards - not sure if that's because they also sell the analog repeater/adapter/controller boards for app_rpt use. The USRP and friends will one day put that entire class of hardware into the same bin as the horse and buggy...
73
Max
participants (5)
-
Doug Bade -
ikj1234i -
ikjtel
-
md123＠nycap.rr.com -
n4dav