Date   

Re: #brandmeister #brandmeister

Steve N4IRS
 

Based on the log, I think MB has a problem with the config. Not sure what. I would:
systemctl stop mmdvm_bridge
cd /opt/MMDVM_Bridge
./MMDVM_Bridge MMDVM_Bridge.ini
show the result, to the end.

Steve

On 3/23/2021 12:34 PM, Bill Kittilson wrote:
On Tue, Mar 23, 2021 at 09:29 AM, Steve N4IRS wrote:
I would like to see the log where MB is trying to connect to BM.


Re: #brandmeister #brandmeister

Bill Kittilson <bill.kittilson@...>
 

On Tue, Mar 23, 2021 at 09:29 AM, Steve N4IRS wrote:
I would like to see the log where MB is trying to connect to BM.


Re: #brandmeister #brandmeister

Steve N4IRS
 

OK,
Your settings look good. I would like to see the log where MB is trying to connect to BM.

On 3/23/2021 12:25 PM, Bill Kittilson wrote:
log file:

I: 2021-03-23 15:56:02.904     Callsign: N3JHS
I: 2021-03-23 15:56:02.904     Id: 3142103
I: 2021-03-23 15:56:02.904     Duplex: no
I: 2021-03-23 15:56:02.904     Timeout: 180s
I: 2021-03-23 15:56:02.905     D-Star: disabled
I: 2021-03-23 15:56:02.905     DMR: enabled
I: 2021-03-23 15:56:02.905     YSF: enabled
I: 2021-03-23 15:56:02.905     P25: disabled
I: 2021-03-23 15:56:02.905     NXDN: disabled
I: 2021-03-23 15:56:02.905 Modem Parameters
I: 2021-03-23 15:56:02.905     Port: /dev/null
I: 2021-03-23 15:56:02.905     RX Invert: no
I: 2021-03-23 15:56:02.905     TX Invert: no
I: 2021-03-23 15:56:02.905     PTT Invert: no
I: 2021-03-23 15:56:02.905     TX Delay: 100ms
I: 2021-03-23 15:56:02.905     RX Offset: 0Hz
I: 2021-03-23 15:56:02.905     TX Offset: 0Hz
I: 2021-03-23 15:56:02.905     RX DC Offset: 0
I: 2021-03-23 15:56:02.905     TX DC Offset: 0
I: 2021-03-23 15:56:02.905     RF Level: 100.0%
I: 2021-03-23 15:56:02.905     DMR Delay: 0 (0.0ms)
I: 2021-03-23 15:56:02.905     RX Level: 50.0%
I: 2021-03-23 15:56:02.905     CW Id TX Level: 50.0%
I: 2021-03-23 15:56:02.905     D-Star TX Level: 50.0%
I: 2021-03-23 15:56:02.905     DMR TX Level: 50.0%
I: 2021-03-23 15:56:02.905     YSF TX Level: 50.0%
I: 2021-03-23 15:56:02.905     P25 TX Level: 50.0%
I: 2021-03-23 15:56:02.905     NXDN TX Level: 50.0%
I: 2021-03-23 15:56:02.905     RX Frequency: 446100000Hz (446100000Hz)
I: 2021-03-23 15:56:02.905     TX Frequency: 446100000Hz (446100000Hz)
M: 2021-03-23 15:56:02.905 Opening the MMDVM
I: 2021-03-23 15:56:02.905 Display Parameters
I: 2021-03-23 15:56:02.905     Type: 
I: 2021-03-23 15:56:02.905 DMR Network Parameters
I: 2021-03-23 15:56:02.905     Address: 3103.repeater.net
I: 2021-03-23 15:56:02.905     Port: 0
I: 2021-03-23 15:56:02.905     Local: 62031
I: 2021-03-23 15:56:02.905     Jitter: 360ms
I: 2021-03-23 15:56:02.905     Slot 1: disabled
I: 2021-03-23 15:56:02.905     Slot 2: enabled
I: 2021-03-23 15:56:02.905     Mode Hang: 3s

[General]
Callsign=N3JHS
Id=3142103
Timeout=180
Duplex=0
 
[Info]
RXFrequency=446100000
TXFrequency=446100000
Power=1
Latitude=40.151390
Longitude=-74.827390
Height=30
Location=Levittown, PA
Description=MMDVM_Bridge
 
 


Re: #brandmeister #brandmeister

Bill Kittilson <bill.kittilson@...>
 

log file:

I: 2021-03-23 15:56:02.904     Callsign: N3JHS
I: 2021-03-23 15:56:02.904     Id: 3142103
I: 2021-03-23 15:56:02.904     Duplex: no
I: 2021-03-23 15:56:02.904     Timeout: 180s
I: 2021-03-23 15:56:02.905     D-Star: disabled
I: 2021-03-23 15:56:02.905     DMR: enabled
I: 2021-03-23 15:56:02.905     YSF: enabled
I: 2021-03-23 15:56:02.905     P25: disabled
I: 2021-03-23 15:56:02.905     NXDN: disabled
I: 2021-03-23 15:56:02.905 Modem Parameters
I: 2021-03-23 15:56:02.905     Port: /dev/null
I: 2021-03-23 15:56:02.905     RX Invert: no
I: 2021-03-23 15:56:02.905     TX Invert: no
I: 2021-03-23 15:56:02.905     PTT Invert: no
I: 2021-03-23 15:56:02.905     TX Delay: 100ms
I: 2021-03-23 15:56:02.905     RX Offset: 0Hz
I: 2021-03-23 15:56:02.905     TX Offset: 0Hz
I: 2021-03-23 15:56:02.905     RX DC Offset: 0
I: 2021-03-23 15:56:02.905     TX DC Offset: 0
I: 2021-03-23 15:56:02.905     RF Level: 100.0%
I: 2021-03-23 15:56:02.905     DMR Delay: 0 (0.0ms)
I: 2021-03-23 15:56:02.905     RX Level: 50.0%
I: 2021-03-23 15:56:02.905     CW Id TX Level: 50.0%
I: 2021-03-23 15:56:02.905     D-Star TX Level: 50.0%
I: 2021-03-23 15:56:02.905     DMR TX Level: 50.0%
I: 2021-03-23 15:56:02.905     YSF TX Level: 50.0%
I: 2021-03-23 15:56:02.905     P25 TX Level: 50.0%
I: 2021-03-23 15:56:02.905     NXDN TX Level: 50.0%
I: 2021-03-23 15:56:02.905     RX Frequency: 446100000Hz (446100000Hz)
I: 2021-03-23 15:56:02.905     TX Frequency: 446100000Hz (446100000Hz)
M: 2021-03-23 15:56:02.905 Opening the MMDVM
I: 2021-03-23 15:56:02.905 Display Parameters
I: 2021-03-23 15:56:02.905     Type: 
I: 2021-03-23 15:56:02.905 DMR Network Parameters
I: 2021-03-23 15:56:02.905     Address: 3103.repeater.net
I: 2021-03-23 15:56:02.905     Port: 0
I: 2021-03-23 15:56:02.905     Local: 62031
I: 2021-03-23 15:56:02.905     Jitter: 360ms
I: 2021-03-23 15:56:02.905     Slot 1: disabled
I: 2021-03-23 15:56:02.905     Slot 2: enabled
I: 2021-03-23 15:56:02.905     Mode Hang: 3s

[General]
Callsign=N3JHS
Id=3142103
Timeout=180
Duplex=0
 
[Info]
RXFrequency=446100000
TXFrequency=446100000
Power=1
Latitude=40.151390
Longitude=-74.827390
Height=30
Location=Levittown, PA
Description=MMDVM_Bridge
URL=https://groups.io/g/DVSwitch
 
 


Re: #brandmeister #brandmeister

Steve N4IRS
 

Set duplex = 0
frequencies to simplex
make sure callsign and dmrID point to correct user.

What does the log show?

On 3/23/2021 12:10 PM, Bill Kittilson wrote:

I am no longer able to connect to brandmister,  I checked with brandmister and I am not blocked.   I did enable my password and changed the MMDVM_bridge.ini file.  I did fix the frequency in the file also.  

 

Is this the current version of MMDVM_Bridge  1.01-20180420-3?

 

 

[DMR Network]

Enable=1

Address=3103.repeater.net

Jitter=360

Local=62031

Password=mypassword

# for DMR+ see https://github.com/DVSwitch/MMDVM_Bridge/blob/master/DOC/DMRplus_startup_options.md

# for XLX the syntax is: Options=XLX:4009

# Options=

Slot1=0

Slot2=1

Debug=1

 

 

Any ideas?

 

 

Thanks

Bill N3JHS



#brandmeister #brandmeister

Bill Kittilson <bill.kittilson@...>
 

I am no longer able to connect to brandmister,  I checked with brandmister and I am not blocked.   I did enable my password and changed the MMDVM_bridge.ini file.  I did fix the frequency in the file also.  

 

Is this the current version of MMDVM_Bridge  1.01-20180420-3?

 

 

[DMR Network]

Enable=1

Address=3103.repeater.net

Jitter=360

Local=62031

Password=mypassword

# for DMR+ see https://github.com/DVSwitch/MMDVM_Bridge/blob/master/DOC/DMRplus_startup_options.md

# for XLX the syntax is: Options=XLX:4009

# Options=

Slot1=0

Slot2=1

Debug=1

 

 

Any ideas?

 

 

Thanks

Bill N3JHS


Re: DMR Chan Chg problem on RPi4

Chris K7AZ
 

I hope to upgrade my nodes to RTCM and RPi4 soon.  All parts in hand.  Just need to stuff the 1's and 0's in the right place.  :)



Sent from my Verizon, Samsung Galaxy smartphone


-------- Original message --------
From: Steve N4IRS <szingman@...>
Date: 3/22/21 13:48 (GMT-08:00)
To: main@DVSwitch.groups.io
Subject: Re: [DVSwitch] DMR Chan Chg problem on RPi4

No problem

Sent by smoke signal (AT&T)

From: main@... <main@DVSwitch.groups.io> on behalf of Gary <w5bi@...>
Sent: Monday, March 22, 2021 4:29:44 PM
To: main@DVSwitch.groups.io <main@DVSwitch.groups.io>
Subject: Re: [DVSwitch] DMR Chan Chg problem on RPi4
 
My repeater uses RTCM and thus "rxchannel=Voter/27610".
I created a separate node and link to it for DMR, etc:
[1973]
rxchannel=USRP/127.0.0.1:34001:32001
duplex=0



See any problems with this approach?

de W5BI Gary


Re: DMR Chan Chg problem on RPi4

Steve N4IRS
 

No problem

Sent by smoke signal (AT&T)


From: main@DVSwitch.groups.io <main@DVSwitch.groups.io> on behalf of Gary <w5bi@...>
Sent: Monday, March 22, 2021 4:29:44 PM
To: main@DVSwitch.groups.io <main@DVSwitch.groups.io>
Subject: Re: [DVSwitch] DMR Chan Chg problem on RPi4
 
My repeater uses RTCM and thus "rxchannel=Voter/27610".
I created a separate node and link to it for DMR, etc:
[1973]
rxchannel=USRP/127.0.0.1:34001:32001
duplex=0
.
.

See any problems with this approach?

de W5BI Gary


Re: Bridge

Randy AA6RH
 

On Mon, Mar 22, 2021 at 08:40 AM, Steve N4IRS wrote:
BM is unhappy about any bridge they do not control.
Understatement of the week right there.

--R
--
Randy Hall AA6RH (not K7AGE, quit asking) 😁


Re: DMR Chan Chg problem on RPi4

Gary
 

My repeater uses RTCM and thus "rxchannel=Voter/27610".
I created a separate node and link to it for DMR, etc:
[1973]
rxchannel=USRP/127.0.0.1:34001:32001
duplex=0
.
.

See any problems with this approach?

de W5BI Gary


Re: DMR Chan Chg problem on RPi4

Steve N4IRS
 

Good, question. That imag was a proof of concept quickie. Next one will be more complete.

So, if you are going to start with the AllStarLink beta:
Boot the image and go through their complete setup. Make sure the node is working correctly
reboot
wget http://dvswitch.org/buster
chmod +x buster
./buster
apt install dvswitch-server
Use the dvs menu to setup DVSwitch Server
Make sure everything is working.
apt install analog-reflector
cd /opt/Analog_Reflector
cd ssl
./mkcerts.sh
cd /opt/Analog_Reflector
edit Analog_Reflector.json (change as little as possible)
edit DMR ID etc
Put in your AllStar node number (in place of 1999)
 edit /etc/asterisk/rpt.conf
Change you node to use the rxchannel chan_usrp (unless the ASL menu let you do this already.)
enable chan_usrp in modules.conf

Steve N4IRS

On 3/22/2021 3:34 PM, Gary wrote:
Thanks fer reply Steve.

BTW, "rpt fun 27610 *327580" does work with good audio telem response. No idea why the "*09xxxx" autopatch trick fails.
Further debug req'd.

If I use ASL 2.0x Beta image on RPi4 as starting point,
  what are proper install steps fer DVSwitch-Server & Analog-Reflector?

de W5BI Gary


Re: DMR Chan Chg problem on RPi4

Gary
 

Thanks fer reply Steve.

BTW, "rpt fun 27610 *327580" does work with good audio telem response. No idea why the "*09xxxx" autopatch trick fails.
Further debug req'd.

If I use ASL 2.0x Beta image on RPi4 as starting point,
  what are proper install steps fer DVSwitch-Server & Analog-Reflector?

de W5BI Gary


Re: DMR Chan Chg problem on RPi4

Steve N4IRS
 

Gary,
I would say yes, it looks like there is problem with the current DVSwitch-Server-Allstar-lite based on your error. Once we complete the next software release, we will be revisiting the images. (menus, dashboard etc) There are a few upgrades that need to be made.

Steve N4IRS

On 3/22/2021 2:02 PM, Gary wrote:
Installed on RPi4 using 2021-02-14-DVSwitch-Server-Allstar-lite.zip
All  AOK until attempt to chg DMT TG...(using autopatch hook) ...NO audio spoken and system hangs
Cud this be issue with kernel on RPi4?? Should I start with ASL Beta 2.xx image??
BTW, running FB on RPi3.
Snippet here...

W5BIRPTR*CLI> rpt fun 27610 *093135
    -- Executing [3135@tgtune:1] NoOp("DAHDI/pseudo-1726154610", "1") in new stack
    -- Executing [3135@tgtune:2] SayAlpha("DAHDI/pseudo-1726154610", "dmr|3135") in new stack
    -- <DAHDI/pseudo-1726154610> Playing 'letters/d' (language 'en')
W5BIRPTR*CLI>
Message from syslogd@W5BIRPTR at Mar 22 11:33:49 ...
 kernel:[73522.219444] Internal error: Oops: 207 [#1] SMP ARM

Message from syslogd@W5BIRPTR at Mar 22 11:33:49 ...
 kernel:[73522.219860] Process asterisk (pid: 31385, stack limit = 0xa771d5fd)

Message from syslogd@W5BIRPTR at Mar 22 11:33:49 ...
 kernel:[73522.219866] Stack: (0xc4b4fdc0 to 0xc4b50000)

Message from syslogd@W5BIRPTR at Mar 22 11:33:49 ...
 kernel:[73522.219876] fdc0: c024f42c c032dfbc 00000000 c0247594 60000013 c4b4fdd8 0000800c 0000800e
.
.
.


DMR Chan Chg problem on RPi4

Gary
 
Edited

Installed on RPi4 using 2021-02-14-DVSwitch-Server-Allstar-lite.zip
All  AOK until attempt to chg DMT TG...(using autopatch hook) ...NO audio spoken and system hangs
Cud this be issue with kernel on RPi4?? Should I start with ASL Beta 2.xx image??
BTW, running FB on RPi3.
Snippet here...

W5BIRPTR*CLI> rpt fun 27610 *093135
    -- Executing [3135@tgtune:1] NoOp("DAHDI/pseudo-1726154610", "1") in new stack
    -- Executing [3135@tgtune:2] SayAlpha("DAHDI/pseudo-1726154610", "dmr|3135") in new stack
    -- <DAHDI/pseudo-1726154610> Playing 'letters/d' (language 'en')
W5BIRPTR*CLI>
Message from syslogd@W5BIRPTR at Mar 22 11:33:49 ...
 kernel:[73522.219444] Internal error: Oops: 207 [#1] SMP ARM

Message from syslogd@W5BIRPTR at Mar 22 11:33:49 ...
 kernel:[73522.219860] Process asterisk (pid: 31385, stack limit = 0xa771d5fd)

Message from syslogd@W5BIRPTR at Mar 22 11:33:49 ...
 kernel:[73522.219866] Stack: (0xc4b4fdc0 to 0xc4b50000)

Message from syslogd@W5BIRPTR at Mar 22 11:33:49 ...
 kernel:[73522.219876] fdc0: c024f42c c032dfbc 00000000 c0247594 60000013 c4b4fdd8 0000800c 0000800e
.
.
.
EDIR: rpt fun 27610 *3xxxxx works and produces good audio telem.


Re: Bridge

mark rosenberg
 

Yep i did that and it started workkng again, but 4z1yr told me that he thinks they still want to get rid of our cloud bridges


On Mon, Mar 22, 2021, 17:40 Steve N4IRS <szingman@...> wrote:
BM is unhappy about any bridge they do not control.

BM is implementing controls to disallow mis-configured hotspots from connecting to their network. Some of our early configurations violate this and cause a connection to not complete. Here is what you need to check:
in /opt/MMDVM_Bridge/MMDVM_Bridge.ini

[General]
Callsign=N4IRS
Id=3112138
duplex=0
 
[Info]
RXFrequency=224940000
TXFrequency=224940000
 
Make sure your RX Frequency matches your TX frequency and that your callsign is correct for your DMRID+SSID
 
restart.

We have a replacement connection method in beta test now. That method, Simple Terminal Feature Update uses the connection method required by BM. Simple Terminal Feature Update is our answer to BM. We will release the software on March 1.

Steve N4IRS

On 3/22/2021 10:47 AM, Pierre Martel wrote:
It is not that they are unhappy about bridges.  What they don't like is the fact that some bridges are done in such a way that it creates loops between multiple networks. 


Le lun. 22 mars 2021 à 10:33, mark rosenberg <4x1ks.mark@...> a écrit :
Something is going on with BM not happy about bridge service to allstar. I have a cloud server with allstar bridged to bm and i have heard that they consider bridges using cloud servers or rpi's to be troublesome

On Thu, Dec 17, 2020, 05:34 <ibjosh1985@...> wrote:
3165298


Re: Bridge

Steve N4IRS
 

BM is unhappy about any bridge they do not control.

BM is implementing controls to disallow mis-configured hotspots from connecting to their network. Some of our early configurations violate this and cause a connection to not complete. Here is what you need to check:
in /opt/MMDVM_Bridge/MMDVM_Bridge.ini

[General]
Callsign=N4IRS
Id=3112138
duplex=0
 
[Info]
RXFrequency=224940000
TXFrequency=224940000
 
Make sure your RX Frequency matches your TX frequency and that your callsign is correct for your DMRID+SSID
 
restart.

We have a replacement connection method in beta test now. That method, Simple Terminal Feature Update uses the connection method required by BM. Simple Terminal Feature Update is our answer to BM. We will release the software on March 1.

Steve N4IRS

On 3/22/2021 10:47 AM, Pierre Martel wrote:
It is not that they are unhappy about bridges.  What they don't like is the fact that some bridges are done in such a way that it creates loops between multiple networks. 


Le lun. 22 mars 2021 à 10:33, mark rosenberg <4x1ks.mark@...> a écrit :
Something is going on with BM not happy about bridge service to allstar. I have a cloud server with allstar bridged to bm and i have heard that they consider bridges using cloud servers or rpi's to be troublesome

On Thu, Dec 17, 2020, 05:34 <ibjosh1985@...> wrote:
3165298


Re: Bridge

Pierre Martel
 

It is not that they are unhappy about bridges.  What they don't like is the fact that some bridges are done in such a way that it creates loops between multiple networks. 


Le lun. 22 mars 2021 à 10:33, mark rosenberg <4x1ks.mark@...> a écrit :
Something is going on with BM not happy about bridge service to allstar. I have a cloud server with allstar bridged to bm and i have heard that they consider bridges using cloud servers or rpi's to be troublesome

On Thu, Dec 17, 2020, 05:34 <ibjosh1985@...> wrote:
3165298


Re: Bridge

mark rosenberg
 

Something is going on with BM not happy about bridge service to allstar. I have a cloud server with allstar bridged to bm and i have heard that they consider bridges using cloud servers or rpi's to be troublesome


On Thu, Dec 17, 2020, 05:34 <ibjosh1985@...> wrote:
3165298


Re: Bridge

Randy AA6RH
 

On Sun, Mar 21, 2021 at 09:26 PM, <ibjosh1985@...> wrote:
not looking for some one to do it for me just answer questions i have sent my files , logs and copy and past so the audio bridge file for dmr once launched it says it cannot bind a port but when changing ports it still say's the samething and then i'm getting this Your gatewayDmrId 3174494 is NOT  in the subscriber file.
Fantastic, glad to hear that you're on board with doing the work.

Part of that work is to carefully diagram what you're configuration looks like in a block diagram with arrows indicating data flows (and port numbers). This will help you figure out what the configuration looks like (because we've been saying that this looks like a configuration problem). Please do the diagram (there are examples on this site, look in the wiki (one example is on this page: https://dvswitch.groups.io/g/main/wiki/3016) and then provide that as a reply here.

It is my feeling (and I think Steve would agree) that if you do this, the problem is going to become either a) obvious to you, so that you can fix it, or b) obvious to us, so we can offer specific advice.

Thanks,

--R
 
--
Randy Hall AA6RH (not K7AGE, quit asking) 😁


Re: Bridge

Steve N4IRS
 

Your configuration will look like this:

DMR Network <-> MMDVM_Bridge_DMR <-> Analog_Bridge_DMR <-> Analog_Bridge_P25 <-> MMDVM_Bridge_P25 <-> P25Gateway <-> P25 Network
MMDVM_Bridge_DMR and MMDVM_Bridge_P25 are a single instance of MMDVM_Bridge
Analog_Bridge_DMR and Analog_Bridge_P25 are 2 instances of Anallog_Bridge

1: stop ALL dvswitch services.
2: Setup MMDVM_Bridge to connect the the DMR network. Verify it is connecting and passing traffic. Run it in the foreground so you can see the traffic. Only enable the DMR mode and DMR Networking.
    You will need to set a static TG in selfcare if using BM.
 
 

On 3/22/2021 9:17 AM, ibjosh1985@... wrote:
DMR / P25

VPS running Debian

881 - 900 of 9821