Jump to content
Vodia PBX forum

All Activity

This stream auto-updates     

  1. Yesterday
  2. Yes if you want you can try the 63.0.2 build available for CentOS64 and Debian64.
  3. Did you set the country code for the domain, so that the PBX can automatically convert the numbers into the same format?
  4. Hi there, just checking in if there was any progress with this
  5. Last week
  6. Hello, Im having some troubles with cell phone integrations in Vodia (running Version: 63.0.1). When the cellphone 316XXXXXXXX calls the own extension 3188XXXXXXX the PVA should be provided but this is not the case in my system. I checked the trunk, Dialplan, Camp offer, Voicemail and extension settings but I cant find the cause. I also checked the logs when the cellphone calls the extension see below: Attendant: +316XXXXXXXX is calling its own extension 401@ABC.DEF.GHI. Provide PVA Did anyone have the same problem? And fixed it? Hope someone could help me. Best regards, Michael.
  7. Hi team, Just a quick follow up for clarification on this. If the fundamental functionality of this agent group setting has indeed been changed in v63, can we request an additional field so we can add numerous extensions simultaneously as per previous versions. Many thanks
  8. You find that on https://doc.vodia.com/releasenotes - the IOP were produced on a version that did not list the available options yet. The newer version show you right in the update page what is available.
  9. Its clear where the message is being generated, but not clear why there is now a list... It will take a few more days to figure that out.
  10. Next training will be in Texas - if you like we can share the slides with you.
  11. I'm looking through the forums for links to the software versions available for download. However, I cannot seem to find anything except posts of problems with older versions. What site has a list of the current version? Just picked up an IOP and want to get it current.
  12. Earlier
  13. @Vodia PBX - is there any other information i can supply that may help?
  14. Hello... Is there any one out there that has been using this system for a while and is willing to help us learn it? Vodia's documentation is really not all that helpful and I got an email from them saying they didn't have time to do one-off training. They wanted me to fly cross country to attend one of their classes. I don't think the expense is worth it. If you know the system well and are willing to assist. Please reach out. We are based in the USA and would appreciate assistance from another USA Vendor. Thanks!
  15. I sent the licence info to your Zendesk on Monday. Received no answer so far.
  16. Hi there, Just a snippet. 200 is the ACD, 101-107 are the Agents of 200. When the call is connected to one of the Agents, say 102 - we get the following output below, which does not allow us to uniquely identify which Agent has entered the connected state. account":"200","start":"1522280.620","domain":"domain.com","rec":"none","cmc":"","priority":"1","trunk":["Outbound Trunk*"],"extension":["101","102","103","104","105","106","107"],"callstate":"","state":"connected"}]} Pre v60, it will output: (where Agent 102 connected the call) "account":"200","start":"1522220.620","domain":"domain.com","rec":"none","cmc":"","priority":"1","trunk":["Primary Inbound*"],"extension":["102"],"callstate":"","state":"connected"}]} So unless there is a setting on the ACD page which changes this behavior, im not sure what has happened.
  17. Used Vernon's recommendation and it worked perfectly.
  18. The scope would be within the ACD, not on domain level but it would send calls away if there is anybody else in the ACD. Maybe you can elaborate a little bit more on the use case, and then we can take a look what we can do to get as close a possible.
  19. Do you have a frame so that we can say exactly where the problem is?
  20. You can try utilizing the CO lines for a specific trunk, then when it runs out of lines it should prioritize the busy routing you've created for that specific trunk. That way you can keep your attendant without having to use any other accounts.
  21. No that won't work either. If the call is forwarded out, then it considers it released, and will accept new calls.
  22. You can do this in the ACD - there is a setting on how many calls may be in the ACD and then redirect the number. But for the auto attendant there is no such setting.
  23. Hi, Pre-version 60, Websocket data relating to ACDs would allow us to identify which Agent has picked up the call (showing only the Agent that connected to the call) under Call-state. Since the update to version 60+, when an Agent is connected to the Caller, it simply shows ALL logged in Agents (which was not the behaviour previously). Given there have been a substancial number of changes and configuration parameters now available under ACDs, does anybody know if this is simply a bug, or is there a parameter in the ACD group which needs to be turned on/off?
  24. Tried it and it doesn't work. Say you put 2 in the total calls/total calls on trunk. One call is active, the next one gets disconnected.
  25. What kind of license do you have? You can send us the license code in a secure message for us to check.
  26. You can limit the number of calls in the domain settings on system level. Would that work?
  27. How can I call forward to an extension if calls on the trunk are busy. What I'm trying to test is: To only allow one active call per system. For example, someone calls in reaches an auto attendant, the caller presses the key and then the call is forwarded to an external number. The second call that comes in, to go directly to voicemail.
  1. Load more activity


  • Who's Online (See full list)

    There are no registered users currently online

×
×
  • Create New...