V20 Dep. Admin can't select SBC when adding phone

Status
Not open for further replies.

Rick-Arcus-IT

Platinum Partner
Advanced Certified
Joined
Jun 25, 2020
Messages
153
Reaction score
64
Hello,

We gave one of our end users some extra rights, Department Admin. This company is using an SBC. When this admin creates a new user and wants to add a phone to that user, he can't select the 'Connect via SBC/Router phone' option, only the Local LAN option. Does this have something to do with the rights? When I check the 3CX Access role rights table (https://www.3cx.com/docs/manual/access-roles/), the department admin should have rights to Voice & chat (Trunks, WhatsApp, Facebook, Live Chat & SBC).

Kind regards,

Rick
 
Voice and chat panel has a header for Department, I wonder if the SBC has to be assigned to the dept but i cant see how
 
Last edited:
That's what I also thought, but when I open the SBC in trunks, I don't have an option to assign it to an department.
 
Looks like system admin gives access to SBC
 
Yes but also access to the sip trunks, and that's not something we would like our end users to have access to.
 
Hello @Rick-Arcus-IT

As mentioned by@Alphabetic, the SBC is not assigned to the Department and that is why you do not get the option to connect via SBC/router phone.
The System Owner and The System Administrator roles are system-wide roles as mentioned in our guide User Access Roles Explained.

The Department Administrator can only see the departments that he is part of ( this includes also SBC/Router Phones)
You can add the department admin to the main/default group and then you will be able to see the system-wide SBCs and select them.

You cannot change the department of the SBC. If you navigate to the Voice and Chat with the System Owner or System Admin roles you can see where all the SBC/Router phones are assigned.
 
  • Like
Reactions: Charles_3CX
Hello @Rick-Arcus-IT

As mentioned by@Alphabetic, the SBC is not assigned to the Department and that is why you do not get the option to connect via SBC/router phone.
The System Owner and The System Administrator roles are system-wide roles as mentioned in our guide User Access Roles Explained.

The Department Administrator can only see the departments that he is part of ( this includes also SBC/Router Phones)
You can add the department admin to the main/default group and then you will be able to see the system-wide SBCs and select them.

You cannot change the department of the SBC. If you navigate to the Voice and Chat with the System Owner or System Admin roles you can see where all the SBC/Router phones are assigned.
Thanks for you reply Dimitri. The department admin is added to the default group, this customer doesn't have any extra departments, but it looks like the SBC is not in any group, or is it system-wide? If I reinstall the SBC, could I then add it to a department?

edit: I just checked, adding another SBC doesn't give me the option to assign it to a department.
 

Attachments

  • trunks.png
    trunks.png
    37 KB · Views: 18
If it's not possible to assign an SBC to a department, then that's no problem. Then we will add the phones to the PBX on blank users and explain the enduser to reassign the extentions to users when he needs them. The phones would then automagically provision.
 
  • Like
Reactions: Alphabetic
You cannot directly assign a department to an SBC/Router Phone.
If you add an SBC with a user that is a department admin to Department A ( for example ), then the SBC will be part of Department A.
If you create an SBC with system-wide roles ( System Owner or System Administrator ) then the SBC will be system-wide.
 
  • Like
Reactions: Rick-Arcus-IT
You cannot directly assign a department to an SBC/Router Phone.
If you add an SBC with a user that is a department admin to Department A ( for example ), then the SBC will be part of Department A.
If you create an SBC with system-wide roles ( System Owner or System Administrator ) then the SBC will be system-wide.
That explains it, thank you! Then if I understand correctly, system-wide doesn't mean that it's available in the default department? Because otherwise the department admin in the default department would see the SBC? Please correct me if i'm wrong.
 
Last edited:
That is correct.
System-wide means that only the roles that have system-wide access can see them.
 
  • Like
Reactions: Rick-Arcus-IT
Alright, thanks for the explanation!
 
That is correct.
System-wide means that only the roles that have system-wide access can see them.
And this also mean that nobody can change a user, even the name exept the system-wide acces role. All other roles see a red flag on the IP Phone setting that are no routing phone available is.
 
  • Like
Reactions: Davdi and Phil-STIC
Hello,
We're having a little trouble with this.

As @Energa pointed out, when a department owner wants to make changes to an extension whose phone is associated with an SBC created by a system owner, the changes are not possible since the SBC is not visible to them.

If I understand correctly, we have to recreate the SBC, being the owner of its department, so that it can make changes to the extensions assigned to this SBC?

This is annoying because we have hundreds of SBCs in this situation, and we don't have remote access to most of them.

Will a future update correct this problem?
 
I would also like to know if this will be fixed in a future update. When we prepare 3CX systems, we obviously do this as the system owner. It's easy to forget that you have to create the SBC as separate user with department admin rights, instead of the system owner, otherwise the end-user with dep. admin rights would not be able to provision phones for their users.
It would be amazing if it's possible to change the default department an SBC is a member of. This was we can assign the SBC to a department (most of our PBX's are 1 department systems), so that the end-user can use the SBC option when provisioning. I'll create a feature request for this.
 
  • Like
Reactions: Lars Kruse
  • Like
Reactions: Lars Kruse
And this also mean that nobody can change a user, even the name exept the system-wide acces role. All other roles see a red flag on the IP Phone setting that are no routing phone available is.
I am assuming this is a bug that will get fixed? Is there a feature request or bug report on this aspect of the issue?
 
I am assuming this is a bug that will get fixed? Is there a feature request or bug report on this aspect of the issue?
Yes it's 2 messages up. But this will be fixed in update 3.
 
Status
Not open for further replies.

Forum statistics

Threads
111,954
Messages
589,921
Members
164,852
Latest member
priya