Date   

Re: System test

K4VL <73dek4vl@...>
 

OK so can you give me some guidance as to where I have these entry's the same? I am looking and cannot find it.

On Fri, Jan 25, 2019 at 5:32 PM Steve N4IRS <szingman@...> wrote:
repeaterID can not be the same as gatewayDmrId

On 1/25/19 6:25 PM, K4VL wrote:
> I: 2019-01-25 23:24:10.846 Analog Bridge is starting
> F: 2019-01-25 23:24:10.846 Repeater ID can not be the same as
> subscriber ID
>





Re: System test

Steve N4IRS
 

repeaterID can not be the same as gatewayDmrId

On 1/25/19 6:25 PM, K4VL wrote:
I: 2019-01-25 23:24:10.846 Analog Bridge is starting
F: 2019-01-25 23:24:10.846 Repeater ID can not be the same as subscriber ID


Re: System test

Steve N4IRS
 

That would help.

On 1/25/19 6:25 PM, K4VL wrote:
I just noticed this when starting Analog_Bridge

I: 2019-01-25 23:24:10.846 Analog Bridge is starting
F: 2019-01-25 23:24:10.846 Repeater ID can not be the same as subscriber ID



On Fri, Jan 25, 2019 at 5:21 PM Steve N4IRS <szingman@...> wrote:
No,
It sets up like any MMDVM hot spot.

On 1/25/19 6:07 PM, K4VL wrote:
I have this build on a PC that has a wired connection to my network. Are there any ports in the router that need to be forwarded besides the ASL port?

On Fri, Jan 25, 2019 at 5:05 PM Steve N4IRS <szingman@...> wrote:
You have a communications problem between MMDVM_Bridge and Analog_Bridge. You also seem to have a issue maintaining a connection to the Master.

On 1/25/19 6:01 PM, K4VL wrote:
This worked before I changed my callsign from AA4II to K4VL. I do get this happening when I key my radio

M: 2019-01-25 22:58:26.343 DMR, Logged into the master successfully
M: 2019-01-25 22:58:38.645 DMR Slot 2, received network voice header from K4VL to    TG 310286
M: 2019-01-25 22:58:39.197 DMR Talker Alias (Data Format 1, Received 6/20 char):    'K4VL D'
M: 2019-01-25 22:58:39.922 DMR Talker Alias (Data Format 1, Received 13/20 char):    'K4VL DMR ID: '
M: 2019-01-25 22:58:40.035 DMR Slot 2, received network end of voice transmission   , 1.6 seconds, 0% packet loss, BER: 0.0%
M: 2019-01-25 22:59:13.768 DMR Slot 2, received network voice header from K4VL to TG 310286
M: 2019-01-25 22:59:14.479 DMR Talker Alias (Data Format 1, Received 6/20 char): 'K4VL D'
M: 2019-01-25 22:59:15.198 DMR Talker Alias (Data Format 1, Received 13/20 char): 'K4VL DMR ID: '
M: 2019-01-25 22:59:15.918 DMR Talker Alias (Data Format 1, Received 20/20 char): 'K4VL DMR ID: 3116280'
D: 2019-01-25 22:59:17.165 DMR Slot 2, lost audio for 766ms filling in
M: 2019-01-25 22:59:17.569 DMR Slot 2, received network end of voice transmission, 3

Analog_Bridge does not change when I key the radio.

On Fri, Jan 25, 2019 at 4:33 PM K4VL via Groups.Io <73dek4vl=gmail.com@groups.io> wrote:
So when it says logged into Master successfully it's not really logged in correct?

On Fri, Jan 25, 2019, 4:26 PM Steve N4IRS <szingman@...> wrote:
No it is not normal. it is never logging in.


On 1/25/19 5:11 PM, K4VL wrote:
Is the amount of times my MMDVM_Bridge's login fail normal. I am letting it run and this ir what I see.

M: 2019-01-25 21:54:54.590 DMR, Logged into the master successfully
W: 2019-01-25 21:55:54.650 DMR, Login to the master has failed, retrying login ...
E: 2019-01-25 21:56:54.689 DMR, Connection to the master has timed out, retrying connection
M: 2019-01-25 21:56:54.689 DMR, Closing DMR Network
M: 2019-01-25 21:56:54.689 DMR, Opening DMR Network
D: 2019-01-25 21:57:04.732 DMR, Sending authorisation
D: 2019-01-25 21:57:04.768 DMR, Sending configuration
M: 2019-01-25 21:57:04.799 DMR, Logged into the master successfully
W: 2019-01-25 21:58:04.876 DMR, Login to the master has failed, retrying login ...
E: 2019-01-25 21:59:04.915 DMR, Connection to the master has timed out, retrying connection
M: 2019-01-25 21:59:04.916 DMR, Closing DMR Network
M: 2019-01-25 21:59:04.916 DMR, Opening DMR Network
D: 2019-01-25 21:59:14.963 DMR, Sending authorisation
D: 2019-01-25 21:59:14.993 DMR, Sending configuration
M: 2019-01-25 21:59:15.029 DMR, Logged into the master successfully
W: 2019-01-25 22:00:15.095 DMR, Login to the master has failed, retrying login ...
E: 2019-01-25 22:01:15.131 DMR, Connection to the master has timed out, retrying connection
M: 2019-01-25 22:01:15.131 DMR, Closing DMR Network
M: 2019-01-25 22:01:15.131 DMR, Opening DMR Network
D: 2019-01-25 22:01:25.175 DMR, Sending authorisation
D: 2019-01-25 22:01:25.210 DMR, Sending configuration
M: 2019-01-25 22:01:25.241 DMR, Logged into the master successfully
W: 2019-01-25 22:02:25.317 DMR, Login to the master has failed, retrying login ...
E: 2019-01-25 22:03:25.349 DMR, Connection to the master has timed out, retrying connection
M: 2019-01-25 22:03:25.349 DMR, Closing DMR Network
M: 2019-01-25 22:03:25.349 DMR, Opening DMR Network
D: 2019-01-25 22:03:35.386 DMR, Sending authorisation
D: 2019-01-25 22:03:35.416 DMR, Sending configuration
M: 2019-01-25 22:03:35.447 DMR, Logged into the master successfully
W: 2019-01-25 22:04:35.521 DMR, Login to the master has failed, retrying login ...
E: 2019-01-25 22:05:35.570 DMR, Connection to the master has timed out, retrying connection
M: 2019-01-25 22:05:35.571 DMR, Closing DMR Network
M: 2019-01-25 22:05:35.571 DMR, Opening DMR Network
D: 2019-01-25 22:05:45.609 DMR, Sending authorisation
D: 2019-01-25 22:05:45.644 DMR, Sending configuration
M: 2019-01-25 22:05:45.675 DMR, Logged into the master successfully
W: 2019-01-25 22:06:45.767 DMR, Login to the master has failed, retrying login ...
^CM: 2019-01-25 22:07:36.791 Closing the MMDVM
I: 2019-01-25 22:07:37.307 Stopped the DMR Id lookup reload thread
M: 2019-01-25 22:07:37.308 DMR, Closing DMR Network
I: 2019-01-25 22:07:37.308 MMDVM_Bridge-20180423 exited on receipt of SIGINT
root@K4VL-DMR_Bridge:/opt/MMDVM_Bridge#


On Wed, Jan 23, 2019 at 7:04 PM K4VL via Groups.Io <73dek4vl=gmail.com@groups.io> wrote:
Everything appears to work except When I transmit I see activity on
MMDVM_Bridge but not Analog_Bridge. It worked in the past when others
connected to me. I just can't get my radio to work. My radio is working on
other talkgroups.

On Wed, Jan 23, 2019 at 6:13 PM Steve N4IRS <szingman@...> wrote:
That looks OK.

Did the bridge ever work.
Did you follow the howto including the testing at each step?

On 1/23/19 6:17 PM, K4VL wrote:
DVSwitch.ini


; Configure the DMR Partner
; Audio format is AMBE 72 bit
[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

Analog_Bridge.ini

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



Virus-free. www.avg.com

On Wed, Jan 23, 2019 at 4:27 PM Steve N4IRS <szingman@...> wrote:
Did the bridge ever work.
Did you follow the howto including the testing at each step?
Please post the following. Post the [DMR] stanza of DVSwitch.ini and the [AMBE_AUDIO] stanza of Analog_Bridge.ini

Steve


On 1/23/19 4:16 PM, K4VL wrote:
Everything appears to be correct based on the ASL to DMR Bridge document

On Wed, Jan 23, 2019 at 2:56 PM Steve N4IRS <szingman@...> wrote:
Check the port numbers between MMDVM_Bridge and Analog_Bridge.

On 1/23/2019 3:55 PM, K4VL wrote:
After running both MMDVM_Bridge and Analog_Bridge in the foreground, I can keyup and see it in MMDVM_Bridge but nothing in Analog_Bridge

On Wed, Jan 23, 2019 at 2:28 PM K4VL via Groups.Io <73dek4vl=gmail.com@groups.io> wrote:
I just saw the search at the top of the last heard page and added a search for my call. I see my attempts now

On Wed, Jan 23, 2019 at 2:15 PM Corey Dean N3FE <n3fe@...> wrote:
Why not just watch last heard?  Use a rule in it and watch your traffic that way.

Corey  N3FE

On Wed, Jan 23, 2019 at 3:08 PM K4VL <73dek4vl@...> wrote:
With hoseline not working is there anyway I can see these logs when I login?

On Wed, Jan 23, 2019 at 2:02 PM Corey Dean N3FE <n3fe@...> wrote:
I don’t want to post the logs here as it has your ip address in it, but I can confirm you have connected and disconnected many times in the last few hours.  I also see where traffic was coming from bm toward you a few times but I didn’t not verify the talkgroup.

Corey n3fe

On Wed, Jan 23, 2019 at 2:57 PM K4VL <73dek4vl@...> wrote:
My server is setup as 311628005 and my talkgroup is 310286

On Wed, Jan 23, 2019 at 1:56 PM Corey Dean N3FE <n3fe@...> wrote:
Your id you are using to connect to 3108 with?

On Wed, Jan 23, 2019 at 2:45 PM K4VL <73dek4vl@...> wrote:
3108

On Wed, Jan 23, 2019 at 1:42 PM Corey Dean N3FE <n3fe@...> wrote:
What master are you trying to connect to?

Corey n3fe

On Wed, Jan 23, 2019 at 2:37 PM K4VL <73dek4vl@...> wrote:
I was wondering... Could my problem be that  my gatewayDmrId in the Analog_Bridge.ini is the same as the Radio ID in my handheld radio? Do I need to get another DMR ID?

On Wed, Jan 23, 2019 at 1:31 PM Steve N4IRS <szingman@...> wrote:
These are the items in MMDVM_Bridge.in that deal with logging into a Master:
[General]
Callsign=W1AW
Id=3112111
Duplex=0

[DMR Network]
Enable=1
Address=310x.repeater.net
Port=62031
Jitter=500
Local=62032
Password=passw0rd
Slot1=1
Slot2=1
Debug=0




On 1/23/2019 2:26 PM, K4VL wrote:
The password under DMR Network is correct

On Wed, Jan 23, 2019 at 1:22 PM Steve N4IRS <szingman@...> wrote:
Check your password. Should be passw0rd Notice the 0

On 1/23/2019 2:20 PM, K4VL wrote:
OK I can see when I key up the last line that comes up says Login to master has failed, retrying login ...

On Wed, Jan 23, 2019 at 1:11 PM Steve N4IRS <szingman@...> wrote:
Run the program(s) in the foreground to look for errors.
Running the program in the foreground simply means starting the program from the command prompt.
Example: root@myhost:/opt/MMDVM_Bridge# ./MMDVM_Host MMDVM.ini This runs the program from the prompt. Notice the ./ in front of the program name. This means run the program in this directory.

On 1/23/2019 2:09 PM, K4VL wrote:
forgive my ignorance but I don't know how to run it in the foreground

On Wed, Jan 23, 2019 at 1:06 PM Steve N4IRS <szingman@...> wrote:
Hoseline has been up and down. First check your self care page and make sure MMDVM_Bridge is logged in to BM. Running MMDVM_Bridge in the foreground will also tell you if it is connected to BM.

On 1/23/2019 2:04 PM, K4VL wrote:
I did see that I am connected to Brandmeister it has me wondering if my radio is not programmed correctly. I did also try to click on hoseline and got a 503 service unavailable page.

On Wed, Jan 23, 2019 at 12:50 PM Steve N4IRS <szingman@...> wrote:
Not a lot of information to go on but in general:
Run each program in the foreground so you can see what is happening. Start at one end and work to the other end.

Steve

On 1/23/2019 1:42 PM, K4VL wrote:
I was wondering how to test my bridge? I don't seem to be getting to it through my hotspot. I went to the CLI and keyed my radio and nothing showed up. My server is setup as 311628005 and my talkgroup is 310286.

Thanks








Virus-free. www.avg.com






Re: System test

K4VL <73dek4vl@...>
 

I just noticed this when starting Analog_Bridge

I: 2019-01-25 23:24:10.846 Analog Bridge is starting
F: 2019-01-25 23:24:10.846 Repeater ID can not be the same as subscriber ID



On Fri, Jan 25, 2019 at 5:21 PM Steve N4IRS <szingman@...> wrote:
No,
It sets up like any MMDVM hot spot.

On 1/25/19 6:07 PM, K4VL wrote:
I have this build on a PC that has a wired connection to my network. Are there any ports in the router that need to be forwarded besides the ASL port?

On Fri, Jan 25, 2019 at 5:05 PM Steve N4IRS <szingman@...> wrote:
You have a communications problem between MMDVM_Bridge and Analog_Bridge. You also seem to have a issue maintaining a connection to the Master.

On 1/25/19 6:01 PM, K4VL wrote:
This worked before I changed my callsign from AA4II to K4VL. I do get this happening when I key my radio

M: 2019-01-25 22:58:26.343 DMR, Logged into the master successfully
M: 2019-01-25 22:58:38.645 DMR Slot 2, received network voice header from K4VL to    TG 310286
M: 2019-01-25 22:58:39.197 DMR Talker Alias (Data Format 1, Received 6/20 char):    'K4VL D'
M: 2019-01-25 22:58:39.922 DMR Talker Alias (Data Format 1, Received 13/20 char):    'K4VL DMR ID: '
M: 2019-01-25 22:58:40.035 DMR Slot 2, received network end of voice transmission   , 1.6 seconds, 0% packet loss, BER: 0.0%
M: 2019-01-25 22:59:13.768 DMR Slot 2, received network voice header from K4VL to TG 310286
M: 2019-01-25 22:59:14.479 DMR Talker Alias (Data Format 1, Received 6/20 char): 'K4VL D'
M: 2019-01-25 22:59:15.198 DMR Talker Alias (Data Format 1, Received 13/20 char): 'K4VL DMR ID: '
M: 2019-01-25 22:59:15.918 DMR Talker Alias (Data Format 1, Received 20/20 char): 'K4VL DMR ID: 3116280'
D: 2019-01-25 22:59:17.165 DMR Slot 2, lost audio for 766ms filling in
M: 2019-01-25 22:59:17.569 DMR Slot 2, received network end of voice transmission, 3

Analog_Bridge does not change when I key the radio.

On Fri, Jan 25, 2019 at 4:33 PM K4VL via Groups.Io <73dek4vl=gmail.com@groups.io> wrote:
So when it says logged into Master successfully it's not really logged in correct?

On Fri, Jan 25, 2019, 4:26 PM Steve N4IRS <szingman@...> wrote:
No it is not normal. it is never logging in.


On 1/25/19 5:11 PM, K4VL wrote:
Is the amount of times my MMDVM_Bridge's login fail normal. I am letting it run and this ir what I see.

M: 2019-01-25 21:54:54.590 DMR, Logged into the master successfully
W: 2019-01-25 21:55:54.650 DMR, Login to the master has failed, retrying login ...
E: 2019-01-25 21:56:54.689 DMR, Connection to the master has timed out, retrying connection
M: 2019-01-25 21:56:54.689 DMR, Closing DMR Network
M: 2019-01-25 21:56:54.689 DMR, Opening DMR Network
D: 2019-01-25 21:57:04.732 DMR, Sending authorisation
D: 2019-01-25 21:57:04.768 DMR, Sending configuration
M: 2019-01-25 21:57:04.799 DMR, Logged into the master successfully
W: 2019-01-25 21:58:04.876 DMR, Login to the master has failed, retrying login ...
E: 2019-01-25 21:59:04.915 DMR, Connection to the master has timed out, retrying connection
M: 2019-01-25 21:59:04.916 DMR, Closing DMR Network
M: 2019-01-25 21:59:04.916 DMR, Opening DMR Network
D: 2019-01-25 21:59:14.963 DMR, Sending authorisation
D: 2019-01-25 21:59:14.993 DMR, Sending configuration
M: 2019-01-25 21:59:15.029 DMR, Logged into the master successfully
W: 2019-01-25 22:00:15.095 DMR, Login to the master has failed, retrying login ...
E: 2019-01-25 22:01:15.131 DMR, Connection to the master has timed out, retrying connection
M: 2019-01-25 22:01:15.131 DMR, Closing DMR Network
M: 2019-01-25 22:01:15.131 DMR, Opening DMR Network
D: 2019-01-25 22:01:25.175 DMR, Sending authorisation
D: 2019-01-25 22:01:25.210 DMR, Sending configuration
M: 2019-01-25 22:01:25.241 DMR, Logged into the master successfully
W: 2019-01-25 22:02:25.317 DMR, Login to the master has failed, retrying login ...
E: 2019-01-25 22:03:25.349 DMR, Connection to the master has timed out, retrying connection
M: 2019-01-25 22:03:25.349 DMR, Closing DMR Network
M: 2019-01-25 22:03:25.349 DMR, Opening DMR Network
D: 2019-01-25 22:03:35.386 DMR, Sending authorisation
D: 2019-01-25 22:03:35.416 DMR, Sending configuration
M: 2019-01-25 22:03:35.447 DMR, Logged into the master successfully
W: 2019-01-25 22:04:35.521 DMR, Login to the master has failed, retrying login ...
E: 2019-01-25 22:05:35.570 DMR, Connection to the master has timed out, retrying connection
M: 2019-01-25 22:05:35.571 DMR, Closing DMR Network
M: 2019-01-25 22:05:35.571 DMR, Opening DMR Network
D: 2019-01-25 22:05:45.609 DMR, Sending authorisation
D: 2019-01-25 22:05:45.644 DMR, Sending configuration
M: 2019-01-25 22:05:45.675 DMR, Logged into the master successfully
W: 2019-01-25 22:06:45.767 DMR, Login to the master has failed, retrying login ...
^CM: 2019-01-25 22:07:36.791 Closing the MMDVM
I: 2019-01-25 22:07:37.307 Stopped the DMR Id lookup reload thread
M: 2019-01-25 22:07:37.308 DMR, Closing DMR Network
I: 2019-01-25 22:07:37.308 MMDVM_Bridge-20180423 exited on receipt of SIGINT
root@K4VL-DMR_Bridge:/opt/MMDVM_Bridge#


On Wed, Jan 23, 2019 at 7:04 PM K4VL via Groups.Io <73dek4vl=gmail.com@groups.io> wrote:
Everything appears to work except When I transmit I see activity on
MMDVM_Bridge but not Analog_Bridge. It worked in the past when others
connected to me. I just can't get my radio to work. My radio is working on
other talkgroups.

On Wed, Jan 23, 2019 at 6:13 PM Steve N4IRS <szingman@...> wrote:
That looks OK.

Did the bridge ever work.
Did you follow the howto including the testing at each step?

On 1/23/19 6:17 PM, K4VL wrote:
DVSwitch.ini


; Configure the DMR Partner
; Audio format is AMBE 72 bit
[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

Analog_Bridge.ini

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



Virus-free. www.avg.com

On Wed, Jan 23, 2019 at 4:27 PM Steve N4IRS <szingman@...> wrote:
Did the bridge ever work.
Did you follow the howto including the testing at each step?
Please post the following. Post the [DMR] stanza of DVSwitch.ini and the [AMBE_AUDIO] stanza of Analog_Bridge.ini

Steve


On 1/23/19 4:16 PM, K4VL wrote:
Everything appears to be correct based on the ASL to DMR Bridge document

On Wed, Jan 23, 2019 at 2:56 PM Steve N4IRS <szingman@...> wrote:
Check the port numbers between MMDVM_Bridge and Analog_Bridge.

On 1/23/2019 3:55 PM, K4VL wrote:
After running both MMDVM_Bridge and Analog_Bridge in the foreground, I can keyup and see it in MMDVM_Bridge but nothing in Analog_Bridge

On Wed, Jan 23, 2019 at 2:28 PM K4VL via Groups.Io <73dek4vl=gmail.com@groups.io> wrote:
I just saw the search at the top of the last heard page and added a search for my call. I see my attempts now

On Wed, Jan 23, 2019 at 2:15 PM Corey Dean N3FE <n3fe@...> wrote:
Why not just watch last heard?  Use a rule in it and watch your traffic that way.

Corey  N3FE

On Wed, Jan 23, 2019 at 3:08 PM K4VL <73dek4vl@...> wrote:
With hoseline not working is there anyway I can see these logs when I login?

On Wed, Jan 23, 2019 at 2:02 PM Corey Dean N3FE <n3fe@...> wrote:
I don’t want to post the logs here as it has your ip address in it, but I can confirm you have connected and disconnected many times in the last few hours.  I also see where traffic was coming from bm toward you a few times but I didn’t not verify the talkgroup.

Corey n3fe

On Wed, Jan 23, 2019 at 2:57 PM K4VL <73dek4vl@...> wrote:
My server is setup as 311628005 and my talkgroup is 310286

On Wed, Jan 23, 2019 at 1:56 PM Corey Dean N3FE <n3fe@...> wrote:
Your id you are using to connect to 3108 with?

On Wed, Jan 23, 2019 at 2:45 PM K4VL <73dek4vl@...> wrote:
3108

On Wed, Jan 23, 2019 at 1:42 PM Corey Dean N3FE <n3fe@...> wrote:
What master are you trying to connect to?

Corey n3fe

On Wed, Jan 23, 2019 at 2:37 PM K4VL <73dek4vl@...> wrote:
I was wondering... Could my problem be that  my gatewayDmrId in the Analog_Bridge.ini is the same as the Radio ID in my handheld radio? Do I need to get another DMR ID?

On Wed, Jan 23, 2019 at 1:31 PM Steve N4IRS <szingman@...> wrote:
These are the items in MMDVM_Bridge.in that deal with logging into a Master:
[General]
Callsign=W1AW
Id=3112111
Duplex=0

[DMR Network]
Enable=1
Address=310x.repeater.net
Port=62031
Jitter=500
Local=62032
Password=passw0rd
Slot1=1
Slot2=1
Debug=0




On 1/23/2019 2:26 PM, K4VL wrote:
The password under DMR Network is correct

On Wed, Jan 23, 2019 at 1:22 PM Steve N4IRS <szingman@...> wrote:
Check your password. Should be passw0rd Notice the 0

On 1/23/2019 2:20 PM, K4VL wrote:
OK I can see when I key up the last line that comes up says Login to master has failed, retrying login ...

On Wed, Jan 23, 2019 at 1:11 PM Steve N4IRS <szingman@...> wrote:
Run the program(s) in the foreground to look for errors.
Running the program in the foreground simply means starting the program from the command prompt.
Example: root@myhost:/opt/MMDVM_Bridge# ./MMDVM_Host MMDVM.ini This runs the program from the prompt. Notice the ./ in front of the program name. This means run the program in this directory.

On 1/23/2019 2:09 PM, K4VL wrote:
forgive my ignorance but I don't know how to run it in the foreground

On Wed, Jan 23, 2019 at 1:06 PM Steve N4IRS <szingman@...> wrote:
Hoseline has been up and down. First check your self care page and make sure MMDVM_Bridge is logged in to BM. Running MMDVM_Bridge in the foreground will also tell you if it is connected to BM.

On 1/23/2019 2:04 PM, K4VL wrote:
I did see that I am connected to Brandmeister it has me wondering if my radio is not programmed correctly. I did also try to click on hoseline and got a 503 service unavailable page.

On Wed, Jan 23, 2019 at 12:50 PM Steve N4IRS <szingman@...> wrote:
Not a lot of information to go on but in general:
Run each program in the foreground so you can see what is happening. Start at one end and work to the other end.

Steve

On 1/23/2019 1:42 PM, K4VL wrote:
I was wondering how to test my bridge? I don't seem to be getting to it through my hotspot. I went to the CLI and keyed my radio and nothing showed up. My server is setup as 311628005 and my talkgroup is 310286.

Thanks








Virus-free. www.avg.com





Re: System test

Steve N4IRS
 

No,
It sets up like any MMDVM hot spot.

On 1/25/19 6:07 PM, K4VL wrote:
I have this build on a PC that has a wired connection to my network. Are there any ports in the router that need to be forwarded besides the ASL port?

On Fri, Jan 25, 2019 at 5:05 PM Steve N4IRS <szingman@...> wrote:
You have a communications problem between MMDVM_Bridge and Analog_Bridge. You also seem to have a issue maintaining a connection to the Master.

On 1/25/19 6:01 PM, K4VL wrote:
This worked before I changed my callsign from AA4II to K4VL. I do get this happening when I key my radio

M: 2019-01-25 22:58:26.343 DMR, Logged into the master successfully
M: 2019-01-25 22:58:38.645 DMR Slot 2, received network voice header from K4VL to    TG 310286
M: 2019-01-25 22:58:39.197 DMR Talker Alias (Data Format 1, Received 6/20 char):    'K4VL D'
M: 2019-01-25 22:58:39.922 DMR Talker Alias (Data Format 1, Received 13/20 char):    'K4VL DMR ID: '
M: 2019-01-25 22:58:40.035 DMR Slot 2, received network end of voice transmission   , 1.6 seconds, 0% packet loss, BER: 0.0%
M: 2019-01-25 22:59:13.768 DMR Slot 2, received network voice header from K4VL to TG 310286
M: 2019-01-25 22:59:14.479 DMR Talker Alias (Data Format 1, Received 6/20 char): 'K4VL D'
M: 2019-01-25 22:59:15.198 DMR Talker Alias (Data Format 1, Received 13/20 char): 'K4VL DMR ID: '
M: 2019-01-25 22:59:15.918 DMR Talker Alias (Data Format 1, Received 20/20 char): 'K4VL DMR ID: 3116280'
D: 2019-01-25 22:59:17.165 DMR Slot 2, lost audio for 766ms filling in
M: 2019-01-25 22:59:17.569 DMR Slot 2, received network end of voice transmission, 3

Analog_Bridge does not change when I key the radio.

On Fri, Jan 25, 2019 at 4:33 PM K4VL via Groups.Io <73dek4vl=gmail.com@groups.io> wrote:
So when it says logged into Master successfully it's not really logged in correct?

On Fri, Jan 25, 2019, 4:26 PM Steve N4IRS <szingman@...> wrote:
No it is not normal. it is never logging in.


On 1/25/19 5:11 PM, K4VL wrote:
Is the amount of times my MMDVM_Bridge's login fail normal. I am letting it run and this ir what I see.

M: 2019-01-25 21:54:54.590 DMR, Logged into the master successfully
W: 2019-01-25 21:55:54.650 DMR, Login to the master has failed, retrying login ...
E: 2019-01-25 21:56:54.689 DMR, Connection to the master has timed out, retrying connection
M: 2019-01-25 21:56:54.689 DMR, Closing DMR Network
M: 2019-01-25 21:56:54.689 DMR, Opening DMR Network
D: 2019-01-25 21:57:04.732 DMR, Sending authorisation
D: 2019-01-25 21:57:04.768 DMR, Sending configuration
M: 2019-01-25 21:57:04.799 DMR, Logged into the master successfully
W: 2019-01-25 21:58:04.876 DMR, Login to the master has failed, retrying login ...
E: 2019-01-25 21:59:04.915 DMR, Connection to the master has timed out, retrying connection
M: 2019-01-25 21:59:04.916 DMR, Closing DMR Network
M: 2019-01-25 21:59:04.916 DMR, Opening DMR Network
D: 2019-01-25 21:59:14.963 DMR, Sending authorisation
D: 2019-01-25 21:59:14.993 DMR, Sending configuration
M: 2019-01-25 21:59:15.029 DMR, Logged into the master successfully
W: 2019-01-25 22:00:15.095 DMR, Login to the master has failed, retrying login ...
E: 2019-01-25 22:01:15.131 DMR, Connection to the master has timed out, retrying connection
M: 2019-01-25 22:01:15.131 DMR, Closing DMR Network
M: 2019-01-25 22:01:15.131 DMR, Opening DMR Network
D: 2019-01-25 22:01:25.175 DMR, Sending authorisation
D: 2019-01-25 22:01:25.210 DMR, Sending configuration
M: 2019-01-25 22:01:25.241 DMR, Logged into the master successfully
W: 2019-01-25 22:02:25.317 DMR, Login to the master has failed, retrying login ...
E: 2019-01-25 22:03:25.349 DMR, Connection to the master has timed out, retrying connection
M: 2019-01-25 22:03:25.349 DMR, Closing DMR Network
M: 2019-01-25 22:03:25.349 DMR, Opening DMR Network
D: 2019-01-25 22:03:35.386 DMR, Sending authorisation
D: 2019-01-25 22:03:35.416 DMR, Sending configuration
M: 2019-01-25 22:03:35.447 DMR, Logged into the master successfully
W: 2019-01-25 22:04:35.521 DMR, Login to the master has failed, retrying login ...
E: 2019-01-25 22:05:35.570 DMR, Connection to the master has timed out, retrying connection
M: 2019-01-25 22:05:35.571 DMR, Closing DMR Network
M: 2019-01-25 22:05:35.571 DMR, Opening DMR Network
D: 2019-01-25 22:05:45.609 DMR, Sending authorisation
D: 2019-01-25 22:05:45.644 DMR, Sending configuration
M: 2019-01-25 22:05:45.675 DMR, Logged into the master successfully
W: 2019-01-25 22:06:45.767 DMR, Login to the master has failed, retrying login ...
^CM: 2019-01-25 22:07:36.791 Closing the MMDVM
I: 2019-01-25 22:07:37.307 Stopped the DMR Id lookup reload thread
M: 2019-01-25 22:07:37.308 DMR, Closing DMR Network
I: 2019-01-25 22:07:37.308 MMDVM_Bridge-20180423 exited on receipt of SIGINT
root@K4VL-DMR_Bridge:/opt/MMDVM_Bridge#


On Wed, Jan 23, 2019 at 7:04 PM K4VL via Groups.Io <73dek4vl=gmail.com@groups.io> wrote:
Everything appears to work except When I transmit I see activity on
MMDVM_Bridge but not Analog_Bridge. It worked in the past when others
connected to me. I just can't get my radio to work. My radio is working on
other talkgroups.

On Wed, Jan 23, 2019 at 6:13 PM Steve N4IRS <szingman@...> wrote:
That looks OK.

Did the bridge ever work.
Did you follow the howto including the testing at each step?

On 1/23/19 6:17 PM, K4VL wrote:
DVSwitch.ini


; Configure the DMR Partner
; Audio format is AMBE 72 bit
[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

Analog_Bridge.ini

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



Virus-free. www.avg.com

On Wed, Jan 23, 2019 at 4:27 PM Steve N4IRS <szingman@...> wrote:
Did the bridge ever work.
Did you follow the howto including the testing at each step?
Please post the following. Post the [DMR] stanza of DVSwitch.ini and the [AMBE_AUDIO] stanza of Analog_Bridge.ini

Steve


On 1/23/19 4:16 PM, K4VL wrote:
Everything appears to be correct based on the ASL to DMR Bridge document

On Wed, Jan 23, 2019 at 2:56 PM Steve N4IRS <szingman@...> wrote:
Check the port numbers between MMDVM_Bridge and Analog_Bridge.

On 1/23/2019 3:55 PM, K4VL wrote:
After running both MMDVM_Bridge and Analog_Bridge in the foreground, I can keyup and see it in MMDVM_Bridge but nothing in Analog_Bridge

On Wed, Jan 23, 2019 at 2:28 PM K4VL via Groups.Io <73dek4vl=gmail.com@groups.io> wrote:
I just saw the search at the top of the last heard page and added a search for my call. I see my attempts now

On Wed, Jan 23, 2019 at 2:15 PM Corey Dean N3FE <n3fe@...> wrote:
Why not just watch last heard?  Use a rule in it and watch your traffic that way.

Corey  N3FE

On Wed, Jan 23, 2019 at 3:08 PM K4VL <73dek4vl@...> wrote:
With hoseline not working is there anyway I can see these logs when I login?

On Wed, Jan 23, 2019 at 2:02 PM Corey Dean N3FE <n3fe@...> wrote:
I don’t want to post the logs here as it has your ip address in it, but I can confirm you have connected and disconnected many times in the last few hours.  I also see where traffic was coming from bm toward you a few times but I didn’t not verify the talkgroup.

Corey n3fe

On Wed, Jan 23, 2019 at 2:57 PM K4VL <73dek4vl@...> wrote:
My server is setup as 311628005 and my talkgroup is 310286

On Wed, Jan 23, 2019 at 1:56 PM Corey Dean N3FE <n3fe@...> wrote:
Your id you are using to connect to 3108 with?

On Wed, Jan 23, 2019 at 2:45 PM K4VL <73dek4vl@...> wrote:
3108

On Wed, Jan 23, 2019 at 1:42 PM Corey Dean N3FE <n3fe@...> wrote:
What master are you trying to connect to?

Corey n3fe

On Wed, Jan 23, 2019 at 2:37 PM K4VL <73dek4vl@...> wrote:
I was wondering... Could my problem be that  my gatewayDmrId in the Analog_Bridge.ini is the same as the Radio ID in my handheld radio? Do I need to get another DMR ID?

On Wed, Jan 23, 2019 at 1:31 PM Steve N4IRS <szingman@...> wrote:
These are the items in MMDVM_Bridge.in that deal with logging into a Master:
[General]
Callsign=W1AW
Id=3112111
Duplex=0

[DMR Network]
Enable=1
Address=310x.repeater.net
Port=62031
Jitter=500
Local=62032
Password=passw0rd
Slot1=1
Slot2=1
Debug=0




On 1/23/2019 2:26 PM, K4VL wrote:
The password under DMR Network is correct

On Wed, Jan 23, 2019 at 1:22 PM Steve N4IRS <szingman@...> wrote:
Check your password. Should be passw0rd Notice the 0

On 1/23/2019 2:20 PM, K4VL wrote:
OK I can see when I key up the last line that comes up says Login to master has failed, retrying login ...

On Wed, Jan 23, 2019 at 1:11 PM Steve N4IRS <szingman@...> wrote:
Run the program(s) in the foreground to look for errors.
Running the program in the foreground simply means starting the program from the command prompt.
Example: root@myhost:/opt/MMDVM_Bridge# ./MMDVM_Host MMDVM.ini This runs the program from the prompt. Notice the ./ in front of the program name. This means run the program in this directory.

On 1/23/2019 2:09 PM, K4VL wrote:
forgive my ignorance but I don't know how to run it in the foreground

On Wed, Jan 23, 2019 at 1:06 PM Steve N4IRS <szingman@...> wrote:
Hoseline has been up and down. First check your self care page and make sure MMDVM_Bridge is logged in to BM. Running MMDVM_Bridge in the foreground will also tell you if it is connected to BM.

On 1/23/2019 2:04 PM, K4VL wrote:
I did see that I am connected to Brandmeister it has me wondering if my radio is not programmed correctly. I did also try to click on hoseline and got a 503 service unavailable page.

On Wed, Jan 23, 2019 at 12:50 PM Steve N4IRS <szingman@...> wrote:
Not a lot of information to go on but in general:
Run each program in the foreground so you can see what is happening. Start at one end and work to the other end.

Steve

On 1/23/2019 1:42 PM, K4VL wrote:
I was wondering how to test my bridge? I don't seem to be getting to it through my hotspot. I went to the CLI and keyed my radio and nothing showed up. My server is setup as 311628005 and my talkgroup is 310286.

Thanks








Virus-free. www.avg.com





Re: System test

K4VL <73dek4vl@...>
 

I have this build on a PC that has a wired connection to my network. Are there any ports in the router that need to be forwarded besides the ASL port?

On Fri, Jan 25, 2019 at 5:05 PM Steve N4IRS <szingman@...> wrote:
You have a communications problem between MMDVM_Bridge and Analog_Bridge. You also seem to have a issue maintaining a connection to the Master.

On 1/25/19 6:01 PM, K4VL wrote:
This worked before I changed my callsign from AA4II to K4VL. I do get this happening when I key my radio

M: 2019-01-25 22:58:26.343 DMR, Logged into the master successfully
M: 2019-01-25 22:58:38.645 DMR Slot 2, received network voice header from K4VL to    TG 310286
M: 2019-01-25 22:58:39.197 DMR Talker Alias (Data Format 1, Received 6/20 char):    'K4VL D'
M: 2019-01-25 22:58:39.922 DMR Talker Alias (Data Format 1, Received 13/20 char):    'K4VL DMR ID: '
M: 2019-01-25 22:58:40.035 DMR Slot 2, received network end of voice transmission   , 1.6 seconds, 0% packet loss, BER: 0.0%
M: 2019-01-25 22:59:13.768 DMR Slot 2, received network voice header from K4VL to TG 310286
M: 2019-01-25 22:59:14.479 DMR Talker Alias (Data Format 1, Received 6/20 char): 'K4VL D'
M: 2019-01-25 22:59:15.198 DMR Talker Alias (Data Format 1, Received 13/20 char): 'K4VL DMR ID: '
M: 2019-01-25 22:59:15.918 DMR Talker Alias (Data Format 1, Received 20/20 char): 'K4VL DMR ID: 3116280'
D: 2019-01-25 22:59:17.165 DMR Slot 2, lost audio for 766ms filling in
M: 2019-01-25 22:59:17.569 DMR Slot 2, received network end of voice transmission, 3

Analog_Bridge does not change when I key the radio.

On Fri, Jan 25, 2019 at 4:33 PM K4VL via Groups.Io <73dek4vl=gmail.com@groups.io> wrote:
So when it says logged into Master successfully it's not really logged in correct?

On Fri, Jan 25, 2019, 4:26 PM Steve N4IRS <szingman@...> wrote:
No it is not normal. it is never logging in.


On 1/25/19 5:11 PM, K4VL wrote:
Is the amount of times my MMDVM_Bridge's login fail normal. I am letting it run and this ir what I see.

M: 2019-01-25 21:54:54.590 DMR, Logged into the master successfully
W: 2019-01-25 21:55:54.650 DMR, Login to the master has failed, retrying login ...
E: 2019-01-25 21:56:54.689 DMR, Connection to the master has timed out, retrying connection
M: 2019-01-25 21:56:54.689 DMR, Closing DMR Network
M: 2019-01-25 21:56:54.689 DMR, Opening DMR Network
D: 2019-01-25 21:57:04.732 DMR, Sending authorisation
D: 2019-01-25 21:57:04.768 DMR, Sending configuration
M: 2019-01-25 21:57:04.799 DMR, Logged into the master successfully
W: 2019-01-25 21:58:04.876 DMR, Login to the master has failed, retrying login ...
E: 2019-01-25 21:59:04.915 DMR, Connection to the master has timed out, retrying connection
M: 2019-01-25 21:59:04.916 DMR, Closing DMR Network
M: 2019-01-25 21:59:04.916 DMR, Opening DMR Network
D: 2019-01-25 21:59:14.963 DMR, Sending authorisation
D: 2019-01-25 21:59:14.993 DMR, Sending configuration
M: 2019-01-25 21:59:15.029 DMR, Logged into the master successfully
W: 2019-01-25 22:00:15.095 DMR, Login to the master has failed, retrying login ...
E: 2019-01-25 22:01:15.131 DMR, Connection to the master has timed out, retrying connection
M: 2019-01-25 22:01:15.131 DMR, Closing DMR Network
M: 2019-01-25 22:01:15.131 DMR, Opening DMR Network
D: 2019-01-25 22:01:25.175 DMR, Sending authorisation
D: 2019-01-25 22:01:25.210 DMR, Sending configuration
M: 2019-01-25 22:01:25.241 DMR, Logged into the master successfully
W: 2019-01-25 22:02:25.317 DMR, Login to the master has failed, retrying login ...
E: 2019-01-25 22:03:25.349 DMR, Connection to the master has timed out, retrying connection
M: 2019-01-25 22:03:25.349 DMR, Closing DMR Network
M: 2019-01-25 22:03:25.349 DMR, Opening DMR Network
D: 2019-01-25 22:03:35.386 DMR, Sending authorisation
D: 2019-01-25 22:03:35.416 DMR, Sending configuration
M: 2019-01-25 22:03:35.447 DMR, Logged into the master successfully
W: 2019-01-25 22:04:35.521 DMR, Login to the master has failed, retrying login ...
E: 2019-01-25 22:05:35.570 DMR, Connection to the master has timed out, retrying connection
M: 2019-01-25 22:05:35.571 DMR, Closing DMR Network
M: 2019-01-25 22:05:35.571 DMR, Opening DMR Network
D: 2019-01-25 22:05:45.609 DMR, Sending authorisation
D: 2019-01-25 22:05:45.644 DMR, Sending configuration
M: 2019-01-25 22:05:45.675 DMR, Logged into the master successfully
W: 2019-01-25 22:06:45.767 DMR, Login to the master has failed, retrying login ...
^CM: 2019-01-25 22:07:36.791 Closing the MMDVM
I: 2019-01-25 22:07:37.307 Stopped the DMR Id lookup reload thread
M: 2019-01-25 22:07:37.308 DMR, Closing DMR Network
I: 2019-01-25 22:07:37.308 MMDVM_Bridge-20180423 exited on receipt of SIGINT
root@K4VL-DMR_Bridge:/opt/MMDVM_Bridge#


On Wed, Jan 23, 2019 at 7:04 PM K4VL via Groups.Io <73dek4vl=gmail.com@groups.io> wrote:
Everything appears to work except When I transmit I see activity on
MMDVM_Bridge but not Analog_Bridge. It worked in the past when others
connected to me. I just can't get my radio to work. My radio is working on
other talkgroups.

On Wed, Jan 23, 2019 at 6:13 PM Steve N4IRS <szingman@...> wrote:
That looks OK.

Did the bridge ever work.
Did you follow the howto including the testing at each step?

On 1/23/19 6:17 PM, K4VL wrote:
DVSwitch.ini


; Configure the DMR Partner
; Audio format is AMBE 72 bit
[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

Analog_Bridge.ini

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



Virus-free. www.avg.com

On Wed, Jan 23, 2019 at 4:27 PM Steve N4IRS <szingman@...> wrote:
Did the bridge ever work.
Did you follow the howto including the testing at each step?
Please post the following. Post the [DMR] stanza of DVSwitch.ini and the [AMBE_AUDIO] stanza of Analog_Bridge.ini

Steve


On 1/23/19 4:16 PM, K4VL wrote:
Everything appears to be correct based on the ASL to DMR Bridge document

On Wed, Jan 23, 2019 at 2:56 PM Steve N4IRS <szingman@...> wrote:
Check the port numbers between MMDVM_Bridge and Analog_Bridge.

On 1/23/2019 3:55 PM, K4VL wrote:
After running both MMDVM_Bridge and Analog_Bridge in the foreground, I can keyup and see it in MMDVM_Bridge but nothing in Analog_Bridge

On Wed, Jan 23, 2019 at 2:28 PM K4VL via Groups.Io <73dek4vl=gmail.com@groups.io> wrote:
I just saw the search at the top of the last heard page and added a search for my call. I see my attempts now

On Wed, Jan 23, 2019 at 2:15 PM Corey Dean N3FE <n3fe@...> wrote:
Why not just watch last heard?  Use a rule in it and watch your traffic that way.

Corey  N3FE

On Wed, Jan 23, 2019 at 3:08 PM K4VL <73dek4vl@...> wrote:
With hoseline not working is there anyway I can see these logs when I login?

On Wed, Jan 23, 2019 at 2:02 PM Corey Dean N3FE <n3fe@...> wrote:
I don’t want to post the logs here as it has your ip address in it, but I can confirm you have connected and disconnected many times in the last few hours.  I also see where traffic was coming from bm toward you a few times but I didn’t not verify the talkgroup.

Corey n3fe

On Wed, Jan 23, 2019 at 2:57 PM K4VL <73dek4vl@...> wrote:
My server is setup as 311628005 and my talkgroup is 310286

On Wed, Jan 23, 2019 at 1:56 PM Corey Dean N3FE <n3fe@...> wrote:
Your id you are using to connect to 3108 with?

On Wed, Jan 23, 2019 at 2:45 PM K4VL <73dek4vl@...> wrote:
3108

On Wed, Jan 23, 2019 at 1:42 PM Corey Dean N3FE <n3fe@...> wrote:
What master are you trying to connect to?

Corey n3fe

On Wed, Jan 23, 2019 at 2:37 PM K4VL <73dek4vl@...> wrote:
I was wondering... Could my problem be that  my gatewayDmrId in the Analog_Bridge.ini is the same as the Radio ID in my handheld radio? Do I need to get another DMR ID?

On Wed, Jan 23, 2019 at 1:31 PM Steve N4IRS <szingman@...> wrote:
These are the items in MMDVM_Bridge.in that deal with logging into a Master:
[General]
Callsign=W1AW
Id=3112111
Duplex=0

[DMR Network]
Enable=1
Address=310x.repeater.net
Port=62031
Jitter=500
Local=62032
Password=passw0rd
Slot1=1
Slot2=1
Debug=0




On 1/23/2019 2:26 PM, K4VL wrote:
The password under DMR Network is correct

On Wed, Jan 23, 2019 at 1:22 PM Steve N4IRS <szingman@...> wrote:
Check your password. Should be passw0rd Notice the 0

On 1/23/2019 2:20 PM, K4VL wrote:
OK I can see when I key up the last line that comes up says Login to master has failed, retrying login ...

On Wed, Jan 23, 2019 at 1:11 PM Steve N4IRS <szingman@...> wrote:
Run the program(s) in the foreground to look for errors.
Running the program in the foreground simply means starting the program from the command prompt.
Example: root@myhost:/opt/MMDVM_Bridge# ./MMDVM_Host MMDVM.ini This runs the program from the prompt. Notice the ./ in front of the program name. This means run the program in this directory.

On 1/23/2019 2:09 PM, K4VL wrote:
forgive my ignorance but I don't know how to run it in the foreground

On Wed, Jan 23, 2019 at 1:06 PM Steve N4IRS <szingman@...> wrote:
Hoseline has been up and down. First check your self care page and make sure MMDVM_Bridge is logged in to BM. Running MMDVM_Bridge in the foreground will also tell you if it is connected to BM.

On 1/23/2019 2:04 PM, K4VL wrote:
I did see that I am connected to Brandmeister it has me wondering if my radio is not programmed correctly. I did also try to click on hoseline and got a 503 service unavailable page.

On Wed, Jan 23, 2019 at 12:50 PM Steve N4IRS <szingman@...> wrote:
Not a lot of information to go on but in general:
Run each program in the foreground so you can see what is happening. Start at one end and work to the other end.

Steve

On 1/23/2019 1:42 PM, K4VL wrote:
I was wondering how to test my bridge? I don't seem to be getting to it through my hotspot. I went to the CLI and keyed my radio and nothing showed up. My server is setup as 311628005 and my talkgroup is 310286.

Thanks








Virus-free. www.avg.com




Re: System test

Steve N4IRS
 

You have a communications problem between MMDVM_Bridge and Analog_Bridge. You also seem to have a issue maintaining a connection to the Master.

On 1/25/19 6:01 PM, K4VL wrote:
This worked before I changed my callsign from AA4II to K4VL. I do get this happening when I key my radio

M: 2019-01-25 22:58:26.343 DMR, Logged into the master successfully
M: 2019-01-25 22:58:38.645 DMR Slot 2, received network voice header from K4VL to    TG 310286
M: 2019-01-25 22:58:39.197 DMR Talker Alias (Data Format 1, Received 6/20 char):    'K4VL D'
M: 2019-01-25 22:58:39.922 DMR Talker Alias (Data Format 1, Received 13/20 char):    'K4VL DMR ID: '
M: 2019-01-25 22:58:40.035 DMR Slot 2, received network end of voice transmission   , 1.6 seconds, 0% packet loss, BER: 0.0%
M: 2019-01-25 22:59:13.768 DMR Slot 2, received network voice header from K4VL to TG 310286
M: 2019-01-25 22:59:14.479 DMR Talker Alias (Data Format 1, Received 6/20 char): 'K4VL D'
M: 2019-01-25 22:59:15.198 DMR Talker Alias (Data Format 1, Received 13/20 char): 'K4VL DMR ID: '
M: 2019-01-25 22:59:15.918 DMR Talker Alias (Data Format 1, Received 20/20 char): 'K4VL DMR ID: 3116280'
D: 2019-01-25 22:59:17.165 DMR Slot 2, lost audio for 766ms filling in
M: 2019-01-25 22:59:17.569 DMR Slot 2, received network end of voice transmission, 3

Analog_Bridge does not change when I key the radio.

On Fri, Jan 25, 2019 at 4:33 PM K4VL via Groups.Io <73dek4vl=gmail.com@groups.io> wrote:
So when it says logged into Master successfully it's not really logged in correct?

On Fri, Jan 25, 2019, 4:26 PM Steve N4IRS <szingman@...> wrote:
No it is not normal. it is never logging in.


On 1/25/19 5:11 PM, K4VL wrote:
Is the amount of times my MMDVM_Bridge's login fail normal. I am letting it run and this ir what I see.

M: 2019-01-25 21:54:54.590 DMR, Logged into the master successfully
W: 2019-01-25 21:55:54.650 DMR, Login to the master has failed, retrying login ...
E: 2019-01-25 21:56:54.689 DMR, Connection to the master has timed out, retrying connection
M: 2019-01-25 21:56:54.689 DMR, Closing DMR Network
M: 2019-01-25 21:56:54.689 DMR, Opening DMR Network
D: 2019-01-25 21:57:04.732 DMR, Sending authorisation
D: 2019-01-25 21:57:04.768 DMR, Sending configuration
M: 2019-01-25 21:57:04.799 DMR, Logged into the master successfully
W: 2019-01-25 21:58:04.876 DMR, Login to the master has failed, retrying login ...
E: 2019-01-25 21:59:04.915 DMR, Connection to the master has timed out, retrying connection
M: 2019-01-25 21:59:04.916 DMR, Closing DMR Network
M: 2019-01-25 21:59:04.916 DMR, Opening DMR Network
D: 2019-01-25 21:59:14.963 DMR, Sending authorisation
D: 2019-01-25 21:59:14.993 DMR, Sending configuration
M: 2019-01-25 21:59:15.029 DMR, Logged into the master successfully
W: 2019-01-25 22:00:15.095 DMR, Login to the master has failed, retrying login ...
E: 2019-01-25 22:01:15.131 DMR, Connection to the master has timed out, retrying connection
M: 2019-01-25 22:01:15.131 DMR, Closing DMR Network
M: 2019-01-25 22:01:15.131 DMR, Opening DMR Network
D: 2019-01-25 22:01:25.175 DMR, Sending authorisation
D: 2019-01-25 22:01:25.210 DMR, Sending configuration
M: 2019-01-25 22:01:25.241 DMR, Logged into the master successfully
W: 2019-01-25 22:02:25.317 DMR, Login to the master has failed, retrying login ...
E: 2019-01-25 22:03:25.349 DMR, Connection to the master has timed out, retrying connection
M: 2019-01-25 22:03:25.349 DMR, Closing DMR Network
M: 2019-01-25 22:03:25.349 DMR, Opening DMR Network
D: 2019-01-25 22:03:35.386 DMR, Sending authorisation
D: 2019-01-25 22:03:35.416 DMR, Sending configuration
M: 2019-01-25 22:03:35.447 DMR, Logged into the master successfully
W: 2019-01-25 22:04:35.521 DMR, Login to the master has failed, retrying login ...
E: 2019-01-25 22:05:35.570 DMR, Connection to the master has timed out, retrying connection
M: 2019-01-25 22:05:35.571 DMR, Closing DMR Network
M: 2019-01-25 22:05:35.571 DMR, Opening DMR Network
D: 2019-01-25 22:05:45.609 DMR, Sending authorisation
D: 2019-01-25 22:05:45.644 DMR, Sending configuration
M: 2019-01-25 22:05:45.675 DMR, Logged into the master successfully
W: 2019-01-25 22:06:45.767 DMR, Login to the master has failed, retrying login ...
^CM: 2019-01-25 22:07:36.791 Closing the MMDVM
I: 2019-01-25 22:07:37.307 Stopped the DMR Id lookup reload thread
M: 2019-01-25 22:07:37.308 DMR, Closing DMR Network
I: 2019-01-25 22:07:37.308 MMDVM_Bridge-20180423 exited on receipt of SIGINT
root@K4VL-DMR_Bridge:/opt/MMDVM_Bridge#


On Wed, Jan 23, 2019 at 7:04 PM K4VL via Groups.Io <73dek4vl=gmail.com@groups.io> wrote:
Everything appears to work except When I transmit I see activity on
MMDVM_Bridge but not Analog_Bridge. It worked in the past when others
connected to me. I just can't get my radio to work. My radio is working on
other talkgroups.

On Wed, Jan 23, 2019 at 6:13 PM Steve N4IRS <szingman@...> wrote:
That looks OK.

Did the bridge ever work.
Did you follow the howto including the testing at each step?

On 1/23/19 6:17 PM, K4VL wrote:
DVSwitch.ini


; Configure the DMR Partner
; Audio format is AMBE 72 bit
[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

Analog_Bridge.ini

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



Virus-free. www.avg.com

On Wed, Jan 23, 2019 at 4:27 PM Steve N4IRS <szingman@...> wrote:
Did the bridge ever work.
Did you follow the howto including the testing at each step?
Please post the following. Post the [DMR] stanza of DVSwitch.ini and the [AMBE_AUDIO] stanza of Analog_Bridge.ini

Steve


On 1/23/19 4:16 PM, K4VL wrote:
Everything appears to be correct based on the ASL to DMR Bridge document

On Wed, Jan 23, 2019 at 2:56 PM Steve N4IRS <szingman@...> wrote:
Check the port numbers between MMDVM_Bridge and Analog_Bridge.

On 1/23/2019 3:55 PM, K4VL wrote:
After running both MMDVM_Bridge and Analog_Bridge in the foreground, I can keyup and see it in MMDVM_Bridge but nothing in Analog_Bridge

On Wed, Jan 23, 2019 at 2:28 PM K4VL via Groups.Io <73dek4vl=gmail.com@groups.io> wrote:
I just saw the search at the top of the last heard page and added a search for my call. I see my attempts now

On Wed, Jan 23, 2019 at 2:15 PM Corey Dean N3FE <n3fe@...> wrote:
Why not just watch last heard?  Use a rule in it and watch your traffic that way.

Corey  N3FE

On Wed, Jan 23, 2019 at 3:08 PM K4VL <73dek4vl@...> wrote:
With hoseline not working is there anyway I can see these logs when I login?

On Wed, Jan 23, 2019 at 2:02 PM Corey Dean N3FE <n3fe@...> wrote:
I don’t want to post the logs here as it has your ip address in it, but I can confirm you have connected and disconnected many times in the last few hours.  I also see where traffic was coming from bm toward you a few times but I didn’t not verify the talkgroup.

Corey n3fe

On Wed, Jan 23, 2019 at 2:57 PM K4VL <73dek4vl@...> wrote:
My server is setup as 311628005 and my talkgroup is 310286

On Wed, Jan 23, 2019 at 1:56 PM Corey Dean N3FE <n3fe@...> wrote:
Your id you are using to connect to 3108 with?

On Wed, Jan 23, 2019 at 2:45 PM K4VL <73dek4vl@...> wrote:
3108

On Wed, Jan 23, 2019 at 1:42 PM Corey Dean N3FE <n3fe@...> wrote:
What master are you trying to connect to?

Corey n3fe

On Wed, Jan 23, 2019 at 2:37 PM K4VL <73dek4vl@...> wrote:
I was wondering... Could my problem be that  my gatewayDmrId in the Analog_Bridge.ini is the same as the Radio ID in my handheld radio? Do I need to get another DMR ID?

On Wed, Jan 23, 2019 at 1:31 PM Steve N4IRS <szingman@...> wrote:
These are the items in MMDVM_Bridge.in that deal with logging into a Master:
[General]
Callsign=W1AW
Id=3112111
Duplex=0

[DMR Network]
Enable=1
Address=310x.repeater.net
Port=62031
Jitter=500
Local=62032
Password=passw0rd
Slot1=1
Slot2=1
Debug=0




On 1/23/2019 2:26 PM, K4VL wrote:
The password under DMR Network is correct

On Wed, Jan 23, 2019 at 1:22 PM Steve N4IRS <szingman@...> wrote:
Check your password. Should be passw0rd Notice the 0

On 1/23/2019 2:20 PM, K4VL wrote:
OK I can see when I key up the last line that comes up says Login to master has failed, retrying login ...

On Wed, Jan 23, 2019 at 1:11 PM Steve N4IRS <szingman@...> wrote:
Run the program(s) in the foreground to look for errors.
Running the program in the foreground simply means starting the program from the command prompt.
Example: root@myhost:/opt/MMDVM_Bridge# ./MMDVM_Host MMDVM.ini This runs the program from the prompt. Notice the ./ in front of the program name. This means run the program in this directory.

On 1/23/2019 2:09 PM, K4VL wrote:
forgive my ignorance but I don't know how to run it in the foreground

On Wed, Jan 23, 2019 at 1:06 PM Steve N4IRS <szingman@...> wrote:
Hoseline has been up and down. First check your self care page and make sure MMDVM_Bridge is logged in to BM. Running MMDVM_Bridge in the foreground will also tell you if it is connected to BM.

On 1/23/2019 2:04 PM, K4VL wrote:
I did see that I am connected to Brandmeister it has me wondering if my radio is not programmed correctly. I did also try to click on hoseline and got a 503 service unavailable page.

On Wed, Jan 23, 2019 at 12:50 PM Steve N4IRS <szingman@...> wrote:
Not a lot of information to go on but in general:
Run each program in the foreground so you can see what is happening. Start at one end and work to the other end.

Steve

On 1/23/2019 1:42 PM, K4VL wrote:
I was wondering how to test my bridge? I don't seem to be getting to it through my hotspot. I went to the CLI and keyed my radio and nothing showed up. My server is setup as 311628005 and my talkgroup is 310286.

Thanks








Virus-free. www.avg.com




Re: System test

Steve N4IRS
 

Sorryu, I missed the Logged into the master successfully

On 1/25/19 5:32 PM, K4VL wrote:
So when it says logged into Master successfully it's not really logged in correct?

On Fri, Jan 25, 2019, 4:26 PM Steve N4IRS <szingman@...> wrote:
No it is not normal. it is never logging in.


On 1/25/19 5:11 PM, K4VL wrote:
Is the amount of times my MMDVM_Bridge's login fail normal. I am letting it run and this ir what I see.

M: 2019-01-25 21:54:54.590 DMR, Logged into the master successfully
W: 2019-01-25 21:55:54.650 DMR, Login to the master has failed, retrying login ...
E: 2019-01-25 21:56:54.689 DMR, Connection to the master has timed out, retrying connection
M: 2019-01-25 21:56:54.689 DMR, Closing DMR Network
M: 2019-01-25 21:56:54.689 DMR, Opening DMR Network
D: 2019-01-25 21:57:04.732 DMR, Sending authorisation
D: 2019-01-25 21:57:04.768 DMR, Sending configuration
M: 2019-01-25 21:57:04.799 DMR, Logged into the master successfully
W: 2019-01-25 21:58:04.876 DMR, Login to the master has failed, retrying login ...
E: 2019-01-25 21:59:04.915 DMR, Connection to the master has timed out, retrying connection
M: 2019-01-25 21:59:04.916 DMR, Closing DMR Network
M: 2019-01-25 21:59:04.916 DMR, Opening DMR Network
D: 2019-01-25 21:59:14.963 DMR, Sending authorisation
D: 2019-01-25 21:59:14.993 DMR, Sending configuration
M: 2019-01-25 21:59:15.029 DMR, Logged into the master successfully
W: 2019-01-25 22:00:15.095 DMR, Login to the master has failed, retrying login ...
E: 2019-01-25 22:01:15.131 DMR, Connection to the master has timed out, retrying connection
M: 2019-01-25 22:01:15.131 DMR, Closing DMR Network
M: 2019-01-25 22:01:15.131 DMR, Opening DMR Network
D: 2019-01-25 22:01:25.175 DMR, Sending authorisation
D: 2019-01-25 22:01:25.210 DMR, Sending configuration
M: 2019-01-25 22:01:25.241 DMR, Logged into the master successfully
W: 2019-01-25 22:02:25.317 DMR, Login to the master has failed, retrying login ...
E: 2019-01-25 22:03:25.349 DMR, Connection to the master has timed out, retrying connection
M: 2019-01-25 22:03:25.349 DMR, Closing DMR Network
M: 2019-01-25 22:03:25.349 DMR, Opening DMR Network
D: 2019-01-25 22:03:35.386 DMR, Sending authorisation
D: 2019-01-25 22:03:35.416 DMR, Sending configuration
M: 2019-01-25 22:03:35.447 DMR, Logged into the master successfully
W: 2019-01-25 22:04:35.521 DMR, Login to the master has failed, retrying login ...
E: 2019-01-25 22:05:35.570 DMR, Connection to the master has timed out, retrying connection
M: 2019-01-25 22:05:35.571 DMR, Closing DMR Network
M: 2019-01-25 22:05:35.571 DMR, Opening DMR Network
D: 2019-01-25 22:05:45.609 DMR, Sending authorisation
D: 2019-01-25 22:05:45.644 DMR, Sending configuration
M: 2019-01-25 22:05:45.675 DMR, Logged into the master successfully
W: 2019-01-25 22:06:45.767 DMR, Login to the master has failed, retrying login ...
^CM: 2019-01-25 22:07:36.791 Closing the MMDVM
I: 2019-01-25 22:07:37.307 Stopped the DMR Id lookup reload thread
M: 2019-01-25 22:07:37.308 DMR, Closing DMR Network
I: 2019-01-25 22:07:37.308 MMDVM_Bridge-20180423 exited on receipt of SIGINT
root@K4VL-DMR_Bridge:/opt/MMDVM_Bridge#


On Wed, Jan 23, 2019 at 7:04 PM K4VL via Groups.Io <73dek4vl=gmail.com@groups.io> wrote:
Everything appears to work except When I transmit I see activity on
MMDVM_Bridge but not Analog_Bridge. It worked in the past when others
connected to me. I just can't get my radio to work. My radio is working on
other talkgroups.

On Wed, Jan 23, 2019 at 6:13 PM Steve N4IRS <szingman@...> wrote:
That looks OK.

Did the bridge ever work.
Did you follow the howto including the testing at each step?

On 1/23/19 6:17 PM, K4VL wrote:
DVSwitch.ini


; Configure the DMR Partner
; Audio format is AMBE 72 bit
[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

Analog_Bridge.ini

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



Virus-free. www.avg.com

On Wed, Jan 23, 2019 at 4:27 PM Steve N4IRS <szingman@...> wrote:
Did the bridge ever work.
Did you follow the howto including the testing at each step?
Please post the following. Post the [DMR] stanza of DVSwitch.ini and the [AMBE_AUDIO] stanza of Analog_Bridge.ini

Steve


On 1/23/19 4:16 PM, K4VL wrote:
Everything appears to be correct based on the ASL to DMR Bridge document

On Wed, Jan 23, 2019 at 2:56 PM Steve N4IRS <szingman@...> wrote:
Check the port numbers between MMDVM_Bridge and Analog_Bridge.

On 1/23/2019 3:55 PM, K4VL wrote:
After running both MMDVM_Bridge and Analog_Bridge in the foreground, I can keyup and see it in MMDVM_Bridge but nothing in Analog_Bridge

On Wed, Jan 23, 2019 at 2:28 PM K4VL via Groups.Io <73dek4vl=gmail.com@groups.io> wrote:
I just saw the search at the top of the last heard page and added a search for my call. I see my attempts now

On Wed, Jan 23, 2019 at 2:15 PM Corey Dean N3FE <n3fe@...> wrote:
Why not just watch last heard?  Use a rule in it and watch your traffic that way.

Corey  N3FE

On Wed, Jan 23, 2019 at 3:08 PM K4VL <73dek4vl@...> wrote:
With hoseline not working is there anyway I can see these logs when I login?

On Wed, Jan 23, 2019 at 2:02 PM Corey Dean N3FE <n3fe@...> wrote:
I don’t want to post the logs here as it has your ip address in it, but I can confirm you have connected and disconnected many times in the last few hours.  I also see where traffic was coming from bm toward you a few times but I didn’t not verify the talkgroup.

Corey n3fe

On Wed, Jan 23, 2019 at 2:57 PM K4VL <73dek4vl@...> wrote:
My server is setup as 311628005 and my talkgroup is 310286

On Wed, Jan 23, 2019 at 1:56 PM Corey Dean N3FE <n3fe@...> wrote:
Your id you are using to connect to 3108 with?

On Wed, Jan 23, 2019 at 2:45 PM K4VL <73dek4vl@...> wrote:
3108

On Wed, Jan 23, 2019 at 1:42 PM Corey Dean N3FE <n3fe@...> wrote:
What master are you trying to connect to?

Corey n3fe

On Wed, Jan 23, 2019 at 2:37 PM K4VL <73dek4vl@...> wrote:
I was wondering... Could my problem be that  my gatewayDmrId in the Analog_Bridge.ini is the same as the Radio ID in my handheld radio? Do I need to get another DMR ID?

On Wed, Jan 23, 2019 at 1:31 PM Steve N4IRS <szingman@...> wrote:
These are the items in MMDVM_Bridge.in that deal with logging into a Master:
[General]
Callsign=W1AW
Id=3112111
Duplex=0

[DMR Network]
Enable=1
Address=310x.repeater.net
Port=62031
Jitter=500
Local=62032
Password=passw0rd
Slot1=1
Slot2=1
Debug=0




On 1/23/2019 2:26 PM, K4VL wrote:
The password under DMR Network is correct

On Wed, Jan 23, 2019 at 1:22 PM Steve N4IRS <szingman@...> wrote:
Check your password. Should be passw0rd Notice the 0

On 1/23/2019 2:20 PM, K4VL wrote:
OK I can see when I key up the last line that comes up says Login to master has failed, retrying login ...

On Wed, Jan 23, 2019 at 1:11 PM Steve N4IRS <szingman@...> wrote:
Run the program(s) in the foreground to look for errors.
Running the program in the foreground simply means starting the program from the command prompt.
Example: root@myhost:/opt/MMDVM_Bridge# ./MMDVM_Host MMDVM.ini This runs the program from the prompt. Notice the ./ in front of the program name. This means run the program in this directory.

On 1/23/2019 2:09 PM, K4VL wrote:
forgive my ignorance but I don't know how to run it in the foreground

On Wed, Jan 23, 2019 at 1:06 PM Steve N4IRS <szingman@...> wrote:
Hoseline has been up and down. First check your self care page and make sure MMDVM_Bridge is logged in to BM. Running MMDVM_Bridge in the foreground will also tell you if it is connected to BM.

On 1/23/2019 2:04 PM, K4VL wrote:
I did see that I am connected to Brandmeister it has me wondering if my radio is not programmed correctly. I did also try to click on hoseline and got a 503 service unavailable page.

On Wed, Jan 23, 2019 at 12:50 PM Steve N4IRS <szingman@...> wrote:
Not a lot of information to go on but in general:
Run each program in the foreground so you can see what is happening. Start at one end and work to the other end.

Steve

On 1/23/2019 1:42 PM, K4VL wrote:
I was wondering how to test my bridge? I don't seem to be getting to it through my hotspot. I went to the CLI and keyed my radio and nothing showed up. My server is setup as 311628005 and my talkgroup is 310286.

Thanks








Virus-free. www.avg.com




Re: System test

K4VL <73dek4vl@...>
 

This worked before I changed my callsign from AA4II to K4VL. I do get this happening when I key my radio

M: 2019-01-25 22:58:26.343 DMR, Logged into the master successfully
M: 2019-01-25 22:58:38.645 DMR Slot 2, received network voice header from K4VL to    TG 310286
M: 2019-01-25 22:58:39.197 DMR Talker Alias (Data Format 1, Received 6/20 char):    'K4VL D'
M: 2019-01-25 22:58:39.922 DMR Talker Alias (Data Format 1, Received 13/20 char):    'K4VL DMR ID: '
M: 2019-01-25 22:58:40.035 DMR Slot 2, received network end of voice transmission   , 1.6 seconds, 0% packet loss, BER: 0.0%
M: 2019-01-25 22:59:13.768 DMR Slot 2, received network voice header from K4VL to TG 310286
M: 2019-01-25 22:59:14.479 DMR Talker Alias (Data Format 1, Received 6/20 char): 'K4VL D'
M: 2019-01-25 22:59:15.198 DMR Talker Alias (Data Format 1, Received 13/20 char): 'K4VL DMR ID: '
M: 2019-01-25 22:59:15.918 DMR Talker Alias (Data Format 1, Received 20/20 char): 'K4VL DMR ID: 3116280'
D: 2019-01-25 22:59:17.165 DMR Slot 2, lost audio for 766ms filling in
M: 2019-01-25 22:59:17.569 DMR Slot 2, received network end of voice transmission, 3

Analog_Bridge does not change when I key the radio.

On Fri, Jan 25, 2019 at 4:33 PM K4VL via Groups.Io <73dek4vl=gmail.com@groups.io> wrote:
So when it says logged into Master successfully it's not really logged in correct?

On Fri, Jan 25, 2019, 4:26 PM Steve N4IRS <szingman@...> wrote:
No it is not normal. it is never logging in.


On 1/25/19 5:11 PM, K4VL wrote:
Is the amount of times my MMDVM_Bridge's login fail normal. I am letting it run and this ir what I see.

M: 2019-01-25 21:54:54.590 DMR, Logged into the master successfully
W: 2019-01-25 21:55:54.650 DMR, Login to the master has failed, retrying login ...
E: 2019-01-25 21:56:54.689 DMR, Connection to the master has timed out, retrying connection
M: 2019-01-25 21:56:54.689 DMR, Closing DMR Network
M: 2019-01-25 21:56:54.689 DMR, Opening DMR Network
D: 2019-01-25 21:57:04.732 DMR, Sending authorisation
D: 2019-01-25 21:57:04.768 DMR, Sending configuration
M: 2019-01-25 21:57:04.799 DMR, Logged into the master successfully
W: 2019-01-25 21:58:04.876 DMR, Login to the master has failed, retrying login ...
E: 2019-01-25 21:59:04.915 DMR, Connection to the master has timed out, retrying connection
M: 2019-01-25 21:59:04.916 DMR, Closing DMR Network
M: 2019-01-25 21:59:04.916 DMR, Opening DMR Network
D: 2019-01-25 21:59:14.963 DMR, Sending authorisation
D: 2019-01-25 21:59:14.993 DMR, Sending configuration
M: 2019-01-25 21:59:15.029 DMR, Logged into the master successfully
W: 2019-01-25 22:00:15.095 DMR, Login to the master has failed, retrying login ...
E: 2019-01-25 22:01:15.131 DMR, Connection to the master has timed out, retrying connection
M: 2019-01-25 22:01:15.131 DMR, Closing DMR Network
M: 2019-01-25 22:01:15.131 DMR, Opening DMR Network
D: 2019-01-25 22:01:25.175 DMR, Sending authorisation
D: 2019-01-25 22:01:25.210 DMR, Sending configuration
M: 2019-01-25 22:01:25.241 DMR, Logged into the master successfully
W: 2019-01-25 22:02:25.317 DMR, Login to the master has failed, retrying login ...
E: 2019-01-25 22:03:25.349 DMR, Connection to the master has timed out, retrying connection
M: 2019-01-25 22:03:25.349 DMR, Closing DMR Network
M: 2019-01-25 22:03:25.349 DMR, Opening DMR Network
D: 2019-01-25 22:03:35.386 DMR, Sending authorisation
D: 2019-01-25 22:03:35.416 DMR, Sending configuration
M: 2019-01-25 22:03:35.447 DMR, Logged into the master successfully
W: 2019-01-25 22:04:35.521 DMR, Login to the master has failed, retrying login ...
E: 2019-01-25 22:05:35.570 DMR, Connection to the master has timed out, retrying connection
M: 2019-01-25 22:05:35.571 DMR, Closing DMR Network
M: 2019-01-25 22:05:35.571 DMR, Opening DMR Network
D: 2019-01-25 22:05:45.609 DMR, Sending authorisation
D: 2019-01-25 22:05:45.644 DMR, Sending configuration
M: 2019-01-25 22:05:45.675 DMR, Logged into the master successfully
W: 2019-01-25 22:06:45.767 DMR, Login to the master has failed, retrying login ...
^CM: 2019-01-25 22:07:36.791 Closing the MMDVM
I: 2019-01-25 22:07:37.307 Stopped the DMR Id lookup reload thread
M: 2019-01-25 22:07:37.308 DMR, Closing DMR Network
I: 2019-01-25 22:07:37.308 MMDVM_Bridge-20180423 exited on receipt of SIGINT
root@K4VL-DMR_Bridge:/opt/MMDVM_Bridge#


On Wed, Jan 23, 2019 at 7:04 PM K4VL via Groups.Io <73dek4vl=gmail.com@groups.io> wrote:
Everything appears to work except When I transmit I see activity on
MMDVM_Bridge but not Analog_Bridge. It worked in the past when others
connected to me. I just can't get my radio to work. My radio is working on
other talkgroups.

On Wed, Jan 23, 2019 at 6:13 PM Steve N4IRS <szingman@...> wrote:
That looks OK.

Did the bridge ever work.
Did you follow the howto including the testing at each step?

On 1/23/19 6:17 PM, K4VL wrote:
DVSwitch.ini


; Configure the DMR Partner
; Audio format is AMBE 72 bit
[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

Analog_Bridge.ini

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



Virus-free. www.avg.com

On Wed, Jan 23, 2019 at 4:27 PM Steve N4IRS <szingman@...> wrote:
Did the bridge ever work.
Did you follow the howto including the testing at each step?
Please post the following. Post the [DMR] stanza of DVSwitch.ini and the [AMBE_AUDIO] stanza of Analog_Bridge.ini

Steve


On 1/23/19 4:16 PM, K4VL wrote:
Everything appears to be correct based on the ASL to DMR Bridge document

On Wed, Jan 23, 2019 at 2:56 PM Steve N4IRS <szingman@...> wrote:
Check the port numbers between MMDVM_Bridge and Analog_Bridge.

On 1/23/2019 3:55 PM, K4VL wrote:
After running both MMDVM_Bridge and Analog_Bridge in the foreground, I can keyup and see it in MMDVM_Bridge but nothing in Analog_Bridge

On Wed, Jan 23, 2019 at 2:28 PM K4VL via Groups.Io <73dek4vl=gmail.com@groups.io> wrote:
I just saw the search at the top of the last heard page and added a search for my call. I see my attempts now

On Wed, Jan 23, 2019 at 2:15 PM Corey Dean N3FE <n3fe@...> wrote:
Why not just watch last heard?  Use a rule in it and watch your traffic that way.

Corey  N3FE

On Wed, Jan 23, 2019 at 3:08 PM K4VL <73dek4vl@...> wrote:
With hoseline not working is there anyway I can see these logs when I login?

On Wed, Jan 23, 2019 at 2:02 PM Corey Dean N3FE <n3fe@...> wrote:
I don’t want to post the logs here as it has your ip address in it, but I can confirm you have connected and disconnected many times in the last few hours.  I also see where traffic was coming from bm toward you a few times but I didn’t not verify the talkgroup.

Corey n3fe

On Wed, Jan 23, 2019 at 2:57 PM K4VL <73dek4vl@...> wrote:
My server is setup as 311628005 and my talkgroup is 310286

On Wed, Jan 23, 2019 at 1:56 PM Corey Dean N3FE <n3fe@...> wrote:
Your id you are using to connect to 3108 with?

On Wed, Jan 23, 2019 at 2:45 PM K4VL <73dek4vl@...> wrote:
3108

On Wed, Jan 23, 2019 at 1:42 PM Corey Dean N3FE <n3fe@...> wrote:
What master are you trying to connect to?

Corey n3fe

On Wed, Jan 23, 2019 at 2:37 PM K4VL <73dek4vl@...> wrote:
I was wondering... Could my problem be that  my gatewayDmrId in the Analog_Bridge.ini is the same as the Radio ID in my handheld radio? Do I need to get another DMR ID?

On Wed, Jan 23, 2019 at 1:31 PM Steve N4IRS <szingman@...> wrote:
These are the items in MMDVM_Bridge.in that deal with logging into a Master:
[General]
Callsign=W1AW
Id=3112111
Duplex=0

[DMR Network]
Enable=1
Address=310x.repeater.net
Port=62031
Jitter=500
Local=62032
Password=passw0rd
Slot1=1
Slot2=1
Debug=0




On 1/23/2019 2:26 PM, K4VL wrote:
The password under DMR Network is correct

On Wed, Jan 23, 2019 at 1:22 PM Steve N4IRS <szingman@...> wrote:
Check your password. Should be passw0rd Notice the 0

On 1/23/2019 2:20 PM, K4VL wrote:
OK I can see when I key up the last line that comes up says Login to master has failed, retrying login ...

On Wed, Jan 23, 2019 at 1:11 PM Steve N4IRS <szingman@...> wrote:
Run the program(s) in the foreground to look for errors.
Running the program in the foreground simply means starting the program from the command prompt.
Example: root@myhost:/opt/MMDVM_Bridge# ./MMDVM_Host MMDVM.ini This runs the program from the prompt. Notice the ./ in front of the program name. This means run the program in this directory.

On 1/23/2019 2:09 PM, K4VL wrote:
forgive my ignorance but I don't know how to run it in the foreground

On Wed, Jan 23, 2019 at 1:06 PM Steve N4IRS <szingman@...> wrote:
Hoseline has been up and down. First check your self care page and make sure MMDVM_Bridge is logged in to BM. Running MMDVM_Bridge in the foreground will also tell you if it is connected to BM.

On 1/23/2019 2:04 PM, K4VL wrote:
I did see that I am connected to Brandmeister it has me wondering if my radio is not programmed correctly. I did also try to click on hoseline and got a 503 service unavailable page.

On Wed, Jan 23, 2019 at 12:50 PM Steve N4IRS <szingman@...> wrote:
Not a lot of information to go on but in general:
Run each program in the foreground so you can see what is happening. Start at one end and work to the other end.

Steve

On 1/23/2019 1:42 PM, K4VL wrote:
I was wondering how to test my bridge? I don't seem to be getting to it through my hotspot. I went to the CLI and keyed my radio and nothing showed up. My server is setup as 311628005 and my talkgroup is 310286.

Thanks








Virus-free. www.avg.com



Re: System test

K4VL <73dek4vl@...>
 

So when it says logged into Master successfully it's not really logged in correct?


On Fri, Jan 25, 2019, 4:26 PM Steve N4IRS <szingman@...> wrote:
No it is not normal. it is never logging in.


On 1/25/19 5:11 PM, K4VL wrote:
Is the amount of times my MMDVM_Bridge's login fail normal. I am letting it run and this ir what I see.

M: 2019-01-25 21:54:54.590 DMR, Logged into the master successfully
W: 2019-01-25 21:55:54.650 DMR, Login to the master has failed, retrying login ...
E: 2019-01-25 21:56:54.689 DMR, Connection to the master has timed out, retrying connection
M: 2019-01-25 21:56:54.689 DMR, Closing DMR Network
M: 2019-01-25 21:56:54.689 DMR, Opening DMR Network
D: 2019-01-25 21:57:04.732 DMR, Sending authorisation
D: 2019-01-25 21:57:04.768 DMR, Sending configuration
M: 2019-01-25 21:57:04.799 DMR, Logged into the master successfully
W: 2019-01-25 21:58:04.876 DMR, Login to the master has failed, retrying login ...
E: 2019-01-25 21:59:04.915 DMR, Connection to the master has timed out, retrying connection
M: 2019-01-25 21:59:04.916 DMR, Closing DMR Network
M: 2019-01-25 21:59:04.916 DMR, Opening DMR Network
D: 2019-01-25 21:59:14.963 DMR, Sending authorisation
D: 2019-01-25 21:59:14.993 DMR, Sending configuration
M: 2019-01-25 21:59:15.029 DMR, Logged into the master successfully
W: 2019-01-25 22:00:15.095 DMR, Login to the master has failed, retrying login ...
E: 2019-01-25 22:01:15.131 DMR, Connection to the master has timed out, retrying connection
M: 2019-01-25 22:01:15.131 DMR, Closing DMR Network
M: 2019-01-25 22:01:15.131 DMR, Opening DMR Network
D: 2019-01-25 22:01:25.175 DMR, Sending authorisation
D: 2019-01-25 22:01:25.210 DMR, Sending configuration
M: 2019-01-25 22:01:25.241 DMR, Logged into the master successfully
W: 2019-01-25 22:02:25.317 DMR, Login to the master has failed, retrying login ...
E: 2019-01-25 22:03:25.349 DMR, Connection to the master has timed out, retrying connection
M: 2019-01-25 22:03:25.349 DMR, Closing DMR Network
M: 2019-01-25 22:03:25.349 DMR, Opening DMR Network
D: 2019-01-25 22:03:35.386 DMR, Sending authorisation
D: 2019-01-25 22:03:35.416 DMR, Sending configuration
M: 2019-01-25 22:03:35.447 DMR, Logged into the master successfully
W: 2019-01-25 22:04:35.521 DMR, Login to the master has failed, retrying login ...
E: 2019-01-25 22:05:35.570 DMR, Connection to the master has timed out, retrying connection
M: 2019-01-25 22:05:35.571 DMR, Closing DMR Network
M: 2019-01-25 22:05:35.571 DMR, Opening DMR Network
D: 2019-01-25 22:05:45.609 DMR, Sending authorisation
D: 2019-01-25 22:05:45.644 DMR, Sending configuration
M: 2019-01-25 22:05:45.675 DMR, Logged into the master successfully
W: 2019-01-25 22:06:45.767 DMR, Login to the master has failed, retrying login ...
^CM: 2019-01-25 22:07:36.791 Closing the MMDVM
I: 2019-01-25 22:07:37.307 Stopped the DMR Id lookup reload thread
M: 2019-01-25 22:07:37.308 DMR, Closing DMR Network
I: 2019-01-25 22:07:37.308 MMDVM_Bridge-20180423 exited on receipt of SIGINT
root@K4VL-DMR_Bridge:/opt/MMDVM_Bridge#


On Wed, Jan 23, 2019 at 7:04 PM K4VL via Groups.Io <73dek4vl=gmail.com@groups.io> wrote:
Everything appears to work except When I transmit I see activity on
MMDVM_Bridge but not Analog_Bridge. It worked in the past when others
connected to me. I just can't get my radio to work. My radio is working on
other talkgroups.

On Wed, Jan 23, 2019 at 6:13 PM Steve N4IRS <szingman@...> wrote:
That looks OK.

Did the bridge ever work.
Did you follow the howto including the testing at each step?

On 1/23/19 6:17 PM, K4VL wrote:
DVSwitch.ini


; Configure the DMR Partner
; Audio format is AMBE 72 bit
[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

Analog_Bridge.ini

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



Virus-free. www.avg.com

On Wed, Jan 23, 2019 at 4:27 PM Steve N4IRS <szingman@...> wrote:
Did the bridge ever work.
Did you follow the howto including the testing at each step?
Please post the following. Post the [DMR] stanza of DVSwitch.ini and the [AMBE_AUDIO] stanza of Analog_Bridge.ini

Steve


On 1/23/19 4:16 PM, K4VL wrote:
Everything appears to be correct based on the ASL to DMR Bridge document

On Wed, Jan 23, 2019 at 2:56 PM Steve N4IRS <szingman@...> wrote:
Check the port numbers between MMDVM_Bridge and Analog_Bridge.

On 1/23/2019 3:55 PM, K4VL wrote:
After running both MMDVM_Bridge and Analog_Bridge in the foreground, I can keyup and see it in MMDVM_Bridge but nothing in Analog_Bridge

On Wed, Jan 23, 2019 at 2:28 PM K4VL via Groups.Io <73dek4vl=gmail.com@groups.io> wrote:
I just saw the search at the top of the last heard page and added a search for my call. I see my attempts now

On Wed, Jan 23, 2019 at 2:15 PM Corey Dean N3FE <n3fe@...> wrote:
Why not just watch last heard?  Use a rule in it and watch your traffic that way.

Corey  N3FE

On Wed, Jan 23, 2019 at 3:08 PM K4VL <73dek4vl@...> wrote:
With hoseline not working is there anyway I can see these logs when I login?

On Wed, Jan 23, 2019 at 2:02 PM Corey Dean N3FE <n3fe@...> wrote:
I don’t want to post the logs here as it has your ip address in it, but I can confirm you have connected and disconnected many times in the last few hours.  I also see where traffic was coming from bm toward you a few times but I didn’t not verify the talkgroup.

Corey n3fe

On Wed, Jan 23, 2019 at 2:57 PM K4VL <73dek4vl@...> wrote:
My server is setup as 311628005 and my talkgroup is 310286

On Wed, Jan 23, 2019 at 1:56 PM Corey Dean N3FE <n3fe@...> wrote:
Your id you are using to connect to 3108 with?

On Wed, Jan 23, 2019 at 2:45 PM K4VL <73dek4vl@...> wrote:
3108

On Wed, Jan 23, 2019 at 1:42 PM Corey Dean N3FE <n3fe@...> wrote:
What master are you trying to connect to?

Corey n3fe

On Wed, Jan 23, 2019 at 2:37 PM K4VL <73dek4vl@...> wrote:
I was wondering... Could my problem be that  my gatewayDmrId in the Analog_Bridge.ini is the same as the Radio ID in my handheld radio? Do I need to get another DMR ID?

On Wed, Jan 23, 2019 at 1:31 PM Steve N4IRS <szingman@...> wrote:
These are the items in MMDVM_Bridge.in that deal with logging into a Master:
[General]
Callsign=W1AW
Id=3112111
Duplex=0

[DMR Network]
Enable=1
Address=310x.repeater.net
Port=62031
Jitter=500
Local=62032
Password=passw0rd
Slot1=1
Slot2=1
Debug=0




On 1/23/2019 2:26 PM, K4VL wrote:
The password under DMR Network is correct

On Wed, Jan 23, 2019 at 1:22 PM Steve N4IRS <szingman@...> wrote:
Check your password. Should be passw0rd Notice the 0

On 1/23/2019 2:20 PM, K4VL wrote:
OK I can see when I key up the last line that comes up says Login to master has failed, retrying login ...

On Wed, Jan 23, 2019 at 1:11 PM Steve N4IRS <szingman@...> wrote:
Run the program(s) in the foreground to look for errors.
Running the program in the foreground simply means starting the program from the command prompt.
Example: root@myhost:/opt/MMDVM_Bridge# ./MMDVM_Host MMDVM.ini This runs the program from the prompt. Notice the ./ in front of the program name. This means run the program in this directory.

On 1/23/2019 2:09 PM, K4VL wrote:
forgive my ignorance but I don't know how to run it in the foreground

On Wed, Jan 23, 2019 at 1:06 PM Steve N4IRS <szingman@...> wrote:
Hoseline has been up and down. First check your self care page and make sure MMDVM_Bridge is logged in to BM. Running MMDVM_Bridge in the foreground will also tell you if it is connected to BM.

On 1/23/2019 2:04 PM, K4VL wrote:
I did see that I am connected to Brandmeister it has me wondering if my radio is not programmed correctly. I did also try to click on hoseline and got a 503 service unavailable page.

On Wed, Jan 23, 2019 at 12:50 PM Steve N4IRS <szingman@...> wrote:
Not a lot of information to go on but in general:
Run each program in the foreground so you can see what is happening. Start at one end and work to the other end.

Steve

On 1/23/2019 1:42 PM, K4VL wrote:
I was wondering how to test my bridge? I don't seem to be getting to it through my hotspot. I went to the CLI and keyed my radio and nothing showed up. My server is setup as 311628005 and my talkgroup is 310286.

Thanks








Virus-free. www.avg.com



Re: System test

Steve N4IRS
 

No it is not normal. it is never logging in.

On 1/25/19 5:11 PM, K4VL wrote:
Is the amount of times my MMDVM_Bridge's login fail normal. I am letting it run and this ir what I see.

M: 2019-01-25 21:54:54.590 DMR, Logged into the master successfully
W: 2019-01-25 21:55:54.650 DMR, Login to the master has failed, retrying login ...
E: 2019-01-25 21:56:54.689 DMR, Connection to the master has timed out, retrying connection
M: 2019-01-25 21:56:54.689 DMR, Closing DMR Network
M: 2019-01-25 21:56:54.689 DMR, Opening DMR Network
D: 2019-01-25 21:57:04.732 DMR, Sending authorisation
D: 2019-01-25 21:57:04.768 DMR, Sending configuration
M: 2019-01-25 21:57:04.799 DMR, Logged into the master successfully
W: 2019-01-25 21:58:04.876 DMR, Login to the master has failed, retrying login ...
E: 2019-01-25 21:59:04.915 DMR, Connection to the master has timed out, retrying connection
M: 2019-01-25 21:59:04.916 DMR, Closing DMR Network
M: 2019-01-25 21:59:04.916 DMR, Opening DMR Network
D: 2019-01-25 21:59:14.963 DMR, Sending authorisation
D: 2019-01-25 21:59:14.993 DMR, Sending configuration
M: 2019-01-25 21:59:15.029 DMR, Logged into the master successfully
W: 2019-01-25 22:00:15.095 DMR, Login to the master has failed, retrying login ...
E: 2019-01-25 22:01:15.131 DMR, Connection to the master has timed out, retrying connection
M: 2019-01-25 22:01:15.131 DMR, Closing DMR Network
M: 2019-01-25 22:01:15.131 DMR, Opening DMR Network
D: 2019-01-25 22:01:25.175 DMR, Sending authorisation
D: 2019-01-25 22:01:25.210 DMR, Sending configuration
M: 2019-01-25 22:01:25.241 DMR, Logged into the master successfully
W: 2019-01-25 22:02:25.317 DMR, Login to the master has failed, retrying login ...
E: 2019-01-25 22:03:25.349 DMR, Connection to the master has timed out, retrying connection
M: 2019-01-25 22:03:25.349 DMR, Closing DMR Network
M: 2019-01-25 22:03:25.349 DMR, Opening DMR Network
D: 2019-01-25 22:03:35.386 DMR, Sending authorisation
D: 2019-01-25 22:03:35.416 DMR, Sending configuration
M: 2019-01-25 22:03:35.447 DMR, Logged into the master successfully
W: 2019-01-25 22:04:35.521 DMR, Login to the master has failed, retrying login ...
E: 2019-01-25 22:05:35.570 DMR, Connection to the master has timed out, retrying connection
M: 2019-01-25 22:05:35.571 DMR, Closing DMR Network
M: 2019-01-25 22:05:35.571 DMR, Opening DMR Network
D: 2019-01-25 22:05:45.609 DMR, Sending authorisation
D: 2019-01-25 22:05:45.644 DMR, Sending configuration
M: 2019-01-25 22:05:45.675 DMR, Logged into the master successfully
W: 2019-01-25 22:06:45.767 DMR, Login to the master has failed, retrying login ...
^CM: 2019-01-25 22:07:36.791 Closing the MMDVM
I: 2019-01-25 22:07:37.307 Stopped the DMR Id lookup reload thread
M: 2019-01-25 22:07:37.308 DMR, Closing DMR Network
I: 2019-01-25 22:07:37.308 MMDVM_Bridge-20180423 exited on receipt of SIGINT
root@K4VL-DMR_Bridge:/opt/MMDVM_Bridge#


On Wed, Jan 23, 2019 at 7:04 PM K4VL via Groups.Io <73dek4vl=gmail.com@groups.io> wrote:
Everything appears to work except When I transmit I see activity on
MMDVM_Bridge but not Analog_Bridge. It worked in the past when others
connected to me. I just can't get my radio to work. My radio is working on
other talkgroups.

On Wed, Jan 23, 2019 at 6:13 PM Steve N4IRS <szingman@...> wrote:
That looks OK.

Did the bridge ever work.
Did you follow the howto including the testing at each step?

On 1/23/19 6:17 PM, K4VL wrote:
DVSwitch.ini


; Configure the DMR Partner
; Audio format is AMBE 72 bit
[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

Analog_Bridge.ini

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



Virus-free. www.avg.com

On Wed, Jan 23, 2019 at 4:27 PM Steve N4IRS <szingman@...> wrote:
Did the bridge ever work.
Did you follow the howto including the testing at each step?
Please post the following. Post the [DMR] stanza of DVSwitch.ini and the [AMBE_AUDIO] stanza of Analog_Bridge.ini

Steve


On 1/23/19 4:16 PM, K4VL wrote:
Everything appears to be correct based on the ASL to DMR Bridge document

On Wed, Jan 23, 2019 at 2:56 PM Steve N4IRS <szingman@...> wrote:
Check the port numbers between MMDVM_Bridge and Analog_Bridge.

On 1/23/2019 3:55 PM, K4VL wrote:
After running both MMDVM_Bridge and Analog_Bridge in the foreground, I can keyup and see it in MMDVM_Bridge but nothing in Analog_Bridge

On Wed, Jan 23, 2019 at 2:28 PM K4VL via Groups.Io <73dek4vl=gmail.com@groups.io> wrote:
I just saw the search at the top of the last heard page and added a search for my call. I see my attempts now

On Wed, Jan 23, 2019 at 2:15 PM Corey Dean N3FE <n3fe@...> wrote:
Why not just watch last heard?  Use a rule in it and watch your traffic that way.

Corey  N3FE

On Wed, Jan 23, 2019 at 3:08 PM K4VL <73dek4vl@...> wrote:
With hoseline not working is there anyway I can see these logs when I login?

On Wed, Jan 23, 2019 at 2:02 PM Corey Dean N3FE <n3fe@...> wrote:
I don’t want to post the logs here as it has your ip address in it, but I can confirm you have connected and disconnected many times in the last few hours.  I also see where traffic was coming from bm toward you a few times but I didn’t not verify the talkgroup.

Corey n3fe

On Wed, Jan 23, 2019 at 2:57 PM K4VL <73dek4vl@...> wrote:
My server is setup as 311628005 and my talkgroup is 310286

On Wed, Jan 23, 2019 at 1:56 PM Corey Dean N3FE <n3fe@...> wrote:
Your id you are using to connect to 3108 with?

On Wed, Jan 23, 2019 at 2:45 PM K4VL <73dek4vl@...> wrote:
3108

On Wed, Jan 23, 2019 at 1:42 PM Corey Dean N3FE <n3fe@...> wrote:
What master are you trying to connect to?

Corey n3fe

On Wed, Jan 23, 2019 at 2:37 PM K4VL <73dek4vl@...> wrote:
I was wondering... Could my problem be that  my gatewayDmrId in the Analog_Bridge.ini is the same as the Radio ID in my handheld radio? Do I need to get another DMR ID?

On Wed, Jan 23, 2019 at 1:31 PM Steve N4IRS <szingman@...> wrote:
These are the items in MMDVM_Bridge.in that deal with logging into a Master:
[General]
Callsign=W1AW
Id=3112111
Duplex=0

[DMR Network]
Enable=1
Address=310x.repeater.net
Port=62031
Jitter=500
Local=62032
Password=passw0rd
Slot1=1
Slot2=1
Debug=0




On 1/23/2019 2:26 PM, K4VL wrote:
The password under DMR Network is correct

On Wed, Jan 23, 2019 at 1:22 PM Steve N4IRS <szingman@...> wrote:
Check your password. Should be passw0rd Notice the 0

On 1/23/2019 2:20 PM, K4VL wrote:
OK I can see when I key up the last line that comes up says Login to master has failed, retrying login ...

On Wed, Jan 23, 2019 at 1:11 PM Steve N4IRS <szingman@...> wrote:
Run the program(s) in the foreground to look for errors.
Running the program in the foreground simply means starting the program from the command prompt.
Example: root@myhost:/opt/MMDVM_Bridge# ./MMDVM_Host MMDVM.ini This runs the program from the prompt. Notice the ./ in front of the program name. This means run the program in this directory.

On 1/23/2019 2:09 PM, K4VL wrote:
forgive my ignorance but I don't know how to run it in the foreground

On Wed, Jan 23, 2019 at 1:06 PM Steve N4IRS <szingman@...> wrote:
Hoseline has been up and down. First check your self care page and make sure MMDVM_Bridge is logged in to BM. Running MMDVM_Bridge in the foreground will also tell you if it is connected to BM.

On 1/23/2019 2:04 PM, K4VL wrote:
I did see that I am connected to Brandmeister it has me wondering if my radio is not programmed correctly. I did also try to click on hoseline and got a 503 service unavailable page.

On Wed, Jan 23, 2019 at 12:50 PM Steve N4IRS <szingman@...> wrote:
Not a lot of information to go on but in general:
Run each program in the foreground so you can see what is happening. Start at one end and work to the other end.

Steve

On 1/23/2019 1:42 PM, K4VL wrote:
I was wondering how to test my bridge? I don't seem to be getting to it through my hotspot. I went to the CLI and keyed my radio and nothing showed up. My server is setup as 311628005 and my talkgroup is 310286.

Thanks








Virus-free. www.avg.com



Re: System test

K4VL <73dek4vl@...>
 

Is the amount of times my MMDVM_Bridge's login fail normal. I am letting it run and this ir what I see.

M: 2019-01-25 21:54:54.590 DMR, Logged into the master successfully
W: 2019-01-25 21:55:54.650 DMR, Login to the master has failed, retrying login ...
E: 2019-01-25 21:56:54.689 DMR, Connection to the master has timed out, retrying connection
M: 2019-01-25 21:56:54.689 DMR, Closing DMR Network
M: 2019-01-25 21:56:54.689 DMR, Opening DMR Network
D: 2019-01-25 21:57:04.732 DMR, Sending authorisation
D: 2019-01-25 21:57:04.768 DMR, Sending configuration
M: 2019-01-25 21:57:04.799 DMR, Logged into the master successfully
W: 2019-01-25 21:58:04.876 DMR, Login to the master has failed, retrying login ...
E: 2019-01-25 21:59:04.915 DMR, Connection to the master has timed out, retrying connection
M: 2019-01-25 21:59:04.916 DMR, Closing DMR Network
M: 2019-01-25 21:59:04.916 DMR, Opening DMR Network
D: 2019-01-25 21:59:14.963 DMR, Sending authorisation
D: 2019-01-25 21:59:14.993 DMR, Sending configuration
M: 2019-01-25 21:59:15.029 DMR, Logged into the master successfully
W: 2019-01-25 22:00:15.095 DMR, Login to the master has failed, retrying login ...
E: 2019-01-25 22:01:15.131 DMR, Connection to the master has timed out, retrying connection
M: 2019-01-25 22:01:15.131 DMR, Closing DMR Network
M: 2019-01-25 22:01:15.131 DMR, Opening DMR Network
D: 2019-01-25 22:01:25.175 DMR, Sending authorisation
D: 2019-01-25 22:01:25.210 DMR, Sending configuration
M: 2019-01-25 22:01:25.241 DMR, Logged into the master successfully
W: 2019-01-25 22:02:25.317 DMR, Login to the master has failed, retrying login ...
E: 2019-01-25 22:03:25.349 DMR, Connection to the master has timed out, retrying connection
M: 2019-01-25 22:03:25.349 DMR, Closing DMR Network
M: 2019-01-25 22:03:25.349 DMR, Opening DMR Network
D: 2019-01-25 22:03:35.386 DMR, Sending authorisation
D: 2019-01-25 22:03:35.416 DMR, Sending configuration
M: 2019-01-25 22:03:35.447 DMR, Logged into the master successfully
W: 2019-01-25 22:04:35.521 DMR, Login to the master has failed, retrying login ...
E: 2019-01-25 22:05:35.570 DMR, Connection to the master has timed out, retrying connection
M: 2019-01-25 22:05:35.571 DMR, Closing DMR Network
M: 2019-01-25 22:05:35.571 DMR, Opening DMR Network
D: 2019-01-25 22:05:45.609 DMR, Sending authorisation
D: 2019-01-25 22:05:45.644 DMR, Sending configuration
M: 2019-01-25 22:05:45.675 DMR, Logged into the master successfully
W: 2019-01-25 22:06:45.767 DMR, Login to the master has failed, retrying login ...
^CM: 2019-01-25 22:07:36.791 Closing the MMDVM
I: 2019-01-25 22:07:37.307 Stopped the DMR Id lookup reload thread
M: 2019-01-25 22:07:37.308 DMR, Closing DMR Network
I: 2019-01-25 22:07:37.308 MMDVM_Bridge-20180423 exited on receipt of SIGINT
root@K4VL-DMR_Bridge:/opt/MMDVM_Bridge#


On Wed, Jan 23, 2019 at 7:04 PM K4VL via Groups.Io <73dek4vl=gmail.com@groups.io> wrote:
Everything appears to work except When I transmit I see activity on
MMDVM_Bridge but not Analog_Bridge. It worked in the past when others
connected to me. I just can't get my radio to work. My radio is working on
other talkgroups.

On Wed, Jan 23, 2019 at 6:13 PM Steve N4IRS <szingman@...> wrote:
That looks OK.

Did the bridge ever work.
Did you follow the howto including the testing at each step?

On 1/23/19 6:17 PM, K4VL wrote:
DVSwitch.ini


; Configure the DMR Partner
; Audio format is AMBE 72 bit
[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

Analog_Bridge.ini

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



Virus-free. www.avg.com

On Wed, Jan 23, 2019 at 4:27 PM Steve N4IRS <szingman@...> wrote:
Did the bridge ever work.
Did you follow the howto including the testing at each step?
Please post the following. Post the [DMR] stanza of DVSwitch.ini and the [AMBE_AUDIO] stanza of Analog_Bridge.ini

Steve


On 1/23/19 4:16 PM, K4VL wrote:
Everything appears to be correct based on the ASL to DMR Bridge document

On Wed, Jan 23, 2019 at 2:56 PM Steve N4IRS <szingman@...> wrote:
Check the port numbers between MMDVM_Bridge and Analog_Bridge.

On 1/23/2019 3:55 PM, K4VL wrote:
After running both MMDVM_Bridge and Analog_Bridge in the foreground, I can keyup and see it in MMDVM_Bridge but nothing in Analog_Bridge

On Wed, Jan 23, 2019 at 2:28 PM K4VL via Groups.Io <73dek4vl=gmail.com@groups.io> wrote:
I just saw the search at the top of the last heard page and added a search for my call. I see my attempts now

On Wed, Jan 23, 2019 at 2:15 PM Corey Dean N3FE <n3fe@...> wrote:
Why not just watch last heard?  Use a rule in it and watch your traffic that way.

Corey  N3FE

On Wed, Jan 23, 2019 at 3:08 PM K4VL <73dek4vl@...> wrote:
With hoseline not working is there anyway I can see these logs when I login?

On Wed, Jan 23, 2019 at 2:02 PM Corey Dean N3FE <n3fe@...> wrote:
I don’t want to post the logs here as it has your ip address in it, but I can confirm you have connected and disconnected many times in the last few hours.  I also see where traffic was coming from bm toward you a few times but I didn’t not verify the talkgroup.

Corey n3fe

On Wed, Jan 23, 2019 at 2:57 PM K4VL <73dek4vl@...> wrote:
My server is setup as 311628005 and my talkgroup is 310286

On Wed, Jan 23, 2019 at 1:56 PM Corey Dean N3FE <n3fe@...> wrote:
Your id you are using to connect to 3108 with?

On Wed, Jan 23, 2019 at 2:45 PM K4VL <73dek4vl@...> wrote:
3108

On Wed, Jan 23, 2019 at 1:42 PM Corey Dean N3FE <n3fe@...> wrote:
What master are you trying to connect to?

Corey n3fe

On Wed, Jan 23, 2019 at 2:37 PM K4VL <73dek4vl@...> wrote:
I was wondering... Could my problem be that  my gatewayDmrId in the Analog_Bridge.ini is the same as the Radio ID in my handheld radio? Do I need to get another DMR ID?

On Wed, Jan 23, 2019 at 1:31 PM Steve N4IRS <szingman@...> wrote:
These are the items in MMDVM_Bridge.in that deal with logging into a Master:
[General]
Callsign=W1AW
Id=3112111
Duplex=0

[DMR Network]
Enable=1
Address=310x.repeater.net
Port=62031
Jitter=500
Local=62032
Password=passw0rd
Slot1=1
Slot2=1
Debug=0




On 1/23/2019 2:26 PM, K4VL wrote:
The password under DMR Network is correct

On Wed, Jan 23, 2019 at 1:22 PM Steve N4IRS <szingman@...> wrote:
Check your password. Should be passw0rd Notice the 0

On 1/23/2019 2:20 PM, K4VL wrote:
OK I can see when I key up the last line that comes up says Login to master has failed, retrying login ...

On Wed, Jan 23, 2019 at 1:11 PM Steve N4IRS <szingman@...> wrote:
Run the program(s) in the foreground to look for errors.
Running the program in the foreground simply means starting the program from the command prompt.
Example: root@myhost:/opt/MMDVM_Bridge# ./MMDVM_Host MMDVM.ini This runs the program from the prompt. Notice the ./ in front of the program name. This means run the program in this directory.

On 1/23/2019 2:09 PM, K4VL wrote:
forgive my ignorance but I don't know how to run it in the foreground

On Wed, Jan 23, 2019 at 1:06 PM Steve N4IRS <szingman@...> wrote:
Hoseline has been up and down. First check your self care page and make sure MMDVM_Bridge is logged in to BM. Running MMDVM_Bridge in the foreground will also tell you if it is connected to BM.

On 1/23/2019 2:04 PM, K4VL wrote:
I did see that I am connected to Brandmeister it has me wondering if my radio is not programmed correctly. I did also try to click on hoseline and got a 503 service unavailable page.

On Wed, Jan 23, 2019 at 12:50 PM Steve N4IRS <szingman@...> wrote:
Not a lot of information to go on but in general:
Run each program in the foreground so you can see what is happening. Start at one end and work to the other end.

Steve

On 1/23/2019 1:42 PM, K4VL wrote:
I was wondering how to test my bridge? I don't seem to be getting to it through my hotspot. I went to the CLI and keyed my radio and nothing showed up. My server is setup as 311628005 and my talkgroup is 310286.

Thanks








Virus-free. www.avg.com


Re: HB_Bridge Migration

Cort N0MJS <n0mjs@...>
 

I’m gonna jump in with Steve here to say that HB_Bridge <-> IPSC_Bridge really just works. There’s no need to do much with it. The things I’m working on in hblink3 are increases in performance primarily for large single-ended networks and bridging/routing: Things I’m still envisioning are voice telemetry when bridge actions are taken (really need someone to port the AllStar’s voice library into AMBE files and tell me how they’re packed and I’ll do the rest), a bridge_cache mechanism for faster packet processing (above the 2x speed up of P3 and asyncio) and FINALLY getting better logging/export for a real dashboard that’s worth having.

None of those things really benefit HB_Bridge <-> IPSC_Bridge.

On Jan 24, 2019, at 2:34 PM, Steve N4IRS <szingman@...> wrote:

Jon,
Just so I'm up to speed, other then HB_Bridge <-> IPSC_Bridge What Python3 features is it missing?

Steve

On 1/24/2019 3:31 PM, Jon K1IMD wrote:
JJC, that is interesting.  I wonder how you blended the two applications being that he run in different languages.

Steve, that sounds great!  I know many c-Bridge ops that support hotspot connections would like some of the new features and speed of Python3.  For what I do it does not matter that much except that hblink is going on life support.

73
Jon
K1IMD

On 1/24/2019 13:23, Steve N4IRS wrote:
Jon,
Mike and I have discussed it somewhat. Keeping the ability to bridge IPSC <-> HB is still important.

Steve

On 1/24/2019 1:05 PM, Jon K1IMD wrote:
Steve & Group,
With Cort's announcement of EOL of hblink will there be any migration of HB_Bridge with hblink3?

The reason I ask is that I (and many others I believe) we have a number of ISPC_Bridge<->HB_Bridge to connect mmdvm repeaters to c-Bridges.  In my case I am not doing any TGID translations or remapping presently and I assume that hblink should run fine for the foreseeable future.  However, it would be nice to take advantage of some of the features in hblink3 at some point in the future directly verses perhaps daisy chaining hblink<->hblink3.

73
Jon
K1IMD





Cort Buffington
785-865-7206


Re: HB_Bridge Migration

Cort N0MJS <n0mjs@...>
 

And while they’re different languages, the majority of the syntax is the same – meaning it only took a few hours to get hblink.py to run in python3 vs. python2… The devil is in the details though. While MOST of the syntax is the same, some of the changes required different syntax – especially with a few modules. Quite seriously there were times where one line (like calculating an HMAC and getting it into the right format) took 45 minutes.

On Jan 24, 2019, at 3:13 PM, JJ Cummings <cummingsj@...> wrote:

Python and Python3 can co-exist on the same system (as can pip and pip3) and of course then there is also always virtualenv (all things you can google for more info)

Sent from the iRoad

On Jan 24, 2019, at 13:31, Jon K1IMD <lists@...> wrote:

JJC, that is interesting.  I wonder how you blended the two applications being that he run in different languages.

Steve, that sounds great!  I know many c-Bridge ops that support hotspot connections would like some of the new features and speed of Python3.  For what I do it does not matter that much except that hblink is going on life support.

73
Jon
K1IMD

On 1/24/2019 13:23, Steve N4IRS wrote:
Jon,
Mike and I have discussed it somewhat. Keeping the ability to bridge IPSC <-> HB is still important.

Steve

On 1/24/2019 1:05 PM, Jon K1IMD wrote:
Steve & Group,
With Cort's announcement of EOL of hblink will there be any migration of HB_Bridge with hblink3?

The reason I ask is that I (and many others I believe) we have a number of ISPC_Bridge<->HB_Bridge to connect mmdvm repeaters to c-Bridges.  In my case I am not doing any TGID translations or remapping presently and I assume that hblink should run fine for the foreseeable future.  However, it would be nice to take advantage of some of the features in hblink3 at some point in the future directly verses perhaps daisy chaining hblink<->hblink3.

73
Jon
K1IMD




Cort Buffington
785-865-7206


Re: HB_Bridge Migration

JJ Cummings
 

Python and Python3 can co-exist on the same system (as can pip and pip3) and of course then there is also always virtualenv (all things you can google for more info)

Sent from the iRoad

On Jan 24, 2019, at 13:31, Jon K1IMD <lists@...> wrote:

JJC, that is interesting.  I wonder how you blended the two applications being that he run in different languages.

Steve, that sounds great!  I know many c-Bridge ops that support hotspot connections would like some of the new features and speed of Python3.  For what I do it does not matter that much except that hblink is going on life support.

73
Jon
K1IMD

On 1/24/2019 13:23, Steve N4IRS wrote:
Jon,
Mike and I have discussed it somewhat. Keeping the ability to bridge IPSC <-> HB is still important.

Steve

On 1/24/2019 1:05 PM, Jon K1IMD wrote:
Steve & Group,
With Cort's announcement of EOL of hblink will there be any migration of HB_Bridge with hblink3?

The reason I ask is that I (and many others I believe) we have a number of ISPC_Bridge<->HB_Bridge to connect mmdvm repeaters to c-Bridges.  In my case I am not doing any TGID translations or remapping presently and I assume that hblink should run fine for the foreseeable future.  However, it would be nice to take advantage of some of the features in hblink3 at some point in the future directly verses perhaps daisy chaining hblink<->hblink3.

73
Jon
K1IMD




Re: HB_Bridge Migration

Steve N4IRS
 

Jon,
Just so I'm up to speed, other then HB_Bridge <-> IPSC_Bridge What Python3 features is it missing?

Steve

On 1/24/2019 3:31 PM, Jon K1IMD wrote:
JJC, that is interesting.  I wonder how you blended the two applications being that he run in different languages.

Steve, that sounds great!  I know many c-Bridge ops that support hotspot connections would like some of the new features and speed of Python3.  For what I do it does not matter that much except that hblink is going on life support.

73
Jon
K1IMD

On 1/24/2019 13:23, Steve N4IRS wrote:
Jon,
Mike and I have discussed it somewhat. Keeping the ability to bridge IPSC <-> HB is still important.

Steve

On 1/24/2019 1:05 PM, Jon K1IMD wrote:
Steve & Group,
With Cort's announcement of EOL of hblink will there be any migration of HB_Bridge with hblink3?

The reason I ask is that I (and many others I believe) we have a number of ISPC_Bridge<->HB_Bridge to connect mmdvm repeaters to c-Bridges.  In my case I am not doing any TGID translations or remapping presently and I assume that hblink should run fine for the foreseeable future.  However, it would be nice to take advantage of some of the features in hblink3 at some point in the future directly verses perhaps daisy chaining hblink<->hblink3.

73
Jon
K1IMD





Re: HB_Bridge Migration

Jon K1IMD
 

JJC, that is interesting.  I wonder how you blended the two applications being that he run in different languages.

Steve, that sounds great!  I know many c-Bridge ops that support hotspot connections would like some of the new features and speed of Python3.  For what I do it does not matter that much except that hblink is going on life support.

73
Jon
K1IMD

On 1/24/2019 13:23, Steve N4IRS wrote:
Jon,
Mike and I have discussed it somewhat. Keeping the ability to bridge IPSC <-> HB is still important.

Steve

On 1/24/2019 1:05 PM, Jon K1IMD wrote:
Steve & Group,
With Cort's announcement of EOL of hblink will there be any migration of HB_Bridge with hblink3?

The reason I ask is that I (and many others I believe) we have a number of ISPC_Bridge<->HB_Bridge to connect mmdvm repeaters to c-Bridges.  In my case I am not doing any TGID translations or remapping presently and I assume that hblink should run fine for the foreseeable future.  However, it would be nice to take advantage of some of the features in hblink3 at some point in the future directly verses perhaps daisy chaining hblink<->hblink3.

73
Jon
K1IMD




Re: HB_Bridge Migration

Steve N4IRS
 

Jon,
Mike and I have discussed it somewhat. Keeping the ability to bridge IPSC <-> HB is still important.

Steve

On 1/24/2019 1:05 PM, Jon K1IMD wrote:
Steve & Group,
With Cort's announcement of EOL of hblink will there be any migration of HB_Bridge with hblink3?

The reason I ask is that I (and many others I believe) we have a number of ISPC_Bridge<->HB_Bridge to connect mmdvm repeaters to c-Bridges.  In my case I am not doing any TGID translations or remapping presently and I assume that hblink should run fine for the foreseeable future.  However, it would be nice to take advantage of some of the features in hblink3 at some point in the future directly verses perhaps daisy chaining hblink<->hblink3.

73
Jon
K1IMD



Re: XLX to YSF

Steve N4IRS
 

Notice to all:
Doug will be teaching the next class. ;)

Good to hear.
73, Steve N4IRS

On 1/24/2019 1:20 PM, Doug - W4DBG wrote:
I figured it out. Operator error :) thanks for all the help. By the time I am finished I may know what I am doing. 

On Thu, Jan 24, 2019 at 11:29 AM Steve N4IRS <szingman@...> wrote:
What is not staying connected? DMRGateway or MMDVM_Bridge?



On 1/24/2019 12:15 PM, Doug - W4DBG wrote:
That did it :)

 The only thing I am noticing is that it is not staying connected to the Reflector it does work it just doesn’t stay connected   

On Thu, Jan 24, 2019 at 10:50 AM Steve N4IRS <szingman@...> wrote:
Pay attention to this in MMDVM_Bridge.ini

[DMR Network]
Port=62031
Local=62032

And this in DMRGateway.ini

[General]
RptPort=62032
LocalPort=62031


Steve


On 1/24/2019 11:33 AM, Doug - W4DBG wrote:
Steve,

Can I see your MMDVM_Bridge.ini file?

I really want to learn this one on my own and if I can do all the work I will grasp it more.



On Wed, Jan 23, 2019 at 7:50 PM Steve N4IRS <szingman@...> wrote:
It's waiting for MMDVM_Bridge to connect.

On 1/23/19 8:49 PM, Doug - W4DBG wrote:
Here is the log from DMRGateway:

I: 2019-01-24 01:45:40.230 This software is for use on amateur radio networks only,
I: 2019-01-24 01:45:40.230 it is to be used for educational purposes only. Its use on
I: 2019-01-24 01:45:40.234 commercial networks is strictly prohibited.
I: 2019-01-24 01:45:40.234 Copyright(C) 2017 by Jonathan Naylor, G4KLX and others
M: 2019-01-24 01:45:40.235 DMRGateway-20180606 is starting
M: 2019-01-24 01:45:40.235 Built 15:31:52 Jan 22 2019 (GitID #9579565)
I: 2019-01-24 01:45:40.235 MMDVM Network Parameters
I: 2019-01-24 01:45:40.235     Rpt Address: 127.0.0.1
I: 2019-01-24 01:45:40.236     Rpt Port: 62032
I: 2019-01-24 01:45:40.236     Local Address: 127.0.0.1
I: 2019-01-24 01:45:40.236     Local Port: 62031
M: 2019-01-24 01:45:40.236 MMDVM Network, Opening
M: 2019-01-24 01:45:40.237 Waiting for MMDVM to connect.....

And it just sits there.

On Wed, Jan 23, 2019 at 7:32 PM Steve N4IRS <szingman@...> wrote:
I am hearing the traffic but when I tried this afternoon I had carrier but no audio. It MAY be me. I need to make sure I did not break something here.

On 1/23/19 8:29 PM, Doug - W4DBG wrote:
I saw the same thing. Somehow is the Reflector not seeing what mode you are on?

DMR from MMDVM shows "DMR"

DSTAR shows whatever is setup in the users settings of the radio.



On Wed, Jan 23, 2019 at 7:21 PM Steve N4IRS <szingman@...> wrote:
One thing I'm wondering is why I don't have a suffix. Where does that come from?




On 1/23/19 4:15 PM, Doug - W4DBG wrote:
I am getting:

Cannot bind the UDP Address, err: 99

That might be my problem.



On Wed, Jan 23, 2019 at 12:33 PM Steve N4IRS <szingman@...> wrote:
Maybe this will help:
root@repeater:/opt/DMRGateway# ./DMRGateway DMRGateway.ini
I: 2019-01-23 18:31:40.982 This software is for use on amateur radio networks only,
I: 2019-01-23 18:31:40.982 it is to be used for educational purposes only. Its use on
I: 2019-01-23 18:31:40.982 commercial networks is strictly prohibited.
I: 2019-01-23 18:31:40.982 Copyright(C) 2017 by Jonathan Naylor, G4KLX and others
M: 2019-01-23 18:31:40.983 DMRGateway-20180606 is starting
M: 2019-01-23 18:31:40.983 Built 11:29:08 Jan 10 2019 (GitID #9579565)
I: 2019-01-23 18:31:40.983 MMDVM Network Parameters
I: 2019-01-23 18:31:40.983     Rpt Address: 127.0.0.1
I: 2019-01-23 18:31:40.983     Rpt Port: 62032
I: 2019-01-23 18:31:40.983     Local Address: 127.0.0.1
I: 2019-01-23 18:31:40.983     Local Port: 62031
M: 2019-01-23 18:31:40.984 MMDVM Network, Opening
M: 2019-01-23 18:31:40.984 Waiting for MMDVM to connect.....
M: 2019-01-23 18:32:00.014 MMDVM has connected
I: 2019-01-23 18:32:00.015 Rule trace: no
I: 2019-01-23 18:32:00.017 Loaded 301 XLX reflectors
I: 2019-01-23 18:32:00.017 XLX Network Parameters
I: 2019-01-23 18:32:00.018     Id: 3112138
I: 2019-01-23 18:32:00.018     Hosts file: ./XLXHosts.txt
I: 2019-01-23 18:32:00.018     Reload time: 60 minutes
I: 2019-01-23 18:32:00.018     Local: random
I: 2019-01-23 18:32:00.018     Port: 62030
I: 2019-01-23 18:32:00.018     Slot: 2
I: 2019-01-23 18:32:00.018     TG: 6
I: 2019-01-23 18:32:00.018     Base: 64000
I: 2019-01-23 18:32:00.018     Startup: XLX334
I: 2019-01-23 18:32:00.018     Relink: 10 minutes
I: 2019-01-23 18:32:00.018     User Control: enabled
I: 2019-01-23 18:32:00.018      Module: E
I: 2019-01-23 18:32:00.019 XLX: Using original configuration message: N4IRS   222340000224940000010141.73329-50.39989000Iceberg, North AtlanMMDVM_Bridge       4https://groups.io/g/DVSwitch                                                                                                20180423                                MMDVM_Unknown    
M: 2019-01-23 18:32:00.019 XLX, Opening DMR Network
M: 2019-01-23 18:32:00.019 XLX, Connecting to XLX334
I: 2019-01-23 18:32:00.019 Voice Parameters
I: 2019-01-23 18:32:00.019     Enabled: yes
I: 2019-01-23 18:32:00.019     Language: en_US
I: 2019-01-23 18:32:00.019     Directory: ./Audio
M: 2019-01-23 18:32:00.020 DMRGateway-20180606 is running
D: 2019-01-23 18:32:10.071 XLX, Sending authorisation
D: 2019-01-23 18:32:10.122 XLX, Sending configuration
M: 2019-01-23 18:32:10.173 XLX, Logged into the master successfully
M: 2019-01-23 18:32:10.173 XLX, Linking to reflector XLX334 E



On 1/23/2019 1:29 PM, Doug - W4DBG wrote:
There is an E but no parrot is installed. 

I guess I have muffed something up. I have the same thing as you but no module showing. 

I checked the log and it looks like it connects and disconnects. 




On Wed, Jan 23, 2019 at 12:28 PM Steve N4IRS <szingman@...> wrote:
Is there a Echo module? E?


On 1/23/2019 9:44 AM, Doug - W4DBG wrote:
I will keep plugging away at it. I must still have something “off” attached is a photo of the reflector dashboard showing the module missing. 



On Wed, Jan 23, 2019 at 8:20 AM Steve N4IRS <szingman@...> wrote:
Doug,
I have zero experience with XLX and DMRGateway but I think what you want is is DMRGateway.ini
[XLX Network]
Enabled=1
File=XLXHosts.txt
Port=62030
Password=passw0rd
ReloadTime=60
# Local=3351
Slot=1
TG=6
Base=64000
Startup=950
Relink=10
Debug=0
#Allow user linking control using Private Calls
UserControl=1
#Override default module for startup reflector
#Module=A <-------------------------------------------------------- Uncomment this and set to the module you want.


On 1/23/2019 9:15 AM, Doug - W4DBG wrote:
DMRGateway 



On Wed, Jan 23, 2019 at 8:15 AM Steve N4IRS <szingman@...> wrote:
It is.
Are you using DMRGateway to connect to XLX or going direct from MMDVM_Bridge?

Steve


On 1/23/2019 9:13 AM, Doug - W4DBG wrote:
Maybe I am missing something. Is YSF2DMR in the setup?

I thought that was a hotspot setting?



On Wed, Jan 23, 2019 at 7:13 AM Steve KC1AWV <smiller@...> wrote:
Hi Doug-

I assume you're using YSF2DMR? The DMR Network stanza by default shows commented out settings for XLX. Here's mine for example.

[DMR Network]
Id=[Your DMR ID]
XLXFile=XLXHosts.txt
XLXReflector=740
XLXModule=B
#StartupDstId=9990
# For TG call: StartupPC=0
#StartupPC=1
#Address=44.131.4.1
Port=62030
Jitter=500
EnableUnlink=1
TGUnlink=4000
PCUnlink=0
# Local=62032
Password=PASSWORD
# Options=
TGListFile=TGList-DMR.txt
Debug=0

Steve KC1AWV

On Wed, Jan 23, 2019 at 8:11 AM Doug - W4DBG <douggooden@...> wrote:
Hello to the group...

I have read other threads but I haven't really seen an answer that I am looking for.

I want to bridge a YSF reflector to a XLX Reflector in DMR mode.

It looks like I am successful connecting to the YSF reflector and the XLX reflector using the proper gateways but on the XLX reflector it is not connected to a specific Module. I just need to know what to change to attach it to a specific module.

Thanks!

Doug
W4DBG



--
Doug Gooden
troytrojan@...


--
Steve Miller
KC1AWV
--
Doug Gooden
troytrojan@...

--
Doug Gooden
troytrojan@...

--
Doug Gooden
troytrojan@...

--
Doug Gooden
troytrojan@...



--
Doug Gooden
troytrojan@...



--
Doug Gooden
troytrojan@...



--
Doug Gooden
troytrojan@...



--
Doug Gooden
troytrojan@...

--
Doug Gooden
troytrojan@...

--
Doug Gooden
troytrojan@...


Re: XLX to YSF

Doug - W4DBG
 

I figured it out. Operator error :) thanks for all the help. By the time I am finished I may know what I am doing. 

On Thu, Jan 24, 2019 at 11:29 AM Steve N4IRS <szingman@...> wrote:
What is not staying connected? DMRGateway or MMDVM_Bridge?



On 1/24/2019 12:15 PM, Doug - W4DBG wrote:
That did it :)

 The only thing I am noticing is that it is not staying connected to the Reflector it does work it just doesn’t stay connected   

On Thu, Jan 24, 2019 at 10:50 AM Steve N4IRS <szingman@...> wrote:
Pay attention to this in MMDVM_Bridge.ini

[DMR Network]
Port=62031
Local=62032

And this in DMRGateway.ini

[General]
RptPort=62032
LocalPort=62031


Steve


On 1/24/2019 11:33 AM, Doug - W4DBG wrote:
Steve,

Can I see your MMDVM_Bridge.ini file?

I really want to learn this one on my own and if I can do all the work I will grasp it more.



On Wed, Jan 23, 2019 at 7:50 PM Steve N4IRS <szingman@...> wrote:
It's waiting for MMDVM_Bridge to connect.

On 1/23/19 8:49 PM, Doug - W4DBG wrote:
Here is the log from DMRGateway:

I: 2019-01-24 01:45:40.230 This software is for use on amateur radio networks only,
I: 2019-01-24 01:45:40.230 it is to be used for educational purposes only. Its use on
I: 2019-01-24 01:45:40.234 commercial networks is strictly prohibited.
I: 2019-01-24 01:45:40.234 Copyright(C) 2017 by Jonathan Naylor, G4KLX and others
M: 2019-01-24 01:45:40.235 DMRGateway-20180606 is starting
M: 2019-01-24 01:45:40.235 Built 15:31:52 Jan 22 2019 (GitID #9579565)
I: 2019-01-24 01:45:40.235 MMDVM Network Parameters
I: 2019-01-24 01:45:40.235     Rpt Address: 127.0.0.1
I: 2019-01-24 01:45:40.236     Rpt Port: 62032
I: 2019-01-24 01:45:40.236     Local Address: 127.0.0.1
I: 2019-01-24 01:45:40.236     Local Port: 62031
M: 2019-01-24 01:45:40.236 MMDVM Network, Opening
M: 2019-01-24 01:45:40.237 Waiting for MMDVM to connect.....

And it just sits there.

On Wed, Jan 23, 2019 at 7:32 PM Steve N4IRS <szingman@...> wrote:
I am hearing the traffic but when I tried this afternoon I had carrier but no audio. It MAY be me. I need to make sure I did not break something here.

On 1/23/19 8:29 PM, Doug - W4DBG wrote:
I saw the same thing. Somehow is the Reflector not seeing what mode you are on?

DMR from MMDVM shows "DMR"

DSTAR shows whatever is setup in the users settings of the radio.



On Wed, Jan 23, 2019 at 7:21 PM Steve N4IRS <szingman@...> wrote:
One thing I'm wondering is why I don't have a suffix. Where does that come from?




On 1/23/19 4:15 PM, Doug - W4DBG wrote:
I am getting:

Cannot bind the UDP Address, err: 99

That might be my problem.



On Wed, Jan 23, 2019 at 12:33 PM Steve N4IRS <szingman@...> wrote:
Maybe this will help:
root@repeater:/opt/DMRGateway# ./DMRGateway DMRGateway.ini
I: 2019-01-23 18:31:40.982 This software is for use on amateur radio networks only,
I: 2019-01-23 18:31:40.982 it is to be used for educational purposes only. Its use on
I: 2019-01-23 18:31:40.982 commercial networks is strictly prohibited.
I: 2019-01-23 18:31:40.982 Copyright(C) 2017 by Jonathan Naylor, G4KLX and others
M: 2019-01-23 18:31:40.983 DMRGateway-20180606 is starting
M: 2019-01-23 18:31:40.983 Built 11:29:08 Jan 10 2019 (GitID #9579565)
I: 2019-01-23 18:31:40.983 MMDVM Network Parameters
I: 2019-01-23 18:31:40.983     Rpt Address: 127.0.0.1
I: 2019-01-23 18:31:40.983     Rpt Port: 62032
I: 2019-01-23 18:31:40.983     Local Address: 127.0.0.1
I: 2019-01-23 18:31:40.983     Local Port: 62031
M: 2019-01-23 18:31:40.984 MMDVM Network, Opening
M: 2019-01-23 18:31:40.984 Waiting for MMDVM to connect.....
M: 2019-01-23 18:32:00.014 MMDVM has connected
I: 2019-01-23 18:32:00.015 Rule trace: no
I: 2019-01-23 18:32:00.017 Loaded 301 XLX reflectors
I: 2019-01-23 18:32:00.017 XLX Network Parameters
I: 2019-01-23 18:32:00.018     Id: 3112138
I: 2019-01-23 18:32:00.018     Hosts file: ./XLXHosts.txt
I: 2019-01-23 18:32:00.018     Reload time: 60 minutes
I: 2019-01-23 18:32:00.018     Local: random
I: 2019-01-23 18:32:00.018     Port: 62030
I: 2019-01-23 18:32:00.018     Slot: 2
I: 2019-01-23 18:32:00.018     TG: 6
I: 2019-01-23 18:32:00.018     Base: 64000
I: 2019-01-23 18:32:00.018     Startup: XLX334
I: 2019-01-23 18:32:00.018     Relink: 10 minutes
I: 2019-01-23 18:32:00.018     User Control: enabled
I: 2019-01-23 18:32:00.018      Module: E
I: 2019-01-23 18:32:00.019 XLX: Using original configuration message: N4IRS   222340000224940000010141.73329-50.39989000Iceberg, North AtlanMMDVM_Bridge       4https://groups.io/g/DVSwitch                                                                                                20180423                                MMDVM_Unknown    
M: 2019-01-23 18:32:00.019 XLX, Opening DMR Network
M: 2019-01-23 18:32:00.019 XLX, Connecting to XLX334
I: 2019-01-23 18:32:00.019 Voice Parameters
I: 2019-01-23 18:32:00.019     Enabled: yes
I: 2019-01-23 18:32:00.019     Language: en_US
I: 2019-01-23 18:32:00.019     Directory: ./Audio
M: 2019-01-23 18:32:00.020 DMRGateway-20180606 is running
D: 2019-01-23 18:32:10.071 XLX, Sending authorisation
D: 2019-01-23 18:32:10.122 XLX, Sending configuration
M: 2019-01-23 18:32:10.173 XLX, Logged into the master successfully
M: 2019-01-23 18:32:10.173 XLX, Linking to reflector XLX334 E



On 1/23/2019 1:29 PM, Doug - W4DBG wrote:
There is an E but no parrot is installed. 

I guess I have muffed something up. I have the same thing as you but no module showing. 

I checked the log and it looks like it connects and disconnects. 




On Wed, Jan 23, 2019 at 12:28 PM Steve N4IRS <szingman@...> wrote:
Is there a Echo module? E?


On 1/23/2019 9:44 AM, Doug - W4DBG wrote:
I will keep plugging away at it. I must still have something “off” attached is a photo of the reflector dashboard showing the module missing. 



On Wed, Jan 23, 2019 at 8:20 AM Steve N4IRS <szingman@...> wrote:
Doug,
I have zero experience with XLX and DMRGateway but I think what you want is is DMRGateway.ini
[XLX Network]
Enabled=1
File=XLXHosts.txt
Port=62030
Password=passw0rd
ReloadTime=60
# Local=3351
Slot=1
TG=6
Base=64000
Startup=950
Relink=10
Debug=0
#Allow user linking control using Private Calls
UserControl=1
#Override default module for startup reflector
#Module=A <-------------------------------------------------------- Uncomment this and set to the module you want.


On 1/23/2019 9:15 AM, Doug - W4DBG wrote:
DMRGateway 



On Wed, Jan 23, 2019 at 8:15 AM Steve N4IRS <szingman@...> wrote:
It is.
Are you using DMRGateway to connect to XLX or going direct from MMDVM_Bridge?

Steve


On 1/23/2019 9:13 AM, Doug - W4DBG wrote:
Maybe I am missing something. Is YSF2DMR in the setup?

I thought that was a hotspot setting?



On Wed, Jan 23, 2019 at 7:13 AM Steve KC1AWV <smiller@...> wrote:
Hi Doug-

I assume you're using YSF2DMR? The DMR Network stanza by default shows commented out settings for XLX. Here's mine for example.

[DMR Network]
Id=[Your DMR ID]
XLXFile=XLXHosts.txt
XLXReflector=740
XLXModule=B
#StartupDstId=9990
# For TG call: StartupPC=0
#StartupPC=1
#Address=44.131.4.1
Port=62030
Jitter=500
EnableUnlink=1
TGUnlink=4000
PCUnlink=0
# Local=62032
Password=PASSWORD
# Options=
TGListFile=TGList-DMR.txt
Debug=0

Steve KC1AWV

On Wed, Jan 23, 2019 at 8:11 AM Doug - W4DBG <douggooden@...> wrote:
Hello to the group...

I have read other threads but I haven't really seen an answer that I am looking for.

I want to bridge a YSF reflector to a XLX Reflector in DMR mode.

It looks like I am successful connecting to the YSF reflector and the XLX reflector using the proper gateways but on the XLX reflector it is not connected to a specific Module. I just need to know what to change to attach it to a specific module.

Thanks!

Doug
W4DBG



--
Doug Gooden
troytrojan@...


--
Steve Miller
KC1AWV
--
Doug Gooden
troytrojan@...

--
Doug Gooden
troytrojan@...

--
Doug Gooden
troytrojan@...

--
Doug Gooden
troytrojan@...



--
Doug Gooden
troytrojan@...



--
Doug Gooden
troytrojan@...



--
Doug Gooden
troytrojan@...



--
Doug Gooden
troytrojan@...

--
Doug Gooden
troytrojan@...

--
Doug Gooden
troytrojan@...

7601 - 7620 of 10639