<br><br><div class="gmail_quote">On Tue, Feb 23, 2010 at 4:27 PM, Brian May <span dir="ltr"><<a href="mailto:brian@microcomaustralia.com.au">brian@microcomaustralia.com.au</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hello,<br>
<br>
Why is it recommended to use separate profiles for internal and external SIP?<br>
<br>
This page:<br>
<<a href="http://wiki.freeswitch.org/wiki/External_profile" target="_blank">http://wiki.freeswitch.org/wiki/External_profile</a>><br>
suggests it is because of NAT.<br>
<br>
However this page recommends using separate profiles even if NAT is<br>
not an issue:<br>
<<a href="http://wiki.freeswitch.org/wiki/Auto_NAT" target="_blank">http://wiki.freeswitch.org/wiki/Auto_NAT</a>>: "NOTE: It is still<br>
recommended that you use a second profile for your SIP providers. The<br>
default conf/sip_profiles/external.xml is set up specifically for use<br>
with providers."<br>
<br>
However I am still left uncertain what this means.<br>
<br>
Not trying to criticize here, just trying to learn.<br></blockquote><div><br>No problem. Separating them has a few advantages: security, scalability, and readability. The first one on the list is definitely the most important. If you stuff everything in the internal profile it's easier to open yourself up to toll fraud.<br>
-MC<br><br></div></div>