<HTML>
<HEAD>
<TITLE>Re: [Freeswitch-users] FreeSwitch setup as a "Dumb" SBC</TITLE>
</HEAD>
<BODY>
<FONT SIZE="4"><FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'>Yes you can do that, but there is nothing that says you cant have FreeSWITCH just do those lookups and ENUM (FS Supports ENUM out of the box) and do the exact same thing so it would work like Provider -> ingress SBC -> egress SBC/Registration Server -> customer<BR>
<BR>
Loosing a whole hop in the process<BR>
<BR>
<HR ALIGN=CENTER SIZE="3" WIDTH="95%"><B>From: </B>Adam Long <ajlong@worldlink.net><BR>
<B>Reply-To: </B><freeswitch-users@lists.freeswitch.org><BR>
<B>Date: </B>Mon, 2 Feb 2009 22:05:17 -0500<BR>
<B>To: </B><freeswitch-users@lists.freeswitch.org><BR>
<B>Subject: </B>[Freeswitch-users] FreeSwitch setup as a "Dumb" SBC<BR>
<BR>
Hi Guys,<BR>
<BR>
I’ve been working at setting up a couple of FreeSwitch nodes as a topology hiding SBCs that handles both ingress traffic from my<BR>
providers/peers and pass traffic up to an openser router that then routes call across the cluster of SBCs through which they reach the destination.<BR>
<BR>
I have OpenSIPS/SER setup doing DB route lookups and ENUM with LCR/Serial forking etc.<BR>
<BR>
My question is what would be the best way to send a call out to a destination choosen by the OpenSER router?<BR>
<BR>
For example:<BR>
SIP Provider -- > SBC --- > OpenSER ---- ( route lookup returns 123.123.123.4 as dest ) -- > SBC --- > 123.123.123.4<BR>
<BR>
I was thinking something along the lines of adding a “X-Route-To: +1NXXNXXXXXX@123.123.123.4” with openser<BR>
and then something like this in the SBC…<BR>
<BR>
<context name="from-sipcore"><BR>
<extension name="outboundroute"><BR>
<action application="bridge" data="sofia/external/${sip_h_X-Route-To}" /><BR>
</extension><BR>
</context><BR>
<BR>
Is this a wise approach, is there anything I could do to do this better?<BR>
I’d like to keep the logic in the SBCs as simple as possible.<BR>
<BR>
I am pretty familiar with SIP but my knowledge fades when it gets into the nitty gritty of routing… ie the Contact: and Via: headers<BR>
and all that good stuff.<BR>
<BR>
I should also state I have two profiles defined one for the internal/private “core” network and one for the outside “external” network.<BR>
<BR>
Any thoughts on this at all would be greatly appreciated.<BR>
Am I missing something in the SIP spec that would allow for this is a standardized way?<BR>
<BR>
Regards,<BR>
-Adam<BR>
<BR>
<HR ALIGN=CENTER SIZE="3" WIDTH="95%"></SPAN></FONT><FONT FACE="Consolas, Courier New, Courier"><SPAN STYLE='font-size:10pt'>_______________________________________________<BR>
Freeswitch-users mailing list<BR>
Freeswitch-users@lists.freeswitch.org<BR>
<a href="http://lists.freeswitch.org/mailman/listinfo/freeswitch-users">http://lists.freeswitch.org/mailman/listinfo/freeswitch-users</a><BR>
UNSUBSCRIBE:<a href="http://lists.freeswitch.org/mailman/options/freeswitch-users">http://lists.freeswitch.org/mailman/options/freeswitch-users</a><BR>
<a href="http://www.freeswitch.org">http://www.freeswitch.org</a><BR>
</SPAN></FONT></FONT>
</BODY>
</HTML>