Class Of Restriction - Avaya Communication Manager Administrator's Manual

If you decide to ignore the above advice and attempt signaling from a new system that is using 802.1p
and 802.1Q VLANs on their signaling channels to an older system that does not support these protocols,
then whether signaling information would:
•
Reach the destination, with the network using the frames' VLAN and priority information, or
•
Reach the destination, but without having been given VLAN or priority treatment, or
•
Be dropped, either by the destination or by an intermediate device, depends on the capabilities of
the switches or hubs used in the data network and how they are configured.
The third possibility, "all frames dropped," means no signals get through between the server
running Avaya Communication Manager and the other device.

Class of restriction

You use COR to define the types of calls your users can place and receive. Your system may have only a
single COR, a COR with no restrictions, or as many CORs as necessary to effect the desired restrictions.
You will see the COR field in many different places throughout Communication Manager - when
administering phones, trunks, agent logins, and data modules, to name a few. You must enter a COR on
these screens, although you control the level of restriction the COR provides. You must administer a COR
for the following objects:
•
Agent LoginID
•
Access Endpoint
•
Announcements/Audio Sources
•
Attendant Console
•
Authorization Code — COR Mapping
•
Console-Parameters
•
Hunt Groups
•
Loudspeaker Paging
•
Data Modules
•
Remote Access (each barrier code has a COR)
•
Station
•
Terminating Extension Group
•
Trunk Groups
•
Vector Directory Number
Called-party and calling-party restrictions
Called-party and calling-party restrictions are the basis for all CORs. When no restrictions are needed,
assign a single COR with called-party and calling-party restrictions set to none. You can use this COR for
unrestricted telephones, trunk groups, TEGs, UCD groups, DDC groups, data modules, attendant groups,
and individual attendant extensions.
Administrator's Guide for Avaya Communication Manager
November 2003
Feature Reference
Class of restriction
1495