Support
-
Posts
1,000 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Posts posted by Support
-
-
For that the queue manager will always have to be logged in into the User portal > ACD > ACD of his choice.
And from there it's just a process as shown here: https://doc.vodia.com/wac
-
62.0 or lower.
-
If you're on the older user portal then you should be able to drag and drop the call as a queue manager.
-
Try: 192.168.1.0/255.255.0.0/192.168.1.28 0.0.0.0/0.0.0.0/public
Make sure your private network and subnet that you gave are correct ( we based our reply on that)
-
It's Debian64, but shouldn't make a difference though.
-
We replicated your agent group's setting here and everything is still the same. It works for us.
We tried both 20 and 30 secs.
You're sure you're not redirecting any of your extensions right?
-
37 minutes ago, chrispopp said:
it doesn't seem to follow the ring durations. It's at exactly 30 seconds intervals.
So we retry this at every 30 secs now ? Instead of 20 or 361 secs that you mentioned earlier?
-
You mentioned that you saw this happen every 20 secs to we let it ring for 40 something secs.
Fine, we'll make it ring longer this time. And then try to pick the call.
We have both Snom's here.
-
Can you tell us where exactly are you seeing the number of calls being increased?
Because we tried with your setup and ours too, but we couldn't reproduce the issue on 64.0.
The number of calls was always 1 on both the agents and in active calls list. And when we picked up either of the phones up, it stopped ringing.
Maybe there's a redirection involved in your scenario?
-
If you're unable to accomplish this, please create a ticket on vodia.zammad.com and give us the following details:
1. Your admin login to your PBX.
2. Name of the domain having issues.
3. Name of the domain where your trunk is.
4. Name of the trunk.
5. Number to dial to test to replicate this issue. -
Hi,
This would be a process of trail and error as every trunk has different requirements. If you can go through this webpage https://doc.vodia.com/trunk_custom_headers and https://doc.vodia.com/trunk_ani, it will give you multiple options of how you would like the call to be represented.
Also your trunk provider might need those settings in the "Remote party ID" or "P-Preferred-Identity" etc. section which will also have to be tried out.
If you're unable to accomplish this, please create a ticket on vodia.zammad.com with all the admin level login, domain name, trunk (name and where can we find it on the PBX domain) details and we can take a look.
-
This needs to be placed there: http://portal.vodia.com/downloads/pbx/version-63.1.xml
-
-
Not sure how the update ink would corrupt your system. It will either go through or it won't.
Please let us know from the webclient Admin level 9 logs what error is it giving you when upgrading fails.
-
-
Which version of the PBX are you on? Because on the latest version (63.1) we've made the PBX lot smarter about this.
-
It will require a PBX update as well.
-
Hi,
Apologies for the late reply. It is Vodia's web-server that we've developed.
-
20 hours ago, Vodia PBX said:
You need to make sure that the PBX actually reads from the file system in the system settings (reg_ports.htm - Read content for global and domain files).
If you've done the above, then your path should be:
/usr/local/pbx/generated/<domain_name>
-
3 hours ago, Scott1234 said:
When using the call back feature if the agent hangs up the call first and or does not let the menu play out to the 'press #' to check the rest of the list the system will keep calling back even if there is no more calls in the list. Can it not just assume the operation as being closed if no further calls are in the list no matter who hangs up?
We can look into that further.
3 hours ago, Scott1234 said:Also, at the moment when a call back operation happens the caller ID comes up as *55xx(xx = agent group number) and wont present any group name identification.
Would the Agents not remember from the AG number being dialed, which agent that call back belongs to? Having the name feature does help make it clearer, but AG number should be fine too no?
-
The default one is /usr/local/pbx
-
Hi,
What do you mean the template path? If you mean customized files then you can just add them from the GUI itself.
Wouldn't that work for you?
-
That might be the reason we came up with 63.0.5 with those and many other settings along with it.
Please always be on the latest to get the most out of our system.
-
You mean the MAC?
Transfer Agent Group Call
in Agent Group Setup
Posted
OK, we should've added this with our point that, this cannot be done, if there are no agents logged onto the ACD.
Other option that can be done is by using "explicitly specify pick up preference" inside the external extensions. These extensions can just press *87 and pick up the AG calls and queue manager cannot do anything about it (those extensions have to be proactive about it).
OR
In the AG itself you can assign the call to to go to selected extensions if the call has rang more than XX secs.