Jump to content
Vodia PBX forum

All Activity

This stream auto-updates     

  1. Today
  2. Yesterday
  3. this worked many thanks for the fast help
  4. The above setting should be on the /reg_pnp_settings.htm page of the Admin level PBX GUI.
  5. When you provision the phone for the first time, it sets the address for the PBX - including the port number. If you change the port number, well, it will become unavailable. What you can do is to keep the old port open (e.g. use "8080 80" in the HTTP port settings). You can change the templates from the web interface (/reg_texts.htm): You can do this on system, domain and extension level. But usually you don't have to do that, just set the general parameter for the phones (reg_pnpparm.htm). When you change buttons the PBX automatically sends a re-provision request to the phone. You can manually trigger that by going to the registration tab for the extension (dom_ext3.htm) and there click on the re-provision or the reboot button for the registration.
  6. Hi, I'm on vodia V63 with debian 9.9. I found a bug in the provisioning. If you change http or https port from standard port 80 or 443 provisioning stop to working correctly. In my case i provisioned a Snom 710 with standard port 80. Then i change http port to 8090. Deleted mac address bid to extension, reset the phone. This result in provisioning fault. Restoring port http 80 all start to working good. I think this is a possible bug. Then I install new clean PBX: i do same test changing http port to 8090 directly before provisioning: same result: provisioning fail. This is my fisrt problem. Second problem is that i need to modify standard provisioning template to change phone standard beahaviour for some parameters. Were are located in a linux debian environment .xml provisioning files ? I search in all folders under usr/local/pbx without result. Last question is about reprovisioning phones. I cannot find command to send reprovisioning command in case we need to change BLF or bottoms. Thank you in advance Matteo
  7. What you could try to do is to set the "Label template for private lines" from "{user} {name}" to "", so that the label sent to the phone is empty:
  8. Last week
  9. We're currently testing the new Snom D385 phone with LCD button labels. When assigning the phone buttons we noticed that the "private line" feature of the phone does not work as expected: If you assign a private line to a button using the phone web interface itself and you do not provide a custom label the button is automatically labeled with "Private line", as soon as you're using this line the label in the button display changed to the remote party number (or name) so that you can see which call is on each line (really cool feature due to the LCD labels). If you configure the private line through the Vodia provisioning we can either assign a custom label for the private line, which is always displayed or the PBX automatically assigns the label "extension number: last name, first name" but it's impossible to configure an unlabeled button so that the phone will label it with the current remote party. Could you please provide the possibility to provision "private line" buttons without any label so the button LCD can show the current remote party?
  10. Yes if you want you can try the 63.0.2 build available for CentOS64 and Debian64.
  11. Did you set the country code for the domain, so that the PBX can automatically convert the numbers into the same format?
  12. Hi there, just checking in if there was any progress with this
  13. 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.
  14. 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
  15. 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.
  16. 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.
  17. Next training will be in Texas - if you like we can share the slides with you.
  18. Earlier
  19. 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.
  20. @Vodia PBX - is there any other information i can supply that may help?
  21. 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!
  22. I sent the licence info to your Zendesk on Monday. Received no answer so far.
  23. 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.
  24. Used Vernon's recommendation and it worked perfectly.
  25. 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.
  26. Do you have a frame so that we can say exactly where the problem is?
  27. 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.
  28. No that won't work either. If the call is forwarded out, then it considers it released, and will accept new calls.
  1. Load more activity

  • Who's Online (See full list)

    There are no registered users currently online

  • Create New...