- Allstar-Digital - lists.keekles.org

Re: [Allstar Digital] Allstar-Digital Digest, Vol 6, Issue 2
by Chris HIll/K7AZ 09 May '16

09 May '16

Is this digest still active? Chris K7AZ Sent from my dumb-smart DROID... allstar-digital-request(a)lists.keekles.org wrote: >Send Allstar-Digital mailing list submissions to > allstar-digital(a)lists.keekles.org > >To subscribe or unsubscribe via the World Wide Web, visit > http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital >or, via email, send a message with subject or body 'help' to > allstar-digital-request(a)lists.keekles.org > >You can reach the person managing the list at > allstar-digital-owner(a)lists.keekles.org > >When replying, please edit your Subject line so it is more specific >than "Re: Contents of Allstar-Digital digest..." > > >Today's Topics: > > 1. Re: status so far (Robert Newberry) > 2. Looking for test subject (Robert Newberry) > 3. Re: status so far (Steve Zingman) > 4. Re: status so far (Robert Newberry) > > >---------------------------------------------------------------------- > >Message: 1 >Date: Wed, 2 Mar 2016 13:06:07 -0500 >From: Robert Newberry <N1XBM(a)amsat.org> >To: Digital linking using Asterisk and app_rpt > <allstar-digital(a)lists.keekles.org> >Subject: Re: [Allstar Digital] status so far >Message-ID: > <CAM09xEYpzQx4Z7xzgSkWSGE2XNzzzkhDqTxx1kpsGY4-CuEmrA(a)mail.gmail.com> >Content-Type: text/plain; charset="utf-8" > >My fault on the ID, I understand why the IDs need to be unique. I >misunderstood the big picture. Once Mike explained it, I understood. > >Now what about the template.bin? Is there an explanation for that such as a >screw up in my end? > >N1XBM >Apparare Scientor >Paratus Communicare >Allstar Node # 27086, 41540, 41812, 42086, 42658 > >On Mar 1, 2016 10:02 AM, "Steve Zingman" <szingman(a)msgstor.com> wrote: > >> Update: >> I logged in to Roberts node. He had the Radio ID for the dmrlink.cfg peer >> set the same as the Motorola repeater he was trying to connect from. That >> is wrong. Each Master / Peer in a IPSC network needs a unique Radio ID. He >> also had the gatewayDmrId set to the same Radio ID as the repeater. Last >> but not least, template.bin which is required for AllStar ---> DMR was not >> in the ambe_audio directory. He is now up and running. >> >> 73, Steve N4IRS >> >> On Sun, Feb 28, 2016 at 10:18 PM, Robert Newberry <N1XBM(a)amsat.org> wrote: >> >>> Going to call it a night, the bridge appears to be working OK. I am >>> hearing feeds from other networks. >>> >>> I do not have the gateway running yet. for audio in either direction. >>> When ambe_audio.py runs I am not seeing any errors on DEBUG. I am how ever >>> not seeing any traffic when I key up my HT, which leads me to believe I've >>> missed a setting somewhere. I would assume I should see some reference to >>> TS and TG that it might be seeing. >>> >>> Now I'm too a point where I'm spinning my wheels and need some rest. >>> >>> _______________________________________________ >>> Allstar-Digital mailing list >>> Allstar-Digital(a)lists.keekles.org >>> http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital >>> >>> >> >> _______________________________________________ >> Allstar-Digital mailing list >> Allstar-Digital(a)lists.keekles.org >> http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital >> >> >

2 1

DMRGateway configuration
by Steve Zingman 07 May '16

07 May '16

I know it's been rather quiet lately. Mike and I have been working on a number of Digital and Analog projects. Some will be demonstrated at Dayton, so we are coming down to the wire. I have been configuring DMRGateway on a Micro-Node DPAC for the show. It's built on the next revision of DIAL for the RPi. Though most of the underlying Asterisk, DMRGateway and DMRlink code is mostly unchanged I ran in to something "interesting" Consider the DPAC. It's a dual node AllStar server with 2 radio ports, hardware real time clock, serial console port and dual TFT displays. it mounts in a 1 RU box. For the demo, I set it up with 2 analog repeaters and a DMRGateway. The idea is that the DMRGateway is a "private" node (1997) if either of the 2 analog repeaters wanted DMR access they could just connect to 1997 and they would be on DMR. Pretty much the same way that anyone might setup a tightly controlled ASL <---> DMR Gateway. Using the remote control ability built into ambe_audio a analog user can change to pre-defined TS / TG configurations with DTMF. This can also be done from Allmon2. There is also a standalone client coming called DMRGui. Think a DMR node with a local mic and speaker. Now comes the issue. We know that a DMRGateway node should be setup with duplex = 0 and comment out the idrecording and idtalkover entries so no ID goes out over DMR. With a duplex = 0 there should be no hang time or telemetry. Or so would one think. Turns out that the USRP channel driver still uses the hangtime and possibly the alt hangtime values. If you just comment them out, you get the default values of 5000 ms. Set hangtime and althangtime to 0 !!! Otherwise there is a hang time between the drop of the input analog signal and the drop of the outbound DMR signal. We are checking the code now, and we THINK it's in the USRP channel driver. Not sure it's a negative yet. There is a small hang built in DMRGateway on purpose. For INAD, 73 Steve N4IRS -- "Anything is possible if you don't know what you are talking about." 1st Law of Logic

1 0

CC connections dmrlink
by Robert Newberry 27 Apr '16

27 Apr '16

I was talking to a c-bridge owner today. He asked if I was capable of a cc connection. I'm pretty sure Dmrlink is not capable of it as it is something only the Rayfield's can do. I figured I would double check. I couldn't see anything in the files that referenced it. N1XBM Apparare Scientor Paratus Communicare Allstar Node # 27086, 41540, 41812, 42086, 42658, 42657

2 1

Re: [Allstar Digital] dmrgateway
by Steve Zingman 23 Apr '16

23 Apr '16

The one way connection you describe I believe has been a routing issue on BM. Here is some data From http://84.232.5.113/status/status.htm @ 06:42 EST Your connection to the Master: SmartPTT Bridge Network 2148006 - 106, 24588, 1026, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 1005697088, 0, 0, 0, 0, 0 From /etc/opt/dmrlink/ambe_audio.cfg This is the TS and TG ambe_audio is using [BM] # BrandMeister tgFilter = 9108 # A list of TG IDs to monitor. All TGs will be passed to DMRGateway txTg = 9108 # TG to use for all frames received from DMRGateway -> IPSC txTs = 2 # Slot to use for frames received from DMRGateway -> IPSC From /opt/dmrlink/ambe_audio/dmrlink.cfg [BM] ENABLED: True RADIO_ID: 2148006 IP: 192.168.0.194 PORT: 50000 ALIVE_TIMER: 5 MAX_MISSED: 20 PEER_OPER = True IPSC_MODE = DIGITAL TS1_LINK: True TS2_LINK: True CSBK_CALL = False RCM = True CON_APP = True XNL_CALL = False XNL_MASTER = False DATA_CALL = True VOICE_CALL = True MASTER_PEER = False AUTH_ENABLED = False AUTH_KEY: MASTER_IP: 84.232.5.113 MASTER_PORT: 55001 From a BM Master, this is what the routing should look like. This is mine: --[ Links for N4IRS ]-- if (destination == 3100) then local contexts = getContextTable() for _, parameters in pairs(contexts) do -- To SmartPTT if (parameters.number == 311221) and (number ~= 311221) then newRoute(LINK_TYPE_NETWORK, 311221, 1, 0) end -- From SmartPTT if (number == 311221) and (parameters.name == "FastForward") then newRoute(parameters.object, slot, 0) end end end 73, Steve N4IRS On 04/23/2016 12:12 AM, ea8ee wrote: > It seems in BM that routing is tg9108 to 2148006 > El El sáb, 23 abr 2016 a las 5:03, ea8ee <ea8ee1(a)gmail.com > <mailto:ea8ee1@gmail.com>> escribió: > > and the ip ssh port is not correct ea8ee.no-ip.org:222 > <http://ea8ee.no-ip.org:222> routing works well from ea8ee > 2,148,003 tg to 9108 when someone speaks for allstar but I guess > if someone speaks for tg 9108 should route it to 2148003? I do not > see what is the connection of the master smartptt 2141 > El El sáb, 23 abr 2016 a las 4:31, Steve Zingman > <szingman(a)msgstor.com <mailto:szingman@msgstor.com>> escribió: > > That sounds like a BM routing problem. Please check the TG > routing on BM. > > On Apr 22, 2016 11:02 PM, ea8ee <ea8ee1(a)gmail.com > <mailto:ea8ee1@gmail.com>> wrote: > > I tested the gateway dmr when I pass by allstarlink I hear > perfectly by tg9108 however does not happen the other way > around when I speak of the tg9108 I hear nothing in the > allstar > > ---------- Forwarded message --------- > From: Steve Zingman <szingman(a)msgstor.com > <mailto:szingman@msgstor.com>> > Date: El sáb, 23 abr 2016 a las 3:18 > Subject: Re: dmrgateway > To: ea8ee <ea8ee1(a)gmail.com <mailto:ea8ee1@gmail.com>> > > > To start the gateway: > cd /opt/dmrlink/ambe_audio > python ambe_audio.py & > /usr/local/bin/DMRGateway & > > > On 04/22/2016 10:15 PM, ea8ee wrote: > > done tg9108 slot 2 enroute to 2148006 > El El jue, 21 abr 2016 a las 22:31, Steve Zingman > <szingman(a)msgstor.com <mailto:szingman@msgstor.com>> > escribió: > > On Apr 21, 2016 11:49 AM, Steve Zingman > <szingman(a)msgstor.com > <mailto:szingman@msgstor.com>> wrote: > > I see you rebooted the server. > So, > to start the gateway: > python /opt/dmrlink/ambe_audio/ambe_audio.py & > /usr/local/bin/DMRGateway & > > Steve > > On 4/21/2016 10:38 AM, ea8ee wrote: > > I just go with the password albacete 12 I > have to change the routing in the master > tg you notice when ready > > 2016-04-21 15:02 GMT+01:00 Steve Zingman > <szingman(a)msgstor.com > <mailto:szingman@msgstor.com>>: > > did you change the root password? I'm > trying albacete12 > > > On 4/21/2016 9:54 AM, ea8ee wrote: > > one moment > > 2016-04-21 14:52 GMT+01:00 Steve > Zingman <szingman(a)msgstor.com > <mailto:szingman@msgstor.com>>: > > Is TG9108 routed to 2148006? > > On 4/21/2016 9:49 AM, ea8ee wrote: > > done, try again > > 2016-04-21 14:18 GMT+01:00 > Steve Zingman > <szingman(a)msgstor.com > <mailto:szingman@msgstor.com>>: > > OK, > I can not proceed > without it. > > > On 4/21/2016 8:51 AM, > ea8ee wrote: > > i will change the > usb connector > El El jue, 21 abr > 2016 a las 13:35, > Steve Zingman > <szingman(a)msgstor.com > <mailto:szingman@msgstor.com>> > escribió: > > I don't see it > connected. > root@ea8ee:/etc/asterisk# > lsusb > Bus 005 Device > 002: ID > 058f:6362 > Alcor Micro > Corp. Flash > Card Reader/Writer > Bus 005 Device > 001: ID > 1d6b:0002 > Linux > Foundation 2.0 > root hub > Bus 004 Device > 001: ID > 1d6b:0001 > Linux > Foundation 1.1 > root hub > Bus 003 Device > 001: ID > 1d6b:0001 > Linux > Foundation 1.1 > root hub > Bus 002 Device > 001: ID > 1d6b:0001 > Linux > Foundation 1.1 > root hub > Bus 001 Device > 001: ID > 1d6b:0001 > Linux > Foundation 1.1 > root hub > > > > On 4/21/2016 > 8:34 AM, ea8ee > wrote: > > usb > El El jue, > 21 abr > 2016 a las > 13:26, > Steve > Zingman > <szingman(a)msgstor.com > <mailto:szingman@msgstor.com>> > escribió: > > how is > the > DV3000 > connected? > GPIO? USB? > > > On > 4/21/2016 > 7:20 > AM, > ea8ee > wrote: > > ed8zab > 2148006 > i > can forward > the tg9108 > to > this > id > 84.232.5.113 > ea8ee > 2148003 > > El > El > jue, > 21 > abr 2016 > a > las 11:29, > Steve > Zingman > <szingman(a)msgstor.com > <mailto:szingman@msgstor.com>> > escribió: > > What > radio > (repeater) > ID > are > you > presenting > to > BM? > Have > you > routed > a TG > to > that > ID? > What > is > the > IP > of > the > master > to > connect > to? > What > radio > ID > do > you > want > the > traffic > coming > from > DMRGateway > to > use? > > > On > 04/21/2016 > 06:26 > AM, > ea8ee > wrote: > > I made > some > changes > in > a file > in > any > case > the > id > is > 2148006 > ed8zab > I am > national > co-manager > of > the > master > 2141 > and > selected > th9108 > El > El > jue, > 21 > abr > 2016 > a las > 10:51, > Steve > Zingman > <szingman(a)msgstor.com > <mailto:szingman@msgstor.com>> > escribió: > > You > have > not > put > in > and > radio > IDs > for > dmrlink > or > ambeaudio. > dmrlink.cfg > needs > the > radio > id > you > want > to > use > to > connect > to > BM. > ambe_audio.cfg > needs > the > radio > id > you > want > to > show > up > when > a AllStar > node > transmits > through > the > gateway. > You > also > need > to > arrange > with > your > BM > administrator > for > what > Talk > Groups > to > route > to > your > repeater. > > Steve > > > > > On > 04/21/2016 > 04:37 > AM, > ea8ee > wrote: > > Steve > tried > to > read > all > the > information > dmrgateway > but > I am > not > able > to > activate > it > my > linux > isnt > enough > good, > you > could > lend > me > a hand > my > id > is > 2148002 > and > tg > 9108 > in > BM, > ip > ea8ee.no-ip.org:222 > <http://ea8ee.no-ip.org:222> > and > password > albacete12 > > > -- > "Anything is possible if you don't know what you are talking about." > 1st Law of Logic > > > -- > "Anything is possible if you don't know what you are talking about." > 1st Law of Logic > > > -- > "Anything is possible if you don't know what you are talking about." > 1st Law of Logic > > > -- > "Anything is possible if you don't know what you are talking about." > 1st Law of Logic > > > -- > "Anything is possible if you don't know what you are talking about." > 1st Law of Logic > > > > -- > "Anything is possible if you don't know what you are talking about." > 1st Law of Logic > > > > -- > "Anything is possible if you don't know what you are talking about." > 1st Law of Logic > > > > -- > "Anything is possible if you don't know what you are talking about." > 1st Law of Logic > > > -- > "Anything is possible if you don't know what you are talking about." > 1st Law of Logic > -- "Anything is possible if you don't know what you are talking about." 1st Law of Logic

1 0

port forwarding
by ea8ee 23 Apr '16

23 Apr '16

you need to open some udp port on my router? I have done tests and from allstar works well but contrary to dmr not receive audio

1 0

Audio delay
by Robert Newberry 14 Apr '16

14 Apr '16

Just thought I'd post an update. I noticed with long winded extended QSO on allstar the delay of audio going to DMR would get up to 5 seconds. I had been talking with N4IRS over the air about it a few days ago. He suggested I check my log levels. I had everything set to INFO and I changed it all to CRITICAL. The problem wasn't noticed until a long QSO was going on. Today I monitored another long winded extended QSO and the delay appeared consistent the whole QSO and appeared to be one second or less judging by ear. N1XBM Apparare Scientor Paratus Communicare Allstar Node # 27086, 41540, 41812, 42086, 42658, 42657

1 0

Observations while in use DMRgateway
by Robert Newberry 11 Apr '16

11 Apr '16

There was a extended QSO going to today on my analog side of the network. I was listening in on DMR. I noticed one of the users would consistently drop out like he was on VOX or letting off on the PTT. It was brief so I didn't seem to miss much. The other user didn't seem to have an issue keeping the DMR side keyed up. The other thing I noticed as the QSO went long the delay from analog to digital was about 5 seconds. Just wondering if anyone has observed this? N1XBM Apparare Scientor Paratus Communicare Allstar Node # 27086, 41540, 41812, 42086, 42658, 42657

1 0

Dayton
by Steve Zingman 11 Apr '16

11 Apr '16

We will be in Dayton showing DIAL, DMRGateway, DMRlink and... Mike N4IRR Kurt K4SRN Steve N4IRS Coming in Thursday Leaving Sunday Staying in South Dayton at the Country Inn We will be in the Repeater-Builder booth and the Micro-Node booth. For INAD 73, Steve N4IRS -- "Anything is possible if you don't know what you are talking about." 1st Law of Logic

3 2

Re: [Allstar Digital] Dayton
by Mark Guibord 10 Apr '16

10 Apr '16

Say what!!! Please explain your comment David I don't think you know the whole story. I was ask by Jim in 2011 to develop a professionally packaged version of the original voter/simulcast hardware at a reasonable price that hams could afford. We did just that at our cost not to mention the cost for a development computer, test equipment as well as many RTCM's given to Jim during the design phase. I realize Jim has a very big investment of time developing the Allstar software system but I in no way ripped him off, no one is getting rich here. I would appreciate it if you have a problem with me that you be courteous enough to contact me directly before you publicly make derogatory statements without knowing the whole story. Mark Guibord Micro-Node International From: Allstar-Digital [mailto:allstar-digital-bounces@lists.keekles.org] On Behalf Of David KE6UPI Sent: Sunday, April 10, 2016 12:11 PM To: Digital linking using Asterisk and app_rpt Subject: Re: [Allstar Digital] Dayton I guess I'll see you there, but not with Micro-Node guy. You know he ripped off WB6NIL over the RTCM he sales. David On Sun, Apr 10, 2016 at 10:01 AM, Steve Zingman <szingman(a)msgstor.com> wrote: We will be in Dayton showing DIAL, DMRGateway, DMRlink and... Mike N4IRR Kurt K4SRN Steve N4IRS Coming in Thursday Leaving Sunday Staying in South Dayton at the Country Inn We will be in the Repeater-Builder booth and the Micro-Node booth. For INAD 73, Steve N4IRS -- "Anything is possible if you don't know what you are talking about." 1st Law of Logic _______________________________________________ Allstar-Digital mailing list Allstar-Digital(a)lists.keekles.org http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital

1 0

DMRlink and RDAC
by Robert Newberry 08 Apr '16

08 Apr '16

I am wondering if anyone is using RDAC with DRMlink? Can I ask how you are doing it?

2 3