Date   

Re: Asterisk Error

K4VL
 

BTW I'm getting the same error when I look at the status of mmdvm_bridge. analog_bridge is running.


Re: Asterisk Error

K4VL
 

The logs appear empty. I event went into the asterisk log folder and opened the event log and it was blank.


Re: Asterisk Error

Steve KC1AWV
 

Ok, sorry I was thinking along the systemd lines. Run this instead

tail -n50 /var/log/asterisk/messages

That will show the actual error. The journal logs are just showing the restarts that systemd is doing 

On Tue, Mar 26, 2019, 9:06 PM K4VL <73dek4vl@...> wrote:
On Tue, Mar 26, 2019 at 12:23 PM, Steve KC1AWV wrote:
journalctl -u asterisk.service --since today
 
This is what it does every ten minutes it seams. I have no idea what this means.

-- Logs begin at Mon 2019-03-25 09:17:01 CDT, end at Tue 2019-03-26 20:04:48 CDT. --
Mar 26 17:46:39 repeater systemd[1]: asterisk.service: Service hold-off time over, scheduling restart.
Mar 26 17:46:39 repeater systemd[1]: Stopped Asterisk PBX and telephony daemon.
Mar 26 17:46:39 repeater systemd[1]: Started Asterisk PBX and telephony daemon.
Mar 26 17:46:39 repeater systemd[1]: asterisk.service: Main process exited, code=exited, status=1/FAILURE
Mar 26 17:46:39 repeater systemd[1]: asterisk.service: Control process exited, code=exited status=1
Mar 26 17:46:39 repeater systemd[1]: asterisk.service: Unit entered failed state.
Mar 26 17:46:39 repeater systemd[1]: asterisk.service: Failed with result 'exit-code'.
Mar 26 17:46:49 repeater systemd[1]: asterisk.service: Service hold-off time over, scheduling restart.
Mar 26 17:46:49 repeater systemd[1]: Stopped Asterisk PBX and telephony daemon.
Mar 26 17:46:49 repeater systemd[1]: Started Asterisk PBX and telephony daemon.
Mar 26 17:46:49 repeater systemd[1]: asterisk.service: Main process exited, code=exited, status=1/FAILURE
Mar 26 17:46:49 repeater systemd[1]: asterisk.service: Control process exited, code=exited status=1
Mar 26 17:46:49 repeater systemd[1]: asterisk.service: Unit entered failed state.
Mar 26 17:46:49 repeater systemd[1]: asterisk.service: Failed with result 'exit-code'.
Mar 26 17:46:59 repeater systemd[1]: asterisk.service: Service hold-off time over, scheduling restart.
Mar 26 17:46:59 repeater systemd[1]: Stopped Asterisk PBX and telephony daemon.
Mar 26 17:46:59 repeater systemd[1]: Started Asterisk PBX and telephony daemon.
Mar 26 17:46:59 repeater systemd[1]: asterisk.service: Main process exited, code=exited, status=1/FAILURE
Mar 26 17:46:59 repeater systemd[1]: asterisk.service: Control process exited, code=exited status=1
Mar 26 17:46:59 repeater systemd[1]: asterisk.service: Unit entered failed state.
Mar 26 17:46:59 repeater systemd[1]: asterisk.service: Failed with result 'exit-code'.
Mar 26 17:47:10 repeater systemd[1]: asterisk.service: Service hold-off time over, scheduling restart.
Mar 26 17:47:10 repeater systemd[1]: Stopped Asterisk PBX and telephony daemon.
Mar 26 17:47:10 repeater systemd[1]: Started Asterisk PBX and telephony daemon.
Mar 26 17:47:10 repeater systemd[1]: asterisk.service: Main process exited, code=exited, status=1/FAILURE
Mar 26 17:47:10 repeater systemd[1]: asterisk.service: Control process exited, code=exited status=1
Mar 26 17:47:10 repeater systemd[1]: asterisk.service: Unit entered failed state.
Mar 26 17:47:10 repeater systemd[1]: asterisk.service: Failed with result 'exit-code'.
Mar 26 17:47:20 repeater systemd[1]: asterisk.service: Service hold-off time over, scheduling restart.
Mar 26 17:47:20 repeater systemd[1]: Stopped Asterisk PBX and telephony daemon.
Mar 26 17:47:20 repeater systemd[1]: Started Asterisk PBX and telephony daemon.
Mar 26 17:47:20 repeater systemd[1]: asterisk.service: Main process exited, code=exited, status=1/FAILURE
Mar 26 17:47:20 repeater systemd[1]: asterisk.service: Control process exited, code=exited status=1


Re: Asterisk Error

K4VL
 

On Tue, Mar 26, 2019 at 12:23 PM, Steve KC1AWV wrote:
journalctl -u asterisk.service --since today
 
This is what it does every ten minutes it seams. I have no idea what this means.

-- Logs begin at Mon 2019-03-25 09:17:01 CDT, end at Tue 2019-03-26 20:04:48 CDT. --
Mar 26 17:46:39 repeater systemd[1]: asterisk.service: Service hold-off time over, scheduling restart.
Mar 26 17:46:39 repeater systemd[1]: Stopped Asterisk PBX and telephony daemon.
Mar 26 17:46:39 repeater systemd[1]: Started Asterisk PBX and telephony daemon.
Mar 26 17:46:39 repeater systemd[1]: asterisk.service: Main process exited, code=exited, status=1/FAILURE
Mar 26 17:46:39 repeater systemd[1]: asterisk.service: Control process exited, code=exited status=1
Mar 26 17:46:39 repeater systemd[1]: asterisk.service: Unit entered failed state.
Mar 26 17:46:39 repeater systemd[1]: asterisk.service: Failed with result 'exit-code'.
Mar 26 17:46:49 repeater systemd[1]: asterisk.service: Service hold-off time over, scheduling restart.
Mar 26 17:46:49 repeater systemd[1]: Stopped Asterisk PBX and telephony daemon.
Mar 26 17:46:49 repeater systemd[1]: Started Asterisk PBX and telephony daemon.
Mar 26 17:46:49 repeater systemd[1]: asterisk.service: Main process exited, code=exited, status=1/FAILURE
Mar 26 17:46:49 repeater systemd[1]: asterisk.service: Control process exited, code=exited status=1
Mar 26 17:46:49 repeater systemd[1]: asterisk.service: Unit entered failed state.
Mar 26 17:46:49 repeater systemd[1]: asterisk.service: Failed with result 'exit-code'.
Mar 26 17:46:59 repeater systemd[1]: asterisk.service: Service hold-off time over, scheduling restart.
Mar 26 17:46:59 repeater systemd[1]: Stopped Asterisk PBX and telephony daemon.
Mar 26 17:46:59 repeater systemd[1]: Started Asterisk PBX and telephony daemon.
Mar 26 17:46:59 repeater systemd[1]: asterisk.service: Main process exited, code=exited, status=1/FAILURE
Mar 26 17:46:59 repeater systemd[1]: asterisk.service: Control process exited, code=exited status=1
Mar 26 17:46:59 repeater systemd[1]: asterisk.service: Unit entered failed state.
Mar 26 17:46:59 repeater systemd[1]: asterisk.service: Failed with result 'exit-code'.
Mar 26 17:47:10 repeater systemd[1]: asterisk.service: Service hold-off time over, scheduling restart.
Mar 26 17:47:10 repeater systemd[1]: Stopped Asterisk PBX and telephony daemon.
Mar 26 17:47:10 repeater systemd[1]: Started Asterisk PBX and telephony daemon.
Mar 26 17:47:10 repeater systemd[1]: asterisk.service: Main process exited, code=exited, status=1/FAILURE
Mar 26 17:47:10 repeater systemd[1]: asterisk.service: Control process exited, code=exited status=1
Mar 26 17:47:10 repeater systemd[1]: asterisk.service: Unit entered failed state.
Mar 26 17:47:10 repeater systemd[1]: asterisk.service: Failed with result 'exit-code'.
Mar 26 17:47:20 repeater systemd[1]: asterisk.service: Service hold-off time over, scheduling restart.
Mar 26 17:47:20 repeater systemd[1]: Stopped Asterisk PBX and telephony daemon.
Mar 26 17:47:20 repeater systemd[1]: Started Asterisk PBX and telephony daemon.
Mar 26 17:47:20 repeater systemd[1]: asterisk.service: Main process exited, code=exited, status=1/FAILURE
Mar 26 17:47:20 repeater systemd[1]: asterisk.service: Control process exited, code=exited status=1


Re: Asterisk Error

Steve KC1AWV
 

Try running the command

journalctl -u asterisk.service --since today

to view more of the asterisk logs to find the error.

On Tue, Mar 26, 2019 at 1:22 PM K4VL <73dek4vl@...> wrote:
After a power failure my asterisk quit working. See the attached. I ran systemctl status asterisk



--
Steve Miller
KC1AWV


Asterisk Error

K4VL
 

After a power failure my asterisk quit working. See the attached. I ran systemctl status asterisk


Re: DMR to DSTAR

David
 

HI Steve
does dvswitch support DVmege 3003 transcode ?
http://www.dvmega.co.uk/AMBE3003%20DV%20USB%20Stick.html 

because i had this .and it can not detect this dongle


Re: DTMF

Rob WX1N
 

Thanks Steve. Any plans to add that in the future or a way, or is it too much effort to be worth it?

-----Original Message-----
From: main@DVSwitch.groups.io <main@DVSwitch.groups.io> On Behalf Of Steve N4IRS
Sent: Sunday, March 24, 2019 15:01
To: main@DVSwitch.groups.io
Subject: Re: [DVSwitch] DTMF

Rob,
The USRP_channel driver does not decode DTMF. So the answer is no, you can not decode the DTMF and control the ASL node.

73, Steve N4IRS

On 3/24/19 12:36 PM, Rob WX1N wrote:
Hi Steve and all,

Did any of you go any further with this? I have a DMR<>analog bridge going, but the USRP channel driver does not appear to decode DTMF. I've verified that the DMR radio in question does indeed transmit DTMF via the DMR audio, and that it decodes nicely in other applications, but monitoring the asterisk cli, no digits are detected. Not sure if this is a hard and fast limitation of the USRP driver, or if there is a way to configure it to pass the dtmf through to the ASL software.

Rob, WX1N



Re: DTMF

Steve N4IRS
 

Rob,
The USRP_channel driver does not decode DTMF. So the answer is no, you can not decode the DTMF and control the ASL node.

73, Steve N4IRS

On 3/24/19 12:36 PM, Rob WX1N wrote:
Hi Steve and all,

Did any of you go any further with this? I have a DMR<>analog bridge going, but the USRP channel driver does not appear to decode DTMF. I've verified that the DMR radio in question does indeed transmit DTMF via the DMR audio, and that it decodes nicely in other applications, but monitoring the asterisk cli, no digits are detected. Not sure if this is a hard and fast limitation of the USRP driver, or if there is a way to configure it to pass the dtmf through to the ASL software.

Rob, WX1N


Re: DTMF

Rob WX1N
 

Hi Steve and all,

Did any of you go any further with this? I have a DMR<>analog bridge going, but the USRP channel driver does not appear to decode DTMF. I've verified that the DMR radio in question does indeed transmit DTMF via the DMR audio, and that it decodes nicely in other applications, but monitoring the asterisk cli, no digits are detected. Not sure if this is a hard and fast limitation of the USRP driver, or if there is a way to configure it to pass the dtmf through to the ASL software.

Rob, WX1N


Re: Setting up a YSFn <--> ASL bridge

steve@...
 

Thanks for you replies!  I'm happy to say it's working now.  I plugged in the IP address instead of the name, changed the local address to 0 and the gateway port to 42001 (I tried 42000 but according to the trusty pi-star YSFHosts.txt file it said it was 42001 for Americalink).  Now I'm getting audio and it seems to be working fine.  Thanks very much for your help.
73,
Steve - W7RD


Re: Linking P25 to P25 using two mmdvm's

Mike AE4ML
 

I have done this on raspberry pi 2 and 3B+


Re: Linking P25 to P25 using two mmdvm's

Tony Steele
 

Ok,
Ignore the last, I tried a different image for the OrangePi Zero, this time I used Armbian and the install of p25reflector seems to have gone fine with no errors.

Now to proceed with the rest of the install.


Re: Which base image to use with DV Switch: Allstar or HamVoIP

David McGough
 

Hi,

Yes, I've got a alpha pre-release test package now. This weekend I'm
verifying that nothing is "badly broken." I expect a preliminary release
announcement this weekend.

73, David KB4FXC

On Sat, 23 Mar 2019, Igor Videc wrote:

David,

have you made any progress with this ?

73
Igor 9A6NVI




Re: Which base image to use with DV Switch: Allstar or HamVoIP

Igor Videc
 

David,

have you made any progress with this ?

73
Igor 9A6NVI


Re: Setting up a YSFn <--> ASL bridge

Doug - W4DBG
 

The Gateway Port should be 42001

Doug
W4DBG




On Sat, Mar 23, 2019 at 8:54 AM steve via Groups.Io <steve=w7rd.com@groups.io> wrote:
Hi,
I've set up numerous DMR <--> ASL bridges and they all work fine.  It seems like it would be a walk in the park to switch out YSFn for DMR.  But I'm having no luck.  The logs haven't been much help either:
From MM_DVM_Bridge.ini:

[System Fusion Network]
Enable=1
LocalAddress=127.0.0.1
LocalPort=3200
GatewayPort=42166
Debug=1

And from DVSwitch.ini:

[YSF]
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)
FallbackID = 3113417            ; In case we can not find a valid DMR id in the database, export this one
ExportTG = 13953                 ; Which TG to export
Slot = 2   

And Analog_Bridge.ini:

[AMBE_AUDIO]
address = 127.0.0.1                     ; IP address of xx_Bridge
txPort = 31103                          ; Transmit TLV frames to partner on this port
rxPort = 31100                          ; Listen for TLV frames from partner on this port
ambeMode = YSFN                          ; DMR, DMR_IPSC, DSTAR, NXDN, P25, YSFN, YSFW (encode PCM to this format)
minTxTimeMS = 2000   

gatewayDmrId = 3113417                        ; ID to use when transmitting from Analog_Bridge
repeaterID = 311341706                          ; ID of source repeater
txTg = 13953                                ; TG to use for all frames sent from Analog_Bridge -> xx_Bridge
txTs = 2                                ; Slot to use for frames sent from Analog_Bridge -> xx_Bridge
colorCode = 1   

Does anyone know what I'm doing wrong or have success with doing this and can give me a pointer or two?
Thanks and 73,
Steve - W7RD

--
Doug Gooden
troytrojan@...


Re: Setting up a YSFn <--> ASL bridge

Mike KB8JNM
 

Not sure...
But I would use the ip over the domain. It saves a step looking up the IP address. Double check your info...
the registry shows this...
TG 02034
96.47.95.121
port 42000

https://register.ysfreflector.de/

If you would like to test, try ysfn tg 88023 (asl 29999)
64.154.38.103
port 42000
dash 29999.link/ysf

On 3/23/2019 9:54 AM, steve via Groups.Io wrote:
Hi,
I've set up numerous DMR <--> ASL bridges and they all work fine.  It seems like it would be a walk in the park to switch out YSFn for DMR.  But I'm having no luck.  The logs haven't been much help either:
From MM_DVM_Bridge.ini:
[System Fusion Network]
Enable=1
LocalAddress=127.0.0.1
LocalPort=3200
GatewayAddress=amlink.alabamalink.info
GatewayPort=42166
Debug=1
And from DVSwitch.ini:
[YSF]
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)
FallbackID = 3113417            ; In case we can not find a valid DMR id in the database, export this one
ExportTG = 13953                 ; Which TG to export
Slot = 2
And Analog_Bridge.ini:
[AMBE_AUDIO]
address = 127.0.0.1                     ; IP address of xx_Bridge
txPort = 31103                          ; Transmit TLV frames to partner on this port
rxPort = 31100                          ; Listen for TLV frames from partner on this port
ambeMode = YSFN                          ; DMR, DMR_IPSC, DSTAR, NXDN, P25, YSFN, YSFW (encode PCM to this format)
minTxTimeMS = 2000
gatewayDmrId = 3113417                        ; ID to use when transmitting from Analog_Bridge
repeaterID = 311341706                          ; ID of source repeater
txTg = 13953                                ; TG to use for all frames sent from Analog_Bridge -> xx_Bridge
txTs = 2                                ; Slot to use for frames sent from Analog_Bridge -> xx_Bridge
colorCode = 1
Does anyone know what I'm doing wrong or have success with doing this and can give me a pointer or two?
Thanks and 73,
Steve - W7RD


Re: Setting up a YSFn <--> ASL bridge

Steve N4IRS
 

Steve,
In MMDVM_Bridge [System Fusion Network] stanza set:
LocalAddress=0

What are you seeing in the logs?

That all being said, though the bridge will work, I suggest after making sure everything connects and you can pass traffic, you wait a few days. I will be testing and then updating MMDVM_Bridge. There are a couple of bugs that cause issues for people listening on some radios on the YSFReflector.

Steve

On 3/23/19 9:54 AM, steve via Groups.Io wrote:
Hi,
I've set up numerous DMR <--> ASL bridges and they all work fine.  It seems like it would be a walk in the park to switch out YSFn for DMR.  But I'm having no luck.  The logs haven't been much help either:
From MM_DVM_Bridge.ini:

[System Fusion Network]
Enable=1
LocalAddress=127.0.0.1
LocalPort=3200
GatewayAddress=amlink.alabamalink.info
GatewayPort=42166
Debug=1

And from DVSwitch.ini:

[YSF]
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)
FallbackID = 3113417            ; In case we can not find a valid DMR id in the database, export this one
ExportTG = 13953                 ; Which TG to export
Slot = 2   

And Analog_Bridge.ini:

[AMBE_AUDIO]
address = 127.0.0.1                     ; IP address of xx_Bridge
txPort = 31103                          ; Transmit TLV frames to partner on this port
rxPort = 31100                          ; Listen for TLV frames from partner on this port
ambeMode = YSFN                          ; DMR, DMR_IPSC, DSTAR, NXDN, P25, YSFN, YSFW (encode PCM to this format)
minTxTimeMS = 2000   

gatewayDmrId = 3113417                        ; ID to use when transmitting from Analog_Bridge
repeaterID = 311341706                          ; ID of source repeater
txTg = 13953                                ; TG to use for all frames sent from Analog_Bridge -> xx_Bridge
txTs = 2                                ; Slot to use for frames sent from Analog_Bridge -> xx_Bridge
colorCode = 1   

Does anyone know what I'm doing wrong or have success with doing this and can give me a pointer or two?
Thanks and 73,
Steve - W7RD


Setting up a YSFn <--> ASL bridge

steve@...
 

Hi,
I've set up numerous DMR <--> ASL bridges and they all work fine.  It seems like it would be a walk in the park to switch out YSFn for DMR.  But I'm having no luck.  The logs haven't been much help either:
From MM_DVM_Bridge.ini:

[System Fusion Network]
Enable=1
LocalAddress=127.0.0.1
LocalPort=3200
GatewayAddress=amlink.alabamalink.info
GatewayPort=42166
Debug=1

And from DVSwitch.ini:

[YSF]
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)
FallbackID = 3113417            ; In case we can not find a valid DMR id in the database, export this one
ExportTG = 13953                 ; Which TG to export
Slot = 2   

And Analog_Bridge.ini:

[AMBE_AUDIO]
address = 127.0.0.1                     ; IP address of xx_Bridge
txPort = 31103                          ; Transmit TLV frames to partner on this port
rxPort = 31100                          ; Listen for TLV frames from partner on this port
ambeMode = YSFN                          ; DMR, DMR_IPSC, DSTAR, NXDN, P25, YSFN, YSFW (encode PCM to this format)
minTxTimeMS = 2000   

gatewayDmrId = 3113417                        ; ID to use when transmitting from Analog_Bridge
repeaterID = 311341706                          ; ID of source repeater
txTg = 13953                                ; TG to use for all frames sent from Analog_Bridge -> xx_Bridge
txTs = 2                                ; Slot to use for frames sent from Analog_Bridge -> xx_Bridge
colorCode = 1   

Does anyone know what I'm doing wrong or have success with doing this and can give me a pointer or two?
Thanks and 73,
Steve - W7RD


Re: Linking P25 to P25 using two mmdvm's

Tony Steele
 

Mike,
I've fallen at the (almost) first hurdle!
Using an OrangePi zero running Raspbian.
I've installed the dvswitch repo, then done an
apt-get update
then apt-get install dvswitch
Which initially seems fine, but as the install progress's, it  seems to fail with the following

orangepi@OrangePI:/tmp$ sudo apt-get install dvswitch
.......
.....
...
.
Setting up dvswitch-base (1.01-20180420-11) ...
dpkg: error processing package dvswitch-base (--configure):
 subprocess installed post-installation script returned error exit status 5
dpkg: dependency problems prevent configuration of analog-bridge:
 analog-bridge depends on dvswitch-base; however:
  Package dvswitch-base is not configured yet.
 
dpkg: error processing package analog-bridge (--configure):
 dependency problems - leaving unconfigured
Setting up md380-emu (1.1-20180424-3) ...
/var/lib/dpkg/info/md380-emu.postinst: 5: /var/lib/dpkg/info/md380-emu.postinst: systemctl: not found
dpkg: error processing package md380-emu (--configure):
 subprocess installed post-installation script returned error exit status 127
dpkg: dependency problems prevent configuration of mmdvm-bridge:
 mmdvm-bridge depends on dvswitch-base; however:
  Package dvswitch-base is not configured yet.
 
dpkg: error processing package mmdvm-bridge (--configure):
 dependency problems - leaving unconfigured
Errors were encountered while processing:
 dvswitch-base
 analog-bridge
 md380-emu
 mmdvm-bridge
E: Sub-process /usr/bin/dpkg returned an error code (1)
 

Can you suggest what could be the issue?  I can't see that i've missed anything.
Does something require configuring?

I'm lost!!

Regards
Tony

5961 - 5980 of 9589