<br><br><div class="gmail_quote">On Wed, Aug 12, 2009 at 6:10 PM, Tina Martinez <span dir="ltr"><<a href="mailto:tina@a2unlimited.com" target="_blank">tina@a2unlimited.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;">
Michael,<br>
<br>
Thanks for the welcome, and for the response to my question.<br>
<br>
The call control and dynamic setup of conferences I have working (pretty cool stuff).<br>
The tricky part, as you said, is "linking" the servers together.<br>
<br>
Basically, what I need to do is establish a connection that will not be dependent<br>
on a live person being on the call. And I would prefer to avoid having to<br>
register actual phone extensions for every server -- and for every conference call.<br>
<br>
I apologize if I'm slow, but I'm new to working an application like this.</blockquote><div><br>No worries. :)<br> <br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>
<br>
In your example, you stated, "3900 is an extension set up in FS_B's dialplan",<br>
does this extension have to be a live person (or soft-phone connected using an<br>
auto-answer mechanism)? or can I setup something where there is not a phone<br>
actually connected?<br>
</blockquote><div><br>No actual telephone is needed. Here's an example dialplan snippet that you could drop right into conf/dialplan/default/ in a new file. (I prefer to put my own custom dialplan entries into a separate file instead of editing default.xml)<br>
<br><include><br> <extension name="Sample Conference at 3900"><br> <condition field="destination_number" expression="^3900$"><br> <action application="conference" data="Conf@FS_B"/><br>
</condition><br> </extension><br></include><br> <br>Put the above into conf/dialplan/default/01_ConfB.xml on the "FS_B" server. (You can make a similar file on the "FS_A" server or any other server if you'd like.)<br>
<br>You will also need to create a "public" extension which will route the inbound calls appropriately. (If that doesn't make any sense right now then don't worry, just do it. :)<br><br>Put the following into a file named conf/dialplan/public/01_ConfB.xml:<br>
<include><br>
<extension name="Sample Conference at 3900"><br>
<condition field="destination_number" expression="^3900$"><br>
<action application="transfer" data="3900 XML default"/><br>
</condition><br>
</extension><br>
</include><br><br>(Again, you can do the same on all of your servers - this will allow all servers to receive calls and route them to x3900.)<br><br>Now that you've got 3900 set up you can test it. Press F6 (or type "reloadxml") at the CLI for FS_B. Then, have a phone that is registered to FS_B make a call to 3900. It should be alone in the conference.<br>
<br>Now you'll need to set up some sort of dialplan routing to call from FS_A to FS_B, unless you have a SIP phone registered to FS_A that can dial a SIP URI. The SIP URI is: sip:3900@FS_B.IP.Address. For kicks, let's add a simple dialplan extension on FS_A that allows you to dial "23900" to get to FS_B's 3900 extension. Put this into conf/dialplan/default/01_Dial_ConfB.xml on FS_A:<br>
<br><include><br>
<extension name="Sample Conference at 3900"><br>
<condition field="destination_number" expression="^2(3900)$"><br>
<action application="bridge" data="sofia/internal/$1@FS_B.IP.Address"/><br>
</condition><br>
</extension><br>
</include><br><br>Save, and do the reloadxml (or F6) thing on FS_A CLI. Now on FS_A you can dial "23900" and it will ring right into 3900 on FS_B so that the phone registered at FS_A is in the conference on FS_B. Got it?<br>
<br>Have fun tinkering and let us know how it all goes.<br>-MC<br><br><br></div>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br>
Right now I'm able to place a call from one machine to another, but I'm calling<br>
an X-Lite phone on the second server.<br>
<br>
Also, if it is possible to call a "virtual" extension, I have no problem<br>
incorporating application logic that would clean-up the orphaned conferences on<br>
all machines when a conference call is complete. I'm more concerned with being<br>
able to setup the "links" quickly and in an elegant fashion.<br>
<br>
- T<br>
<br>
<br>
<br>
<br>
_______________________________________________<br>
FreeSWITCH-users mailing list<br>
<a href="mailto:FreeSWITCH-users@lists.freeswitch.org" target="_blank">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>