Date   

Re: ASL<>Analog_Bridge<>HBlink not working

Steve N4IRS
 

Steve,
Assumptions:
You are running HB_Bridge.py not hblink.py
HB_Bridge ports are pointing at Analog_Bridge ports.

Post your HB_Bridge config file.

Steve


On 04/14/2018 05:15 PM, Steve Siesel [K4KSA] wrote:

 

 

All,

 

I’ve just upgraded to the latest Analog Bridge and HBLink from github and I am having some issues and need some help. Originally I was thinking my DV3000 was not working but after doing AMBEtest4.py it came back successful.

ASL does talk to analog_bridge…I see can see the PTT on and off:

 

                M: 2018-04-14 20:54:02.109 PTT on

              M: 2018-04-14 20:54:07.288 PTT off (keyed for 5179 ms)

 

However  I don’t see anything in the HBlink screen. Also I don’t see DMR transmissions made on the talkgroup:

 

INFO 2018-04-14 17:01:57,649 (REPEATER-1) Sending login request to master 74.91.114.19:62031

DEBUG 2018-04-14 17:01:57,650 CLIENT instance created: REPEATER-1, <__main__.HBSYSTEM instance at 0x764d3da0>

INFO 2018-04-14 17:01:57,690 (REPEATER-1) Repeater Login ACK Received with 32bit ID: 2715672343

INFO 2018-04-14 17:01:57,737 (REPEATER-1) Repeater Authentication Accepted

INFO 2018-04-14 17:01:57,739 (REPEATER-1) Repeater Configuration Sent

INFO 2018-04-14 17:01:57,785 (REPEATER-1) Repeater Configuration Accepted

INFO 2018-04-14 17:01:57,786 (REPEATER-1) Connection to Master Completed

DEBUG 2018-04-14 17:02:02,652 (REPEATER-1) Client maintenance loop started

DEBUG 2018-04-14 17:02:02,653 (REPEATER-1) RPTPING Sent to Master. Total Sent: 0, Total Missed: 0, Currently Outstanding: 0

DEBUG 2018-04-14 17:02:02,693 (REPEATER-1) MSTPONG Received. Pongs Since Connected: 1

DEBUG 2018-04-14 17:02:07,652 (REPEATER-1) Client maintenance loop started

DEBUG 2018-04-14 17:02:07,653 (REPEATER-1) RPTPING Sent to Master. Total Sent: 1, Total Missed: 0, Currently Outstanding: 0

DEBUG 2018-04-14 17:02:07,693 (REPEATER-1) MSTPONG Received. Pongs Since Connected: 2

 

 

Here is my Analog_bridge.ini:

 

; 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]

; Audio devices are normally not needed when in gateway service.  These devices should

; only be set when local monitor or dongle modes are required.

 

logLevel = 2                    ; Show messages and above

outputAudioDevice = /dev/null   ; Audio device /dev/null, /dev/dsp1, portaudio, etc

inputAudioDevice = /dev/null    ; Only used for dongle mode

decoderFallBack = false         ; Use software AMBE decoder

 

; 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_Bridge.py

[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)

ambeSize = 49                   ; 72 bit is HB_Bridge AMBE, 49 bit is IPSC_Bridge AMBE

minTxTimeMS = 2000              ; Minimum time in MS for hang delay

gatewayDmrId = 1112721          ; ID to use when transmitting from Analog_Bridge

repeaterID =   11127213         ; ID of source repeater

txTg = 31676                    ; 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 matches the rpt.conf ASL file with a setting like:

;   rxchannel = usrp/127.0.0.1:34001:32001

[USRP]

server = 127.0.0.1              ; IP address of Allstar/Asterisk

toASLPort = 32001               ; PCM from ASL

fromASLPort = 34001             ; PCM to ASL

aslAudio = AUDIO_USE_AGC        ; 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_GAIN, AUDIO_BPF)

dmrGain = 0.35                  ; Gain factor of audio from ASL (0.0-1.0)

 

; Information for DV3000 hardware decoder

;   Use top server and port if using AMBEServer

;   Use bottom server/port and serial = true if using the DV3000u (thumbdv)

[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

 

 

And my hblink.cfg:

 

# PROGRAM-WIDE PARAMETERS GO HERE

# PATH - working path for files, leave it alone unless you NEED to change it

# PING_TIME - the interval that clients will ping the master, and re-try registraion

#           - how often the Master maintenance loop runs

# MAX_MISSED - how many pings are missed before we give up and re-register

#           - number of times the master maintenance loop runs before de-registering a client

[GLOBAL]

PATH: ./

PING_TIME: 5

MAX_MISSED: 3

 

# SYSTEM LOGGER CONFIGURAITON

#   This allows the logger to be configured without chaning the individual

#   python logger stuff. LOG_FILE should be a complete path/filename for *your*

#   system -- use /dev/null for non-file handlers.

#   LOG_HANDERLS may be any of the following, please, no spaces in the

#   list if you use several:

#       null

#       console

#       console-timed

#       file

#       file-timed

#       syslog

#   LOG_LEVEL may be any of the standard syslog logging levels, though

#   as of now, DEBUG, INFO, WARNING and CRITICAL are the only ones

#   used.

#

[LOGGER]

LOG_FILE: /var/log/hblink.log

LOG_HANDLERS: console-timed

LOG_LEVEL: DEBUG

LOG_NAME: HBlink

 

# DOWNLOAD AND IMPORT SUBSCRIBER, PEER and TGID ALIASES

# Ok, not the TGID, there's no master list I know of to download

# This is intended as a facility for other applcations built on top of

# HBlink to use, and will NOT be used in HBlink directly.

# STALE_DAYS is the number of days since the last download before we

# download again. Don't be an ass and change this to less than a few days.

[ALIASES]

TRY_DOWNLOAD: True

PATH: ./

PEER_FILE: peer_ids.csv

SUBSCRIBER_FILE: subscriber_ids.json

TGID_FILE: talkgroup_ids.json

PEER_URL: http://www.dmr-marc.net/cgi-bin/trbo-database/datadump.cgi?table=repe$

SUBSCRIBER_URL: http://www.dmr-marc.net/cgi-bin/trbo-database/datadump.cgi?tabl$

STALE_DAYS: 7

 

 

# EXPORT AMBE DATA

# This is for exporting AMBE audio frames to an an "external" process for

# decoding or other nefarious actions.

[AMBE]

EXPORT_IP: 127.0.0.1

EXPORT_PORT: 1234

 

# MASTER INSTANCES - DUPLICATE SECTION FOR MULTIPLE MASTERS

# HomeBrew Protocol Master instances go here.

# IP may be left blank if there's one interface on your system.

# Port should be the port you want this master to listen on. It must be unique

# and unused by anything else.

# Repeat - if True, the master repeats traffic to clients, False, it does nothing.

[MASTER-1]

MODE: MASTER

ENABLED: False

REPEAT: True

EXPORT_AMBE: False

IP:

PORT: 54000

PASSPHRASE: s3cr37w0rd

GROUP_HANGTIME: 5

 

# CLIENT INSTANCES - DUPLICATE SECTION FOR MULTIPLE CLIENTS

# There are a LOT of errors in the HB Protocol specifications on this one!

# MOST of these items are just strings and will be properly dealt with by the program

# The TX & RX Frequencies are 9-digit numbers, and are the frequency in Hz.

# Latitude is an 8-digit unsigned floating point number.

# Longitude is a 9-digit signed floating point number.

# Height is in meters

[REPEATER-1]

MODE: CLIENT

ENABLED: True

EXPORT_AMBE: False

IP:

PORT: 54001

MASTER_IP: 3102.repeater.net

MASTER_PORT: 62031

PASSPHRASE: passw0rd

CALLSIGN: K4KSA

RADIO_ID: 11127213

RX_FREQ: 449000000

TX_FREQ: 444000000

TX_POWER: 25

COLORCODE: 1

SLOTS: 3

LATITUDE: 27.863859

LONGITUDE: -82.833252

HEIGHT: 40

LOCATION: Seminole, Florida

DESCRIPTION: DMR<> Allstar Gateway

URL: https://groups.io/g/DVSwitch

SOFTWARE_ID: 20170620

PACKAGE_ID: MMDVM_HBlink

GROUP_HANGTIME: 5

OPTIONS:

 

 

Any help would be appreciated!

Steve

 

 

 



ASL<>Analog_Bridge<>HBlink not working

Steve Siesel [K4KSA]
 

 

 

All,

 

I’ve just upgraded to the latest Analog Bridge and HBLink from github and I am having some issues and need some help. Originally I was thinking my DV3000 was not working but after doing AMBEtest4.py it came back successful.

ASL does talk to analog_bridge…I see can see the PTT on and off:

 

                M: 2018-04-14 20:54:02.109 PTT on

              M: 2018-04-14 20:54:07.288 PTT off (keyed for 5179 ms)

 

However  I don’t see anything in the HBlink screen. Also I don’t see DMR transmissions made on the talkgroup:

 

INFO 2018-04-14 17:01:57,649 (REPEATER-1) Sending login request to master 74.91.114.19:62031

DEBUG 2018-04-14 17:01:57,650 CLIENT instance created: REPEATER-1, <__main__.HBSYSTEM instance at 0x764d3da0>

INFO 2018-04-14 17:01:57,690 (REPEATER-1) Repeater Login ACK Received with 32bit ID: 2715672343

INFO 2018-04-14 17:01:57,737 (REPEATER-1) Repeater Authentication Accepted

INFO 2018-04-14 17:01:57,739 (REPEATER-1) Repeater Configuration Sent

INFO 2018-04-14 17:01:57,785 (REPEATER-1) Repeater Configuration Accepted

INFO 2018-04-14 17:01:57,786 (REPEATER-1) Connection to Master Completed

DEBUG 2018-04-14 17:02:02,652 (REPEATER-1) Client maintenance loop started

DEBUG 2018-04-14 17:02:02,653 (REPEATER-1) RPTPING Sent to Master. Total Sent: 0, Total Missed: 0, Currently Outstanding: 0

DEBUG 2018-04-14 17:02:02,693 (REPEATER-1) MSTPONG Received. Pongs Since Connected: 1

DEBUG 2018-04-14 17:02:07,652 (REPEATER-1) Client maintenance loop started

DEBUG 2018-04-14 17:02:07,653 (REPEATER-1) RPTPING Sent to Master. Total Sent: 1, Total Missed: 0, Currently Outstanding: 0

DEBUG 2018-04-14 17:02:07,693 (REPEATER-1) MSTPONG Received. Pongs Since Connected: 2

 

 

Here is my Analog_bridge.ini:

 

; 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]

; Audio devices are normally not needed when in gateway service.  These devices should

; only be set when local monitor or dongle modes are required.

 

logLevel = 2                    ; Show messages and above

outputAudioDevice = /dev/null   ; Audio device /dev/null, /dev/dsp1, portaudio, etc

inputAudioDevice = /dev/null    ; Only used for dongle mode

decoderFallBack = false         ; Use software AMBE decoder

 

; 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_Bridge.py

[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)

ambeSize = 49                   ; 72 bit is HB_Bridge AMBE, 49 bit is IPSC_Bridge AMBE

minTxTimeMS = 2000              ; Minimum time in MS for hang delay

gatewayDmrId = 1112721          ; ID to use when transmitting from Analog_Bridge

repeaterID =   11127213         ; ID of source repeater

txTg = 31676                    ; 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 matches the rpt.conf ASL file with a setting like:

;   rxchannel = usrp/127.0.0.1:34001:32001

[USRP]

server = 127.0.0.1              ; IP address of Allstar/Asterisk

toASLPort = 32001               ; PCM from ASL

fromASLPort = 34001             ; PCM to ASL

aslAudio = AUDIO_USE_AGC        ; 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_GAIN, AUDIO_BPF)

dmrGain = 0.35                  ; Gain factor of audio from ASL (0.0-1.0)

 

; Information for DV3000 hardware decoder

;   Use top server and port if using AMBEServer

;   Use bottom server/port and serial = true if using the DV3000u (thumbdv)

[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

 

 

And my hblink.cfg:

 

# PROGRAM-WIDE PARAMETERS GO HERE

# PATH - working path for files, leave it alone unless you NEED to change it

# PING_TIME - the interval that clients will ping the master, and re-try registraion

#           - how often the Master maintenance loop runs

# MAX_MISSED - how many pings are missed before we give up and re-register

#           - number of times the master maintenance loop runs before de-registering a client

[GLOBAL]

PATH: ./

PING_TIME: 5

MAX_MISSED: 3

 

# SYSTEM LOGGER CONFIGURAITON

#   This allows the logger to be configured without chaning the individual

#   python logger stuff. LOG_FILE should be a complete path/filename for *your*

#   system -- use /dev/null for non-file handlers.

#   LOG_HANDERLS may be any of the following, please, no spaces in the

#   list if you use several:

#       null

#       console

#       console-timed

#       file

#       file-timed

#       syslog

#   LOG_LEVEL may be any of the standard syslog logging levels, though

#   as of now, DEBUG, INFO, WARNING and CRITICAL are the only ones

#   used.

#

[LOGGER]

LOG_FILE: /var/log/hblink.log

LOG_HANDLERS: console-timed

LOG_LEVEL: DEBUG

LOG_NAME: HBlink

 

# DOWNLOAD AND IMPORT SUBSCRIBER, PEER and TGID ALIASES

# Ok, not the TGID, there's no master list I know of to download

# This is intended as a facility for other applcations built on top of

# HBlink to use, and will NOT be used in HBlink directly.

# STALE_DAYS is the number of days since the last download before we

# download again. Don't be an ass and change this to less than a few days.

[ALIASES]

TRY_DOWNLOAD: True

PATH: ./

PEER_FILE: peer_ids.csv

SUBSCRIBER_FILE: subscriber_ids.json

TGID_FILE: talkgroup_ids.json

PEER_URL: http://www.dmr-marc.net/cgi-bin/trbo-database/datadump.cgi?table=repe$

SUBSCRIBER_URL: http://www.dmr-marc.net/cgi-bin/trbo-database/datadump.cgi?tabl$

STALE_DAYS: 7

 

 

# EXPORT AMBE DATA

# This is for exporting AMBE audio frames to an an "external" process for

# decoding or other nefarious actions.

[AMBE]

EXPORT_IP: 127.0.0.1

EXPORT_PORT: 1234

 

# MASTER INSTANCES - DUPLICATE SECTION FOR MULTIPLE MASTERS

# HomeBrew Protocol Master instances go here.

# IP may be left blank if there's one interface on your system.

# Port should be the port you want this master to listen on. It must be unique

# and unused by anything else.

# Repeat - if True, the master repeats traffic to clients, False, it does nothing.

[MASTER-1]

MODE: MASTER

ENABLED: False

REPEAT: True

EXPORT_AMBE: False

IP:

PORT: 54000

PASSPHRASE: s3cr37w0rd

GROUP_HANGTIME: 5

 

# CLIENT INSTANCES - DUPLICATE SECTION FOR MULTIPLE CLIENTS

# There are a LOT of errors in the HB Protocol specifications on this one!

# MOST of these items are just strings and will be properly dealt with by the program

# The TX & RX Frequencies are 9-digit numbers, and are the frequency in Hz.

# Latitude is an 8-digit unsigned floating point number.

# Longitude is a 9-digit signed floating point number.

# Height is in meters

[REPEATER-1]

MODE: CLIENT

ENABLED: True

EXPORT_AMBE: False

IP:

PORT: 54001

MASTER_IP: 3102.repeater.net

MASTER_PORT: 62031

PASSPHRASE: passw0rd

CALLSIGN: K4KSA

RADIO_ID: 11127213

RX_FREQ: 449000000

TX_FREQ: 444000000

TX_POWER: 25

COLORCODE: 1

SLOTS: 3

LATITUDE: 27.863859

LONGITUDE: -82.833252

HEIGHT: 40

LOCATION: Seminole, Florida

DESCRIPTION: DMR<> Allstar Gateway

URL: https://groups.io/g/DVSwitch

SOFTWARE_ID: 20170620

PACKAGE_ID: MMDVM_HBlink

GROUP_HANGTIME: 5

OPTIONS:

 

 

Any help would be appreciated!

Steve

 

 

 


Re: DVSwitch Status update

James Riley kb9tzq
 

Thanks Steve for everything you guys do and keep up the job hopefully I will have a nxdn talkgroup on mmdvm this weekend and I think I have my p25 talkgroup up and going once you guys come out with the toolkit I will be ready


Re: HB_Bridge send stream back to master

Matthew 2E0SIP
 

Hi Steve,

Good guess, I hadn't declared the duplex setting for the node connected to Analog_Bridge.

Thanks for your assistance and patience,

Matthew


Re: Break this "stuff" into sub groups. #poll

 

We use Groups.io subtopics in nw-digital-radio.groups.io to separate interest groups (eg. AMBE, UDRC, Compass, ...) and it works quite well.


Re: P25 Integration via AllStar Link

Steve N4IRS
 

Well,
This is heating up more then I would have expected. Looking back over one of my first answers, we need to simplify connecting a Quantar P25 to AllStarLink. Mike, N4IRR and I will have to go over it to see what should be done to Quantar Bridge to simplify the Partners needed. Quantar will need to act more like a traditional DVSwitch Partner think it can look something like this:
Quantar (V.24 board) <---> Cisco <---> Analog_bridge <---> AllstarLink.
At least for the foreseeable future, the Cisco will still be required. I am using the 1841. It's at end of life but it's quite available on eBay and the hardware and software can be upgraded to do the job. I will say of the digital voice modes, P25 is one of the best choices to connect to a analog network due to the improved voice quality. The same can be said for Yaesu wide since they are both IMBE.

73, Steve N4IRS        


Re: P25 Integration via AllStar Link

Tracy KI0HC
 

Hi 

This is my first post, I am new to the group, I live in the Denver area and have two Quantar repeaters on 900MHz.
I'm also very interested on how to get my Quantar P25 to work on Allstar, I just changed my repeater over to P25 and would like to take the next step to link it to the Allstar network.

73's
Tracy KI0HC


Re: Break this "stuff" into sub groups. #poll

Rob WX1N
 

Hi Steve and all,

 

I only lurk, as I am not currently in need of assistance and have no experience to contribute.  However, I find reading the variety of topics that come through to be informative, and give me some background info should I wander into any of the areas that are being addressed.  So I would like to see things remain in one group, but I would defer my vote to more active users and their feelings on the matter.

 

73,

 

Rob, WX1N

 

From: main@DVSwitch.groups.io <main@DVSwitch.groups.io> On Behalf Of Steve N4IRS
Sent: Friday, April 13, 2018 11:46 AM
To: main@DVSwitch.groups.io
Subject: [DVSwitch] Break this "stuff" into sub groups. #poll

 

A new poll has been created:

We have just crossed 200 registered users! Though, most people are just lurking. I'm very happy with GroupsIO but I wonder if it's time to breakup the message traffic into sub groups. I did create a "support" subgroup (Is that even the right word?)
What does everybody think? While I have your attention, PLEASE edit you diosplay name to include your call. 

1. Yes, separate the message traffic by subject.
2. No I don't want to search through subgroups to find what I need.
3. I could not care less.

Vote Now


Re: Break this "stuff" into sub groups. #poll

Peter M0NWI
 

Hi Steve,

Really with the quantity of traffic we get through at the moment, I think its better to just see it all in the one group?

73,
Peter


Break this "stuff" into sub groups. #poll

Steve N4IRS
 

We have just crossed 200 registered users! Though, most people are just lurking. I'm very happy with GroupsIO but I wonder if it's time to breakup the message traffic into sub groups. I did create a "support" subgroup (Is that even the right word?)
What does everybody think? While I have your attention, PLEASE edit you diosplay name to include your call. 

Results

See Who Responded


Re: DVSwitch Status update

Steve N4IRS
 

JP,
The Quantar is a great repeater for analog and P25. The work David and others did to extract the data from the Quantar really helped everybody move thing along with networking Quantars. The thing that bothered us was no support for anything other then a Quantar like repeater. The MMDVM P25 network is continuing to grow. With support for home brew repeaters and hot spots, new people are getting on daily. Are all signals perfect? Heck no! I'm not enough of a purest to worry about that too much.

What we did, was leverage the work P25NX did to extract the P25 frames from the Quantar using the Cisco router. Instead of sending that data via VPN to one of the P25NX reflectors, we package up the P25 frames as a MMDVM would like to see them and send them on to a MMDM P25 reflector. It's quite simple in it's application.  The one thing people need to understand is that this is P25 ONLY. That is not to say Quantar_Bridge could not be connected to one of the other _Bridge programs to connect to a DMR, NXDN, or YSF narrow network. For the best audio quality, we feel either stay P25 or YSF wide, since they are both IMBE and not transcoding is required.

As for the Cisco router, you need support for tunneling the serial data. The STUN data is sent to a connected host where the IMBE is extracted and re-packaged. I won't recreate the great documentation P25NX did on setting up the Quantar and Router but I will post links to the forums where the discussion is happening. BTW, I'm no Cisco expert, I can spell enable... I think we can simplify some of the configuration P25NX does to the Cisco just to make it easier to understand.

73, Steve N4IRS

 

On 4/13/2018 11:27 AM, J P Watters wrote:
Steve N4IRS,

Now you really have my attention. I have a pair of V.24 boards(P25NX version). Where do I find out how to configure things for the "MMDVM P25 Network". The P25NX network configuration seemed complicated to the point of questioning how reliable it would be. 

I will have to look at the version of the dual ethernet cisco router that I have on the scrap heap. It came out of a new fiber node a couple of years ago that was that was installed and decommissioned after a month. 

I have a APX portable that I have to keep handy for the public service side of life. P25 phase 2 rollout that was scheduled for last march, still in the going to roll out mode.  This would allow me to program a configuration for our UHF quantar repeater and link it to DMR talk groups.

WOW, one radio, for work and hobby.  And 0xFE receive for everybody!!!

..jpw
KC9KKO
Morris, IL






Re: DVSwitch Status update

J P Watters <kc9kko@...>
 

Steve N4IRS,

Now you really have my attention. I have a pair of V.24 boards(P25NX version). Where do I find out how to configure things for the "MMDVM P25 Network". The P25NX network configuration seemed complicated to the point of questioning how reliable it would be. 

I will have to look at the version of the dual ethernet cisco router that I have on the scrap heap. It came out of a new fiber node a couple of years ago that was that was installed and decommissioned after a month. 

I have a APX portable that I have to keep handy for the public service side of life. P25 phase 2 rollout that was scheduled for last march, still in the going to roll out mode.  This would allow me to program a configuration for our UHF quantar repeater and link it to DMR talk groups.

WOW, one radio, for work and hobby.  And 0xFE receive for everybody!!!

..jpw
KC9KKO
Morris, IL





Re: DVSwitch Status update

Steve N4IRS
 

OK, that IS interesting. We are using the configuration that is the same as P25NX. A V.24 board and a Cisco router. Quantar_Bridge allow you to use a Quantar P25 native on the MMDVM P25 Network. No MMDVM board required.

Steve N4IRS

On 4/13/2018 11:10 AM, J P Watters wrote:
Steve N4IRS,

That is pretty cool news, since both myself and our local club are using Quantar's.

..jpw


Re: DVSwitch Status update

J P Watters <kc9kko@...>
 

Steve N4IRS,

That is pretty cool news, since both myself and our local club are using Quantar's.

..jpw


Re: HB_Bridge send stream back to master

Steve N4IRS
 

A couple of thoughts, my not be anything.
1: Is the node stanza in rpt.conf set duplex or simplex. Should be set to 0
2: Nope, just 1 thought.

On 4/13/2018 9:12 AM, Matthew 2E0SIP wrote:

Hi Guys,

I've noticed when I use HB_Bridge in conjunction with Analog_Bridge and Asterisk, when HB_Bridge receives a stream from the 'master' for decoding, it also sends the stream back to the master, resulting in these duplicate Last Heard entries.

Is this intentional, a bug, or have a I set something up wrong?



Thanks

Matthew
2E0SIP



HB_Bridge send stream back to master

Matthew 2E0SIP
 

Hi Guys,

I've noticed when I use HB_Bridge in conjunction with Analog_Bridge and Asterisk, when HB_Bridge receives a stream from the 'master' for decoding, it also sends the stream back to the master, resulting in these duplicate Last Heard entries.

Is this intentional, a bug, or have a I set something up wrong?



Thanks

Matthew
2E0SIP


Re: DVSwitch Status update

Steve N4IRS
 

James,
We are a few days away from the alpha release of the new programs MMDVM_Bridge and Quantar_Bridge. We will also release a alpha of Analog_Bridge that you will need to do P25 <---> DMR. We have been testing the P25 bridge on TG 31665 and do not expect any issues.

73, Steve N4IRS

On 4/12/2018 11:47 PM, James Riley kb9tzq wrote:
Just wondering how do I get the dvswitch toolkit I am interested in doing p25<>dmr and nxdn<>dmr


Re: DVSwitch Status update

James Riley kb9tzq
 

Just wondering how do I get the dvswitch toolkit I am interested in doing p25<>dmr and nxdn<>dmr


Re: AMBEtest4.py

Steve N4IRS
 

OK

On 4/12/2018 3:53 PM, Steve Siesel [K4KSA] wrote:

Nevermind…I found the correct command line syntax…..DV3000 is good.

 

Thanks,

Steve

 

 

From: main@DVSwitch.groups.io <main@DVSwitch.groups.io> On Behalf Of Steve Siesel [K4KSA]
Sent: Thursday, April 12, 2018 3:45 PM
To: DVSwitch@groups.io
Subject: [DVSwitch] AMBEtest4.py

 

My DMR<> ASL seems to be down….Upgraded to latest versions from Github, however I think there might be a problem with my AMBE USB vocoder….How long should the python script take to provide results? Its just hanging on “Testing Reset DV3000” ?

 

Steve

 



Re: AMBEtest4.py

Steve N4IRS
 

It should not hang, should report error and end.

On 4/12/2018 3:44 PM, Steve Siesel [K4KSA] wrote:

My DMR<> ASL seems to be down….Upgraded to latest versions from Github, however I think there might be a problem with my AMBE USB vocoder….How long should the python script take to provide results? Its just hanging on “Testing Reset DV3000” ?

 

Steve

 


8941 - 8960 of 9891