NEC Neax 2400 Ipx Feature Programming Manual

							NEAX2400 IPX Feature Programming ManualPage 668NDA-24297, Issue 1
S-9 Station Hunting - Terminal
Programming
STEP 1:ASHP- Assign the required data to the Assignment Pilot Hunting command:
TN: Tenant Number
STN: Station Number
SECRET: Secretary Station Number (if necessary)
*STN: Station numbers of the stations included in the Pilot group.
Note:* Indicates the order of a station in the group.
STEP 2:APHN- Assign Phantom Number (PHSTN) to the pilot station:
TN: Tenant Number
REAL STN: Station Number of the pilot station
PH: Phantom Number mode
0 = Used individually
1 = Used as the pilot number (for station hunting)
CNT (PHSTN): Phantom Station Number
For Pilot Stations within a Hunt Group to deny hunting function for incoming call from a station
STEP 1:ASYD- System Data 1, Index 439, Bit 7.
0/1=Incoming call from station is hunted/not hunted.
STEP 2:ASFC- Allow the service feature restriction class (SFI 181) for pilot station which denies hunting
function for a incoming call from station.
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 69, b5:
Hunting Group when transferred party is busy (Station Hunting after Call Forwarding - Busy Line):
0 = Hunt in Transferring Party’s Group
1 = Hunt in Transferred Party’s Group
STEP 2:ASHPN- This data must be assigned to the NCN.
Assign the Hunt Group using Telephone Number.
UGN: User Group Number
TELN: Telephone Number in Hunting Group
SECRETARY TELN: Telephone Number of Secretary Station (if necessary)
STEP 3:APHNN- Assign Phantom Telephone Number (PHTELN) to the pilot station.
UGN: User Group Number
TELN: Telephone Number of the pilot station
PH: Phantom Number Mode
0 = Used individually
1 = Used as the pilot number (for station hunting)
PHTELN: Phantom Telephone Number
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. 
						

							NEAX2400 IPX Feature Programming Manual
NDA-24297, Issue 1Page 669
Station Hunting - Terminal S-9
FCCS Programming (cont’d)
Note 2:Multi PHTELNs (maximum of 16) can be assigned per TELN. Select whether to use each PHTELN for
station hunt or not by the“PH”parameter. 
						

							NEAX2400 IPX Feature Programming ManualPage 670NDA-24297, Issue 1
S-10 Station Message Detail Recording (SMDR)
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 IPX Feature Programming Manual
NDA-24297, Issue 1Page 671
Station Message Detail Recording (SMDR) S-10
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 IPX Feature Programming ManualPage 672NDA-24297, Issue 1
S-10 Station Message Detail Recording (SMDR)
Service Conditions (cont’d)
31. Additional hardware is required.
32. When either of the 2 parties goes On-Hook (or presses Transfer key, Hold key, Answer key, Over key)
during Station-to-Station Calling [S-11], output of the billing information will be completed.
33. Call Time specification:
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.
34. The maximum number of calls available for concurrent storage in the system memory (active calls), is:
1-IMG/4-IMG system 28,000
IPX-U 47,000
35. If an overflow occurs, calls are allowed to complete but are not recorded.
36. To output the FCCS-related billing data, the external SMDR terminal should be compatible also with the
IMXtextformatpatterns.
37. 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.
38. Because the FCCS service achieves a completely fused link between multiple distant nodes, intrastation
connections and node-to-node connections are theoretically considered identical.
SMDR Terminal RS232C / 10 BASE-TTo SMDR Port 
						

							NEAX2400 IPX Feature Programming Manual
NDA-24297, Issue 1Page 673
Station Message Detail Recording (SMDR) S-10
Service Conditions (cont’d)
39. 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.
40. Multiple Center Nodes can be assigned on a FCCS network for centralized billing purposes.
41. Transmission of call base table with 220 bytes.
42. Since Release 5 software, when the user performs system changeover (using MBR key, CMOD command
or etc.), system massages (26-V, 26-W) are displayed. However, there are no defective conditions.
43. 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.
Node C
FCCS - Center Node
IPX
SMDR 
EquipmentFCCS Network
IPX
36456
26549
55213
75213Polling
Billing information of Node B
Node ANode B FCCS
IPX FCCS
Po
lli
ng
79879
84651
35164
6565
Node CFCCS
Billing information of 
Node B
: Fusion Call Control Signal (FCCS)
: Common Channel Inter-Office Signaling (CCIS) 
						

							NEAX2400 IPX Feature Programming ManualPage 674NDA-24297, Issue 1
S-10 Station Message Detail Recording (SMDR)
Service Conditions (cont’d)
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 B
FCCS - Center Node
CCIS - Center Node
IPX
SMDR 
EquipmentNode A
Node B
FCCS Network
Polling
01010
10001
01010
19010
Billing information of 
Node BIPX
Node B FCCS
Polling
IPX
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
00
0
1
0
1
01
0
19
01
0 
						

							NEAX2400 IPX Feature Programming Manual
NDA-24297, Issue 1Page 675
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.
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.
ignores
Node C
FCCS - Center Node
IPX
SMDR 
EquipmentFCCS Network
IPX
08
9
32
1
354
4
30
565
954
54
Polling
B
i
l
li
ng 
in
for
ma
ti
on 
of 
Node 
B
Node AFCCS
non IPX
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
Node C
CCIS - Center Node
non IPX
SMDR 
EquipmentFCCS Network
IPX
36456
55213
25454
75213
Billing information of 
Nodes A, B, C
Node D
IPX CCIS
7
98
7
9
84
651
3
89
25
4
656
5
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 
EquipmentIPX
DPC0:
Node D
Polling FCCS
Node B01010
10001
01010
10110
Bi
ll
ing
 
in
fo
rm
a
tio
n
 
of
 
N
ode
 
C
P
ollin
g
FCCS
FCCS 
						

							NEAX2400 IPX Feature Programming ManualPage 676NDA-24297, Issue 1
S-10 Station Message Detail Recording (SMDR)
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 IPX
SMDR 
Equipment FCCS Network
IPX
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
IPX
Node C
P
ol
lin
g
B
il
l
in
g
 
in
f
orm
a
ti
o
n
 o
f
 
N
od
e
 C7
9
87
9
8
4
651
3
51
65
46
88
9
Node C
IPX
Node B 
						

							NEAX2400 IPX Feature Programming Manual
NDA-24297, Issue 1Page 677
Station Message Detail Recording (SMDR) S-10
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
1. SMDR data can be output via LAN cable.
2. A maximum of four SMDR apparatuses per node are available.
3. When providing this feature with LAN interface, IMX text format must be designated by the ASYDL
command (SYS 1, Index 578-581, b0).
4. SMDR apparatus with LAN interface and SMDR apparatus with RS232C interface cannot be connected
tothesamenode.
NEAX2400 IPX-UMG Conditions
1. When the system is IPX-UMG, SMDR equipment (PC) is connected via RS232C/LAN to SP.
2. The maximum of calls available for concurrent storage in the system memory is:
IPX-UMG 47,000 times the number of LMGs
Relocation condition for SMDR
When relocating a SMDR equipment to other node, reassign the billing information-related data. The relocation
conditions are shown below.
1. Make sure there is no billing information in the each node from Center Node before changing the SMDR
location. (Ex. Make sure billing information is output to the SMDR by sending test signal.)
2. An exact billing information may not be output to SMDR while changing SMDR location.
3. When removing the SMDR equipment from the Center Node, first of all, delete the billing information-
related data, and also when connecting the SMDR to new-Center Node, the user must, first of all, assign
appropriate billing information-related data.
CCIS - Center Node
non IPX
SMDR 
Equipment FCCS Network
IPX
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
IPX
Node C
P
ol
li
n
g
B
ill
in
g
 
in
f
o
rm
a
ti
on
 o
f
 
N
o
d
e
 C79
8
79
8
i1
65
46
825
465
6
5
IPX
Node B
36456
26543
25454
75213Billing information of 
Node D
Node CNode D