<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	
	>
<channel>
	<title>
	Comments on: Deploying Incredible PBX 2027 with Microsoft Windows 11	</title>
	<atom:link href="https://nerdvittles.com/deploying-incredible-pbx-2027-with-microsoft-windows-11/feed/" rel="self" type="application/rss+xml" />
	<link>https://nerdvittles.com/deploying-incredible-pbx-2027-with-microsoft-windows-11/</link>
	<description>Ward Mundy&#039;s Technobabblelog</description>
	<lastBuildDate>Wed, 02 Apr 2025 20:15:05 +0000</lastBuildDate>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	
	<item>
		<title>
		By: Nerd Uno		</title>
		<link>https://nerdvittles.com/deploying-incredible-pbx-2027-with-microsoft-windows-11/comment-page-1/#comment-182051</link>

		<dc:creator><![CDATA[Nerd Uno]]></dc:creator>
		<pubDate>Tue, 15 Aug 2023 13:47:27 +0000</pubDate>
		<guid isPermaLink="false">https://nerdvittles.com/?p=36352#comment-182051</guid>

					<description><![CDATA[If you have issues with IPtables starting in the latest release of WSL, here is the fix after logging in as root::

update-alternatives --set iptables /usr/sbin/iptables-legacy
update-alternatives --set ip6tables /usr/sbin/ip6tables-legacy
iptables-restart]]></description>
			<content:encoded><![CDATA[<p>If you have issues with IPtables starting in the latest release of WSL, here is the fix after logging in as root::</p>
<p>update-alternatives &#8211;set iptables /usr/sbin/iptables-legacy<br />
update-alternatives &#8211;set ip6tables /usr/sbin/ip6tables-legacy<br />
iptables-restart</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: ward		</title>
		<link>https://nerdvittles.com/deploying-incredible-pbx-2027-with-microsoft-windows-11/comment-page-1/#comment-181027</link>

		<dc:creator><![CDATA[ward]]></dc:creator>
		<pubDate>Tue, 07 Mar 2023 18:01:22 +0000</pubDate>
		<guid isPermaLink="false">https://nerdvittles.com/?p=36352#comment-181027</guid>

					<description><![CDATA[Skyetel has been moving to new banks of IP subnets for redundancy, etc. that are different than the default SIP trunks in IPBX2027. They also suggest using PJSIP two create just two trunks this way - in &amp; out.

Here are the added IPBX2027 steps I found to get the old disabled &amp; the new two PJSIP trunks laid down/operational:

1) Disable old SIP Skeytel trunks

2) Add the following to the &quot;/usr/local/sbin/iptables-custom&quot; ...

/usr/sbin/iptables -A INPUT -s 35.85.225.96 -j ACCEPT
/usr/sbin/iptables -A INPUT -s 3.99.65.224 -j ACCEPT
/usr/sbin/iptables -A INPUT -s 3.101.177.224 -j ACCEPT
/usr/sbin/iptables -A INPUT -s 44.199.94.192 -j ACCEPT
/usr/sbin/iptables -A INPUT -s 35.215.45.65 -j ACCEPT
/usr/sbin/iptables -A INPUT -s 35.209.126.210 -j ACCEPT
/usr/sbin/iptables -A INPUT -s 35.212.222.157 -j ACCEPT

3) &quot;iptables-restart&quot;

4) If you have a hardware firewall with say whitelisting, be sure to add these subnets &amp; IP&#039;s there as well of course.

5) Follow Skyetel&#039;s FreePBX PJSIP trunk directions:

INBOUND: https://support.skyetel.com/hc/en-us/articles/4410765264791-FreePBX-13-Create-Inbound-Trunk

OUTBOUND North America: https://support.skyetel.com/hc/en-us/articles/4410672050967-FreePBX-13-Create-Outbound-Trunk-for-North-America

6) Create or change your Skyetel &quot;IP Authentication -&gt; IP Group&quot; entry to use 5061 rather than 5060 to connect

That&#039;s it, and only two trunks using latest Skyetel infrastructure.]]></description>
			<content:encoded><![CDATA[<p>Skyetel has been moving to new banks of IP subnets for redundancy, etc. that are different than the default SIP trunks in IPBX2027. They also suggest using PJSIP two create just two trunks this way &#8211; in &#038; out.</p>
<p>Here are the added IPBX2027 steps I found to get the old disabled &#038; the new two PJSIP trunks laid down/operational:</p>
<p>1) Disable old SIP Skeytel trunks</p>
<p>2) Add the following to the "/usr/local/sbin/iptables-custom" &#8230;</p>
<p>/usr/sbin/iptables -A INPUT -s 35.85.225.96 -j ACCEPT<br />
/usr/sbin/iptables -A INPUT -s 3.99.65.224 -j ACCEPT<br />
/usr/sbin/iptables -A INPUT -s 3.101.177.224 -j ACCEPT<br />
/usr/sbin/iptables -A INPUT -s 44.199.94.192 -j ACCEPT<br />
/usr/sbin/iptables -A INPUT -s 35.215.45.65 -j ACCEPT<br />
/usr/sbin/iptables -A INPUT -s 35.209.126.210 -j ACCEPT<br />
/usr/sbin/iptables -A INPUT -s 35.212.222.157 -j ACCEPT</p>
<p>3) "iptables-restart"</p>
<p>4) If you have a hardware firewall with say whitelisting, be sure to add these subnets &#038; IP&#8217;s there as well of course.</p>
<p>5) Follow Skyetel&#8217;s FreePBX PJSIP trunk directions:</p>
<p>INBOUND: <a href="https://support.skyetel.com/hc/en-us/articles/4410765264791-FreePBX-13-Create-Inbound-Trunk" rel="nofollow ugc">https://support.skyetel.com/hc/en-us/articles/4410765264791-FreePBX-13-Create-Inbound-Trunk</a></p>
<p>OUTBOUND North America: <a href="https://support.skyetel.com/hc/en-us/articles/4410672050967-FreePBX-13-Create-Outbound-Trunk-for-North-America" rel="nofollow ugc">https://support.skyetel.com/hc/en-us/articles/4410672050967-FreePBX-13-Create-Outbound-Trunk-for-North-America</a></p>
<p>6) Create or change your Skyetel "IP Authentication -> IP Group" entry to use 5061 rather than 5060 to connect</p>
<p>That&#8217;s it, and only two trunks using latest Skyetel infrastructure.</p>
]]></content:encoded>
		
			</item>
	</channel>
</rss>
