« previous next »
Pages: [1]   Go Down

Author Topic: Blocking ext to ext calling  (Read 1479 times)

Offline JasonTL

  • Sr. Member
  • ****
  • Posts: 208
  • Country: us
  • Karma: +0/-1
    • View Profile
Blocking ext to ext calling
« on: September 19, 2018, 11:13:35 AM »
Can you block extension to extension calling to a specific extension?

Mitel 3300 running 8.0 SP1
Logged

Offline lundah

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 1216
  • Country: us
  • Karma: +66/-0
  • Senior Chief Grunt
    • View Profile
Re: Blocking ext to ext calling
« Reply #1 on: September 19, 2018, 03:15:45 PM »
You can use Interconnect Restriction to do this. But be very careful, you can break a lot of things quite easily.
Logged

Offline johnp

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 2202
  • Country: us
  • Karma: +66/-0
    • View Profile
Re: Blocking ext to ext calling
« Reply #2 on: September 19, 2018, 06:57:26 PM »
You could also use tenanting. I usually put trunks, voicemail etc in one by itself. Then you can use the next tenant for the primary group and a third for this user. Tenanting is great if you have groups that need different MOH
Logged

Offline JasonTL

  • Sr. Member
  • ****
  • Posts: 208
  • Country: us
  • Karma: +0/-1
    • View Profile
Re: Blocking ext to ext calling
« Reply #3 on: September 20, 2018, 03:37:18 PM »
It looks like the interconnect solution may not work with ACD groups. Not sure if tennating will either.

The exact scenario I have is the customer wants to block one ACD group from calling another ACD group.

Logged

Offline johnp

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 2202
  • Country: us
  • Karma: +66/-0
    • View Profile
Re: Blocking ext to ext calling
« Reply #4 on: September 20, 2018, 08:23:58 PM »
Yes, agree that the proposed likely won't work for a path. Is this an enterprise or standalone?
Logged

Pages: [1]   Go Up
« previous next »
 

Sitemap 1 2 3 4 5 6 7 8 9 10