That may be true, because you don't always know what files/folders to edit. Technically, you may not even need files/folders because you are using mod_xml_curl or something like that. However, we could add a sentence like:<br>
<br>"If you are using the default 'vanilla' configs, the groups are defined in conf/directory/default.xml and the dialplan entries are found in conf/dialplan/default.xml"<br><br>Would that help? If so, please add that text as I'm positive that it's correct. If you are having trouble with wiki editing let me know and I'll be happy to help. At some point one of these days I'm gonna do screencast w/ training on how to do wiki editing...<br>
<br>-MC<br><br><div class="gmail_quote">On Mon, Jul 9, 2012 at 10:08 AM, Todd Bailey <span dir="ltr"><<a href="mailto:toddb@toddbailey.net" target="_blank">toddb@toddbailey.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I think what is missing in this wiki is it doesn't explicitly state what<br>
file(s) and in what folder(s) needs to be edited.<br>
<br>
<br>
<br>
here is an extract of the section that I suspect is what I need to<br>
follow<br>
<br>
Groups<br>
<br>
A group is a logical collection of users that FreeSWITCH can use to<br>
bridge calls in a serial or parallel fashion, depending on the arguments<br>
to the group_call application. Using groups is optional -- you can put<br>
your users straight into the domain section if you desire.<br>
<br>
This is specially useful if you use mod_xml_curl to provide the user<br>
directory to FreeSWITCH and want to group some users in a logical<br>
structure. The following group '200' groups four users. It's interesting<br>
to notice the "dial-string" param, which is used to bridge the calls to<br>
those users. Users 1000 and 1001 will use the default "dial-string"<br>
while user 2014 uses a loopback channel so FreeSWITCH can actually query<br>
the dialplan to figure out how to reach that user (this also works for<br>
external numbers through OpenZAP and gateways):<br>
<br>
type="pointer" is a pointer so you can have the same user in multiple<br>
groups. It basically means to keep searching for the user in the<br>
directory.<br>
<br>
<document type="freeswitch/xml"><br>
<section name="directory"><br>
<domain name="<a href="http://sip.example.com" target="_blank">sip.example.com</a>"><br>
<users><br>
<user id="1000"><br>
<params><br>
<param name="dial-string" value="{presence_id=${dialed_user}@<br>
${dialed_domain}}${sofia_contact(${dialed_user}@${dialed_domain})}"/><br>
</params><br>
<variables><br>
<variable name="user_context" value="default"/><br>
</variables><br>
</user><br>
<user id="1001"><br>
<params><br>
<param name="dial-string" value="{presence_id=${dialed_user}@<br>
${dialed_domain}}${sofia_contact(${dialed_user}@${dialed_domain})}"/><br>
</params><br>
<variables><br>
<variable name="user_context" value="default"/><br>
</variables><br>
</user><br>
</users><br>
<groups><br>
<group name="200"><br>
<users><br>
<user id="2014"><br>
<params><br>
<param name="dial-string"<br>
value="loopback/2014/default/XML"/><br>
</params><br>
<variables><br>
<variable name="user_context" value="default"/><br>
</variables><br>
</user><br>
<user id="1000" type="pointer"/><br>
<user id="1001" type="pointer"/><br>
</users><br>
</group><br>
</groups><br>
</domain><br>
</section><br>
</document><br>
<br>
The dialplan for the above group can be defined like this:<br>
<br>
<extension name="Group 200"><br>
<condition field="destination_number" expression="200"><br>
<action application="set" data="hangup_after_bridge=true"/><br>
<action application="set" data="continue_on_fail=true"/><br>
<action application="set"<br>
data="originate_continue_on_timeout=true"/><br>
<action application="set" data="call_timeout=15"/><br>
<action application="bridge" data="${group_call(200@<br>
${domain_name}+F)}"/><br>
<action application="transfer" data="200 XML default"/><br>
<action application="hangup"/><br>
</condition><br>
</extension><br>
<br>
The extension 200 will ring all the users defined in the user directory<br>
for group 200 in a serial fashion (specified by the +F argument, if you<br>
want to ring all the users at once use the +A argument) for 15 seconds,<br>
then it will transfer the call to the same group again so the call will<br>
ring the group infinitely.<br>
<br>
To explain the variables set prior to the bridge:<br>
<br>
The hangup_after_bridge is set to true for this effect: if the bridge is<br>
successfully answered and the B-leg later hangs up, the A-leg will also<br>
be hung up.<br>
<br>
The continue_on_fail is set to true for this: if the bridge fails,<br>
dialplan execution will continue and the transfer will be executed.<br>
<br>
The originate_continue_on_timeout is set to true for this: if the<br>
bridge's dial string specifies several destinations separated by the<br>
"|" (this is for failover), the bridge will time out on an unanswered<br>
destination and will attempt the next specified destination. Without<br>
originate_continue_on_timeout set to true, the bridge will time out on<br>
the first destination it tries and the bridge itself will fail. (In the<br>
example above, the bridge string is generated by group_call with the +F<br>
option; this specifies a dial string with all the group's destinations<br>
separated by "|". So originate_continue_on_timeout needs to be set to<br>
true for serial calling behavior.)<br>
<br>
The call_timeout is set so that the bridge attempt to a destination that<br>
goes unanswered will time out. NOTE: If the destination sends early<br>
media, the bridge will be answered (pre-answered) and will NOT time out!<br>
To time out a bridge attempt to a destination sending early media, set<br>
ignore_early_media to true.<br>
<br>
The dialplan for user 2014, which in this example happens to be<br>
terminated through a gateway defined via mod_lcr, can be defined like<br>
this:<br>
<br>
<extension name="Extension 2014"><br>
<condition field="destination_number" expression="2014"><br>
<action application="lcr" data="2014"/><br>
<action application="set" data="dialed_ext=${lcr_auto_route}"/><br>
<action application="export" data="dialed_ext=<br>
${lcr_auto_route}"/><br>
<action application="set" data="hangup_after_bridge=true"/><br>
<action application="set" data="call_timeout=120"/><br>
<action application="bridge" data="${lcr_auto_route}"/><br>
<action application="hangup"/><br>
</condition><br>
</extension><br>
<br>
<br>
<br>
<br>
On Mon, 2012-07-09 at 01:49 -0700, Stanislav Sinyagin wrote:<br>
> <a href="http://wiki.freeswitch.org/wiki/XML_User_Directory_Guide" target="_blank">http://wiki.freeswitch.org/wiki/XML_User_Directory_Guide</a><br>
<br>
<br>
_________________________________________________________________________<br>
Professional FreeSWITCH Consulting Services:<br>
<a href="mailto:consulting@freeswitch.org">consulting@freeswitch.org</a><br>
<a href="http://www.freeswitchsolutions.com" target="_blank">http://www.freeswitchsolutions.com</a><br>
<br>
FreeSWITCH-powered IP PBX: The CudaTel Communication Server<br>
<a href="http://www.cudatel.com" target="_blank">http://www.cudatel.com</a><br>
<br>
Official FreeSWITCH Sites<br>
<a href="http://www.freeswitch.org" target="_blank">http://www.freeswitch.org</a><br>
<a href="http://wiki.freeswitch.org" target="_blank">http://wiki.freeswitch.org</a><br>
<a href="http://www.cluecon.com" target="_blank">http://www.cluecon.com</a><br>
<br>
Join Us At ClueCon - Aug 7-9, 2012<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>