Date   

Re: Large analog_bridge.log

Mike KB8JNM
 

Sounds like a BUG issue for Steve and Mike.

Likely something not exiting after a log entry append.

On 5/14/2021 10:20 AM, oa4doa@... wrote:
I can confirm this issue and it only happens when using the P25 to DMR configuration, restarting one of the AB instances stops the problem momentarily but  when something happens in the DMR part of the bridge and it needs to reconnect to the master the logbook issue starts again, in my case the logbook filled all the remaining space in my SD card, it looks like once the logbook entry is generated it goes into a loop.

I was forgetting to say that the bridge works fine, the only issue is that logbook entry.

Regards,
Christian OA4DOA 


Re: Large analog_bridge.log

oa4doa@...
 

I can confirm this issue and it only happens when using the P25 to DMR configuration, restarting one of the AB instances stops the problem momentarily but  when something happens in the DMR part of the bridge and it needs to reconnect to the master the logbook issue starts again, in my case the logbook filled all the remaining space in my SD card, it looks like once the logbook entry is generated it goes into a loop.

I was forgetting to say that the bridge works fine, the only issue is that logbook entry.

Regards,
Christian OA4DOA 


Re: channel.c:3051 ast_request: No channel type registered

Steve N4IRS
 

Since you already have DVSwitch Server installed, I can't speak to that script, but I would just:
Clean out everything done by the script and then:

apt install allstar.

Steve N4IRS


On 5/14/2021 3:57 AM, Paul on6dp wrote:

HI ,

Yes it’s a new install of allstar link but on the server (VPS on Cloud) there is already a DVSwitch Server (http://dvs.freedmr.be ). The VPS by OVH is under Debian 10 Buster and CPU  AMD64

I mean I have a problem with dahdi. It’s with DKMS

 

Here is the ASL-Build.sh that I was using to build the ASL

 

 

 

 

And when I’m trying to make   apt upgrade -y I have that error

 

 

Any idea to solve that ?

 

73 Paul, ON6DP

 

 

De : main@DVSwitch.groups.io <main@DVSwitch.groups.io> De la part de Steve N4IRS
Envoyé : vendredi 14 mai 2021 00:52
À : main@DVSwitch.groups.io
Objet : Re: [DVSwitch] channel.c:3051 ast_request: No channel type registered

 

Is this a new install? What version of AllStar? Did you make any changes?

On 5/13/21 6:12 PM, Paul on6dp wrote:

Hi guys,
I'm trying to install ASL as Hub but I have the following error messge

[May 14 00:07:39] WARNING[12643]: channel.c:3051 ast_request: No channel type registered for 'dahdi'
rpt:Sorry unable to obtain Rx channel

In module.conf I have :
load => chan_dahdi.so ;

In rpt.conf I have :
[50941]
rxchannel = dahdi/pseudo
;rxchannel = USRP/127.0.0.1:34001:32001  ; Use the USRP channel driver. Must be enabled in modules.conf
                                        ; 127.0.0.1 = IP of the target application
                                        ; 34001 = UDP port the target application is listening on
                                        ; 32001 = UDP port ASL is listening on

duplex = 1                              ; 0 = Half duplex with no telemetry tones or hang time. Ah, but Allison STILL talks!

hangtime = 0                            ; squelch tail hang time 0
althangtime = 0                         ; longer squelch tail hang time 0

holdofftelem = 1                        ; Hold off all telemetry when signal is present on receiver or from connected nodes
                                        ; except when an ID needs to be done and there is a signal coming from a connected node.

telemdefault = 1                        ; 0 = telemetry output off. Don't send Allison to DMR !!!!!!!!!!!!!!!!! Trust me.

telemdynamic = 0                        ; 0 = disallow users to change the local telemetry setting with a COP command,

linktolink = yes                        ; disables forcing physical half-duplex operation of main repeater while
                                        ; still keeping half-duplex semantics (optional)

nounkeyct = 1                           ; Set to a 1 to eliminate courtesy tones and associated delays.

totime = 180000                         ; transmit time-out time (in ms) (optional, default 3 minutes 180000 ms)

idrecording = |ie ON6DP                 ; id recording or morse string see http://ohnosec.org/drupal/node/87
idtalkover = |ie ON6DP                 ; Talkover ID (optional) default is none see http://ohnosec.org/drupal/node/129

The Dahdi vers is DKMS

Where is the mistake ?

Anybody can help Me ?

 


Garanti sans virus. www.avg.com


Re: channel.c:3051 ast_request: No channel type registered

Paul on6dp
 

HI ,

Yes it’s a new install of allstar link but on the server (VPS on Cloud) there is already a DVSwitch Server (http://dvs.freedmr.be ). The VPS by OVH is under Debian 10 Buster and CPU  AMD64

I mean I have a problem with dahdi. It’s with DKMS

 

Here is the ASL-Build.sh that I was using to build the ASL

 

 

 

 

And when I’m trying to make   apt upgrade -y I have that error

 

 

Any idea to solve that ?

 

73 Paul, ON6DP

 

 

De : main@DVSwitch.groups.io <main@DVSwitch.groups.io> De la part de Steve N4IRS
Envoyé : vendredi 14 mai 2021 00:52
À : main@DVSwitch.groups.io
Objet : Re: [DVSwitch] channel.c:3051 ast_request: No channel type registered

 

Is this a new install? What version of AllStar? Did you make any changes?

On 5/13/21 6:12 PM, Paul on6dp wrote:

Hi guys,
I'm trying to install ASL as Hub but I have the following error messge

[May 14 00:07:39] WARNING[12643]: channel.c:3051 ast_request: No channel type registered for 'dahdi'
rpt:Sorry unable to obtain Rx channel

In module.conf I have :
load => chan_dahdi.so ;

In rpt.conf I have :
[50941]
rxchannel = dahdi/pseudo
;rxchannel = USRP/127.0.0.1:34001:32001  ; Use the USRP channel driver. Must be enabled in modules.conf
                                        ; 127.0.0.1 = IP of the target application
                                        ; 34001 = UDP port the target application is listening on
                                        ; 32001 = UDP port ASL is listening on

duplex = 1                              ; 0 = Half duplex with no telemetry tones or hang time. Ah, but Allison STILL talks!

hangtime = 0                            ; squelch tail hang time 0
althangtime = 0                         ; longer squelch tail hang time 0

holdofftelem = 1                        ; Hold off all telemetry when signal is present on receiver or from connected nodes
                                        ; except when an ID needs to be done and there is a signal coming from a connected node.

telemdefault = 1                        ; 0 = telemetry output off. Don't send Allison to DMR !!!!!!!!!!!!!!!!! Trust me.

telemdynamic = 0                        ; 0 = disallow users to change the local telemetry setting with a COP command,

linktolink = yes                        ; disables forcing physical half-duplex operation of main repeater while
                                        ; still keeping half-duplex semantics (optional)

nounkeyct = 1                           ; Set to a 1 to eliminate courtesy tones and associated delays.

totime = 180000                         ; transmit time-out time (in ms) (optional, default 3 minutes 180000 ms)

idrecording = |ie ON6DP                 ; id recording or morse string see http://ohnosec.org/drupal/node/87
idtalkover = |ie ON6DP                 ; Talkover ID (optional) default is none see http://ohnosec.org/drupal/node/129

The Dahdi vers is DKMS

Where is the mistake ?

Anybody can help Me ?

 


Garanti sans virus. www.avg.com


Re: DR2 X connection options

Robin Williams
 

Hi.
The hri200 is connected directly to the Dr-2x repeater.
The pi has a mmdvm hat on it and talks to the repeater on rf .
Hope that helps.
Robin.


On Fri, 14 May 2021, 14:39 N9UMJ, <n9umj2@...> wrote:
Hi Robin

The raspberry pi you mentioned being on the repeater frequency? how are you feeding the audio into pistar on the raspberry pi? and what is the HRi200 connected into? The repeater or the pistar?
I have a DR1X that I'd like to put back online again and  considered bridging  ysf to wires X, Is that what you have done here?

Thanks





On Mon, May 10, 2021 at 5:03 PM Robin Williams <phonetechash@...> wrote:
Hi Jeff.
What we have done here, is, we have a raspberry pi running pi-star sitting next to the repeater and connected to the internet . This is on the repeater frequencys. This pistar is connected to a reflector at my place. This reflector is accessed from anywhere. The repeater also has a hri200 connected directly to it and internet, so we have the best of both worlds.
Cheers
Robin 

On Tue, 11 May 2021, 03:03 Jeff Dixon, <g6yiq.m5aio@...> wrote:
Gents
I have always said if you want to know ask an expert!
I am the keeper of a DR2 X based Wires x connected repeater, It has great coverage up and down a major road so we would rather not use it but some of our members live in RF holes where nothing gets in or out except internet and mobile phones.

I am looking for a reasonably priced way (not an HRi 200 and a £400 radio) that they can link to the repeater. Can we either build a private wires x /Openspot/Zumspot (internet wires X) reflectoer that is connected directly to the repeater or connect it to echolink in some way that still permits Yaesu Wires X/C4FM and FM operation?

Thank you


Re: DR2 X connection options

N9UMJ
 

Hi Robin

The raspberry pi you mentioned being on the repeater frequency? how are you feeding the audio into pistar on the raspberry pi? and what is the HRi200 connected into? The repeater or the pistar?
I have a DR1X that I'd like to put back online again and  considered bridging  ysf to wires X, Is that what you have done here?

Thanks





On Mon, May 10, 2021 at 5:03 PM Robin Williams <phonetechash@...> wrote:
Hi Jeff.
What we have done here, is, we have a raspberry pi running pi-star sitting next to the repeater and connected to the internet . This is on the repeater frequencys. This pistar is connected to a reflector at my place. This reflector is accessed from anywhere. The repeater also has a hri200 connected directly to it and internet, so we have the best of both worlds.
Cheers
Robin 

On Tue, 11 May 2021, 03:03 Jeff Dixon, <g6yiq.m5aio@...> wrote:
Gents
I have always said if you want to know ask an expert!
I am the keeper of a DR2 X based Wires x connected repeater, It has great coverage up and down a major road so we would rather not use it but some of our members live in RF holes where nothing gets in or out except internet and mobile phones.

I am looking for a reasonably priced way (not an HRi 200 and a £400 radio) that they can link to the repeater. Can we either build a private wires x /Openspot/Zumspot (internet wires X) reflectoer that is connected directly to the repeater or connect it to echolink in some way that still permits Yaesu Wires X/C4FM and FM operation?

Thank you


Re: Large analog_bridge.log

Komkit Listisard
 

Mike, stepping out and will be back in a little while.  Basically I have an XLX up and here are the ports that are in use at the moment with all of the stuff that are running.

Struggling with adding P25, when it work it was intermittent.  My NXDN would acting.  Keying up from NXDN would do nothing.  However if I to key up from DMR or D* or YSF, NXDN would lit up and then I can talk on/from NXDN all day long, very strange.  I am sure there is/are conflict somewhere.

NXDN bridged directly to XLX (DMR), I was not going through BM.  P25 also the same way, not going through BM.  Might be some kind of conflict.  Un-bridged P25 for now until we get back and going at it some more.

73, Kit



Re: Large analog_bridge.log

Mike KB8JNM
 

Since you have 2 instances, you might look at ports as well. Make sure each instance is unique port numbers.

Both for your usrp interfaces and mmdvm instances.

Sorry I can't be anything specific. I don't know enough specifics to your issue.

Just some generic advice.

But you could tail the log file when you start/restart for some clues or look in the log.

tail /var/log/dvswitch/Analog_Bridge.log

On 5/13/2021 10:09 PM, Komkit Listisard via groups.io wrote:
Mike, thank you.  I will try it when we get back.  For now I stopped both of the AB instances, I will report back if I find anything.

73, Kit


Re: Large analog_bridge.log

Komkit Listisard
 

Mike, thank you.  I will try it when we get back.  For now I stopped both of the AB instances, I will report back if I find anything.

73, Kit


Re: Large analog_bridge.log

Mike KB8JNM
 

Well,

The first thing I would try is...

systemctl restart analog_bridge

And if that does nothing look in your analog_bridge.ini for any fat finger entries and restart on corrections.

On 5/13/2021 9:40 PM, Komkit Listisard via groups.io wrote:
Hello,

Bridging P25.  My analog_bridge.log got so big filling up 20GB in no time flat!!!

The analog_bridge.log filled up with:

I: 2021-05-14 01:05:58.605 EVENT: {"topic":"dvswitch/MMDVM_Bridge/DMR","message":"login success"}
I: 2021-05-14 01:05:58.605 EVENT: {"topic":"dvswitch/MMDVM_Bridge/DMR","message":"login success"}
I: 2021-05-14 01:05:58.605 EVENT: {"topic":"dvswitch/MMDVM_Bridge/DMR","message":"login success"}
I: 2021-05-14 01:05:58.605 EVENT: {"topic":"dvswitch/MMDVM_Bridge/DMR","message":"login success"}
I: 2021-05-14 01:05:58.605 EVENT: {"topic":"dvswitch/MMDVM_Bridge/DMR","message":"login success"}
I: 2021-05-14 01:05:58.605 EVENT: {"topic":"dvswitch/MMDVM_Bridge/DMR","message":"login success"}
I: 2021-05-14 01:05:58.605 EVENT: {"topic":"dvswitch/MMDVM_Bridge/DMR","message":"login success"}
I: 2021-05-14 01:05:58.605 EVENT: {"topic":"dvswitch/MMDVM_Bridge/DMR","message":"login success"}
I: 2021-05-14 01:05:58.605 EVENT: {"topic":"dvswitch/MMDVM_Bridge/DMR","message":"login success"}
I: 2021-05-14 01:05:58.605 EVENT: {"topic":"dvswitch/MMDVM_Bridge/DMR","message":"login success"}
I: 2021-05-14 01:05:58.605 EVENT: {"topic":"dvswitch/MMDVM_Bridge/DMR","message":"login success"}
I: 2021-05-14 01:05:58.605 EVENT: {"topic":"dvswitch/MMDVM_Bridge/DMR","message":"login success"}
I: 2021-05-14 01:05:58.605 EVENT: {"topic":"dvswitch/MMDVM_Bridge/DMR","message":"login success"}
I: 2021-05-14 01:05:58.605 EVENT: {"topic":"dvswitch/MMDVM_Bridge/DMR","message":"login success"}
I: 2021-05-14 01:05:58.605 EVENT: {"topic":"dvswitch/MMDVM_Bridge/DMR","message":"login success"}
I: 2021-05-14 01:05:58.606 EVENT: {"topic":"dvswitch/MMDVM_Bridge/DMR","message":"login success"}
I: 2021-05-14 01:05:58.606 EVENT: {"topic":"dvswitch/MMDVM_Bridge/DMR","message":"login success"}
I: 2021-05-14 01:05:58.606 EVENT: {"topic":"dvswitch/MMDVM_Bridge/DMR","message":"login success"}
I: 2021-05-14 01:05:58.606 EVENT: {"topic":"dvswitch/MMDVM_Bridge/DMR","message":"login success"}
I: 2021-05-14 01:05:58.606 EVENT: {"topic":"dvswitch/MMDVM_Bridge/DMR","message":"login success"}
I: 2021-05-14 01:05:58.606 EVENT: {"topic":"dvswitch/MMDVM_Bridge/DMR","message":"login success"}
I: 2021-05-14 01:05:58.606 EVENT: {"topic":"dvswitch/MMDVM_Bridge/DMR","message":"login success"}
I: 2021-05-14 01:05:58.606 EVENT: {"topic":"dvswitch/MMDVM_Bridge/DMR","message":"login success"}
I: 2021-05-14 01:05:58.606 EVENT: {"topic":"dvswitch/MMDVM_Bridge/DMR","message":"login success"}
I: 2021-05-14 01:05:58.606 EVENT: {"topic":"dvswitch/MMDVM_Bridge/DMR","message":"login success"}
I: 2021-05-14 01:05:58.606 EVENT: {"topic":"dvswitch/MMDVM_Bridge/DMR","message":"login success"}
I: 2021-05-14 01:05:58.606 EVENT: ^C

What did I do wrong?

73, Kit


Large analog_bridge.log

Komkit Listisard
 

Hello,

Bridging P25.  My analog_bridge.log got so big filling up 20GB in no time flat!!!

The analog_bridge.log filled up with:

I: 2021-05-14 01:05:58.605 EVENT: {"topic":"dvswitch/MMDVM_Bridge/DMR","message":"login success"}
I: 2021-05-14 01:05:58.605 EVENT: {"topic":"dvswitch/MMDVM_Bridge/DMR","message":"login success"}
I: 2021-05-14 01:05:58.605 EVENT: {"topic":"dvswitch/MMDVM_Bridge/DMR","message":"login success"}
I: 2021-05-14 01:05:58.605 EVENT: {"topic":"dvswitch/MMDVM_Bridge/DMR","message":"login success"}
I: 2021-05-14 01:05:58.605 EVENT: {"topic":"dvswitch/MMDVM_Bridge/DMR","message":"login success"}
I: 2021-05-14 01:05:58.605 EVENT: {"topic":"dvswitch/MMDVM_Bridge/DMR","message":"login success"}
I: 2021-05-14 01:05:58.605 EVENT: {"topic":"dvswitch/MMDVM_Bridge/DMR","message":"login success"}
I: 2021-05-14 01:05:58.605 EVENT: {"topic":"dvswitch/MMDVM_Bridge/DMR","message":"login success"}
I: 2021-05-14 01:05:58.605 EVENT: {"topic":"dvswitch/MMDVM_Bridge/DMR","message":"login success"}
I: 2021-05-14 01:05:58.605 EVENT: {"topic":"dvswitch/MMDVM_Bridge/DMR","message":"login success"}
I: 2021-05-14 01:05:58.605 EVENT: {"topic":"dvswitch/MMDVM_Bridge/DMR","message":"login success"}
I: 2021-05-14 01:05:58.605 EVENT: {"topic":"dvswitch/MMDVM_Bridge/DMR","message":"login success"}
I: 2021-05-14 01:05:58.605 EVENT: {"topic":"dvswitch/MMDVM_Bridge/DMR","message":"login success"}
I: 2021-05-14 01:05:58.605 EVENT: {"topic":"dvswitch/MMDVM_Bridge/DMR","message":"login success"}
I: 2021-05-14 01:05:58.605 EVENT: {"topic":"dvswitch/MMDVM_Bridge/DMR","message":"login success"}
I: 2021-05-14 01:05:58.606 EVENT: {"topic":"dvswitch/MMDVM_Bridge/DMR","message":"login success"}
I: 2021-05-14 01:05:58.606 EVENT: {"topic":"dvswitch/MMDVM_Bridge/DMR","message":"login success"}
I: 2021-05-14 01:05:58.606 EVENT: {"topic":"dvswitch/MMDVM_Bridge/DMR","message":"login success"}
I: 2021-05-14 01:05:58.606 EVENT: {"topic":"dvswitch/MMDVM_Bridge/DMR","message":"login success"}
I: 2021-05-14 01:05:58.606 EVENT: {"topic":"dvswitch/MMDVM_Bridge/DMR","message":"login success"}
I: 2021-05-14 01:05:58.606 EVENT: {"topic":"dvswitch/MMDVM_Bridge/DMR","message":"login success"}
I: 2021-05-14 01:05:58.606 EVENT: {"topic":"dvswitch/MMDVM_Bridge/DMR","message":"login success"}
I: 2021-05-14 01:05:58.606 EVENT: {"topic":"dvswitch/MMDVM_Bridge/DMR","message":"login success"}
I: 2021-05-14 01:05:58.606 EVENT: {"topic":"dvswitch/MMDVM_Bridge/DMR","message":"login success"}
I: 2021-05-14 01:05:58.606 EVENT: {"topic":"dvswitch/MMDVM_Bridge/DMR","message":"login success"}
I: 2021-05-14 01:05:58.606 EVENT: {"topic":"dvswitch/MMDVM_Bridge/DMR","message":"login success"}
I: 2021-05-14 01:05:58.606 EVENT: ^C

What did I do wrong?

73, Kit


Re: channel.c:3051 ast_request: No channel type registered

Steve N4IRS
 

Is this a new install? What version of AllStar? Did you make any changes?

On 5/13/21 6:12 PM, Paul on6dp wrote:
Hi guys,
I'm trying to install ASL as Hub but I have the following error messge

[May 14 00:07:39] WARNING[12643]: channel.c:3051 ast_request: No channel type registered for 'dahdi'
rpt:Sorry unable to obtain Rx channel

In module.conf I have :
load => chan_dahdi.so ;

In rpt.conf I have :
[50941]
rxchannel = dahdi/pseudo
;rxchannel = USRP/127.0.0.1:34001:32001  ; Use the USRP channel driver. Must be enabled in modules.conf
                                        ; 127.0.0.1 = IP of the target application
                                        ; 34001 = UDP port the target application is listening on
                                        ; 32001 = UDP port ASL is listening on

duplex = 1                              ; 0 = Half duplex with no telemetry tones or hang time. Ah, but Allison STILL talks!

hangtime = 0                            ; squelch tail hang time 0
althangtime = 0                         ; longer squelch tail hang time 0

holdofftelem = 1                        ; Hold off all telemetry when signal is present on receiver or from connected nodes
                                        ; except when an ID needs to be done and there is a signal coming from a connected node.

telemdefault = 1                        ; 0 = telemetry output off. Don't send Allison to DMR !!!!!!!!!!!!!!!!! Trust me.

telemdynamic = 0                        ; 0 = disallow users to change the local telemetry setting with a COP command,

linktolink = yes                        ; disables forcing physical half-duplex operation of main repeater while
                                        ; still keeping half-duplex semantics (optional)

nounkeyct = 1                           ; Set to a 1 to eliminate courtesy tones and associated delays.

totime = 180000                         ; transmit time-out time (in ms) (optional, default 3 minutes 180000 ms)

idrecording = |ie ON6DP                 ; id recording or morse string see http://ohnosec.org/drupal/node/87
idtalkover = |ie ON6DP                 ; Talkover ID (optional) default is none see http://ohnosec.org/drupal/node/129

The Dahdi vers is DKMS

Where is the mistake ?

Anybody can help Me ?



channel.c:3051 ast_request: No channel type registered

Paul on6dp
 

Hi guys,
I'm trying to install ASL as Hub but I have the following error messge

[May 14 00:07:39] WARNING[12643]: channel.c:3051 ast_request: No channel type registered for 'dahdi'
rpt:Sorry unable to obtain Rx channel

In module.conf I have :
load => chan_dahdi.so ;

In rpt.conf I have :
[50941]
rxchannel = dahdi/pseudo
;rxchannel = USRP/127.0.0.1:34001:32001  ; Use the USRP channel driver. Must be enabled in modules.conf
                                        ; 127.0.0.1 = IP of the target application
                                        ; 34001 = UDP port the target application is listening on
                                        ; 32001 = UDP port ASL is listening on

duplex = 1                              ; 0 = Half duplex with no telemetry tones or hang time. Ah, but Allison STILL talks!

hangtime = 0                            ; squelch tail hang time 0
althangtime = 0                         ; longer squelch tail hang time 0

holdofftelem = 1                        ; Hold off all telemetry when signal is present on receiver or from connected nodes
                                        ; except when an ID needs to be done and there is a signal coming from a connected node.

telemdefault = 1                        ; 0 = telemetry output off. Don't send Allison to DMR !!!!!!!!!!!!!!!!! Trust me.

telemdynamic = 0                        ; 0 = disallow users to change the local telemetry setting with a COP command,

linktolink = yes                        ; disables forcing physical half-duplex operation of main repeater while
                                        ; still keeping half-duplex semantics (optional)

nounkeyct = 1                           ; Set to a 1 to eliminate courtesy tones and associated delays.

totime = 180000                         ; transmit time-out time (in ms) (optional, default 3 minutes 180000 ms)

idrecording = |ie ON6DP                 ; id recording or morse string see http://ohnosec.org/drupal/node/87
idtalkover = |ie ON6DP                 ; Talkover ID (optional) default is none see http://ohnosec.org/drupal/node/129

The Dahdi vers is DKMS

Where is the mistake ?

Anybody can help Me ?


Re: DVSWITCH USRP registration drops when idle for a few minutes

Mike Zingman - N4IRR
 

Yes, many routers have problems with "hairpin" routes.
https://en.wikipedia.org/wiki/Hairpinning


Re: DVSWITCH USRP registration drops when idle for a few minutes

krugaber@...
 

Steve,  Problem solved!!  i am using NOIP.COM to direct traffic to the public of my router and then on to my Allstar Node as well as my DVSWITCH server.  The only time I have an issue is when I am at home and do this using USRP for digital contacts on DMR.  So if at home I now use the DVSWITCH Lan IP address and all is good.  When away from I use my service provider cell hotspot and all is well.

There others in our group that don't have the issue but they are using different routers.  Mine is a Netgear.

Thanks for your help.  The divide and conquer routine did its job.

73,

Ken KC9QV


DMR <> P25 (XLX)

Komkit Listisard
 

Hello,

Currently I have DMR <> NXDN bridged using mmdvm_bridge.  My XLX DMR is on 62030.  I looked up the DMR <> P25 bridge diagram,  I see that I need 1 instance of MB and 2 of AB.

Since I have BM running for DMR <> NXDN. Do I need another MB or I can use the same one just have to enable P25?

I plan to have the DMR <> P25 bridge on the same server.  Can it be done since port 62030 is already in use by DMR <> NXDN?

73, Kit

 


Re: DR2 X connection options

Robin Williams
 

Hi 
Just set the hotspot to duplex mode.
Program frquencies and away you go .
Tx frequency is receive fx of repeater and vice versa for Rx frequency 
Robin .

On Wed, 12 May 2021, 05:26 Jeff Dixon, <g6yiq.m5aio@...> wrote:
Robin,
Sorry another question, how did you seperate the TX and RX frequencies?
Did you program it in repeater mode and then switch it back to simplex or am I making it far too complex. I cannot make it tx on one frequency and rx on the other in simplex.

Regards,
Jeff


Re: DR2 X connection options

Jeff Dixon
 

Robin,
Sorry another question, how did you seperate the TX and RX frequencies?
Did you program it in repeater mode and then switch it back to simplex or am I making it far too complex. I cannot make it tx on one frequency and rx on the other in simplex.

Regards,
Jeff


Re: Free DMR with DVS

inmarex@...
 

In order to make it work you need to setup Options field. 


ASL<>YSF dashboard callsign for gateway id?

 

I've been helping a ham with a bridge and we got everything working however, the dashboard
http://ysf.praredn.org/
is showing the DMR ID for the bridge's gateway id instead of the resolved callsign.
I see a database in the /var/lib/mmdvm and it has the callsign/id in it.

not sure if it matters for the problem, but I've got two instances of mmdvm bridge. 1 is ASL<>YSF the other is DMR<>YSF

What am I missing?

361 - 380 of 9595