Dtu

I am running ver6.2 but will go through a couple of things that can be done.

One way to block extensions to external trunks is to bar trunk access at the TAC level.

1. You need to know what access code an Extension in question uses to get an outside line and associate this code with a trunk Main Group.
In most cases 0 (or whatever your access is) is used for outgoing calls. If you enter the command LTMG and enter C (for code) when prompted with group? And the enter 0 (or whatever your access is) when prompted for code?
Alternatively you can enter LTMG A to list all MG’s along with access code.

2. Next step is that you need to make sure that the TAC in question has access to the relevant MG.
To do this enter the command LTGA and when prompted for group? Type the MG number or A to list all. When prompted for zone? Enter 0 9or whatever your access is). The result of this command will show a table with TAC’s 00 to 31 listed on the top and the MG’s down the left side. If there is an N at the cross reference point between TAC and MG that means that a person with that TAC is NOT able to access these trunks and therefore can not make any outgoing calls over that link.

This can be changed by using the command RTGA - Revise Trunk Group Access.

It all depends if you want this to be permanent or on a case by case basis.

You can also go further on route restrictions and TAC levels.

3. Now that you have found out that the TAC in question does have access to a MG for outgoing calls you need to find what restrictions are in place, this is done using the command LACR. Enter the command LACR, when prompted for CODE? Enter the number dialled for outside line (0 or ?) and then enter the TAC you wish to check.
When you have entered this information it will come back advising of a Route Restriction Table (RRT) associated with the TAC attempting to make an outgoing call over a specific link.

4. To check what restrictions are in this RRT enter the command LRRT followed by the table which was obtained in step 3.

I have about six levels of TAC setup, with other multiple restrictions on what numbers are blocked completely like betting and competition lines are completely blocked.

Hope this helps if you have further questions I would be happy to help.

jks

Dear dtu,

Actually I am looking for a facility that can be activated by an extension user itself. ( not through MMI ). Let me explain my requirements in detail…

(1) Extension Dial lock facility – Extension user can lock the extension for a short period to make any type of calls from his extension i.e dial pad deactivation during his absence.

(2) Deny trunk access – Extension user can activate a feature, that can block trunk access ( 0 or 9 ) from his extension for a short period, during his absence.

Thanks for the help…

Dtu

Ok I think this is more what your after:
Once again this is from 6.2 verion software not sure if it can be done for 5.2. I don't think your going to be able to achieve both outcomes.

Extension Lock/Unlock
The Extension Lock feature allows an extension to switch to a default COS and TAC. This feature is used, for example, to prevent unauthorised external calls or access to features when the extension user is absent.

The extension user sets Extension Lock by dialling a feature code and a four digit personal password (PIN). A priveleged extension or an operator's console may also set, or cancel, the feature on behalf of a local extension on the same node.

The Extension Lock feature is assigned by the ACT class-of-service. ACT can be listed and revised byt the commands LCSD and RCSD. The MMI command RACT can be used to invoke the feature on an extension regardless of whether the extension has a PIN or the ACT class-of-service configured.

Extension Lock cannot be applied to the following:

Emergency extension
Magneto extension
Operator console
Pilot number (Hunt group, Distribution group, ACD group, etc.).

The values for the alternative COS and alternative TAC are held in separate sytem parameters, SPACS for the alternative COS and SPATA for the alternative TAC. MMI commands LSSP and RSSP are used to list and revise both of these system parameters.

To prevent unauthorised access to external numbers via a diversion from an extension set to Extension lock, it is recommended that the alternative COS definition either does not permit external diversion (COS: AED - Absent Extension Diversion, EDV - External Diversion) or requires a password for external diversion (COS: EDP - External Diversion Password).

The MMI commands LPIN and RPIN can be used to list and revise the PIN associated with an extension. The 'Change PIN' feature code ###9 can be used by an extension to change its PIN.

So that a user does not need to remember different passwords for different features, the same four digit PIN is applicable to the extension Unlock feature, the External diversion feature and the PIN facility, but not the Pull Diversion feature password which is configured separately via the EPDV command.

Dtu

To achieve Requirement 1 - If you use the Extension Lock/Unlock feature, you could setup the Alternate COS to have Inter-COS call blocking - ie stop that COS from calling all other COS's. This depends on your current setup and how many different COS's you actually use.

LICB - List Inter-COS Call Blocking
Function: To list Class-Of-Service (COS) values (00-31) which cannot call other COS values. The restriction does not apply in the other direction unless specified by configuration or by a separate RICB command.

Horizontal COS value is COS of called extension
Vertical COS value is COS of calling extension
B, at the intersection of two Classes-of-Service, denotes blocking between calling COS and called COS.


RICB - Revise Inter-COS Call Blocking
Function: To prevent (Block) extensions with specified Class-Of-Service (COS) from calling extensions with a specified Class-Of-Service, or to cancel blocking.

Parameters:
FROM COS: COS (0-31) of calling extension
TO COS: COS (0-31) of called extension
BLOCK?: Y to apply blocking
N to cancel blocking
Output:
None.