Jump to content

ahennis@voicespring.net

Members
  • Content Count

    233
  • Joined

  • Last visited

Everything posted by ahennis@voicespring.net

  1. The issue I see here is that and extension BLF on v60.x will not pickup a ringing phone if it is in a hunt group or agent group. Older versions were able to do this. To me this simply makes sense, if I want to pickup a ringing phone I should be able to regardless of it being in a hunt group or agent group. Lets use a Snom D725 as an example. I can see this being problematic if all my buttons are used for BLF and I have multiple hunt groups or agent groups. In older versions if an extension was in a hunt group and you had that extension as a BLF on your phone you could pickup the extension
  2. In v60.0.1 when saving a dial plan as global = yes the system indicates that the dial plan has been saved as global but if you go back into the dial plan it shows global = no. The dial plan still saved as global so you can still use it. The problem that can happen is that if you go back into a dial plan that was set to global = yes to make a change it displays a global = no so when you save it it saves as a non-global dial plan. Here I created a dial plan and set it to global = yes and save it. I can see the dial plan globally in all domains. Here I went back in t
  3. In v60.0.1 what does "Fixed" do in the button config?
  4. I noticed in v60.0.1 that your are required to enter both a first and last name for an extension. It seems to me that it would be better to only require one or the other or frankly neither. Often times we give phones functional names rather then a first and last name or the customer only wants to have there first name. Requiring both first and last name prevents this use case. Please consider switching back to the way it was on previous version where you did not need to enter a name.
  5. V60.0.1 on Centos I have noticed that MOH files that are restricted to a single domain are still visible in other domains. I uploaded a MOH to a domain from the menu "Features | Music on Hold" In the System Level under "Customize|Music on hold" it shows that the file is assigned to the domain but the file is still visible in all domains on the system. Music on Hold at the system level
  6. Version 59.0 on Centos. Using Chrome Version 64.0.3282.186 (Official Build) (64-bit) I noticed that when I change "Play announcement tone" to "no" on a page group and save it the system says the change is saved but when I exit the page group and that go back to it the setting reverts to yes. The tone still plays. Would it also be possible to have two setting? One for the tone at the start of the page and one at the end of the page. Seems more versatile to be able to turn them on/off independently of each other. Maybe the drop down can have Yes No Start tone onl
  7. PBX version 59.0. I have some page groups setup that page phones. The phones are Yealink but I think this happens on our Snom phones as well. Can a feature be added like in a hung group to not have the call be flagged as a missed call?
  8. The "model=snom360" tells the system what model the phone is.
  9. I think this is a known issue. I know it is an issue in version 59.0 and do not know if any newer versions fix this problem. The PBX does not know that 80:5E:C0 is the OUI for a Yealink phone so it does not know which RPS to send the MAC address to. You can manually enter the provisioning URL into the phone as you did. I have been logging into the Yealink RPS and manually adding the phone. As far as I know the only solution is to upgrade the PBX to a version that has this bug fixed.
  10. The Yealink conference phone and DECT phones work with version 58.0. I am installing both on a job right now. The conference phone has a different new MAC OUI of 80:5E:C0 where as the phones have OUI 00:15:65. Because of the new OUI for the conference phone the Vodia server will not auto update the Yalink redirection server so you will need to manually add the MAC of the conference phone to the Yealink redirection server until Vodia release an update that fixed this issue. You would also have to manually upgrade the firmware on the conference phone until Vodia releases an update to fix
  11. The blog posting about blocking SPAM, robocalls and anonymous calls using TrueCNAM says it is only available on the hosted platform? http://blog.vodia.com/search?q=spam Does this refer to the hosted platform that Vodia offers or can I use it on my cloud hosted servers?
  12. Please consider making the login page more customizable. Especially getting rid of that huge picture that does not seem to have any real purpose.
  13. I noticed that when I create a button profile for Yealink phones in v59 that the template starts at button 2 rather than 1. Is this by design to have the first button be a line key?
  14. I think there is an option missing from the selection list on the From-header in hunt groups on v59.0. Notice the bottom of the list where the blue selection bar is. There is no text for the last option in the list. Upon examining the HTML you can see that there is no text to display for the last item in the list. <select class="form-control" id="from_header"> <option value="id">Calling-Party</option> <option value="name">Group name</option> <option value="display">Group name (Calling Name)</option> <option value="numb
  15. Can a domain level administrative account be used for calls to the REST API? I know I can use my Super Administrator account or my System Administrator account but can I use a Domain Administrator account?
  16. So turning on the HTTP redirect to HTTPS in the PBX will not cause phones that are provisioning via HTTP to fail?
  17. I understand that the web server on the PBX will send the browser a redirect to HTTPS. The concern is that the phones are requesting their configuration from the PBX using HTTP. I was not sure if turning the PBX feature to redirect HTTP to HTTPS would cause the phones config request to fail.
  18. How does activating the "Redirect to HTTPS" setting effect phone provisioning?
  19. I have to move a domain from an existing server to a new server. All Snom phones. I know I can backup the domain and then restore it on the new server. My question is how does restoring a domain on a new server effect the the Remote Provisioning Service? When the domain is restored does the PBX update the RPS like it does when a Snom phone is added on the provisioning page? Or do I have to delete the MAC addresses from the old server and then put them back in on the new server? I was wondering if there was some sort of best practice?
  20. Is there a list of what is fixed and/or added to version 59.1 and 59.2? I am just curious. Edit: I thought they were released.
  21. I realize that this is not a feature of any current version of Vodia PBX. As I mentioned in my initial post, it was a feature of their old phone system. It would seem to be a useful feature for a future version if it is even possible to do on the Vodia PBX. I have not offered the solution of camp on yet, but will check it out.
  22. One of my customers ask if when calling from internally extension to extension if it was possible to determine if the extension being called is busy. I know we can do this with BLF but they don't have enough buttons for all the phones. They claim their old system did this. The way they explained the feature was that A calls B. B is on the phone. In the display of A there was some kind of visual indication that B was on the phone. Not sure what the old system was but it was an older analog system.
×
×
  • Create New...