[App_rpt-users] Nodes on same server linked, but not repeating audio?

Wed Nov 1 04:36:47 UTC 2017

Jeremy, et al:

You just got my thinking, so I just looked a known working config I
saved from April of this year.

I had three nodes on the server, all listening to the same port number.
All could connect to each other, as well as in/outbound connections
worked fine.

On the ASL portal, each server, under 'Network Config' is where the
incoming connection port is defined. The port was not defined for
individual nodes.

In a traditional Asterisk PBX system, this is the same. You will have
two  remote PBXs with several nodes(phones) at each end, and all can be
talking to each over over the same IAX2 trunk using port 4569.

Remember, IAX is Inter-Asterisk eXchange trunking protocol, which can
be used for one or many conversations, going over/through/whatever, the
 same inbound port.

Now, if you are going to have separate servers at the house/wherever,
then yes, each server will need to be on its own port, different from
the next.

I looked at someone else's rpt.conf, who shared it with me early part
of last year, to do a side-by-side comparison for something I was
fooling with.

At the bottom of his rpt.conf, he has three nodes on the same box, all
with the same port number.

My rpt.conf:
28569 = radio at 127.0.0.1:4569/28569,NONE	; port number must be
specified in the event the standard port number is NOT used locally or
for remote stations. 
29314 = radio at 127.0.0.1:4569/29314,NONE	; The port number for
the local machine that is not standard should be the port number in the
iax.conf 
1968 = radio at w8jvf.net:4570/1968,NONE
41575 = radio at w8jvf.net/41575,NONE
45222 = radio at 127.0.0.1:4569/45222,NONE

his rpt.conf
1954 = radio at 127.0.0.1:4569/1954,NONE,y  ;maxtrac at home
1953 = radio at 127.0.0.1:4569/1953,NONE,y  ;DR135
40804 = radio at 127.0.0.1:4569/40804,NONE	 ;hub

My extensions.conf:
[radio-secure]
exten => 28569,1,rpt,28569
exten => 29314,1,rpt,29314
exten => 45222,1,rpt,45222

[radio-secure-proxy]
exten => 28569,1,rpt,28569|X
exten => 29314,1,rpt,29314|X
exten => 45222,1,rpt,45222|X
exten => _0X.,1,Goto(allstar-sys|${EXTEN:1}|1)

~Benjamin, KB9LFZ

On Tue, 2017-10-31 at 23:12 -0500, Benjamin Naber wrote:
> Bryan, et al:
> 
> I've also been having some connection issues, those of which never
> seemed to occur until I moved from Columbus, GA to here. Coincidence,
> I'm sure.
> 
> However, sometimes I have been able to connect to nodes, and the next
> day, I will try to connect to the same nodes whose uptimes has been
> clicked up another 12 or 24 hours, and I cannot connect.
> 
> Digging further, I've went into the logger.conf and changed:
> messages => notice,warning,error,debug
> 
> saved, and restarted asterisk.
> 
> ....
> Before I moved, or just possibly noticed a couple of times, when my
> node was up for 60+ days, the registration requests look something
> akin
> to this:
> "something, something, who sees us as (IP:14569) with no messages
> waiting."
> 
> Later, went through my montage of HDDs dying from old age, installed
> DIAL 8.5, and now only says the line above, as soon as asterisk is
> started, and that is it. The the usual registration requests, and re-
> requests every 60-ish seconds.
> 
> Saturday night I sent an email out the group about the
> updatenodelist.service, to which at the time when systemctl reported
> it
> as failed, I could not even connect to the hub node on the same ASL
> box, until the updatenodelist was restarted. That should have nothing
> to do with it, but it has not been crossed-off yet.
> 
> .......
> to further add to things, until a few hours ago, I had ASL web portal
> set for the server to use port 14569 instead of 4569. I've been using
> 14569 for the last two years. Inbound/outbound connections were never
> an issue.
> 
> With Asterisk reporting that ASL "registration core" sees me as
> IP:port, yesterday and today it was advising it was seeing me at port
> 4569 and NOT what I've been using. I was not able to receive inbound
> connections.
> 
> So, after all this mess, I went to ASL portal, changed the port for
> the
> server back to 4569, updated NAT on the router, and all seems to be
> well; 20 minutes after I made those changes, four Allstarlink Tech
> Net
> new-comers connected their nodes connected to 45221 on my server.
> 
> Either I'm sleep messing with stuff or something, but these
> connection
> issues have me scratching dandruff, because as I said, until a couple
> weeks ago, everything was peachy. The county I live in is a dry
> county,
> the closest package store is 20 miles away, so I have not drunk-
> configured things for magical-ness in a month, haha.
> 
> ~Benjamin, KB9LFZ
> 
> 
> 
> On Tue, 2017-10-31 at 14:50 -0400, Bryan Fields wrote:
> > I have 3 nodes on the same server, and have seen this behavior
> > before, and
> > it's happening now again.
> > 
> > My node 40821, 41618, 420 are linked and report as linked, but a
> > user
> > on one
> > doesn't bring the other up and vice versa.  A restart will clear
> > it,
> > but is
> > there any troubleshooting I can do to debug this problem?
> > 
> > Thanks,
> 
> _______________________________________________
> App_rpt-users mailing list
> App_rpt-users at lists.allstarlink.org
> http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users
> 
> To unsubscribe from this list please visit http://lists.allstarlink.o
> rg/cgi-bin/mailman/listinfo/app_rpt-users and scroll down to the
> bottom of the page. Enter your email address and press the
> "Unsubscribe or edit options button"
> You do not need a password to unsubscribe, you can do it via email
> confirmation. If you have trouble unsubscribing, please send a
> message to the list detailing the problem. 