Thanks for your quick response !!! I think it's better to have separate process for originate & event listen. But due to my application design issue, i have to stick with same cgi process for originate & event listen. I will check feasibility of separate process in my app design. Incase of any further queries, Please feel free to mail me or contact me on the numbers provided below. Thanks & Regards, Chaitanya Bhatt Software Engineer. Viva Infomedia Pvt. Ltd. 242, Oshiwara Industrial Centre, New Link Road, Opp. Oshiwara Bus Depot, Goregaon West, Mumbai 400104. Direct: +91.22.40310356 Board: +91.22.40310310 Email : chaitanya@vivainfomedia.com Viva Infomedia: Awarded as Best SME (E-Commerce) at CNBC Emerging India Awards 2009 On Thu, Aug 19, 2010 at 2:21 AM, Anthony Minessale < anthony.minessale@gmail.com> wrote:
and make sure the sps is not set too low
On Wed, Aug 18, 2010 at 2:13 PM, Michael Collins <msc@freeswitch.org> wrote:
Comments inline...
On Wed, Aug 18, 2010 at 3:02 AM, Chaitanya Bhatt // Viva <chaitanya@vivainfomedia.com> wrote:
Hey
I am facing problem in making few outbound calls simultaneously. I am executing "api originate" command from perl over ESL. After calling originate ,same perl file listens for CHANNEL_ORIGINATE CHANNEL_ANSWER CHANNEL_HANGUP_COMPLETE events. When perl file receives CHANNEL_HANGUP_COMPLETE event, it get terminates.
I have done this code of originate & hangup listen event in perl cgi.
When
i do 10-20 request (10-20 simultaneous call), at freeswitch only 2-3 calls get serviced. To find out issue when i commented the code of event listen in cgi, i was able to make all 10-20 calls simulateneously.
I wonder if your script isn't able to handle all the events quickly enough?
I have already checked apache configuration & is working well. Now i want to know whether freeswitch has limitation on number of
clients
listening to its events or there is some other issue of ESL.
Using Perl, ESL, and POE I've done upwards of 50-60 simultaneous calls with originate. I used bgapi originate xxxx. It's not the most efficient way but it did work. However, the best way to handle something like this is to have several processes each with a specific purpose: one to send the bgapi originate commands and one to listen for the CHANNEL_XXX events and act accordingly. By having each process do just one thing you can scale better and it's easier to identify trouble spots.
-MC
_______________________________________________ FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
-- Anthony Minessale II
FreeSWITCH http://www.freeswitch.org/ ClueCon http://www.cluecon.com/ Twitter: http://twitter.com/FreeSWITCH_wire
AIM: anthm MSN:anthony_minessale@hotmail.com <MSN%3Aanthony_minessale@hotmail.com> GTALK/JABBER/PAYPAL:anthony.minessale@gmail.com<PAYPAL%3Aanthony.minessale@gmail.com> IRC: irc.freenode.net #freeswitch
FreeSWITCH Developer Conference sip:888@conference.freeswitch.org <sip%3A888@conference.freeswitch.org> googletalk:conf+888@conference.freeswitch.org<googletalk%3Aconf%2B888@conference.freeswitch.org> pstn:+19193869900
_______________________________________________ FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org