Need help please have issues with connecting to 1999
I need help with my node won't connect to 1999 says connection failed my cell is 1-906-364-1858
https://www.facebook.com/N6NWS
|
|
Have you set-up connection string in rpt.conf for the private node ? Did you also set a extension for the connection in extensions .conf ? If you are still at this in the morn I will try again then. Going to bed. paste the lines you used so we can look at them
On 7/17/2020 10:04 PM, Jeremy N6NWS
3138138 wrote:
I need help with my node won't connect to 1999 says connection failed my cell is 1-906-364-1858
|
|
Greetings,
I'm having a similar issue and found this thread via search, since the OP didn't come back figured I'd continue the thread. My issue only occurs if I need to drop 1999 for some reason and then try to reconnect to it. My extensions.conf have a line for 1999 in the globals stanza [globals] NODE1 = 1999; This is a private node [1999] 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 $
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 f$ ; except when an ID needs to be done and there is a signal comin$
telemdefault = 0 ; 0 = telemetry output off. Don't send Allison to DMR !!!!!!!!!!$
telemdynamic = 0 ; 0 = disallow users to change the local telemetry setting with $
linktolink = no ; disables forcing physical half-duplex operation of main repeat$ ; 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 18$
idrecording = |ie ; id recording or morse string see http://ohnosec.org/drupal/nod$ idtalkover = |ie ; Talkover ID (optional) default is none see http://ohnosec.org/$
|
|
You need to have 1999 in your nodes stanza or rpt.conf
toggle quoted messageShow quoted text
Search rpt.conf for "[nodes] Add: 1999 = radio@....0.1:4569/1999,NONE ; assuming you are using 4569 as your IAX port.
On 1/29/2021 2:57 PM, Vince Pimentel
wrote:
Greetings,
|
|
Vince Pimentel
Copy that, and that is also present. Sorry, didn't even think about that. #doh
1999 = radio@....0.1:4569/1999,NONE ; and iax port number if not the default
|
|
Check for:
toggle quoted messageShow quoted text
[radio-secure] exten => ${NODE1},1,rpt,${NODE1} In extensions.conf
On 1/29/2021 3:52 PM, Vince Pimentel
wrote:
Copy that, and that is also present. Sorry, didn't even think about that. #doh
|
|
Vince Pimentel
Yep, looks good. [radio-secure] exten => ${NODE},1,rpt,${NODE} exten => ${NODE1},1,rpt,${NODE1} startup_macro = *31999 /var/log/asterisk/messages.1:[Jan 28 18:51:19] NOTICE[480] app_rpt.c: Normal Repeater Init 1999 /var/log/asterisk/messages.1:[Jan 28 20:01:16] NOTICE[480] app_rpt.c: Normal Repeater Init 1999
/var/log/asterisk/messages.1:[Jan 29 02:30:16] NOTICE[481] app_rpt.c: Normal Repeater Init 1999
Welp, I just tried to connect to it again to see if I could get anything to show in the logs that would easier to find and it worked. Disconnected and reconnected like 5 times with success. No file changes, reboots or anything like that.
Thanks for the replies and help but it's a mystery still. Will see if I can learn anything more if it happens again. Any further thoughts or things to check/confirm are welcome but with it working. We won't be able to confirm that it was a fix.
|
|
Could it be that a node you were connected to or a node connected to you also had a 1999 private node ? If so, it will not allow you to connect as long as one is present in the 'connected network'. Suggest using a odd number like 1325. everyone seems to use 1999
for there first private node. Something to look for next time.
On 1/29/2021 5:02 PM, Vince Pimentel
wrote:
|
|
Valid point. Need to test and come up with a unique private or number.
Sent by smoke signal (AT&T)
From: main@DVSwitch.groups.io <main@DVSwitch.groups.io> on behalf of Mike KB8JNM <groupio@...>
Sent: Friday, January 29, 2021 5:12:25 PM To: main@DVSwitch.groups.io <main@DVSwitch.groups.io> Subject: Re: [DVSwitch] Need help please have issues with connecting to 1999 Could it be that a node you were connected to or a node connected to you also had a 1999 private node ? If so, it will not allow you to connect as long as one is present in the 'connected network'. Suggest using a odd number like 1325. everyone seems to use 1999 for there first private node. Something to look for next time.
On 1/29/2021 5:02 PM, Vince Pimentel wrote:
|
|
Vince Pimentel
OH! I think you gents nailed it! Yes, I was on a substantial sized network and yes there were two other nodes that had 1999 running that I know of. Also DVSwitch bridges I believe. I'm still on that network but those nodes are no longer connected.
I'll give that a go but would put money on it that you're right. Huge thank you!
|
|
Mike,
toggle quoted messageShow quoted text
Lets move the discussion of a scheme for private node numbers to the AllStarLink subgroup.
On 1/29/21 5:12 PM, Mike KB8JNM wrote:
|
|
I did not have a discussion, just a one post answer to the multi post problem. Should I not answer when the answer is not in the right category
as the question ?
On 1/30/2021 9:42 AM, Steve N4IRS
wrote:
Mike,
|
|
No, you are fine. I am starting a discussion and I think we should
have it in the AllStarLink subgroup. Sorry I was not clear enough.
toggle quoted messageShow quoted text
On 1/30/21 9:57 AM, Mike KB8JNM wrote:
|
|
Vince Pimentel
Hey Gents,
Just wanted to follow up and let you know that I was able to rework my system to use my node number with a 1 at the beginning for the private node to make it unique and tested it this weekend. Solved! Thank you for the time, effort and support that you provide.
|
|