NEAX2400 IPX Feature Programming Manual
NDA-24297, Issue 1
Page 557
Outgoing Trunk Queuing - D
term
O-2D
Service Conditions (cont’d)
4.
Individual stations may only initiate one OUTGOING TRUNK QUEUE - D
term
at a time. Subsequent
attempts will produce a reorder tone.
5.
Stations may be restricted from use of this feature via CLASS OF SERVICE - INDIVIDUAL [C-15].
6.
The station is put in queuing condition for a maximum of 30 seconds to one hour (adjustable through
system data). After this timing, OG queuing will be cancelled automatically.
7.
The maximum number of simultaneous OGQs per system:
1 IMG:
64 calls
4 IMG/IPX-U: 256 calls
8.
CALL PICKUP [C-7] cannot be used to answer a call directed to another station using the OUTGOING
TRUNK QUEUING - D
term
feature.
9.
OUTGOING TRUNK QUEUE - D
term
is common to all trunk groups (COT, TIE, FX, WATS, etc.) in the
system.
10.
OUTGOING TRUNK QUEUING - D
term
and CALL BACK [C-1] are mutually exclusive.
11.
OUTGOING TRUNK QUEUING - D
term
is denied to a station if the CALL BACK [C-1] or CALL HOLD
[C-6] feature is already activated.
12.
The Attendant cannot CAMP-ON [A-1] a call to a station that has activated this feature.
13.
ACCOUNT CODE [A-18] and FORCED ACCOUNT CODE [F-7] information can be recorded on
SMDR [S-10] when used in conjunction with OUTGOING TRUNK QUEUING - D
term
.
14.
OUTGOING TRUNK QUEUING - D
term
is only available from the MY- Line of a D
term
.
15.
This feature can also be activated when using a trunk in the remote node via FCCS link.
16.
The maximum number for the OGQ station is 1,024 within the FCCS network (NCN can manage a
maximum of 1,024 calls).
17.
OGQ data is transmitted to and stored in the Network Control Node (NCN). Therefore, all the OGQ data
will be cleared by the system initialization of the NCN.
18.
When the access to the NCN is impossible (system down, cable disconnection or trouble has occurred),
the user cannot set or cancel OGQ data. (After dialing the access code or pressing the feature keys for set/
cancel OGQ, the user hears the reorder tone.)
19.
When the trunk becomes idle status after the NCN is recovered, the call in the queue will be called back,
if data has not been cleared. If data has been cleared, the call is cancelled automatically.
Node A
Node B
FCCS link
Busy
Busy
Busy
Example: Node A and Node B are in an FCCS network.
•
Although a station belonging to Node A tried to call outside using a trunk belonging to Node B, all the trunks are busy.
The call can be in the queue using this feature.
TK
TK
TK