[Freeswitch-dev] Conference Hangup
Is there a way to configure the dialplan so that the FS could terminate the conference session upon certain condition? The scenario is: 1. User A dials a number 2. FS starts a conference session by ringing User B and User C ( and User D or any number of other Users ) 3. User B joins the conference ( along with other invited Users ) 4. After talking a while, User B leaves the conference 5. At here, could FS be triggered to terminate the conference? Regards Scott
The question is why user B? how do you determine which user that that leave that need to trigger conference termination. FS is very flexible, It definitely can support your scenario. It may not be from dialplan alone, You might want to take a look at event_socket module for advance conference control. On Mon, Feb 16, 2009 at 6:46 PM, Scott Shen <sshen@oa.com.au> wrote:
Is there a way to configure the dialplan so that the FS could terminate the conference session upon certain condition?
The scenario is:
User A dials a number FS starts a conference session by ringing User B and User C ( and User D or any number of other Users ) User B joins the conference ( along with other invited Users ) After talking a while, User B leaves the conference At here, could FS be triggered to terminate the conference?
Regards
Scott
_______________________________________________ Freeswitch-dev mailing list Freeswitch-dev@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-dev UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-dev http://www.freeswitch.org
You make sure you push the user into the conference with the endconf flag. ie 1234@default+flags{endconf} /b On Feb 17, 2009, at 5:25 PM, Johny Kadarisman wrote:
The question is why user B? how do you determine which user that that leave that need to trigger conference termination.
FS is very flexible, It definitely can support your scenario. It may not be from dialplan alone, You might want to take a look at event_socket module for advance conference control.
You make sure you push the user into the conference with the endconf flag. ie 1234@default+flags{endconf}
/b
FYI, it looks like many of the conference flags are missing from the wiki. I will update the mod_conference page and make sure that all of the flags are properly documented. -MC
There you go, something to learn everytime i read a new post. I feel event_socket kind of old fashion, now seems like tons of dialplan flags that will do some magic trick :) On Tue, Feb 17, 2009 at 6:38 PM, Michael Collins <msc@freeswitch.org> wrote:
You make sure you push the user into the conference with the endconf flag. ie 1234@default+flags{endconf}
/b
FYI, it looks like many of the conference flags are missing from the wiki. I will update the mod_conference page and make sure that all of the flags are properly documented.
-MC
_______________________________________________ Freeswitch-dev mailing list Freeswitch-dev@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-dev UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-dev http://www.freeswitch.org
On Tue, Feb 17, 2009 at 3:52 PM, Johny Kadarisman <jkr888@gmail.com> wrote:
There you go, something to learn everytime i read a new post. I feel event_socket kind of old fashion, now seems like tons of dialplan flags that will do some magic trick :)
FYI, I am working on the documentation for all of this. I will keep updating things as I learn them also. This item wasn't anywhere on the wiki. I will have it and the rest of the member flags documented shortly. -MC
Thanks MC, i dont meant to complain, just saying that FS evolve so quickly, that none of us (pointing to me) can keep up with all the nice trick with dialplan flags/var. Should we have some central location in wiki to track this? or even better, maybe we should do something at code level that automatically track this kind of flags. Something like a core api to registers the flags + some description. Then, we can issus something like "show flags" or similar. This at least show us what kind of flags that available in the system. On Tue, Feb 17, 2009 at 7:09 PM, Michael Collins <msc@freeswitch.org> wrote:
On Tue, Feb 17, 2009 at 3:52 PM, Johny Kadarisman <jkr888@gmail.com> wrote:
There you go, something to learn everytime i read a new post. I feel event_socket kind of old fashion, now seems like tons of dialplan flags that will do some magic trick :)
FYI, I am working on the documentation for all of this. I will keep updating things as I learn them also. This item wasn't anywhere on the wiki. I will have it and the rest of the member flags documented shortly.
-MC
_______________________________________________ Freeswitch-dev mailing list Freeswitch-dev@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-dev UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-dev http://www.freeswitch.org
On Tue, Feb 17, 2009 at 5:12 PM, Johny Kadarisman <jkr888@gmail.com> wrote:
Thanks MC, i dont meant to complain, just saying that FS evolve so quickly, that none of us (pointing to me) can keep up with all the nice trick with dialplan flags/var. Yeah, now try to document all that stuff! ;) It's okay, everyone knows that Tony and company can write software much faster than we can document it.
Should we have some central location in wiki to track this? or even better, maybe we should do something at code level that automatically track this kind of flags. Something like a core api to registers the flags + some description.
There is merit to this idea. I would be willing to discuss it further. Please contact me off list if you have ideas. It's something that I've been wanting to do for a while. -MC
Then, we can issus something like "show flags" or similar. This at least show us what kind of flags that available in the system.
How about we bring back our weekly meetings and start writing docs in a more collaborative method? /b On Feb 17, 2009, at 7:12 PM, Johny Kadarisman wrote:
Thanks MC, i dont meant to complain, just saying that FS evolve so quickly, that none of us (pointing to me) can keep up with all the nice trick with dialplan flags/var. Should we have some central location in wiki to track this? or even better, maybe we should do something at code level that automatically track this kind of flags. Something like a core api to registers the flags + some description. Then, we can issus something like "show flags" or similar. This at least show us what kind of flags that available in the system.
Can this flag be used in a group_call? How? If yes, is it means anyone in the group who joined the conference will be able to terminate the conference upon leaving? -----Original Message----- From: freeswitch-dev-bounces@lists.freeswitch.org [mailto:freeswitch-dev-bounces@lists.freeswitch.org] On Behalf Of Brian West Sent: Wednesday, 18 February 2009 10:30 AM To: freeswitch-dev@lists.freeswitch.org Subject: Re: [Freeswitch-dev] Conference Hangup You make sure you push the user into the conference with the endconf flag. ie 1234@default+flags{endconf} /b On Feb 17, 2009, at 5:25 PM, Johny Kadarisman wrote:
The question is why user B? how do you determine which user that that leave that need to trigger conference termination.
FS is very flexible, It definitely can support your scenario. It may not be from dialplan alone, You might want to take a look at event_socket module for advance conference control.
_______________________________________________ Freeswitch-dev mailing list Freeswitch-dev@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-dev UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-dev http://www.freeswitch.org
If everyone trigger the termination, then I think it should even easier to accomplish. When you put the new participant into conference, per Brian recommendation, just initiate conference with that flags. ie. "3000@default+flags{endconf}" On Tue, Feb 17, 2009 at 7:36 PM, Scott Shen <sshen@oa.com.au> wrote:
Can this flag be used in a group_call? How? If yes, is it means anyone in the group who joined the conference will be able to terminate the conference upon leaving?
-----Original Message----- From: freeswitch-dev-bounces@lists.freeswitch.org [mailto:freeswitch-dev-bounces@lists.freeswitch.org] On Behalf Of Brian West Sent: Wednesday, 18 February 2009 10:30 AM To: freeswitch-dev@lists.freeswitch.org Subject: Re: [Freeswitch-dev] Conference Hangup
You make sure you push the user into the conference with the endconf flag. ie 1234@default+flags{endconf}
/b
On Feb 17, 2009, at 5:25 PM, Johny Kadarisman wrote:
The question is why user B? how do you determine which user that that leave that need to trigger conference termination.
FS is very flexible, It definitely can support your scenario. It may not be from dialplan alone, You might want to take a look at event_socket module for advance conference control.
_______________________________________________ Freeswitch-dev mailing list Freeswitch-dev@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-dev UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-dev http://www.freeswitch.org
_______________________________________________ Freeswitch-dev mailing list Freeswitch-dev@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-dev UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-dev http://www.freeswitch.org
Thanks for the quick response, however, I meant "group call", something like <action application="conference_set_auto_outcall" data="${group_call(sales)}"/> could I do something like <action application="conference_set_auto_outcall" data="${group_call(sales)}+flag(endconf)"/> In this case, I would assume anyone in the group could terminate the conference upon leaving, is that right? -----Original Message----- From: freeswitch-dev-bounces@lists.freeswitch.org [mailto:freeswitch-dev-bounces@lists.freeswitch.org] On Behalf Of Johny Kadarisman Sent: Wednesday, 18 February 2009 11:53 AM To: freeswitch-dev@lists.freeswitch.org Subject: Re: [Freeswitch-dev] Conference Hangup If everyone trigger the termination, then I think it should even easier to accomplish. When you put the new participant into conference, per Brian recommendation, just initiate conference with that flags. ie. "3000@default+flags{endconf}" On Tue, Feb 17, 2009 at 7:36 PM, Scott Shen <sshen@oa.com.au> wrote:
Can this flag be used in a group_call? How? If yes, is it means anyone in the group who joined the conference will be able to terminate the conference upon leaving?
-----Original Message----- From: freeswitch-dev-bounces@lists.freeswitch.org [mailto:freeswitch-dev-bounces@lists.freeswitch.org] On Behalf Of Brian West Sent: Wednesday, 18 February 2009 10:30 AM To: freeswitch-dev@lists.freeswitch.org Subject: Re: [Freeswitch-dev] Conference Hangup
You make sure you push the user into the conference with the endconf flag. ie 1234@default+flags{endconf}
/b
On Feb 17, 2009, at 5:25 PM, Johny Kadarisman wrote:
The question is why user B? how do you determine which user that that leave that need to trigger conference termination.
FS is very flexible, It definitely can support your scenario. It may not be from dialplan alone, You might want to take a look at event_socket module for advance conference control.
_______________________________________________ Freeswitch-dev mailing list Freeswitch-dev@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-dev UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-dev http://www.freeswitch.org
_______________________________________________ Freeswitch-dev mailing list Freeswitch-dev@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-dev UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-dev http://www.freeswitch.org
_______________________________________________ Freeswitch-dev mailing list Freeswitch-dev@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-dev UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-dev http://www.freeswitch.org
participants (4)
-
Brian West
-
Johny Kadarisman
-
Michael Collins
-
Scott Shen