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 href="mailto: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 href="mailto: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 href="mailto: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 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 href="mailto: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 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 href="http://acme.domain.com" target="_blank">acme.domain.com</a>' and<br>
'user/<a href="mailto: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 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><br clear="all"><br>-- <br>Anthony Minessale II<br><br>FreeSWITCH <a href="http://www.freeswitch.org/">http://www.freeswitch.org/</a><br>ClueCon <a href="http://www.cluecon.com/">http://www.cluecon.com/</a><br>
<br>AIM: anthm<br><a href="mailto:MSN%3Aanthony_minessale@hotmail.com">MSN:anthony_minessale@hotmail.com</a><br>GTALK/JABBER/<a href="mailto:PAYPAL%3Aanthony.minessale@gmail.com">PAYPAL:anthony.minessale@gmail.com</a><br>
IRC: <a href="http://irc.freenode.net">irc.freenode.net</a> #freeswitch<br><br>FreeSWITCH Developer Conference<br><a href="mailto:sip%3A888@conference.freeswitch.org">sip:888@conference.freeswitch.org</a><br><a href="http://iax:guest@conference.freeswitch.org/888">iax:guest@conference.freeswitch.org/888</a><br>
<a href="mailto:googletalk%3Aconf%2B888@conference.freeswitch.org">googletalk:conf+888@conference.freeswitch.org</a><br>pstn:213-799-1400<br>