Re: Early Adopters Pre-Sale for the Digital Radio Amateur Workstation - DRAWS
John,
Nice product, why not make the little unit compatible with other
SBCs other than Rasberry Pi? Maybe an added usb port to interface
would make the unit interface with many SBCs and making sales go
up even more?
Will / W4WWM
toggle quoted messageShow quoted text
On 9/21/2018 3:52 PM, John D Hays -
K7VE wrote:
DRAWS - Raspberry Pi HAT
[The boards will be run in the next couple of weeks, this is
an opportunity to order early and save $20 on the board, and
$5 on the GPS LNA Antenna]
HW Features:
• Raspberry Pi 3 Compliant HAT
• Power HAT and Pi from 6-15VDC
• Onboard Voltage Monitor
• 2 Radio Interfaces
• On Board GPS
• Optional External Antenna w/LNA
• PPS for Stratum 1 Time Source
• Battery Backed Real Time Clock
• Accessory Port
• PWR, IO, Serial Port, Analog In
• Headless, operate from your Computer
• Workstation, operate locally by adding
Open Source Software:
DRAWS™ self identifies to the OS for
configuration.
An image will be available on release with
popular applications pre-installed, including:
• Digital Voice Repeater/Hotspot
Order at http://nwdigitalradio.com/product/draws-digital-radio-amateur-workstation/
For those who were not in attendance at DCC or the NWAPRS
Summer Gathering, NW Digital Radio will be offering
a tiered roll out of the DRAWS product.
Individual components such as the DRAWS HAT, GPS LNA
Antenna, Metal Case, Pre-loaded SD Card, ... will be
available for purchase independently.
The initial offering will be only for the HAT and optional
antenna. Other offerings will roll out over the 4th
quarter.
There will also be an offer for a complete, assembled
system with all components integrated in a single package.
Specific bundles (e.g. everything but the Raspberry Pi)
may be offered as well.
John D. Hays
Edmonds,
WA
K7VE
|
|
My call is WV8CW.trying to log in 3101.
: 2018-09-25 01:15:38.900 DMR Talker Alias (Data Format 1, Received 6/7 char): 'KA1MXL'
E: 2018-09-25 01:15:39.206 DMR, Connection to the master has timed out, retrying connection
M: 2018-09-25 01:15:39.206 DMR, Closing DMR Network
M: 2018-09-25 01:15:39.206 DMR, Opening DMR Network
M: 2018-09-25 01:15:39.606 DMR Talker Alias (Data Format 1, Received 7/7 char): 'KA1MXL '
M: 2018-09-25 01:15:44.782 DMR Slot 2, received network end of voice transmission, 6.6 seconds, 0% packet loss, BER: 0.0%
M: 2018-09-25 01:15:49.436 DMR, Logged into the master successfully
E: 2018-09-25 01:16:44.555 DMR, Connection to the master has timed out, retrying connection
M: 2018-09-25 01:16:44.555 DMR, Closing DMR Network
M: 2018-09-25 01:16:44.555 DMR, Opening DMR Network
M: 2018-09-25 01:16:54.762 DMR, Logged into the master successfully
M: 2018-09-25 01:17:02.394 DMR Slot 2, received network voice header from KA1MXL to TG 31462
M: 2018-09-25 01:17:03.055 DMR Talker Alias (Data Format 1, Received 6/7 char): 'KA1MXL'
M: 2018-09-25 01:17:03.774 DMR Talker Alias (Data Format 1, Received 7/7 char): 'KA1MXL '
M: 2018-09-25 01:17:12.912 DMR Slot 2, received network end of voice transmission, 10.6 seconds, 0% packet loss, BER: 0.0%
M: 2018-09-25 01:17:16.149 DMR Slot 2, received network voice header from WV8CW to TG 31462
M: 2018-09-25 01:17:16.825 DMR Talker Alias (Data Format 1, Received 6/21 char): 'WV8CW '
M: 2018-09-25 01:17:17.546 DMR Talker Alias (Data Format 1, Received 13/21 char): 'WV8CW DMR ID:'
M: 2018-09-25 01:17:18.385 DMR Talker Alias (Data Format 1, Received 20/21 char): 'WV8CW DMR ID: 314602'
M: 2018-09-25 01:17:19.107 DMR Talker Alias (Data Format 1, Received 21/21 char): 'WV8CW DMR ID: 3146023'
M: 2018-09-25 01:17:21.384 DMR Slot 2, received network end of voice transmission, 5.2 seconds, 0% packet loss, BER: 0.0%
M: 2018-09-25 01:17:25.764 DMR Slot 2, received network voice header from KA1MXL to TG 31462
M: 2018-09-25 01:17:26.424 DMR Talker Alias (Data Format 1, Received 6/7 char): 'KA1MXL'
M: 2018-09-25 01:17:27.146 DMR Talker Alias (Data Format 1, Received 7/7 char): 'KA1MXL '
M: 2018-09-25 01:17:31.587 DMR Slot 2, received network end of voice transmission, 5.9 seconds, 0% packet loss, BER: 0.0%
M: 2018-09-25 01:17:33.593 DMR Slot 2, received network voice header from KA1MXL to TG 31462
M: 2018-09-25 01:17:34.243 DMR Talker Alias (Data Format 1, Received 6/7 char): 'KA1MXL'
M: 2018-09-25 01:17:34.975 DMR Talker Alias (Data Format 1, Received 7/7 char): 'KA1MXL '
M: 2018-09-25 01:17:37.975 DMR Slot 2, received network end of voice transmission, 4.4 seconds, 0% packet loss, BER: 0.0%
E: 2018-09-25 01:17:49.522 DMR, Connection to the master has timed out, retrying connection
M: 2018-09-25 01:17:49.522 DMR, Closing DMR Network
M: 2018-09-25 01:17:49.522 DMR, Opening DMR Network
M: 2018-09-25 01:17:59.748 DMR, Logged into the master successfully
toggle quoted messageShow quoted text
-----Original Message-----
From: Mark N2NUO <n2nuo@...>
To: main <main@DVSwitch.groups.io>
Sent: Sun, Sep 23, 2018 9:17 am
Subject: Re: [DVSwitch] dmr
I was looking up your DMRID and I do not see that there was a
DMRID issued to you. If you do have one, supply us with the
info0rmation and the server you are trying to connect to and we
could help you.
Mark
On 09/22/2018 10:28 PM, kd8itc via
Groups.Io wrote:
mmdvm bridge not staying connected was last night now it keeps
opening and closing
|
|
Check RadioID.net; I registered through them. My DMR ID is 3120252.
toggle quoted messageShow quoted text
From: main@DVSwitch.groups.io [mailto:main@DVSwitch.groups.io] On Behalf Of Mark N2NUO Sent: Sunday, September 23, 2018 9:17 AM To: main@DVSwitch.groups.io Subject: Re: [DVSwitch] dmr I was looking up your DMRID and I do not see that there was a DMRID issued to you. If you do have one, supply us with the info0rmation and the server you are trying to connect to and we could help you. Mark On 09/22/2018 10:28 PM, kd8itc via Groups.Io wrote: mmdvm bridge not staying connected was last night now it keeps opening and closing
|
|
Make sure all of your firmware is updated everywhere. I'm not as familiar with the MMDVM setup, but with CBridges and repeaters, outdated firmware will behave as you are describing.
| | Jason Johnston KC5HWB, Ham Radio 2.0 | |
|
toggle quoted messageShow quoted text
On Sun, Sep 23, 2018 at 9:17 AM Mark N2NUO < n2nuo@...> wrote:
I was looking up your DMRID and I do not see that there was a
DMRID issued to you. If you do have one, supply us with the
info0rmation and the server you are trying to connect to and we
could help you.
Mark
On 09/22/2018 10:28 PM, kd8itc via
Groups.Io wrote:
mmdvm bridge not staying connected was last night now it keeps
opening and closing
|
|
I was looking up your DMRID and I do not see that there was a
DMRID issued to you. If you do have one, supply us with the
info0rmation and the server you are trying to connect to and we
could help you.
Mark
toggle quoted messageShow quoted text
On 09/22/2018 10:28 PM, kd8itc via
Groups.Io wrote:
mmdvm bridge not staying connected was last night now it keeps
opening and closing
|
|
Corey Dean N3FE <n3fe@...>
Any errors? Is it a program error or is tuenmaster not letting you connect. We really need something more to go on.
Corey n3fe
toggle quoted messageShow quoted text
On Sun, Sep 23, 2018 at 8:51 AM kd8itc via Groups.Io <kd8itc= aol.com@groups.io> wrote: mmdvm bridge not staying connected was last night now it keeps opening and closing
|
|
mmdvm bridge not staying connected was last night now it keeps opening and closing
|
|
Early Adopters Pre-Sale for the Digital Radio Amateur Workstation - DRAWS
DRAWS - Raspberry Pi HAT [The boards will be run in the next couple of weeks, this is an opportunity to order early and save $20 on the board, and $5 on the GPS LNA Antenna] HW Features: • Raspberry Pi 3 Compliant HAT • Power HAT and Pi from 6-15VDC
• Onboard Voltage Monitor
• 2 Radio Interfaces • On Board GPS • Optional External Antenna w/LNA
• PPS for Stratum 1 Time Source
• Battery Backed Real Time Clock
• Accessory Port • PWR, IO, Serial Port, Analog In
• Headless, operate from your Computer • Workstation, operate locally by adding
Open Source Software: DRAWS™ self identifies to the OS for
configuration.
An image will be available on release with
popular applications pre-installed, including: • Digital Voice Repeater/Hotspot
Order at http://nwdigitalradio.com/product/draws-digital-radio-amateur-workstation/For those who were not in attendance at DCC or the NWAPRS Summer Gathering, NW Digital Radio will be offering a tiered roll out of the DRAWS product. Individual components such as the DRAWS HAT, GPS LNA Antenna, Metal Case, Pre-loaded SD Card, ... will be available for purchase independently.
The initial offering will be only for the HAT and optional antenna. Other offerings will roll out over the 4th quarter. There will also be an offer for a complete, assembled system with all components integrated in a single package. Specific bundles (e.g. everything but the Raspberry Pi) may be offered as well.
John D. Hays Edmonds, WA K7VE
|
|
Re: DMRlink - bridging GPS - private data
Cheers Cort, didn't want to bug you on retired stuff, and wondered if anyone else had brute forced their way through it :)
I'm informed that GPS is delivered as a kinda SMS to a router with a link to APRS.fi, I'm connecting to a DMR+ IPSC2 server in the UK, so I'll ask if they can see anything arriving. Not overly worried if we lose the odd one, its just logging anyway.
73
Sent from Outlook
From: main@DVSwitch.groups.io <main@DVSwitch.groups.io> on behalf of Cort N0MJS via Groups.Io <n0mjs@...>
Sent: 20 September 2018 17:35:23
To: main@DVSwitch.groups.io
Subject: Re: [DVSwitch] DMRlink - bridging GPS - private data
You could just ask the guy who wrote it… ‘cause you know, he’s on this list too.
I would not trust the data routing routines in bridge.py. They were never completed, and may kinda work, but have some serious gaps. At the time I wrote that, I didn’t know enough about IPSC to make sure I could re-write things properly. I used
a very poor approach that, sooner or later, will result in corrupted data in some packets. The question is, now often and how much? I don’t know.
I would recommend not using it.
All,
Before I run off down the rabbit hole, has anyone proven that the bridging of Private_data packets works under DMRlink?
I can see the code is there for the packet type callback in bridge.py, but not in confbridge.py, so I'm using bridge, and I think I've added the rules using the correct header Private_data, with from and
too and I'm getting some stuff in the log, but can't figure if I'm actually routing it or not! Suppose I'll have to run up TCPDump.
Rules;
'PRIVATE_DATA': [
{'NAME': 'GROUPNAME', 'ACTIVE': True, 'TO_TYPE': 'NONE', 'TIMEOUT': 2, 'ON': [], 'OFF': [], 'SRC_TS': 1, 'SRC_GROUP': 5050, 'DST_NET': 'IPSC-GB7EL', 'DST_TS': 1, 'DST_GROUP': 5050 },
{'NAME': 'GROUPNAME', 'ACTIVE': True, 'TO_TYPE': 'NONE', 'TIMEOUT': 2, 'ON': [], 'OFF': [], 'SRC_TS': 1, 'SRC_GROUP': 5055, 'DST_NET': 'IPSC-GB7EL', 'DST_TS': 1, 'DST_GROUP': 5055 },
{'NAME': 'GROUPNAME', 'ACTIVE': True, 'TO_TYPE': 'NONE', 'TIMEOUT': 2, 'ON': [], 'OFF': [], 'SRC_TS': 1, 'SRC_GROUP': 5056, 'DST_NET': 'IPSC-GB7EL', 'DST_TS': 1, 'DST_GROUP': 5056 },
{'NAME': 'GROUPNAME', 'ACTIVE': True, 'TO_TYPE': 'NONE', 'TIMEOUT': 2, 'ON': [], 'OFF': [], 'SRC_TS': 1, 'SRC_GROUP': 5057, 'DST_NET': 'IPSC-GB7EL', 'DST_TS': 1, 'DST_GROUP': 5057 },
log output;
DEBUG 2018-09-20 16:18:57,717 (IPSC-GB7EL) Private Data Packet Received From: 2351266, IPSC Peer 235125, Destination
5057
DEBUG 2018-09-20 16:18:57,776 (IPSC-GB7EL) Private Data Packet Received From: 2351266, IPSC Peer 235125, Destination
5057
Regards
Peter
Cort Buffington
785-865-7206
|
|
Re: DMRlink - bridging GPS - private data
You could just ask the guy who wrote it… ‘cause you know, he’s on this list too.
I would not trust the data routing routines in bridge.py. They were never completed, and may kinda work, but have some serious gaps. At the time I wrote that, I didn’t know enough about IPSC to make sure I could re-write things properly. I used a very poor approach that, sooner or later, will result in corrupted data in some packets. The question is, now often and how much? I don’t know.
I would recommend not using it.
All,
Before I run off down the rabbit hole, has anyone proven that the bridging of Private_data packets works under DMRlink?
I can see the code is there for the packet type callback in bridge.py, but not in confbridge.py, so I'm using bridge, and I think I've added the rules using the correct header Private_data, with from and too and I'm getting some stuff in the log, but can't figure if I'm actually routing it or not! Suppose I'll have to run up TCPDump.
Rules; 'PRIVATE_DATA': [ {'NAME': 'GROUPNAME', 'ACTIVE': True, 'TO_TYPE': 'NONE', 'TIMEOUT': 2, 'ON': [], 'OFF': [], 'SRC_TS': 1, 'SRC_GROUP': 5050, 'DST_NET': 'IPSC-GB7EL', 'DST_TS': 1, 'DST_GROUP': 5050 }, {'NAME': 'GROUPNAME', 'ACTIVE': True, 'TO_TYPE': 'NONE', 'TIMEOUT': 2, 'ON': [], 'OFF': [], 'SRC_TS': 1, 'SRC_GROUP': 5055, 'DST_NET': 'IPSC-GB7EL', 'DST_TS': 1, 'DST_GROUP': 5055 }, {'NAME': 'GROUPNAME', 'ACTIVE': True, 'TO_TYPE': 'NONE', 'TIMEOUT': 2, 'ON': [], 'OFF': [], 'SRC_TS': 1, 'SRC_GROUP': 5056, 'DST_NET': 'IPSC-GB7EL', 'DST_TS': 1, 'DST_GROUP': 5056 }, {'NAME': 'GROUPNAME', 'ACTIVE': True, 'TO_TYPE': 'NONE', 'TIMEOUT': 2, 'ON': [], 'OFF': [], 'SRC_TS': 1, 'SRC_GROUP': 5057, 'DST_NET': 'IPSC-GB7EL', 'DST_TS': 1, 'DST_GROUP': 5057 },
log output; DEBUG 2018-09-20 16:18:57,717 (IPSC-GB7EL) Private Data Packet Received From: 2351266, IPSC Peer 235125, Destination 5057 DEBUG 2018-09-20 16:18:57,776 (IPSC-GB7EL) Private Data Packet Received From: 2351266, IPSC Peer 235125, Destination 5057
Regards Peter
Cort Buffington 785-865-7206
|
|
DMRlink - bridging GPS - private data
All,
Before I run off down the rabbit hole, has anyone proven that the bridging of Private_data packets works under DMRlink?
I can see the code is there for the packet type callback in bridge.py, but not in confbridge.py, so I'm using bridge, and I think I've added the rules using the correct header Private_data, with from and too and I'm getting
some stuff in the log, but can't figure if I'm actually routing it or not! Suppose I'll have to run up TCPDump.
Rules;
'PRIVATE_DATA': [
{'NAME': 'GROUPNAME', 'ACTIVE': True, 'TO_TYPE': 'NONE', 'TIMEOUT': 2, 'ON': [], 'OFF': [], 'SRC_TS': 1, 'SRC_GROUP': 5050, 'DST_NET': 'IPSC-GB7EL', 'DST_TS': 1, 'DST_GROUP': 5050 },
{'NAME': 'GROUPNAME', 'ACTIVE': True, 'TO_TYPE': 'NONE', 'TIMEOUT': 2, 'ON': [], 'OFF': [], 'SRC_TS': 1, 'SRC_GROUP': 5055, 'DST_NET': 'IPSC-GB7EL', 'DST_TS': 1, 'DST_GROUP': 5055 },
{'NAME': 'GROUPNAME', 'ACTIVE': True, 'TO_TYPE': 'NONE', 'TIMEOUT': 2, 'ON': [], 'OFF': [], 'SRC_TS': 1, 'SRC_GROUP': 5056, 'DST_NET': 'IPSC-GB7EL', 'DST_TS': 1, 'DST_GROUP': 5056 },
{'NAME': 'GROUPNAME', 'ACTIVE': True, 'TO_TYPE': 'NONE', 'TIMEOUT': 2, 'ON': [], 'OFF': [], 'SRC_TS': 1, 'SRC_GROUP': 5057, 'DST_NET': 'IPSC-GB7EL', 'DST_TS': 1, 'DST_GROUP': 5057 },
log output;
DEBUG 2018-09-20 16:18:57,717 (IPSC-GB7EL) Private Data Packet Received From: 2351266, IPSC Peer 235125, Destination 5057
DEBUG 2018-09-20 16:18:57,776 (IPSC-GB7EL) Private Data Packet Received From: 2351266, IPSC Peer 235125, Destination 5057
Regards
Peter
|
|
Re: Help trascoding DMR <> P25
|
|
Re: Help trascoding DMR <> P25

Steve N4IRS
That is a correct layout of the software.
You can use md380-emu for DMR decode / encode
OP25 does P25 Decode / encode It is built into Analog_Bridge.
Nothing external needed.
73, Steve N4IRS
toggle quoted messageShow quoted text
On 9/19/2018 3:38 PM, EA5GVK Joaquin
wrote:
Hi,
please need help.
The logic I
think I understand would be using this software in this
order:
P25Reflector
<-> P25Gateway <-> MMDVM_Bridge <->
Analog_Bridge_1 <-> Analog_Bridge_2 <->
MMDVM_Bridge <-> BrandMeister
But what hardware or
software do I need for transcoding?
The md380-emu software is
for P25?
I've heard about the OP25 software, does it work for P25
correct?
Where is the OP25 obtained and what are the instructions
to execute it?
With a ThumbDV or DVStick30 would it serve for the
complete transcoding of DMR <> P25?
|
|
Help trascoding DMR <> P25
Hi, please need help. The logic I think I understand would be using this software in this order: P25Reflector <-> P25Gateway <-> MMDVM_Bridge <-> Analog_Bridge_1 <-> Analog_Bridge_2 <-> MMDVM_Bridge <-> BrandMeister
But what hardware or software do I need for transcoding?
The md380-emu software is for P25?
I've heard about the OP25 software, does it work for P25 correct?
Where is the OP25 obtained and what are the instructions to execute it?
With a ThumbDV or DVStick30 would it serve for the complete transcoding of DMR <> P25?
|
|
Re: Setting up Analog_bridge for P25
Update, I got this working :)
Turns out I had the wrong port numbers in the Analog_bridge ini file for txPort and rxPort under the [AMBE_AUDIO] section, I corrected that and now have bi-directional traffic.
73 Stephen
toggle quoted messageShow quoted text
On Tue, Sep 11, 2018 at 3:58 PM Steve N4IRS < szingman@...> wrote:
Just as a general FYI:
For DMR in order of quality, best to worst:
DV3000
md380-emu
OP25
OP25 does P25 well
OP25 does DMR "OK"
OP25 does D-Star "Just slightly better then not at all" Not really
fair but that's me.
Steve
On 9/11/2018 3:37 PM, Jeff Carrier
wrote:
ok weird, I guess i'm running OP25 and didn't know
it. :O
Here are my configs. You'll have to change calls, IP's and
anything else specific to your installation. Hopefully this
will get you started.
On Tue, Sep 11, 2018 at 1:30 PM Steve N4IRS < szingman@...>
wrote:
Except
the DV3000 does not do P25
Sent
via smoke signal (AT&T)
I can send you my config Stephen.
I'm not running OP25 because IMHO I believe the
DV3000 produces better audio.
Give me a few to get logged in and grab them.
On Tue, Sep 11, 2018 at 1:13 PM Stephen
Brown - K1LNX < k1lnx@...>
wrote:
Thanks Steve, but still no go on
this... and I noticed under the [AMBE_AUDIO] section
that ambeMode = DMR, should this be set to P25
instead, or does it matter? I did set it to P25.
Do I need to be using the emulator for P25/IMBE
mode? I still feel like I might be missing
something, but maybe not.
On Tue, Sep 11, 2018 at 11:29 AM
Steve N4IRS < szingman@...>
wrote:
Stephen,
It looks like I need to update the RPi and the
x86 versions of Analog_Bridge. I will TRY to get
it done this week, but this is my first day back
at work after a week. I doing catch up. In the
mean time, use this as a template for your RPi
AB:
; Analog_Bridge configuration file.
; This file should be placed in either /etc
or it can be
; supplied as a path on the Analog_Bridge
command line.
; General Section describes settings for
Analog_Bridge itself.
; For RPI, don't forget to modprobe
snd_pcm_oss to get the devices populated
[GENERAL]
logLevel = 2 ; Show
messages and above 0=No logging, 1=Debug,
2=Message, 3=Info, 4=Warning, 5=Error, 6=Fatal
; Metadata management
exportMetadata = true ;
Export metadata to USRP partner (transcode
setups require this)
subscriberFile =
/var/lib/dvswitch/subscriber_ids.csv ; DMR
ID to callsign lookup data
; General vocoder setup information
decoderFallBack = true ; Allow
software AMBE decoding if a hardware decoder
is not found
useEmulator = true ; Use
the MD380 AMBE emulator for AMBE72
(DMR/YSFN/NXDN)
emulatorAddress = 127.0.0.1:2470
; IP address and port of the server
; Audio devices are normally not needed when
in gateway service. These devices should
; only be set when local monitor or dongle
modes are required.
outputAudioDevice = /dev/null ;
Audio device /dev/null, /dev/dsp1, portaudio,
etc
inputAudioDevice = /dev/null ; Only
used for dongle mode
; Below values are for using this as a local
DMR dongle (no ASL needed)
useMicrophone = false ; Use
app as just a fancy dongle for DMR
useVox = false ; If
using dongle mode (useMicrophone), enable VOX
voxDecay = 2 ; Hang
time in seconds
voxTrigger = 200 ;
Value to trip PTT (0-32767)
; Information for xx_Bridges (Where xx is
MMDVM, HB, IPSC)
[AMBE_AUDIO]
server = 127.0.0.1 ; IP
address of xx_Bridge.py
fromDMRPort = 31000 ; AMBE
frames from xx_Bridge (should match
"toGatewayPort" in xx_Bridge.cfg)
toDMRPort = 31003 ; AMBE
frames from xx_Bridge (should match
"fromGatewayPort" in xx_Bridge.cfg)
ambeMode = DMR ; DMR,
DMR_IPSC, DSTAR, NXDN, P25, YSFN, YSFW
minTxTimeMS = 2000 ;
Minimum time in MS for hang delay
gatewayDmrId = 3112138 ; ID
to use when transmitting from Analog_Bridge
repeaterID = 311213850 ; ID
of source repeater
txTg = 9 ; TG
to use for all frames received from
Analog_Bridge -> xx_Bridge
txTs = 2 ; Slot
to use for frames received from Analog_Bridge
-> xx_Bridge
colorCode = 1 ;
Color Code to assign DMR frames
; Information for USRP channel driver. This
interface uses PCM to transfer audio
information
; There are two typical configurations, ASL
and Transcode. ASL (AllstarLink) is for
analog clients connected
; to a digital network. Transcode is when
Analog_Bridge actually points its PCM
interfaces back at itself,
; causing a TLV <-- (pcm <--> pcm)
--> TLV type of architecture.
; When using ASL, this matches the rpt.conf
ASL file with a setting like:
; rxchannel = usrp/127.0.0.1:34001:32001
; When Transcoding, make toASLPort equal to
the other instance fromASLPort (crossover)
[USRP]
server = 127.0.0.1 ; IP
address of Allstar/Asterisk
toASLPort = 32001 ;
Analog_Bridge <-- ASL
fromASLPort = 34001 ;
Analog_Bridge --> ASL
aslAudio = AUDIO_UNITY ;
Audio to ASL (AUDIO_UNITY, AUDIO_USE_AGC,
AUDIO_USE_GAIN)
agcGain = -20 ; Gain
(in db) of the AGC filter
dmrAudio = AUDIO_UNITY ;
Audio from ASL (AUDIO_UNITY, AUDIO_USE_GAIN,
AUDIO_BPF)
dmrGain = 0.35 ; Gain
factor of audio from ASL (0.0-1.0)
; Information for DV3000 hardware decoder
; There are two configuration modes: IP
(AMBEServer) and serial (direct connect
hardware)
; Use top server and port if using
AMBEServer
; Use bottom server/port and serial = true
if using the DV3000u (thumbdv)
; Did you run AMBETest4.py before using
this?
[DV3000]
server = 127.0.0.1 ; IP
address of AMBEServer
port = 2460 ; Port
of AMBEServer
; server = /dev/ttyUSB0 ;
Device of DV3000U on this machine
; port = 460800 ; Baud
rate of the dongle
; serial = true ; Use
serial (DV3000U) or IP
On
9/11/2018 11:18 AM, Stephen Brown - K1LNX
wrote:
Thanks Steve, here it is:
; Analog_Bridge configuration file.
; This file should be placed in
either /etc or it can be
; supplied as a path on the
Analog_Bridge command line.
; The best way to think of this file
is that there are two main sections, the
USRP (analog audio) and
; AMBE_AUDIO (compressed audio).
Analog_Bridge will take everything sent
to the USRP port and
; encode it for transmission on the
AMBE_AUDIO port. The encoder will use
the format defined in ambeMode.
; As you might expect, the reverse
direction is defined too.
; General Section describes settings
for Analog_Bridge itself.
[GENERAL]
logLevel = 2
; Show messages and above 0=No
logging, 1=Debug, 2=Message, 3=Info,
4=Warning, 5=Error, 6=Fatal
; Metadata management
subscriberFile =
./subscriber_ids.csv ; DMR ID to
callsign lookup data
exportMetadata = true
; Export metadata to USRP partner
(transcode setups require this)
; General vocoder setup information
decoderFallBack = true
; Allow software AMBE decoding if a
hardware decoder is not found
useEmulator = false
; Use the MD380 AMBE emulator for
AMBE72 (DMR/YSFN/NXDN)
emulatorAddress = 127.0.0.1:2470
; IP address and port of the md380
server
; Information for xx_Bridge (Where xx
is MMDVM, Quantar, HB, IPSC)
[AMBE_AUDIO]
address = 127.0.0.1
; IP address of xx_Bridge
txPort = 31003
; Transmit TLV frames to partner on
this port
rxPort = 31000
; Listen for TLV frames from partner
on this port
ambeMode = P25
; DMR, DMR_IPSC, DSTAR, NXDN, P25,
YSFN, YSFW (encode PCM to this format)
minTxTimeMS = 2000
; Minimum time in MS for hang delay
(0-10000)
; The metadata below is used when ASL
is the source since it does not have any
concept of digital modes
gatewayDmrId = 1234567
; ID to use when transmitting from
Analog_Bridge
repeaterID = 123456789
; ID of source repeater
txTg = 9
; TG to use for all frames sent from
Analog_Bridge -> xx_Bridge
txTs = 2
; Slot to use for frames sent from
Analog_Bridge -> xx_Bridge
colorCode = 1
; Color Code to assign DMR frames
; Information for USRP channel
driver. This interface uses PCM to
transfer audio information
; There are two typical
configurations, ASL and Transcode. ASL
(AllstarLink) is for analog clients
connected
; to a digital network. Transcode is
when Analog_Bridge actually points its
PCM interfaces back at itself,
; causing a TLV <-- (pcm
<--> pcm) --> TLV type of
architecture.
; When using ASL, this matches the
rpt.conf ASL file with a setting like:
; rxchannel =
usrp/127.0.0.1:34001:32001
; When Transcoding, make two ini
files and set txPort equal to the other
instance rxPort (crossover). Launch
; each instance with its own ini
file.
[USRP]
address = 127.0.0.1
; IP address of USRP partner
(Allstar/Asterisk or another
Analog_Bridge)
txPort = 32001
; Transmit USRP frames on this port
rxPort = 34001
; Listen for USRP frames on this port
aslAudio = AUDIO_UNITY
; Audio to ASL (AUDIO_UNITY,
AUDIO_USE_AGC, AUDIO_USE_GAIN)
agcGain = -20
; Gain (in db) of the AGC filter
dmrAudio = AUDIO_UNITY
; Audio from ASL (AUDIO_UNITY,
AUDIO_USE_GAIN, AUDIO_BPF)
dmrGain = 0.35
; Gain factor of audio from ASL
(0.0-1.0)
; Information for DV3000 hardware
decoder
; There are two configuration
modes: IP (AMBEServer) and serial
(direct connect hardware)
; Use top server and port if using
AMBEServer
; Use bottom server/port and serial
= true if using the DV3000u (thumbdv)
; Did you run AMBETest4.py before
using this?
[DV3000]
address = 127.0.0.1
; IP address of AMBEServer
rxPort = 2460
; Port of AMBEServer
; address = /dev/ttyUSB0
; Device of DV3000U on this machine
; baud = 460800
; Baud rate of the dongle (230400 or
460800)
; serial = true
; Use serial=true for direct connect
or serial=false for AMBEServer
On Tue, Sep 11, 2018 at 11:16
AM Steve N4IRS < szingman@...>
wrote:
Stephen,
Please post your Analog_Bridge_P25.ini
On
9/11/2018 11:01 AM, Stephen Brown -
K1LNX wrote:
Hi guys,
So I'm just starting to
play with Analog_bridge and P25.
My (limited) understanding is
that transcoding to/from PCM is
handled via software and the
OP25 libraries.
I think I have everything
setup correctly, however I don't
seem to be getting any traffic
from P25 into Analog_bridge.
There also seems to be some
conflicts in the ini file, I see
this in the debug messages when
I start it up:
root@radioserver:/opt/Analog_Bridge#
./Analog_Bridge
Analog_Bridge_P25.ini
I: 2018-09-10 23:15:23.979
Analog Bridge Version 1.1 Wed
9 May 05:56:17 EDT 2018
I: 2018-09-10 23:15:23.979
Copyright (C) 2018 DVSwitch,
INAD.
I: 2018-09-10 23:15:23.979
Created by Mike N4IRR and
Steve N4IRS
I: 2018-09-10 23:15:23.979
Analog Bridge comes with
ABSOLUTELY NO WARRANTY
I: 2018-09-10 23:15:23.979
I: 2018-09-10 23:15:23.979
This software is for use on
amateur radio networks only,
I: 2018-09-10 23:15:23.979
it is to be used for
educational purposes only. Its
use on
I: 2018-09-10 23:15:23.979
commercial networks is
strictly prohibited.
I: 2018-09-10 23:15:23.979
I: 2018-09-10 23:15:23.979
Analog Bridge is starting
M: 2018-09-10 23:15:23.980
Setting [GENERAL] logLevel
-> 2
M: 2018-09-10 23:15:23.980
Setting [GENERAL]
subscriberFile ->
./subscriber_ids.csv
M: 2018-09-10 23:15:23.980
Setting [GENERAL]
exportMetadata -> true
M: 2018-09-10 23:15:23.980
Setting [GENERAL]
decoderFallBack -> true
M: 2018-09-10 23:15:23.980
Setting [GENERAL] useEmulator
-> false
M: 2018-09-10 23:15:23.980
Setting [GENERAL]
emulatorAddress ->
127.0.0.1:2470
W: 2018-09-10 23:15:23.980
Unknown section/name in .ini
file: AMBE_AUDIO/address
W: 2018-09-10 23:15:23.980
Unknown section/name in .ini
file: AMBE_AUDIO/txPort
W: 2018-09-10 23:15:23.980
Unknown section/name in .ini
file: AMBE_AUDIO/rxPort
M: 2018-09-10 23:15:23.980
Setting [AMBE_AUDIO] ambeMode
-> P25
M: 2018-09-10 23:15:23.980
Setting [AMBE_AUDIO]
minTxTimeMS -> 2000
M: 2018-09-10 23:15:23.980
Setting [AMBE_AUDIO]
gatewayDmrId -> 1234567
M: 2018-09-10 23:15:23.980
Setting [AMBE_AUDIO]
repeaterID -> 123456789
M: 2018-09-10 23:15:23.980
Setting [AMBE_AUDIO] txTg
-> 9
M: 2018-09-10 23:15:23.980
Setting [AMBE_AUDIO] txTs
-> 2
M: 2018-09-10 23:15:23.981
Setting [AMBE_AUDIO] colorCode
-> 1
W: 2018-09-10 23:15:23.981
Unknown section/name in .ini
file: USRP/address
W: 2018-09-10 23:15:23.981
Unknown section/name in .ini
file: USRP/txPort
W: 2018-09-10 23:15:23.981
Unknown section/name in .ini
file: USRP/rxPort
M: 2018-09-10 23:15:23.981
Setting [USRP] aslAudio ->
AUDIO_UNITY
M: 2018-09-10 23:15:23.981
Setting [USRP] agcGain ->
-20
M: 2018-09-10 23:15:23.981
Setting [USRP] dmrAudio ->
AUDIO_UNITY
M: 2018-09-10 23:15:23.981
Setting [USRP] dmrGain ->
0.35
W: 2018-09-10 23:15:23.981
Unknown section/name in .ini
file: DV3000/address
W: 2018-09-10 23:15:23.981
Unknown section/name in .ini
file: DV3000/rxPort
W: 2018-09-10 23:15:23.981
ioctl reset error
W: 2018-09-10 23:15:23.981
ioctl speed error
W: 2018-09-10 23:15:23.981
ioctl stereo error
W: 2018-09-10 23:15:23.981
ioctl setfmt error
M: 2018-09-10 23:15:23.981
Audio In/Out Device: /dev/null
M: 2018-09-10 23:15:23.982
Connecting to DV3000
hardware......
Project 25 IMBE
Encoder/Decoder Fixed-Point
implementation
Version 1.0 (c) Copyright
2009
This program comes with
ABSOLUTELY NO WARRANTY.
This is free software, and
you are welcome to
redistribute it
under certain conditions;
see the file ``LICENSE'' for
details.
I: 2018-09-10 23:15:24.992
Subscriber IDs file not found.
I: 2018-09-10 23:15:24.992
Default extended metadata
<1234567>
W: 2018-09-10 23:15:24.992
Using software MBE decoder
version 1.2.3
W: 2018-09-10 23:15:24.992
Using software OP25 IMBE/AMBE
vocoder
I: 2018-09-10 23:15:24.993
Starting Analog_Bridge -->
USRP thread
I: 2018-09-10 23:15:24.993
Starting USRP -->
IPSC_Bridge thread
MMDVM_bridge/P25Gateway
appear to work fine, I have them
pointed at a test reflector I
built. All are locally hosted on
the same raspberry pi, and there
doesn't appear to be any
firewall issues blocking
anything, I allow everyting in
and out on lo. I built a private
node on the app_rpt side and see
key/unkey events if I connect my
normal node to it so that part
seems to be working at least.
I think I might be missing
something, or something is
potentially misconfig'd, but
can't really put a finger on it.
Does Analog_bridge handle
P25/IMBE transcoding, or do I
need something "external" for
that to take place? I also will
typically use a different ID on
private networks such as this,
and have had that sort of stuff
get me in the past, so also
wanted to make sure there is no
ID checking?
73
Stephen
K1LNX
|
|

Manos Darkadakis
Thank you for the answers both David and John. The repeater is DR1X, not XE FR and the firmware is the latest according to Yaesu U.K. I have no reason to believe otherwise. I tent to believe that it is the case John says, they have taken actions against using it for other modes. All references that I am aware of have been done successfully to older firmware versions. The system works but rx is unstable for no reason, even when there is no signal received the receiver output amplitude is up and down, not much but enough to disturb the ber when it receives a valid dmr signal. I will do a last try to see if I can get a better signal before the accessory port. If not I have a pair of Motorola radios ready to go. Thanks again everyone Manos SV1IW
|
|
Re: Setting up Analog_bridge for P25

Steve N4IRS
Just as a general FYI:
For DMR in order of quality, best to worst:
DV3000
md380-emu
OP25
OP25 does P25 well
OP25 does DMR "OK"
OP25 does D-Star "Just slightly better then not at all" Not really
fair but that's me.
Steve
toggle quoted messageShow quoted text
On 9/11/2018 3:37 PM, Jeff Carrier
wrote:
ok weird, I guess i'm running OP25 and didn't know
it. :O
Here are my configs. You'll have to change calls, IP's and
anything else specific to your installation. Hopefully this
will get you started.
On Tue, Sep 11, 2018 at 1:30 PM Steve N4IRS < szingman@...>
wrote:
Except
the DV3000 does not do P25
Sent
via smoke signal (AT&T)
I can send you my config Stephen.
I'm not running OP25 because IMHO I believe the
DV3000 produces better audio.
Give me a few to get logged in and grab them.
On Tue, Sep 11, 2018 at 1:13 PM Stephen
Brown - K1LNX < k1lnx@...>
wrote:
Thanks Steve, but still no go on
this... and I noticed under the [AMBE_AUDIO] section
that ambeMode = DMR, should this be set to P25
instead, or does it matter? I did set it to P25.
Do I need to be using the emulator for P25/IMBE
mode? I still feel like I might be missing
something, but maybe not.
On Tue, Sep 11, 2018 at 11:29 AM
Steve N4IRS < szingman@...>
wrote:
Stephen,
It looks like I need to update the RPi and the
x86 versions of Analog_Bridge. I will TRY to get
it done this week, but this is my first day back
at work after a week. I doing catch up. In the
mean time, use this as a template for your RPi
AB:
; Analog_Bridge configuration file.
; This file should be placed in either /etc
or it can be
; supplied as a path on the Analog_Bridge
command line.
; General Section describes settings for
Analog_Bridge itself.
; For RPI, don't forget to modprobe
snd_pcm_oss to get the devices populated
[GENERAL]
logLevel = 2 ; Show
messages and above 0=No logging, 1=Debug,
2=Message, 3=Info, 4=Warning, 5=Error, 6=Fatal
; Metadata management
exportMetadata = true ;
Export metadata to USRP partner (transcode
setups require this)
subscriberFile =
/var/lib/dvswitch/subscriber_ids.csv ; DMR
ID to callsign lookup data
; General vocoder setup information
decoderFallBack = true ; Allow
software AMBE decoding if a hardware decoder
is not found
useEmulator = true ; Use
the MD380 AMBE emulator for AMBE72
(DMR/YSFN/NXDN)
emulatorAddress = 127.0.0.1:2470
; IP address and port of the server
; Audio devices are normally not needed when
in gateway service. These devices should
; only be set when local monitor or dongle
modes are required.
outputAudioDevice = /dev/null ;
Audio device /dev/null, /dev/dsp1, portaudio,
etc
inputAudioDevice = /dev/null ; Only
used for dongle mode
; Below values are for using this as a local
DMR dongle (no ASL needed)
useMicrophone = false ; Use
app as just a fancy dongle for DMR
useVox = false ; If
using dongle mode (useMicrophone), enable VOX
voxDecay = 2 ; Hang
time in seconds
voxTrigger = 200 ;
Value to trip PTT (0-32767)
; Information for xx_Bridges (Where xx is
MMDVM, HB, IPSC)
[AMBE_AUDIO]
server = 127.0.0.1 ; IP
address of xx_Bridge.py
fromDMRPort = 31000 ; AMBE
frames from xx_Bridge (should match
"toGatewayPort" in xx_Bridge.cfg)
toDMRPort = 31003 ; AMBE
frames from xx_Bridge (should match
"fromGatewayPort" in xx_Bridge.cfg)
ambeMode = DMR ; DMR,
DMR_IPSC, DSTAR, NXDN, P25, YSFN, YSFW
minTxTimeMS = 2000 ;
Minimum time in MS for hang delay
gatewayDmrId = 3112138 ; ID
to use when transmitting from Analog_Bridge
repeaterID = 311213850 ; ID
of source repeater
txTg = 9 ; TG
to use for all frames received from
Analog_Bridge -> xx_Bridge
txTs = 2 ; Slot
to use for frames received from Analog_Bridge
-> xx_Bridge
colorCode = 1 ;
Color Code to assign DMR frames
; Information for USRP channel driver. This
interface uses PCM to transfer audio
information
; There are two typical configurations, ASL
and Transcode. ASL (AllstarLink) is for
analog clients connected
; to a digital network. Transcode is when
Analog_Bridge actually points its PCM
interfaces back at itself,
; causing a TLV <-- (pcm <--> pcm)
--> TLV type of architecture.
; When using ASL, this matches the rpt.conf
ASL file with a setting like:
; rxchannel = usrp/127.0.0.1:34001:32001
; When Transcoding, make toASLPort equal to
the other instance fromASLPort (crossover)
[USRP]
server = 127.0.0.1 ; IP
address of Allstar/Asterisk
toASLPort = 32001 ;
Analog_Bridge <-- ASL
fromASLPort = 34001 ;
Analog_Bridge --> ASL
aslAudio = AUDIO_UNITY ;
Audio to ASL (AUDIO_UNITY, AUDIO_USE_AGC,
AUDIO_USE_GAIN)
agcGain = -20 ; Gain
(in db) of the AGC filter
dmrAudio = AUDIO_UNITY ;
Audio from ASL (AUDIO_UNITY, AUDIO_USE_GAIN,
AUDIO_BPF)
dmrGain = 0.35 ; Gain
factor of audio from ASL (0.0-1.0)
; Information for DV3000 hardware decoder
; There are two configuration modes: IP
(AMBEServer) and serial (direct connect
hardware)
; Use top server and port if using
AMBEServer
; Use bottom server/port and serial = true
if using the DV3000u (thumbdv)
; Did you run AMBETest4.py before using
this?
[DV3000]
server = 127.0.0.1 ; IP
address of AMBEServer
port = 2460 ; Port
of AMBEServer
; server = /dev/ttyUSB0 ;
Device of DV3000U on this machine
; port = 460800 ; Baud
rate of the dongle
; serial = true ; Use
serial (DV3000U) or IP
On
9/11/2018 11:18 AM, Stephen Brown - K1LNX
wrote:
Thanks Steve, here it is:
; Analog_Bridge configuration file.
; This file should be placed in
either /etc or it can be
; supplied as a path on the
Analog_Bridge command line.
; The best way to think of this file
is that there are two main sections, the
USRP (analog audio) and
; AMBE_AUDIO (compressed audio).
Analog_Bridge will take everything sent
to the USRP port and
; encode it for transmission on the
AMBE_AUDIO port. The encoder will use
the format defined in ambeMode.
; As you might expect, the reverse
direction is defined too.
; General Section describes settings
for Analog_Bridge itself.
[GENERAL]
logLevel = 2
; Show messages and above 0=No
logging, 1=Debug, 2=Message, 3=Info,
4=Warning, 5=Error, 6=Fatal
; Metadata management
subscriberFile =
./subscriber_ids.csv ; DMR ID to
callsign lookup data
exportMetadata = true
; Export metadata to USRP partner
(transcode setups require this)
; General vocoder setup information
decoderFallBack = true
; Allow software AMBE decoding if a
hardware decoder is not found
useEmulator = false
; Use the MD380 AMBE emulator for
AMBE72 (DMR/YSFN/NXDN)
emulatorAddress = 127.0.0.1:2470
; IP address and port of the md380
server
; Information for xx_Bridge (Where xx
is MMDVM, Quantar, HB, IPSC)
[AMBE_AUDIO]
address = 127.0.0.1
; IP address of xx_Bridge
txPort = 31003
; Transmit TLV frames to partner on
this port
rxPort = 31000
; Listen for TLV frames from partner
on this port
ambeMode = P25
; DMR, DMR_IPSC, DSTAR, NXDN, P25,
YSFN, YSFW (encode PCM to this format)
minTxTimeMS = 2000
; Minimum time in MS for hang delay
(0-10000)
; The metadata below is used when ASL
is the source since it does not have any
concept of digital modes
gatewayDmrId = 1234567
; ID to use when transmitting from
Analog_Bridge
repeaterID = 123456789
; ID of source repeater
txTg = 9
; TG to use for all frames sent from
Analog_Bridge -> xx_Bridge
txTs = 2
; Slot to use for frames sent from
Analog_Bridge -> xx_Bridge
colorCode = 1
; Color Code to assign DMR frames
; Information for USRP channel
driver. This interface uses PCM to
transfer audio information
; There are two typical
configurations, ASL and Transcode. ASL
(AllstarLink) is for analog clients
connected
; to a digital network. Transcode is
when Analog_Bridge actually points its
PCM interfaces back at itself,
; causing a TLV <-- (pcm
<--> pcm) --> TLV type of
architecture.
; When using ASL, this matches the
rpt.conf ASL file with a setting like:
; rxchannel =
usrp/127.0.0.1:34001:32001
; When Transcoding, make two ini
files and set txPort equal to the other
instance rxPort (crossover). Launch
; each instance with its own ini
file.
[USRP]
address = 127.0.0.1
; IP address of USRP partner
(Allstar/Asterisk or another
Analog_Bridge)
txPort = 32001
; Transmit USRP frames on this port
rxPort = 34001
; Listen for USRP frames on this port
aslAudio = AUDIO_UNITY
; Audio to ASL (AUDIO_UNITY,
AUDIO_USE_AGC, AUDIO_USE_GAIN)
agcGain = -20
; Gain (in db) of the AGC filter
dmrAudio = AUDIO_UNITY
; Audio from ASL (AUDIO_UNITY,
AUDIO_USE_GAIN, AUDIO_BPF)
dmrGain = 0.35
; Gain factor of audio from ASL
(0.0-1.0)
; Information for DV3000 hardware
decoder
; There are two configuration
modes: IP (AMBEServer) and serial
(direct connect hardware)
; Use top server and port if using
AMBEServer
; Use bottom server/port and serial
= true if using the DV3000u (thumbdv)
; Did you run AMBETest4.py before
using this?
[DV3000]
address = 127.0.0.1
; IP address of AMBEServer
rxPort = 2460
; Port of AMBEServer
; address = /dev/ttyUSB0
; Device of DV3000U on this machine
; baud = 460800
; Baud rate of the dongle (230400 or
460800)
; serial = true
; Use serial=true for direct connect
or serial=false for AMBEServer
On Tue, Sep 11, 2018 at 11:16
AM Steve N4IRS < szingman@...>
wrote:
Stephen,
Please post your Analog_Bridge_P25.ini
On
9/11/2018 11:01 AM, Stephen Brown -
K1LNX wrote:
Hi guys,
So I'm just starting to
play with Analog_bridge and P25.
My (limited) understanding is
that transcoding to/from PCM is
handled via software and the
OP25 libraries.
I think I have everything
setup correctly, however I don't
seem to be getting any traffic
from P25 into Analog_bridge.
There also seems to be some
conflicts in the ini file, I see
this in the debug messages when
I start it up:
root@radioserver:/opt/Analog_Bridge#
./Analog_Bridge
Analog_Bridge_P25.ini
I: 2018-09-10 23:15:23.979
Analog Bridge Version 1.1 Wed
9 May 05:56:17 EDT 2018
I: 2018-09-10 23:15:23.979
Copyright (C) 2018 DVSwitch,
INAD.
I: 2018-09-10 23:15:23.979
Created by Mike N4IRR and
Steve N4IRS
I: 2018-09-10 23:15:23.979
Analog Bridge comes with
ABSOLUTELY NO WARRANTY
I: 2018-09-10 23:15:23.979
I: 2018-09-10 23:15:23.979
This software is for use on
amateur radio networks only,
I: 2018-09-10 23:15:23.979
it is to be used for
educational purposes only. Its
use on
I: 2018-09-10 23:15:23.979
commercial networks is
strictly prohibited.
I: 2018-09-10 23:15:23.979
I: 2018-09-10 23:15:23.979
Analog Bridge is starting
M: 2018-09-10 23:15:23.980
Setting [GENERAL] logLevel
-> 2
M: 2018-09-10 23:15:23.980
Setting [GENERAL]
subscriberFile ->
./subscriber_ids.csv
M: 2018-09-10 23:15:23.980
Setting [GENERAL]
exportMetadata -> true
M: 2018-09-10 23:15:23.980
Setting [GENERAL]
decoderFallBack -> true
M: 2018-09-10 23:15:23.980
Setting [GENERAL] useEmulator
-> false
M: 2018-09-10 23:15:23.980
Setting [GENERAL]
emulatorAddress ->
127.0.0.1:2470
W: 2018-09-10 23:15:23.980
Unknown section/name in .ini
file: AMBE_AUDIO/address
W: 2018-09-10 23:15:23.980
Unknown section/name in .ini
file: AMBE_AUDIO/txPort
W: 2018-09-10 23:15:23.980
Unknown section/name in .ini
file: AMBE_AUDIO/rxPort
M: 2018-09-10 23:15:23.980
Setting [AMBE_AUDIO] ambeMode
-> P25
M: 2018-09-10 23:15:23.980
Setting [AMBE_AUDIO]
minTxTimeMS -> 2000
M: 2018-09-10 23:15:23.980
Setting [AMBE_AUDIO]
gatewayDmrId -> 1234567
M: 2018-09-10 23:15:23.980
Setting [AMBE_AUDIO]
repeaterID -> 123456789
M: 2018-09-10 23:15:23.980
Setting [AMBE_AUDIO] txTg
-> 9
M: 2018-09-10 23:15:23.980
Setting [AMBE_AUDIO] txTs
-> 2
M: 2018-09-10 23:15:23.981
Setting [AMBE_AUDIO] colorCode
-> 1
W: 2018-09-10 23:15:23.981
Unknown section/name in .ini
file: USRP/address
W: 2018-09-10 23:15:23.981
Unknown section/name in .ini
file: USRP/txPort
W: 2018-09-10 23:15:23.981
Unknown section/name in .ini
file: USRP/rxPort
M: 2018-09-10 23:15:23.981
Setting [USRP] aslAudio ->
AUDIO_UNITY
M: 2018-09-10 23:15:23.981
Setting [USRP] agcGain ->
-20
M: 2018-09-10 23:15:23.981
Setting [USRP] dmrAudio ->
AUDIO_UNITY
M: 2018-09-10 23:15:23.981
Setting [USRP] dmrGain ->
0.35
W: 2018-09-10 23:15:23.981
Unknown section/name in .ini
file: DV3000/address
W: 2018-09-10 23:15:23.981
Unknown section/name in .ini
file: DV3000/rxPort
W: 2018-09-10 23:15:23.981
ioctl reset error
W: 2018-09-10 23:15:23.981
ioctl speed error
W: 2018-09-10 23:15:23.981
ioctl stereo error
W: 2018-09-10 23:15:23.981
ioctl setfmt error
M: 2018-09-10 23:15:23.981
Audio In/Out Device: /dev/null
M: 2018-09-10 23:15:23.982
Connecting to DV3000
hardware......
Project 25 IMBE
Encoder/Decoder Fixed-Point
implementation
Version 1.0 (c) Copyright
2009
This program comes with
ABSOLUTELY NO WARRANTY.
This is free software, and
you are welcome to
redistribute it
under certain conditions;
see the file ``LICENSE'' for
details.
I: 2018-09-10 23:15:24.992
Subscriber IDs file not found.
I: 2018-09-10 23:15:24.992
Default extended metadata
<1234567>
W: 2018-09-10 23:15:24.992
Using software MBE decoder
version 1.2.3
W: 2018-09-10 23:15:24.992
Using software OP25 IMBE/AMBE
vocoder
I: 2018-09-10 23:15:24.993
Starting Analog_Bridge -->
USRP thread
I: 2018-09-10 23:15:24.993
Starting USRP -->
IPSC_Bridge thread
MMDVM_bridge/P25Gateway
appear to work fine, I have them
pointed at a test reflector I
built. All are locally hosted on
the same raspberry pi, and there
doesn't appear to be any
firewall issues blocking
anything, I allow everyting in
and out on lo. I built a private
node on the app_rpt side and see
key/unkey events if I connect my
normal node to it so that part
seems to be working at least.
I think I might be missing
something, or something is
potentially misconfig'd, but
can't really put a finger on it.
Does Analog_bridge handle
P25/IMBE transcoding, or do I
need something "external" for
that to take place? I also will
typically use a different ID on
private networks such as this,
and have had that sort of stuff
get me in the past, so also
wanted to make sure there is no
ID checking?
73
Stephen
K1LNX
|
|
Re: Setting up Analog_bridge for P25
Thanks Jeff! Ill take a look at these and advise...
toggle quoted messageShow quoted text
ok weird, I guess i'm running OP25 and didn't know it. :O
Here are my configs. You'll have to change calls, IP's and anything else specific to your installation. Hopefully this will get you started.
On Tue, Sep 11, 2018 at 1:30 PM Steve N4IRS < szingman@...> wrote:
Except the DV3000 does not do P25
Sent via smoke signal (AT&T)
I can send you my config Stephen.
I'm not running OP25 because IMHO I believe the DV3000 produces better audio.
Give me a few to get logged in and grab them.
On Tue, Sep 11, 2018 at 1:13 PM Stephen Brown - K1LNX < k1lnx@...> wrote:
Thanks Steve, but still no go on this... and I noticed under the [AMBE_AUDIO] section that ambeMode = DMR, should this be set to P25 instead, or does it matter? I did set it to P25.
Do I need to be using the emulator for P25/IMBE mode? I still feel like I might be missing something, but maybe not.
On Tue, Sep 11, 2018 at 11:29 AM Steve N4IRS < szingman@...> wrote:
Stephen,
It looks like I need to update the RPi and the x86 versions of Analog_Bridge. I will TRY to get it done this week, but this is my first day back at work after a week. I doing catch up. In the mean time, use this as a template for your RPi AB:
; Analog_Bridge configuration file.
; This file should be placed in either /etc or it can be
; supplied as a path on the Analog_Bridge command line.
; General Section describes settings for Analog_Bridge itself.
; For RPI, don't forget to modprobe snd_pcm_oss to get the devices populated
[GENERAL]
logLevel = 2 ; Show messages and above 0=No logging, 1=Debug, 2=Message, 3=Info, 4=Warning, 5=Error, 6=Fatal
; Metadata management
exportMetadata = true ; Export metadata to USRP partner (transcode setups require this)
subscriberFile = /var/lib/dvswitch/subscriber_ids.csv ; DMR ID to callsign lookup data
; General vocoder setup information
decoderFallBack = true ; Allow software AMBE decoding if a hardware decoder is not found
useEmulator = true ; Use the MD380 AMBE emulator for AMBE72 (DMR/YSFN/NXDN)
emulatorAddress = 127.0.0.1:2470 ; IP address and port of the server
; Audio devices are normally not needed when in gateway service. These devices should
; only be set when local monitor or dongle modes are required.
outputAudioDevice = /dev/null ; Audio device /dev/null, /dev/dsp1, portaudio, etc
inputAudioDevice = /dev/null ; Only used for dongle mode
; Below values are for using this as a local DMR dongle (no ASL needed)
useMicrophone = false ; Use app as just a fancy dongle for DMR
useVox = false ; If using dongle mode (useMicrophone), enable VOX
voxDecay = 2 ; Hang time in seconds
voxTrigger = 200 ; Value to trip PTT (0-32767)
; Information for xx_Bridges (Where xx is MMDVM, HB, IPSC)
[AMBE_AUDIO]
server = 127.0.0.1 ; IP address of xx_Bridge.py
fromDMRPort = 31000 ; AMBE frames from xx_Bridge (should match "toGatewayPort" in xx_Bridge.cfg)
toDMRPort = 31003 ; AMBE frames from xx_Bridge (should match "fromGatewayPort" in xx_Bridge.cfg)
ambeMode = DMR ; DMR, DMR_IPSC, DSTAR, NXDN, P25, YSFN, YSFW
minTxTimeMS = 2000 ; Minimum time in MS for hang delay
gatewayDmrId = 3112138 ; ID to use when transmitting from Analog_Bridge
repeaterID = 311213850 ; ID of source repeater
txTg = 9 ; TG to use for all frames received from Analog_Bridge -> xx_Bridge
txTs = 2 ; Slot to use for frames received from Analog_Bridge -> xx_Bridge
colorCode = 1 ; Color Code to assign DMR frames
; Information for USRP channel driver. This interface uses PCM to transfer audio information
; There are two typical configurations, ASL and Transcode. ASL (AllstarLink) is for analog clients connected
; to a digital network. Transcode is when Analog_Bridge actually points its PCM interfaces back at itself,
; causing a TLV <-- (pcm <--> pcm) --> TLV type of architecture.
; When using ASL, this matches the rpt.conf ASL file with a setting like:
; rxchannel = usrp/127.0.0.1:34001:32001
; When Transcoding, make toASLPort equal to the other instance fromASLPort (crossover)
[USRP]
server = 127.0.0.1 ; IP address of Allstar/Asterisk
toASLPort = 32001 ; Analog_Bridge <-- ASL
fromASLPort = 34001 ; Analog_Bridge --> ASL
aslAudio = AUDIO_UNITY ; Audio to ASL (AUDIO_UNITY, AUDIO_USE_AGC, AUDIO_USE_GAIN)
agcGain = -20 ; Gain (in db) of the AGC filter
dmrAudio = AUDIO_UNITY ; Audio from ASL (AUDIO_UNITY, AUDIO_USE_GAIN, AUDIO_BPF)
dmrGain = 0.35 ; Gain factor of audio from ASL (0.0-1.0)
; Information for DV3000 hardware decoder
; There are two configuration modes: IP (AMBEServer) and serial (direct connect hardware)
; Use top server and port if using AMBEServer
; Use bottom server/port and serial = true if using the DV3000u (thumbdv)
; Did you run AMBETest4.py before using this?
[DV3000]
server = 127.0.0.1 ; IP address of AMBEServer
port = 2460 ; Port of AMBEServer
; server = /dev/ttyUSB0 ; Device of DV3000U on this machine
; port = 460800 ; Baud rate of the dongle
; serial = true ; Use serial (DV3000U) or IP
On 9/11/2018 11:18 AM, Stephen Brown - K1LNX wrote:
Thanks Steve, here it is:
; Analog_Bridge configuration file.
; This file should be placed in either /etc or it can be
; supplied as a path on the Analog_Bridge command line.
; The best way to think of this file is that there are two main sections, the USRP (analog audio) and
; AMBE_AUDIO (compressed audio). Analog_Bridge will take everything sent to the USRP port and
; encode it for transmission on the AMBE_AUDIO port. The encoder will use the format defined in ambeMode.
; As you might expect, the reverse direction is defined too.
; General Section describes settings for Analog_Bridge itself.
[GENERAL]
logLevel = 2 ; Show messages and above 0=No logging, 1=Debug, 2=Message, 3=Info, 4=Warning, 5=Error, 6=Fatal
; Metadata management
subscriberFile = ./subscriber_ids.csv ; DMR ID to callsign lookup data
exportMetadata = true ; Export metadata to USRP partner (transcode setups require this)
; General vocoder setup information
decoderFallBack = true ; Allow software AMBE decoding if a hardware decoder is not found
useEmulator = false ; Use the MD380 AMBE emulator for AMBE72 (DMR/YSFN/NXDN)
emulatorAddress = 127.0.0.1:2470 ; IP address and port of the md380 server
; Information for xx_Bridge (Where xx is MMDVM, Quantar, HB, IPSC)
[AMBE_AUDIO]
address = 127.0.0.1 ; IP address of xx_Bridge
txPort = 31003 ; Transmit TLV frames to partner on this port
rxPort = 31000 ; Listen for TLV frames from partner on this port
ambeMode = P25 ; DMR, DMR_IPSC, DSTAR, NXDN, P25, YSFN, YSFW (encode PCM to this format)
minTxTimeMS = 2000 ; Minimum time in MS for hang delay (0-10000)
; The metadata below is used when ASL is the source since it does not have any concept of digital modes
gatewayDmrId = 1234567 ; ID to use when transmitting from Analog_Bridge
repeaterID = 123456789 ; ID of source repeater
txTg = 9 ; TG to use for all frames sent from Analog_Bridge -> xx_Bridge
txTs = 2 ; Slot to use for frames sent from Analog_Bridge -> xx_Bridge
colorCode = 1 ; Color Code to assign DMR frames
; Information for USRP channel driver. This interface uses PCM to transfer audio information
; There are two typical configurations, ASL and Transcode. ASL (AllstarLink) is for analog clients connected
; to a digital network. Transcode is when Analog_Bridge actually points its PCM interfaces back at itself,
; causing a TLV <-- (pcm <--> pcm) --> TLV type of architecture.
; When using ASL, this matches the rpt.conf ASL file with a setting like:
; rxchannel = usrp/127.0.0.1:34001:32001
; When Transcoding, make two ini files and set txPort equal to the other instance rxPort (crossover). Launch
; each instance with its own ini file.
[USRP]
address = 127.0.0.1 ; IP address of USRP partner (Allstar/Asterisk or another Analog_Bridge)
txPort = 32001 ; Transmit USRP frames on this port
rxPort = 34001 ; Listen for USRP frames on this port
aslAudio = AUDIO_UNITY ; Audio to ASL (AUDIO_UNITY, AUDIO_USE_AGC, AUDIO_USE_GAIN)
agcGain = -20 ; Gain (in db) of the AGC filter
dmrAudio = AUDIO_UNITY ; Audio from ASL (AUDIO_UNITY, AUDIO_USE_GAIN, AUDIO_BPF)
dmrGain = 0.35 ; Gain factor of audio from ASL (0.0-1.0)
; Information for DV3000 hardware decoder
; There are two configuration modes: IP (AMBEServer) and serial (direct connect hardware)
; Use top server and port if using AMBEServer
; Use bottom server/port and serial = true if using the DV3000u (thumbdv)
; Did you run AMBETest4.py before using this?
[DV3000]
address = 127.0.0.1 ; IP address of AMBEServer
rxPort = 2460 ; Port of AMBEServer
; address = /dev/ttyUSB0 ; Device of DV3000U on this machine
; baud = 460800 ; Baud rate of the dongle (230400 or 460800)
; serial = true ; Use serial=true for direct connect or serial=false for AMBEServer
On Tue, Sep 11, 2018 at 11:16 AM Steve N4IRS < szingman@...> wrote:
Stephen,
Please post your Analog_Bridge_P25.ini
On 9/11/2018 11:01 AM, Stephen Brown - K1LNX wrote:
Hi guys,
So I'm just starting to play with Analog_bridge and P25. My (limited) understanding is that transcoding to/from PCM is handled via software and the OP25 libraries.
I think I have everything setup correctly, however I don't seem to be getting any traffic from P25 into Analog_bridge. There also seems to be some conflicts in the ini file, I see this in the debug messages when I start it up:
root@radioserver:/opt/Analog_Bridge# ./Analog_Bridge Analog_Bridge_P25.ini
I: 2018-09-10 23:15:23.979 Analog Bridge Version 1.1 Wed 9 May 05:56:17 EDT 2018
I: 2018-09-10 23:15:23.979 Copyright (C) 2018 DVSwitch, INAD.
I: 2018-09-10 23:15:23.979 Created by Mike N4IRR and Steve N4IRS
I: 2018-09-10 23:15:23.979 Analog Bridge comes with ABSOLUTELY NO WARRANTY
I: 2018-09-10 23:15:23.979
I: 2018-09-10 23:15:23.979 This software is for use on amateur radio networks only,
I: 2018-09-10 23:15:23.979 it is to be used for educational purposes only. Its use on
I: 2018-09-10 23:15:23.979 commercial networks is strictly prohibited.
I: 2018-09-10 23:15:23.979
I: 2018-09-10 23:15:23.979 Analog Bridge is starting
M: 2018-09-10 23:15:23.980 Setting [GENERAL] logLevel -> 2
M: 2018-09-10 23:15:23.980 Setting [GENERAL] subscriberFile -> ./subscriber_ids.csv
M: 2018-09-10 23:15:23.980 Setting [GENERAL] exportMetadata -> true
M: 2018-09-10 23:15:23.980 Setting [GENERAL] decoderFallBack -> true
M: 2018-09-10 23:15:23.980 Setting [GENERAL] useEmulator -> false
M: 2018-09-10 23:15:23.980 Setting [GENERAL] emulatorAddress ->
127.0.0.1:2470
W: 2018-09-10 23:15:23.980 Unknown section/name in .ini file: AMBE_AUDIO/address
W: 2018-09-10 23:15:23.980 Unknown section/name in .ini file: AMBE_AUDIO/txPort
W: 2018-09-10 23:15:23.980 Unknown section/name in .ini file: AMBE_AUDIO/rxPort
M: 2018-09-10 23:15:23.980 Setting [AMBE_AUDIO] ambeMode -> P25
M: 2018-09-10 23:15:23.980 Setting [AMBE_AUDIO] minTxTimeMS -> 2000
M: 2018-09-10 23:15:23.980 Setting [AMBE_AUDIO] gatewayDmrId -> 1234567
M: 2018-09-10 23:15:23.980 Setting [AMBE_AUDIO] repeaterID -> 123456789
M: 2018-09-10 23:15:23.980 Setting [AMBE_AUDIO] txTg -> 9
M: 2018-09-10 23:15:23.980 Setting [AMBE_AUDIO] txTs -> 2
M: 2018-09-10 23:15:23.981 Setting [AMBE_AUDIO] colorCode -> 1
W: 2018-09-10 23:15:23.981 Unknown section/name in .ini file: USRP/address
W: 2018-09-10 23:15:23.981 Unknown section/name in .ini file: USRP/txPort
W: 2018-09-10 23:15:23.981 Unknown section/name in .ini file: USRP/rxPort
M: 2018-09-10 23:15:23.981 Setting [USRP] aslAudio -> AUDIO_UNITY
M: 2018-09-10 23:15:23.981 Setting [USRP] agcGain -> -20
M: 2018-09-10 23:15:23.981 Setting [USRP] dmrAudio -> AUDIO_UNITY
M: 2018-09-10 23:15:23.981 Setting [USRP] dmrGain -> 0.35
W: 2018-09-10 23:15:23.981 Unknown section/name in .ini file: DV3000/address
W: 2018-09-10 23:15:23.981 Unknown section/name in .ini file: DV3000/rxPort
W: 2018-09-10 23:15:23.981 ioctl reset error
W: 2018-09-10 23:15:23.981 ioctl speed error
W: 2018-09-10 23:15:23.981 ioctl stereo error
W: 2018-09-10 23:15:23.981 ioctl setfmt error
M: 2018-09-10 23:15:23.981 Audio In/Out Device: /dev/null
M: 2018-09-10 23:15:23.982 Connecting to DV3000 hardware......
Project 25 IMBE Encoder/Decoder Fixed-Point implementation
Version 1.0 (c) Copyright 2009
This program comes with ABSOLUTELY NO WARRANTY.
This is free software, and you are welcome to redistribute it
under certain conditions; see the file ``LICENSE'' for details.
I: 2018-09-10 23:15:24.992 Subscriber IDs file not found.
I: 2018-09-10 23:15:24.992 Default extended metadata <1234567>
W: 2018-09-10 23:15:24.992 Using software MBE decoder version 1.2.3
W: 2018-09-10 23:15:24.992 Using software OP25 IMBE/AMBE vocoder
I: 2018-09-10 23:15:24.993 Starting Analog_Bridge --> USRP thread
I: 2018-09-10 23:15:24.993 Starting USRP --> IPSC_Bridge thread
MMDVM_bridge/P25Gateway appear to work fine, I have them pointed at a test reflector I built. All are locally hosted on the same raspberry pi, and there doesn't appear to be any firewall issues blocking anything, I allow everyting in and out on lo. I built
a private node on the app_rpt side and see key/unkey events if I connect my normal node to it so that part seems to be working at least.
I think I might be missing something, or something is potentially misconfig'd, but can't really put a finger on it. Does Analog_bridge handle P25/IMBE transcoding, or do I need something "external" for that to take place? I also will typically use a different
ID on private networks such as this, and have had that sort of stuff get me in the past, so also wanted to make sure there is no ID checking?
73
Stephen
K1LNX
|
|
Re: Setting up Analog_bridge for P25
ok weird, I guess i'm running OP25 and didn't know it. :O
Here are my configs. You'll have to change calls, IP's and anything else specific to your installation. Hopefully this will get you started.
toggle quoted messageShow quoted text
On Tue, Sep 11, 2018 at 1:30 PM Steve N4IRS < szingman@...> wrote:
Except the DV3000 does not do P25
Sent via smoke signal (AT&T)
I can send you my config Stephen.
I'm not running OP25 because IMHO I believe the DV3000 produces better audio.
Give me a few to get logged in and grab them.
On Tue, Sep 11, 2018 at 1:13 PM Stephen Brown - K1LNX < k1lnx@...> wrote:
Thanks Steve, but still no go on this... and I noticed under the [AMBE_AUDIO] section that ambeMode = DMR, should this be set to P25 instead, or does it matter? I did set it to P25.
Do I need to be using the emulator for P25/IMBE mode? I still feel like I might be missing something, but maybe not.
On Tue, Sep 11, 2018 at 11:29 AM Steve N4IRS < szingman@...> wrote:
Stephen,
It looks like I need to update the RPi and the x86 versions of Analog_Bridge. I will TRY to get it done this week, but this is my first day back at work after a week. I doing catch up. In the mean time, use this as a template for your RPi AB:
; Analog_Bridge configuration file.
; This file should be placed in either /etc or it can be
; supplied as a path on the Analog_Bridge command line.
; General Section describes settings for Analog_Bridge itself.
; For RPI, don't forget to modprobe snd_pcm_oss to get the devices populated
[GENERAL]
logLevel = 2 ; Show messages and above 0=No logging, 1=Debug, 2=Message, 3=Info, 4=Warning, 5=Error, 6=Fatal
; Metadata management
exportMetadata = true ; Export metadata to USRP partner (transcode setups require this)
subscriberFile = /var/lib/dvswitch/subscriber_ids.csv ; DMR ID to callsign lookup data
; General vocoder setup information
decoderFallBack = true ; Allow software AMBE decoding if a hardware decoder is not found
useEmulator = true ; Use the MD380 AMBE emulator for AMBE72 (DMR/YSFN/NXDN)
emulatorAddress = 127.0.0.1:2470 ; IP address and port of the server
; Audio devices are normally not needed when in gateway service. These devices should
; only be set when local monitor or dongle modes are required.
outputAudioDevice = /dev/null ; Audio device /dev/null, /dev/dsp1, portaudio, etc
inputAudioDevice = /dev/null ; Only used for dongle mode
; Below values are for using this as a local DMR dongle (no ASL needed)
useMicrophone = false ; Use app as just a fancy dongle for DMR
useVox = false ; If using dongle mode (useMicrophone), enable VOX
voxDecay = 2 ; Hang time in seconds
voxTrigger = 200 ; Value to trip PTT (0-32767)
; Information for xx_Bridges (Where xx is MMDVM, HB, IPSC)
[AMBE_AUDIO]
server = 127.0.0.1 ; IP address of xx_Bridge.py
fromDMRPort = 31000 ; AMBE frames from xx_Bridge (should match "toGatewayPort" in xx_Bridge.cfg)
toDMRPort = 31003 ; AMBE frames from xx_Bridge (should match "fromGatewayPort" in xx_Bridge.cfg)
ambeMode = DMR ; DMR, DMR_IPSC, DSTAR, NXDN, P25, YSFN, YSFW
minTxTimeMS = 2000 ; Minimum time in MS for hang delay
gatewayDmrId = 3112138 ; ID to use when transmitting from Analog_Bridge
repeaterID = 311213850 ; ID of source repeater
txTg = 9 ; TG to use for all frames received from Analog_Bridge -> xx_Bridge
txTs = 2 ; Slot to use for frames received from Analog_Bridge -> xx_Bridge
colorCode = 1 ; Color Code to assign DMR frames
; Information for USRP channel driver. This interface uses PCM to transfer audio information
; There are two typical configurations, ASL and Transcode. ASL (AllstarLink) is for analog clients connected
; to a digital network. Transcode is when Analog_Bridge actually points its PCM interfaces back at itself,
; causing a TLV <-- (pcm <--> pcm) --> TLV type of architecture.
; When using ASL, this matches the rpt.conf ASL file with a setting like:
; rxchannel = usrp/127.0.0.1:34001:32001
; When Transcoding, make toASLPort equal to the other instance fromASLPort (crossover)
[USRP]
server = 127.0.0.1 ; IP address of Allstar/Asterisk
toASLPort = 32001 ; Analog_Bridge <-- ASL
fromASLPort = 34001 ; Analog_Bridge --> ASL
aslAudio = AUDIO_UNITY ; Audio to ASL (AUDIO_UNITY, AUDIO_USE_AGC, AUDIO_USE_GAIN)
agcGain = -20 ; Gain (in db) of the AGC filter
dmrAudio = AUDIO_UNITY ; Audio from ASL (AUDIO_UNITY, AUDIO_USE_GAIN, AUDIO_BPF)
dmrGain = 0.35 ; Gain factor of audio from ASL (0.0-1.0)
; Information for DV3000 hardware decoder
; There are two configuration modes: IP (AMBEServer) and serial (direct connect hardware)
; Use top server and port if using AMBEServer
; Use bottom server/port and serial = true if using the DV3000u (thumbdv)
; Did you run AMBETest4.py before using this?
[DV3000]
server = 127.0.0.1 ; IP address of AMBEServer
port = 2460 ; Port of AMBEServer
; server = /dev/ttyUSB0 ; Device of DV3000U on this machine
; port = 460800 ; Baud rate of the dongle
; serial = true ; Use serial (DV3000U) or IP
On 9/11/2018 11:18 AM, Stephen Brown - K1LNX wrote:
Thanks Steve, here it is:
; Analog_Bridge configuration file.
; This file should be placed in either /etc or it can be
; supplied as a path on the Analog_Bridge command line.
; The best way to think of this file is that there are two main sections, the USRP (analog audio) and
; AMBE_AUDIO (compressed audio). Analog_Bridge will take everything sent to the USRP port and
; encode it for transmission on the AMBE_AUDIO port. The encoder will use the format defined in ambeMode.
; As you might expect, the reverse direction is defined too.
; General Section describes settings for Analog_Bridge itself.
[GENERAL]
logLevel = 2 ; Show messages and above 0=No logging, 1=Debug, 2=Message, 3=Info, 4=Warning, 5=Error, 6=Fatal
; Metadata management
subscriberFile = ./subscriber_ids.csv ; DMR ID to callsign lookup data
exportMetadata = true ; Export metadata to USRP partner (transcode setups require this)
; General vocoder setup information
decoderFallBack = true ; Allow software AMBE decoding if a hardware decoder is not found
useEmulator = false ; Use the MD380 AMBE emulator for AMBE72 (DMR/YSFN/NXDN)
emulatorAddress = 127.0.0.1:2470 ; IP address and port of the md380 server
; Information for xx_Bridge (Where xx is MMDVM, Quantar, HB, IPSC)
[AMBE_AUDIO]
address = 127.0.0.1 ; IP address of xx_Bridge
txPort = 31003 ; Transmit TLV frames to partner on this port
rxPort = 31000 ; Listen for TLV frames from partner on this port
ambeMode = P25 ; DMR, DMR_IPSC, DSTAR, NXDN, P25, YSFN, YSFW (encode PCM to this format)
minTxTimeMS = 2000 ; Minimum time in MS for hang delay (0-10000)
; The metadata below is used when ASL is the source since it does not have any concept of digital modes
gatewayDmrId = 1234567 ; ID to use when transmitting from Analog_Bridge
repeaterID = 123456789 ; ID of source repeater
txTg = 9 ; TG to use for all frames sent from Analog_Bridge -> xx_Bridge
txTs = 2 ; Slot to use for frames sent from Analog_Bridge -> xx_Bridge
colorCode = 1 ; Color Code to assign DMR frames
; Information for USRP channel driver. This interface uses PCM to transfer audio information
; There are two typical configurations, ASL and Transcode. ASL (AllstarLink) is for analog clients connected
; to a digital network. Transcode is when Analog_Bridge actually points its PCM interfaces back at itself,
; causing a TLV <-- (pcm <--> pcm) --> TLV type of architecture.
; When using ASL, this matches the rpt.conf ASL file with a setting like:
; rxchannel = usrp/127.0.0.1:34001:32001
; When Transcoding, make two ini files and set txPort equal to the other instance rxPort (crossover). Launch
; each instance with its own ini file.
[USRP]
address = 127.0.0.1 ; IP address of USRP partner (Allstar/Asterisk or another Analog_Bridge)
txPort = 32001 ; Transmit USRP frames on this port
rxPort = 34001 ; Listen for USRP frames on this port
aslAudio = AUDIO_UNITY ; Audio to ASL (AUDIO_UNITY, AUDIO_USE_AGC, AUDIO_USE_GAIN)
agcGain = -20 ; Gain (in db) of the AGC filter
dmrAudio = AUDIO_UNITY ; Audio from ASL (AUDIO_UNITY, AUDIO_USE_GAIN, AUDIO_BPF)
dmrGain = 0.35 ; Gain factor of audio from ASL (0.0-1.0)
; Information for DV3000 hardware decoder
; There are two configuration modes: IP (AMBEServer) and serial (direct connect hardware)
; Use top server and port if using AMBEServer
; Use bottom server/port and serial = true if using the DV3000u (thumbdv)
; Did you run AMBETest4.py before using this?
[DV3000]
address = 127.0.0.1 ; IP address of AMBEServer
rxPort = 2460 ; Port of AMBEServer
; address = /dev/ttyUSB0 ; Device of DV3000U on this machine
; baud = 460800 ; Baud rate of the dongle (230400 or 460800)
; serial = true ; Use serial=true for direct connect or serial=false for AMBEServer
On Tue, Sep 11, 2018 at 11:16 AM Steve N4IRS < szingman@...> wrote:
Stephen,
Please post your Analog_Bridge_P25.ini
On 9/11/2018 11:01 AM, Stephen Brown - K1LNX wrote:
Hi guys,
So I'm just starting to play with Analog_bridge and P25. My (limited) understanding is that transcoding to/from PCM is handled via software and the OP25 libraries.
I think I have everything setup correctly, however I don't seem to be getting any traffic from P25 into Analog_bridge. There also seems to be some conflicts in the ini file, I see this in the debug messages when I start it up:
root@radioserver:/opt/Analog_Bridge# ./Analog_Bridge Analog_Bridge_P25.ini
I: 2018-09-10 23:15:23.979 Analog Bridge Version 1.1 Wed 9 May 05:56:17 EDT 2018
I: 2018-09-10 23:15:23.979 Copyright (C) 2018 DVSwitch, INAD.
I: 2018-09-10 23:15:23.979 Created by Mike N4IRR and Steve N4IRS
I: 2018-09-10 23:15:23.979 Analog Bridge comes with ABSOLUTELY NO WARRANTY
I: 2018-09-10 23:15:23.979
I: 2018-09-10 23:15:23.979 This software is for use on amateur radio networks only,
I: 2018-09-10 23:15:23.979 it is to be used for educational purposes only. Its use on
I: 2018-09-10 23:15:23.979 commercial networks is strictly prohibited.
I: 2018-09-10 23:15:23.979
I: 2018-09-10 23:15:23.979 Analog Bridge is starting
M: 2018-09-10 23:15:23.980 Setting [GENERAL] logLevel -> 2
M: 2018-09-10 23:15:23.980 Setting [GENERAL] subscriberFile -> ./subscriber_ids.csv
M: 2018-09-10 23:15:23.980 Setting [GENERAL] exportMetadata -> true
M: 2018-09-10 23:15:23.980 Setting [GENERAL] decoderFallBack -> true
M: 2018-09-10 23:15:23.980 Setting [GENERAL] useEmulator -> false
M: 2018-09-10 23:15:23.980 Setting [GENERAL] emulatorAddress ->
127.0.0.1:2470
W: 2018-09-10 23:15:23.980 Unknown section/name in .ini file: AMBE_AUDIO/address
W: 2018-09-10 23:15:23.980 Unknown section/name in .ini file: AMBE_AUDIO/txPort
W: 2018-09-10 23:15:23.980 Unknown section/name in .ini file: AMBE_AUDIO/rxPort
M: 2018-09-10 23:15:23.980 Setting [AMBE_AUDIO] ambeMode -> P25
M: 2018-09-10 23:15:23.980 Setting [AMBE_AUDIO] minTxTimeMS -> 2000
M: 2018-09-10 23:15:23.980 Setting [AMBE_AUDIO] gatewayDmrId -> 1234567
M: 2018-09-10 23:15:23.980 Setting [AMBE_AUDIO] repeaterID -> 123456789
M: 2018-09-10 23:15:23.980 Setting [AMBE_AUDIO] txTg -> 9
M: 2018-09-10 23:15:23.980 Setting [AMBE_AUDIO] txTs -> 2
M: 2018-09-10 23:15:23.981 Setting [AMBE_AUDIO] colorCode -> 1
W: 2018-09-10 23:15:23.981 Unknown section/name in .ini file: USRP/address
W: 2018-09-10 23:15:23.981 Unknown section/name in .ini file: USRP/txPort
W: 2018-09-10 23:15:23.981 Unknown section/name in .ini file: USRP/rxPort
M: 2018-09-10 23:15:23.981 Setting [USRP] aslAudio -> AUDIO_UNITY
M: 2018-09-10 23:15:23.981 Setting [USRP] agcGain -> -20
M: 2018-09-10 23:15:23.981 Setting [USRP] dmrAudio -> AUDIO_UNITY
M: 2018-09-10 23:15:23.981 Setting [USRP] dmrGain -> 0.35
W: 2018-09-10 23:15:23.981 Unknown section/name in .ini file: DV3000/address
W: 2018-09-10 23:15:23.981 Unknown section/name in .ini file: DV3000/rxPort
W: 2018-09-10 23:15:23.981 ioctl reset error
W: 2018-09-10 23:15:23.981 ioctl speed error
W: 2018-09-10 23:15:23.981 ioctl stereo error
W: 2018-09-10 23:15:23.981 ioctl setfmt error
M: 2018-09-10 23:15:23.981 Audio In/Out Device: /dev/null
M: 2018-09-10 23:15:23.982 Connecting to DV3000 hardware......
Project 25 IMBE Encoder/Decoder Fixed-Point implementation
Version 1.0 (c) Copyright 2009
This program comes with ABSOLUTELY NO WARRANTY.
This is free software, and you are welcome to redistribute it
under certain conditions; see the file ``LICENSE'' for details.
I: 2018-09-10 23:15:24.992 Subscriber IDs file not found.
I: 2018-09-10 23:15:24.992 Default extended metadata <1234567>
W: 2018-09-10 23:15:24.992 Using software MBE decoder version 1.2.3
W: 2018-09-10 23:15:24.992 Using software OP25 IMBE/AMBE vocoder
I: 2018-09-10 23:15:24.993 Starting Analog_Bridge --> USRP thread
I: 2018-09-10 23:15:24.993 Starting USRP --> IPSC_Bridge thread
MMDVM_bridge/P25Gateway appear to work fine, I have them pointed at a test reflector I built. All are locally hosted on the same raspberry pi, and there doesn't appear to be any firewall issues blocking anything, I allow everyting in and out on lo. I built
a private node on the app_rpt side and see key/unkey events if I connect my normal node to it so that part seems to be working at least.
I think I might be missing something, or something is potentially misconfig'd, but can't really put a finger on it. Does Analog_bridge handle P25/IMBE transcoding, or do I need something "external" for that to take place? I also will typically use a different
ID on private networks such as this, and have had that sort of stuff get me in the past, so also wanted to make sure there is no ID checking?
73
Stephen
K1LNX
|
|
Re: Setting up Analog_bridge for P25

Steve N4IRS
Except the DV3000 does not do P25
Sent via smoke signal (AT&T)
toggle quoted messageShow quoted text
From: main@DVSwitch.groups.io <main@DVSwitch.groups.io> on behalf of Jeff Carrier <k0jsc.jeff@...>
Sent: Tuesday, September 11, 2018 3:29:00 PM
To: main@dvswitch.groups.io
Subject: Re: [DVSwitch] Setting up Analog_bridge for P25
I can send you my config Stephen.
I'm not running OP25 because IMHO I believe the DV3000 produces better audio.
Give me a few to get logged in and grab them.
On Tue, Sep 11, 2018 at 1:13 PM Stephen Brown - K1LNX < k1lnx@...> wrote:
Thanks Steve, but still no go on this... and I noticed under the [AMBE_AUDIO] section that ambeMode = DMR, should this be set to P25 instead, or does it matter? I did set it to P25.
Do I need to be using the emulator for P25/IMBE mode? I still feel like I might be missing something, but maybe not.
On Tue, Sep 11, 2018 at 11:29 AM Steve N4IRS < szingman@...> wrote:
Stephen,
It looks like I need to update the RPi and the x86 versions of Analog_Bridge. I will TRY to get it done this week, but this is my first day back at work after a week. I doing catch up. In the mean time, use this as a template for your RPi AB:
; Analog_Bridge configuration file.
; This file should be placed in either /etc or it can be
; supplied as a path on the Analog_Bridge command line.
; General Section describes settings for Analog_Bridge itself.
; For RPI, don't forget to modprobe snd_pcm_oss to get the devices populated
[GENERAL]
logLevel = 2 ; Show messages and above 0=No logging, 1=Debug, 2=Message, 3=Info, 4=Warning, 5=Error, 6=Fatal
; Metadata management
exportMetadata = true ; Export metadata to USRP partner (transcode setups require this)
subscriberFile = /var/lib/dvswitch/subscriber_ids.csv ; DMR ID to callsign lookup data
; General vocoder setup information
decoderFallBack = true ; Allow software AMBE decoding if a hardware decoder is not found
useEmulator = true ; Use the MD380 AMBE emulator for AMBE72 (DMR/YSFN/NXDN)
emulatorAddress = 127.0.0.1:2470 ; IP address and port of the server
; Audio devices are normally not needed when in gateway service. These devices should
; only be set when local monitor or dongle modes are required.
outputAudioDevice = /dev/null ; Audio device /dev/null, /dev/dsp1, portaudio, etc
inputAudioDevice = /dev/null ; Only used for dongle mode
; Below values are for using this as a local DMR dongle (no ASL needed)
useMicrophone = false ; Use app as just a fancy dongle for DMR
useVox = false ; If using dongle mode (useMicrophone), enable VOX
voxDecay = 2 ; Hang time in seconds
voxTrigger = 200 ; Value to trip PTT (0-32767)
; Information for xx_Bridges (Where xx is MMDVM, HB, IPSC)
[AMBE_AUDIO]
server = 127.0.0.1 ; IP address of xx_Bridge.py
fromDMRPort = 31000 ; AMBE frames from xx_Bridge (should match "toGatewayPort" in xx_Bridge.cfg)
toDMRPort = 31003 ; AMBE frames from xx_Bridge (should match "fromGatewayPort" in xx_Bridge.cfg)
ambeMode = DMR ; DMR, DMR_IPSC, DSTAR, NXDN, P25, YSFN, YSFW
minTxTimeMS = 2000 ; Minimum time in MS for hang delay
gatewayDmrId = 3112138 ; ID to use when transmitting from Analog_Bridge
repeaterID = 311213850 ; ID of source repeater
txTg = 9 ; TG to use for all frames received from Analog_Bridge -> xx_Bridge
txTs = 2 ; Slot to use for frames received from Analog_Bridge -> xx_Bridge
colorCode = 1 ; Color Code to assign DMR frames
; Information for USRP channel driver. This interface uses PCM to transfer audio information
; There are two typical configurations, ASL and Transcode. ASL (AllstarLink) is for analog clients connected
; to a digital network. Transcode is when Analog_Bridge actually points its PCM interfaces back at itself,
; causing a TLV <-- (pcm <--> pcm) --> TLV type of architecture.
; When using ASL, this matches the rpt.conf ASL file with a setting like:
; rxchannel = usrp/127.0.0.1:34001:32001
; When Transcoding, make toASLPort equal to the other instance fromASLPort (crossover)
[USRP]
server = 127.0.0.1 ; IP address of Allstar/Asterisk
toASLPort = 32001 ; Analog_Bridge <-- ASL
fromASLPort = 34001 ; Analog_Bridge --> ASL
aslAudio = AUDIO_UNITY ; Audio to ASL (AUDIO_UNITY, AUDIO_USE_AGC, AUDIO_USE_GAIN)
agcGain = -20 ; Gain (in db) of the AGC filter
dmrAudio = AUDIO_UNITY ; Audio from ASL (AUDIO_UNITY, AUDIO_USE_GAIN, AUDIO_BPF)
dmrGain = 0.35 ; Gain factor of audio from ASL (0.0-1.0)
; Information for DV3000 hardware decoder
; There are two configuration modes: IP (AMBEServer) and serial (direct connect hardware)
; Use top server and port if using AMBEServer
; Use bottom server/port and serial = true if using the DV3000u (thumbdv)
; Did you run AMBETest4.py before using this?
[DV3000]
server = 127.0.0.1 ; IP address of AMBEServer
port = 2460 ; Port of AMBEServer
; server = /dev/ttyUSB0 ; Device of DV3000U on this machine
; port = 460800 ; Baud rate of the dongle
; serial = true ; Use serial (DV3000U) or IP
On 9/11/2018 11:18 AM, Stephen Brown - K1LNX wrote:
Thanks Steve, here it is:
; Analog_Bridge configuration file.
; This file should be placed in either /etc or it can be
; supplied as a path on the Analog_Bridge command line.
; The best way to think of this file is that there are two main sections, the USRP (analog audio) and
; AMBE_AUDIO (compressed audio). Analog_Bridge will take everything sent to the USRP port and
; encode it for transmission on the AMBE_AUDIO port. The encoder will use the format defined in ambeMode.
; As you might expect, the reverse direction is defined too.
; General Section describes settings for Analog_Bridge itself.
[GENERAL]
logLevel = 2 ; Show messages and above 0=No logging, 1=Debug, 2=Message, 3=Info, 4=Warning, 5=Error, 6=Fatal
; Metadata management
subscriberFile = ./subscriber_ids.csv ; DMR ID to callsign lookup data
exportMetadata = true ; Export metadata to USRP partner (transcode setups require this)
; General vocoder setup information
decoderFallBack = true ; Allow software AMBE decoding if a hardware decoder is not found
useEmulator = false ; Use the MD380 AMBE emulator for AMBE72 (DMR/YSFN/NXDN)
emulatorAddress = 127.0.0.1:2470 ; IP address and port of the md380 server
; Information for xx_Bridge (Where xx is MMDVM, Quantar, HB, IPSC)
[AMBE_AUDIO]
address = 127.0.0.1 ; IP address of xx_Bridge
txPort = 31003 ; Transmit TLV frames to partner on this port
rxPort = 31000 ; Listen for TLV frames from partner on this port
ambeMode = P25 ; DMR, DMR_IPSC, DSTAR, NXDN, P25, YSFN, YSFW (encode PCM to this format)
minTxTimeMS = 2000 ; Minimum time in MS for hang delay (0-10000)
; The metadata below is used when ASL is the source since it does not have any concept of digital modes
gatewayDmrId = 1234567 ; ID to use when transmitting from Analog_Bridge
repeaterID = 123456789 ; ID of source repeater
txTg = 9 ; TG to use for all frames sent from Analog_Bridge -> xx_Bridge
txTs = 2 ; Slot to use for frames sent from Analog_Bridge -> xx_Bridge
colorCode = 1 ; Color Code to assign DMR frames
; Information for USRP channel driver. This interface uses PCM to transfer audio information
; There are two typical configurations, ASL and Transcode. ASL (AllstarLink) is for analog clients connected
; to a digital network. Transcode is when Analog_Bridge actually points its PCM interfaces back at itself,
; causing a TLV <-- (pcm <--> pcm) --> TLV type of architecture.
; When using ASL, this matches the rpt.conf ASL file with a setting like:
; rxchannel = usrp/127.0.0.1:34001:32001
; When Transcoding, make two ini files and set txPort equal to the other instance rxPort (crossover). Launch
; each instance with its own ini file.
[USRP]
address = 127.0.0.1 ; IP address of USRP partner (Allstar/Asterisk or another Analog_Bridge)
txPort = 32001 ; Transmit USRP frames on this port
rxPort = 34001 ; Listen for USRP frames on this port
aslAudio = AUDIO_UNITY ; Audio to ASL (AUDIO_UNITY, AUDIO_USE_AGC, AUDIO_USE_GAIN)
agcGain = -20 ; Gain (in db) of the AGC filter
dmrAudio = AUDIO_UNITY ; Audio from ASL (AUDIO_UNITY, AUDIO_USE_GAIN, AUDIO_BPF)
dmrGain = 0.35 ; Gain factor of audio from ASL (0.0-1.0)
; Information for DV3000 hardware decoder
; There are two configuration modes: IP (AMBEServer) and serial (direct connect hardware)
; Use top server and port if using AMBEServer
; Use bottom server/port and serial = true if using the DV3000u (thumbdv)
; Did you run AMBETest4.py before using this?
[DV3000]
address = 127.0.0.1 ; IP address of AMBEServer
rxPort = 2460 ; Port of AMBEServer
; address = /dev/ttyUSB0 ; Device of DV3000U on this machine
; baud = 460800 ; Baud rate of the dongle (230400 or 460800)
; serial = true ; Use serial=true for direct connect or serial=false for AMBEServer
On Tue, Sep 11, 2018 at 11:16 AM Steve N4IRS < szingman@...> wrote:
Stephen,
Please post your Analog_Bridge_P25.ini
On 9/11/2018 11:01 AM, Stephen Brown - K1LNX wrote:
Hi guys,
So I'm just starting to play with Analog_bridge and P25. My (limited) understanding is that transcoding to/from PCM is handled via software and the OP25 libraries.
I think I have everything setup correctly, however I don't seem to be getting any traffic from P25 into Analog_bridge. There also seems to be some conflicts in the ini file, I see this in the debug messages when I start it up:
root@radioserver:/opt/Analog_Bridge# ./Analog_Bridge Analog_Bridge_P25.ini
I: 2018-09-10 23:15:23.979 Analog Bridge Version 1.1 Wed 9 May 05:56:17 EDT 2018
I: 2018-09-10 23:15:23.979 Copyright (C) 2018 DVSwitch, INAD.
I: 2018-09-10 23:15:23.979 Created by Mike N4IRR and Steve N4IRS
I: 2018-09-10 23:15:23.979 Analog Bridge comes with ABSOLUTELY NO WARRANTY
I: 2018-09-10 23:15:23.979
I: 2018-09-10 23:15:23.979 This software is for use on amateur radio networks only,
I: 2018-09-10 23:15:23.979 it is to be used for educational purposes only. Its use on
I: 2018-09-10 23:15:23.979 commercial networks is strictly prohibited.
I: 2018-09-10 23:15:23.979
I: 2018-09-10 23:15:23.979 Analog Bridge is starting
M: 2018-09-10 23:15:23.980 Setting [GENERAL] logLevel -> 2
M: 2018-09-10 23:15:23.980 Setting [GENERAL] subscriberFile -> ./subscriber_ids.csv
M: 2018-09-10 23:15:23.980 Setting [GENERAL] exportMetadata -> true
M: 2018-09-10 23:15:23.980 Setting [GENERAL] decoderFallBack -> true
M: 2018-09-10 23:15:23.980 Setting [GENERAL] useEmulator -> false
M: 2018-09-10 23:15:23.980 Setting [GENERAL] emulatorAddress ->
127.0.0.1:2470
W: 2018-09-10 23:15:23.980 Unknown section/name in .ini file: AMBE_AUDIO/address
W: 2018-09-10 23:15:23.980 Unknown section/name in .ini file: AMBE_AUDIO/txPort
W: 2018-09-10 23:15:23.980 Unknown section/name in .ini file: AMBE_AUDIO/rxPort
M: 2018-09-10 23:15:23.980 Setting [AMBE_AUDIO] ambeMode -> P25
M: 2018-09-10 23:15:23.980 Setting [AMBE_AUDIO] minTxTimeMS -> 2000
M: 2018-09-10 23:15:23.980 Setting [AMBE_AUDIO] gatewayDmrId -> 1234567
M: 2018-09-10 23:15:23.980 Setting [AMBE_AUDIO] repeaterID -> 123456789
M: 2018-09-10 23:15:23.980 Setting [AMBE_AUDIO] txTg -> 9
M: 2018-09-10 23:15:23.980 Setting [AMBE_AUDIO] txTs -> 2
M: 2018-09-10 23:15:23.981 Setting [AMBE_AUDIO] colorCode -> 1
W: 2018-09-10 23:15:23.981 Unknown section/name in .ini file: USRP/address
W: 2018-09-10 23:15:23.981 Unknown section/name in .ini file: USRP/txPort
W: 2018-09-10 23:15:23.981 Unknown section/name in .ini file: USRP/rxPort
M: 2018-09-10 23:15:23.981 Setting [USRP] aslAudio -> AUDIO_UNITY
M: 2018-09-10 23:15:23.981 Setting [USRP] agcGain -> -20
M: 2018-09-10 23:15:23.981 Setting [USRP] dmrAudio -> AUDIO_UNITY
M: 2018-09-10 23:15:23.981 Setting [USRP] dmrGain -> 0.35
W: 2018-09-10 23:15:23.981 Unknown section/name in .ini file: DV3000/address
W: 2018-09-10 23:15:23.981 Unknown section/name in .ini file: DV3000/rxPort
W: 2018-09-10 23:15:23.981 ioctl reset error
W: 2018-09-10 23:15:23.981 ioctl speed error
W: 2018-09-10 23:15:23.981 ioctl stereo error
W: 2018-09-10 23:15:23.981 ioctl setfmt error
M: 2018-09-10 23:15:23.981 Audio In/Out Device: /dev/null
M: 2018-09-10 23:15:23.982 Connecting to DV3000 hardware......
Project 25 IMBE Encoder/Decoder Fixed-Point implementation
Version 1.0 (c) Copyright 2009
This program comes with ABSOLUTELY NO WARRANTY.
This is free software, and you are welcome to redistribute it
under certain conditions; see the file ``LICENSE'' for details.
I: 2018-09-10 23:15:24.992 Subscriber IDs file not found.
I: 2018-09-10 23:15:24.992 Default extended metadata <1234567>
W: 2018-09-10 23:15:24.992 Using software MBE decoder version 1.2.3
W: 2018-09-10 23:15:24.992 Using software OP25 IMBE/AMBE vocoder
I: 2018-09-10 23:15:24.993 Starting Analog_Bridge --> USRP thread
I: 2018-09-10 23:15:24.993 Starting USRP --> IPSC_Bridge thread
MMDVM_bridge/P25Gateway appear to work fine, I have them pointed at a test reflector I built. All are locally hosted on the same raspberry pi, and there doesn't appear to be any firewall issues blocking anything, I allow everyting in and out on lo. I built
a private node on the app_rpt side and see key/unkey events if I connect my normal node to it so that part seems to be working at least.
I think I might be missing something, or something is potentially misconfig'd, but can't really put a finger on it. Does Analog_bridge handle P25/IMBE transcoding, or do I need something "external" for that to take place? I also will typically use a different
ID on private networks such as this, and have had that sort of stuff get me in the past, so also wanted to make sure there is no ID checking?
73
Stephen
K1LNX
|
|