NEC Neax 2400 Ipx Feature Programming Manual

							NEAX2400 IPX Feature Programming ManualPage 558NDA-24297, Issue 1
O-2D Outgoing Trunk Queuing - Dterm
Interactions
1. Dial pad operation for Dtermsets may be exercised. A FLASH BUTTON [F-3D] must be programmed to
a programmable line/feature key.
2. OGQ-AUTOMATIC may operate with either same or separate access codes. If the Automatic option is
chosen, service set tone will be sent when encountering an all trunks busy situation. No dial pad operation
will be required.
3. When testing OGQ, at least one trunk of the trunk group being tested must be engaged in a station-to-trunk
or trunk-to-trunk connection. Use of the MB key only on the trunk circuit card will not allow OGQ to test
and operate properly.
Programming
STEP 1:ASYD- System Data 1, Index 68, Bit 3. Enables automatic cancel timer, as set in System Data 1,
Index 159. 0/1: -/Enable.
System Data 1, Index 159. OGQ release timer. Standard data of 00H for 30 minutes may be assigned.
(RAM data of 3C [Hex] provides for 30 minutes).
System Data 2, Index 4, Bit 0. Should the access code for CALL BACK and OGQ be the same? 0/1:
No/Yes. Usually assign data“1”. Assign on a per-tenant basis.
System Data 2, Index 4, Bit 1. Enable Automatic OGQ? 0/1: No/Yes. Assign on a per-tenant basis.
Automatic operation eliminates the need to access via dial pad.
System Data 2, Index 4, Bit 2. Enable OFF-HOOK OGQ for the Attendant Console? 0/1: No/Yes.
Assign on a per-tenant basis. (See OUTGOING TRUNK QUEUING-ATTENDANT[O-16].)
System Data 1, Index 139, timer for the recall ringing.
STEP 2:ANPD- Reserve a number level for service feature access and cancel. Assign Connection Indexes, CI
= N, H, B; Normal (N), Hooking (H), and Busy (B) (applicable to any feature assigned to this level).
Assign NND in accordance with a predetermined numbering plan.
STEP 3:ASPA- If System Data 2, Index 4, Bit 0 is assigned for separate access codes, assign an access code to
OGQ, SRV = SSC (Service Code), SID = 19, and to OGQ cancel, SRV = SSC (Service Code), SID =
20. Assign SID = 19 for a Connection Index of Busy (B) and SID = 20 for a Connection Index of
Normal (N). If the access codes are the same, either the access codes for OGQ or the access codes for
CALL BACK may be assigned.
STEP 4:ASFC- If access codes are separate, assign a Service Feature Class that allows SFI 1 to stations that
will have OGQ. If access codes are the same, assign an SFC that allows SRI 1, SFI 1 and SFI 2 to the
station.
STEP 5:ARTD- Routes to be used for OGQ must be flagged in CDN 9:TQ, Trunk Queuing Service. Always
allow queuing to Route 31, the LCR (S) flag route.
STEP 6:AKYD-ForD
termset the following data to assign CALL BACK Key. Type:Function:CALL BACK
[5].
STEP 7:ADSL- SN=6 (Trunk is Busy) and FKY=5 (Call Back; CB).
This command is used for assigning the function to each soft key.
FCCS Programming 
This data setting describes only the additional or replacement commands used to activate FCCS
services. When used as an FCCS feature, these commands replace the non-network commands (for
example, AAED is replaced by AAEDN). Note that the data setting for FCCS service varies depending
on the node.
Note 1
STEP 1:ASYDN- These data must be assigned to the NCN. 
						

							NEAX2400 IPX Feature Programming Manual
NDA-24297, Issue 1Page 559
Outgoing Trunk Queuing - DtermO-2D
FCCS Programming (cont’d)
System Data 1, Index 41: Designate the Trunk Queuing Override Timer
Index 68, b3: Enables automatic cancel timer
0/1: -/Automatic cancel timer is Available
Index 159: Designate Automatic Cancel Timer
STEP 2:ASPAN- These data must be assigned to the NCN.
TN: Tenant Number
ACC: Access number
CI: B = Busy (for Entry), N = Normal (for Cancel)
SRV: SSC
SID: 19 = OG Queuing-Entry
SID: 20 = OG Queuing-Cancel
STEP 3:ANPDN- These data must be assigned to the NCN.
TN: Tenant
1st DC: 1st Digit
CI: Normal (N), Hooking (H) and Busy (B)
NND: Number of Necessary Digits
BLF: Busy Lamp Field
STEP 4:ARTDN- These data must be assigned to the NCN.
LGRT: Logical Route Number
Assign CDN 9:TQ, Trunk Queuing Service = 1
Note 1:When using ASYDL or ASYDN to program an FCCS feature, the basic programming of ASYD is required
in addition to ASYDL or ASYDN.
Note 2:The current data should also be set in addition the above-mentioned command.
The command to be set to the node that accommodates the trunk: ARTD
The command to be set to all the nodes: ASFC, AKYD, ASPA 
						

							NEAX2400 IPX Feature Programming ManualPage 560NDA-24297, Issue 1
O-6 Off-Hook Alarm
O-6 Off-Hook Alarm
General Description
This feature allows a user to call the Attendant or a predetermined station by simply staying OFF-HOOK. The
calling number is automatically displayed at the ATTENDANT CONSOLE [A-3] or a Dtermseries with a display.
Operating Procedure
1. Lift the handset and stay off-hook.
2. After a predetermined time elapses (2 to 30 sec.), the call will terminate at the ATTENDANT CONSOLE
[A-3] or the predetermined station.
3. The calling telephone number will be displayed at the ATTENDANT CONSOLE [A-3] or D
termwhen
answered.
Service Conditions
1. Predetermined timing interval is programmable through the MAINTENANCE ADMINISTRATION
TERMINAL [M-18] (MAT) (2 to 30 seconds).
2. In the night mode, an OFF-HOOK ALARM call directed to the ATTENDANT CONSOLE [A-3] will not
terminate at the ATTENDANT NIGHT TRANSFER [A-19] predetermined night station. The caller will
receive a reorder tone.
3. A station will be assigned as a member of an OFF-HOOK ALARM group and will be connected to the
predetermined stations that are assigned for each off-hook group.
4. Maximum number of OFF-HOOK ALARM groups is 7 per-TENANT [T-12] group. A group number
must be assigned to all the stations to be included in a group.
5. The station assigned as a terminating station of each OFF-HOOK ALARM group can be a member of a
HUNTING GROUP [S-7, 8, 9].
6. This service is programmed via system data. Stations may be restricted from using this feature in CLASS
OF SERVICE - INDIVIDUAL [C-15].
7. The ATTENDANT CONSOLE [A-3] can answer by pressing EMG key, which must be assigned by the
MAT [M-18]. Using the ANSWER key will not give priority to the OFF-HOOK ALARM call.
8. The predetermined target station can set CALL FORWARDING - ALL CALLS [C-5] and CALL
FORWARDING - BUSY LINE [C-2].
9. When the predetermined station is busy, the OFF-HOOK ALARM call receives ringback tone until the
station becomes idle.
10. This feature cannot be applied while in CONSULTATION HOLD - ALL CALLS [C-17] or CALL HOLD
[C-6] mode.
11. When an OFF-HOOK ALARM call is directed to a Pilot station of a UCD [U-1] group, queuing is not
available when all the stations within the group are busy.
12. This feature can also be activated when a station and the called party belong to different nodes. 
						

							NEAX2400 IPX Feature Programming Manual
NDA-24297, Issue 1Page 561
Off-Hook Alarm O-6
Service Conditions (cont’d)
13. If a station belongs to the node that has an Attendant Console, the station is connected with the Attendant
Console. If a station belongs to the node that does not have an Attendant Console, the station is connected
with the specified Attendant Console in the remote node according to the system data assigned. See the
figure below.
Interactions
1. A total of seven OFF-HOOK ALARM Groups per tenant may be assigned to the system, if the termination
point is a station. Any station not assigned in ASGD will go to reorder tone after the Register Prepause
timer (ASYD, System Data 1, Index 128) expires. If the termination point is the Attendant Console, all
stations in the tenant will terminate to the Attendant Console.
2. ASAT cannot be used to construct different OFF-HOOK ALARM groups terminating to specific
Attendant Consoles. If the tenant is equipped with more than one Attendant Console, OFF-HOOK
ALARM calls will be directed to all consoles with OFF-HOOK ALARM keys programmed in AAKP.
3. The following features will function on terminating calls to a predetermined station:
CALL PICKUP [C-7]
CALL TRANSFER [C-11]
CALL HOLD [C-6]
CALL FORWARDING [C-5A]
4. No tone is provided on CALL WAITING-TERMINATING [C-12].
Programming
STEP 1:ASYD- System Data 1, Index 128, Bits 0-3. Register Prepause timer is used for OFF-HOOK
ALARM. After the register times out, the station assigned to an OFF-HOOK ALARM group will ring
at the terminating Attendant Console or station. Leave Index 128 as 00H for normal operation.
System Data 1, Index 168, Bit 4. Enable OFF-HOOK ALARM? 0/1: No/Yes.
System Data 1, Index 168, Bit 5. Is the terminating point for OFF-HOOK ALARM an Attendant
Console or station? 0/1: Attendant Console/Station. If Attendant Console is chosen, go to AAKP
command. If station is chosen, go to the ASID and ASGD commands.
STEP 2:ASID- This command defines the purpose of this Special Incoming Group, and is used in conjunction
with ASGD. Assign the following:
TN: Tenant Number
F: Function Number (0-7)
0: OFF-HOOK ALARM
GN: Group Number (1-7).
S/A: Special Incoming Equipment
Node A Node B
Node B Attendant Console AFCCS LinkStation A has been set 
to be connected with 
the Attendant Console 
A by system data. 
						

							NEAX2400 IPX Feature Programming ManualPage 562NDA-24297, Issue 1
O-6 Off-Hook Alarm
Programming (cont’d)
S: Station
A: Attendant Console
SSTN: Special Station Number
STEP 3:ASGD- This command defines what stations belong to the Special Incoming Group. Assign the
following:
TN: Tenant Number
STN: Station Number
F: Function Number (0-7)
0: Off-Hook Alarm
GN: Group Number (1-7)
STEP 4:ASFC- Assign a Service Feature Class that allows SFI 30 to stations that will have OFF-HOOK
ALARM.
STEP 5:AAKP- Assign the Attendant Console Key Pattern. The ATN: Attendant Number (TRK No. for RTE
901); KYN = 1-6; and FUNC = 2. (The console must be in Night mode to assign this command.)
FCCS Programming 
This data setting describes only the additional or replacement commands used to activate FCCS
services. When used as an FCCS feature, these commands replace the non-network commands (for
example, AAED is replaced by AAEDN). Note that the data setting for FCCS service varies depending
on the node.
 Note 1
ASYDL- This data must be set to all the nodes.
System Data 1, Index 640, assign the Fusion Point Code (FPC) of the node providing the Attendant
Console.
Note 2
Note 1:
When using ASYDL or ASYDN to program an FCCS feature, the basic programming of ASYD is required
in addition to ASYDL or ASYDN.
Note 2:Assign the self FPC at the terminating node.
The current data should also be set in addition the above-mentioned command.
The command to be set to the node that accommodates the attendant console: AAKP, ACFR (when the
destination is the Night ATT: ATNR)
The command to be set to all the nodes: ASYD, ASFC 
						

							NEAX2400 IPX Feature Programming Manual
NDA-24297, Issue 1Page 563
Off-Hook Queuing O-7
O-7 Off-Hook Queuing
General Description
This service allows a user, upon encountering a trunk-busy condition, to remain off-hook and automatically enter a
first-in, first-out queue. As soon as an outgoing trunk becomes available, the switch connects the next call to this
trunk.
Operating Procedure
1. Lift the handset; receive a dial tone.
2. Dial the Outgoing Call access code and the desired number (LCR access).
3. The NEAX2400 IPX determines that no trunks are available and places the call in an available queue slot.
4. The caller receives service set tone; remains off-hook and waits.
5. When a trunk becomes available, the dialed number is automatically sent forward.
Service Conditions
1. This feature is usually used in conjunction with LEAST COST ROUTING - 3/6-DIGIT [L-5].
2. The maximum number of simultaneous OFF-HOOK QUEUEs per system:
1IMG: 64calls
4 IMG/IPX-U: 256 calls
3. The queue slots are used commonly by OFF-HOOK QUEUING, OUTGOING TRUNK QUEUING [O-
2] and INTER-OFFICE OFF-HOOK QUEUING [I-11].
4. If no queue slots are available, the user will receive busy tone.
5. Route Class of the LCR can give the choice of the OFF-HOOK QUEUING.
6. CLASS OF SERVICE - INDIVIDUAL [C-15] is applied for each station. This class of service is different
from the class of service for OUTGOING TRUNK QUEUING [O-2]. Both services are mutually
exclusive.
7. When automatic outgoing queuing (on-hook queuing) is in service (tenant basis), OFF-HOOK QUEUING
service is not effective.
8. ACCOUNT CODE [A-18] and FORCED ACCOUNT CODE [F-7] information can be recorded on
SMDR [S-10], when used in conjunction with OFF-HOOK QUEUING.
9. This feature can also be activated when using a trunk in the remote node via FCCS link.
Node A Node BFCCS linkBusy
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
TKTK 
						

							NEAX2400 IPX Feature Programming ManualPage 564NDA-24297, Issue 1
O-7 Off-Hook Queuing
Service Conditions (cont’d)
10. The maximum of number of the OGQ stations is 1,024 within the FCCS network (NCN can manage a
maximum of 1,024 calls).
11. 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.
12. 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.)
13. 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.
Interactions
1. UNIVERSAL SENDER [U-3] must first be provided.
2. The PBX attempts trunk seizure every four seconds until the connection has been completed.
3. LEAST-COST ROUTING-3/6 DIGIT [L-5] information will be applied to these attempts. Therefore,
OUTGOING TRUNK QUEUING will be set against all routes in the Outgoing Routing Pattern (OPR).
4. If all queuing memory slots are in use, the user will receive a trunk-busy signal.
5. The time a call may remain in queue is unlimited.
6. The following features cannot be activated toward the busy station: CALL WAITING - ORIGINATING
[C-31], CALL WAITING - TERMINATING [C-12], ATTENDANT CAMP-ON WITH TONE
INDICATION [A-1], BUSY VERIFICATION [B-3] and EXECUTIVE RIGHT-OF-WAY [E-1].
7. Do not disable constant service set tone by changing System Data 1, Index 42, Bit 7 to data“1”.This
changes constant service set tone to burst special dial tone, and special dial tone to burst special dial tone,
followed by constant dial tone. This will also disable TANDEM OFF-HOOK QUEUING.
Programming
STEP 1:ASYD- System Data 2, Index 4, Bit 1. Enable Automatic OUTGOING TRUNK QUEUING? 0/1:
OFF-HOOK QUEUING/Automatic OUTGOING TRUNK QUEUING. (OFF-HOOK QUEUING and
Automatic OUTGOING TRUNK QUEUING are mutually exclusive.) Assigning data“0”allows
OFF-HOOK QUEUING.
STEP 2:ASFC- Assign a Service Feature Class that allows SFI 21 to stations that will have OFF-HOOK
QUEUING.
STEP 3:ARTD- Routes to be used for OFF-HOOK QUEUING must be flagged in CDN 9:TQ. Also allow
OUTGOING TRUNK QUEUING to the LCR(s) flag route.
FCCS Programming 
This data setting describes only the additional or replacement commands used to activate FCCS
services. When used as an FCCS feature, these commands replace the non-network commands (for
example, AAED is replaced by AAEDN). Note that the data setting for FCCS service varies depending
on the node.
 Note 1
STEP 1:ASYDN- This data must be assigned to the NCN. System Data 1, Index 41: Designate the Trunk
Queuing Override Timer.
STEP 2:ASPAN- This data must be assigned to the NCN.
TN: Tenant Number
ACC: Access Number 
						

							NEAX2400 IPX Feature Programming Manual
NDA-24297, Issue 1Page 565
Off-Hook Queuing O-7
FCCS Programming (cont’d)
CI: B = Busy (for Entry), N = Normal (for Cancel)
SRV: SSC
SID: 19 - OG Queuing - Entry
CI: N = Normal
SID: 20 = OG Queuing - Cancel
Note 1:When using ASYDL or ASYDN to program an FCCS feature, the basic programming of ASYD is required
in addition to ASYDL or ASYDN.
Note 2:The current data should also be set in addition the above-mentioned commands.
The command to be set to the node accommodating the trunk: ARTD
The command to be set to all the nodes: ASYD, ASFC 
						

							NEAX2400 IPX Feature Programming ManualPage 566NDA-24297, Issue 1
O-13 Overflow - UCD
O-13  Overflow - UCD
General Description
1. When a call has terminated to UCD [U-1] Group A, and the incoming call has encountered all stations
busy in Group A, the call is transferred to UCD [U-1] Group B, if Group B is registered as the
OVERFLOW-UCD destination.
2. If all stations are busy in Group B, then the call is placed in queue for the originally called UCD [U-1]
group (Group A).
Operating Procedure
No manual operation is required.
Service Conditions
1. An OVERFLOW group must be a UCD [U-1] Group.
2. One OVERFLOW group can be provided for one UCD [U-1] Group.
3. OVERFLOW is performed only once.
4. An OVERFLOW group cannot be registered into a queue.
Call TerminationUCD 
Group A 
All Busy
OverflowUCD 
Group B
 
Call Termination
OverflowUCD 
Group A 
All Busy
Group B 
All Busy Call registered in Group A 
						

							NEAX2400 IPX Feature Programming Manual
NDA-24297, Issue 1Page 567
Overflow - UCD O-13
Service Conditions (cont’d)
5. A call can be overflowed 4 times at the maximum by using this feature. If overflowing destinations are all
busy, the call is queued into original group (depending on system data). For details, refer to the figure
below.
Note:The call cannot be overflow more than 5 times.
6. UCD OVERFLOW data can be programmed in Local Data Memory (LDM).
7. The overflowing destination which can be assigned to UCD group is as follows:
UCD group (that is busy) Overflowing Destination
UCD group assigned by ASHU command→UCD group designated by AUOG command
UCD group assigned by ASHUL command→UCD group designated by AUOGL command
UCD group assigned by ASHUN command→UCD group designated by AUOGN command
8. This feature can be activated via FCCS.
9. When using the FCCS network, the number type (telephone number or Physical Station Number) for the
station assignment must be the same between the originally called group and the forwarded group.
Interactions
ALL UNIFORM CALL DISTRIBUTION [U-1] interactions apply to the UCD overflow group. The incoming
overflow call is handled in the same way as a regular incoming call. If both UCD groups are busy, the call will queue
at Group A.
Programming
STEP 1:ASHU/ASHUL- Assign the required data for the UCD Group:
TN/UGN: Tenant Number/User Group Number (Fixed to“1”)
STN/TELN: Station Number/Telephone Number (max: 16 digits)
CNT: Number of stations to be entered (recommended maximum of 100 stations)
ADD: Number of stations to be added (recommended maximum of 100 stations)
*EDIT STN/EDIT TELN: Station Numbers/Telephone Numbers of the stations included in the UCD
group (*indicates the order of a station in the group)
Overflowing destination  
    for UCD group A
Overflowing destination  
    for UCD group B
Overflowing destination  
    for UCD group C
Overflowing destination  
    for UCD group D Overflowing destination  
    for UCD group E
Ca
ll
 
Te
rm
ina
t
io
n
   UCD  
 group A 
 All Busy
   UCD  
 group B 
All Busy
   UCD  
 group C 
All Busy
   UCD  
 group D 
All Busy
   UCD  
 group E 
 All Busy    UCD  
 group F 
 
 The call is placed in queue for the 
 originally called U CD  group A.Overflow
Overflow
Overflow
Overflow
Note