Make sure you didn't break your [allstar-public] context in extensions.conf and iax.conf.
well, I didnl’t change a thing in either of those files until I added my user to test if it would accept a direct connect. which it did. like I mentioned, this is a fresh install. hasn’t been up but a couple of days
can you shed light on how the file sections should be setup?
IAXRPT in extensions.conf
<<< choose one of the following formats >>>>>>>
exten = 1234,1,Rpt,1234|X ; Change 1234 to your node number < this is for "pre" ASL3
exten = 1234,1,Rpt(1234|X) ; Change 1234 to your node number < this is for ASL3
In IAX.conf
[iaxrpt] ; Connect from iaxrpt Username field (PC AllStar Client)
type = user ; Notice type is user here <---------------
username= your username
context = iaxrpt ; Context to jump to in extensions.conf
auth = md5
secret = XXXxxxxx
host = dynamic
disallow = all
allow = ulaw
allow = adpcm
allow = gsm
transfer = no
requirecalltoken=no
No, [iaxrpt] is the wrong context for WT. See these links:
ok. i did a file compare, and with the exception of the node numbers and secret password, I have an exact match to those. still not allowing connects. I do have one question however, two of my three nodes work and they have different secret passwords in the iax.conf for the iaxclient, however one of those nodes has the exact same password as the node that does not work. My question is where/when are these secret passwords generated and is it possible that my non working node has the wrong password?
Your_Secret_Password_Here is string-replaced at install with a randomly generated value. If it's duplicated, one file was copied to another system. Again, however, those stanzas are irrelevant to WT mode. Only the [allstar-public] stanzas matter and that password has to be 'allstar' because the real "password" is checked in the extension configuration.
well, thanks for that information. I learned something today, so not a waste. However, it still isn’t working lol. so Maybe I just need to start from scratch and reflash the card, setup once again.
654581 is showing unregistered as I just tried it. (Maybe you’ve already taken it offline?)
We have updated the format to match the Asterisk standard…
Rpt(1234|X) should now be Rpt(1234,X). (Note the , in place of | )
good to know, and where is this exactly? I did not see it in extensions.conf nor iax.conf
however I did find this: same => n,Rpt(${NODENUM},X)
yes, I had already taken it offline.
1 Like
so, new flash on sd card. node setup, absolutely nothing added to the node. bare bones. still not connecting.
Possibly stupid question:
Are you trying to connect to your own node via WT from inside the same network where the node lives? If so, this may be a hairpin/NAT problem, nothing to do with ASL3. You said at the top that you are using 44net, so figure this is probably a non-issue. Do you see anything at all on the console when you try making a connection?
sudo asterisk -rvvvv
thank you for your question. No, I am not trying to connect from the same network. I was aware of the hairpin issue so I did not try from the same network. I tried from several different networks. when I try to make the connection the console shows absolutely nothing. I only get an immediate call failed notification on the phone. When i try to connect to my other nodes, it definitely shows incoming requests. this one does not. Now, this one is an absolutely fresh install as of right now. straight from the mfg so to speak. no mods.
OK, so if your server never sees it but normal node connections work, and web transceiver support is enabled for that node on the Allstarlink.org portal, that’s possibly a client-side issue.
Just for fun, try connecting to the DVSwitch demo account (100) which will push an updated node list to your client, then try again once your node is online and registered again. I see that 654581 is not currently online. I think there is possibly a macro that will also retrieve the current node list. My primary mobile OS is not Android, and I haven’t used DVSM in a while.
In DVSM, tap the More... bar, then Allstarlink, then Update Node List to refresh node list.
David, WD5M
connecting from my phone? i tried connecting to 100 and got node not found.
thank you, but this did not help either.
I have solved my problem. thanks to all who responded to my request.