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




Join main@DVSwitch.groups.io to automatically receive all group messages.