Messages

1

Outbound and QueueMetrics / Dialout on icon page not working

« on: October 27, 2015, 21:01:49 »

Greetings,

We have at least one agent for whom the Dialout interface on the ICON page does not work. She loggs into an outgoing queue, selects a Campaign from the dropdown in the Dialout windows, types in a valid phone number, presses the green call button and nothing happens. The asterisk logs create the following two lines:

[2015-10-27 14:46:10] NOTICE[22784][C-0002d4d3]: chan_local.c:968 local_call: No such extension/context @from-internal while calling Local channel
[2015-10-27 14:46:10] NOTICE[22784][C-0002d4d3]: channel.c:5694 __ast_request_and_dial: Unable to call channel Local/@from-internal/n

If I log into queuemetrics as myself then login to the same outgoing queue using her extension number as my "Current Extension" I am able to Dialout successfully and her extension rings.

I have tried making her agent and user settings identical to my own, and I have also tried deleting her user and recreating it with no success.

Has anyone else here encountered/solved this issue?

Thank you,
~ardy

2

Running QueueMetrics / Dialer stopped working after update to latest version

« on: May 27, 2015, 20:06:24 »

Hello, I have submitted an email to support regarding this issue though I have yet to receive a response.

Ever since updating to the latest version of Queuemetrics using yum our agents have not been able to dial out using the dialer on the Icon page. While waiting for support to respond I have managed to isolate the issue, however the workaround leaves much to be desired.

Basically, if the agent does not have multiple "Asterisk Aliases" defined they are able to dial out just fine, however if they have more than one asterisk alias, dialing out will not work for them. My workaround has been to limit agents to 1 asterisk alias, however now they are showing up multiple times in the reports. Please address this issue ASAP as we were able to use multiple aliases in previous versions of queuemetrics prior to the most recent update.

Thank you.

3

QueueMetrics installation / Re: Illegal file access: the file is not in the list of allowed files.

« on: June 11, 2014, 04:50:41 »

Thanks again for the excellent solutions (moving forward, fixing the past, and the one-liner for database consistency between past and present), although for whatever reason it wasn't working for me. After some googling I learned of the "from-pstn-e164-us" context which is already written into freepbx, specifically for the purpose of removing the +1. Simply putting your trunks in that context will remove the +1, and the best part about this solution is no need for a shell, it can be done in the GUI.

Alternatively, for those who wish to use your custom context but ran into my problem (the context doesn't stick), they may choose to name the context whatever they wish, and simply place the trunks into that context which they named.

The offices are all closed now, so if I run into any problems tomorrow I'll post once I learn of them, though I don't foresee any issues.

Once again thank you for the excellent writeup, I had been revisiting this annoyance every so often over the past months and was very excited to find this thread.


P.S. From what I gather the reason your method was not working for me may have been, and I'm not sure here, the order of the dial plans in memory. If it matches another dial plan first thats what it will go with.

4

QueueMetrics installation / Re: Illegal file access: the file is not in the list of allowed files.

« on: June 10, 2014, 19:15:15 »

Firstly, thank you Dreaken667 for the excellent writeup, I have been struggling with this for sometime myself and was surprised that Queuemetrics didn't have a solution to offer.

Secondly, I'm afraid I'm still struggling. After adding the proposed dial plan to /etc/asterisk/extensions_custom.conf (I think there may be a typo in the original post, it says to add the dial plan to /etc/asterisk/extension_custom.conf (no s, singular not plural)) and reloading the dial plan, everything remains the same. Watching the logs I can see that the added lines are never executed.

We are using SIP trunks, though from what I gather that should not make a difference, when a call comes in the logs show (DID#)@from-pstn is executed, and based on the messages it is not the dial plan added to extensions_custom.conf.

Do you have any pointers as to what I may be missing?

Thank You,

~ardy