<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
I actually spent a big chunk of today doing various tests. Freeswitch
is doing all the right things in this scenario. The problem actually
turns out to be my router/firewall that I'm testing behind. When the
phones register, it only opens up the port back from the IP address of
the server it registers to, so when the secondary server tries to send
the invite, the router blocks it. In case anyone is curious, the
router/firewall is a Linux box running Arno's Firewall. I'll be doing
more tests with different routers to see which ones work and which ones
don't. I'll post my results on the wiki page that I'll be creating
that covers the setup I've got.<br>
<br>
For your other points, I'll take them (at least a few of them) one by
one.<br>
<br>
1. I'm doing this already to an extent. My "fs1" box is using a
floating IP address and is being monitored using Redhat's cluster
suite. If that box goes down, the IP's migrate to a backup machine
that contains identical copies of the configurations and access to the
shared storage. While not a load balancer, this keeps the primary
switch up (except for the wedges that I've been experiencing that I
talk about in another thread).<br>
<br>
The failover switch, my "fs2" box, is running on in a Xen guest machine
on another server.<br>
<br>
<br>
2. Freeswitch can't do what you describe. I believe that it does have
the architecture for it, though, and it will just be a SMOP(tm) (Simple
Matter Of Programming). Once Freeswitch matures a bit more I expect
we'll be seeing all sorts of enterprise solutions for it.<br>
<br>
3. True. Unless you control everything end to end like Cisco's Call
Manager, you have to deal with what's out there, so you work up
solutions like the one I've described.<br>
<br>
4. Brian followed up on this point, and he said it better than I could.<br>
<br>
5. I do agree that conferencing needs to be a bit more robust in a
clustered environment. However, there is already a lot of that can be
done to make Freeswitch scale by having multiple boxes and putting
different conferences on different servers. Using xml_curl, you can
write a back-end application that easily routes conferences to multiple
different boxes to allow some form of load balancing.<br>
<br>
6. I'm not nearly as worried about current calls dropping in the case
of a failure as I am about new calls being routed and phones being
registered. It would be nice in the case of a failure to not have
calls drop, but not a requirement for me.<br>
<br>
7. Carrierroute works extremely well for me in my environment. It
allows me to have great control with least cost routing as well as have
automatic redundant gateways both in and out. It also supports the
shared database model for building in my own redundancies. The only
thing that I don't like about it is that I can't selectively handle the
media path. With my CR setup it doesn't touch any media at all. That
has caused me some issues with one or two of my carriers, but nothing
that was insurmountable. The ones I've had problems with expect you to
be running a b2bua and have media come from the same IP as the SIP
messages. For that reason alone I may end up replacing OpenSER with
Freeswitch at some point in the future and selectively bypass media,
but only if I can get a configuration as efficient as my CR setup. If
not, I'll just add a second Freeswitch gateway that talks only to those
certain providers. Not ideal, but it works.<br>
<br>
I will be starting a wiki page about everything I've setup within the
next couple days.<br>
<br>
- Marc<br>
<br>
Yuval Hertzog wrote:
<blockquote cite="mid:54220.1225324473@iinet.net.au" type="cite">
<p class="MsoNormal" style="margin: 0cm 0cm 12pt;"><span
style="font-size: 9pt; font-family: Arial;">I assume the problem you
asked about it happening because the client is disregarding the INVITE
from a server with an IP address it was not registered to. If you try
to capture the packets going out of your FS (or packets coming in your
phone client), I bet you'll see the INVITE request, but no activity
thereafter.<br>
<br>
I believe that when considering High-Availability for FreeSWITCH, these
issues need to be addressed:<br>
1. A shared/floating IP clustering solution such as a load-balancer
will only work if the <st1:City w:st="on"><st1:place w:st="on">SOFIA</st1:place></st1:City>
hash table is shared between all servers. I don’t know if FreeSWITCH
entire state is being held in the database or whether some elements are
being held in memory.<o:p></o:p></span></p>
<p class="MsoNormal" style="margin: 0cm 0cm 12pt;"><span
style="font-size: 9pt; font-family: Arial;">2. FreeSWITCH needs to
have shared-bus architecture to allow for a fully clustered solution.
Currently, I don’t think that two parked channels on different
cluster nodes can be bridged in the current architecture because
there’s no inter-cluster media switching protocol that I know of.<o:p></o:p></span></p>
<p class="MsoNormal" style="margin: 0cm 0cm 12pt;"><span
style="font-size: 9pt; font-family: Arial;">3. A Meshed server
approach where different clients are registered to different nodes
(like the Cisco Call Manager architecture) seems to be the only
immediate option but it is problematic as it requires the client to be
configured with a list of redundant servers and most clients don’t
have that functionality.<o:p></o:p></span></p>
<p class="MsoNormal" style="margin: 0cm 0cm 12pt;"><span
style="font-size: 9pt; font-family: Arial;">4. I would strongly
recommend reconsidering the use of any DNS feature (such as SRV
records) when deploying a telephony infrastructure. Of course, it all
depends what this deployment is for. DNS is commonly used in the ITSP
space due to the vast audience but enterprises (all sized) are
recommended to refrain adding DNS to the list of point-of-failures in
their telephony architectures.<o:p></o:p></span></p>
<p class="MsoNormal" style="margin: 0cm 0cm 12pt;"><span
style="font-size: 9pt; font-family: Arial;">5. I believe the
FreeSWITCH conferencing module needs to be adapted to support
clustering in order to scale over more than one server. This is due to
the same share-bus issue mentioned earlier.<o:p></o:p></span></p>
<p class="MsoNormal" style="margin: 0cm 0cm 12pt;"><span
style="font-size: 9pt; font-family: Arial;">6. In a meshed servers
architecture you will need to implement a mechanism that will identify
which node in the cluster “owns” B-Leg, bridge the call to that
node and in that node bridge the call again to B-Leg. When you find a
way to implement it (I believe FreeSWITCH to have the tools to enable
you to do it now), it would solve your current issue.<o:p></o:p></span></p>
<p class="MsoNormal" style="margin: 0cm 0cm 12pt;"><span
style="font-size: 9pt; font-family: Arial;">7. I still have doubts
about using carrierroute module opposed to the DISPATCHER module for
inbound traffic, mainly because of the registration issue, but I
don’t have sufficient experience to determine that.<o:p></o:p></span></p>
<p class="MsoNormal" style="margin: 0cm 0cm 12pt;"><span
style="font-size: 9pt; font-family: Arial;"><o:p> </o:p></span></p>
<p class="MsoNormal" style="margin: 0cm 0cm 12pt;"><span
style="font-size: 9pt; font-family: Arial;">Anyway, it’s very
interesting and I definitely like to know how you’re going with it.<o:p></o:p></span></p>
<br>
<br>
<br>
<b>On Thu Oct 30 2:04 , "Anthony Minessale" <ANTHONY.MINESSALE@GMAIL.COM>sent:<br>
<br>
</ANTHONY.MINESSALE@GMAIL.COM></b>
<blockquote
style="border-left: 2px solid rgb(81, 103, 198); padding-right: 0px; padding-left: 5px; margin-left: 5px; margin-right: 0px;">This
all seems right and would make a great wiki page.<br>
What you have described *should* work.<br>
<br>
when a phone registers try doing <br>
sofia_contact <<a moz-do-not-send="true"
href="javascript:top.opencompose('user@domain.com','','','')">user@domain.com</a>>
<br>
from the cli on each box and see what you get.<br>
<br>
you can also use this function in the dialpan <br>
${sofia_contact(<a moz-do-not-send="true"
href="javascript:top.opencompose('user@domain.com','','','')">user@domain.com</a>)}<br>
<br>
check that they are both using the same domain name as the profile name<br>
or at least have an alais for it etc.<br>
<br>
if it's a bug i can fix it pretty fast as that is the intended behaviour<br>
perhaps you can join irc and get us in the box(s) to have a look at it
as we <br>
do not have that situation labbed up anywhere.<br>
<br>
<br>
<br>
<br>
<div class="gmail_quote">On Tue, Oct 28, 2008 at 6:41 PM, Marc
Lewis <span dir="ltr"><<a moz-do-not-send="true"
href="javascript:top.opencompose('marc@avvatel.com','','','')">marc@avvatel.com</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;"><br>
I am in the process of making my FreeSWITCH installation highly<br>
available and I'm running into a couple of snags that was hoping that<br>
someone may have some insight on.<br>
<br>
First, the setup as it is now.<br>
<br>
There are two installations of FS on two different servers, lets call<br>
them fs1 and fs2. They each pull their configurations, dialplan,<br>
directory and post CDR's all using mod_curl from a central web server.<br>
That part works great.<br>
<br>
Calls into and out of FS go through an OpenSER proxy set up using<br>
carrierroute. That part also works great for outbound calls to the<br>
PSTN. Inbound calls also come in through this OpenSER proxy and get<br>
routed to the primary switch fs1. That also works perfectly as long as<br>
its going to fs1.<br>
<br>
fs1 and fs2 are both setup to use an ODBC connection to store<br>
registrations. This is pointed to a MySQL database made highly<br>
available using the RedHat Cluster Suite on a shared fibre channel<br>
partition. fs1 and fs2 both share the same database. Voicemail storage<br>
on fs1 is directly mounted on a GFS2 partition, fs2 is mounting the<br>
shared storage from a different server via NFS for no single point of<br>
failure.<br>
<br>
For the phones, I have them setup to use SRV records and have fs1 at<br>
priority 10 and fs2 at priority 20 for <a moz-do-not-send="true"
href="http://acme.domain.com" target="_blank">acme.domain.com</a>.
I've tested<br>
this and phones register to the correct server and the sip_registration<br>
table shows either fs1 or fs2 as the hostname as I would expect.<br>
<br>
Here is the problem. If user <a moz-do-not-send="true"
href="javascript:top.opencompose('100@acme.domain.com','','','')">100@acme.domain.com</a>
registers on fs2 and a<br>
call comes in from the OpenSER proxy to fs1, bridging the call to<br>
/sofia/internal/100%<a moz-do-not-send="true"
href="http://acme.domain.com" target="_blank">acme.domain.com</a> from
fs1 doesn't ring the phone. Is<br>
there a difference between 'sofia/internal/100%<a moz-do-not-send="true"
href="http://acme.domain.com" target="_blank">acme.domain.com</a>' and<br>
'user/<a moz-do-not-send="true"
href="javascript:top.opencompose('100@acme.domain.com','','','')">100@acme.domain.com</a>'?<br>
<br>
Calls out from either fs1 or fs2 routed to the proxy work fine, its just<br>
calls coming in from the proxy. If the call doesn't go to the switch<br>
the user is registered on, the user's phone doesn't ring. It still goes<br>
to voicemail, etc., so that part works.<br>
<br>
Is there a better way to cluster FreeSWITCH than DNS SRV records and a<br>
shared state database?<br>
<br>
Also, as a side note to Anthony, Brian, et al, if this is the best way,<br>
I'll be happy to write up a wiki page on how I have this setup with a<br>
lot more detail than this. I was not able to find much in the way of<br>
highly available configurations or cluster configurations, so I put<br>
together this system using information cobbled from the wiki, mailing<br>
list messages and lurking on IRC.<br>
<br>
Thanks.<br>
<br>
- Marc<br>
<br>
--<br>
Marc Lewis<br>
Avvatel Corporation<br>
<br>
<br>
_______________________________________________<br>
Freeswitch-users mailing list<br>
<a moz-do-not-send="true"
href="javascript:top.opencompose('Freeswitch-users@lists.freeswitch.org','','','')">Freeswitch-users@lists.freeswitch.org</a><br>
<a moz-do-not-send="true"
href="http://lists.freeswitch.org/mailman/listinfo/freeswitch-users"
target="_blank">http://lists.freeswitch.org/mailman/listinfo/freeswitch-users</a><br>
UNSUBSCRIBE:<a moz-do-not-send="true"
href="http://lists.freeswitch.org/mailman/options/freeswitch-users"
target="_blank">http://lists.freeswitch.org/mailman/options/freeswitch-users</a><br>
<a moz-do-not-send="true" href="http://www.freeswitch.org"
target="_blank">http://www.freeswitch.org</a><br>
</blockquote>
</div>
<br>
<br clear="all">
<br>
-- <br>
Anthony Minessale II<br>
<br>
FreeSWITCH <a moz-do-not-send="true" href="http://www.freeswitch.org/"
target="_blank">http://www.freeswitch.org/</a><br>
ClueCon <a moz-do-not-send="true" href="http://www.cluecon.com/"
target="_blank">http://www.cluecon.com/</a><br>
<br>
AIM: anthm<br>
<a moz-do-not-send="true"
href="javascript:top.opencompose('MSN:anthony_minessale@hotmail.com','','','')">MSN:anthony_minessale@hotmail.com</a><br>
GTALK/JABBER/<a moz-do-not-send="true"
href="javascript:top.opencompose('PAYPAL:anthony.minessale@gmail.com','','','')">PAYPAL:anthony.minessale@gmail.com</a><br>
IRC: <a moz-do-not-send="true" href="http://irc.freenode.net">irc.freenode.net</a>
#freeswitch<br>
<br>
FreeSWITCH Developer Conference<br>
<a moz-do-not-send="true"
href="javascript:top.opencompose('sip:888@conference.freeswitch.org','','','')">sip:888@conference.freeswitch.org</a><br>
<a moz-do-not-send="true"
href="http://iax:guest@conference.freeswitch.org/888">iax:guest@conference.freeswitch.org/888</a><br>
<a moz-do-not-send="true"
href="javascript:top.opencompose('googletalk:conf_PLUS_888@conference.freeswitch.org','','','')">googletalk:conf+888@conference.freeswitch.org</a><br>
pstn:213-799-1400<br>
</blockquote>
<br>
<pre wrap="">
<hr size="4" width="90%">
_______________________________________________
Freeswitch-users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Freeswitch-users@lists.freeswitch.org">Freeswitch-users@lists.freeswitch.org</a>
<a class="moz-txt-link-freetext" href="http://lists.freeswitch.org/mailman/listinfo/freeswitch-users">http://lists.freeswitch.org/mailman/listinfo/freeswitch-users</a>
UNSUBSCRIBE:<a class="moz-txt-link-freetext" href="http://lists.freeswitch.org/mailman/options/freeswitch-users">http://lists.freeswitch.org/mailman/options/freeswitch-users</a>
<a class="moz-txt-link-freetext" href="http://www.freeswitch.org">http://www.freeswitch.org</a>
</pre>
</blockquote>
<br>
<br>
<pre class="moz-signature" cols="72">--
Marc Lewis
Avvatel Corporation
</pre>
</body>
</html>