Does anyone have experience with presence on FreeSWITCH when under load? We've considered offloading presence to a Kamailio proxy but it would great if we could understand the limitations of presence on FreeSWITCH and recommended configuration for best performance under load.
We've been experiencing issues with presence (BLF) intermittently not working or being delayed by 5 minutes or more. The BLF lights may show an extension as available when they're on the phone, as ringing when they're available etc. This problem can only be re-produced on a system which has been under load but it doesn't occur immediately unless the system has been running for a couple of weeks. This effects multiple SIP profiles in a multi-tenant (multi domain) environment with roughly 800 registrations, 500 registrations on one SIP profile and 300 on another.
The FreeSWITCH DB files use a 512MB RAM disk and we've balanced extensions across multiple SIP profiles using separate (not shared) DB files to distribute load.
What we've noticed is the internal DB files (i.e. sofia_reg_internal.db) appear to increase exponentially over time after roughly 22MB we often start to run into problems with presence while the system is under load, restarting FreeSWITCH and flushing the internal DB files clears the problem.
Interestingly we didn't have this problem on FreeSWITCH 1.4
We've recently adjusted the following settings on our internal SIP profiles and are continuing to monitor:
force-subscription-expires [900] -> [1800]
sip-subscription-max-deviation [300] -> [600]
max-proceeding [1000] -> [5000]
initial-event-threads [2] -> [4]
Here is a snippet of our internal SIP profile configuration:
nonce-ttl [60]
outbound-codec-prefs [G722,PCMA,H264]
pass-rfc2833 [true]
record-path [/path/freeswitch/recordings]
record-template [${domain_name}/archive/${strftime(%Y)}/${strftime(%b)}/${strftime(%d)}/${uuid}.${record_ext}]
multiple-registrations [contact]
inbound-reg-force-matching-username [true]
inbound-reg-in-new-thread [true]
initial-event-threads [4]
local-network-acl [localnet.auto]
manage-presence [true]
unregister-on-options-fail [true]
tls-version [tlsv1.2]
tls-cert-dir [/path/freeswitch/certs]
tls-bind-params [transport=tls]
tls [true]
stun-enabled [false]
stun-auto-disable [false]
sip-trace [no]
sip-subscription-max-deviation [600]
sip-port [xxxx]
sip-ip [x.x.x.x]
sip-force-expires [900]
sip-expires-max-deviation [300]
sip-capture [no]
rtp-timeout-sec [0]
rtp-timer-name [soft]
rtp-ip [x.x.x.x]
rtp-hold-timeout-sec [0]
tls-verify-in-subjects []
tls-verify-depth [2]
tls-verify-date [true]
tls-sip-port [xxxx]
tls-passphrase []
tls-only [false]
inbound-codec-prefs [G722,PCMA,H264]
inbound-codec-negotiation [greedy]
log-auth-failures [true]
user-agent-string [FreeSWITCH]
watchdog-enabled [no]
watchdog-event-timeout [30000]
watchdog-step-timeout [30000]
ext-rtp-ip [x.x.x.x]
accept-blind-auth [false]
accept-blind-reg [false]
aggressive-nat-detection [true]
apply-inbound-acl [domains]
apply-nat-acl [nat.auto]
auth-all-packets [false]
auth-calls [true]
challenge-realm [auto_from]
context [public]
debug [0]
dialplan [XML]
dtmf-duration [2000]
dtmf-type [rfc2833]
enable-timer [true]
ext-sip-ip [x.x.x.x]
registration-thread-frequency [240]
rfc2833-pt [101]
force-subscription-expires [1800]
forward-unsolicited-mwi-notify [false]
hold-music [local_stream://default]
nat-options-ping [true]
NDLB-force-rport [safe]
max-proceeding [5000]
______________________________________________________________________
This message has been checked for all known viruses by MessageLabs Virus Scanning Service.
______________________________________________________________________