Moises Silva [Fri, 16 Aug 2013 21:39:18 +0000 (17:39 -0400)]
Improvements to mod_bert
* Added BERT stats channel variables
* Check if the channel is going down when out of sync to avoid flagging it
as out of sync, if the channel is going down it is expected to have some errors
Moises Silva [Mon, 5 Aug 2013 05:30:44 +0000 (01:30 -0400)]
Improvements to mod_bert
* Calculate sampling error rate over a time window
* Create the following variables to control bert testing behavior:
bert_timeout_ms - Milliseconds to wait for bert sync before timing out
bert_window_ms - Window of time to calculate sampling error rate percentage
bert_max_err - Max percentage of error tolerated before going out of sync
bert_hangup_on_error - Hangup when error occurs (Timeout or going out of sync)
Mike Jerris [Mon, 8 Sep 2014 19:35:47 +0000 (14:35 -0500)]
Merge pull request #38 in FS/freeswitch from ~ALEXDG/freeswitch-event-for-gateway-ping:master to master
* commit '388e9638de7c14e00272777245dacc87cf09fc1c':
F-5946 add the patches. if in the sofia gateway config the param pin-monitoring is true, then every ping result raise an sofia::gateway-state event
Seven Du [Sun, 7 Sep 2014 03:45:12 +0000 (11:45 +0800)]
fix incorrect string termination
if read multi times when waiting for a slow client, then bytes is much shorter than datalen
so it could incorrectly terminate the string and data could be lost
Mike Jerris [Thu, 4 Sep 2014 19:34:24 +0000 (14:34 -0500)]
Merge pull request #34 in FS/freeswitch from ~RTRELEAVEN/fs-6773:fs-6773 to master
* commit 'a159b58790cf980df375faa5a55fb713faf257c5':
fix missing "/" in path
add support for cache directory make configs use specific directory variables instead of just base_dir so that one configuration can be used for fhs and legacy installations
In `sofia status gateway ...` let's show the uptime in seconds rather
than in microseconds. We'll output the uptime in microseconds in
`xmlstatus` and we'll label it as such.
What if the hash were destroyed by one thread holding the lock while
another thread was waiting for the lock? The waiting thread would
have already checked that the hash was non-null and would proceed on
that assumption after acquiring the lock.
With this commit we check only after acquiring the lock.
add support for cache directory
make configs use specific directory variables instead of just base_dir
so that one configuration can be used for fhs and legacy installations
Travis Cross [Thu, 28 Aug 2014 13:29:23 +0000 (13:29 +0000)]
Check gcc support for -Wno-unused-result
We're using -Wno-unused-result to work around what is arguably a GCC
bug, but this option is not supported on older GCC versions. So on
those versions we won't pass -Werror either.
Travis Cross [Thu, 28 Aug 2014 12:24:44 +0000 (12:24 +0000)]
Avoid overaggressive chmod/chown on upgrade
It's reasonable for someone to change one or more of these directory
permissions after installation. We shouldn't touch more than we need
on upgrade. Each directory needs to be owned by the freeswitch user,
but past that we can leave discretion to the system administrator.
Travis Cross [Thu, 28 Aug 2014 01:40:36 +0000 (01:40 +0000)]
Lower log level of limit increases and releases
In some configurations where many limits are used, the limit increases
and releases were generating a lot of noise and making it harder to
see when limits were exceeded, which was at the same log level.
Travis Cross [Wed, 27 Aug 2014 23:10:54 +0000 (23:10 +0000)]
Remove misleading `tport` example from configs
As an example of using mod_sofia's gateway parameter `contact-params`
we'd used the value `tport=tcp`. Looking around, it's clear this has
misled people into believing you can specify `tport=tcp` to make the
gateway use TCP or `tport=tls` to make the gateway use TLS. This does
not work.
The actual contact parameter is named `transport` rather than `tport`,
and you shouldn't use `transport` in `contact-params` because we
automatically add a `transport` to the Contact: based on the value of
`register-transport` (even if the gateway is set to not register).
It's clear why this would be confusing, so we'll just remove this as
an example.
Travis Cross [Tue, 26 Aug 2014 18:41:01 +0000 (18:41 +0000)]
Avoid output of junk text by fs_cli
In some cases where `redisplay()` is called immediately after a
command is run (e.g. `log ...`) we often get a prompt, junk output,
and a second prompt. This is due to a (known) race.
We believe we're falling afoul of this code in `el_deletestr`:
if (el->el_line.cursor < &el->el_line.buffer[n])
return;
Basing the length of text to delete off of the cursor position
resolves the issue of junk text, but the real solution is to eliminate
the race conditions, which will also resolve the sometimes duplicated
prompt.