FS-7083 #resolve #comment this should do it. The problem is linked to side-effects from the read thread being delayed by writing to the file handle. It was so much worse on mp3 because the shout encoder blocks while its churning the data and delays it more. This patch adds a dedicated thread for writing to the file and the channel_variable RECORD_USE_THREAD=false will disable it and sync may still be maintained at the cost of dropping more data from the audio signal.
Chris Rienzo [Wed, 17 Dec 2014 19:49:01 +0000 (14:49 -0500)]
FS-7091 #resolve #comment [mod_rayo] Removed unnecessary mutex lock inside input component's cleanup function since the input component won't be cleaned up unless all references have been released. This fixes a deadlock when output component is created at the same time an input component completes.
Moises Silva [Thu, 11 Dec 2014 22:50:30 +0000 (17:50 -0500)]
Add bert stats to mod_bert::lost_sync event
The following values can be read from the event:
sync_lost_percent - Error percentage within the analysis window
sync_lost_count - How many times sync has been lost
cng_count - Counter of confort noise packets
err_samples - Number of samples that did not match the sequence
Merge pull request #127 in FS/freeswitch from ~ITALOROSSI/freeswitch:mod_callcenter-queue-list-count-by-state to master
* commit 'f63f8686bc8da391b3c46b24e10571215c8b377f':
FS-7049 - Documentation for state optional paramenter in callcenter_config queue list and count
fix FS-7049 - Count and list agents based on their state
FS-7015 #resolve #comment The code was not properly catching the 0.0.0.0 after changing it to work with ICE SDPs because it was looking in the wrong place for the 0.0.0.0
FS-6891 FS-7002 FS-7059 FS-7072 FS-7073 FS-7076 #close #comment All of these bugs are invalidated due to a botched revert -- commit 72c3df5ed39b724590b5266fb31eea090f56dba7 was supposed to revert commit 1b612fecb6e8db11da9b15c5522b87e7b642423d but it only reverted part of it. commit 158c1f23da9263e0c6aacf6a22e0a504c8909e37 from the other day was erroneously created to work around the result of the botched revert so it is reverted. The result of this commit should be to bring it back to effectively properly revert 1b612fecb6e8db11da9b15c5522b87e7b642423d and now you can test and open new bugs if necessary. This includes the segfault in eavesdrop, and any media bug releated reports. Consider working together and only reporting one new bug if you still encounter any more problems and be sure to include details and make sure the jitter buffer is being used.
Mike Jerris [Wed, 10 Dec 2014 15:35:28 +0000 (09:35 -0600)]
Merge pull request #139 in FS/freeswitch from bugfix/FS-6688-notify-message-record-route-tag to master
* commit '5376e82669d2f53d8acd06f49a27949bfbb21fcd':
FS-6688: don't update the contact when the original had fs_path, the new one doesnt, and the contact didn't change. This will fix the normal case of record route from a proxy without breaking normal changing of a contact
Michael Jerris [Thu, 4 Dec 2014 17:34:05 +0000 (12:34 -0500)]
FS-6688: don't update the contact when the original had fs_path, the new one doesnt, and the contact didn't change. This will fix the normal case of record route from a proxy without breaking normal changing of a contact
Mike Jerris [Tue, 9 Dec 2014 17:57:34 +0000 (11:57 -0600)]
Merge pull request #137 in FS/freeswitch from bugfix/FS-7061-add-q-header-param-on-300-responses to master
* commit '21458f85cc4228e54151350dd89c5c87cc3dfef4':
FS-7062: [mod_sofia] on redirect, when uri are passed in without <> with multiple uris, automatically add the q= header param in decending order. This should make 300 Multiple Choices work well with devices that require the q param. If you would like to specify explicit q-values, please use the syntax of redirect where you specify the entire header using the <>
Michael Jerris [Fri, 5 Dec 2014 22:28:48 +0000 (17:28 -0500)]
FS-7062: [mod_sofia] on redirect, when uri are passed in without <> with multiple uris, automatically add the q= header param in decending order. This should make 300 Multiple Choices work well with devices that require the q param. If you would like to specify explicit q-values, please use the syntax of redirect where you specify the entire header using the <>
Paul Arnold [Thu, 4 Dec 2014 22:52:29 +0000 (09:52 +1100)]
FS-7051: Preserve the annexb=no/yes status
As per RFC4856, Annex B mode for G.729 is disabled if the SDP contains a
fmtp parameter annexb=no and enabled if annexb=yes or the annexb parameter
is missing.
When responding to an offer mod_sangoma_codec always returns an answer
without a fmtp parameter. Even in response to a SDP offer which contains
one. This has the effect of responding to a request to disable Annex B
with an answer that only Annex B is supported.
With this change mod_sangoma_codec copies the fmtp parameter from the
offer to the answer fixing the problem.
Hristo Trendev [Tue, 2 Dec 2014 16:08:12 +0000 (17:08 +0100)]
add timezone support to mod_say_{de,es,ja,nl,th,zh}
This is nothing more than a shameless copy/paste from another mod_say
module, which already had timezone support. It simply checks if the
timezone variable is set and if it contains a valid timezone, then this
timezone will be used when announcing times/dates.