Date   

Re: ASL ><DMR /DVswitch Audio jitter - port problem ?

Steve N4IRS
 

If I had to guess, I would say you are repeating the DMR traffic back. I suggest this as a DMR ASL node https://dvswitch.groups.io/g/allstarlink/wiki/home
In MMDVM_Bridge log:
M: 2018-06-12 08:52:37.928 DMR, TX state = OFF

M: 2018-06-12 08:52:40.650 DMR, TX state = ON

Steve

On 6/12/2018 11:33 AM, KB8JNM wrote:

Well if it ain't broke, you never learn anything.

I have but one more issue that kept me up the night.

Running on BM TG's, I found if I connect to a quite group (no activity) everything is just fine.
As soon as I switch to a goup with activity, dvswitch/the virtual private node beginds to transmit on its own on the network, holding it up.

The mmdvm bridge /L5 data is the only log file I see that shows something that I am trying yet to understand.
But I can see the activity from BM's self care board. Get plenty of hate mail from it LOL.
This section of the log shows where I switched TG's twice I think.
It seems to be generated perhaps/guessing? by the public connected node but I have striped it away as much as I can of anything in telemetry but perhaps I'm missing something. But I am wondering if there is a direct way to know when dvswitch is txing on the dmr side.
I feel a little lost as I have no way of knowing when I am creating problems.

I: 2018-06-12 08:50:39.564 DMR, Begin TX: src=3101607 rpt=310160705 dst=1148793 slot=2 cc=1 metadata=KB8JNM
M: 2018-06-12 08:52:37.928 DMR, TX state = OFF
M: 2018-06-12 08:52:40.614 DMR Slot 2, received network voice header from KB5RIR to TG KB5RIR
M: 2018-06-12 08:52:40.650 DMR, TX state = ON
I: 2018-06-12 08:52:40.650 DMR, Begin TX: src=3101607 rpt=310160705 dst=1148793 slot=2 cc=1 metadata=KB8JNM
M: 2018-06-12 08:52:41.187 DMR Talker Alias (Data Format 1, Received 6/7 char): 'KB5RIR'
M: 2018-06-12 08:52:41.881 DMR Talker Alias (Data Format 1, Received 7/7 char): 'KB5RIR '
M: 2018-06-12 08:53:16.400 DMR Slot 2, received network end of voice transmission, 35.9 seconds, 0% packet loss, BER: 0.0%
M: 2018-06-12 08:53:58.313 DMR, TX state = OFF
M: 2018-06-12 08:56:37.606 DMR, TX state = ON
I: 2018-06-12 08:56:37.606 DMR, Begin TX: src=3101607 rpt=310160705 dst=114 slot=2 cc=1 metadata=KB8JNM
M: 2018-06-12 08:56:43.772 DMR, TX state = OFF
M: 2018-06-12 08:59:56.763 DMR, TX state = ON
I: 2018-06-12 08:59:56.763 DMR, Begin TX: src=3101607 rpt=310160705 dst=114 slot=2 cc=1 metadata=KB8JNM
M: 2018-06-12 09:00:02.188 DMR, TX state = OFF
M: 2018-06-12 09:03:34.864 DMR, TX state = ON
I: 2018-06-12 09:03:34.864 DMR, Begin TX: src=3101607 rpt=310160705 dst=114 slot=2 cc=1 metadata=KB8JNM
M: 2018-06-12 09:03:51.365 DMR, TX state = OFF
M: 2018-06-12 09:04:00.125 DMR, TX state = ON
I: 2018-06-12 09:04:00.125 DMR, Begin TX: src=3101607 rpt=310160705 dst=114 slot=2 cc=1 metadata=KB8JNM
M: 2018-06-12 09:04:06.729 DMR, TX state = OFF
M: 2018-06-12 09:05:04.467 DMR, TX state = ON
I: 2018-06-12 09:05:04.467 DMR, Begin TX: src=3101607 rpt=310160705 dst=114 slot=2 cc=1 metadata=KB8JNM
M: 2018-06-12 09:05:19.176 DMR, TX state = OFF
M: 2018-06-12 09:06:57.851 DMR, TX state = ON
I: 2018-06-12 09:06:57.851 DMR, Begin TX: src=3101607 rpt=310160705 dst=114 slot=2 cc=1 metadata=KB8JNM
M: 2018-06-12 09:07:09.170 DMR, TX state = OFF
M: 2018-06-12 09:09:15.131 DMR, TX state = ON
I: 2018-06-12 09:09:15.131 DMR, Begin TX: src=3101607 rpt=310160705 dst=114 slot=2 cc=1 metadata=KB8JNM
M: 2018-06-12 09:09:20.519 DMR, TX state = OFF
M: 2018-06-12 09:25:19.847 DMR, TX state = ON
I: 2018-06-12 09:25:19.847 DMR, Begin TX: src=3101607 rpt=310160705 dst=114 slot=2 cc=1 metadata=KB8JNM
M: 2018-06-12 09:25:41.751 DMR, TX state = OFF
M: 2018-06-12 09:39:32.967 DMR, TX state = ON
I: 2018-06-12 09:39:32.967 DMR, Begin TX: src=3101607 rpt=310160705 dst=310 slot=2 cc=1 metadata=KB8JNM
M: 2018-06-12 09:39:44.825 DMR, TX state = OFF
M: 2018-06-12 09:41:14.387 DMR, TX state = ON
I: 2018-06-12 09:41:14.387 DMR, Begin TX: src=3101607 rpt=310160705 dst=310 slot=2 cc=1 metadata=KB8JNM
M: 2018-06-12 09:41:21.400 DMR, TX state = OFF
M: 2018-06-12 09:41:30.185 DMR Slot 2, received network voice header from W9KJO to TG 310
M: 2018-06-12 09:41:30.206 DMR, TX state = ON
I: 2018-06-12 09:41:30.206 DMR, Begin TX: src=3101607 rpt=310160705 dst=310 slot=2 cc=1 metadata=KB8JNM
M: 2018-06-12 09:41:30.779 DMR Talker Alias (Data Format 1, Received 6/21 char): 'W9KJO '
M: 2018-06-12 09:41:31.439 DMR Talker Alias (Data Format 1, Received 13/21 char): 'W9KJO DMR ID:'
M: 2018-06-12 09:41:32.144 DMR Talker Alias (Data Format 1, Received 20/21 char): 'W9KJO DMR ID: 111830'
M: 2018-06-12 09:41:32.875 DMR Talker Alias (Data Format 1, Received 21/21 char): 'W9KJO DMR ID: 1118308'
M: 2018-06-12 09:41:34.439 DMR Slot 2, received network end of voice transmission, 4.4 seconds, 0% packet loss, BER: 0.0%
M: 2018-06-12 09:41:41.361 DMR, TX state = OFF
M: 2018-06-12 09:41:58.905 DMR Slot 2, received network voice header from N6DIQ to TG 310
M: 2018-06-12 09:41:58.946 DMR, TX state = ON
I: 2018-06-12 09:41:58.946 DMR, Begin TX: src=3101607 rpt=310160705 dst=310 slot=2 cc=1 metadata=KB8JNM
M: 2018-06-12 09:41:59.217 DMR Talker Alias (Data Format 1, Received 6/21 char): 'N6DIQ '
M: 2018-06-12 09:41:59.848 DMR Talker Alias (Data Format 1, Received 13/21 char): 'N6DIQ DMR ID:'
M: 2018-06-12 09:42:00.491 DMR Talker Alias (Data Format 1, Received 20/21 char): 'N6DIQ DMR ID: 110666'
M: 2018-06-12 09:42:01.226 DMR Talker Alias (Data Format 1, Received 21/21 char): 'N6DIQ DMR ID: 1106668'
M: 2018-06-12 09:42:04.025 DMR Slot 2, received network end of voice transmission, 5.7 seconds, 0% packet loss, BER: 0.0%
M: 2018-06-12 09:42:11.042 DMR, TX state = OFF
M: 2018-06-12 09:42:17.002 DMR Slot 2, received network voice header from W9KJO to TG 310
M: 2018-06-12 09:42:17.023 DMR, TX state = ON
I: 2018-06-12 09:42:17.023 DMR, Begin TX: src=3101607 rpt=310160705 dst=310 slot=2 cc=1 metadata=KB8JNM
M: 2018-06-12 09:42:17.610 DMR Talker Alias (Data Format 1, Received 6/21 char): 'W9KJO '
M: 2018-06-12 09:42:18.326 DMR Talker Alias (Data Format 1, Received 13/21 char): 'W9KJO DMR ID:'
M: 2018-06-12 09:42:19.061 DMR Talker Alias (Data Format 1, Received 20/21 char): 'W9KJO DMR ID: 111830'
M: 2018-06-12 09:42:19.771 DMR Talker Alias (Data Format 1, Received 21/21 char): 'W9KJO DMR ID: 1118308'
M: 2018-06-12 09:42:24.569 DMR Slot 2, received network end of voice transmission, 7.7 seconds, 0% packet loss, BER: 0.0%
M: 2018-06-12 09:42:31.427 DMR, TX state = OFF
M: 2018-06-12 09:42:31.753 DMR Slot 2, received network voice header from N6DIQ to TG 310
M: 2018-06-12 09:42:31.784 DMR, TX state = ON
I: 2018-06-12 09:42:31.784 DMR, Begin TX: src=3101607 rpt=310160705 dst=310 slot=2 cc=1 metadata=KB8JNM
M: 2018-06-12 09:42:32.024 DMR Talker Alias (Data Format 0, Received 0/0 char): ''
M: 2018-06-12 09:42:32.714 DMR Talker Alias (Data Format 0, Received 0/0 char): ''
M: 2018-06-12 09:42:33.434 DMR Talker Alias (Data Format 1, Received 6/21 char): 'N6DIQ '
M: 2018-06-12 09:42:34.155 DMR Talker Alias (Data Format 1, Received 21/21 char): 'N6DIQ DMR ID: 1106668'
M: 2018-06-12 09:42:46.270 DMR Slot 2, received network end of voice transmission, 14.6 seconds, 0% packet loss, BER: 0.0%
M: 2018-06-12 09:42:53.260 DMR, TX state = OFF
M: 2018-06-12 09:42:58.147 DMR Slot 2, received network voice header from W9KJO to TG 310
M: 2018-06-12 09:42:58.188 DMR, TX state = ON
I: 2018-06-12 09:42:58.188 DMR, Begin TX: src=3101607 rpt=310160705 dst=310 slot=2 cc=1 metadata=KB8JNM
M: 2018-06-12 09:43:02.507 DMR Slot 2, received network end of voice transmission, 5.2 seconds, 12% packet loss, BER: 0.0%
M: 2018-06-12 09:43:09.602 DMR, TX state = OFF
M: 2018-06-12 09:43:10.035 DMR Slot 2, received network voice header from N6DIQ to TG 310
M: 2018-06-12 09:43:10.065 DMR, TX state = ON
I: 2018-06-12 09:43:10.066 DMR, Begin TX: src=3101607 rpt=310160705 dst=310 slot=2 cc=1 metadata=KB8JNM
M: 2018-06-12 09:43:10.275 DMR Talker Alias (Data Format 1, Received 6/21 char): 'N6DIQ '
M: 2018-06-12 09:43:10.996 DMR Talker Alias (Data Format 1, Received 13/21 char): 'N6DIQ DMR ID:'
M: 2018-06-12 09:43:11.712 DMR Talker Alias (Data Format 1, Received 20/21 char): 'N6DIQ DMR ID: 110666'
M: 2018-06-12 09:43:12.433 DMR Talker Alias (Data Format 1, Received 21/21 char): 'N6DIQ DMR ID: 1106668'
M: 2018-06-12 09:43:14.884 DMR Slot 2, received network end of voice transmission, 5.0 seconds, 0% packet loss, BER: 0.0%
M: 2018-06-12 09:43:21.802 DMR, TX state = OFF
M: 2018-06-12 09:43:29.308 DMR Slot 2, received network voice header from W9KJO to TG 310
M: 2018-06-12 09:43:29.344 DMR, TX state = ON
I: 2018-06-12 09:43:29.344 DMR, Begin TX: src=3101607 rpt=310160705 dst=310 slot=2 cc=1 metadata=KB8JNM
M: 2018-06-12 09:43:29.804 DMR Talker Alias (Data Format 1, Received 6/21 char): 'W9KJO '
M: 2018-06-12 09:43:30.524 DMR Talker Alias (Data Format 1, Received 13/21 char): 'W9KJO DMR ID:'
M: 2018-06-12 09:43:31.246 DMR Talker Alias (Data Format 1, Received 20/21 char): 'W9KJO DMR ID: 111830'
M: 2018-06-12 09:43:31.966 DMR Talker Alias (Data Format 1, Received 21/21 char): 'W9KJO DMR ID: 1118308'
M: 2018-06-12 09:43:46.125 DMR Slot 2, received network end of voice transmission, 17.0 seconds, 0% packet loss, BER: 0.0%
M: 2018-06-12 09:43:53.100 DMR, TX state = OFF
M: 2018-06-12 09:43:53.594 DMR Slot 2, received network voice header from N6DIQ to TG 310
M: 2018-06-12 09:43:53.630 DMR, TX state = ON
I: 2018-06-12 09:43:53.630 DMR, Begin TX: src=3101607 rpt=310160705 dst=310 slot=2 cc=1 metadata=KB8JNM
M: 2018-06-12 09:43:53.839 DMR Talker Alias (Data Format 0, Received 0/0 char): ''
M: 2018-06-12 09:43:54.554 DMR Talker Alias (Data Format 1, Received 6/21 char): 'N6DIQ '
M: 2018-06-12 09:43:55.277 DMR Talker Alias (Data Format 1, Received 13/21 char): 'N6DIQ DMR ID:'
M: 2018-06-12 09:43:55.997 DMR Talker Alias (Data Format 1, Received 21/21 char): 'N6DIQ DMR ID: 1106668'
M: 2018-06-12 09:44:16.027 DMR Slot 2, received network end of voice transmission, 22.4 seconds, 0% packet loss, BER: 0.0%
M: 2018-06-12 09:44:22.247 DMR, TX state = ON
I: 2018-06-12 09:44:22.247 DMR, Begin TX: src=3101607 rpt=310160705 dst=314 slot=2 cc=1 metadata=KB8JNM
M: 2018-06-12 09:44:23.771 DMR, TX state = OFF
M: 2018-06-12 09:49:29.374 DMR Slot 2, received network voice header from W1FPW to TG 310
M: 2018-06-12 09:49:29.680 DMR Slot 2, received network end of voice transmission, 0.5 seconds, 0% packet loss, BER: 1.4%
M: 2018-06-12 09:50:31.119 DMR Slot 2, received network voice header from W2ZH to TG 310
M: 2018-06-12 09:50:32.366 DMR Slot 2, received network end of voice transmission, 1.0 seconds, 70% packet loss, BER: 0.0%
M: 2018-06-12 09:51:54.348 DMR Slot 2, received network voice header from W9KJO to TG 310
M: 2018-06-12 09:51:54.706 DMR Slot 2, received network end of voice transmission, 0.5 seconds, 0% packet loss, BER: 0.0%
M: 2018-06-12 09:52:08.698 DMR Slot 2, received network voice header from W1FPW to TG 310
M: 2018-06-12 09:52:09.269 DMR Talker Alias (Data Format 1, Received 6/21 char): 'W1FPW '
M: 2018-06-12 09:52:09.988 DMR Talker Alias (Data Format 1, Received 13/21 char): 'W1FPW DMR ID:'
M: 2018-06-12 09:52:10.712 DMR Talker Alias (Data Format 1, Received 20/21 char): 'W1FPW DMR ID: 312586'
M: 2018-06-12 09:52:11.431 DMR Talker Alias (Data Format 1, Received 21/21 char): 'W1FPW DMR ID: 3125869'
M: 2018-06-12 09:52:17.309 DMR Slot 2, received network end of voice transmission, 8.8 seconds, 0% packet loss, BER: 0.0%
M: 2018-06-12 09:52:23.544 DMR Slot 2, received network voice header from KD7CWB to TG 310
M: 2018-06-12 09:52:24.730 DMR Slot 2, received network end of voice transmission, 1.1 seconds, 66% packet loss, BER: 0.0%
M: 2018-06-12 09:52:27.872 DMR Slot 2, received network voice header from N6DIQ to TG 310
M: 2018-06-12 09:52:28.290 DMR Talker Alias (Data Format 1, Received 6/21 char): 'N6DIQ '
M: 2018-06-12 09:52:28.892 DMR Talker Alias (Data Format 1, Received 13/21 char): 'N6DIQ DMR ID:'
M: 2018-06-12 09:52:29.382 DMR Talker Alias (Data Format 1, Received 20/21 char): 'N6DIQ DMR ID: 110666'
M: 2018-06-12 09:52:30.075 DMR Talker Alias (Data Format 1, Received 21/21 char): 'N6DIQ DMR ID: 1106668'
M: 2018-06-12 09:52:37.922 DMR Slot 2, received network end of voice transmission, 10.7 seconds, 0% packet loss, BER: 0.0%
M: 2018-06-12 09:52:42.112 DMR Slot 2, received network voice header from W1FPW to TG 310
M: 2018-06-12 09:52:42.657 DMR Talker Alias (Data Format 1, Received 6/21 char): 'W1FPW '
M: 2018-06-12 09:52:43.381 DMR Talker Alias (Data Format 1, Received 13/21 char): 'W1FPW DMR ID:'
M: 2018-06-12 09:52:44.100 DMR Talker Alias (Data Format 1, Received 20/21 char): 'W1FPW DMR ID: 312586'
M: 2018-06-12 09:52:44.819 DMR Talker Alias (Data Format 1, Received 21/21 char): 'W1FPW DMR ID: 3125869'
M: 2018-06-12 09:52:58.982 DMR Slot 2, received network end of voice transmission, 17.0 seconds, 0% packet loss, BER: 0.0%
M: 2018-06-12 09:53:03.885 DMR Slot 2, received network voice header from N6DIQ to TG 310
M: 2018-06-12 09:53:04.187 DMR Talker Alias (Data Format 1, Received 6/21 char): 'N6DIQ '
M: 2018-06-12 09:53:04.830 DMR Talker Alias (Data Format 1, Received 13/21 char): 'N6DIQ DMR ID:'
M: 2018-06-12 09:53:05.534 DMR Talker Alias (Data Format 1, Received 20/21 char): 'N6DIQ DMR ID: 110666'
M: 2018-06-12 09:53:06.257 DMR Talker Alias (Data Format 1, Received 21/21 char): 'N6DIQ DMR ID: 1106668'
M: 2018-06-12 09:53:17.283 DMR Slot 2, received network end of voice transmission, 13.9 seconds, 0% packet loss, BER: 0.0%
M: 2018-06-12 09:53:22.867 DMR Slot 2, received network voice header from W1FPW to TG 310


Re: ASL ><DMR /DVswitch Audio jitter - port problem ?

Mike KB8JNM
 


Well if it ain't broke, you never learn anything.

I have but one more issue that kept me up the night.

Running on BM TG's, I found if I connect to a quite group (no activity) everything is just fine.
As soon as I switch to a goup with activity, dvswitch/the virtual private node beginds to transmit on its own on the network, holding it up.

The mmdvm bridge /L5 data is the only log file I see that shows something that I am trying yet to understand.
But I can see the activity from BM's self care board. Get plenty of hate mail from it LOL.
This section of the log shows where I switched TG's twice I think.
It seems to be generated perhaps/guessing? by the public connected node but I have striped it away as much as I can of anything in telemetry but perhaps I'm missing something. But I am wondering if there is a direct way to know when dvswitch is txing on the dmr side.
I feel a little lost as I have no way of knowing when I am creating problems.

I: 2018-06-12 08:50:39.564 DMR, Begin TX: src=3101607 rpt=310160705 dst=1148793 slot=2 cc=1 metadata=KB8JNM
M: 2018-06-12 08:52:37.928 DMR, TX state = OFF
M: 2018-06-12 08:52:40.614 DMR Slot 2, received network voice header from KB5RIR to TG KB5RIR
M: 2018-06-12 08:52:40.650 DMR, TX state = ON
I: 2018-06-12 08:52:40.650 DMR, Begin TX: src=3101607 rpt=310160705 dst=1148793 slot=2 cc=1 metadata=KB8JNM
M: 2018-06-12 08:52:41.187 DMR Talker Alias (Data Format 1, Received 6/7 char): 'KB5RIR'
M: 2018-06-12 08:52:41.881 DMR Talker Alias (Data Format 1, Received 7/7 char): 'KB5RIR '
M: 2018-06-12 08:53:16.400 DMR Slot 2, received network end of voice transmission, 35.9 seconds, 0% packet loss, BER: 0.0%
M: 2018-06-12 08:53:58.313 DMR, TX state = OFF
M: 2018-06-12 08:56:37.606 DMR, TX state = ON
I: 2018-06-12 08:56:37.606 DMR, Begin TX: src=3101607 rpt=310160705 dst=114 slot=2 cc=1 metadata=KB8JNM
M: 2018-06-12 08:56:43.772 DMR, TX state = OFF
M: 2018-06-12 08:59:56.763 DMR, TX state = ON
I: 2018-06-12 08:59:56.763 DMR, Begin TX: src=3101607 rpt=310160705 dst=114 slot=2 cc=1 metadata=KB8JNM
M: 2018-06-12 09:00:02.188 DMR, TX state = OFF
M: 2018-06-12 09:03:34.864 DMR, TX state = ON
I: 2018-06-12 09:03:34.864 DMR, Begin TX: src=3101607 rpt=310160705 dst=114 slot=2 cc=1 metadata=KB8JNM
M: 2018-06-12 09:03:51.365 DMR, TX state = OFF
M: 2018-06-12 09:04:00.125 DMR, TX state = ON
I: 2018-06-12 09:04:00.125 DMR, Begin TX: src=3101607 rpt=310160705 dst=114 slot=2 cc=1 metadata=KB8JNM
M: 2018-06-12 09:04:06.729 DMR, TX state = OFF
M: 2018-06-12 09:05:04.467 DMR, TX state = ON
I: 2018-06-12 09:05:04.467 DMR, Begin TX: src=3101607 rpt=310160705 dst=114 slot=2 cc=1 metadata=KB8JNM
M: 2018-06-12 09:05:19.176 DMR, TX state = OFF
M: 2018-06-12 09:06:57.851 DMR, TX state = ON
I: 2018-06-12 09:06:57.851 DMR, Begin TX: src=3101607 rpt=310160705 dst=114 slot=2 cc=1 metadata=KB8JNM
M: 2018-06-12 09:07:09.170 DMR, TX state = OFF
M: 2018-06-12 09:09:15.131 DMR, TX state = ON
I: 2018-06-12 09:09:15.131 DMR, Begin TX: src=3101607 rpt=310160705 dst=114 slot=2 cc=1 metadata=KB8JNM
M: 2018-06-12 09:09:20.519 DMR, TX state = OFF
M: 2018-06-12 09:25:19.847 DMR, TX state = ON
I: 2018-06-12 09:25:19.847 DMR, Begin TX: src=3101607 rpt=310160705 dst=114 slot=2 cc=1 metadata=KB8JNM
M: 2018-06-12 09:25:41.751 DMR, TX state = OFF
M: 2018-06-12 09:39:32.967 DMR, TX state = ON
I: 2018-06-12 09:39:32.967 DMR, Begin TX: src=3101607 rpt=310160705 dst=310 slot=2 cc=1 metadata=KB8JNM
M: 2018-06-12 09:39:44.825 DMR, TX state = OFF
M: 2018-06-12 09:41:14.387 DMR, TX state = ON
I: 2018-06-12 09:41:14.387 DMR, Begin TX: src=3101607 rpt=310160705 dst=310 slot=2 cc=1 metadata=KB8JNM
M: 2018-06-12 09:41:21.400 DMR, TX state = OFF
M: 2018-06-12 09:41:30.185 DMR Slot 2, received network voice header from W9KJO to TG 310
M: 2018-06-12 09:41:30.206 DMR, TX state = ON
I: 2018-06-12 09:41:30.206 DMR, Begin TX: src=3101607 rpt=310160705 dst=310 slot=2 cc=1 metadata=KB8JNM
M: 2018-06-12 09:41:30.779 DMR Talker Alias (Data Format 1, Received 6/21 char): 'W9KJO '
M: 2018-06-12 09:41:31.439 DMR Talker Alias (Data Format 1, Received 13/21 char): 'W9KJO DMR ID:'
M: 2018-06-12 09:41:32.144 DMR Talker Alias (Data Format 1, Received 20/21 char): 'W9KJO DMR ID: 111830'
M: 2018-06-12 09:41:32.875 DMR Talker Alias (Data Format 1, Received 21/21 char): 'W9KJO DMR ID: 1118308'
M: 2018-06-12 09:41:34.439 DMR Slot 2, received network end of voice transmission, 4.4 seconds, 0% packet loss, BER: 0.0%
M: 2018-06-12 09:41:41.361 DMR, TX state = OFF
M: 2018-06-12 09:41:58.905 DMR Slot 2, received network voice header from N6DIQ to TG 310
M: 2018-06-12 09:41:58.946 DMR, TX state = ON
I: 2018-06-12 09:41:58.946 DMR, Begin TX: src=3101607 rpt=310160705 dst=310 slot=2 cc=1 metadata=KB8JNM
M: 2018-06-12 09:41:59.217 DMR Talker Alias (Data Format 1, Received 6/21 char): 'N6DIQ '
M: 2018-06-12 09:41:59.848 DMR Talker Alias (Data Format 1, Received 13/21 char): 'N6DIQ DMR ID:'
M: 2018-06-12 09:42:00.491 DMR Talker Alias (Data Format 1, Received 20/21 char): 'N6DIQ DMR ID: 110666'
M: 2018-06-12 09:42:01.226 DMR Talker Alias (Data Format 1, Received 21/21 char): 'N6DIQ DMR ID: 1106668'
M: 2018-06-12 09:42:04.025 DMR Slot 2, received network end of voice transmission, 5.7 seconds, 0% packet loss, BER: 0.0%
M: 2018-06-12 09:42:11.042 DMR, TX state = OFF
M: 2018-06-12 09:42:17.002 DMR Slot 2, received network voice header from W9KJO to TG 310
M: 2018-06-12 09:42:17.023 DMR, TX state = ON
I: 2018-06-12 09:42:17.023 DMR, Begin TX: src=3101607 rpt=310160705 dst=310 slot=2 cc=1 metadata=KB8JNM
M: 2018-06-12 09:42:17.610 DMR Talker Alias (Data Format 1, Received 6/21 char): 'W9KJO '
M: 2018-06-12 09:42:18.326 DMR Talker Alias (Data Format 1, Received 13/21 char): 'W9KJO DMR ID:'
M: 2018-06-12 09:42:19.061 DMR Talker Alias (Data Format 1, Received 20/21 char): 'W9KJO DMR ID: 111830'
M: 2018-06-12 09:42:19.771 DMR Talker Alias (Data Format 1, Received 21/21 char): 'W9KJO DMR ID: 1118308'
M: 2018-06-12 09:42:24.569 DMR Slot 2, received network end of voice transmission, 7.7 seconds, 0% packet loss, BER: 0.0%
M: 2018-06-12 09:42:31.427 DMR, TX state = OFF
M: 2018-06-12 09:42:31.753 DMR Slot 2, received network voice header from N6DIQ to TG 310
M: 2018-06-12 09:42:31.784 DMR, TX state = ON
I: 2018-06-12 09:42:31.784 DMR, Begin TX: src=3101607 rpt=310160705 dst=310 slot=2 cc=1 metadata=KB8JNM
M: 2018-06-12 09:42:32.024 DMR Talker Alias (Data Format 0, Received 0/0 char): ''
M: 2018-06-12 09:42:32.714 DMR Talker Alias (Data Format 0, Received 0/0 char): ''
M: 2018-06-12 09:42:33.434 DMR Talker Alias (Data Format 1, Received 6/21 char): 'N6DIQ '
M: 2018-06-12 09:42:34.155 DMR Talker Alias (Data Format 1, Received 21/21 char): 'N6DIQ DMR ID: 1106668'
M: 2018-06-12 09:42:46.270 DMR Slot 2, received network end of voice transmission, 14.6 seconds, 0% packet loss, BER: 0.0%
M: 2018-06-12 09:42:53.260 DMR, TX state = OFF
M: 2018-06-12 09:42:58.147 DMR Slot 2, received network voice header from W9KJO to TG 310
M: 2018-06-12 09:42:58.188 DMR, TX state = ON
I: 2018-06-12 09:42:58.188 DMR, Begin TX: src=3101607 rpt=310160705 dst=310 slot=2 cc=1 metadata=KB8JNM
M: 2018-06-12 09:43:02.507 DMR Slot 2, received network end of voice transmission, 5.2 seconds, 12% packet loss, BER: 0.0%
M: 2018-06-12 09:43:09.602 DMR, TX state = OFF
M: 2018-06-12 09:43:10.035 DMR Slot 2, received network voice header from N6DIQ to TG 310
M: 2018-06-12 09:43:10.065 DMR, TX state = ON
I: 2018-06-12 09:43:10.066 DMR, Begin TX: src=3101607 rpt=310160705 dst=310 slot=2 cc=1 metadata=KB8JNM
M: 2018-06-12 09:43:10.275 DMR Talker Alias (Data Format 1, Received 6/21 char): 'N6DIQ '
M: 2018-06-12 09:43:10.996 DMR Talker Alias (Data Format 1, Received 13/21 char): 'N6DIQ DMR ID:'
M: 2018-06-12 09:43:11.712 DMR Talker Alias (Data Format 1, Received 20/21 char): 'N6DIQ DMR ID: 110666'
M: 2018-06-12 09:43:12.433 DMR Talker Alias (Data Format 1, Received 21/21 char): 'N6DIQ DMR ID: 1106668'
M: 2018-06-12 09:43:14.884 DMR Slot 2, received network end of voice transmission, 5.0 seconds, 0% packet loss, BER: 0.0%
M: 2018-06-12 09:43:21.802 DMR, TX state = OFF
M: 2018-06-12 09:43:29.308 DMR Slot 2, received network voice header from W9KJO to TG 310
M: 2018-06-12 09:43:29.344 DMR, TX state = ON
I: 2018-06-12 09:43:29.344 DMR, Begin TX: src=3101607 rpt=310160705 dst=310 slot=2 cc=1 metadata=KB8JNM
M: 2018-06-12 09:43:29.804 DMR Talker Alias (Data Format 1, Received 6/21 char): 'W9KJO '
M: 2018-06-12 09:43:30.524 DMR Talker Alias (Data Format 1, Received 13/21 char): 'W9KJO DMR ID:'
M: 2018-06-12 09:43:31.246 DMR Talker Alias (Data Format 1, Received 20/21 char): 'W9KJO DMR ID: 111830'
M: 2018-06-12 09:43:31.966 DMR Talker Alias (Data Format 1, Received 21/21 char): 'W9KJO DMR ID: 1118308'
M: 2018-06-12 09:43:46.125 DMR Slot 2, received network end of voice transmission, 17.0 seconds, 0% packet loss, BER: 0.0%
M: 2018-06-12 09:43:53.100 DMR, TX state = OFF
M: 2018-06-12 09:43:53.594 DMR Slot 2, received network voice header from N6DIQ to TG 310
M: 2018-06-12 09:43:53.630 DMR, TX state = ON
I: 2018-06-12 09:43:53.630 DMR, Begin TX: src=3101607 rpt=310160705 dst=310 slot=2 cc=1 metadata=KB8JNM
M: 2018-06-12 09:43:53.839 DMR Talker Alias (Data Format 0, Received 0/0 char): ''
M: 2018-06-12 09:43:54.554 DMR Talker Alias (Data Format 1, Received 6/21 char): 'N6DIQ '
M: 2018-06-12 09:43:55.277 DMR Talker Alias (Data Format 1, Received 13/21 char): 'N6DIQ DMR ID:'
M: 2018-06-12 09:43:55.997 DMR Talker Alias (Data Format 1, Received 21/21 char): 'N6DIQ DMR ID: 1106668'
M: 2018-06-12 09:44:16.027 DMR Slot 2, received network end of voice transmission, 22.4 seconds, 0% packet loss, BER: 0.0%
M: 2018-06-12 09:44:22.247 DMR, TX state = ON
I: 2018-06-12 09:44:22.247 DMR, Begin TX: src=3101607 rpt=310160705 dst=314 slot=2 cc=1 metadata=KB8JNM
M: 2018-06-12 09:44:23.771 DMR, TX state = OFF
M: 2018-06-12 09:49:29.374 DMR Slot 2, received network voice header from W1FPW to TG 310
M: 2018-06-12 09:49:29.680 DMR Slot 2, received network end of voice transmission, 0.5 seconds, 0% packet loss, BER: 1.4%
M: 2018-06-12 09:50:31.119 DMR Slot 2, received network voice header from W2ZH to TG 310
M: 2018-06-12 09:50:32.366 DMR Slot 2, received network end of voice transmission, 1.0 seconds, 70% packet loss, BER: 0.0%
M: 2018-06-12 09:51:54.348 DMR Slot 2, received network voice header from W9KJO to TG 310
M: 2018-06-12 09:51:54.706 DMR Slot 2, received network end of voice transmission, 0.5 seconds, 0% packet loss, BER: 0.0%
M: 2018-06-12 09:52:08.698 DMR Slot 2, received network voice header from W1FPW to TG 310
M: 2018-06-12 09:52:09.269 DMR Talker Alias (Data Format 1, Received 6/21 char): 'W1FPW '
M: 2018-06-12 09:52:09.988 DMR Talker Alias (Data Format 1, Received 13/21 char): 'W1FPW DMR ID:'
M: 2018-06-12 09:52:10.712 DMR Talker Alias (Data Format 1, Received 20/21 char): 'W1FPW DMR ID: 312586'
M: 2018-06-12 09:52:11.431 DMR Talker Alias (Data Format 1, Received 21/21 char): 'W1FPW DMR ID: 3125869'
M: 2018-06-12 09:52:17.309 DMR Slot 2, received network end of voice transmission, 8.8 seconds, 0% packet loss, BER: 0.0%
M: 2018-06-12 09:52:23.544 DMR Slot 2, received network voice header from KD7CWB to TG 310
M: 2018-06-12 09:52:24.730 DMR Slot 2, received network end of voice transmission, 1.1 seconds, 66% packet loss, BER: 0.0%
M: 2018-06-12 09:52:27.872 DMR Slot 2, received network voice header from N6DIQ to TG 310
M: 2018-06-12 09:52:28.290 DMR Talker Alias (Data Format 1, Received 6/21 char): 'N6DIQ '
M: 2018-06-12 09:52:28.892 DMR Talker Alias (Data Format 1, Received 13/21 char): 'N6DIQ DMR ID:'
M: 2018-06-12 09:52:29.382 DMR Talker Alias (Data Format 1, Received 20/21 char): 'N6DIQ DMR ID: 110666'
M: 2018-06-12 09:52:30.075 DMR Talker Alias (Data Format 1, Received 21/21 char): 'N6DIQ DMR ID: 1106668'
M: 2018-06-12 09:52:37.922 DMR Slot 2, received network end of voice transmission, 10.7 seconds, 0% packet loss, BER: 0.0%
M: 2018-06-12 09:52:42.112 DMR Slot 2, received network voice header from W1FPW to TG 310
M: 2018-06-12 09:52:42.657 DMR Talker Alias (Data Format 1, Received 6/21 char): 'W1FPW '
M: 2018-06-12 09:52:43.381 DMR Talker Alias (Data Format 1, Received 13/21 char): 'W1FPW DMR ID:'
M: 2018-06-12 09:52:44.100 DMR Talker Alias (Data Format 1, Received 20/21 char): 'W1FPW DMR ID: 312586'
M: 2018-06-12 09:52:44.819 DMR Talker Alias (Data Format 1, Received 21/21 char): 'W1FPW DMR ID: 3125869'
M: 2018-06-12 09:52:58.982 DMR Slot 2, received network end of voice transmission, 17.0 seconds, 0% packet loss, BER: 0.0%
M: 2018-06-12 09:53:03.885 DMR Slot 2, received network voice header from N6DIQ to TG 310
M: 2018-06-12 09:53:04.187 DMR Talker Alias (Data Format 1, Received 6/21 char): 'N6DIQ '
M: 2018-06-12 09:53:04.830 DMR Talker Alias (Data Format 1, Received 13/21 char): 'N6DIQ DMR ID:'
M: 2018-06-12 09:53:05.534 DMR Talker Alias (Data Format 1, Received 20/21 char): 'N6DIQ DMR ID: 110666'
M: 2018-06-12 09:53:06.257 DMR Talker Alias (Data Format 1, Received 21/21 char): 'N6DIQ DMR ID: 1106668'
M: 2018-06-12 09:53:17.283 DMR Slot 2, received network end of voice transmission, 13.9 seconds, 0% packet loss, BER: 0.0%
M: 2018-06-12 09:53:22.867 DMR Slot 2, received network voice header from W1FPW to TG 310


Re: How to configure a ASL server

TG9AOR
 

Jeff, I thank you for your comments. Very well taken. I came into this project with 0 AllStar knowledge, I got my Node number over on Memorial Day Weekend, so your input is very valuable to me. The Echolink integration I took upon it as a personal challenge, in order to use the DVSwitch tools to convert one audio format to another, and since I had no AllStar Node or infrastructure I could access, the Echolink world was the only system I knew or used for analog FM. So as I read on the AllStar Wiki and the documentation I am more inclined to use the AllStar system and just leave Echolink as an option. Have a great day.
--
José Roberto Ruíz García Salas
TG9AOR


Re: ASL ><DMR /DVswitch Audio jitter - port problem ?

J P Watters KC9KKO <kc9kko@...>
 

Mike,

I am interested in your USRP configuration. 
The Ettus chassis, the RF Daugherboard, etc

you can email me off list. KC9KKO@...

..jpw


Re: ASL ><DMR /DVswitch Audio jitter - port problem ?

Mike KB8JNM
 

good grief...
That seems to have fixed it.... but I did try it that way. Perhaps when my ports were incorrect.

Seems to be working nicely.
TNX


Re: ASL ><DMR /DVswitch Audio jitter - port problem ?

Steve N4IRS
 

Change and retest

[GENERAL]
useEmulator = false                     ; Use the MD380 AMBE emulator for AMBE72 (DMR/YSFN/NXDN)

On 06/11/2018 10:25 PM, KB8JNM wrote:
[GENERAL]
logLevel = 2                            ; Show messages and above 0=No logging, 1=Debug, 2=Message, 3=Info, 4=Warning, 5=Error, 6=Fatal

; Metadata management
exportMetadata = true                   ; Export metadata to USRP partner (transcode setups require this)
subscriberFile = /var/lib/dvswitch/subscriber_ids.csv   ; DMR ID to callsign lookup data

; General vocoder setup information
decoderFallBack = true                 ; Allow software AMBE decoding if a hardware decoder is not found
useEmulator = true                     ; Use the MD380 AMBE emulator for AMBE72 (DMR/YSFN/NXDN)


Re: ASL ><DMR /DVswitch Audio jitter - port problem ?

Mike KB8JNM
 

sorry steve

; 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]
logLevel = 2                            ; Show messages and above 0=No logging, 1=Debug, 2=Message, 3=Info, 4=Warning, 5=Error, 6=Fatal

; Metadata management
exportMetadata = true                   ; Export metadata to USRP partner (transcode setups require this)
subscriberFile = /var/lib/dvswitch/subscriber_ids.csv   ; DMR ID to callsign lookup data

; General vocoder setup information
decoderFallBack = true                 ; Allow software AMBE decoding if a hardware decoder is not found
useEmulator = true                     ; Use the MD380 AMBE emulator for AMBE72 (DMR/YSFN/NXDN)
emulatorAddress = 127.0.0.1:2470        ; IP address and port of the server

; Audio devices are normally not needed when in gateway service.  These devices should
; only be set when local monitor or dongle modes are required.
outputAudioDevice = /dev/null           ; Audio device /dev/null, /dev/dsp1, portaudio, etc
inputAudioDevice = /dev/null            ; Only used for dongle mode

; 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_Bridges (Where xx is MMDVM, HB, IPSC)
[AMBE_AUDIO]
server = 127.0.0.1                      ; IP address of xx_Bridge.py
fromDMRPort = 31100                     ; AMBE frames from xx_Bridge (should match "toGatewayPort" in xx_Bridge.cfg)
toDMRPort = 31103                       ; AMBE frames from xx_Bridge (should match "fromGatewayPort" in xx_Bridge.cfg)
ambeMode = DMR                          ; DMR, DMR_IPSC, DSTAR, NXDN, P25, YSFN, YSFW
minTxTimeMS = 2500                      ; Minimum time in MS for hang delay
gatewayDmrId = 3101607                        ; ID to use when transmitting from Analog_Bridge
repeaterID = 310160705                          ; ID of source repeater
txTg = 312                             ; 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 interface uses PCM to transfer audio information
; There are two typical configurations, ASL and Transcode.  ASL (AllstarLink) is for analog clients connected
; to a digital network.  Transcode is when Analog_Bridge actually points its PCM interfaces back at itself,
; causing a TLV <-- (pcm <--> pcm) --> TLV type of architecture.
;   When using ASL, this matches the rpt.conf ASL file with a setting like:
;   rxchannel = usrp/127.0.0.1:34001:32001
;   When Transcoding, make toASLPort equal to the other instance fromASLPort (crossover)
[USRP]
server = 127.0.0.1                      ; IP address of Allstar/Asterisk
toASLPort = 32001                       ; Analog_Bridge <-- ASL
fromASLPort = 34001                     ; Analog_Bridge --> ASL
aslAudio = AUDIO_UNITY                  ; 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_USE_GAIN, AUDIO_BPF)
dmrGain = 0.35                          ; Gain factor of audio from ASL (0.0-1.0)

; Information for DV3000 hardware decoder
;   There are two configuration modes: IP (AMBEServer) and serial (direct connect hardware)
;   Use top server and port if using AMBEServer
;   Use bottom server/port and serial = true if using the DV3000u (thumbdv)
;   Did you run AMBETest4.py before using this?
[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


Re: ASL ><DMR /DVswitch Audio jitter - port problem ?

Steve N4IRS
 

I shoulkd have asked for the whole Analog_Bridge.ini

On 06/11/2018 10:09 PM, KB8JNM wrote:
opps... thought i caught them all

Intel atom 2.1ghz 4gb ram

[USRP]
server = 127.0.0.1                      ; IP address of Allstar/Asterisk
toASLPort = 32001                       ; Analog_Bridge <-- ASL
fromASLPort = 34001                     ; Analog_Bridge --> ASL
aslAudio = AUDIO_UNITY                  ; 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_USE_GAIN, AUDIO_BPF)
dmrGain = 0.35


Re: ASL ><DMR /DVswitch Audio jitter - port problem ?

Mike KB8JNM
 

opps... thought i caught them all

Intel atom 2.1ghz 4gb ram

[USRP]
server = 127.0.0.1                      ; IP address of Allstar/Asterisk
toASLPort = 32001                       ; Analog_Bridge <-- ASL
fromASLPort = 34001                     ; Analog_Bridge --> ASL
aslAudio = AUDIO_UNITY                  ; 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_USE_GAIN, AUDIO_BPF)
dmrGain = 0.35


Re: ASL ><DMR /DVswitch Audio jitter - port problem ?

Steve N4IRS
 

What hardware are you running on?
Please show us your [USRP] stanza

Steve

On 06/11/2018 09:27 PM, KB8JNM wrote:
Well after thinking I had this under wraps, and connecting to a busy TG,
I found it was tx-ing the channel.(got some hate mail)

Scope back trough the docs and files, found a port mismatch.
But, after that, has such terrible audio on rx, not manageable.

It sounds like a port conflict to me but I can't find it.
I had check the tx audio with a friend and herd it back through his phone. Perfect.

So... out of hair on this one for 8 hours or more !
But it sounds really like something else in my network is causing the issue.  ???

[AMBE_AUDIO]
server = 127.0.0.1                      ; IP address of xx_Bridge.py
fromDMRPort = 31100                     ; AMBE frames from xx_Bridge (should match "toGatewayPort" in xx_Bridge.cfg)
toDMRPort = 31103                       ; AMBE frames from xx_Bridge (should match "fromGatewayPort" in xx_Bridge.cfg)
ambeMode = DMR                          ; DMR, DMR_IPSC, DSTAR, NXDN, P25, YSFN, YSFW
minTxTimeMS = 2500                      ; Minimum time in MS for hang delay
gatewayDmrId = 3101607                        ; ID to use when transmitting from Analog_Bridge
repeaterID = 310160705                          ; ID of source repeater
txTg = 312                             ; 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         

-----------------
[DMR]
Enable=1
ColorCode=1
EmbeddedLCOnly=1
DumpTAData=0
-------------
[DMR Network]
Enable=1
Address=3102.repeater.net
Port=62031
Jitter=360
Local=62032
Password=passw0rd
Slot1=1
Slot2=1
Debug=0
--------------
[1999]
rxchannel = USRP/127.0.0.1:34001:32001


ASL ><DMR /DVswitch Audio jitter - port problem ?

Mike KB8JNM
 
Edited

Well after thinking I had this under wraps, and connecting to a busy TG,
I found it was tx-ing the channel.(got some hate mail)

Scope back trough the docs and files, found a port mismatch.
But, after that, has such terrible audio on rx, not manageable.

It sounds like a port conflict to me but I can't find it.
I had check the tx audio with a friend and herd it back through his phone. Perfect.

So... out of hair on this one for 8 hours or more !
But it sounds really like something else in my network is causing the issue.  ???

[AMBE_AUDIO]
server = 127.0.0.1                      ; IP address of xx_Bridge.py
fromDMRPort = 31100                     ; AMBE frames from xx_Bridge (should match "toGatewayPort" in xx_Bridge.cfg)
toDMRPort = 31103                       ; AMBE frames from xx_Bridge (should match "fromGatewayPort" in xx_Bridge.cfg)
ambeMode = DMR                          ; DMR, DMR_IPSC, DSTAR, NXDN, P25, YSFN, YSFW
minTxTimeMS = 2500                      ; Minimum time in MS for hang delay
gatewayDmrId = 3101607                        ; ID to use when transmitting from Analog_Bridge
repeaterID = 310160705                          ; ID of source repeater
txTg = 312                             ; 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         

-----------------
[DMR]
Enable=1
ColorCode=1
EmbeddedLCOnly=1
DumpTAData=0
-------------
[DMR Network]
Enable=1
Address=3102.repeater.net
Port=62031
Jitter=360
Local=62032
Password=passw0rd
Slot1=1
Slot2=1
Debug=0
--------------
[1999]
rxchannel = USRP/127.0.0.1:34001:32001

dvswitch.ini
[DMR]
Address = 127.0.0.1             ; Address to send AMBE TLV frames to (export)
TXPort = 31100                  ; Port to send AMBE TLV frames to (export)
RXPort = 31103                  ; Port to listen on (import)
Slot = 2                        ; Export slot


Re: How to configure a ASL server

Alec-N1AJW
 

thank you Steve.


Problem with Allstar to DMR Gateway.

Steve WA0SLL
 

I have built a DMR to Allstar gateway on a Raspberry Pi 3b+ using information from your group, and KV4S.  I can key up my talkgroup on my dmr radio and hear it on the phone portal.  I cannot get the Phone portal to transmit to the DMR.  I see the status change on the Brandmister Dashboard, but it has no audio on the hoseline nor does it key the DMR Repeater.  Any Ideas?


Stephen L. Lechliter
WAØSLL, Amateur Radio General Class
913-596-8038


Re: How to configure a ASL server

Steve N4IRS
 

Alec,
The ASL <-> DMR how to will show you how to add a second node https://docs.google.com/document/d/1eN50Csr29eAprBu7eKA0Bfa2XUcsXw5iktY1Ey-Qjkg/edit?usp=sharing

Steve

On 6/11/2018 12:15 PM, Alec J Wasserman wrote:
do you have a template that has two nodes on it?  i actually want to move my ASL link to my other server with a node.  I looked for a template online for two nodes.  I know very little about ASL to know where to just add 2nd node.  

Alec
N1AJW


Re: How to configure a ASL server

Alec-N1AJW
 

do you have a template that has two nodes on it?  i actually want to move my ASL link to my other server with a node.  I looked for a template online for two nodes.  I know very little about ASL to know where to just add 2nd node.  

Alec
N1AJW


Re: How to configure a ASL server

Mike KB8JNM
 

The advantage is nobody from the outside can connect if that is what is required.
When you want that, then connect it to a public node. You have more choices.
Going to be more node security issues as we move forward with more people with knowledge on how the system works.
Just my half cent.
You gotta do what works for your situation and get along peacefully with your neighbors.


Re: How to configure a ASL server

Steve N4IRS
 

Jeff,
I don't think you are overthinking it at all. I don't make too many outgoing EL connections so it has not been a issue for me. We can look at possibilities to streamline operation. That is the power of ASL.

Steve

On 6/11/2018 9:49 AM, Jeff Lehman, KC8QCH wrote:

Steve, Jose, Et Al,

 

I’ve been mulling this in my head for the last half hour because I like the idea of the concept, but there is one disadvantage I see to connecting echolink to a separate private node vs connecting it directly to the node itself. To make outgoing echolink connections you would need to use the remote command and then dial out. If you are on a different node and need to dial out you would need to set remote twice…

 

So in other words. Public node is 12345. Your private echolink node is 1999. If you are connected to 12345 via say Zoiper or RF, you would need to *41999 – wait for confirmation and then dial *33<Elnodenumber> and then # to exit remote mode.

 

Example 2: Say you care connected to 12345 from 67890. From 67890 you would need to issue *412345 to gain remote mode on 12345 and then *41999 to gain remote mode on your echolink connection. Then *33<elnode number> to dial out. Then # and then # again to close remote modes coming back out. And you need to remember which node you are controlling at the time. Plus if you have telem announcements on….this could get messy quickly.

 

Don’t get me wrong, the idea of having one ASL node and then using multiple private nodes to tie things together to turn features on and off on the fly is pretty cool. But am I just overthinking the private node for EL thing?  I know that it is really no different then tying a DMR bridge in via a private node, but with El, since you can issue dialout commands? I’m probably over thinking this aren’t i?

 

Again this my just my thoughts and 2 cents….Feel  free to ignore me and take what I Have with a grain of salt LOL. I Promise I won’t be offended.

 

   Jeff

 

From: main@DVSwitch.groups.io <main@DVSwitch.groups.io> On Behalf Of TG9AOR
Sent: Monday, June 11, 2018 08:48
To: main@DVSwitch.groups.io
Subject: Re: [DVSwitch] How to configure a ASL server

 

Oh yes it does help. Many thanks.. I could then make 1999 the echolink connection, 1998 the DMR connection, and my node 48270 which is the AllStarlink node may have these added features on to it via CLI and so making it a straight AllStar node or an enhanced AllStar node. I have been reading the AllStar documentation, as well as the AllStar Wiki. I am liking it very much.
--
José Roberto Ruíz García Salas
TG9AOR



Re: How to configure a ASL server

Jeff Lehman, N8ACL
 

Steve, Jose, Et Al,

 

I’ve been mulling this in my head for the last half hour because I like the idea of the concept, but there is one disadvantage I see to connecting echolink to a separate private node vs connecting it directly to the node itself. To make outgoing echolink connections you would need to use the remote command and then dial out. If you are on a different node and need to dial out you would need to set remote twice…

 

So in other words. Public node is 12345. Your private echolink node is 1999. If you are connected to 12345 via say Zoiper or RF, you would need to *41999 – wait for confirmation and then dial *33<Elnodenumber> and then # to exit remote mode.

 

Example 2: Say you care connected to 12345 from 67890. From 67890 you would need to issue *412345 to gain remote mode on 12345 and then *41999 to gain remote mode on your echolink connection. Then *33<elnode number> to dial out. Then # and then # again to close remote modes coming back out. And you need to remember which node you are controlling at the time. Plus if you have telem announcements on….this could get messy quickly.

 

Don’t get me wrong, the idea of having one ASL node and then using multiple private nodes to tie things together to turn features on and off on the fly is pretty cool. But am I just overthinking the private node for EL thing?  I know that it is really no different then tying a DMR bridge in via a private node, but with El, since you can issue dialout commands? I’m probably over thinking this aren’t i?

 

Again this my just my thoughts and 2 cents….Feel  free to ignore me and take what I Have with a grain of salt LOL. I Promise I won’t be offended.

 

   Jeff

 

From: main@DVSwitch.groups.io <main@DVSwitch.groups.io> On Behalf Of TG9AOR
Sent: Monday, June 11, 2018 08:48
To: main@DVSwitch.groups.io
Subject: Re: [DVSwitch] How to configure a ASL server

 

Oh yes it does help. Many thanks.. I could then make 1999 the echolink connection, 1998 the DMR connection, and my node 48270 which is the AllStarlink node may have these added features on to it via CLI and so making it a straight AllStar node or an enhanced AllStar node. I have been reading the AllStar documentation, as well as the AllStar Wiki. I am liking it very much.
--
José Roberto Ruíz García Salas
TG9AOR


Re: How to configure a ASL server

TG9AOR
 

Oh yes it does help. Many thanks.. I could then make 1999 the echolink connection, 1998 the DMR connection, and my node 48270 which is the AllStarlink node may have these added features on to it via CLI and so making it a straight AllStar node or an enhanced AllStar node. I have been reading the AllStar documentation, as well as the AllStar Wiki. I am liking it very much.
--
José Roberto Ruíz García Salas
TG9AOR


Re: Turn on logging and view logs ASL

Steve N4IRS
 

Chris,
The ASL log is in /var/log/asterisk/messages
To enable more verbose logging at he the CLI> prompt:

rpt debug level 0 - 7

7 being the most verbose.


On 06/10/2018 12:07 PM, Chris via Groups.Io wrote:
Could someone point me in the right direction as to turning on all the logging that I can in ASL and where to view those logs.
I have a weird little issue cropping up in my DMR to ASL bridge and would like to be able to chase it down.

Chris
WB4ULK

8201 - 8220 of 9795