I am writing this to let you know that this behavior
persists in the 1.0.4pre9.
Could the calls/sec issue be due to the single threaded nature of Sofia?
Because I am getting the feeling that the number of simultaneous
channels doesn't really burdens FS, but many Calls/sec does.
Apostolos
Anthony Minessale wrote:
FS uses async rtp timers so you may want to set rtp-timer-name=none in
the profile param to simulate asterisk conditions.
I tried that - although I am not using rtp in my scenario - with the
same results.
Also keep in mind that asterisk as an atvantage in a tiny
In the process of trying to use Freeswitch in a production
environment I conducted a number of performance tests using
various servers. It was then that I noticed some strange behavior
from FS. When I stripped down the scenario I was using to a simple
bridge scenario, I stumbled upon a strange
On Jun 4, 2009, at 9:32 AM, Apostolos Pantsiopoulos wrote:
NOTE No 1 : All the performance recommendations found in the wiki has
been applied. In fact only the essential modules that could make this
scenario work
were loaded.
What are you testing against? What OS, Hardware, Distro and such?
The dialplan :
?xml version=1.0 encoding=utf-8?
!-- http://wiki.freeswitch.org/wiki/Dialplan_XML --
include
context name=mydialplan
extension name=dial1
condition field=destination_number expression=^.*$
You forgot the parens around .*
It should be
Michael Collins wrote:
The dialplan :
?xml version=1.0 encoding=utf-8?
!-- http://wiki.freeswitch.org/wiki/Dialplan_XML --
include
context name=mydialplan
extension name=dial1
condition field=destination_number
FS uses async rtp timers so you may want to set rtp-timer-name=none in the
profile param to simulate asterisk conditions.
Also keep in mind that asterisk as an atvantage in a tiny crappy 32 bit
single cpu box because that was what was popular when it was designed and
the chance for race conditions
