TGAR and TARG
If a route (RDB) is set to type (TKTP) = TIE, then the access restrictions are controlled by TGAR (Trunk Group Access Restrictions) and TARG (Trunk Access Restriction Group). A TARG/TGAR match denies ACOD access (dialing the access code). TGAR is also checked if LD 86 ESN, TGAR=YES (not default).
The rule is: when TARG and TGAR match, the set is denied access to the route. A set with a TGAR of 0 (zero) has no access restrictions.
Eg: When a set with a TGAR of "1" dials the route access code of a route with a TARG of "1", the call is blocked.
- TGAR is assigned to a phone. Each phone has one TGAR entry, 0=unrestricted (PRT in LD 20).
- TARG is assigned to the trunk route. Each route can have multiple TARG entries (PRT in LD 21).
Example:
If the Routes have the following TARGs:
Local | Long Distance | International | Tie to Site 2 | Tie to Site 3 | |
Set↓ RDB→ | TARG: 1 | TARG: 1 2 3 | TARG: 1 3 | TARG: 3 | TARG: 4 |
TGAR: 0 | ✅ | ✅ | ✅ | ✅ | ✅ |
TGAR: 1 | ❌ | ❌ | ❌ | ✅ | ✅ |
TGAR: 2 | ✅ | ❌ | ✅ | ✅ | ✅ |
TGAR: 3 | ✅ | ❌ | ❌ | ❌ | ✅ |
TGAR: 4 | ✅ | ✅ | ✅ | ✅ | ❌ |
Sets with:
- TGAR 0 can use all routes
- TGAR 1 can call sites 2 and 3
- TGAR 2 cannot call Long Distance
- TGAR 3 can only call local and Site 3
- TGAR 4 can call everything except Site 3