SCOPTEL IP PBX Software - Class of Service Configuration

PDF Version


The Class of Service Manager is used to create objects with permissions or restrictions to Outgoing Lines, Incoming Lines, Extensions, Feature Codes, or Applications. These CoS objects can then be applied to Extensions, Incoming Lines, Auto Attendants, Outgoing Lines, or Applications

The Class of Service Manager can be found by navigating to Configuration>Telephony>Manager>Class of Service.

  • Class of Service objects also control permissions and restrictions which vary depending on whether or not a Hot Desk Extension, Agent Extension, or Room (Hotel) Restriction Feature code has been invoked. For example an extension can have a Class of Service which restricts long distance Outgoing Lines when no Hotdesk Extension is logged but if a valid Hotdesk Extension logs in then the Outgoing Lines access is allowed.

  • There is no limit on the number of Class of Service objects which can be created. Therefore many CoS objects can be added to create granular security rules which can easily be applied to Outgoing Lines, Incoming Lines, Extensions, Feature Codes, or Applications.

  • The Class of Service is one of the last objects to be built during a new installation because many pre - requisites are required.
    • Before a new Extension can be added a CoS must be built so that the CoS can be assigned to the new extension.

    • Before a non default Feature Code can be created the matching module must be configured.

    • Before a Feature Code can be included in a CoS the Feature Code must be configured.

    • Before an Application can be assigned to a CoS the Application must exist. It is therefore more efficient to create any required Applications prior to adding any new CoS objects so that the CoS does not have to be edited more than once.

    • Before an Outgoing Line can be included in a CoS object the Outgoing Line must already exist.

NOTE : It is best practice to leave Incoming Lines>Options>Class of Service configured to the default “System Default” setting. This is because the PSTN interface also has a “System Default” CoS value and the Incoming Line CoS and the Interface CoS must use matching values else incoming calls will fail. Unique requirements could dictate non default settings. Also choosing a non System Default CoS on an Incoming Line can have serious security implications if not configured correctly.

Default CoS


Editing using the Select Tool

  • The Select tool is visible whenever you edit the Class of Service’s Services, Applications, Local Extensions, Outgoing Lines tabs

  • From the column on the left showing the available feature codes highlight each feature code required using a mouse and then click >> to assign those codes to the column on the right. Click on the “OK” button to close this window. Feature Codes listed in the right column will be added to the new CoS once the new CoS is saved. Only the objects included in each tab using the Select tool will be allowed wherever this CoS is applied.


Outgoing Line precedence

  • After selecting which Outgoing Line objects are allowed it is imperative to select the Outgoing Lines in the correct order of precedence.

  • Outgoing Lines are matched when dialed according to the precedence defined in the configured CoS object in top to bottom priority. Items at the top if matched will be immediately passed to the dial plan running in memory.

  • The most specific entry and most important dial plan matches should be placed in the highest priority.

  • By example a Outgoing Line equal to 1 NXXNXXXXXX ! should have a lower priority than a dial plan equal to 1800 NXXXXXX! Else that rule would be matched and dialed first before querying the next possible match. This can affect which trunk is accessed or LCR rule is used to place the outgoing call.