Date   

Re: What is an ISPC2 Server?

DO1KBL, Kim
 

Thank you Steve.
Mike is also reading Here?

Von meinem iPhone gesendet

Am 14.12.2021 um 15:01 schrieb Steve N4IRS <szingman@...>:

Randy has accepted the pull request so the change to dmr_utils is now in their repo. We will be updating pypi so that the change are available via pip.


Re: What is an ISPC2 Server?

Steve N4IRS
 

Randy has accepted the pull request so the change to dmr_utils is now in their repo. We will be updating pypi so that the change are available via pip.


Re: #dmrlink Accepting DTMF tones in asterisk to link with allstar nodes #dmrlink

Steve N4IRS
 

On 12/13/21 11:40 PM, Eric KE8GRY wrote:
Hello, I followed the allstar <-> dvswitch setup guide, and have asterisk talking to my radio. Really cool stuff. Now I just need to know how to control it. I desire to setup some DTMF commands to link/unlink with specific allstar nodes.
Here's the dream setup:
DTMF "D" Disconnects me from anything.
DTMF "C" Connects me to a specific allstar node.
DTMF "A" and "B" would be available to trigger something like an audio weather report or just turn on and off parrot mode....
Connections time out after 15 minutes of inactivity.

Current rpt.conf stanza for 1999 is as follows.
[1999]
rxchannel = USRP/127.0.0.1:34001:32001  ; Use the USRP channel driver. Must be enabled in modules.conf
                                        ; 127.0.0.1 = IP of the target application
                                        ; 34001 = UDP port the target application is listening on
                                        ; 32001 = UDP port ASL is listening on

duplex = 0                              ; 0 = Half duplex with no telemetry tones or hang time. Ah, but Allison STILL talks!

hangtime = 0                            ; squelch tail hang time 0
althangtime = 0                         ; longer squelch tail hang time 0

holdofftelem = 1                        ; Hold off all telemetry when signal is present on receiver or from connected nodes
                                        ; except when an ID needs to be done and there is a signal coming from a connected node.

telemdefault = 0                        ; 0 = telemetry output off. Don't send Allison to DMR !!!!!!!!!!!!!!!!! Trust me.

telemdynamic = 0                        ; 0 = disallow users to change the local telemetry setting with a COP command,

linktolink = no                         ; disables forcing physical half-duplex operation of main repeater while
                                        ; still keeping half-duplex semantics (optional)

nounkeyct = 1                           ; Set to a 1 to eliminate courtesy tones and associated delays.

totime = 180000                         ; transmit time-out time (in ms) (optional, default 3 minutes 180000 ms)

idrecording = |ie                       ; id recording or morse string see http://ohnosec.org/drupal/node/87
idtalkover = |ie                        ; Talkover ID (optional) default is none see http://ohnosec.org/drupal/node/129


#dmrlink Accepting DTMF tones in asterisk to link with allstar nodes #dmrlink

Eric KE8GRY
 

Hello, I followed the allstar <-> dvswitch setup guide, and have asterisk talking to my radio. Really cool stuff. Now I just need to know how to control it. I desire to setup some DTMF commands to link/unlink with specific allstar nodes.
Here's the dream setup:
DTMF "D" Disconnects me from anything.
DTMF "C" Connects me to a specific allstar node.
DTMF "A" and "B" would be available to trigger something like an audio weather report or just turn on and off parrot mode....
Connections time out after 15 minutes of inactivity.

Current rpt.conf stanza for 1999 is as follows.
[1999]
rxchannel = USRP/127.0.0.1:34001:32001  ; Use the USRP channel driver. Must be enabled in modules.conf
                                        ; 127.0.0.1 = IP of the target application
                                        ; 34001 = UDP port the target application is listening on
                                        ; 32001 = UDP port ASL is listening on

duplex = 0                              ; 0 = Half duplex with no telemetry tones or hang time. Ah, but Allison STILL talks!

hangtime = 0                            ; squelch tail hang time 0
althangtime = 0                         ; longer squelch tail hang time 0

holdofftelem = 1                        ; Hold off all telemetry when signal is present on receiver or from connected nodes
                                        ; except when an ID needs to be done and there is a signal coming from a connected node.

telemdefault = 0                        ; 0 = telemetry output off. Don't send Allison to DMR !!!!!!!!!!!!!!!!! Trust me.

telemdynamic = 0                        ; 0 = disallow users to change the local telemetry setting with a COP command,

linktolink = no                         ; disables forcing physical half-duplex operation of main repeater while
                                        ; still keeping half-duplex semantics (optional)

nounkeyct = 1                           ; Set to a 1 to eliminate courtesy tones and associated delays.

totime = 180000                         ; transmit time-out time (in ms) (optional, default 3 minutes 180000 ms)

idrecording = |ie                       ; id recording or morse string see http://ohnosec.org/drupal/node/87
idtalkover = |ie                        ; Talkover ID (optional) default is none see http://ohnosec.org/drupal/node/129


Re: What is an ISPC2 Server?

Steve N4IRS
 

I have submitted the pull request to HBLink-org


Re: ircddbgateway to XLX reflector

Patrick Perdue
 

I thought about that, but there is so much stuff linked to module A, and comparatively few D-STAR users that it is probably easier to just move D-STAR to module B and have those few people reprogram their radios.

D-STAR is one of the least popular modes on my system, the least being WIRES x. I have an analog WIRES x bridge connected using a Yaesu HRI-200 interfaced to a private ASL node. Most are using Allstar.

On 12/13/2021 1:28 AM, Tony Langdon wrote:
Yep sounds like a plan.  The main thing is to ensure ircDDBGateway and
xlxd are on different IPs.

One little query though is whether it might not be better to move the
non D-STAR users, since this could possibly be done a bit more
transparently, rather than relying on users to reprogram their radios or
remember to change their destination?

On 13/12/21 2:36 pm, Patrick Perdue wrote:
That is exactly what I plan to do -- move D-STAR users to module B,
and keep all the other digital stuff on module A, then take the XLX
transcoder offline. Ideally, this wouldn't be necessary, but as you
said, there is no PCM stream from XLXD.

I've got plenty of IP's and network interfaces to play with, no big
deal there.


On 12/12/2021 3:47 PM, Tony Langdon wrote:
On 12/12/21 2:24 am, Patrick Perdue wrote:
Hi:

I know this isn't a forum for ircddbgateway, but I am trying to get it
connected to my XLX reflector on module B.

Currently, I have a setup involving XLX with a pair of AMBE dongles,
which I set up before implementing ASL and DVSwitch over two years
ago. This means there is a second layer of transcoding between Allstar
and D-STAR. I want to attach this to an instance of Analog_Bridge, and
thus, Analog_Reflector, to remove this layer of transcoding, and free
up one of my AMBE dongles in the process. However, I'm not familiar
enough with ircddbgateway to really know what I'm doing, and have read
so many forum posts that nothing makes sense anymore.
Unfortunately, the problem here is xlxd itself.  The PCM stream isn't
made available to the outside world.  The ideal solution is to add USRP
support to xlxd, which would allow it to be linked directly to
Analog_Reflector, AllStar, etc.  Of course, you'd still need both AMBE
dongles.  I suspect adding USRP would be a complicated undertaking,
because of how the transcoding is used dynamically between modules as
needed.

While there's a lot to like about xlxd, it can also be a pain to
integrate into more complex networks.

A workaround is to use different modules for D-STAR and DMR/Fusion.
Each with its own instance of Analog_Bridge and MMDVM_Bridge, with
ircDDBGateway linking to the D-STAR module.  Note that you need to use a
different IP for ircDDBGateway and xlxd, because both listen on the same
ports.  I use a variation of this idea for my main multimode reflector.
XLX432 D is the D-STAR reflector.  Fusion (Same codec as DMR) has its
own reflector.



Re: Good morning to all

Steve N4IRS
 

Take a look at HBlink playback.py <https://github.com/HBLink-org/hblink3>  discussion here <https://dvswitch.groups.io/g/HBlink>

On 12/13/2021 9:40 AM, Mike AE4ML wrote:
I hope where I'm posting this is correct. 
how do I build a Parrot of on the  DMR system for local users in our group ? 

There are issues with Parrot on the network and I would like to keep this as a local device.
Possibly just setup a raspberry pi to handle this simple task. I hope. 

Mike AE4ML


Good morning to all

Mike AE4ML
 

I hope where I'm posting this is correct. 
how do I build a Parrot of on the  DMR system for local users in our group ? 

There are issues with Parrot on the network and I would like to keep this as a local device.
Possibly just setup a raspberry pi to handle this simple task. I hope. 

Mike AE4ML


Re: What is an ISPC2 Server?

DO1KBL, Kim
 

thx, for groupcall its very nice tool it work without problems


Re: What is an ISPC2 Server?

Steve N4IRS
 

There may be more work done on IPSC_Bridge and HB_Bridge still to come. I'll do some testing.

Steve

On 12/13/2021 9:15 AM, Kim-Benjamin Lütkemeier via groups.io wrote:
yes Steve
Unit / Private call is the same, I try to find a solution for this

hb_bridge (connected on a hblink3 server) receives corrrectly the Unit call i think it was 0x80 for groupcall and 0x81 for unit-call

but ipsc_bridge will transmit as like a groupcall with unit id.

Other direction IPSC_Bridge to hblink its not programmed in the def private_call its only print('private call') maybe you have some information about the tlv protocol or its small work for mike he can maybe update it?


Re: I'm stumped....

Steve N4IRS
 

David,
I don't think the dashboard takes STFU into account. I'll look into that for the next update.

Steve

On 12/13/2021 9:16 AM, David - W9DWH via groups.io wrote:
Thanks Steve.  It appears I have it working now:

● stfu.service - STFU Service
   Loaded: loaded (/lib/systemd/system/stfu.service; enabled; vendor preset: enabled)
   Active: active (running) since Mon 2021-12-13 08:42:19 EST; 25min ago
  Process: 510 ExecStartPre=/bin/sh -c echo "Starting STFU: [`date +%T.%3N`]" >> /var/log/netcheck (code=exited, status=0/SUCCESS)
 Main PID: 558 (STFU)
    Tasks: 3 (limit: 1150)
   Memory: 952.0K
   CGroup: /system.slice/stfu.service
           └─558 /opt/STFU/STFU /opt/MMDVM_Bridge/DVSwitch.ini
 
Dec 13 08:42:19 dvswitch systemd[1]: Starting STFU Service...
Dec 13 08:42:19 dvswitch systemd[1]: Started STFU Service.

I have STFU set for 3104.repeater.net.  However the DVS dashboard is still showing me as connected to the Mexico master (which I was using previously). Brandmeister is also still showing me on the Mexico master as well (when I look up my hotspot). 


Re: I'm stumped....

David - W9DWH
 

Thanks Steve.  It appears I have it working now:

● stfu.service - STFU Service
   Loaded: loaded (/lib/systemd/system/stfu.service; enabled; vendor preset: enabled)
   Active: active (running) since Mon 2021-12-13 08:42:19 EST; 25min ago
  Process: 510 ExecStartPre=/bin/sh -c echo "Starting STFU: [`date +%T.%3N`]" >> /var/log/netcheck (code=exited, status=0/SUCCESS)
 Main PID: 558 (STFU)
    Tasks: 3 (limit: 1150)
   Memory: 952.0K
   CGroup: /system.slice/stfu.service
           └─558 /opt/STFU/STFU /opt/MMDVM_Bridge/DVSwitch.ini
 
Dec 13 08:42:19 dvswitch systemd[1]: Starting STFU Service...
Dec 13 08:42:19 dvswitch systemd[1]: Started STFU Service.

I have STFU set for 3104.repeater.net.  However the DVS dashboard is still showing me as connected to the Mexico master (which I was using previously). Brandmeister is also still showing me on the Mexico master as well (when I look up my hotspot). 


Re: What is an ISPC2 Server?

DO1KBL, Kim
 

yes Steve
Unit / Private call is the same, I try to find a solution for this

hb_bridge (connected on a hblink3 server) receives corrrectly the Unit call i think it was 0x80 for groupcall and 0x81 for unit-call

but ipsc_bridge will transmit as like a groupcall with unit id.

Other direction IPSC_Bridge to hblink its not programmed in the def private_call its only print('private call') maybe you have some information about the tlv protocol or its small work for mike he can maybe update it?


Re: What is an ISPC2 Server?

Steve N4IRS
 

Is unit call the same as private call? If so, I have not tested it. I will submit a pull request to HBlink soon.

On 12/13/2021 8:59 AM, Kim-Benjamin Lütkemeier via groups.io wrote:
It’s unit call support also working in ipsc_bridge / hb_bridge ?

Where I can find the pull of this fix ?

Von meinem iPhone gesendet

Am 13.12.2021 um 14:28 schrieb Steve N4IRS <szingman@...>:

The issue with dual time slots in a HB_Bridge <-> IPSC_Bridge configuration is fixed. It turns out the changed that needed to be made was in dmr_utils, not a bug in DMRlink or HBlink. Mike N4IRR fixed it over the weekend and I'll submit a pull request to HBlink soon.  


Re: What is an ISPC2 Server?

DO1KBL, Kim
 

It’s unit call support also working in ipsc_bridge / hb_bridge ?

Where I can find the pull of this fix ?

Von meinem iPhone gesendet

Am 13.12.2021 um 14:28 schrieb Steve N4IRS <szingman@...>:

The issue with dual time slots in a HB_Bridge <-> IPSC_Bridge configuration is fixed. It turns out the changed that needed to be made was in dmr_utils, not a bug in DMRlink or HBlink. Mike N4IRR fixed it over the weekend and I'll submit a pull request to HBlink soon.  


Re: What is an ISPC2 Server?

Steve N4IRS
 

The issue with dual time slots in a HB_Bridge <-> IPSC_Bridge configuration is fixed. It turns out the changed that needed to be made was in dmr_utils, not a bug in DMRlink or HBlink. Mike N4IRR fixed it over the weekend and I'll submit a pull request to HBlink soon.  


Re: General support for all things MMDVM

Kevin Halton
 

Don’t forget if sending, send it as friends and family so no fees charged. 


On Dec 13, 2021, at 8:13 AM, Steve N4IRS <szingman@...> wrote:

Jonathan, G4KLX has posted on the OpenDV group a request for support. Without his work on MMDVM related projects, we would all be a LOT worse off. If you were around pre MMDVM days you know basic things were. Here is a link to his post: A little favour to ask..... We encourage everyone using any of the MMDVM based project to consider Jonathans request.


General support for all things MMDVM

Steve N4IRS
 

Jonathan, G4KLX has posted on the OpenDV group a request for support. Without his work on MMDVM related projects, we would all be a LOT worse off. If you were around pre MMDVM days you know basic things were. Here is a link to his post: A little favour to ask..... We encourage everyone using any of the MMDVM based project to consider Jonathans request.


Re: ircddbgateway to XLX reflector

 

Yep sounds like a plan.  The main thing is to ensure ircDDBGateway and
xlxd are on different IPs.

One little query though is whether it might not be better to move the
non D-STAR users, since this could possibly be done a bit more
transparently, rather than relying on users to reprogram their radios or
remember to change their destination?

On 13/12/21 2:36 pm, Patrick Perdue wrote:
That is exactly what I plan to do -- move D-STAR users to module B,
and keep all the other digital stuff on module A, then take the XLX
transcoder offline. Ideally, this wouldn't be necessary, but as you
said, there is no PCM stream from XLXD.

I've got plenty of IP's and network interfaces to play with, no big
deal there.


On 12/12/2021 3:47 PM, Tony Langdon wrote:
On 12/12/21 2:24 am, Patrick Perdue wrote:
Hi:

I know this isn't a forum for ircddbgateway, but I am trying to get it
connected to my XLX reflector on module B.

Currently, I have a setup involving XLX with a pair of AMBE dongles,
which I set up before implementing ASL and DVSwitch over two years
ago. This means there is a second layer of transcoding between Allstar
and D-STAR. I want to attach this to an instance of Analog_Bridge, and
thus, Analog_Reflector, to remove this layer of transcoding, and free
up one of my AMBE dongles in the process. However, I'm not familiar
enough with ircddbgateway to really know what I'm doing, and have read
so many forum posts that nothing makes sense anymore.
Unfortunately, the problem here is xlxd itself.  The PCM stream isn't
made available to the outside world.  The ideal solution is to add USRP
support to xlxd, which would allow it to be linked directly to
Analog_Reflector, AllStar, etc.  Of course, you'd still need both AMBE
dongles.  I suspect adding USRP would be a complicated undertaking,
because of how the transcoding is used dynamically between modules as
needed.

While there's a lot to like about xlxd, it can also be a pain to
integrate into more complex networks.

A workaround is to use different modules for D-STAR and DMR/Fusion.
Each with its own instance of Analog_Bridge and MMDVM_Bridge, with
ircDDBGateway linking to the D-STAR module.  Note that you need to use a
different IP for ircDDBGateway and xlxd, because both listen on the same
ports.  I use a variation of this idea for my main multimode reflector.
XLX432 D is the D-STAR reflector.  Fusion (Same codec as DMR) has its
own reflector.



--
73 de Tony VK3JED/VK3IRL
http://vkradio.com


Re: ircddbgateway to XLX reflector

Patrick Perdue
 

That is exactly what I plan to do -- move D-STAR users to module B, and keep all the other digital stuff on module A, then take the XLX transcoder offline. Ideally, this wouldn't be necessary, but as you said, there is no PCM stream from XLXD.

I've got plenty of IP's and network interfaces to play with, no big deal there.

On 12/12/2021 3:47 PM, Tony Langdon wrote:
On 12/12/21 2:24 am, Patrick Perdue wrote:
Hi:

I know this isn't a forum for ircddbgateway, but I am trying to get it
connected to my XLX reflector on module B.

Currently, I have a setup involving XLX with a pair of AMBE dongles,
which I set up before implementing ASL and DVSwitch over two years
ago. This means there is a second layer of transcoding between Allstar
and D-STAR. I want to attach this to an instance of Analog_Bridge, and
thus, Analog_Reflector, to remove this layer of transcoding, and free
up one of my AMBE dongles in the process. However, I'm not familiar
enough with ircddbgateway to really know what I'm doing, and have read
so many forum posts that nothing makes sense anymore.
Unfortunately, the problem here is xlxd itself.  The PCM stream isn't
made available to the outside world.  The ideal solution is to add USRP
support to xlxd, which would allow it to be linked directly to
Analog_Reflector, AllStar, etc.  Of course, you'd still need both AMBE
dongles.  I suspect adding USRP would be a complicated undertaking,
because of how the transcoding is used dynamically between modules as
needed.

While there's a lot to like about xlxd, it can also be a pain to
integrate into more complex networks.

A workaround is to use different modules for D-STAR and DMR/Fusion.
Each with its own instance of Analog_Bridge and MMDVM_Bridge, with
ircDDBGateway linking to the D-STAR module.  Note that you need to use a
different IP for ircDDBGateway and xlxd, because both listen on the same
ports.  I use a variation of this idea for my main multimode reflector.
XLX432 D is the D-STAR reflector.  Fusion (Same codec as DMR) has its
own reflector.

121 - 140 of 10078