The solution to this is to set up the outbound NAT like this: And then do Diagnostics -> States -> Filter on the node’s IP address -> Kill. All services including ssh will be temporarily dropped and automatically restarted. Thank you Mike KB6GZL for your help with this -- Tim :wq On Aug 22, 2014, at 8:01 AM, Tim Sawyer <tim.sawyer@mac.com> wrote:
Mike,
Thanks I’ll try that as soon as the pfsense router gets reinstalled. Just for grins could you do “iax2 show registry”? Is the perceived port correct?
*CLI> iax2 show registry Host dnsmgr Username Perceived Refresh State 67.215.233.178:4569 N 2504 108.13.3.89:4569 60 Registered -- Tim WD6AWP
On Aug 22, 2014, at 7:56 AM, Michael Wolthuis <wolthuis@gmail.com> wrote:
Tim, I run PFSense with many of my Allstar nodes. I have to set STATIC outbound NAT for the specific IP addresses that are Asterisk. This will cause them to not pick random ports outbound.
I am not sure what iax2 show registry does, but I could not get it to work until I put in a static NAT outbound.
Here is a copy of my outbound NAT statement for one of my nodes:
I believe the key is the last YES, which is the STATIC PORT heading.
Hope that helps, Mike kb8zgl
From: Tim Sawyer <tim.sawyer@mac.com> Date: Friday, August 22, 2014 at 10:52 AM To: "app_rpt-users@ohnosec.org" <app_rpt-users@ohnosec.org> Subject: [App_rpt-users] pfsense router?
Is anyone using a pfsense router in your Asterisk network? While app_rpt seems to work fine it shows a weird port, not 4569, with “iax2 show registry”. I assume pfsense is doing something weird with NAT that I don’t understand. Can anyone shed some light on this subject?
-- Tim WD6AWP
