I am programming a URI node using the Allstarlink.org beta software. I have bindport=4570 specified in iax.conf also in my router and Allstarling.org server settings, but yet upon entering the CLI command CLI>iax2 show registry it states port 4569. How is this possible?
what is the node number(s) in question ?
My repeater node is 548272. Port 4570 is specified in iax.conf, in my router and in server settings, but yet iax2 show registery states 4569.
Can you post your iax.conf
Mask off the password on the ‘register’ line but do not disturb the line beyond that.
At this moment, I am showing 548272=radio@72.170.230.42:4570/548272,72.170.230.42
And… is this hamvoip system or what version of software are you using ?
I am using Allstarlink.org beta software on a RPI 4B.
CLI>iax2 show registry
162.248.92.131:4569 Y 548272 72.170.230.42:4569 179 Registered
; Inter-Asterisk eXchange driver definition
[general]
; !!! Change this to match your node registration !!!
register=548272:mypasswordn@register.allstarlink.org ; This must be changed to your node number, password
; remove the leading “;”
bindport = 4570 ; bindport and bindaddr may be specified
; NOTE: bindport must be specified BEFORE
; bindaddr or may be specified on a specific
; bindaddr if followed by colon and port
; (e.g. bindaddr=192.168.0.1:4569)
; bindaddr = 192.168.0.1 ; more than once to bind to multiple
; addresses, but the first will be the
; default
;bindaddr = 192.168.42.3:4570
bindaddr = 0.0.0.0
disallow = all ; The permitted codecs for outgoing connections
; Audio Quality Bandwidth
;allow = ulaw ; best 87 kbps
;allow = adpcm ; good 55 kbps
;allow = gsm ; medicore 36 kbps
allow = ulaw
allow = adpcm
allow = g722
allow = g726aal2
allow = gsm
allow = ilbc
jitterbuffer = yes
forcejitterbuffer = yes
dropcount = 2
maxjitterbuffer = 4000
maxjitterinterps = 10
resyncthreshold = 1000
maxexcessbuffer = 80
minexcessbuffer = 10
jittershrinkrate = 1
tos = 0x1E
autokill = yes
delayreject = yes
; iaxthreadcount = 30
; iaxmaxthreadcount = 150
; Incoming radio connections
[radio]
type = user
disallow = all
allow = ulaw
allow = adpcm
allow = g722
allow = g726aal2
allow = gsm
allow = ilbc
codecpriority = host
context = radio-secure
transfer = no
[iaxrpt] ; Connect from iaxrpt Username field (PC AllStar Client)
type = user ; Notice type is user here <---------------
context = iaxrpt ; Context to jump to in extensions.conf
auth = md5
secret = Your_Secret_Pasword_Here
host = dynamic
disallow = all
allow = ulaw
allow = adpcm
allow = gsm
transfer = no
[iaxclient] ; Connect from iax client (Zoiper…)
type = friend ; Notice type here is friend <--------------
context = iax-client ; Context to jump to in extensions.conf
auth = md5
secret = Your_Secret_Password_Here
host = dynamic
disallow = all
allow = ulaw
allow = adpcm
allow = gsm
transfer = no
[allstar-sys]
type = user
context = allstar-sys
auth = rsa
inkeys = allstar
disallow = all
allow = ulaw
[allstar-public]
type = user
context = allstar-public
auth = md5
secret = allstar
disallow = all
allow = ulaw
allow = gsm
; The following should be un-commented to support Allstar Autopatch service
; [allstar-autopatch]
; type = peer
; host = register.allstarlink.org
; username =
; secret =
; auth = md5
; disallow = all
; allow = ulaw
; transfer = no
#includeifexists custom/iax.conf
I tried this on one of my systems and it reports the same. But I am using a port in the 8xxx range.
Using it for 5+ years.
I don’t think I would worry about it.
It is not changing how your system connects or receives connects.
As long as your bindport matches what is on the nodelist broadcast and the same port is forwarded from your router to the nat ip of the server…
Thank you. The only reason I thought this was important is because I cannot connect to any node, inbound nor outbound for reasons unknown.
CLI>548272 *3548270
WARNING[622]:channel.c:2447 ast_indicate_data: ‘IAX2/75.107.93.78:4571-701’
A search for this warning produced nothing. Any ideas?
Plenty of ideas.
Lets see if we can’t narrow them down so I don’t have to write a book LOL
I did connect to yo earlier, and again at this message so I really do not think there is anything wrong.
node 548272
If this is what you are typing, it’s likely the issue.
CLI commands start with rpt for radio nodes.
It is a asterisk command line interface which our software is a part of.
And all node commands will start with rpt
You can type
help rpt
And follow the help summary.
Then help rpt cmd will bring help with that
Yes, I always use the command CLI> rpt fun 548272 *3XXXXXX command. I just left that out unknowing that I did so. Research has suggested that is a NAT’ing issue, but in the myriad of times I have checked my port settings, I don’t believe this is the cause. Sometimes this warning appears and other times it does not. Thank you to connecting to my repeater node; this is very helpful.
The reason I believe it was not connecting is due to the fact that I have another ASL node 548270 (Node Ventures) which the repeater would not connect to.
I have been through all the RC-210 controller hardware settings numerous times as well at the RCP programming for the controller and all is correct. I have even verified these settings with a call to Arcom Controllers. As a side note, I want to make users aware that when programming the controller for ASL, regardless of which port they are using to use macro 121, not 118 combined with 119. Only this macro will communicate with the node.
In any event, I have downloaded the diagnostic file and submitted it to the ASL help team for their review to perhaps discover if I am ellipse or in error of any of the ASL software parameters.
That is a different issue in cause perhaps.
Are each node on a separate server but behind the same NAT router ?
This would require additional config.
The Node Ventures node 548270 uses a different server and router.
So do I have this correct as your issue…
You only have issues connecting 548270 and 548272 ?
Actually, I have two Node Ventures nodes, 548270 and 548273 both on different servers and routers and the repeater node 548272 will not connect.
Update: I just tried connecting Node Ventures 548270 to the repeater node 548272 and the connection was successful. However, CLI>rpt fun 548272 *3548270, does not work.
So, the issue is 548272 can not connect to 548270 ?
I just tried 548270 and I can not connect to it either.
Let’s see 548270 iax.conf -mask password(s)
Correct. Outbound call from the repeater node 548272 will not connect to either Venture Nodes 548270 nor 548273 which are on different servers and routers.
Let’s see 548270 iax.conf -mask password(s)
Here is the iax.conf file for Node Ventures 548270:
; Inter-Asterisk eXchange driver definition
;
; For manual configuration edit the registration lines
; below and also passwords for various connections.
; Updated 1/2019 to include additional features
; Before attempting to add features ensure they
; are not already installed
; THIS IS AN IMPORTANT FILE! EDIT CAREFULLY!
; MAKE A BACKUP BEFORE EDITING
[general]
bindport=4569
bindaddr=0.0.0.0
disallow=all
allow=ulaw
allow=g726aal2
allow=ilbc
allow=gsm
jitterbuffer=yes
forcejitterbuffer=yes
dropcount=2
maxjitterbuffer=4000
maxjitterinterps=10
resyncthreshold=1000
maxexcessbuffer=80
minexcessbuffer=10
jittershrinkrate=1
tos=0x1E
autokill=yes
delayreject=yes
;iaxthreadcount=30
;iaxmaxthreadcount=150
; ASL and HamVoIP Registrataion lines
register => 548270:mypassword@register.allstarlink.org
[radio-proxy]
type=user
;deny=0.0.0.0/0.0.0.0
;permit=0.0.0.0/255.255.255.255
context=radio-secure-proxy
disallow=all
allow=g726aal2
allow=ilbc
allow=ulaw
allow=gsm
transfer=no
[radio-proxy-out]
type=peer
host=
username=548270
secret=boardman
auth=md5
disallow=all
allow=g726aal2
allow=ilbc
allow=ulaw
allow=gsm
transfer=no
[dvswitch]
; Settings for DVSwitch
requirecalltoken=no
type=friend
context=cn-dvswitch-iax
auth=md5
secret=boardman
host=dynamic
disallow = all
allow = slin
allow = ulaw
allow = adpcm
transfer = no
codecpriority = Caller
[zoiper]
; Settings for Zoiper
requirecalltoken=no
type=friend
context=cn-zoiper-iax
host=dynamic
auth=md5
secret=boardman
disallow=all
allow=ulaw
allow=g726aal2
allow=gsm
transfer=no
codecpriority=host
transfer=no
[iaxrpt]
requirecalltoken=no
user=iaxrpt
type=friend
context=radio-iaxrpt
auth=md5
secret=boardman
host=dynamic
disallow=all
allow=ulaw
allow=gsm
transfer=no
; Incoming radios needed connections
[radio]
type=user
disallow=all
allow=g726aal2
allow=ilbc
allow=ulaw
allow=gsm
codecpriority=host
; To use the ban/allow (blacklist/whitelist) feature
; comment with a ‘;’ the context = radio-secure line and
; remove the ‘;’ from either the context = whitelist or
; context = blacklist line. ONLY ONE of the three lines
; can be active (uncommented).
;
; The best way to allow or ban nodes from the database is to
; use the Supermon application or the node-ban-allow.sh script.
context = radio-secure
;context = whitelist
;context = blacklist
transfer=no
; For Allstar Phone access
[allstar-sys]
type=user
context=allstar-sys
auth=rsa
inkeys=allstar
disallow=all
allow=ulaw
; For Allstar web page access
[allstar-public]
requirecalltoken=no
type=user
context=allstar-public
auth=md5
secret=allstar
disallow=all
allow=ulaw
allow=gsm
#includeifexists custom/iax.conf
The software used by Gerry Filby at Node Ventures looks like it is from Allstarlink.org running on a RPI 3B.
Well, after all that rhetoric it turns out that the problem is with my other two nodes from Node Ventures, 548270 and 548273. I tried connecting to the Los Angles hum 2560 from the repeater 548272 and the connection worked fine. Mike, thank you for all your help.
I don’t understand how you can say that but OK if you are fine with it.
There does not appear to be any issue with 548272 as I said before.
I still can not connect to 548270, so you have an issue unless you have turned off connections.
I will let Gerry Filby at Node Ventures try to figure out what’s wrong the nodes 548270 and 548273. I also noticed the audio is dead on 548273. I will send these nodes back to him for repair. Thank you again.