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





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