Hi Eric - The way that we do it is to keep each gateway in its own Sofia profile. Issuing api sofia profile <profile> start reloadxml does one call to the web server for that profile's XML, which can be pretty compact if it just contains one gateway. --Dave

Hello,

We are looking at Freeswitch to solve a problem of ours, we have thousands of users with individual gateway information. The user's will not register with us, but we need to register with their gateways on their behalf.

Since users will be constantly adding/changing/deleting gateways, we figure mox_xml_curl is the best way to maintain the configuration.

What we are not sure of is if we should be putting the gateway information in the directory entry for each user (gateways are not shared between users) or if the gateway should go in the configuration.

If the gateway configuration is in the directory, how does sofia know when the gateway configuration changes? The reloadxml documentation doesn't talk about gateways in the directory, does it work with the directory. If so, is it one curl call or one call per user? Is there a way to tell sofia that only one user's gateway configuration has changed?

Likewise with gateways in the configuration. Does reloadxml generate one curl call or many?

In both cases, is there a way to minimize parsing the data that has not changed?

-- Eric Chamberlain

_______________________________________________ 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