Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
prevent display of route acod on digital sets, icog
- Thread starter MWETT
- Start date
MWETT.. If a user dials an ACOD the access restrictions from the NCOS settings still apply. This is because if the user normally has access to the route, the ACOD and AC1 code are both valid.
If you want to stop a user dialling a particular route the TGAR/TARG barring would be used.
Extensions and trunks have, as part of their attributes, a Trunk Group Access Restriction (TGAR) .The TGAR can be used to bar access to routes in the following ways.
Dialling the Route Access Code (ACOD) can be used to access trunks. A check is made of the extension/trunk TGAR. It is compared with the entries under TARG, the Trunk Access Restriction Group. If there is a match between the number allocated in extension/trunk TGAR and one of the numbers entered in the route TARG list, then access to the route will be barred. An example of this can be seen below.
Call originator TGAR = 1. Route being accessed TARG = 1, 2, 3. Call originator cannot access route.
Call originator TGAR = 5. Route being accessed TARG = 1, 2, 3. Call originator can access route
In this example, the call originator with the TGAR 1 would not be allowed to dial the access code of the particular route as well as any call originators with a TGAR 2 or TGAR 3. The call originator with TGAR 5 or any other TGAR not in the TARG list will be able to access the route.
TGARs can be overridden by Basic Alternate Route Selection (BARS) which means that they are not totally effective in controlling trunk access. The programming option TGAR (NO)/YES in LD 86 FEAT= ESN gives the choice to (ignore) or use the TGAR/TARG programming when calls are routed with BARS.
If TGAR=NO in LD 86, TGAR/TARG can deny access when the access code is used, but if the call is routed through BARS the call can be allowed. If TGAR=YES in LD 86, TGAR/TARG will deny access when the access code or BARS is used.
This gives another possibility; different departments within a customer's organisation can each be given their own trunk route for billing purposes. Access is through BARS (everyone dials 9 for a trunk) and TGAR/TARG barring is arranged so that each department can only access their own route.
With Class of Service and TGAR/TARG restrictions, it is possible for one to allow the call and the other to bar the call, in situations like that the most restrictive is the one that applies. This is true for all trunk access restrictions, the one that says NO wins.
To prevent a route ACOD being displayed give the ACOD a name using LD 95. You can change the ACOD to an alternative DN and then add the name.
Colin
If you want to stop a user dialling a particular route the TGAR/TARG barring would be used.
Extensions and trunks have, as part of their attributes, a Trunk Group Access Restriction (TGAR) .The TGAR can be used to bar access to routes in the following ways.
Dialling the Route Access Code (ACOD) can be used to access trunks. A check is made of the extension/trunk TGAR. It is compared with the entries under TARG, the Trunk Access Restriction Group. If there is a match between the number allocated in extension/trunk TGAR and one of the numbers entered in the route TARG list, then access to the route will be barred. An example of this can be seen below.
Call originator TGAR = 1. Route being accessed TARG = 1, 2, 3. Call originator cannot access route.
Call originator TGAR = 5. Route being accessed TARG = 1, 2, 3. Call originator can access route
In this example, the call originator with the TGAR 1 would not be allowed to dial the access code of the particular route as well as any call originators with a TGAR 2 or TGAR 3. The call originator with TGAR 5 or any other TGAR not in the TARG list will be able to access the route.
TGARs can be overridden by Basic Alternate Route Selection (BARS) which means that they are not totally effective in controlling trunk access. The programming option TGAR (NO)/YES in LD 86 FEAT= ESN gives the choice to (ignore) or use the TGAR/TARG programming when calls are routed with BARS.
If TGAR=NO in LD 86, TGAR/TARG can deny access when the access code is used, but if the call is routed through BARS the call can be allowed. If TGAR=YES in LD 86, TGAR/TARG will deny access when the access code or BARS is used.
This gives another possibility; different departments within a customer's organisation can each be given their own trunk route for billing purposes. Access is through BARS (everyone dials 9 for a trunk) and TGAR/TARG barring is arranged so that each department can only access their own route.
With Class of Service and TGAR/TARG restrictions, it is possible for one to allow the call and the other to bar the call, in situations like that the most restrictive is the one that applies. This is true for all trunk access restrictions, the one that says NO wins.
To prevent a route ACOD being displayed give the ACOD a name using LD 95. You can change the ACOD to an alternative DN and then add the name.
Colin
- Status
Similar threads
- Question
- Locked
- Question