[Freeswitch-users] conference calling ideas
Michael Collins
msc at freeswitch.org
Wed Mar 25 13:53:02 PDT 2009
Hey, if you guys get this all figured out, tested, and working then
please be sure to put it on the wiki. You could create a whole new
page and then link to/from the mod_conference page.
-MC
On Wed, Mar 25, 2009 at 7:02 AM, Szymon Olko <solko at gcdf.pl> wrote:
> Steven Ward pisze:
>> Szymon, I want to provide a service wherein a user can reserve a
>> teleconference room for a partiuclar time and control who can join the
>> conference call (only those invited). I want to support several of
>> such conference calls at any given time.
>>
>> I want callers who were not invited to a conference call, but who try to
>> call in, to be notified they can't join.
>>
> Reserving conference means some storage of it. I think you have write some application to control it.
> You can use store that in dialplan but it will be hard to make such dialplan.
> There is pin code for conference so you can use it.
>
>> Also, it should be simple enough that the user just has to dial a number
>> and be able to know what to do from there to join the conference.
>>
>> If the conference leader is late to the conference call and others try
>> to call in (before the conference is created), the callers should be
>> notified the conf leader hasn't started the conference yet. Perhaps
>> they can be told to try later, or they can be put on hold.
>>
>> These are the kinds of things I need to think about implementing, and I
>> do not know yet what other features would be useful. Thanks.
>
> I would make it like that. If you need to limit total number of conferences then you have to manage time of reservation. If you
> don't need that then make one extension in which you do the following.
> - get pincode from user.
> - get admin_pincode from user.
> - look in db for next available conference number
> - store conference number and pincode in database.
> - return that number to user.
>
> Make second extension where you do folowing:
> - get conference number from user
> - get pincode from user
> - check in db if conference and pincode are the same as stored in db.
> - check in database if admin is in conference.
>
>
> Make third extension:
> - get conference number from user
> - get admin pincode from user
> - check for matching in db
> - transfer to conference
> - store in db that admin is online
>
>
> With this way users must get conference name and pincode to access. You can change it and in first extension add ability for user
> to add others members with their personal number or something like that.
>
> Szymon Olko
>
>> On Wed, Mar 25, 2009 at 9:02 AM, Szymon Olko <solko at gcdf.pl> wrote:
>>
>> Steven Ward pisze:
>> > If any can share some ideas, I'm looking at making conference
>> > calls simple for the end-users of my FS system.
>> >
>> > Here are some issues I'm kicking around:
>> >
>> > 1. To create/join conferences - do you make a pre-defined list of
>> > extensions, each of which would join the caller to a particular
>> > conference room, or do you perhaps define one extension that will join
>> > the caller to a dynamically-named conference room (perhaps after
>> making
>> > a choice in an IVR)?
>> >
>> > 2. How do you implement the idea of a conference leader - having a
>> > user who must call into a conference first before anybody else can
>> join?
>> >
>> > Thanks for any ideas.
>> >
>> Can you give more info what you plan to do?
>>
>> If you don't care for conferences name and they can be numbers then
>> just make one extension and then use that extension or part of
>> it to name conference.
>>
>> If you want to make conference leader then make 2 separate
>> extensions, in second extension which is used for not leaders use that
>> conference command. 'conference xxx bgdial <endpoint>'.In current
>> SVN, bgdial does not create new conference it must exists to
>> make that command.
>>
>> This can be make just by dial plan. If you plan to control FS from
>> any language then you have much more abilities.
>>
>> > - SW
>> >
>> >
>> >
>> ------------------------------------------------------------------------
>> >
>> > _______________________________________________
>> > Freeswitch-users mailing list
>> > Freeswitch-users at lists.freeswitch.org
>> <mailto:Freeswitch-users at lists.freeswitch.org>
>> > http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
>> >
>> UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
>> > http://www.freeswitch.org <http://www.freeswitch.org/>
>>
>>
>> _______________________________________________
>> Freeswitch-users mailing list
>> Freeswitch-users at lists.freeswitch.org
>> <mailto:Freeswitch-users at lists.freeswitch.org>
>> http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
>> UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
>> http://www.freeswitch.org <http://www.freeswitch.org/>
>>
>>
>>
>> ------------------------------------------------------------------------
>>
>> _______________________________________________
>> Freeswitch-users mailing list
>> Freeswitch-users at lists.freeswitch.org
>> http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
>> UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
>> http://www.freeswitch.org
>
>
> _______________________________________________
> Freeswitch-users mailing list
> Freeswitch-users at lists.freeswitch.org
> http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
> UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
> http://www.freeswitch.org
>
More information about the FreeSWITCH-users
mailing list