Project

General

Profile

Forums » GOautodial Help »

SoftPhone HANGS up when Agent Clicks on HANG UP in the screen

Added by gm.cust3 gm.cust3 over 12 years ago

GoautoDial 2.1
No extra Hardware
-------------------------

SoftPhone HANGS up when Agent Clicks on HANG UP in the screen

Cant make out why its happening ?

My server got 2 Lan Cards , One for WAN and Another for LAN.

I use Xlite and also Tried Eyebeam but same issues.

COLORED HANG UP BUTTON ON THE LEFT SIDE OF THE AGENT SCREEN.

After they press Hang Up, call in Eyebeam gets hang up also and agent gets into the pause mode.

One change which I did was I delete the Phone Entries which gets created by default and made the as cc101 and etc ..

Can that be the reason ?

Also I noticed 2 things :

1) When I make a manual call and Click on Hang Up, SoftPhone DOESN'T get Hang Up.

2) When I am the Only person on the dialer as an agent, and when I am on Pause Mode and Dial a MANUAL CALL, I see in CLI dialing few numbers .. How come ? It shld have dialed Only 1 number ?


Replies (7)

RE: SoftPhone HANGS up when Agent Clicks on HANG UP in the screen - Added by gm.cust3 gm.cust3 over 12 years ago

When I try with the base Install , It works perfectly.

But when I delete 8001 and etc Phones and add cc01 and etc, it give me the above issues.

RE: SoftPhone HANGS up when Agent Clicks on HANG UP in the screen - Added by Demian Biscocho over 12 years ago

We can't recreate your issues. We're using different SIP/IAX phone entries. Have you double checked your configurations?

RE: SoftPhone HANGS up when Agent Clicks on HANG UP in the screen - Added by gm.cust3 gm.cust3 over 12 years ago

If $volumecontrol_active = '1'; changed to $volumecontrol_active = '0'; , issue pops In

RE: SoftPhone HANGS up when Agent Clicks on HANG UP in the screen - Added by Demian Biscocho over 12 years ago

Can you reproduce this in the default Vicidial agent UI?

RE: SoftPhone HANGS up when Agent Clicks on HANG UP in the screen - Added by Demian Biscocho over 12 years ago

This might be a Vicidial bug. Have you reported this to their issue tracker?

    (1-7/7)     Go to top