10.8  

Toll restriction in CorNet-N 
 
Implementing features, see also Manager E Toll restriction in CorNet-N

Definition  
HiPath 3000 supports PABX traffic via CorNet. The system can be operated as an end node (system without CO access, only CorNet trunk group), as a transit node (system with at least 2 CorNet trunk groups, no central office), and as a gateway (system with CO and CorNet trunk group).
In addition to the Basic Call (outgoing and incoming call setup), the Toll Restriction feature is supported.
If HiPath 3000 is operated in networked environments, the toll restriction assigned to the station is verified and transferred, or received in the case of incoming calls, when a CorNet line is seized (toll restriction transfer). The class of service is transferred to a gateway system in standardized form every time an outgoing line is seized and every time an extension answers.

Model-Specific Data  

 Subject  
 HiPath 3800  
 HiPath 3550  
 HiPath 3500  
 HiPath 3350  
 HiPath 3300  
Feature available in  
 x  
 x  
 x  
Hardware requirements  
 -  
 -  
 -  
Software requirements  
 V5.0 or later  
 V1.0 or later  
 V1.0 or later  
Restrictions  
 As main or satellite CS  
 only as satellite CS  

 

Dependencies/Restrictions  

 Subject  
 Dependency/Restriction  
Class of service  
The following 15 classes of service exist for class-of-service transfer:  
 •   Internal access only (0)
 •   Outward restricted trunk access (1)
 •   Local public network (2-13, including 6 allowed and 6 denied lists)
 •   Unrestricted trunk access (14)
Classes of service for two networked systems  
When there is an external seizure of a station from the satellite CS (with COS 2-13) over the main CS, the main CS's first denied list always does the seizing.  
For this reason, keep the first denied line of the main CS free for the assessment of the stations from the satellite CS.  
The system keeps COS 0, 1, and 14 of the satellite CS.