Date   

Re: WA3XYZ PL 88.5 Announcement #analog_bridge #mmdvm_bridge

Patrick Perdue
 

And I can tell you from experience, having done it on four different bridges, that it doesn't do anything at all if idrecording and idtalkover aren't defined.

I originally used your example because I thought it would do that as well, but after being annoyed by a dit coming across USRP, holding things up on a pretty busy talkgroup every time it happened, I just commented those lines out, and it went away with no consequence.


On 12/27/2020 2:39 PM, Steve N4IRS wrote:
I disagree, I'll check it again. I believe if app_rpt does not find the entry it will default to ID.

On 12/27/20 2:36 PM, Patrick Perdue wrote:

No, it definitely won't even try to send an ID if that line is commented out, so there's really no point in having it there in the first place on a USRP bridge.


On 12/27/2020 2:34 PM, Steve N4IRS wrote:

I think it will send "ID" if you comment it out.

On 12/27/20 2:33 PM, Patrick Perdue wrote:

Just comment the line out entirely. It isn't needed. Not even a dit.


On 12/27/2020 2:28 PM, Steve N4IRS wrote:
totime = 180000 ; transmit time-out time (in ms) (default 3 min 180000 ms)
idrecording = |ie ; id recording or morse string
idtalkover = |ie ; Talkover ID (optional) default is none

It's going to send a ID to USRP. So, make it a E (dit)



Re: WA3XYZ PL 88.5 Announcement #analog_bridge #mmdvm_bridge

Frank C. D'Amato
 

which rpt.conf?

on the dvswitch or hamvoip?

In the ect/asterick directory?


Re: WA3XYZ PL 88.5 Announcement #analog_bridge #mmdvm_bridge

Steve N4IRS
 

I disagree, I'll check it again. I believe if app_rpt does not find the entry it will default to ID.

On 12/27/20 2:36 PM, Patrick Perdue wrote:

No, it definitely won't even try to send an ID if that line is commented out, so there's really no point in having it there in the first place on a USRP bridge.


On 12/27/2020 2:34 PM, Steve N4IRS wrote:

I think it will send "ID" if you comment it out.

On 12/27/20 2:33 PM, Patrick Perdue wrote:

Just comment the line out entirely. It isn't needed. Not even a dit.


On 12/27/2020 2:28 PM, Steve N4IRS wrote:
totime = 180000 ; transmit time-out time (in ms) (default 3 min 180000 ms)
idrecording = |ie ; id recording or morse string
idtalkover = |ie ; Talkover ID (optional) default is none

It's going to send a ID to USRP. So, make it a E (dit)



Re: WA3XYZ PL 88.5 Announcement #analog_bridge #mmdvm_bridge

Patrick Perdue
 

No, it definitely won't even try to send an ID if that line is commented out, so there's really no point in having it there in the first place on a USRP bridge.


On 12/27/2020 2:34 PM, Steve N4IRS wrote:

I think it will send "ID" if you comment it out.

On 12/27/20 2:33 PM, Patrick Perdue wrote:

Just comment the line out entirely. It isn't needed. Not even a dit.


On 12/27/2020 2:28 PM, Steve N4IRS wrote:
totime = 180000 ; transmit time-out time (in ms) (default 3 min 180000 ms)
idrecording = |ie ; id recording or morse string
idtalkover = |ie ; Talkover ID (optional) default is none

It's going to send a ID to USRP. So, make it a E (dit)


Re: WA3XYZ PL 88.5 Announcement #analog_bridge #mmdvm_bridge

Steve N4IRS
 

On 12/27/20 2:33 PM, Patrick Perdue wrote:

Just comment the line out entirely. It isn't needed. Not even a dit.


On 12/27/2020 2:28 PM, Steve N4IRS wrote:
totime = 180000 ; transmit time-out time (in ms) (default 3 min 180000 ms)
idrecording = |ie ; id recording or morse string
idtalkover = |ie ; Talkover ID (optional) default is none

It's going to send a ID to USRP. So, make it a E (dit)


Re: WA3XYZ PL 88.5 Announcement #analog_bridge #mmdvm_bridge

Steve N4IRS
 

I think it will send "ID" if you comment it out.

On 12/27/20 2:33 PM, Patrick Perdue wrote:

Just comment the line out entirely. It isn't needed. Not even a dit.


On 12/27/2020 2:28 PM, Steve N4IRS wrote:
totime = 180000 ; transmit time-out time (in ms) (default 3 min 180000 ms)
idrecording = |ie ; id recording or morse string
idtalkover = |ie ; Talkover ID (optional) default is none

It's going to send a ID to USRP. So, make it a E (dit)


Re: WA3XYZ PL 88.5 Announcement #analog_bridge #mmdvm_bridge

Patrick Perdue
 

Just comment the line out entirely. It isn't needed. Not even a dit.


On 12/27/2020 2:28 PM, Steve N4IRS wrote:
totime = 180000 ; transmit time-out time (in ms) (default 3 min 180000 ms)
idrecording = |ie ; id recording or morse string
idtalkover = |ie ; Talkover ID (optional) default is none

It's going to send a ID to USRP. So, make it a E (dit)


Re: WA3XYZ PL 88.5 Announcement #analog_bridge #mmdvm_bridge

Patrick Perdue
 

Make sure the lines starting with idrecording and idtalkover are either commented out or don't exist in /etc/asterisk/rpt.conf under the stanza for the node where your DMR bridge lives. You may also want to make sure duplex=0 and telemdefault=0, unless you have a special case, as I do.


On 12/27/2020 2:23 PM, Mike KB8JNM wrote:

Check your radio programming for the channel

On 12/27/2020 2:17 PM, Frank C. D'Amato wrote:
I finally got the DVswitch up and running.  The Analog to dmr link is working fine.

The only issue I have, is every 10 minutes, this ID is played ONLY on the DMR TG (Not the analog side)
Anyone know where this ID is living?  I ; out all the ID's in analog_bridge.ini

Video of the ID Going Off


Re: WA3XYZ PL 88.5 Announcement #analog_bridge #mmdvm_bridge

Steve N4IRS
 

totime = 180000 ; transmit time-out time (in ms) (default 3 min 180000 ms)
idrecording = |ie ; id recording or morse string
idtalkover = |ie ; Talkover ID (optional) default is none

It's going to send a ID to USRP. So, make it a E (dit)


Re: WA3XYZ PL 88.5 Announcement #analog_bridge #mmdvm_bridge

Mike KB8JNM
 

Check your radio programming for the channel

On 12/27/2020 2:17 PM, Frank C. D'Amato wrote:
I finally got the DVswitch up and running.  The Analog to dmr link is working fine.

The only issue I have, is every 10 minutes, this ID is played ONLY on the DMR TG (Not the analog side)
Anyone know where this ID is living?  I ; out all the ID's in analog_bridge.ini

Video of the ID Going Off


Re: DVSwitch running on 2nd Raspberry Pi

Frank C. D'Amato
 

I decided i'm not gonna run the pyUC


WA3XYZ PL 88.5 Announcement #analog_bridge #mmdvm_bridge

Frank C. D'Amato
 

I finally got the DVswitch up and running.  The Analog to dmr link is working fine.

The only issue I have, is every 10 minutes, this ID is played ONLY on the DMR TG (Not the analog side)
Anyone know where this ID is living?  I ; out all the ID's in analog_bridge.ini

Video of the ID Going Off


Restarting DVSwitch Services

g8ptn@...
 

Hi,

I have noticed that when restarting services via the "dvs" menu “Restart DVSwitch Services” or using the “Drop Dynamic TGs” in the DVSM App, the DMR server always returns to a particular server.


When restarting DVSwitch services, what determines what DMR server is selected?

Regards,
   Dave


Re: Brandmeister TG to XLX Bridge ini files #brandmeister 'mmdvm #brandmeister

Dave M0UPM
 

Corey, I have messaged him as much in a private mail. Dave M0UPM BM UK Admin 


On 26 Dec 2020, at 22:31, Corey Dean N3FE <n3fe@...> wrote:

Brandmeister prefers you to directly work with the master and do a true xlx connection as it uses the xlx protocol directly.


On Dec 26, 2020, at 2:06 PM, craig.jump via groups.io <craig.jump@...> wrote:

These are my ini files for a Brandmeister TG to XLX bridge

BM TG <> MMDVM_Bridge <> MMDVM_Bridge <> XLX (DMR Mode)

Had one way audio for a while and was tearing my hair out.. (now have none left :-) )

These might save someone some time..     problem was the DVSwitch ini file where I had to define the TG..  otherwise one way audio..

Remember and setup a static TG on the BM self service page and set your password accordingly.

Craig
2M0JUM
<MMDVM_BM_BRIDGEtoXLX.zip>


Re: Brandmeister TG to XLX Bridge ini files #brandmeister 'mmdvm #brandmeister

Corey Dean N3FE
 

Brandmeister prefers you to directly work with the master and do a true xlx connection as it uses the xlx protocol directly.


On Dec 26, 2020, at 2:06 PM, craig.jump via groups.io <craig.jump@...> wrote:

These are my ini files for a Brandmeister TG to XLX bridge

BM TG <> MMDVM_Bridge <> MMDVM_Bridge <> XLX (DMR Mode)

Had one way audio for a while and was tearing my hair out.. (now have none left :-) )

These might save someone some time..     problem was the DVSwitch ini file where I had to define the TG..  otherwise one way audio..

Remember and setup a static TG on the BM self service page and set your password accordingly.

Craig
2M0JUM
<MMDVM_BM_BRIDGEtoXLX.zip>


Brandmeister TG to XLX Bridge ini files #brandmeister 'mmdvm #brandmeister

craig.jump@...
 

These are my ini files for a Brandmeister TG to XLX bridge

BM TG <> MMDVM_Bridge <> MMDVM_Bridge <> XLX (DMR Mode)

Had one way audio for a while and was tearing my hair out.. (now have none left :-) )

These might save someone some time..     problem was the DVSwitch ini file where I had to define the TG..  otherwise one way audio..

Remember and setup a static TG on the BM self service page and set your password accordingly.

Craig
2M0JUM


Re: DVSwitch running on 2nd Raspberry Pi

Ken Kayser
 

Frank.  Anytime you try and execute a command from the current directory, you must proceed it with a ./ so you should enter ./pyUC.py    Also, Python may not be in your path.  Try python3 pyUC.py.  Let us know what happens


Re: DVSM APP server pool

Ralf, DC9NYC
 

I am sorry - the IP address is: ...

87.191.190.207, Port 50111
87.191.190.207, Port 50112
87.191.190.207, Port 50113

Ralf, DC9NYC


Re: #hblink is throwing out many " DMR Slot 2, overflow in the DMR slot RF queue" #hblink

fabiobassa
 

Sure Steve I will post there too and ty again for wonderfull work done on those digital systems

73 ' s


Re: #hblink is throwing out many " DMR Slot 2, overflow in the DMR slot RF queue" #hblink

Steve N4IRS
 

I suggest you post this information in the HBlink subgroup <https://dvswitch.groups.io/g/HBlink> Where more HBlink users will see it.

Steve N4IRS

On 12/26/20 6:45 AM, fabiobassa wrote:

Hello Bob, thank you for kind replay.

unfortunately Parrot documentation on hblink3 is fragmented , a piece here, a piece there so a bit unconfortable to follow the puzzle

On my radio of course the parrot is a group call and I can engage the parrot, what is frustrating  WAS the wrong audio coming back

I  found another polish man talking about parrot  on hblink3 and he says that first is necessary start the parrot service itself , otherwise no parrot service on board

So it ise necessary have a parrot.service or start by hand calling

/usr/bin/python3 /srv/HBlink3-main/HBlink3/playback.py  -c /srv/HBlink3-main/HBlink3/playback.cfg

that is my relative path.

Following the guidance to have a parrot.service , in facts,  now the parrot is working succesfully

Was just the lack of a service

thanks again , 73's Marco IZ8XOH


1541 - 1560 of 9503