Daniel - in most cases you need only return the XML that is being requested. It is not incorrect to return more, but not as efficient. To be clear - you tried this XML and it is still failing? (the configuration name is sofia.conf) <document type="freeswitch/xml"> <section name="*directory*"> * <configuration name="sofia.conf" description="sofia gateway for user">* * <profiles>* * <profile name="user">* * <gateways>* <gateway name="user_gw_1_foobar"> <param name="username" value=""/> <param name="password" value=""/> <param name="proxy" value="foobar.example.de"/> <param name="register" value="false"/> <param name="expire-seconds" value="300"/> <param name="ping" value="300"/> <param name="retry-seconds" value="300"/> <param name="context" value="default"/> <param name="caller-id-in-from" value="true"/> </gateway> </gateways> </profile> </profiles> </configuration> </section> </document> On Wed, Apr 16, 2014 at 2:17 AM, Daniel Neubert <dnspyder@gmail.com> wrote:
Unfortunately no success - what does your local profile xml look like? I assume that at leats sth. like this has to be defined:
<profile name="user"> <gateways> </gateways> <aliases> </aliases> <domains> <domain name="user" alias="false" parse="true"/> </domains>
<settings> <param name="debug" value="0"/> [...] </settings> </profile>
I fear I do not understand the concept of mod_xml_curl here - Why does it request "gateways" for a specific profile and expects a full profile?
On 15.04.2014 19:14, Ian McMaster wrote:
Daniel,
Your XML is not complete. Try this format, which I use successfully:
<document type="freeswitch/xml"> <section name="*directory*"> * <configuration name="sofia.c" description="sofia gateway for user">* * <profiles>* * <profile name="user">* * <gateways>* <gateway name="user_gw_1_foobar"> <param name="username" value=""/> <param name="password" value=""/> <param name="proxy" value="foobar.example.de"/> <param name="register" value="false"/> <param name="expire-seconds" value="300"/> <param name="ping" value="300"/> <param name="retry-seconds" value="300"/> <param name="context" value="default"/> <param name="caller-id-in-from" value="true"/> </gateway> </gateways> </profile> </profiles> </configuration> </section> </document>
On Tue, Apr 15, 2014 at 7:20 AM, Daniel Neubert <dnspyder@gmail.com>wrote:
I've tried to include custom gateways via mod_xml_curl.
The request is correctly issued by mod_xml_curl and received by the backend:
"hostname=fire§ion=directory&tag_name=domain&key_name=name&key_value=user&Event-Name=REQUEST_PARAMS&Core-UUID=18b2b698-c487-11e3-bcc9-39daad6bb1f3&FreeSWITCH-Hostname=fire&FreeSWITCH-Switchname=fire&FreeSWITCH-IPv4=192.123.321.123&FreeSWITCH-IPv6=%3A%3A1&Event-Date-Local=2014-04-15%2012%3A48%3A57&Event-Date-GMT=Tue,%2015%20Apr%202014%2010%3A48%3A57%20GMT&Event-Date-Timestamp=1397558937493970&Event-Calling-File=sofia.c&Event-Calling-Function=config_sofia&Event-Calling-Line-Number=5174&Event-Sequence=1510&purpose=gateways&profile=user"
The backend interprets the request by "purpose=gateways" and "profile=user" to send back all gateways required for profile "user"
<document type="freeswitch/xml"> <section name="configuration">
<include> <gateway name="user_gw_1_foobar"> <param name="username" value=""/> <param name="password" value=""/> <param name="proxy" value="foobar.example.de"/> <param name="register" value="false"/> <param name="expire-seconds" value="300"/> <param name="ping" value="300"/> <param name="retry-seconds" value="300"/> <param name="context" value="default"/> <param name="caller-id-in-from" value="true"/> </gateway> </include>
</section> </document>
I've tried to remove "document", "section", "include" but no effect.
Removing all gateway xml files from local filesystem does not change anything, either.
Unfortunately the wiki https://wiki.freeswitch.org/wiki/Mod_xml_curl#Example:_purpose.3Dgatewaysdoe... not give a proper example
Thx and regards Daniel
_________________________________________________________________________ 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
_________________________________________________________________________ Professional FreeSWITCH Consulting Services:consulting@freeswitch.orghttp://www.freeswitchsolutions.com
FreeSWITCH-powered IP PBX: The CudaTel Communication Serverhttp://www.cudatel.com
Official FreeSWITCH Siteshttp://www.freeswitch.orghttp://wiki.freeswitch.orghttp://www.cluecon.com
FreeSWITCH-users mailing listFreeSWITCH-users@lists.freeswitch.orghttp://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-usershttp://www.frees...
_________________________________________________________________________ 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