We will be taking down the original AllStarLink server (allstarlink.org) in the near future. More on that later. For now, the following node numbers need to update their IAX registration.
2300
2323
2585
27051
27260
27413
27422
28564
29324
40222
40332
41137
41228
41263
41676
42845
43231
43456
43459
45477
45698
45831
46031
46079
47367
48056
48194
48398
48889
49247
49407
50076
50215
50409
50640
50752
50956
51058
51086
51149
51258
51407
51445
51551
51585
51589
51592
51646
51659
51679
51754
404120
504440
513091
If your node number is listed above, please change your registration configuration to:
register=nnnn:ppppppp@register.allstarlink.org ;where nnnn = node, ppppp=passwd
Failure to make the change will render your node unable to connect to other AllStar nodes when we decommission the server. Let us know if you need help or further information. The announcement regarding the decommissioning of old allstarlink.org server will be posted later.
In addition to above, there is another change that these nodes and possible others may need. All nodes should have a conf file named dnsmgr.conf in the /etc/asterisk directory. It should look like this:
[general]
enable=yes ; enable creation of managed DNS lookups
; default is 'no'
refreshinterval=300 ; refresh managed DNS lookups every <n> seconds
; default is 300 (5 minutes)
Once you make that change, restart your node and run the command shown below. You should see the Y under dnsmgr.
*CLI> iax2 show registry
Host dnsmgr Username Perceived Refresh State
162.248.93.134:4569 Y 2530 xx.xx.xx.xx:4569 60 Registered
Also see my reply to the original topic… I forgot to mention something.
It turns out that the old server does not expire registrations from phone portal use. Apparently the list of node numbers above are from just that, phone portal usage, not direct registrations with allstarlink.org. Please ignore the list of node numbers from the previous post. I’m sorry for the confusion.
Even so, it is important that all users have the dns manager configuration file installed. This allows the registration load to be distributed across the (currently) 5 registration servers.