[Freeswitch-users] FreeSWITCH-users Digest, Vol 80, Issue 70

Sun Feb 10 19:27:52 MSK 2013

Hi Jun,

There is a member-flag called endconf which does what you want. However,
I'm not sure how to specify that as part of "conference dial"...

Regards,
Martyn

On 10 February 2013 11:54, <freeswitch-users-request at lists.freeswitch.org>wrote:

> Send FreeSWITCH-users mailing list submissions to
>         freeswitch-users at lists.freeswitch.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
>         http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
> or, via email, send a message with subject or body 'help' to
>         freeswitch-users-request at lists.freeswitch.org
>
> You can reach the person managing the list at
>         freeswitch-users-owner at lists.freeswitch.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of FreeSWITCH-users digest..."
>
> Today's Topics:
>
>    1. how to end conference after initiator hangs up    (dialout
>       style) (Jun Sun)
>    2. Re: High Availability Cluster Module for  FreeSWITCH (Gilad Abada)
>    3. Re: High Availability Cluster Module for  FreeSWITCH (Eliot Gable)
>    4. USSD support for mod_gsmopen (Yuriy Ostapchuk)
>    5. Re: VoIP gateway with PRI (Yehavi Bourvine)
>    6. Re: USSD support for mod_gsmopen (Giovanni Maruzzelli)
>    7. Re: High Availability Cluster Module for  FreeSWITCH
>       (Marcin Gozdalik)
>
>
> ---------- Forwarded message ----------
> From: Jun Sun <jsun at junsun.net>
> To: freeswitch-users at lists.freeswitch.org
> Cc:
> Date: Sat, 09 Feb 2013 14:52:15 -0800
> Subject: [Freeswitch-users] how to end conference after initiator hangs up
> (dialout style)
>
> I have set up a conferencing call node using dialout style. That is, I use
> the following commands to bridge everyone into a conference:
>
> conference $myRoom dial sofia/internal/$myNumber at x.x.**x.x:5060 $myNumber
> conference_test";
> conference $myRoom dial sofia/internal/$theirNumber1@**x.x.x.x:5060
> $myNumber conference_test";
> conference $myRoom dial sofia/internal/$theirNumber2@**x.x.x.x:5060
> $myNumber conference_test";
> ...
>
> Right now things are working fine except for one thing. I like to end the
> conference (i.e., all legs are disconnected) when the initiator ($myNumber)
> hangs up. But it is not doing that (understandably so!).
>
> How can I achieve that?
>
> I searched around and it seems most conf call controls only apply to
> dial-in style conference calls.
>
> Thanks for any pointers!
>
> Jun
>
>
>
>
> ---------- Forwarded message ----------
> From: Gilad Abada <ga at steadfasttelecom.com>
> To: FreeSWITCH Users Help <freeswitch-users at lists.freeswitch.org>
> Cc:
> Date: Sat, 9 Feb 2013 18:49:56 -0500
> Subject: Re: [Freeswitch-users] High Availability Cluster Module for
> FreeSWITCH
> Hey Eliot
>
> Sounds exciting. Which DB will you be using Postgres? I will try to
> get my company to pitch in a few dollars.
>
> Sent from my mobile device.
>
> On Feb 9, 2013, at 12:11 PM, Eliot Gable <egable+freeswitch at gmail.com>
> wrote:
>
> > For the past two years, I have been working on and off on a high
> > availability cluster module for FreeSWITCH. If you would like to see
> > HA built into FreeSWITCH directly, instead of dealing with Pacemaker +
> > Corosync or other 3rd party systems, please check out the module,
> > voice your support, provide feedback and suggestions, and consider
> > supporting it.
> >
> > Some advantages over a 3rd party solution like Pacemaker include:
> >
> > - Sub-second failure detection and response (meaning it can start
> > recovering calls less than a second after a failure occurs)
> > - Failure detection is built into FreeSWITCH so it can detect
> > conditions which 3rd party modules cannot detect
> > - One shared configuration file between all nodes (no per-node IP
> > configuration required)
> > - No fixed number of nodes
> > - Graceful migration of calls with a maintenance mode (requires DNS)
> >
> > These are just some of the benefits of building a FreeSWITCH-specific
> > HA system. For additional details about the project, please visit:
> >
> > http://wiki.freeswitch.org/wiki/Mod_ha_cluster
> >
> >
> > If you would like to see this project come to fruition, please
> > consider financially supporting it through Kickstarter:
> >
> >
> http://www.kickstarter.com/projects/1175121367/high-availability-cluster-module-for-freeswitch
> >
> >
> >
> > Thanks in advance for anyone who contributes, either with just a
> > shout-out, with feedback and/or suggestions, and especially to those
> > who pledge some financial support.
> >
> > --
> > Eliot Gable
> >
> > _________________________________________________________________________
> > Professional FreeSWITCH Consulting Services:
> > consulting at freeswitch.org
> > http://www.freeswitchsolutions.com
> >
> > 
> > 
> >
> > Official FreeSWITCH Sites
> > http://www.freeswitch.org
> > http://wiki.freeswitch.org
> > http://www.cluecon.com
> >
> > 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
>
>
>
>
> ---------- Forwarded message ----------
> From: Eliot Gable <egable+freeswitch at gmail.com>
> To: FreeSWITCH Users Help <freeswitch-users at lists.freeswitch.org>
> Cc:
> Date: Sat, 9 Feb 2013 23:00:59 -0500
> Subject: Re: [Freeswitch-users] High Availability Cluster Module for
> FreeSWITCH
> The beauty of the module is that it will not require any 3rd party
> software to operate. I am designing it to run entirely in-memory using
> multi-cast events to communicate between cluster nodes. No external
> database will be required to enable the automatic fail over and call
> recovery.
>
> If you have your customers / clients using DNS to point traffic to
> your system and you run multiple master nodes with DNS performing load
> balancing, you can also make use of the maintenance mode I have
> planned which will use a separate IP address and update your DNS
> records to remove the master which you put into maintenance mode and
> put in the maintenance IP which is assigned to the slave node which is
> being promoted as master. This allows calls to drain off the master
> while new calls come up on the slave, and then you can gracefully shut
> down the master when all calls are finished. Once you are done with
> maintenance, you simply bring it back online and it comes up as a
> slave or a master as needed (according to your configured master /
> slave ratio). The IP which it was using as a master node becomes the
> new designated maintenance IP. This is the only case where a 3rd party
> software package is required, and it is an optional feature.
>
>
> On Sat, Feb 9, 2013 at 6:49 PM, Gilad Abada <ga at steadfasttelecom.com>
> wrote:
> > Hey Eliot
> >
> > Sounds exciting. Which DB will you be using Postgres? I will try to
> > get my company to pitch in a few dollars.
> >
> > Sent from my mobile device.
> >
> > On Feb 9, 2013, at 12:11 PM, Eliot Gable <egable+freeswitch at gmail.com>
> wrote:
> >
> >> For the past two years, I have been working on and off on a high
> >> availability cluster module for FreeSWITCH. If you would like to see
> >> HA built into FreeSWITCH directly, instead of dealing with Pacemaker +
> >> Corosync or other 3rd party systems, please check out the module,
> >> voice your support, provide feedback and suggestions, and consider
> >> supporting it.
> >>
> >> Some advantages over a 3rd party solution like Pacemaker include:
> >>
> >> - Sub-second failure detection and response (meaning it can start
> >> recovering calls less than a second after a failure occurs)
> >> - Failure detection is built into FreeSWITCH so it can detect
> >> conditions which 3rd party modules cannot detect
> >> - One shared configuration file between all nodes (no per-node IP
> >> configuration required)
> >> - No fixed number of nodes
> >> - Graceful migration of calls with a maintenance mode (requires DNS)
> >>
> >> These are just some of the benefits of building a FreeSWITCH-specific
> >> HA system. For additional details about the project, please visit:
> >>
> >> http://wiki.freeswitch.org/wiki/Mod_ha_cluster
> >>
> >>
> >> If you would like to see this project come to fruition, please
> >> consider financially supporting it through Kickstarter:
> >>
> >>
> http://www.kickstarter.com/projects/1175121367/high-availability-cluster-module-for-freeswitch
> >>
> >>
> >>
> >> Thanks in advance for anyone who contributes, either with just a
> >> shout-out, with feedback and/or suggestions, and especially to those
> >> who pledge some financial support.
> >>
>
>
>
>
> ---------- Forwarded message ----------
> From: Yuriy Ostapchuk <yura407 at gmail.com>
> To: freeswitch-users at lists.freeswitch.org
> Cc:
> Date: Sun, 10 Feb 2013 00:10:39 -0500
> Subject: [Freeswitch-users] USSD support for mod_gsmopen
> Hi,
> I've submitted a patch that implements USSD messaging support.
> (useful for checking and refilling account balance and other
> provider-specific usage)
>
> Here is the JIRA ticket:
> http://jira.freeswitch.org/browse/FS-5078
>
> If this feature is considered useful, I would appreciate if it's
> integrated in git.
>
> Thanks,
> Yuriy
>
>
> ---------- Forwarded message ----------
> From: Yehavi Bourvine <yehavi.bourvine at gmail.com>
> To: FreeSWITCH Users Help <freeswitch-users at lists.freeswitch.org>
> Cc:
> Date: Sun, 10 Feb 2013 11:21:25 +0200
> Subject: Re: [Freeswitch-users] VoIP gateway with PRI
> Hi,
>   I just checked with our Audiocodes support, and you can do what you want.
>
> In order to route a call from one PRI to the other, you insert an entry in
> two tables:
> Tel->IP: the destination is localhost.
> IP->Tel - the source is either any or localhost.
>
>                  Regards, __Yehavi:
>
>
> 2013/2/7 Mimiko <vbvbrj at gmail.com>
>
>> Hello.
>>
>> I want to propose for purchasing a VoIP gateway to connect some PRI
>> lines with FS. Basic operation has to be routing like this:
>>
>> One line PRI will be connected to phone provider. Some calls to certain
>> numbers thru this connection must be routed to FS via IP. Other
>> destination numbers must be routed to second PRI connection for legacy
>> PBX for analog phones. So the VoIP gateway must have two PRI (T1/E1)
>> connections and two LAN connection for failover.
>>
>> After a while this VoIP gateway will be as a tehnology converter from IP
>> to PRI. So LAN connectors will be used for connection to FS in a
>> failover manner. And two PRI connectors will be used to connect to
>> legacy PBX which have two PRI inputs to handle 60 concurrent connection.
>>
>> I've spotted three models:
>> 1) Patton SN4951/4E60V2GS/EUI 4T1/E1/PRI 60 VoIP Channels G.SHDSL for
>> $5,000
>>
>> 2) Audiocodes Mediant 1000 M1K-D2 2T1/E1 for  $3,800
>>
>> 3) Sangoma Vega 400 2 T1/E1 Digital Gateway for $4,437
>>
>> Which of this is a better working solution with failover and extended
>> call routing plans?
>>
>> Thansk.
>>
>> --
>> Mimiko desu.
>>
>> _________________________________________________________________________
>> Professional FreeSWITCH Consulting Services:
>> consulting at freeswitch.org
>> http://www.freeswitchsolutions.com
>>
>> 
>> 
>>
>> Official FreeSWITCH Sites
>> http://www.freeswitch.org
>> http://wiki.freeswitch.org
>> http://www.cluecon.com
>>
>> 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
>>
>
>
>
> ---------- Forwarded message ----------
> From: Giovanni Maruzzelli <gmaruzz at gmail.com>
> To: FreeSWITCH Users Help <freeswitch-users at lists.freeswitch.org>
> Cc:
> Date: Sun, 10 Feb 2013 12:36:28 +0100
> Subject: Re: [Freeswitch-users] USSD support for mod_gsmopen
>
> On Sun, Feb 10, 2013 at 6:10 AM, Yuriy Ostapchuk <yura407 at gmail.com> wrot
>
>> Hi,
>> I've submitted a patch that implements USSD messaging support.
>> (useful for checking and refilling account balance and other
>> provider-specific usage)
>>
>>
>> Here is the JIRA ticket:
>> http://jira.freeswitch.org/browse/FS-5078
>>
>> If this feature is considered useful, I would appreciate if it's
>> integrated in git.
>>
>
> Thanks Yuriy, I'll have a look into it asap next week.
>
> Thanks again, yes is considered useful and grateful received.
>
> -giovanni
>
>
> --
> Sincerely,
>
> Giovanni Maruzzelli
> Cell : +39-347-2665618
>
>
> ---------- Forwarded message ----------
> From: Marcin Gozdalik <gozdal at gmail.com>
> To: FreeSWITCH Users Help <freeswitch-users at lists.freeswitch.org>
> Cc:
> Date: Sun, 10 Feb 2013 12:54:12 +0100
> Subject: Re: [Freeswitch-users] High Availability Cluster Module for
> FreeSWITCH
> I wonder how do you handle network partition? Simply "knowing" which nodes
> are up in a distributed system is hard enough and there is a reason why
> solutions like pacemaker/corosync have years of development behind them.
>
> W dniu niedziela, 10 lutego 2013 użytkownik Eliot Gable napisał:
>
>> The beauty of the module is that it will not require any 3rd party
>> software to operate. I am designing it to run entirely in-memory using
>> multi-cast events to communicate between cluster nodes. No external
>> database will be required to enable the automatic fail over and call
>> recovery.
>>
>> If you have your customers / clients using DNS to point traffic to
>> your system and you run multiple master nodes with DNS performing load
>> balancing, you can also make use of the maintenance mode I have
>> planned which will use a separate IP address and update your DNS
>> records to remove the master which you put into maintenance mode and
>> put in the maintenance IP which is assigned to the slave node which is
>> being promoted as master. This allows calls to drain off the master
>> while new calls come up on the slave, and then you can gracefully shut
>> down the master when all calls are finished. Once you are done with
>> maintenance, you simply bring it back online and it comes up as a
>> slave or a master as needed (according to your configured master /
>> slave ratio). The IP which it was using as a master node becomes the
>> new designated maintenance IP. This is the only case where a 3rd party
>> software package is required, and it is an optional feature.
>>
>>
>> On Sat, Feb 9, 2013 at 6:49 PM, Gilad Abada <ga at steadfasttelecom.com>
>> wrote:
>> > Hey Eliot
>> >
>> > Sounds exciting. Which DB will you be using Postgres? I will try to
>> > get my company to pitch in a few dollars.
>> >
>> > Sent from my mobile device.
>> >
>> > On Feb 9, 2013, at 12:11 PM, Eliot Gable <egable+freeswitch at gmail.com>
>> wrote:
>> >
>> >> For the past two years, I have been working on and off on a high
>> >> availability cluster module for FreeSWITCH. If you would like to see
>> >> HA built into FreeSWITCH directly, instead of dealing with Pacemaker +
>> >> Corosync or other 3rd party systems, please check out the module,
>> >> voice your support, provide feedback and suggestions, and consider
>> >> supporting it.
>> >>
>> >> Some advantages over a 3rd party solution like Pacemaker include:
>> >>
>> >> - Sub-second failure detection and response (meaning it can start
>> >> recovering calls less than a second after a failure occurs)
>> >> - Failure detection is built into FreeSWITCH so it can detect
>> >> conditions which 3rd party modules cannot detect
>> >> - One shared configuration file between all nodes (no per-node IP
>> >> configuration required)
>> >> - No fixed number of nodes
>> >> - Graceful migration of calls with a maintenance mode (requires DNS)
>> >>
>> >> These are just some of the benefits of building a FreeSWITCH-specific
>> >> HA system. For additional details about the project, please visit:
>> >>
>> >> http://wiki.freeswitch.org/wiki/Mod_ha_cluster
>> >>
>> >>
>> >> If you would like to see this project come to fruition, please
>> >> consider financially supporting it through Kickstarter:
>> >>
>> >>
>> http://www.kickstarter.com/projects/1175121367/high-availability-cluster-module-for-freeswitch
>> >>
>> >>
>> >>
>> >> Thanks in advance for anyone who contributes, either with just a
>> >> shout-out, with feedback and/or suggestions, and especially to those
>> >> who pledge some financial support.
>> >>
>>
>> _________________________________________________________________________
>> Professional FreeSWITCH Consulting Services:
>> consulting at freeswitch.org
>> http://www.freeswitchsolutions.com
>>
>> 
>> 
>>
>> Official FreeSWITCH Sites
>> http://www.freeswitch.org
>> http://wiki.freeswitch.org
>> http://www.cluecon.com
>>
>> 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
>>
>
>
> --
> Marcin Gozdalik
>
> _______________________________________________
> 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
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.freeswitch.org/pipermail/freeswitch-users/attachments/20130210/e8c6aff3/attachment-0001.html 