Regarding the SIgnaling Problem , the DB was already on tmpfs and you may have read that this was not an I/O problem.

To load Blance a call is simple in our use case.

First understand we use auto-dialers so alot happens in the backend , the rest we send a originate command so simply change the profile used imagine :

originate sofia/external1_profile/22222222@111.11.11.11 IVR XML

The dialer simply changes
originate sofia/external1_profile/22222222@111.11.11.11 IVR XML
originate sofia/external2_profile/22222222@111.11.11.11 IVR XML
originate sofia/external3_profile/22222222@111.11.11.11 IVR XML
originate sofia/external4_profile/22222222@111.11.11.11 IVR XML

We use INB ESL.

Now if you want to use "softphones" i think you can use mod_limit and the XML dialplan to create a realtime version of this.

Notes :

Keep in mind that i do not know if this is the correct way to handle this situation but we have it deployed  this way and as i was able to increase the call volume by a factor of 2 while at the same time increasing quality and decreasing the signaling issues.
 At the expense of RAM more RAM = Profiles.



2011/5/24 jay binks <jaybinks@gmail.com>
moving your SQLlite DB to tempFS is the biggest single change you can have with FS.
that alone would account for the massive increase in calls you were able to achieve.


On Tue, May 24, 2011 at 9:57 PM, Anton VG <anton.vazir@gmail.com> wrote:
do you mean sqlite?

2011/5/24 Tihomir Culjaga <tculjaga@gmail.com>:
> the only real improvment was to move your DB to tmpfs ... the rest ( if
> 64bit) makes really small difference from distro to distro..
>




--
Sincerely

Jay

_______________________________________________
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