Restrict transfer btwn extensions

[VoIPgirl]

I am looking for the best way to restrict transfer btwn extensions. I have multiple companies on my definity. I don't want co A to be able to transfer to co B. Is the best way to set up separate COR for each group and then restrict access btwn COR? Any other ideas or better solutions out there?
Thanks

 

[TJStar]

Depends on what you want these companies share. Normally, tenant partitioning is used.

The best source of info about using this if it will solve your problem is the Definity Administrators Guide book number 555-233-506.

Here an example from the book...

Tenant partitioning examples

The following is a simple example of how you might administer Tenant Partitioning in an office complex.
You assign tenant partition 1, the universal tenant, as the service provider. All other tenants can call and
be called by the service provider.

You assign tenant partitions 2–15 to individual businesses in the complex. You maintain the
system-default restrictions for these tenants. That is, tenants cannot access telephones, trunking facilities,
or other Communication Manager endpoints belonging to other tenants.

You assign tenant partition 16 to the restaurant in the building complex. You give all tenants permission
to call this tenant. However, to prevent the restaurant from accessing trunks and other facilities belonging
to tenants, you do not permit the restaurant to call any other tenants.

You assign tenant partition 17 to all CO trunk groups. You give all tenants permission to call this tenant.
You assign tenant partition 18 to a trunk group that tenants 3 and 7 want to share. You give Tenants 3 and
7 access to this partition; you deny all other tenants access. To prevent toll fraud, you do not allow tenant
18 to call itself.

The Automatic Route Selection (ARS) route pattern can be the same for all tenants. In this example, the
trunk for tenant partition 18 (the private trunk shared by tenants 3 and 7) is first in the route pattern.
Tenant partition 17 is second. Tenants 3 and 7 route first to partition 18 and then as a second choice to
partition 17. You deny all other tenants access to partition 18 and so the system routes them directly to
partition 17.

All facilities that are not shared, including trunk groups, VDNs, telephones, attendant consoles, and other
endpoints, are assigned to the tenant partition that they serve.

Table 100, Calling permissions for partitions, on page 1716 summarizes the calling permissions for the
different partitions. Yes indicates that the partitions have permission to call and be called by each other;
no indicates that partitions cannot call or be called by each other.
=========================================
Table 100
=========================================
Calling tenant Called tenant partition number
partition number
1 2, 4—6, 8—15 3,7 16 17 18
[ul]
[li]1 yes yes yes yes yes yes[/li]
[li]2, yes Each no yes yes no[/li]
4-6 partition
8-15 can call
itself but
not the
others

[li]3,7 yes no Each yes yes yes[/li]
partition
can call
itself but
not the
others

[li]16 yes no no yes yes no[/li]
[li]17 yes yes yes yes yes no[/li]
[li]18 yes no yes no no no[/li]
[/ul]

Tentant partioning has a few interaction with route patterns where you can have multiple trunk groups within a route pattern that are in different tenants. If a user has permission to dial that tenant then they can access the trunks in that tenant only. Even though other trunks are in the route pattern.

Hopefully this gives you some info to go on

-TJ

 

[Bobg1]

If you don't have or dont want to use tenant partitioning,
Yes you can use the COR's to restrict them from calling each other. You can also setup your trunk groups with seperate cors so they call out on ones specific for them.

 

[VoIPgirl]

thanks for the great help!