Date   
Re: Jackhammer Sound

 

I got the jack hammer effect after my computer froze. Would not go away.
sudo apt-get --purge  remove md380-emu then install new copy fixed my problem.

Re: Jackhammer Sound

Steve N4IRS
 

Ernie,
Once the computer froze, did you restart the computer and test before purging and reinstalling md380-emu?

Steve

On 9/10/19 3:12 AM, Ernie Gm7kbk wrote:
I got the jack hammer effect after my computer froze. Would not go away.
sudo apt-get --purge  remove md380-emu then install new copy fixed my problem.

Re: Jackhammer Sound

 

The effect started on reboot of computer. Did a fresh install of the emulator still had the same problem. Found the purge command on google. Worked ever since.


From: main@DVSwitch.groups.io <main@DVSwitch.groups.io> on behalf of Steve N4IRS <szingman@...>
Sent: Tuesday, September 10, 2019 10:35:34 AM
To: main@DVSwitch.groups.io <main@DVSwitch.groups.io>
Subject: Re: [DVSwitch] Jackhammer Sound
 
Ernie,
Once the computer froze, did you restart the computer and test before purging and reinstalling md380-emu?

Steve

On 9/10/19 3:12 AM, Ernie Gm7kbk wrote:
I got the jack hammer effect after my computer froze. Would not go away.
sudo apt-get --purge  remove md380-emu then install new copy fixed my problem.

Tune audio levels in DStar gateway #analog_bridge

Waldek SP2ONG
 
Edited

Hi,

I would like to set the correct audio levels in my DStar gateway, where I use ircddbgateway / MMDVM_Bridge and 2 Ananlog_Bidges connected via USRP

A simple AB connection diagram is below
 
AB DMR                                                    AB DStar
[USRP]                                                       [USRP]
RX   <--------------------------------------------- TX
TX    ---------------------------------------------> RX
aslAudio = AUDIO_USE_GAIN                    aslAudio = AUDIO_USE_GAIN
dmrAudio = AUDIO_USE_GAIN                  dmrAudio = AUDIO_USE_GAIN
agcGain = 10                                              agcGain = 10
dmrGain = 0.35                                           dmrGain = 0.35

I would like to be sure that when I set the audio levels from DSTAR to DMR I need to correct it:

Tune in USRP_DSTAR agcGain  and dmrGain in USRP_DMR    ????


when I set the audio levels from DMR to DSTAR:

Tune  in USRP_DMR agcGain and dmrGain in USRP_DSTAR     ???

I would like to suggest whether it is correct or how to choose the right levels in both directions

73 Waldek SP2ONG

Re: Tune audio levels in DStar gateway #analog_bridge

Steve N4IRS
 

Set one Analog_Bridge to unity in both directions and use the other Analog_Bridge to set levels in and out.

Sent via smoke signal (AT&T)


From: main@DVSwitch.groups.io <main@DVSwitch.groups.io> on behalf of Waldek SP2ONG <sp2ong@...>
Sent: Tuesday, September 10, 2019 7:02:31 AM
To: main@DVSwitch.groups.io <main@DVSwitch.groups.io>
Subject: [DVSwitch] Tune audio levels in DStar gateway #analog_bridge
 

[Edited Message Follows]

Hi,

I would like to set the correct audio levels in my DStar gateway, where I use ircddbgateway / MMDVM_Bridge and 2 Ananlog_Bidges connected via USRP

A simple AB connection diagram is below
 
AB DMR                                                    AB DStar
[USRP]                                                       [USRP]
RX   <--------------------------------------------- TX
TX    ---------------------------------------------> RX
aslAudio = AUDIO_USE_GAIN                    aslAudio = AUDIO_USE_GAIN
dmrAudio = AUDIO_USE_GAIN                  dmrAudio = AUDIO_USE_GAIN
agcGain = 10                                              agcGain = 10
dmrGain = 0.35                                           dmrGain = 0.35

I would like to be sure that when I set the audio levels from DSTAR to DMR I need to correct it:

Tune in USRP_DSTAR agcGain  and dmrGain in USRP_DMR    ????


when I set the audio levels from DMR to DSTAR:

Tune  in USRP_DMR agcGain and dmrGain in USRP_DSTAR     ???

I would like to suggest whether it is correct or how to choose the right levels in both directions

73 Waldek SP2ONG

Re: Tune audio levels in DStar gateway #analog_bridge

Waldek SP2ONG
 

Steve,

Thank you, set in the first AB

aslAudio = AUDIO_UNITY                   
dmrAudio = AUDIO_UNITY

and try to tune in the second AB

aslAudio = AUDIO_USE_GAIN                 
dmrAudio = AUDIO_USE_GAIN


and adjust agcGain and dmrGain

One question about a scalar, if I would like to use AUDIO_USE_GAIN, it is only a multiplier, for example agcGain = 2, this is 2 times the level
but if I would like to use AUDIO_USE_AGC, the agcGain scalar will be in dB?

Waldek


Re: Tune audio levels in DStar gateway #analog_bridge

Mike Zingman - N4IRR
 

For transcoding, I would never use AGC.  Only use linear gain (AUDIO_USE_GAIN) for best results.

Re: Tune audio levels in DStar gateway #analog_bridge

Waldek SP2ONG
 

Mike

Thank you for sharing your experience
and I can confirm your suggestion after the trials I did with linear gain and AGC

Waldek

Re: Can I bulild an offline dmr server?

Ben Fogt
 

This might not be the best place for the following response, but you can quickly and easily spin up an XLX server, and use the "DMR gateway" feature in pi-star to connect to it. The pi-star devices just need their host files updated to reflect the IP of the XLX server. This is the quickest and easiest way to spin up a private DMR server, i think.

On Sat, Sep 7, 2019 at 7:07 PM playexata <ayhantar21@...> wrote:
We have a system was builed  with internet but our internet provider go for a system renewal now we need to work with out internet for 3-5 months. we want to use our dmr radios (which is connected to mmdvm hotsposts) to comminicite. Currently we have  a server runs in office and long range wifi antenas all around mountains.

Questation : Can I build an offline dmr server? which has talk groups or at least some sorth of groups in to the server ?



--
Ben Fogt
N5AMD

Image for Raspberry pi3 with Debian 10 Buster with DVSWICTH SERVER, HBLINK3 AND HBMONITOR.

EA5GVK Joaquin
 

Good morning, I have made an image for raspberry that contains guided menu script to configure dvswitch server and I have also set up an hblink3 server and its hbmonitor.
The news link is this -> http://ea5gvk-dmr.zigor.es
And the link to download the image is this -> https://mega.nz/#!z4wXxKBK!O9BVLKzWXX88yJ7ODAhqCIYBNkgz4-p8fNkkAC2Y6Wk

Thanks to the entire Dvswitch team. Always grateful

Re: Image for Raspberry pi3 with Debian 10 Buster with DVSWICTH SERVER, HBLINK3 AND HBMONITOR.

D B
 

Image link may be bad? Please check.

 

 

 

From: main@DVSwitch.groups.io <main@DVSwitch.groups.io> On Behalf Of EA5GVK Joaquin
Sent: Thursday, September 12, 2019 1:18 AM
To: main@DVSwitch.groups.io
Subject: [DVSwitch] Image for Raspberry pi3 with Debian 10 Buster with DVSWICTH SERVER, HBLINK3 AND HBMONITOR.

 

Good morning, I have made an image for raspberry that contains guided menu script to configure dvswitch server and I have also set up an hblink3 server and its hbmonitor.
The news link is this -> http://ea5gvk-dmr.zigor.es
And the link to download the image is this -> https://mega.nz/#!z4wXxKBK!O9BVLKzWXX88yJ7ODAhqCIYBNkgz4-p8fNkkAC2Y6Wk

Thanks to the entire Dvswitch team. Always grateful

Re: Image for Raspberry pi3 with Debian 10 Buster with DVSWICTH SERVER, HBLINK3 AND HBMONITOR.

EA5GVK Joaquin
 

Yes, I checked and Perfect link
imagen.png

El jue., 12 sept. 2019 a las 19:37, D B (<ou812@...>) escribió:

Image link may be bad? Please check.

 

 

 

From: main@DVSwitch.groups.io <main@DVSwitch.groups.io> On Behalf Of EA5GVK Joaquin
Sent: Thursday, September 12, 2019 1:18 AM
To: main@DVSwitch.groups.io
Subject: [DVSwitch] Image for Raspberry pi3 with Debian 10 Buster with DVSWICTH SERVER, HBLINK3 AND HBMONITOR.

 

Good morning, I have made an image for raspberry that contains guided menu script to configure dvswitch server and I have also set up an hblink3 server and its hbmonitor.
The news link is this -> http://ea5gvk-dmr.zigor.es
And the link to download the image is this -> https://mega.nz/#!z4wXxKBK!O9BVLKzWXX88yJ7ODAhqCIYBNkgz4-p8fNkkAC2Y6Wk

Thanks to the entire Dvswitch team. Always grateful

Re: Image for Raspberry pi3 with Debian 10 Buster with DVSWICTH SERVER, HBLINK3 AND HBMONITOR.

Brad N8PC
 

Works for me


On Thu, Sep 12, 2019, 4:14 PM EA5GVK Joaquin <ea5gvk@...> wrote:
Yes, I checked and Perfect link
imagen.png

El jue., 12 sept. 2019 a las 19:37, D B (<ou812@...>) escribió:

Image link may be bad? Please check.

 

 

 

From: main@DVSwitch.groups.io <main@DVSwitch.groups.io> On Behalf Of EA5GVK Joaquin
Sent: Thursday, September 12, 2019 1:18 AM
To: main@DVSwitch.groups.io
Subject: [DVSwitch] Image for Raspberry pi3 with Debian 10 Buster with DVSWICTH SERVER, HBLINK3 AND HBMONITOR.

 

Good morning, I have made an image for raspberry that contains guided menu script to configure dvswitch server and I have also set up an hblink3 server and its hbmonitor.
The news link is this -> http://ea5gvk-dmr.zigor.es
And the link to download the image is this -> https://mega.nz/#!z4wXxKBK!O9BVLKzWXX88yJ7ODAhqCIYBNkgz4-p8fNkkAC2Y6Wk

Thanks to the entire Dvswitch team. Always grateful

Re: Image for Raspberry pi3 with Debian 10 Buster with DVSWICTH SERVER, HBLINK3 AND HBMONITOR.

D B
 

Thanks it didn’t like the IE browser I’m too old school.

Thanks

 

From: main@DVSwitch.groups.io <main@DVSwitch.groups.io> On Behalf Of Brad N8PC
Sent: Thursday, September 12, 2019 2:21 PM
To: main@dvswitch.groups.io
Subject: Re: [DVSwitch] Image for Raspberry pi3 with Debian 10 Buster with DVSWICTH SERVER, HBLINK3 AND HBMONITOR.

 

Works for me

 

On Thu, Sep 12, 2019, 4:14 PM EA5GVK Joaquin <ea5gvk@...> wrote:

Yes, I checked and Perfect link

imagen.png

 

El jue., 12 sept. 2019 a las 19:37, D B (<ou812@...>) escribió:

Image link may be bad? Please check.

 

 

 

From: main@DVSwitch.groups.io <main@DVSwitch.groups.io> On Behalf Of EA5GVK Joaquin
Sent: Thursday, September 12, 2019 1:18 AM
To: main@DVSwitch.groups.io
Subject: [DVSwitch] Image for Raspberry pi3 with Debian 10 Buster with DVSWICTH SERVER, HBLINK3 AND HBMONITOR.

 

Good morning, I have made an image for raspberry that contains guided menu script to configure dvswitch server and I have also set up an hblink3 server and its hbmonitor.
The news link is this -> http://ea5gvk-dmr.zigor.es
And the link to download the image is this -> https://mega.nz/#!z4wXxKBK!O9BVLKzWXX88yJ7ODAhqCIYBNkgz4-p8fNkkAC2Y6Wk

Thanks to the entire Dvswitch team. Always grateful

DMR to Analog Bridge PTT assert quirk

David Ranch
 

Hello Everyone,

I have a working Brandmeister talk group to Analog Bridge setup working here but I see a PTT quirk that I'm curious if someone can comment on. 


If I key up the local DMR repeater that's in the Brandmeister talk group, this Raspberry Pi 3B+ setup using a URI-X sound card will light up the PTT LED on the URIX but then go off, then light back up and stay lit.  Beyond that, everything works as it should.  I see this behavior regardless if I use the SW IMBE vocoder or if I use a NW Digital THumbDV.  

Any thoughts on how to fix this "ACTIVE_FLAP" issue?

I've also attached a 7.7MB video of this behavior though I don't know if the Groups.IO system will accept it.  Let's see.

--David
KI6ZHD



Asterisk output with "rpt debug level 6"
--
*CLI> [Sep 14 12:25:16] NOTICE[5335]: app_rpt.c:19522 rpt: **** rx key
[Sep 14 12:25:16] NOTICE[5335]: app_rpt.c:17370 cos_state_machine: **** cos_state_machine: COS_SM_CLEAR, event=COS_ACTIVE, new state = COS_SM_ACTIVE, return_cos_value=2
[Sep 14 12:25:16] NOTICE[5335]: app_rpt.c:19532 rpt: **** rx key
[Sep 14 12:25:16] NOTICE[5333]: app_rpt.c:3502 __mklinklist: Last = 1999, K
[Sep 14 12:25:16] NOTICE[5335]: app_rpt.c:19645 rpt: **** rx unkey
[Sep 14 12:25:16] NOTICE[5335]: app_rpt.c:17387 cos_state_machine: **** cos_state_machine: COS_SM_ACTIVE, event=COS_INACTIVE, new state = COS_SM_ACTIVE_FLAP, return_cos_value=2
[Sep 14 12:25:16] NOTICE[5335]: app_rpt.c:17406 cos_state_machine: **** cos_state_machine: COS_SM_ACTIVE_FLAP, event=COS_TIMER, new state = COS_SM_CLEAR, return_cos_value=5
[Sep 14 12:25:16] NOTICE[5335]: app_rpt.c:17467 cos_state_unkey: **** cos state unkey
[Sep 14 12:25:16] NOTICE[5335]: app_rpt.c:17473 cos_state_unkey: **** rx un-key
[Sep 14 12:25:17] NOTICE[5335]: app_rpt.c:19522 rpt: **** rx key
[Sep 14 12:25:17] NOTICE[5335]: app_rpt.c:17370 cos_state_machine: **** cos_state_machine: COS_SM_CLEAR, event=COS_ACTIVE, new state = COS_SM_ACTIVE, return_cos_value=2
[Sep 14 12:25:17] NOTICE[5335]: app_rpt.c:19532 rpt: **** rx key
[Sep 14 12:25:17] NOTICE[5333]: app_rpt.c:3502 __mklinklist: Last = 1999, K
[Sep 14 12:25:17] NOTICE[5335]: app_rpt.c:19645 rpt: **** rx unkey
[Sep 14 12:25:17] NOTICE[5335]: app_rpt.c:17387 cos_state_machine: **** cos_state_machine: COS_SM_ACTIVE, event=COS_INACTIVE, new state = COS_SM_ACTIVE_FLAP, return_cos_value=2
[Sep 14 12:25:17] NOTICE[5335]: app_rpt.c:17406 cos_state_machine: **** cos_state_machine: COS_SM_ACTIVE_FLAP, event=COS_TIMER, new state = COS_SM_CLEAR, return_cos_value=5
[Sep 14 12:25:17] NOTICE[5335]: app_rpt.c:17467 cos_state_unkey: **** cos state unkey
[Sep 14 12:25:17] NOTICE[5335]: app_rpt.c:17473 cos_state_unkey: **** rx un-key
[Sep 14 12:25:17] NOTICE[5335]: app_rpt.c:19522 rpt: **** rx key
[Sep 14 12:25:17] NOTICE[5335]: app_rpt.c:17370 cos_state_machine: **** cos_state_machine: COS_SM_CLEAR, event=COS_ACTIVE, new state = COS_SM_ACTIVE, return_cos_value=2
[Sep 14 12:25:17] NOTICE[5335]: app_rpt.c:19532 rpt: **** rx key
[Sep 14 12:25:17] NOTICE[5333]: app_rpt.c:3502 __mklinklist: Last = 1999, K
[Sep 14 12:25:18] NOTICE[5335]: app_rpt.c:19645 rpt: **** rx unkey
[Sep 14 12:25:18] NOTICE[5335]: app_rpt.c:17387 cos_state_machine: **** cos_state_machine: COS_SM_ACTIVE, event=COS_INACTIVE, new state = COS_SM_ACTIVE_FLAP, return_cos_value=2
[Sep 14 12:25:18] NOTICE[5335]: app_rpt.c:17406 cos_state_machine: **** cos_state_machine: COS_SM_ACTIVE_FLAP, event=COS_TIMER, new state = COS_SM_CLEAR, return_cos_value=5
[Sep 14 12:25:18] NOTICE[5335]: app_rpt.c:17467 cos_state_unkey: **** cos state unkey
[Sep 14 12:25:18] NOTICE[5335]: app_rpt.c:17473 cos_state_unkey: **** rx un-key
--


MMDVM STDOUT output
--
M: 2019-09-14 19:25:16.498 DMR Slot 2, received network voice header from KI6ZHD to TG WB5WXI
M: 2019-09-14 19:25:17.262 DMR Talker Alias (Data Format 1, Received 6/23 char): 'KI6ZHD'
D: 2019-09-14 19:25:17.789 DMR Slot 2, lost audio for 409ms filling in
M: 2019-09-14 19:25:17.980 DMR Talker Alias (Data Format 1, Received 13/23 char): 'KI6ZHD KI6ZHD'
M: 2019-09-14 19:25:18.461 DMR Slot 2, received network end of voice transmission, 2.3 seconds, 15% packet loss, BER: 0.0%
--


Analog_bridge STDOUT output:
--
[ Nothing shown after it starts up successfully ]
--

Re: DMR to Analog Bridge PTT assert quirk

Steve N4IRS
 

David,
It might be interesting to see you log when the issue happens. I am talking about a snip of the ASL, AB, MB logs at the point in time when the issue happens.

On 9/14/19 3:32 PM, David Ranch wrote:
Hello Everyone,

I have a working Brandmeister talk group to Analog Bridge setup working here but I see a PTT quirk that I'm curious if someone can comment on. 


If I key up the local DMR repeater that's in the Brandmeister talk group, this Raspberry Pi 3B+ setup using a URI-X sound card will light up the PTT LED on the URIX but then go off, then light back up and stay lit.  Beyond that, everything works as it should.  I see this behavior regardless if I use the SW IMBE vocoder or if I use a NW Digital THumbDV.  

Any thoughts on how to fix this "ACTIVE_FLAP" issue?

I've also attached a 7.7MB video of this behavior though I don't know if the Groups.IO system will accept it.  Let's see.

--David
KI6ZHD



Asterisk output with "rpt debug level 6"
--
*CLI> [Sep 14 12:25:16] NOTICE[5335]: app_rpt.c:19522 rpt: **** rx key
[Sep 14 12:25:16] NOTICE[5335]: app_rpt.c:17370 cos_state_machine: **** cos_state_machine: COS_SM_CLEAR, event=COS_ACTIVE, new state = COS_SM_ACTIVE, return_cos_value=2
[Sep 14 12:25:16] NOTICE[5335]: app_rpt.c:19532 rpt: **** rx key
[Sep 14 12:25:16] NOTICE[5333]: app_rpt.c:3502 __mklinklist: Last = 1999, K
[Sep 14 12:25:16] NOTICE[5335]: app_rpt.c:19645 rpt: **** rx unkey
[Sep 14 12:25:16] NOTICE[5335]: app_rpt.c:17387 cos_state_machine: **** cos_state_machine: COS_SM_ACTIVE, event=COS_INACTIVE, new state = COS_SM_ACTIVE_FLAP, return_cos_value=2
[Sep 14 12:25:16] NOTICE[5335]: app_rpt.c:17406 cos_state_machine: **** cos_state_machine: COS_SM_ACTIVE_FLAP, event=COS_TIMER, new state = COS_SM_CLEAR, return_cos_value=5
[Sep 14 12:25:16] NOTICE[5335]: app_rpt.c:17467 cos_state_unkey: **** cos state unkey
[Sep 14 12:25:16] NOTICE[5335]: app_rpt.c:17473 cos_state_unkey: **** rx un-key
[Sep 14 12:25:17] NOTICE[5335]: app_rpt.c:19522 rpt: **** rx key
[Sep 14 12:25:17] NOTICE[5335]: app_rpt.c:17370 cos_state_machine: **** cos_state_machine: COS_SM_CLEAR, event=COS_ACTIVE, new state = COS_SM_ACTIVE, return_cos_value=2
[Sep 14 12:25:17] NOTICE[5335]: app_rpt.c:19532 rpt: **** rx key
[Sep 14 12:25:17] NOTICE[5333]: app_rpt.c:3502 __mklinklist: Last = 1999, K
[Sep 14 12:25:17] NOTICE[5335]: app_rpt.c:19645 rpt: **** rx unkey
[Sep 14 12:25:17] NOTICE[5335]: app_rpt.c:17387 cos_state_machine: **** cos_state_machine: COS_SM_ACTIVE, event=COS_INACTIVE, new state = COS_SM_ACTIVE_FLAP, return_cos_value=2
[Sep 14 12:25:17] NOTICE[5335]: app_rpt.c:17406 cos_state_machine: **** cos_state_machine: COS_SM_ACTIVE_FLAP, event=COS_TIMER, new state = COS_SM_CLEAR, return_cos_value=5
[Sep 14 12:25:17] NOTICE[5335]: app_rpt.c:17467 cos_state_unkey: **** cos state unkey
[Sep 14 12:25:17] NOTICE[5335]: app_rpt.c:17473 cos_state_unkey: **** rx un-key
[Sep 14 12:25:17] NOTICE[5335]: app_rpt.c:19522 rpt: **** rx key
[Sep 14 12:25:17] NOTICE[5335]: app_rpt.c:17370 cos_state_machine: **** cos_state_machine: COS_SM_CLEAR, event=COS_ACTIVE, new state = COS_SM_ACTIVE, return_cos_value=2
[Sep 14 12:25:17] NOTICE[5335]: app_rpt.c:19532 rpt: **** rx key
[Sep 14 12:25:17] NOTICE[5333]: app_rpt.c:3502 __mklinklist: Last = 1999, K
[Sep 14 12:25:18] NOTICE[5335]: app_rpt.c:19645 rpt: **** rx unkey
[Sep 14 12:25:18] NOTICE[5335]: app_rpt.c:17387 cos_state_machine: **** cos_state_machine: COS_SM_ACTIVE, event=COS_INACTIVE, new state = COS_SM_ACTIVE_FLAP, return_cos_value=2
[Sep 14 12:25:18] NOTICE[5335]: app_rpt.c:17406 cos_state_machine: **** cos_state_machine: COS_SM_ACTIVE_FLAP, event=COS_TIMER, new state = COS_SM_CLEAR, return_cos_value=5
[Sep 14 12:25:18] NOTICE[5335]: app_rpt.c:17467 cos_state_unkey: **** cos state unkey
[Sep 14 12:25:18] NOTICE[5335]: app_rpt.c:17473 cos_state_unkey: **** rx un-key
--


MMDVM STDOUT output
--
M: 2019-09-14 19:25:16.498 DMR Slot 2, received network voice header from KI6ZHD to TG WB5WXI
M: 2019-09-14 19:25:17.262 DMR Talker Alias (Data Format 1, Received 6/23 char): 'KI6ZHD'
D: 2019-09-14 19:25:17.789 DMR Slot 2, lost audio for 409ms filling in
M: 2019-09-14 19:25:17.980 DMR Talker Alias (Data Format 1, Received 13/23 char): 'KI6ZHD KI6ZHD'
M: 2019-09-14 19:25:18.461 DMR Slot 2, received network end of voice transmission, 2.3 seconds, 15% packet loss, BER: 0.0%
--


Analog_bridge STDOUT output:
--
[ Nothing shown after it starts up successfully ]
--


Re: DMR to Analog Bridge PTT assert quirk

David Ranch
 


Hey Steve,

I'm not 100% sure what you're looking for but here is the output from:

   tail -f /var/log/asterisk/messages &
   tail -f /var/log/Analog_Bridge.log &
   tail -f /var/log/MMDVM_Bridge-`date +%Y-%m-%d`.log &


Let me know if there is anything else you want to see:


--
[root@ww6bay-asl log]# M: 2019-09-14 21:08:36.887 DMR Slot 2, received network voice header from KI6ZHD to TG WB5WXI
[Sep 14 14:08:36] NOTICE[5335] app_rpt.c: **** rx key
[Sep 14 14:08:36] NOTICE[5335] app_rpt.c: **** cos_state_machine: COS_SM_CLEAR, event=COS_ACTIVE, new state = COS_SM_ACTIVE, return_cos_value=2
[Sep 14 14:08:36] NOTICE[5335] app_rpt.c: **** rx key
[Sep 14 14:08:36] NOTICE[5333] app_rpt.c: Last = 1999, K
[Sep 14 14:08:36] NOTICE[5333] app_rpt.c: Tracepoint rpt_telemetry() entered mode=0
[Sep 14 14:08:36] NOTICE[5333] app_rpt.c: Tracepoint rpt_telemetry() exit
[Sep 14 14:08:36] NOTICE[5431] app_rpt.c: [1998] telemetry chan to teleconf
[Sep 14 14:08:36] NOTICE[5335] app_rpt.c: **** rx unkey
[Sep 14 14:08:36] NOTICE[5335] app_rpt.c: **** cos_state_machine: COS_SM_ACTIVE, event=COS_INACTIVE, new state = COS_SM_ACTIVE_FLAP, return_cos_value=2
[Sep 14 14:08:36] NOTICE[5335] app_rpt.c: **** cos_state_machine: COS_SM_ACTIVE_FLAP, event=COS_TIMER, new state = COS_SM_CLEAR, return_cos_value=5
[Sep 14 14:08:36] NOTICE[5335] app_rpt.c: **** cos state unkey
[Sep 14 14:08:36] NOTICE[5335] app_rpt.c: **** rx un-key
[Sep 14 14:08:37] NOTICE[5335] app_rpt.c: **** rx key
[Sep 14 14:08:37] NOTICE[5335] app_rpt.c: **** cos_state_machine: COS_SM_CLEAR, event=COS_ACTIVE, new state = COS_SM_ACTIVE, return_cos_value=2
[Sep 14 14:08:37] NOTICE[5335] app_rpt.c: **** rx key
[Sep 14 14:08:37] NOTICE[5333] app_rpt.c: Last = 1999, K
M: 2019-09-14 21:08:37.687 DMR Talker Alias (Data Format 1, Received 6/23 char): 'KI6ZHD'
M: 2019-09-14 21:08:38.378 DMR Talker Alias (Data Format 1, Received 13/23 char): 'KI6ZHD KI6ZHD'
M: 2019-09-14 21:08:38.839 DMR Slot 2, received network end of voice transmission, 1.9 seconds, 0% packet loss, BER: 0.0%
[Sep 14 14:08:39] NOTICE[5335] app_rpt.c: **** rx unkey
[Sep 14 14:08:39] NOTICE[5335] app_rpt.c: **** cos_state_machine: COS_SM_ACTIVE, event=COS_INACTIVE, new state = COS_SM_ACTIVE_FLAP, return_cos_value=2
[Sep 14 14:08:39] NOTICE[5335] app_rpt.c: **** cos_state_machine: COS_SM_ACTIVE_FLAP, event=COS_TIMER, new state = COS_SM_CLEAR, return_cos_value=5
[Sep 14 14:08:39] NOTICE[5335] app_rpt.c: **** cos state unkey
[Sep 14 14:08:39] NOTICE[5335] app_rpt.c: **** rx un-key
--


Btw.. I'm seeing a lot of error messages like the following today.  Are you aware of Brandmeister having issues today?
--
M: 2019-09-14 20:58:41.665 DMR, Logged into the master successfully
E: 2019-09-14 20:59:41.252 DMR, Connection to the master has timed out, retrying connection
M: 2019-09-14 20:59:41.252 DMR, Closing DMR Network
M: 2019-09-14 20:59:41.252 DMR, Opening DMR Network
M: 2019-09-14 20:59:51.491 DMR, Logged into the master successfully
E: 2019-09-14 21:00:41.753 DMR, Connection to the master has timed out, retrying connection
M: 2019-09-14 21:00:41.753 DMR, Closing DMR Network
M: 2019-09-14 21:00:41.753 DMR, Opening DMR Network
W: 2019-09-14 21:00:51.570 DMR, Login to the master has failed, retrying login ...
M: 2019-09-14 21:00:51.957 DMR, Logged into the master successfully
E: 2019-09-14 21:01:51.570 DMR, Connection to the master has timed out, retrying connection
M: 2019-09-14 21:01:51.570 DMR, Closing DMR Network
M: 2019-09-14 21:01:51.570 DMR, Opening DMR Network
M: 2019-09-14 21:02:01.815 DMR, Logged into the master successfully
E: 2019-09-14 21:02:52.044 DMR, Connection to the master has timed out, retrying connection
M: 2019-09-14 21:02:52.044 DMR, Closing DMR Network
M: 2019-09-14 21:02:52.044 DMR, Opening DMR Network
W: 2019-09-14 21:03:01.897 DMR, Login to the master has failed, retrying login ...
M: 2019-09-14 21:03:02.238 DMR, Logged into the master successfully
E: 2019-09-14 21:04:01.902 DMR, Connection to the master has timed out, retrying connection
M: 2019-09-14 21:04:01.902 DMR, Closing DMR Network
M: 2019-09-14 21:04:01.903 DMR, Opening DMR Network
M: 2019-09-14 21:04:12.143 DMR, Logged into the master successfully
E: 2019-09-14 21:05:02.340 DMR, Connection to the master has timed out, retrying connection
M: 2019-09-14 21:05:02.340 DMR, Closing DMR Network
M: 2019-09-14 21:05:02.340 DMR, Opening DMR Network
W: 2019-09-14 21:05:12.223 DMR, Login to the master has failed, retrying login ...
M: 2019-09-14 21:05:12.556 DMR, Logged into the master successfully
E: 2019-09-14 21:06:12.232 DMR, Connection to the master has timed out, retrying connection
M: 2019-09-14 21:06:12.232 DMR, Closing DMR Network
M: 2019-09-14 21:06:12.232 DMR, Opening DMR Network
M: 2019-09-14 21:06:22.467 DMR, Logged into the master successfully
E: 2019-09-14 21:07:12.670 DMR, Connection to the master has timed out, retrying connection
M: 2019-09-14 21:07:12.670 DMR, Closing DMR Network
M: 2019-09-14 21:07:12.670 DMR, Opening DMR Network
W: 2019-09-14 21:07:22.557 DMR, Login to the master has failed, retrying login ...
M: 2019-09-14 21:07:22.874 DMR, Logged into the master successfully
E: 2019-09-14 21:08:22.566 DMR, Connection to the master has timed out, retrying connection
M: 2019-09-14 21:08:22.567 DMR, Closing DMR Network
M: 2019-09-14 21:08:22.567 DMR, Opening DMR Network
M: 2019-09-14 21:08:32.791 DMR, Logged into the master successfully
--




On 09/14/2019 12:54 PM, Steve N4IRS wrote:
David,
It might be interesting to see you log when the issue happens. I am talking about a snip of the ASL, AB, MB logs at the point in time when the issue happens.

On 9/14/19 3:32 PM, David Ranch wrote:
Hello Everyone,

I have a working Brandmeister talk group to Analog Bridge setup working here but I see a PTT quirk that I'm curious if someone can comment on. 


If I key up the local DMR repeater that's in the Brandmeister talk group, this Raspberry Pi 3B+ setup using a URI-X sound card will light up the PTT LED on the URIX but then go off, then light back up and stay lit.  Beyond that, everything works as it should.  I see this behavior regardless if I use the SW IMBE vocoder or if I use a NW Digital THumbDV.  

Any thoughts on how to fix this "ACTIVE_FLAP" issue?

I've also attached a 7.7MB video of this behavior though I don't know if the Groups.IO system will accept it.  Let's see.

--David
KI6ZHD



Asterisk output with "rpt debug level 6"
--
*CLI> [Sep 14 12:25:16] NOTICE[5335]: app_rpt.c:19522 rpt: **** rx key
[Sep 14 12:25:16] NOTICE[5335]: app_rpt.c:17370 cos_state_machine: **** cos_state_machine: COS_SM_CLEAR, event=COS_ACTIVE, new state = COS_SM_ACTIVE, return_cos_value=2
[Sep 14 12:25:16] NOTICE[5335]: app_rpt.c:19532 rpt: **** rx key
[Sep 14 12:25:16] NOTICE[5333]: app_rpt.c:3502 __mklinklist: Last = 1999, K
[Sep 14 12:25:16] NOTICE[5335]: app_rpt.c:19645 rpt: **** rx unkey
[Sep 14 12:25:16] NOTICE[5335]: app_rpt.c:17387 cos_state_machine: **** cos_state_machine: COS_SM_ACTIVE, event=COS_INACTIVE, new state = COS_SM_ACTIVE_FLAP, return_cos_value=2
[Sep 14 12:25:16] NOTICE[5335]: app_rpt.c:17406 cos_state_machine: **** cos_state_machine: COS_SM_ACTIVE_FLAP, event=COS_TIMER, new state = COS_SM_CLEAR, return_cos_value=5
[Sep 14 12:25:16] NOTICE[5335]: app_rpt.c:17467 cos_state_unkey: **** cos state unkey
[Sep 14 12:25:16] NOTICE[5335]: app_rpt.c:17473 cos_state_unkey: **** rx un-key
[Sep 14 12:25:17] NOTICE[5335]: app_rpt.c:19522 rpt: **** rx key
[Sep 14 12:25:17] NOTICE[5335]: app_rpt.c:17370 cos_state_machine: **** cos_state_machine: COS_SM_CLEAR, event=COS_ACTIVE, new state = COS_SM_ACTIVE, return_cos_value=2
[Sep 14 12:25:17] NOTICE[5335]: app_rpt.c:19532 rpt: **** rx key
[Sep 14 12:25:17] NOTICE[5333]: app_rpt.c:3502 __mklinklist: Last = 1999, K
[Sep 14 12:25:17] NOTICE[5335]: app_rpt.c:19645 rpt: **** rx unkey
[Sep 14 12:25:17] NOTICE[5335]: app_rpt.c:17387 cos_state_machine: **** cos_state_machine: COS_SM_ACTIVE, event=COS_INACTIVE, new state = COS_SM_ACTIVE_FLAP, return_cos_value=2
[Sep 14 12:25:17] NOTICE[5335]: app_rpt.c:17406 cos_state_machine: **** cos_state_machine: COS_SM_ACTIVE_FLAP, event=COS_TIMER, new state = COS_SM_CLEAR, return_cos_value=5
[Sep 14 12:25:17] NOTICE[5335]: app_rpt.c:17467 cos_state_unkey: **** cos state unkey
[Sep 14 12:25:17] NOTICE[5335]: app_rpt.c:17473 cos_state_unkey: **** rx un-key
[Sep 14 12:25:17] NOTICE[5335]: app_rpt.c:19522 rpt: **** rx key
[Sep 14 12:25:17] NOTICE[5335]: app_rpt.c:17370 cos_state_machine: **** cos_state_machine: COS_SM_CLEAR, event=COS_ACTIVE, new state = COS_SM_ACTIVE, return_cos_value=2
[Sep 14 12:25:17] NOTICE[5335]: app_rpt.c:19532 rpt: **** rx key
[Sep 14 12:25:17] NOTICE[5333]: app_rpt.c:3502 __mklinklist: Last = 1999, K
[Sep 14 12:25:18] NOTICE[5335]: app_rpt.c:19645 rpt: **** rx unkey
[Sep 14 12:25:18] NOTICE[5335]: app_rpt.c:17387 cos_state_machine: **** cos_state_machine: COS_SM_ACTIVE, event=COS_INACTIVE, new state = COS_SM_ACTIVE_FLAP, return_cos_value=2
[Sep 14 12:25:18] NOTICE[5335]: app_rpt.c:17406 cos_state_machine: **** cos_state_machine: COS_SM_ACTIVE_FLAP, event=COS_TIMER, new state = COS_SM_CLEAR, return_cos_value=5
[Sep 14 12:25:18] NOTICE[5335]: app_rpt.c:17467 cos_state_unkey: **** cos state unkey
[Sep 14 12:25:18] NOTICE[5335]: app_rpt.c:17473 cos_state_unkey: **** rx un-key
--


MMDVM STDOUT output
--
M: 2019-09-14 19:25:16.498 DMR Slot 2, received network voice header from KI6ZHD to TG WB5WXI
M: 2019-09-14 19:25:17.262 DMR Talker Alias (Data Format 1, Received 6/23 char): 'KI6ZHD'
D: 2019-09-14 19:25:17.789 DMR Slot 2, lost audio for 409ms filling in
M: 2019-09-14 19:25:17.980 DMR Talker Alias (Data Format 1, Received 13/23 char): 'KI6ZHD KI6ZHD'
M: 2019-09-14 19:25:18.461 DMR Slot 2, received network end of voice transmission, 2.3 seconds, 15% packet loss, BER: 0.0%
--


Analog_bridge STDOUT output:
--
[ Nothing shown after it starts up successfully ]
--



Re: DMR to Analog Bridge PTT assert quirk

Steve N4IRS
 

What I want to see is a snip from each log when receiving inbound traffic from DMR. The idea would be to see the start of transmission received on MB, the same signal passed to AB and finally to ASL.

On 9/14/19 5:11 PM, David Ranch wrote:

Hey Steve,

I'm not 100% sure what you're looking for but here is the output from:

   tail -f /var/log/asterisk/messages &
   tail -f /var/log/Analog_Bridge.log &
   tail -f /var/log/MMDVM_Bridge-`date +%Y-%m-%d`.log &


Let me know if there is anything else you want to see:


--
[root@ww6bay-asl log]# M: 2019-09-14 21:08:36.887 DMR Slot 2, received network voice header from KI6ZHD to TG WB5WXI
[Sep 14 14:08:36] NOTICE[5335] app_rpt.c: **** rx key
[Sep 14 14:08:36] NOTICE[5335] app_rpt.c: **** cos_state_machine: COS_SM_CLEAR, event=COS_ACTIVE, new state = COS_SM_ACTIVE, return_cos_value=2
[Sep 14 14:08:36] NOTICE[5335] app_rpt.c: **** rx key
[Sep 14 14:08:36] NOTICE[5333] app_rpt.c: Last = 1999, K
[Sep 14 14:08:36] NOTICE[5333] app_rpt.c: Tracepoint rpt_telemetry() entered mode=0
[Sep 14 14:08:36] NOTICE[5333] app_rpt.c: Tracepoint rpt_telemetry() exit
[Sep 14 14:08:36] NOTICE[5431] app_rpt.c: [1998] telemetry chan to teleconf
[Sep 14 14:08:36] NOTICE[5335] app_rpt.c: **** rx unkey
[Sep 14 14:08:36] NOTICE[5335] app_rpt.c: **** cos_state_machine: COS_SM_ACTIVE, event=COS_INACTIVE, new state = COS_SM_ACTIVE_FLAP, return_cos_value=2
[Sep 14 14:08:36] NOTICE[5335] app_rpt.c: **** cos_state_machine: COS_SM_ACTIVE_FLAP, event=COS_TIMER, new state = COS_SM_CLEAR, return_cos_value=5
[Sep 14 14:08:36] NOTICE[5335] app_rpt.c: **** cos state unkey
[Sep 14 14:08:36] NOTICE[5335] app_rpt.c: **** rx un-key
[Sep 14 14:08:37] NOTICE[5335] app_rpt.c: **** rx key
[Sep 14 14:08:37] NOTICE[5335] app_rpt.c: **** cos_state_machine: COS_SM_CLEAR, event=COS_ACTIVE, new state = COS_SM_ACTIVE, return_cos_value=2
[Sep 14 14:08:37] NOTICE[5335] app_rpt.c: **** rx key
[Sep 14 14:08:37] NOTICE[5333] app_rpt.c: Last = 1999, K
M: 2019-09-14 21:08:37.687 DMR Talker Alias (Data Format 1, Received 6/23 char): 'KI6ZHD'
M: 2019-09-14 21:08:38.378 DMR Talker Alias (Data Format 1, Received 13/23 char): 'KI6ZHD KI6ZHD'
M: 2019-09-14 21:08:38.839 DMR Slot 2, received network end of voice transmission, 1.9 seconds, 0% packet loss, BER: 0.0%
[Sep 14 14:08:39] NOTICE[5335] app_rpt.c: **** rx unkey
[Sep 14 14:08:39] NOTICE[5335] app_rpt.c: **** cos_state_machine: COS_SM_ACTIVE, event=COS_INACTIVE, new state = COS_SM_ACTIVE_FLAP, return_cos_value=2
[Sep 14 14:08:39] NOTICE[5335] app_rpt.c: **** cos_state_machine: COS_SM_ACTIVE_FLAP, event=COS_TIMER, new state = COS_SM_CLEAR, return_cos_value=5
[Sep 14 14:08:39] NOTICE[5335] app_rpt.c: **** cos state unkey
[Sep 14 14:08:39] NOTICE[5335] app_rpt.c: **** rx un-key
--


Btw.. I'm seeing a lot of error messages like the following today.  Are you aware of Brandmeister having issues today?
--
M: 2019-09-14 20:58:41.665 DMR, Logged into the master successfully
E: 2019-09-14 20:59:41.252 DMR, Connection to the master has timed out, retrying connection
M: 2019-09-14 20:59:41.252 DMR, Closing DMR Network
M: 2019-09-14 20:59:41.252 DMR, Opening DMR Network
M: 2019-09-14 20:59:51.491 DMR, Logged into the master successfully
E: 2019-09-14 21:00:41.753 DMR, Connection to the master has timed out, retrying connection
M: 2019-09-14 21:00:41.753 DMR, Closing DMR Network
M: 2019-09-14 21:00:41.753 DMR, Opening DMR Network
W: 2019-09-14 21:00:51.570 DMR, Login to the master has failed, retrying login ...
M: 2019-09-14 21:00:51.957 DMR, Logged into the master successfully
E: 2019-09-14 21:01:51.570 DMR, Connection to the master has timed out, retrying connection
M: 2019-09-14 21:01:51.570 DMR, Closing DMR Network
M: 2019-09-14 21:01:51.570 DMR, Opening DMR Network
M: 2019-09-14 21:02:01.815 DMR, Logged into the master successfully
E: 2019-09-14 21:02:52.044 DMR, Connection to the master has timed out, retrying connection
M: 2019-09-14 21:02:52.044 DMR, Closing DMR Network
M: 2019-09-14 21:02:52.044 DMR, Opening DMR Network
W: 2019-09-14 21:03:01.897 DMR, Login to the master has failed, retrying login ...
M: 2019-09-14 21:03:02.238 DMR, Logged into the master successfully
E: 2019-09-14 21:04:01.902 DMR, Connection to the master has timed out, retrying connection
M: 2019-09-14 21:04:01.902 DMR, Closing DMR Network
M: 2019-09-14 21:04:01.903 DMR, Opening DMR Network
M: 2019-09-14 21:04:12.143 DMR, Logged into the master successfully
E: 2019-09-14 21:05:02.340 DMR, Connection to the master has timed out, retrying connection
M: 2019-09-14 21:05:02.340 DMR, Closing DMR Network
M: 2019-09-14 21:05:02.340 DMR, Opening DMR Network
W: 2019-09-14 21:05:12.223 DMR, Login to the master has failed, retrying login ...
M: 2019-09-14 21:05:12.556 DMR, Logged into the master successfully
E: 2019-09-14 21:06:12.232 DMR, Connection to the master has timed out, retrying connection
M: 2019-09-14 21:06:12.232 DMR, Closing DMR Network
M: 2019-09-14 21:06:12.232 DMR, Opening DMR Network
M: 2019-09-14 21:06:22.467 DMR, Logged into the master successfully
E: 2019-09-14 21:07:12.670 DMR, Connection to the master has timed out, retrying connection
M: 2019-09-14 21:07:12.670 DMR, Closing DMR Network
M: 2019-09-14 21:07:12.670 DMR, Opening DMR Network
W: 2019-09-14 21:07:22.557 DMR, Login to the master has failed, retrying login ...
M: 2019-09-14 21:07:22.874 DMR, Logged into the master successfully
E: 2019-09-14 21:08:22.566 DMR, Connection to the master has timed out, retrying connection
M: 2019-09-14 21:08:22.567 DMR, Closing DMR Network
M: 2019-09-14 21:08:22.567 DMR, Opening DMR Network
M: 2019-09-14 21:08:32.791 DMR, Logged into the master successfully
--




On 09/14/2019 12:54 PM, Steve N4IRS wrote:
David,
It might be interesting to see you log when the issue happens. I am talking about a snip of the ASL, AB, MB logs at the point in time when the issue happens.

On 9/14/19 3:32 PM, David Ranch wrote:
Hello Everyone,

I have a working Brandmeister talk group to Analog Bridge setup working here but I see a PTT quirk that I'm curious if someone can comment on. 


If I key up the local DMR repeater that's in the Brandmeister talk group, this Raspberry Pi 3B+ setup using a URI-X sound card will light up the PTT LED on the URIX but then go off, then light back up and stay lit.  Beyond that, everything works as it should.  I see this behavior regardless if I use the SW IMBE vocoder or if I use a NW Digital THumbDV.  

Any thoughts on how to fix this "ACTIVE_FLAP" issue?

I've also attached a 7.7MB video of this behavior though I don't know if the Groups.IO system will accept it.  Let's see.

--David
KI6ZHD



Asterisk output with "rpt debug level 6"
--
*CLI> [Sep 14 12:25:16] NOTICE[5335]: app_rpt.c:19522 rpt: **** rx key
[Sep 14 12:25:16] NOTICE[5335]: app_rpt.c:17370 cos_state_machine: **** cos_state_machine: COS_SM_CLEAR, event=COS_ACTIVE, new state = COS_SM_ACTIVE, return_cos_value=2
[Sep 14 12:25:16] NOTICE[5335]: app_rpt.c:19532 rpt: **** rx key
[Sep 14 12:25:16] NOTICE[5333]: app_rpt.c:3502 __mklinklist: Last = 1999, K
[Sep 14 12:25:16] NOTICE[5335]: app_rpt.c:19645 rpt: **** rx unkey
[Sep 14 12:25:16] NOTICE[5335]: app_rpt.c:17387 cos_state_machine: **** cos_state_machine: COS_SM_ACTIVE, event=COS_INACTIVE, new state = COS_SM_ACTIVE_FLAP, return_cos_value=2
[Sep 14 12:25:16] NOTICE[5335]: app_rpt.c:17406 cos_state_machine: **** cos_state_machine: COS_SM_ACTIVE_FLAP, event=COS_TIMER, new state = COS_SM_CLEAR, return_cos_value=5
[Sep 14 12:25:16] NOTICE[5335]: app_rpt.c:17467 cos_state_unkey: **** cos state unkey
[Sep 14 12:25:16] NOTICE[5335]: app_rpt.c:17473 cos_state_unkey: **** rx un-key
[Sep 14 12:25:17] NOTICE[5335]: app_rpt.c:19522 rpt: **** rx key
[Sep 14 12:25:17] NOTICE[5335]: app_rpt.c:17370 cos_state_machine: **** cos_state_machine: COS_SM_CLEAR, event=COS_ACTIVE, new state = COS_SM_ACTIVE, return_cos_value=2
[Sep 14 12:25:17] NOTICE[5335]: app_rpt.c:19532 rpt: **** rx key
[Sep 14 12:25:17] NOTICE[5333]: app_rpt.c:3502 __mklinklist: Last = 1999, K
[Sep 14 12:25:17] NOTICE[5335]: app_rpt.c:19645 rpt: **** rx unkey
[Sep 14 12:25:17] NOTICE[5335]: app_rpt.c:17387 cos_state_machine: **** cos_state_machine: COS_SM_ACTIVE, event=COS_INACTIVE, new state = COS_SM_ACTIVE_FLAP, return_cos_value=2
[Sep 14 12:25:17] NOTICE[5335]: app_rpt.c:17406 cos_state_machine: **** cos_state_machine: COS_SM_ACTIVE_FLAP, event=COS_TIMER, new state = COS_SM_CLEAR, return_cos_value=5
[Sep 14 12:25:17] NOTICE[5335]: app_rpt.c:17467 cos_state_unkey: **** cos state unkey
[Sep 14 12:25:17] NOTICE[5335]: app_rpt.c:17473 cos_state_unkey: **** rx un-key
[Sep 14 12:25:17] NOTICE[5335]: app_rpt.c:19522 rpt: **** rx key
[Sep 14 12:25:17] NOTICE[5335]: app_rpt.c:17370 cos_state_machine: **** cos_state_machine: COS_SM_CLEAR, event=COS_ACTIVE, new state = COS_SM_ACTIVE, return_cos_value=2
[Sep 14 12:25:17] NOTICE[5335]: app_rpt.c:19532 rpt: **** rx key
[Sep 14 12:25:17] NOTICE[5333]: app_rpt.c:3502 __mklinklist: Last = 1999, K
[Sep 14 12:25:18] NOTICE[5335]: app_rpt.c:19645 rpt: **** rx unkey
[Sep 14 12:25:18] NOTICE[5335]: app_rpt.c:17387 cos_state_machine: **** cos_state_machine: COS_SM_ACTIVE, event=COS_INACTIVE, new state = COS_SM_ACTIVE_FLAP, return_cos_value=2
[Sep 14 12:25:18] NOTICE[5335]: app_rpt.c:17406 cos_state_machine: **** cos_state_machine: COS_SM_ACTIVE_FLAP, event=COS_TIMER, new state = COS_SM_CLEAR, return_cos_value=5
[Sep 14 12:25:18] NOTICE[5335]: app_rpt.c:17467 cos_state_unkey: **** cos state unkey
[Sep 14 12:25:18] NOTICE[5335]: app_rpt.c:17473 cos_state_unkey: **** rx un-key
--


MMDVM STDOUT output
--
M: 2019-09-14 19:25:16.498 DMR Slot 2, received network voice header from KI6ZHD to TG WB5WXI
M: 2019-09-14 19:25:17.262 DMR Talker Alias (Data Format 1, Received 6/23 char): 'KI6ZHD'
D: 2019-09-14 19:25:17.789 DMR Slot 2, lost audio for 409ms filling in
M: 2019-09-14 19:25:17.980 DMR Talker Alias (Data Format 1, Received 13/23 char): 'KI6ZHD KI6ZHD'
M: 2019-09-14 19:25:18.461 DMR Slot 2, received network end of voice transmission, 2.3 seconds, 15% packet loss, BER: 0.0%
--


Analog_bridge STDOUT output:
--
[ Nothing shown after it starts up successfully ]
--




Re: DMR to Analog Bridge PTT assert quirk

David Ranch
 


Hey Steve,

What I want to see is a snip from each log when receiving inbound traffic from DMR. The idea would be to see the start of transmission received on MB, the same signal passed to AB and finally to ASL.

That's what my first email showed.  It showed the Allstar, the MMDVM, and the Analog_bridge output.   Btw.. there is no Allstar here.. it's just going to Analog_Bridge as the audio will go to an analog repeater controller.

--David
KI6ZHD

Re: DMR to Analog Bridge PTT assert quirk

Steve N4IRS
 

Hey David,
Quote
"It showed the Allstar, the MMDVM, and the Analog_bridge output."
"Btw.. there is no Allstar here"

So, which is it?

From your first message:
*CLI> [Sep 14 12:25:16] NOTICE[5335]: app_rpt.c:19522 rpt: **** rx key
[Sep 14 12:25:16] NOTICE[5335]: app_rpt.c:17370 cos_state_machine: **** cos_state_machine: COS_SM_CLEAR, event=COS_ACTIVE, new state = COS_SM_ACTIVE, return_cos_value=2
[Sep 14 12:25:16] NOTICE[5335]: app_rpt.c:19532 rpt: **** rx key
[Sep 14 12:25:16] NOTICE[5333]: app_rpt.c:3502 __mklinklist: Last = 1999, K

If this is not ASL, what is it?

Yes, I know it's Asterisk and app_rpt

Without seeing the output from AB I don't see the data flow. From the AB systemd unit:
Environment=AnalogBridgeLogDir=/var/log/dvswitch/Analog_Bridge
This is the location of the AB log file.


On 9/14/19 6:55 PM, David Ranch wrote:

Hey Steve,

What I want to see is a snip from each log when receiving inbound traffic from DMR. The idea would be to see the start of transmission received on MB, the same signal passed to AB and finally to ASL.

That's what my first email showed.  It showed the Allstar, the MMDVM, and the Analog_bridge output.   Btw.. there is no Allstar here.. it's just going to Analog_Bridge as the audio will go to an analog repeater controller.

--David
KI6ZHD