Anyone else lose echolink when DMR was added?
ASL 1.01 with everything working. Added DMR (AnalogBridge<>MD380<>MMDVM) using node 1999 (in rpt.conf the DMR node description is at the top of the file). DMR works fine, including changing TGs.
Tried an echolink connect. The echolink node was not logging into the echolink control server. (echolink set to load in modules.conf, echolink.conf from a previous operating implementation (DIAL).
Any ideas??
…STeve - KF5VH
Additional info … IAX works just fine but found this is the /var/log/asterisk/messages file.
[Jun 7 13:27:47] ERROR[458] chan_echolink.c: Unable to resolve echolink APRS server IP address
I don’t see an APRS config file in /etc/asterisk. Any ideas?
…STeve - KF5VH
Steve,
Analog_Bridge simply uses the USRP channel driver to bring digital audio and signaling into ASL.
I can tell you that I run a ASL node with both Analog_Bridge and Echolink. I use a private node 1999 for Analog_Bridge and node 1998 for Echolink. You should be able to disable node 1999 and have EchoLink work as normal. Once you have that working re-add 1999. We do have a discussion area setup where peer to peer support is available for Analog_Bridge connected ASL nodes. https://dvswitch.groups.io/g/allstarlink
73, Steve N4IRS
Steve:
I removed the DMR additions in /etc/asterisk/*.conf and Echolink returned to normal function.
I am curious about your statement that you use node 1998 for Echolink. Is there a place to set that or did I miss it ?? How do I see what it is set to now?
If I add DMR back in and it doesn’t work, should I try changing DMR to a different node number?
…STeve - KF5VH
I’ve moved the DMR 1999 stanza below the radio stanza 42315, echolink doesn’t work.
I’ve moved the DMR stanza back above the radio stanza, echolink doesn’t work.
I’ve changed the numbering of node 1999 to 1991 (all locations), echolink doesn’t work.
But commenting out all references to DMR allows Echolink to work.
Looking for any ideas.
…STeve
How do I tell what node number my echolink is using? Or, how can I force it to a known number?
…STeve
See “astnode =” in echolink.cfg
Steve N4IRS
On 6/19/2019 2:07 PM, Steve Mahler -
KF5VH via AllStarLink Discussion Groups wrote:
June 19 How do I tell what nodenumber my echolink is using? Or, how can I force it to a
known number?
…STeve
Visit Topic
or reply to this email to respond.
In Reply To
June 8 Steve, Analog_Bridge simply usesthe USRP channel driver to bring digital audio and signaling
into ASL. I can tell you that I run a ASL node with both
Analog_Bridge and Echolink. I use a private node 1999 for
Analog_Bridge and node 1998 for Echolink. You should be able
to disable node 1999 and hav…
Visit Topic or reply to
this email to respond.
To unsubscribe from these emails, click here.
Ever since day one … I had astnode=42315 and have now changed to astnode=1999
So, in rpt.conf it should look like …
42315 = radio@127.0.0.1:4569/42315,NONE ; This must be changed to your node number
1999 = radio@127.0.0.1:4569/1999,NONE ; This is the ECHOLINK SUPPORT NODE, a private node number
1991 = radio@127.0.0.1:4569/1991,NONE ; This is the DMR SUPPORT NODE, a private node number
DMR is working, but *31999 gets a connection fail and the echolink doesn’t log into the echolink network.
What am I not understanding?
…STeve
Do you have a node stanza in rpt.conf?
Have you added 1999 and 1991 to extensions.conf?
Example:
`[globals]
HOMENPA = 772 ; change this to your Area Code
NODE = 2600 ; Hub
NODE9 = 42565 ; Public Parrot
NODE1 = 1999 ; Echolink
NODE2 = 1998 ; AMBE
NODE3 = 1997 ; IMBE
NODE4 = 1996 ; DSAMBE
NODE5 = 1995 ; Parrot
NODE6 = 1994 ; Chat
NODE7 = 1993 ;
[default]
exten => i,1,Hangup
[radio-secure]
exten => ${NODE},1,rpt,${NODE} ; 2600
exten => ${NODE1},1,rpt,${NODE1} ; Echolink
exten => ${NODE2},1,rpt,${NODE2} ; AMBE
exten => ${NODE3},1,rpt,${NODE3} ; IMBE
exten => ${NODE4},1,rpt,${NODE4} ; DSAMBE
exten => ${NODE5},1,rpt,${NODE5} ;
exten => ${NODE6},1,rpt,${NODE6} ; Chat
exten => ${NODE9},1,rpt,${NODE9} ;
`
On 6/19/19 4:04 PM, Steve Mahler -
KF5VH via AllStarLink Discussion Groups wrote:
June 19 Ever since day one … Ihad astnode=42315 and have now changed to astnode=1999
So, in rpt.conf itshould look like …
42315 =; This must be changed to
your node number
1999 = ; This is the
ECHOLINK SUPPORT NODE, a private node number
1991 = ; This is the DMR
SUPPORT NODE, a private node number
DMR is working, but*31999 gets a connection fail and the echolink doesn’t log
into the echolink network.
What am I notunderstanding?
…STeve
Visit Topic
or reply to this email to respond.
In Reply To
June 19 See “astnode =” in echolink.cfgSteve N4IRS
··· (click for more details)
Visit Topic or reply to
this email to respond.
To unsubscribe from these emails, click here.
radio@127.0.0.1:4569/42315,NONE
radio@127.0.0.1:4569/1999,NONE
radio@127.0.0.1:4569/1991,NONE
rpt.conf has …
; NODE BELOW, 1991 IS USED FOR DMR
[1991]
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 = 0 ; 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 receive
telemdefault = 0 ; 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 = no ; disables forcing physical half-duplex operation
nounkeyct = 1 ; Set to a 1 to eliminate courtesy tones
totime = 180000 ; transmit time-out time (in ms) default 3 minutes 180000 ms)
idrecording = |ie ; id recording or morse string see http://ohnosec.org/drupal/node/87
idtalkover = |ie ; Talkover ID (optional)
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
followed by the [42315] stanza (normal config) including …
rxchannel = SimpleUSB/usb_42315 ; SimpleUSB
followed by [functions] and the rest.
extensions.conf has …
[globals]
HOMENPA = 337 ; change this to your Area Code
NODE = 42315 ; change this to your node number
NODEELINK = 1999 ; this is the private ECHOLINK node number
NODEDMR = 1991 ; this is the private DMR node number
[default]
exten => i,1,Hangup
[radio-secure]
exten => ${NODE},1,rpt,${NODE} ; the public radio and IAX node
exten => ${NODEELINK},1,rpt,${NODEELINK} ; the private DMR node
exten => ${NODEDMR},1,rpt,${NODEDMR} ; the private DMR node
[iaxrpt] ; entered from iaxrpt in iax.conf
exten => ${NODE},1,rpt(${NODE}|X) ; NODE is the Name field in iaxrpt
I hand ran the connect from inside of asterisk … it looks like this …
Connected to Asterisk GIT Version 004b9dd currently running on KF5VH-AS0 (pid = 441)
Verbosity was 0 and is now 9
KF5VH-AS0*CLI> !rpt 31999
– Remote UNIX connection
== Parsing ‘/var/lib/asterisk/rpt_extnodes’: Found
== Parsing ‘/var/lib/asterisk/rpt_extnodes’: Found
– Remote UNIX connection disconnected
== Parsing ‘/var/lib/asterisk/rpt_extnodes’: Found
– Accepting UNAUTHENTICATED call from 127.0.0.1:
> requested format = gsm,
> requested prefs = (gsm|ulaw|adpcm),
> actual format = ulaw,
> host prefs = (ulaw|adpcm|gsm),
> priority = mine
Node Variable dump for node 42315:
RPT_TXKEYED=1
RPT_NUMLINKS=0
RPT_LINKS=0
RPT_NUMALINKS=0
RPT_ALINKS=0
RPT_AUTOPATCHUP=0
RPT_ETXKEYED=0
RPT_RXKEYED=0
– 8 variables
– Call accepted by 127.0.0.1 (format ulaw)
– Format for call is ulaw
Node Variable dump for node 42315:
RPT_ETXKEYED=1
RPT_TXKEYED=1
RPT_NUMLINKS=0
RPT_LINKS=0
RPT_NUMALINKS=0
RPT_ALINKS=0
RPT_AUTOPATCHUP=0
RPT_RXKEYED=0
– 8 variables
– Executing [1999@radio-secure:1] Rpt(“IAX2/127.0.0.1:4569-644”, “1999”) in new stack
== Parsing ‘/etc/asterisk/rpt.conf’: Found
== Parsing ‘/var/lib/asterisk/rpt_extnodes’: Found
[Jun 19 17:55:10] WARNING[656]: app_rpt.c:22574 rpt_exec: Cannot find specified system node 1999
== Spawn extension (radio-secure, 1999, 1) exited non-zero on ‘IAX2/127.0.0.1:4569-644’
– Hungup ‘IAX2/127.0.0.1:4569-644’
– Hungup ‘IAX2/127.0.0.1:4569-1966’
– Hungup ‘DAHDI/pseudo-1969360104’
[Jun 19 17:55:10] WARNING[483]: chan_iax2.c:10127 iax2_do_register: REGISTER-LOG: Sending registration request for ‘42315’
[Jun 19 17:55:11] WARNING[486]: chan_iax2.c:7690 registry_rerequest: REGISTER-LOG: registry rereqquest
– Hungup ‘DAHDI/pseudo-1410713480’
– <DAHDI/pseudo-92089219> Playing ‘rpt/node’ (language ‘en’)
– <DAHDI/pseudo-92089219> Playing ‘digits/1’ (language ‘en’)
– <DAHDI/pseudo-92089219> Playing ‘digits/9’ (language ‘en’)
– <DAHDI/pseudo-92089219> Playing ‘digits/9’ (language ‘en’)
– <DAHDI/pseudo-92089219> Playing ‘digits/9’ (language ‘en’)
– <DAHDI/pseudo-92089219> Playing ‘rpt/connection_failed’ (language ‘en’)
Node Variable dump for node 42315:
– Hungup ‘DAHDI/pseudo-92089219’
So, what have I done wrong that it can’t find 1999.
OMG, just hit me … do I have to have a [1999] stanza for echolink? I’ve never had one. Maybe because I had astnode=42315 in echolink.conf.
…STeve
Correct. You need a node stanza for each node.
I don’t think I’ve ever seen a skeleton for the Echolink Stanza “[1999]” in RPT.CONF. Can you point me at examples? [sort of amazing I ran a system that worked for > 3 years without this key knowledge … if astnode = # server node number you don’t even have to connect echolink to the node … it just works.]
There is no Echolink stanza per se. In echolink.conf you simply point astnode at a working node stanza in rpt.conf. I use a private node for echolink so I can connect and disconnect from echolink by simply connecting the public to the private node when I want echolink. I keep the node I use for echolink very simple.
You could use a variation of the sample DVSwitch stanza for echolink:
Private node
Change the rxchannel to:
rxchannel = dahdi/pseudo
Steve … I think I have it working. Thank you very much for your essential help.
…STeve