On 12/09/2012 03:07 AM, Chris Buechler wrote:
ll,
>
>I've been attempting to our old 1.2.2 firewall to new hardware and version
>2.0 Release. Everything works with one big exception of the remote phones on
>our Digium Switchvox server. I've attempted this move 3 times, and each time
>I pull the new firewall back to our office after the failure and comb
>through the firewall rules for the Switchvox segment with a fine tooth comb.
>They are identical rule sets on both 1.2.2 and 2.0.
>
The difference between 1.x and 2.x, assuming you're using automatic
outbound NAT, is the former won't rewrite the source port on UDP 5060
and the latter will. 2.x's behavior works significantly more of the
time than 1.x's, but there isn't one setting that works for
everything. Going back to static port on 5060 likely will fix.
http://doc.pfsense.org/index.php/VoIP_Configuration
Chris,
Thanks for the reply, but having read the document you linked and your
email, I'm still not positive that this relates to my situation. Forgive
me for asking for a little more clarification and providing the same.
The remote phones in question are not using NAT, but are publicly
addressed. Local phones on our LAN continue to work just fine. The
firewall is at the local end and sits between the cloud and the
switchvox server. When you say, "going back to a static port on 5060"
what do you mean? Currently, there is an alias set up for VOIP UDP ports
and for VOIP TCP port. All traffic inbound is allowed to those ports if
the destination is the Switchvox server. 5060 is included in the UDP
ports alias.
Any further ideas are greatly appreciated!
Thanks,
--
--
Steven G. Spencer, Network Administrator
KSC Corporate - The Kelly Supply Family of Companies
Office 308-382-8764 Ext. 231
Mobile 308-380-7957
_______________________________________________
List mailing list
[email protected]
http://lists.pfsense.org/mailman/listinfo/list
