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?