search for: 12db

....1/xlator/mgmt/glusterd.so(+0x26edf) [0x7f9b8d19eedf] -->/usr/lib/x86_64-linux-gnu/glusterfs/10.1/xlator/mgmt/glusterd.so(+0xcdad2) [0x7f9b8d245ad2] -->/usr/lib/x86_64-linux-gnu/glusterfs/10.1/xlator/mgmt/glusterd.so(+0xcc525) [0x7f9b8d244525] ) 0-management: Lock for gfs_vms held by a410159b-12db-4cf7-bad5-c5c817679d1b glusterd.log:[2023-06-01 02:22:04.133256 +0000] W [glusterd-locks.c:545:glusterd_mgmt_v3_lock] (-->/usr/lib/x86_64-linux-gnu/glusterfs/10.1/xlator/mgmt/glusterd.so(+0x26edf) [0x7f9b8d19eedf] -->/usr/lib/x86_64-linux-gnu/glusterfs/10.1/xlator/mgmt/glusterd.so(+0xcdad2)...

....1/xlator/mgmt/glusterd.so(+0x26edf) [0x7f9b8d19eedf] -->/usr/lib/x86_64-linux-gnu/glusterfs/10.1/xlator/mgmt/glusterd.so(+0xcdad2) [0x7f9b8d245ad2] -->/usr/lib/x86_64-linux-gnu/glusterfs/10.1/xlator/mgmt/glusterd.so(+0xcc525) [0x7f9b8d244525] ) 0-management: Lock for gfs_vms held by a410159b-12db-4cf7-bad5-c5c817679d1b glusterd.log:[2023-06-01 02:22:04.133256 +0000] W [glusterd-locks.c:545:glusterd_mgmt_v3_lock] (-->/usr/lib/x86_64-linux-gnu/glusterfs/10.1/xlator/mgmt/glusterd.so(+0x26edf) [0x7f9b8d19eedf] -->/usr/lib/x86_64-linux-gnu/glusterfs/10.1/xlator/mgmt/glusterd.so(+0xcdad2)...

....1/xlator/mgmt/glusterd.so(+0x26edf) [0x7f9b8d19eedf] -->/usr/lib/x86_64-linux-gnu/glusterfs/10.1/xlator/mgmt/glusterd.so(+0xcdad2) [0x7f9b8d245ad2] -->/usr/lib/x86_64-linux-gnu/glusterfs/10.1/xlator/mgmt/glusterd.so(+0xcc525) [0x7f9b8d244525] ) 0-management: Lock for gfs_vms held by a410159b-12db-4cf7-bad5-c5c817679d1b glusterd.log:[2023-06-01 02:22:04.133256 +0000] W [glusterd-locks.c:545:glusterd_mgmt_v3_lock] (-->/usr/lib/x86_64-linux-gnu/glusterfs/10.1/xlator/mgmt/glusterd.so(+0x26edf) [0x7f9b8d19eedf] -->/usr/lib/x86_64-linux-gnu/glusterfs/10.1/xlator/mgmt/glusterd.so(+0xcdad2) [...

....1/xlator/mgmt/glusterd.so(+0x26edf) [0x7f9b8d19eedf] -->/usr/lib/x86_64-linux-gnu/glusterfs/10.1/xlator/mgmt/glusterd.so(+0xcdad2) [0x7f9b8d245ad2] -->/usr/lib/x86_64-linux-gnu/glusterfs/10.1/xlator/mgmt/glusterd.so(+0xcc525) [0x7f9b8d244525] ) 0-management: Lock for gfs_vms held by a410159b-12db-4cf7-bad5-c5c817679d1b > glusterd.log:[2023-06-01 02:22:04.133256 +0000] W [glusterd-locks.c:545:glusterd_mgmt_v3_lock] (-->/usr/lib/x86_64-linux-gnu/glusterfs/10.1/xlator/mgmt/glusterd.so(+0x26edf) [0x7f9b8d19eedf] -->/usr/lib/x86_64-linux-gnu/glusterfs/10.1/xlator/mgmt/glusterd.so(+0xcda...

...26edf) > [0x7f9b8d19eedf] > -->/usr/lib/x86_64-linux-gnu/glusterfs/10.1/xlator/mgmt/glusterd.so(+0xcdad2) > [0x7f9b8d245ad2] > -->/usr/lib/x86_64-linux-gnu/glusterfs/10.1/xlator/mgmt/glusterd.so(+0xcc525) > [0x7f9b8d244525] ) 0-management: Lock for gfs_vms held by > a410159b-12db-4cf7-bad5-c5c817679d1b > glusterd.log:[2023-06-01 02:22:04.133256 +0000] W > [glusterd-locks.c:545:glusterd_mgmt_v3_lock] > (-->/usr/lib/x86_64-linux-gnu/glusterfs/10.1/xlator/mgmt/glusterd.so(+0x26edf) > [0x7f9b8d19eedf] > -->/usr/lib/x86_64-linux-gnu/glusterfs/10.1/xlator/mgm...

...26edf) > [0x7f9b8d19eedf] > -->/usr/lib/x86_64-linux-gnu/glusterfs/10.1/xlator/mgmt/glusterd.so(+0xcdad2) > [0x7f9b8d245ad2] > -->/usr/lib/x86_64-linux-gnu/glusterfs/10.1/xlator/mgmt/glusterd.so(+0xcc525) > [0x7f9b8d244525] ) 0-management: Lock for gfs_vms held by > a410159b-12db-4cf7-bad5-c5c817679d1b > > glusterd.log:[2023-06-01 02:22:04.133256 +0000] W > [glusterd-locks.c:545:glusterd_mgmt_v3_lock] > (-->/usr/lib/x86_64-linux-gnu/glusterfs/10.1/xlator/mgmt/glusterd.so(+0x26edf) > [0x7f9b8d19eedf] > -->/usr/lib/x86_64-linux-gnu/glusterfs/10.1/xlato...

...d19eedf] >> -->/usr/lib/x86_64-linux-gnu/glusterfs/10.1/xlator/mgmt/glusterd.so(+0xcdad2) >> [0x7f9b8d245ad2] >> -->/usr/lib/x86_64-linux-gnu/glusterfs/10.1/xlator/mgmt/glusterd.so(+0xcc525) >> [0x7f9b8d244525] ) 0-management: Lock for gfs_vms held by >> a410159b-12db-4cf7-bad5-c5c817679d1b >> > glusterd.log:[2023-06-01 02:22:04.133256 +0000] W >> [glusterd-locks.c:545:glusterd_mgmt_v3_lock] >> (-->/usr/lib/x86_64-linux-gnu/glusterfs/10.1/xlator/mgmt/glusterd.so(+0x26edf) >> [0x7f9b8d19eedf] >> -->/usr/lib/x86_64-linux-gnu/...

...df] -->/usr/lib/x86_64-linux-gnu/glusterfs/10.1/xlator/ > mgmt/glusterd.so(+0xcdad2) [0x7f9b8d245ad2] -->/usr/lib/ > x86_64-linux-gnu/glusterfs/10.1/xlator/mgmt/glusterd.so(+0xcc525) > [0x7f9b8d244525] ) 0-management: Lock for gfs_vms held by > a410159b-12db-4cf7-bad5-c5c817679d1b > > glusterd.log:[2023-06-01 02:22:04.133256 +0000] W > [glusterd-locks.c:545:glusterd_mgmt_v3_lock] (-->/usr/lib/ > x86_64-linux-gnu/glusterfs/10.1/xlator/mgmt/glusterd.so(+0x26edf) > [0x7f9b8d19eedf] -->/usr/lib/x86_64-linux-...

...ly be heard. By adding the proposed voicemail=6.0 statement to the appropriate channel, any calls connected to voicemail via that channel would effectively increase transmission levels by 6db (or whatever the setting happened to be). In this example case, the setting would increase the vm volume by 12db (or about 24db measured in the above). Anyone have any thoughts on this? Rich

.../0dB (65 steps) pcm0: +- ctl 3 (nid 4 out): -64/0dB (65 steps) pcm0: +- ctl 15 (nid 12 in 0): mute pcm0: +- ctl 17 (nid 13 in 0): mute pcm0: +- ctl 19 (nid 14 in 0): mute pcm0: pcm0: Microphone Volume (OSS: mic): 0/30dB pcm0: | pcm0: +- ctl 6 (nid 11 in 0): -34/12dB (32 steps) + mute pcm0: +- ctl 25 (nid 24 out): 0/30dB (4 steps) pcm0: +- ctl 31 (nid 34 in 0): mute pcm0: +- ctl 41 (nid 35 in 0): mute pcm0: pcm0: Line-in Volume (OSS: line): -34/12dB pcm0: | pcm0: +- ctl 8 (nid 11 in 2): -34/12dB (32 steps) + mute pcm0: +- ctl 33...

Hello, I've read in a thread from this mailing list ( http://lists.xiph.org/pipermail/vorbis-dev/2009-September/020019.html) that the usage of FLOOR1_fromdB_LOOKUP table is to convert Floor1 values from a dB scale to a linear scale. In a dB scale, given a reference value, the other dB values are obtained from it, normally dB_value = 10log(p1/p0), where p0 is the reference value. Supposing p0

...# 33a0 <_DYNAMIC+0x10c0> >> 12cc: 0f 1f 40 00 nopl 0x0(%rax) >> >> 00000000000012d0 <foo at plt>: >> 12d0: ff 25 d2 20 00 00 jmpq *0x20d2(%rip) # 33a8 <foo+0x20f3> >> 12d6: 68 00 00 00 00 pushq $0x0 >> 12db: e9 e0 ff ff ff jmpq 12c0 <foo+0xb> >> >> >> Thus the call to foo now goes through the PLT. >> >>> There is no such a need for a new option. These desired characteristics can be achieved with existing mechanisms. >> >> $ ld.lld-10 --Bs...

...to the > > >appropriate channel, any calls connected to voicemail via that > > >channel would effectively increase transmission levels by 6db (or > > >whatever the setting happened to be). In this example case, the > > >setting would increase the vm volume by 12db (or about 24db measured > > >in the above). > > > > > >Anyone have any thoughts on this? > > > > > >Rich > > > > Rich - > > I'll say that this would be very useful. Regardless of where the > > loss is being inserted, i...

Hi there, We have plans to install an office (not call center) with the following setup: 200 linksys 942 phones (sip + g711) on a LAN a server with a dual port E1 sangoma and a remora card with 4 fxo modules. So far when we want to setup a linksys phone, we need to use the http interface of each phone, disable/enable a lot of things and plug it into the network. this is not the best scenario for