Meetme Volume Control

All installation and configuration problems and questions

Moderators: gerski, enjay, williamconley, Op3r, Staydog, gardo, mflorell, MJCoate, mcargile, Kumba, Michael_N

Meetme Volume Control

Postby saif.rahman » Tue Apr 07, 2009 2:43 pm

By clicking on volume up/down link from the agent screen which extensions should be in extensions.conf to work that properly ?
saif.rahman
 
Posts: 24
Joined: Fri Jan 30, 2009 7:00 pm

Postby saif.rahman » Tue Apr 07, 2009 3:36 pm

Able to do by going to "show conference call channel information" link on the agent screen.
But cant able to control volume from the volume control buttons which are on the front screen of agent.

when i do that the following notice occurs on the CLI

chan_local.c:526 local_alloc: No such extension/context XXYYXXYYXXYYXX38600074@default creating local channel
saif.rahman
 
Posts: 24
Joined: Fri Jan 30, 2009 7:00 pm

Postby mflorell » Tue Apr 07, 2009 5:14 pm

Asterisk version?

astguiclient version?
mflorell
Site Admin
 
Posts: 18339
Joined: Wed Jun 07, 2006 2:45 pm
Location: Florida

Postby saif.rahman » Wed Apr 08, 2009 12:47 pm

Asterisk Version 1.2.30.2

Astguiclient VERSION: 2.2.0-176
BUILD: 90322-1105
saif.rahman
 
Posts: 24
Joined: Fri Jan 30, 2009 7:00 pm

Postby mflorell » Wed Apr 08, 2009 4:36 pm

Does this happen when you try to raise, lower and mute/unmute or just one of these?
mflorell
Site Admin
 
Posts: 18339
Joined: Wed Jun 07, 2006 2:45 pm
Location: Florida

Postby saif.rahman » Thu Apr 09, 2009 10:56 am

it happens when i try to raise or lower the volume.

The reason why i want to try this feature because every time we do three way conference call after minute or so the both, i.e. customer and third party cant able to hear each other at all and if i increase the volume for the agent side the voice goes more break up. (It also happens when there is only one agent logged into vicidial).
saif.rahman
 
Posts: 24
Joined: Fri Jan 30, 2009 7:00 pm

Postby mflorell » Thu Apr 09, 2009 2:14 pm

So muting and unmuting works fine?
mflorell
Site Admin
 
Posts: 18339
Joined: Wed Jun 07, 2006 2:45 pm
Location: Florida

Postby saif.rahman » Thu Apr 09, 2009 3:39 pm

yes
saif.rahman
 
Posts: 24
Joined: Fri Jan 30, 2009 7:00 pm

Postby mflorell » Fri Apr 10, 2009 6:23 am

Can you post the action_full.DATE logfile entries of this happening?

After I receive your response I will try to replicate this on our test servers.
mflorell
Site Admin
 
Posts: 18339
Joined: Wed Jun 07, 2006 2:45 pm
Location: Florida

Postby saif.rahman » Fri Apr 10, 2009 9:57 am

2009-04-09 15:57:05|750|0|1|
Action: Originate
Channel: SIP/0013
Context: default
Exten: 8600051
Priority: 1
Callerid: "S0904091557058600051" <0000000000>

|
2009-04-09 15:57:08|751|0|1|
Action: Hangup
Channel: SIP/0013-08756540

|
2009-04-09 15:57:08|752|0|1|
Action: Originate
Channel: Local/55558600051@default
Context: default
Exten: 8300
Priority: 1
Callerid: ULGH34581239307028

|
2009-04-09 15:57:09|750|1||Response: Error
Message: Originate failed

|
2009-04-09 15:57:12|750|2||Response: Goodbye
Message: Thanks for all the fish.

|
2009-04-09 15:57:12|751|1||Response: Success
Message: Channel Hungup

|
2009-04-09 15:57:12|752|1||Response: Error
Message: Originate failed

|
2009-04-09 15:57:15|751|2||Response: Goodbye
Message: Thanks for all the fish.

|
2009-04-09 15:57:15|752|2||Response: Goodbye
Message: Thanks for all the fish.
saif.rahman
 
Posts: 24
Joined: Fri Jan 30, 2009 7:00 pm

Postby mflorell » Fri Apr 10, 2009 7:48 pm

That's a bit much on the logs there. I'll try to duplicate the problem on a fresh install of 2.0.5.
mflorell
Site Admin
 
Posts: 18339
Joined: Wed Jun 07, 2006 2:45 pm
Location: Florida

Postby mflorell » Sat Apr 11, 2009 6:44 am

I truncated your output a bit because most of it was just repeating the same thing.

Does this happen to you on inbound or autodial calls or only on Manual dial calls?

I can repeat this on my test system but only with Manual dial calls. The reason that this occurs is that Manual dial calls are placed as local calls with the flag set to not resolve the Local/ channel handler so that you can hang up the channel during ringtime, otherwise you would not be able to hang up calls until their either picked up or timed out. The agent screen keeps track of the real channel pointer so taht the call can be hungup and transferred properly, but technically the real channel pointer is not in the meetme conference which is why the main volume controls don't work, but the "calls in this conference" volume controls all do work.

Not sure if there's a good fix for this or not, a temporary fix might be to just disable the main volume controls on the main agent screen if the agent placed a Manual dial call.
mflorell
Site Admin
 
Posts: 18339
Joined: Wed Jun 07, 2006 2:45 pm
Location: Florida

Postby saif.rahman » Mon Apr 13, 2009 1:15 pm

Thanks for the detailed input on that. its really make sense. but Matt what about the three way conference call issue i.e. the customer and the third party when connected after some time the agent can hear both of them properly but those two cant hear each other.
saif.rahman
 
Posts: 24
Joined: Fri Jan 30, 2009 7:00 pm

Postby mflorell » Mon Apr 13, 2009 3:43 pm

Not sure about that one, haven't heard of that happening before. What kind of time frame does that happen across?
mflorell
Site Admin
 
Posts: 18339
Joined: Wed Jun 07, 2006 2:45 pm
Location: Florida

Postby saif.rahman » Tue Apr 14, 2009 12:53 am

it happen when there are 20 -30 agents logged into vicidial having dial level set to 3.
saif.rahman
 
Posts: 24
Joined: Fri Jan 30, 2009 7:00 pm


Return to Support

Who is online

Users browsing this forum: No registered users and 239 guests