on FS1 machine define FS2 as gateway and bridge the call to it...<div><br></div><div><br></div><div><br></div><div><meta http-equiv="content-type" content="text/html; charset=utf-8"><div><extension name="To_FS2"></div>
<div> <condition field="destination_number" expression="(.*)"></div><div> <action application="bridge" data="sofia/gateway/FS2/$1"/></div><div> </condition></div>
<div></extension></div></div><div><br></div><div><br></div><div><br></div><div>or without creating any gateways just bridge to FS2 IP address...</div><div><br></div><div><div><extension name="To_FS2"></div>
<div> <condition field="destination_number" expression="(.*)"></div><div> <action application="bridge" data="sofia/profilename/$1@FS2_IP"/></div><div> </condition></div>
<div></extension></div></div><div><br></div><div><br></div><div><br></div><div><br><br><div class="gmail_quote">On Thu, May 26, 2011 at 12:06 PM, William Alianto <span dir="ltr"><<a href="mailto:william@xofap.com">william@xofap.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">I'm trying to do an outbound scenario as following :<br>
<br>
Client --> FS1 --> FS2 --> SBC<br>
<br>
It maybe more simple if I add the SBC as gateway to FS1, but it only<br>
accept IP from FS2 due to IP restriction from provider. Is there any<br>
possible solution for this scenario?<br>
<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></div><br></div>