Sorry, this was confusing, I should have clarified. The way I use freeswitch is via the event socket, so I don't have any UAs, just applications that make calls via ESL.<br><br><div class="gmail_quote">On Fri, Sep 9, 2011 at 7:23 AM, vip killa <span dir="ltr"><<a href="mailto:vipkilla@gmail.com">vipkilla@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div class="im">- I removed the dispatcher module because I didn't need to support registration<div><br></div></div>
<div>Do the UA's register to opensips then? i contributed to that wiki (the opensips install part) but I'm new to opensips, could you explain how this works? Thanks.</div><div><div></div><div class="h5">
<div><br><div class="gmail_quote">On Thu, Sep 8, 2011 at 4:41 PM, Matt Stockton <span dir="ltr"><<a href="mailto:mstockton@harqen.com" target="_blank">mstockton@harqen.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi Mateusz,<div><br></div><div>I was just able to recently get this working using OpenSIPS and the instructions found here:</div><div><a href="http://wiki.freeswitch.com/wiki/Enterprise_deployment_OpenSIPS" target="_blank">http://wiki.freeswitch.com/wiki/Enterprise_deployment_OpenSIPS</a></div>
<div><br></div><div>There were a few modifications I had to make, for example:</div><div>- dlg_flag seems to be no longer available in the newest OpenSips, but I do not think it is needed.</div><div>- I removed the dispatcher module because I didn't need to support registration</div>
<div>- I had to change the INVITE conditional to be dependent on whether or not the invite was coming from outside (e.g. PSTN) or was coming from one of my freeswitch servers. For loadbalancing coming in, the load_balancer module worked fine as configured in the wiki instructions. For outbound, I used the dynamic routing module: </div>
<div><a href="http://www.unixnews.net/2010/09/dynamic-routing-with-opensips.html" target="_blank">http://www.unixnews.net/2010/09/dynamic-routing-with-opensips.html</a></div><div><br></div><div>It seems to be working well so far. I will plan to update the wiki with more information. Feel free to reach out to me if you have any questions.</div>
<div><br></div><div>Thanks,</div><div>Matt</div><div><font color="#888888"><br></font><div class="gmail_quote"><div><div></div><div>On Thu, Sep 8, 2011 at 1:59 PM, Mateusz Bartczak <span dir="ltr"><<a href="mailto:netcentrica@gmail.com" target="_blank">netcentrica@gmail.com</a>></span> wrote:<br>
</div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div></div><div>Hi<br><br>I would like to implement following scenario:<br><br>1. Central SIP proxy with 1 IP address that will redirect all incoming and outgoing SIP traffic to two SIP application servers (FreeSwitch based). Proxy will know online/offline status of each box and route calls only to active one. I need it as a central point because IP address is authorized with my providers. Also providers route incoming calls to that IP address. My providers can't automatically reroute traffic to other server, it can be done manually but it's not fast to do.<br>
<br>2. Mini cluster of two FreeSwitch boxes, box 2 will be exact copy of box 1. If box 1 fails, central server should automatically route all traffic to box 2.<br><br>Do you have any suggestions how to implement this scenario? I think that it should be easy to do, but have no idea where to start.<br>
<br>Best Regards,<br><font color="#888888">Mateusz<br><br><br>
</font><br><br></div></div><div>
FreeSWITCH-users mailing list<br>
<a href="mailto:FreeSWITCH-users@lists.freeswitch.org" target="_blank">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>
<br></div></blockquote></div><br></div>
<br><br>
FreeSWITCH-users mailing list<br>
<a href="mailto:FreeSWITCH-users@lists.freeswitch.org" target="_blank">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>
<br></blockquote></div><br></div>
</div></div><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>
<br></blockquote></div><br>