Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.



Html
<div id="fb-root"></div>
<script>(function(d, s, id) {
  var js, fjs = d.getElementsByTagName(s)[0];
  if (d.getElementById(id)) return;
  js = d.createElement(s); js.id = id;
  js.src = 'https://connect.facebook.net/en_US/sdk.js#xfbml=1&version=v2.11';
  fjs.parentNode.insertBefore(js, fjs);
}(document, 'script', 'facebook-jssdk'));</script>

...

Info

This Guide explains and describes what permissions and limitations for PBX users and administrators can be set to limit access to certain PBX services and features.

Updated: November 2019

Permalink: https://confluence.wildix.com/x/eQaIAQ

Table of Contents

Introduction

...

Via ACL for PBX users it is possible to forbid certain groups of users external calls to certain call classes, limit access to certain PBX services and UC features. The full list of ACL permissions: APPENDIX 2.

Via ACL for PBX administrators it is possible to limit access to certain WMS menus and forbid certain operations related to PBX management to groups of PBX admins. The full list of ACL admin permissions: APPENDIX 3.

Note

Note: Normally, if you don't forbid any certain access via ACL, it means the access is allowed. For example, if you don't have any ACL restriction "Cannot" - "Intrusion", it means intrusion is allowed.

Exception: There are 3 ACLs that are not permitted by default: "Can " - "Modify presence", "Can" - "Delete calls" and "Can" - "See voicemail". At first, you have to set ACL permissions for using these services.

...

  • Admin (no limitations, assigned to “admin” user)
  • Default (see Default ACL settings; assigned to new users by default)

...

Available classes for processing of calls to/ from other countries (see Call classes explanation):

  • North America
  • Africa
  • Europe1
  • Europe2
  • South America
  • Oceania
  • Russia
  • Asia1
  • Asia2
  • International (only WMS 4.0X, contains all mentioned call classes)

...

Recommendations to avoid calls to illegal destinations:

(as in Default ACL settings)

  • First add the rule “cannot call All”
  • Then add a number of “can call” rules

...

  • Internal – internal calls
  • Local - local calls 
  • National – recognized based on the National Prefix in Dialplan General Settings
  • Mobile – recognized based on the Country Code in Dialplan General Settings
  • Emergency – recognized based on the Country Code in Dialplan General Settings
  • Free – recognized based on the Country Code in Dialplan General Settings
  • Premium1 – recognized based on the Country Code in Dialplan General Settings
  • Premium2 – recognized based on the Country Code in Dialplan General Settings
  • Premium3 – not defined
  • Premium4 – not defined
  • North America – calls to numbers starting with 001 or +1
  • Africa – calls to numbers starting with 002 or +2
  • Europe1 – calls to numbers starting with 003 or +3
  • Europe2 – calls to numbers starting with 004 or +4
  • South America – calls to numbers starting with 005 or +5
  • Oceania – calls to numbers starting with 006 or +6
  • Russia – calls to numbers starting with 007 or +7
  • Asia1 – calls to numbers starting with 008 or +8
  • Asia2 – calls to numbers starting with 009 or +9
  • International - calls to Europe1-2, North and South America, Africa, Oceania, Russia, Asia1-2 numbers

Prefixes per country for call class detection:

...

If  "cannot" - "View" - "Group" limitation is set, a user is not able to see users from a specified group when configuring "Voicemail" Function Key.

Current limitation: "Cannot - Share status via Kite" and "Can - Modify presence - Everybody"

ACL "Cannot - Share status via Kite" breaks ACL "Can - Modify presence - Everybody". This means, if a user has ACL "Cannot - Share status via Kite", another user with ACL "Can - Modify presence - Everybody" is not able to change that user status.

APPENDIX 1. Default ACL permissions

...