Well, you're only serving the directory xml via the xml_curl. You need to make use of the Freeswitch's abiltity to use a custom database backend for it's registration and presence tables to make it foolproof. Check the core pgsql support or the odbc support in freeswitch for the listed things. 
What i have done however is to log the registration requests on the server side of the xml_curl servings and then create the bridge commands accordingly to where the user has last registered. It's a more crippled approach, but removes a point of failure for me (maintaining a pgsql server).


On Fri, May 24, 2013 at 11:08 AM, mehroz <mehroz.ashraf85@gmail.com> wrote:
Hi all,

I have a DB server, storing SIP users and auth information.

2 freeswitch servers configured with mod_xml_curl , and an attempt of
registration on both servers looks for SIP authentication from DB server. At
the moment, i am defining 2 domains on DB server (FS-1 IP and FS-2 IP), and
creating unique user , 2 times to address both domains.

I want to get rid of creating 2 users for both domains. What is the best
approach.




--
View this message in context: http://freeswitch-users.2379917.n2.nabble.com/Centralized-SIP-directory-tp7591047.html
Sent from the freeswitch-users mailing list archive at Nabble.com.

_________________________________________________________________________
Professional FreeSWITCH Consulting Services:
consulting@freeswitch.org
http://www.freeswitchsolutions.com

FreeSWITCH-powered IP PBX: The CudaTel Communication Server
http://www.cudatel.com

Official FreeSWITCH Sites
http://www.freeswitch.org
http://wiki.freeswitch.org
http://www.cluecon.com

FreeSWITCH-users mailing list
FreeSWITCH-users@lists.freeswitch.org
http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
http://www.freeswitch.org