GoAutoDial C.E. 2.1 is finally out!

[williamconley]

but then when the buttons start popping up ... the landscape moves around and life gets confusing. clean at the cost of confusing the agents is counterproductive.

might be a nice "option"/"Feature", though. You should request it. Shouldn't be Hard.

[gmcust3]

In Realtime,

STATION
USER
SHOW NAME

Missing Purposely ??

It only shows the session ID.

Why so ?

[maykelsoft]

To view the agent names go into the agent settings (for the user viewing the realtime screen) and set Block Realtime Block User Info to 0... posted by knotbeerdan on the other thread...
http://www.vicidial.org/VICIDIALforum/v ... hp?t=20083

[gmcust3]

User level needs to be more than 6 i.e 7 or 8 or 9 ...

[rtabigue]

Hi,

I applied the patch and my problem solved. agent can now click the dial next however only txt base shown in dial next there is no image. May i know
what's going wrong? please advise

Im using GoAutoDial CE 2.1

[gardo]

Which patch did you apply?

[rtabigue]

This one -> http://goautodial.org/attachments/143/a ... fix.tar.gz

[gardo]

Please check the latest file here:

http://goautodial.org/issues/27

Just untar in /var/www/html/.

[rtabigue]

Thanks Gardo, Its working now..

[williamconley]

but it's not "less" it's "hidden". the real estate still has to be "reserved" so the button has a place to show when the moment comes.

and then when they pop up ... the agent may never notice them. and therefor never use them. bummer.

[stevieo3]

Which patch did you apply?

Hi Gardo

I am having same problem with manual dialing.After dialing the first call the dial next button stays greyed out.I have updated to the latest patch from the goautodial blog but still have the same problem.

[gardo]

Get the latest file here:

http://goautodial.org/issues/27

Untar it to /var/www/html/ and you're good to go.

[stevieo3]

All sorted thanks gardo

[stevieo3]

Get the latest file here:

http://goautodial.org/issues/27

Untar it to /var/www/html/ and you're good to go.

Hi Gardo

I have upgraded to the above patch. I think i may have found a bug. When in manual dial the disposition/wrapup screen only apears after the first call is hung up. Thereafter when calls are hungup the disposition screen does not apear thus calls can not be dispositioned.

[stevieo3]

Anyone any solution to the issue of the disposition screen not showing after calls are hung up .It's causing me alot of hassle .Thanks in advance

[akthilak98]

[Jan 11 19:16:06] == Parsing '/etc/asterisk/manager.conf': [Jan 11 19:16:06] Found
[Jan 11 19:16:06] == Manager 'sendcron' logged on from 127.0.0.1
[Jan 11 19:16:06] == Manager 'sendcron' logged off from 127.0.0.1
[Jan 11 19:17:01] == Parsing '/etc/asterisk/manager.conf': [Jan 11 19:17:01] Found
[Jan 11 19:17:01] == Manager 'sendcron' logged on from 127.0.0.1
[Jan 11 19:17:01] == Parsing '/etc/asterisk/manager.conf': [Jan 11 19:17:01] Found
[Jan 11 19:17:01] == Manager 'sendcron' logged on from 127.0.0.1
[Jan 11 19:17:01] == Manager 'sendcron' logged off from 127.0.0.1
[Jan 11 19:17:03] == Manager 'sendcron' logged off from 127.0.0.1
[Jan 11 19:17:06] == Parsing '/etc/asterisk/manager.conf': [Jan 11 19:17:06] Found
[Jan 11 19:17:06] == Manager 'sendcron' logged on from 127.0.0.1
[Jan 11 19:17:06] == Manager 'sendcron' logged off from 127.0.0.1
[Jan 11 19:17:06] -- Executing [918884081695@default:1] AGI("SIP/8001-00000016", "agi://127.0.0.1:4577/call_log") in new stack
[Jan 11 19:17:06] -- AGI Script agi://127.0.0.1:4577/call_log completed, returning 0
[Jan 11 19:17:06] -- Executing [918884081695@default:2] Dial("SIP/8001-00000016", "&{SIPTata}/0018884081695||To") in new stack
[Jan 11 19:17:06] WARNING[16828]: app_dial.c:1228 dial_exec_full: Dial argument takes format (technology/[device:]number1)
[Jan 11 19:17:06] == Spawn extension (default, 918884081695, 2) exited non-zero on 'SIP/8001-00000016'
[Jan 11 19:17:06] -- Executing [h@default:1] DeadAGI("SIP/8001-00000016", "agi://127.0.0.1:4577/call_log--HVcauses--PRI-----NODEBUG-----0-----INVALIDARGS----------") in new stack
[Jan 11 19:17:06] -- AGI Script agi://127.0.0.1:4577/call_log--HVcauses ... ---------- completed, returning 0
[Jan 11 19:18:01] == Parsing '/etc/asterisk/manager.conf': [Jan 11 19:18:01] Found
[Jan 11 19:18:01] == Manager 'sendcron' logged on from 127.0.0.1
[Jan 11 19:18:01] == Manager 'sendcron' logged off from 127.0.0.1
[Jan 11 19:18:01] == Parsing '/etc/asterisk/manager.conf': [Jan 11 19:18:01] Found
[Jan 11 19:18:01] == Manager 'sendcron' logged on from 127.0.0.1
[Jan 11 19:18:03] == Manager 'sendcron' logged off from 127.0.0.1
[Jan 11 19:18:06] == Parsing '/etc/asterisk/manager.conf': [Jan 11 19:18:06] Found



Can any one Help me on this

[williamconley]

[Jan 11 19:16:06] == Parsing '/etc/asterisk/manager.conf': [Jan 11 19:16:06] Found
[Jan 11 19:16:06] == Manager 'sendcron' logged on from 127.0.0.1

[Jan 11 19:18:01] == Manager 'sendcron' logged off from 127.0.0.1
[Jan 11 19:18:01] == Parsing '/etc/asterisk/manager.conf': [Jan 11 19:18:01] Found
[Jan 11 19:18:01] == Manager 'sendcron' logged on from 127.0.0.1
[Jan 11 19:18:03] == Manager 'sendcron' logged off from 127.0.0.1
[Jan 11 19:18:06] == Parsing '/etc/asterisk/manager.conf': [Jan 11 19:18:06] Found



Can any one Help me on this

sure. after you post it in a separate post instead of tacking it on to the end of a non-related post. also:

when you post, please post your entire configuration including (but not limited to) your installation method and vicidial version with build.

this IS a requirement for posting along with reading the stickies (at the top of each forum) and the manager's manual (available on EFLO.net, both free and paid versions)

You should also post: Asterisk version, telephony hardware (model number is helpful here), cluster information if you have one, and whether any other software is installed in the box. If your installation method is "from scratch" you must post your operating system and should also post the .iso version from which you installed your original operating system.

If this is a "Cloud" or "Virtual" server, please note the technology involved along with the version of that techology (ie: VMware Server Version 2.0.2). If it is not, merely stating the Motherboard model # and CPU would be helpful.

Similar to This:

Vicibox X.X from .iso | Vicidial X.X.X-XXX Build XXXXXX-XXXX | Asterisk X.X.X | Single Server | No Digium/Sangoma Hardware | No Extra Software After Installation | Intel DG35EC | Core2Quad Q6600

The BEST piece of advice I can give you: Read the Vicidial Manager's Manual. It's available on EFLO.net. Start at page one and skip NOTHING. Tell us where you bump into your first problem. (Page and line number) and we'll walk you through it on Your Own Post.

[dcxm]

Hi

Is there an order to apply the patches? or do I have to just use the last one: agent-UI.goCE.11032011.tar.gz

Thanks in advance!!

[williamconley]

Hi

Is there an order to apply the patches? or do I have to just use the last one: agent-UI.goCE.11032011.tar.gz

Thanks in advance!!

Perhaps you should open a new thread with a subject line other than "GoAutoDial C.E. 2.1 is finally out!" which is not (IMHO) indicative of your subject.

[dcxm]

William

As I read in this post all the comments about the patches bugs and fixes, I thought this was the best place to post the question.

[williamconley]

didja notice that there hadn't been a post in 10 months? generally that's a sign that it's a dead thread. and the "subject" of the thread is not related to bugs/patches/fixes ...

[ctc_olsen]

Anyone any solution to the issue of the disposition screen not showing after calls are hung up .It's causing me alot of hassle .Thanks in advance

Just to contribute. Another work around is to use INBOUND_MAN instead of Manual Dial. I was about to run the patch but I figured I tried to try things out first and it did work. Just disable inbound if you don't want those calls coming in.

[harbirjaswal]

Hi,
I am totally new in this ...I have extracted the agent-UI fix in the given path in goautodial....But I dont know the procedure how to patch it....I am executing the command patch -p0 -i vicidial.agent-UI.fix.patch as written in readme file in root but it prompts no such file found....Can u plz help me as how and where will i run this command to patch the file....Thanks n adv....

[williamconley]

Sorry, I'd love to help but we don't use goautodial, we use Vicibox instead. So we've never patched one. However: What filename(s) are in the "fix" you downloaded? if one of them was similar to vicidial.agent-UI.fix.patch ... it could be what you are looking for. (We do have a few clients who use Goautodial, just because it was simpler to install in the old days than Vicibox).

Ordinarily we just recommend you upgrade to the latest Vicidial (for which goautodial is merely in installer) and step away from the Goautodial distro entirely (yes, you can upgrade in place from the Vicidial version that was installed by your goautodial cd to the latest vicidial ...). You will then use the Stock vicidial agent and manager pages instead of the "pretty" (but old, and buggy) goautodial modified versions. And your "web links" in the admin pages will once again be blue and underlined so you can know what to click on. LOL.

Plus you get the new QC module and the new Email module.

But I digress: Here are a few hints for working with Vicidial itself and these forums:

when you post, please post your entire configuration including (but not limited to) your installation method and vicidial version with build.

this IS a requirement for posting along with reading the stickies (at the top of each forum) and the manager's manual (available on EFLO.net, both free and paid versions)

You should also post: Asterisk version, telephony hardware (model number is helpful here), cluster information if you have one, and whether any other software is installed in the box. If your installation method is "from scratch" you must post your operating system and should also post the .iso version from which you installed your original operating system. If your installation is "Hosted" list the site name of the host.

If this is a "Cloud" or "Virtual" server, please note the technology involved along with the version of that techology (ie: VMware Server Version 2.0.2). If it is not, merely stating the Motherboard model # and CPU would be helpful.

Similar to This:

Vicibox X.X from .iso | Vicidial X.X.X-XXX Build XXXXXX-XXXX | Asterisk X.X.X | Single Server | No Digium/Sangoma Hardware | No Extra Software After Installation | Intel DG35EC | Core2Quad Q6600

If you are feeling curious, check out "Vicibox.com". You can back up your database, install vicibox, restore your previous database and then upgrade just the database and have all your data in a fresh brand new Vicidial server with the latest code.