control logo launch

 

  • New extensions added using the Bulk Extension tool are not automatically being created with passwords that meet the password security requirements. Extensions added with the single extension add tool do have the more secure passwords.
    • A fix has been implemented

  • It was discovered that custom user roles do not seem to be getting access to the granular permissions they should be.   
    Under the PBX access and integration, we are currently unable to give the custom user role access to Microsoft 365.  
    The box is selected, but it does not show in the custom user's available features. Please see the attached screenshots.  
    • A fix has been implemented

  • I was creating a new role for a customer's phone system in the management portal and I either have found a bug or am doing something wrong. I want to restrict the user of the role from being able to access the button called " Unlock phone system console". I have that check box deselected in the role properties, yet when I log in with a test account with the role assigned, I am able to launch the phone system console.   
    • A fix has been implemented

  • We are getting a new phone system together for a new client. During the provisioning process there is an issue with saving needed options in the Rights tab. I will set what I want and Save, go back to the extension's Rights tab, and the selected options will not be marked off. Refer to pictures included in this ticket.  
    • A fix has been implemented

  • If you copy an existing extension when the system creates the new extension it uses the old PW generation for the passwords, not the new one with the complexity requirements which means the extension is immediately out of compliance and cannot be saved after it has been created.
    • A fix has been implemented

  • Is it possible to get the notes back for each of the instances on the bvoip portal?
    We used to be able to hover over the note and it would show before we clicked into one.
    For example, our instances have generic names and we don’t know which client it’s for until we click on it, the notes helped identify them –
    • A fix has been implemented