NEC Neax 2400 Imx Business Features And Specifications

							NEAX2400 IMX Business Features and Specifications
NDA-24221, Issue 3
Page 471
Station Hunting - Terminal S-9
Interactions (cont’d)
c.) When PH = 0: Station hunt starts by dialing the pilot station number only. The feature is not
provided when the Phantom Number is dialed.
9. The lead station is the first station programmed in the ASHP command.
10. When Programmed on LDM:
a.) When activating this feature via FCCS, when CALL FORWARDING - ALL CALLS [C-5] is in
service at a pilot station, a call directed to the station is forwarded to the designated station.
b.) When activating this feature via FCCS, when an incoming call to a pilot station is forwarded by
CALL FORWARDING - BUSY LINE [C-2] and the forwarded party (also a member of another
hunting group) is also busy, the resultant hunt target can be designated from the forwarding side
group or the forwarded side group. This can be specified by the ASYD command. For further
information, refer to Programming.
c.) When activating this feature via FCCS, if the following occurs, a non-pilot station is skipped in
the hunting circulation process:
 When CALL FORWARDING - ALL CALLS [C-5] is set at the non-pilot station.
 When CALL FORWARDING - BUSY LINE [C-2] is set at the non-pilot station and the station
is actually in the busy state.
d.) When activating this feature via FCCS, CALL FORWARDING - DON’T ANSWER [C-3] will
respond to any call (both pilot and non-pilot stations). After a certain period of no answer, the call
is forwarded to the designated station.
e.) When activating this feature via FCCS, this feature is not available for a call in recall state by
CALL BACK [C-1] or CALL HOLD [C-6].
f.) When activating this feature via FCCS, a Hot Line station cannot be assigned as a member of the
hunting group.
 
Busy Station
Idle Station
Ringing Station
Phantom StationSecretaryAvailable Other Hunt GroupPilot
Hunt
Hunt Phantom
Ringing Another call to Pilot Call to Phantom, set call 
back / Message 
Reminder to PilotCall to Pilot When PH=0 (Station Hunting does not 
occur by the phantom number) is 
selected in APHN. 
						

							NEAX2400 IMX Business Features and Specifications
Page 472NDA-24221, Issue 3
S-9 Station Hunting - Terminal
Interactions (cont’d)
g.) When using a Phantom Telephone Number (PHTELN) for the pilot station, consider the
following:
 Whether to use the PHTELN to start the station hunt or not can be selected by the command
APHNL. When using the PHTELN, assign “1” in the PH parameter. If not, assign “0”.
 When PH = 1: Station hunt starts by dialing either the pilot station number (telephone number)
or its Phantom Telephone Number. Both numbers can be the pilot number.
 When PH = 0: Station hunt starts by dialing the pilot station number (telephone number) only.
The feature is not provided when the PHTELN is dialed. 
						

							NEAX2400 IMX Business Features and Specifications
NDA-24221, Issue 3
Page 473
Station Message Detail Recording (SMDR) S-10
S-10  Station Message Detail Recording (SMDR)
General Description
This feature provides a call record for all outgoing station to trunk calls and incoming trunk to station calls. When
the system is equipped with this feature, an RS232C output port or a SOCKET interface (LAN) is provided,
permitting interface with a customer-owned computer system. All output is in the ASCII format, and includes the
following:
 Calling telephone number
 Dialed number (24 digits maximum)
 Route number
 Start of call time
 Disconnect time
 Year, month and date
 Condition (Attendant handled, transfer, etc.)
 ACCOUNT CODE [A-18] (10 digits maximum)
 AUTHORIZATION CODE [A-28] (10 digits maximum)
 FORCED ACCOUNT CODE [F-7]
Additional FCCS Format
 Called Party Type (Attendant Console/station)
 Call Start/Call end time (millisecond)
 Call metering
 FPC/User Group/Telephone number (calling party)
 FPC/User Group/Telephone number (called party)
 FPC of the node providing the route for the call
 Logical Route Number
 FPC of the node providing the first-choice route
 First-choice Logical Route Number
Operating Procedure
No manual operation is required. Call record outputs are produced automatically.
Service Conditions
 RS232C Interface Conditions:
1. SMDR information facilitates analysis of trunk traffic and can be readily applied for cost allocation or
billing purposes.
2. SMDR may be programmed to record either all outgoing calls or only toll calls, depending upon user
requirements.
3. Both incomplete and abandoned calls will be discarded by the SMDR.
4. When ROUTE ADVANCE [R-6] or LEAST COST ROUTING (LCR) - 3/6-DIGIT [L-5] is provided with
the system, SMDR will record the route number selected.
5. The maximum number of digits dialed cannot exceed 24.
6. When customer-owned computer equipment is connected via RS232C interface, SMDR information will
be transmitted directly to the computer as each call record is completed.
7. If the outgoing call is directed to a trunk that cannot give answer supervision from the Central Office, the
start of call time is 18 seconds after the last digit is dialed. This timer value is set on the System Data. 
						

							NEAX2400 IMX Business Features and Specifications
Page 474NDA-24221, Issue 3
S-10 Station Message Detail Recording (SMDR)
Service Conditions (cont’d)
8. If the distance between the system and the processing computer exceeds 50 feet (15 meters), an
asynchronous-type modem should be used.
9. RS232C Interface specifications: Synchronization Asynchronous 
Data Speed 300, 600, 1200, 2400, 4800, 9600bps 
Code ASCII 7-Bit + parity Bit 
Maximum Distance 50 ft. (15m) without modem
10. Supervision on the status of the external RS232C terminal is not performed.
11. FORCED ACCOUNT CODE [F-7] can be recorded on SMDR, for INWATS and CO incoming calls,
when used in conjunction with the REMOTE ACCESS TO SYSTEM [R-2] service feature.
12. FORCED ACCOUNT CODE [F-7] cannot be registered on SMDR if the incoming REMOTE ACCESS
TO SYSTEM [R-2] calls are terminated to stations via night service or DID [D-8].
13. For REMOTE ACCESS TO SYSTEM [R-2] tandem connections, the FORCED ACCOUNT CODE [F-
7] is registered for outgoing trunks only.
14. The PBX can accommodate up to 7 active ports or 4 redundant ports. Additional hardware is required.
15. AUTHORIZATION CODE [A-20] can be recorded on SMDR.
16. The maximum number of simultaneous calls can be stored in the system memory (active calls) is 28,000.
When a call is completed, the record is sent to the output device and is removed from memory.
17. If an overflow occurs, calls are allowed to complete and are not recorded.
18. ATTENDANT-CONTROLLED CONFERENCE [A-2]: If the Attendant adds a trunk to the conference,
the Attendant conference line terminal is recorded.
19. LEAST COST ROUTING - 3/6-DIGIT [L-5]: The calling party can dial an ACCOUNT CODE [A-18]
before the LCR access code. The called number is recorded (as modified for sending).
20. If an ACCOUNT CODE [A-18] is dialed, the maximum digits of the called number is 22. 
21. CENTRALIZED ATTENDANT SERVICE (CAS) [C-20]: The SMDR record is provided for calls
extended outward by a CAS Attendant.
22. DIRECT INWARD DIALING (DID) trunk calls [D-8]: If the call is to the Attendant, the Attendant can
input an ACCOUNT CODE [A-18] before extending the call.
23. INDIVIDUAL TRUNK ACCESS [I-4]: The Attendant cannot dial in an SMDR account code before using
direct trunk selection.
24. Incoming TIE trunk calls: If an incoming call to the Attendant is extended, the Attendant can input an
ACCOUNT CODE [A-18].
25. SERIAL CALL [S-15]: The duration of the total call is recorded on the last station call.
26. STATION HUNTING [S-7, 8, 9]: The hunted-to station is recorded in the called number field.
27. TANDEM TIE TRUNK [T-1] Calls: The calling number is the incoming trunk route plus trunk number;
the called number is the number dialed.
28. UNIFORM CALL DISTRIBUTION (UCD) [U-1]: The calling number is the incoming trunk route plus
trunk number. If the call is to a station, the station answering the number is recorded as the dialed number.
29. On an incoming trunk call to the Attendant, the Attendant call record will start upon answering and
complete when the Attendant releases. A station call record will start when the Attendant releases and
complete when the station goes on-hook. If required, a station record will not be generated if the station
does not answer.
30. A system option is available to allow or restrict call completion in the case where a failure occurs in
transmitting SMDR data from the processor to the I/O port. 
						

							NEAX2400 IMX Business Features and Specifications
NDA-24221, Issue 3
Page 475
Station Message Detail Recording (SMDR) S-10
Service Conditions (cont’d)
31. Additional hardware is required.
32. Call Time specification for the FCCS network:
 The base for Call Start Time and Call End Time is the time in the calling party-side node.
 In case there is time difference between each node, related time difference data, based on the UCT
(Universal Coordinated Time) standard, should be written in Network Data Memory (NDM) by using
the ATDF command.
 Because billing information gathering is performed in the called party-side node, the Call Start Time in
the originating node is determined in a way the deduction of time between calling and called party nodes
is added or subtracted to/from the called party-side time. (If there is no time difference data in any [both]
of the nodes, the Call Start Time is specified automatically by that in the called party-side node.)
 A counter, not the clock providing the current time, is used for Call End Time calculation. The
calculation method is as follows:
a.) Call Start Time (by using the clock) and the current counter value are registered to the Call Base
Table, soon after a line connection is established.
b.) Upon the call completion, the deduction between the counter value shown in a.) and that renewed
during the call exchange is calculated.
c.) The deduction is transformed to a time (hour, minute, second, milli-second) format.
d.) The transformed time is added to the Call Start Time registered in a.)-End.
 The counter-based time is renewed in every 16.384 msec.
33. Maximum number of active calls available for concurrent storage in the system memory is 28,000 per
system. When a call is completed, the record is sent to the output device and is removed from the memory.
34. If an overflow occurs, calls are allowed to complete but are not recorded.
35. To output the FCCS-related billing data, the external SMDR terminal should be compatible also with the
IMX text format patterns.
36. When a station originates an outgoing trunk call using a trunk in the remote node (the station and the trunk
belong to an FCCS network), the billing information for the station to trunk connection is not recorded.
37. Because the FCCS service achieves a completely fused link between multiple distant nodes, intrastation
connections and node-to-node connections are theoretically considered identical.
38. When a line connection is established on the FCCS link, the billing data concerned is collected fully in the
called station-side node, not in the calling station side. The collected data is then transmitted to the SMDR
terminal as the call finishes.
39. Multiple Center Nodes can be assigned on a FCCS network for centralized billing purposes.
40. Transmission of call base table with 220 bytes.
SMDR Terminal RS232C / 10 BASE-TTo SMDR Port 
						

							NEAX2400 IMX Business Features and Specifications
Page 476NDA-24221, Issue 3
S-10 Station Message Detail Recording (SMDR)
Service Conditions (cont’d)
41. The figures on the following pages show the Service Conditions of Polling Method, focusing on when
CCIS links are involved.
Example 1
 Node A (Fusion - Center Node) Collects the billing information of Nodes B and C via FCCS using the
polling method.
Example 2
 Node A tries to collect the billing information of Node B and Node C via FCCS, using the polling method
(Node A cannot collect the billing information of Node C via FCCS).
 Node C sends the billing information via CCIS, ignoring polling from Node A.
 Node C deletes the Point Code (CCIS) of Node A for centralized billing data when required to send billing
information for polling from Node A.
Node C
FCCS - Center Node
IMX
SMDR 
EquipmentFCCS Network
IMX
36456
26549
55213
75213Polling
Billing information of Node B
Node ANode B FCCS
IMX FCCS
P
ol
li
ng
79879
8
4651
35
164
656
5
Node CFCCS
Billing information of 
Node B
: Fusion Call Control Signal (FCCS)
: Common Channel Inter-Office Signaling (CCIS)
Node B
FCCS - Center Node
CCIS - Center Node
IMX
SMDR 
EquipmentNode A
Node B
FCCS Network
Polling
01010
10001
01010
19010
Billing information of 
Node BIMX
Node B FCCS
Polling
IMX
DPC0:
Node ANode C
ignores
Billing information of 
Node CCCIS
: Fusion Call Control Signal (FCCS)
: Common Channel Inter-Office Signaling (CCIS)0
10
1
0
1
0
0
0
1
0
10
1
0
1
9
0
1
0 
						

							NEAX2400 IMX Business Features and Specifications
NDA-24221, Issue 3
Page 477
Station Message Detail Recording (SMDR) S-10
Service Conditions (cont’d)
Example 3
 Node A tries to collect the billing information of Node B via FCCS, using the polling method (Node A
cannot collect the billing information of Node B via FCCS).
 Node B sends the billing information via CCIS, ignoring polling from Node A.
 Node B deletes the Point Code (CCIS) of Node C for centralized billing data when required to send billing
information for polling from Node A.
ignores
Node C
FCCS - Center Node
IMX
SMDR 
EquipmentFCCS Network
IMX
08
93
2
135
44
30
56
5
954
54
Polling
B
i
lli
ng in
for
ma
tion
 of N
ode
 B
Node AFCCS
non IMX
C
CI
S
Node C
CC
IS
: Fusion Call Control Signal (FCCS)
: Common Channel Inter-Office Signaling (CCIS)
DPC0:
Node C
SMDR 
Equipment CCIS - Center Node
Node B 
						

							NEAX2400 IMX Business Features and Specifications
Page 478NDA-24221, Issue 3
S-10 Station Message Detail Recording (SMDR)
Service Conditions (cont’d)
Example 4
 Node A collects the billing information of Node B and Node C via FCCS, using the polling method.
 Node A sends the billing information of Node A, Node B and Node C.
Node C
CCIS - Center Node
non IMX
SMDR 
EquipmentFCCS Network
IMX
36456
55213
25454
75213
Billing information of 
Nodes A, B, C
Node D
IMX CCIS
79
87
9
8
46
51
38
92
5
4
65
65
Node C Billing information of Node B
: Fusion Call Control Signal (FCCS)
: Common Channel Inter-Office Signaling (CCIS)
FCCS - Center Node
36456
26546
85454
7521336456
26546
55213
75213
Node A
SMDR 
EquipmentIMX
DPC0:
Node D
Polling
FCCS
Node B01010
10001
01010
10110
B
il
l
i
ng 
in
for
ma
ti
on 
of 
N
ode 
C
Pol
li
ng
FCCS
FCCS 
						

							NEAX2400 IMX Business Features and Specifications
NDA-24221, Issue 3
Page 479
Station Message Detail Recording (SMDR) S-10
Service Conditions (cont’d)
Example 5
 Node A collects the billing information of Node B and Node C via FCCS, using the polling method (Billing
information of Node B cannot be collected).
 Node B sends the billing information to Node D via CCIS, ignoring polling from Node A.
 Node B deletes the Point Code (CCIS) for Node D when Node B wants to send billing information for
polling from Node A.
CCIS - Center Node
non IMX
SMDR 
Equipment FCCS Network
IMX
Billing information of Node B
Node D CCIS
: Fusion Call Control Signal (FCCS)
: Common Channel Inter-Office Signaling (CCIS)
FCCS - Center Node36456
26546
55214
75213
Polling
FCCS
FCCS
FCCS SMDR 
Equipment
DPC0:
Node D
ignores
Node A
Node C
IMX
Node C
Po
ll
i
ng
Bil
lin
g
 in
f
o
r
ma
t
i
o
n
 
o
f 
No
d
e
 
C7
98
79
84
651
3
516
5
46
889
Node C
IMX
Node B 
						

							NEAX2400 IMX Business Features and Specifications
Page 480NDA-24221, Issue 3
S-10 Station Message Detail Recording (SMDR)
Service Conditions (cont’d)
Example 6
 Node A collects the billing information of Node B, Node C and Node D, which are stored in Node B by
polling method.
 Node D sends the billing information to Node B.
 SOCKET Interface (LAN Interface) Conditions:
42. SMDR data can be output via LAN cable.
43. A maximum of four SMDR apparatuses per node are available.
44. When providing this feature with LAN interface, IMX text format must be designated by the ASYDL
command (SYS 1, Index 578-581, b0).
45. SMDR apparatus with LAN interface and SMDR apparatus with RS232C interface cannot be connected
to the same node.
Interactions
1. If LCR(S) is provided, the LCR(S) access code is listed in ARNP. If an outgoing route is not used in
LCR(S), then list the OGCA access code in ARNP. 
2. To test SMDR output, it is recommended that a serial printer or breakout box be used to determine if the
system is sending data.
3. CALL TRANSFER-ALL CALLS [C-11]: Either the first station, last station, or split billing is allowed
with SMDR. Split billing provides a separate call record for both before and after a call transfer. 
4. ATTENDANT CAMP-ON WITH TONE INDICATION [A-1]: The called station number is recorded for
incoming C.O. calls via the Attendant Console (RRI 2 of ARSC). To record the time a destination station
is on a call, split billing or last station billing is required. With split billing, the time the Attendant Console
is on the call is separated from the time the destination station is on the call. For last station billing, the
destination station is charged with the entire time of connection.
CCIS - Center Node
non IMX
SMDR 
Equipment FCCS Network
IMX
Billing information of 
Node B, D
CCIS
: Fusion Call Control Signal (FCCS)
: Common Channel Inter-Office Signaling (CCIS)
DPC: Destination Point Code
FCCS - Center Node
36546
55213
25454
75213
Polling
FCCS
FCCS
FCCS SMDR 
Equipment
DPC0:
Node B
ignoresNode A
Node C
IMX
Node C
P
o
l
l
ing
Bil
lin
g
 
in
f
or
m
a
t
i
on
 
o
f
 
No
de
 
C7
98
79
8i
16
5
4
682
5
46
565
IMX
Node B
36456
26543
25454
75213Billing information of 
Node D
Node C
Node D