April 2016 - freeswitch-dev@lists.freeswitch.org

[Freeswitch-dev] Call center module config caching with xml curl
by Nicholas Tunstall 16 May '16

16 May '16

We're currently using the call center and xml curl modules to pull the xml config on every inbound call. We've encountered an issue where if a queue had already been called once freeswitch won't make another call to grab the queue config via curl. The problem we have is if the queue members/strategies etc get changed we have no way to cleanly get the call center module to update it's internal database/memory copy. I've tested this using both the default callcenter.db and odbc database types, does anyone know a clean way to force the module to pull the config on each call? Thanks -- Join us: Twitter <http://twitter.com/entanet/> (@Entanet) | Facebook <http://www.facebook.com/entanet/> (Entanet) | LinkedIn <http://www.linkedin.com/company/entanet-international-ltd> (Entanet International Ltd) http://www.enta.net Please do not place this in your spam folder. Please also select 'Not Spam' if this mail is in your spam folder to avoid any delay or emails getting blocked. This e-mail and any attachments transmitted with it, including replies and forwarded copies subsequently transmitted, contains information which may be confidential and which may also be legally privileged. The content of this e-mail is for the exclusive use of the individual(s) or entity named above, if you are not the intended recipient, please note that any form of distribution, copying or use of this e-mail or the information in it is strictly prohibited and may be unlawful. If you have received this e-mail in error please reply to the sender at Entanet International Ltd and then delete the e-mail immediately. The views expressed within this message are those of the author, not those of Entanet International Ltd, unless endorsed by a Director. Entanet International Ltd is registered in England and Wales, registered no 3274237, and its registered office is Stafford Park 6, Telford, Shropshire, TF3 3AT. Registered VAT number GB 184 5136 01.

2 1

[Freeswitch-dev] Fwd: Call Center - Memory Leak
by Mersed Kahrimanovic 25 Apr '16

25 Apr '16

Hello, We have implemented call center using a freeswitch as switch for handling calls. It is basically the logic where you have an agents within the queue waiting for an contacts to come in, or contact within the queue waiting if there is no any agents available. For this kind of implementation we used pure lua and hash tables (and not mod_fifo) in order to have a better flexibility and possibility to manage different contact/agent states. Everything was working fine on our old servers, now we are migrating to the cloud and we are using aws for that purpose, of course trying to cut some costs. --------------- After initial setup of our solution we found out that there is a memory leak causing for freeswitch to consume 3 - 10 MB per minute during production hours. (we did not notice anything on old servers because we had like 24 cores and 94GB of ram on those). This is not too much of course but the bottom point is that increase is linear and its constantly raising consuming more and more of RAM. In order to isolate an issue and to conclude that we don't have an issue within our solution I installed 1.6.7 version of freeswitch and setup really simple call center with mod_fifo without anything else (totally independent from call center we are working on) For the reference: *Aws:* m4.large vCPU: 2 RAM: 8GB Throughput (Mbps): 450 *Freeswitch version:* 1.6.7 *OS:* Debian GNU/Linux 8 (jessie) *Number of agents:* 30 *Number of calls per agent:* 1 *Total numbers of channels at time:* 60 *Agents simulated with:* pjsip(http://www.pjsip.org/) *Contact simulated with:* sipp(http://sipp.sourceforge.net/) *Configuration:* I used configuration which came with installation of freeswitch. The only things i changed is: - default password - internal rtp timeout - rtpip and sip ip Test scenario: 1. Start the freeswitch. 2. Autoload lua script is going to ring all of the internal (agents) and push them to the extension where we had mod_fifo 3. After some time, same autoload script is going to start calling contacts each 800 miliseconds and push them to the extension where we have mod_fifo. 4. mod_fifo will do the rest, bridge agent with the contact and handling the queue properly. As a result we will have 30 agents constantly "talking", and when ever call is dropped we will have agent connected with another. Parameters for the test match that scenario, and we dont have more then 60 - 65 channels open at the time (never). Dialplan for handling mod_fifo http://pastie.org/10812261 Autoload lua script http://pastie.org/10812263 Result http://prnt.sc/awm4ao The results are for 24hrs period, and indeed 24hrs is a lot. We will never have production running more then 12hrs (and daily restart will occur). But this basically means that we are not able to host more then 40-45 agents on servers with 8GB of ram. My question is: Is this something which can be considered as memory leak, or this is simply how freeswitch works, behaves and requirements it have? Thank you, Mersed

3 4

Re: [Freeswitch-dev] Fwd: Call Center - Memory Leak
by Customer Care 25 Apr '16

25 Apr '16

Thank you for contacting Alaska Airlines. If you experienced a recent delayed or canceled flight, thank you for sharing your contact information with our Customer Care Department. We will respond to you shortly. If you are requesting to opt out of future Marketing emails from Alaska Airlines and our Partners, we will update your account accordingly. If you wish to change this at any time please call the Mileage Plan Office directly at 1-800-654-5669. For all other questions or for other assistance, please visit our website at alaskaair.com/contactus.

1 0

Re: [Freeswitch-dev] Fwd: Call Center - Memory Leak
by Customer Care 25 Apr '16

25 Apr '16

Thank you for contacting Alaska Airlines. If you experienced a recent delayed or canceled flight, thank you for sharing your contact information with our Customer Care Department. We will respond to you shortly. If you are requesting to opt out of future Marketing emails from Alaska Airlines and our Partners, we will update your account accordingly. If you wish to change this at any time please call the Mileage Plan Office directly at 1-800-654-5669. For all other questions or for other assistance, please visit our website at alaskaair.com/contactus.

1 0