Page 1 of 1

Volume Control in a clustered Setup

PostPosted: Tue Jun 26, 2012 8:50 am
by ronator
hello there,

I'd like to know if it is possible to have the volume control on the agent page working in a clustered setup without opening the "Show conference calls"-links. After some tests I found out that the volume control (in the main agent panel) only works if the agent is logged in on the same server where the call came in. On the other hand, the "mute"-button seems to work fine.

If I use the "show conferences" link, it works as expected, but I consider it as somehow dangerous to have agents using that link, because they could accidently click on the hangup-link or get confused, on which line they should use the volume control due to the fact that they can see their own session. Some Agents are easily confuseable :roll:

Is it possible to get the standard volume control in the main panel running in a clustered setup ? What changes might be necessary ? Or do I just have to upgrade (which would be no option for me) ?

Thank You.

###################
ViciBox Redux v.3.0.6
AstGuiClient: 2.2.1-237
BUILD: 100510-2015

Re: Volume Control in a clustered Setup

PostPosted: Wed Jun 27, 2012 7:57 am
by ronator
if I missed something, you could correct me or gimme a hint !

Re: Volume Control in a clustered Setup

PostPosted: Mon Jul 02, 2012 9:47 am
by ronator
So it seems to me this might be a limitation nobody wants to talk about. what a pity.

Re: Volume Control in a clustered Setup

PostPosted: Tue Jul 03, 2012 6:37 am
by DomeDan
Hehe, I'm sure everyone want that to work but the ones familiar with cluster setups might be on vacation.
I didn't find anything about volume control in the svn-log after 100510-2015, but you could try this in a test-environment with the latest version from trunk and see if it works,
If its not working then you can post a request in the issue-tracker

Re: Volume Control in a clustered Setup

PostPosted: Thu Jul 12, 2012 10:18 am
by ronator
Dear DomeDan,

thank you for answering. I assume waiting for the return of those cluster specialists is an option to me. If I'd had the time to install the newest svn-code in a test environment, I would already have done so, but as you might know: Admins ain't got no time for anything *g

But actually thank you for your suggestion - I was really wondering why my post was "ignored", since I used to get answer really quick in here - although I got GMT +1 over here ;-)