Jump to content
Vodia PBX forum


  • Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

1 Follower

About voltier

  • Rank
    Advanced Member

Profile Information

  • Gender

Recent Profile Visitors

4,514 profile views
  1. Hi Vodia, just to be clear I’m referring to Auto Attendants. I wouldn’t think DMTF is the issue here as User Inputs 1-9 function as intended. Not sure if # is classified as special characters or not
  2. As per title, the system isn’t doing anything with # and I’m suspecting it’s waiting for a command for something else perhaps. Anybody encounter this?
  3. voltier


    Yes thats correct. Mongo call it DNS seedlist connection string - for the purposes of quickly scaling out a cluster without needing to configure individual clients
  4. voltier


    Has anybody had any luck connecting to Mongodb's atlas service? I dont think the connection string from the admin console allows for SRV (which im suspecting is the issue)
  5. I can confirm 63.0.2 fixed the issue. Thank you for the support!
  6. Hi there, just checking in if there was any progress with this
  7. @Vodia PBX - is there any other information i can supply that may help?
  8. 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.
  9. 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?
  10. We have been caught out multiple times when there is a sudden change in the CDR file structure, where it breaks out data ingestion because there are new variables that need to be declared. Can Admins please ensure this information is made available in the Release Notes 'Please'.
  11. voltier


    Hi there - we are wanting to provide an interface on our own portal which will allow the end customer to add/delete/manage the Address Book. Will there be any plans to have Address Book via your API?
  12. Hi Support - any update on this? (Pick up group) I still cant see any documentation and would really like to test this
  13. Hi Devs/Admin, With the release of 57.0, can you point us in the right direction in terms of how to use some of these features. I found Pickup Group under buttons but it isnt exactly intuitive to figure out how to use. Same thing with the Call Back function within ACD. Possibly if you can provide a sample tied to a scenario, that would be great.
  14. Anybody know how long is it before the session key times out or expires?
  15. The construct for DMTF elements is horrible IMHO. Is it possible to have the array represented in the same way as extensionlegs or trunklegs?
  • Create New...