<div><br>You can always connect to your external SIP provider by configuring it as gateway in sofia profile and register on to that provider. </div><div> </div><div><a href="http://wiki.freeswitch.org/wiki/Clarification:gateways">http://wiki.freeswitch.org/wiki/Clarification:gateways</a></div>
<div> </div><div>also look at this parameter </div><div> </div><p><!--send an options ping every x seconds, failure will unregister and/or mark it down--><br><!--<param name="ping" value="25"/>--></p>
<div>So that hole punching thing is taken care of .</div><div> </div><div><br>-- <br>Godson Gera<br><a href="http://godson.in/ivr">IVR India</a></div><div> </div><div> </div><div class="gmail_quote">On Sat, Feb 18, 2012 at 12:14 AM, Josh <span dir="ltr"><<a href="mailto:mojo1736@privatedemail.net">mojo1736@privatedemail.net</a>></span> wrote:<br>
</div><blockquote style="margin:0px 0px 0px 0.8ex;padding-left:1ex;border-left-color:rgb(204,204,204);border-left-width:1px;border-left-style:solid" class="gmail_quote">A few questions to all knowledgeable heads out there: Everything I read<br>
so far about how to set up and configure my FS external sip profile<br>
tells me that I need to have IP address/interface and port (default<br>
being 5080) to bind to in order to receive inbound calls via the<br>
external sip profile.<br>
<br>
Is that really the case? Is this the only way I could receive such calls?<br>
<br>
The reason I am asking is this: my Internet-facing interface cannot<br>
receive calls (or any connections from outside) unless it initiates<br>
these connection first, simply because my ISP is blocking "server"<br>
connections (i.e. connections initiated from outside, destined to my IP<br>
address/interface). If my Internet-facing machine initiates the<br>
connection first (therefore punching a "hole" through the ISPs<br>
firewall), then that's allowed - no restrictions of any sort are applied<br>
by my ISP.<br>
<br>
So, I guess what I am asking is this: Is it possible to configure my<br>
external sip profile in FS in such a way so that it does not listen to a<br>
particular interface:port in order to receive external sip calls, but to<br>
use the control channel/connection established to my external SIP<br>
provider (on sip provider's IP address and port 5060) in order to find<br>
out which ports to use and initiate rtp connections on my machine,<br>
instead of waiting for such connections on a specific port? As I already<br>
pointed out above - such connections initiated from outside will be<br>
blocked by my ISP, but if these are started from my machine they will be<br>
allowed, no problem.<br>
<br>
Hope I am making myself clear with this. Many thanks!<br>
<br>
_________________________________________________________________________<br>
Professional FreeSWITCH Consulting Services:<br>
<a href="mailto:consulting@freeswitch.org">consulting@freeswitch.org</a><br>
<a href="http://www.freeswitchsolutions.com" target="_blank">http://www.freeswitchsolutions.com</a><br>
<br>
FreeSWITCH-powered IP PBX: The CudaTel Communication Server<br>
<a href="http://www.cudatel.com" target="_blank">http://www.cudatel.com</a><br>
<br>
Official FreeSWITCH Sites<br>
<a href="http://www.freeswitch.org" target="_blank">http://www.freeswitch.org</a><br>
<a href="http://wiki.freeswitch.org" target="_blank">http://wiki.freeswitch.org</a><br>
<a href="http://www.cluecon.com" target="_blank">http://www.cluecon.com</a><br>
<br>
FreeSWITCH-users mailing list<br>
<a href="mailto:FreeSWITCH-users@lists.freeswitch.org">FreeSWITCH-users@lists.freeswitch.org</a><br>
<a href="http://lists.freeswitch.org/mailman/listinfo/freeswitch-users" target="_blank">http://lists.freeswitch.org/mailman/listinfo/freeswitch-users</a><br>
UNSUBSCRIBE:<a href="http://lists.freeswitch.org/mailman/options/freeswitch-users" target="_blank">http://lists.freeswitch.org/mailman/options/freeswitch-users</a><br>
<a href="http://www.freeswitch.org" target="_blank">http://www.freeswitch.org</a><br>
</blockquote><br><br clear="all"><br>