NEC Neax 2400 Imx Feature Programming Manual

							NEAX2400 IMX Feature Programming Manual
ND-70184 (E), Issue 3
Page 637
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 Feature Programming Manual
Page 638ND-70184 (E), 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 Feature Programming Manual
ND-70184 (E), Issue 3
Page 639
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 Feature Programming Manual
Page 640ND-70184 (E), 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 
						

							NEAX2400 IMX Feature Programming Manual
ND-70184 (E), Issue 3
Page 641
Station Message Detail Recording (SMDR) S-10
Interactions (cont’d)
5. LEAST-COST ROUTING-3/6-DIGIT [L-5]: SMDR will record the digits sent rather than the digits
dialed.
6. The destination station is recorded on SMDR for the following features:
CALL FORWARDING [C-2, 3, 5]
CALL PICKUP [C-7, 30]
7. CALL FORWARDING-INTERCEPT [C-25]: An incoming trunk call responds to Call Forwarding-
Intercept to the Attendant Console. SMDR records the call as if it is a direct call to the Attendant Console.
8. NIGHT CONNECTION-FIXED/FLEXIBLE: Calls terminated to these stations are recorded on SMDR. 
9. OUTGOING TRUNK QUEUING [O-2]: SMDR records the outgoing call when the system recalls the
user and the digits are sent, not when the trunk is queued.
10. REMOTE ACCESS TO SYSTEM [R-2]: The incoming route and trunk number is recorded as the calling
party. If FORCED ACCOUNT CODE [F-7] is used, it will be recorded on SMDR. REMOTE ACCESS
TO SYSTEM via a DID will not record FORCED ACCOUNT CODE on SMDR.
11. TRUNK-TO-TRUNK CONNECTION [T-10] and TIE LINE ACCESS [T-3]: SMDR records an
incoming TIE Line that uses TRUNK-TO-TRUNK CONNECTION to make an outgoing call. The TIE
Line route and trunk number is recorded as the calling party. The outgoing route is programmed for SMDR
in ARTD, not the incoming TIE Line route. 
12. CALL WAITING-TERMINATING [C-12]: SMDR will begin recording the call when the call is
answered, not when a Call Waiting Tone is heard.
13. ADD ON CONFERENCE - 8 PARTY [A-121]: When output of the billing information for the C.O. call
and station-to-station call is not restricted on either station or port for the calling/called party, the billing
information for the station-to-station call is output to SMDR.
Programming
STEP 1:ASYD - System Data 1, Index 20, Bit 7. Charging to a call transferred by CALL FORWARDING-
OUTSIDE Service 0/1: Charging is made to the caller of the transferred call / charging is made to the
station that has set CALL FORWARDING-OUTSIDE service. System Data 1, Index 32. Assign data
86H. Bit 7 enables SMDR service, Bit 2 will record the route taken, Bit 1 records tenant information.
Optional assignments may include Bit 5 and Bit 6. 
System Data 1, Index 32, Bit 5. Is the Route Access code recorded? 0/1: No/Yes. 
System Data 1, Index 32, Bit 6. Is the number sent or number dialed recorded in SMDR? 0/1: Number
Sent/Number Dialed.
System Data 1, Index 33. Assign this index for Split Billing. If Split Billing is used, assign 00H. If
Total Billing is used, Bits 3 & 4 represent the following: 00: Telephone called first. 01: Telephone
called last. 10: Telephone receiving call from an Attendant Console.
Bit 5 must be assigned as data “1” to provide total billing for incoming calls. 
Bit 6 must be assigned as data “1” to provide total billing for outgoing calls. 
System Data 1, Index 34. Assign data 01H or 21H. Bit 0 enables RS-232C transmission. 
System Data 1, Index 157. Outgoing Trunk, Soft Hold Timer. The point in time when the system will
recognize an outgoing call as answered. Default is 18 seconds. Because of interaction with momentary
pressing of the hook-switch, this data may be reassigned as 31H for 2 seconds. Take the SMDR aspect
into consideration when reassigning this data. 
System Data 1, Indexes 288-295
Designation of the attributes of the SMDR. 
						

							NEAX2400 IMX Feature Programming Manual
Page 642ND-70184 (E), Issue 3
S-10 Station Message Detail Recording (SMDR)
Programming (cont’d)
SMDR output port will be designated. For this designation, the attributes of the terminal that outputs
the detail call information should have been designated by indexes 117-123. (Assigned by the AIOC
command.) 
Also for detecting a fault of the SMDR, set the SMDR fault detect timer.
Index 288 = Charging information port of SMDR A.
Bit 4: IOC Equipment Number (0/1=No.0/No.1)
Bit 5: Expanded SMDR Output (0/1=Out/In Service)
Index 289 = SMDR fault detect timer of SMDR A.
Index 290 = Charging information port of SMDR B.
Bit 4: IOC Equipment Number (0/1=No.0/No.1)
Bit 5: Expanded SMDR Output (0/1=Out/In Service)
Index 291 = SMDR fault detect timer of SMDR B.
Index 292 = Charging information port of SMDR C.
Bit 4: IOC Equipment Number (0/1=No.0/No.1)
Bit 5: Expanded SMDR Output (0/1=Out/In Service)
Index 293 = SMDR fault detect timer of SMDR C.
Index 294 = Charging information port of SMDR D.
Bit 4: IOC Equipment Number (0/1=No.0/No.1)
Bit 5: Expanded SMDR Output (0/1=Out/In Service)
Index 295 = SMDR fault detect timer of SMDR D.
System Data 2, Index 3. Bit 0 enables SMDR registration per tenant. 
System Data 2, Index 3. Optional assignments for station-to-station connection. Bit 6, 0/1: Calling &
Called output/Called output only. Bit 7, 0/1: -/SMDR Output (STN-STN) is in service.
STEP 2:ASYDL - System Data 1, Index 576
Bit 0. Centralized Billing-Fusion (Polling Method): 0/1 = Not/To be provided. Required both for
Center Node and each Local Node.
Bit 1. SMDR for station to station connections in a self-node 0/1=output/not output (Note 1)
Bit 2. 0 = RS-232C interface is used.
System Data 1, Index 577.
Fusion Point Code (FPC) of Center Node.
Provided that “1” is flagging in Bit 0 of Index 576 (System Data 1), let every Local Node recognize its
belonging Center Node for centralized billing-Fusion. Assign data on Center Node FPC at each Local
Node. Given this data, the Local Nodes can acknowledge the SMDR polling only from the Center
Node specified here (the polling from other parties will be ignored).
At the Center Node, assign 00H.
System Data 1, Index 578-581, Bit 0. Assign proper data (0/1) for regulation of output text format
pattern for centralized billing-Fusion. Index 578 corresponds to SMDR A, 579 to SMDR B, 580 to
SMDR C and 581 to SMDR D. The pattern to be adopted will be:
Bit 0 = 0: ICS text format.
Bit 0 = 1: IMX format. 
						

							NEAX2400 IMX Feature Programming Manual
ND-70184 (E), Issue 3
Page 643
Station Message Detail Recording (SMDR) S-10
Programming (cont’d)
System Data 1, Index 582, Bit 0-3. Assign the number of nodes to be polled at once.
0000 = 1 0001 = 1 0010 = 2 0011 = 3 0100 = 4 0101 = 5
0110 = 6 0111 = 7 1000 = 8 1111 = 8 
(Note 2)
Note 1:
This data is valid when the data is assigned at SYS1, Index 512.
Note 2:
For the numbers more than 8, assign the data value as 8.
System Data 1, Index 583, Bit 0-2. The timing for Fusion billing data transmission from the node that
accommodates the outgoing trunk or the node that accommodates the called station to the node that
accommodates the calling party (Valid when SYS 1, INDEX583, b7 = 0 in ASYDN).
Bit 2 1 0 Bit 2 1 0
0 0 0 = 8 seconds 1 0 0 = 8 seconds
0 0 1 = 2 seconds 1 0 1 = 10 seconds
0 1 0 = 4 seconds 1 1 0 = 12 seconds
0 1 1 = 6 seconds 1 1 1 = 14 seconds
System Data 1, Index 608-639.
Fusion Point Code (FPC) of SMDR polling destination. 
						

							NEAX2400 IMX Feature Programming Manual
Page 644ND-70184 (E), Issue 3
S-10 Station Message Detail Recording (SMDR)
Programming (cont’d)
After the Center Node (multiple CN: possible on a network) is assigned for centralized billing-Fusion,
let the Center Node recognize its polling destination (specified by the FPC), referring to the table
below. In the table, each bit represents Fusion Point Code ranging from 1 to 253. When “1” is set, the
FPC is specified as the polling destination.
Indexb7b6b5b4b3b2b1b0
608
7654321 -
609151413211109 8
61023 22 21 20 19 18 17 16
61131 30 29 28 27 26 25 24
61239 38 37 36 35 34 33 32
61347 46 45 44 43 42 41 40
61455 54 53 52 51 50 49 48
61563 62 61 60 59 58 57 56
61671 70 69 68 67 66 65 64
61779 78 77 76 75 74 73 72
61887 86 85 84 83 82 81 80
61995 94 93 92 91 90 89 88
620103 102 101 100 99 98 97 96
621111 110 109 108 107 106 105 104
622119 118 117 116 115 114 113 112
623127 126 125 124 123 122 121 120
624135 134 133 132 131 130 129 128
625143 142 141 140 139 138 137 136
626151 150 149 148 147 146 145 144
627159 158 157 156 155 154 153 152
628167 166 165 164 163 162 161 160
629175 174 173 172 171 170 169 168
630183 182 181 180 179 178 177 176
631191 190 189 188 187 186 185 184
632199 198 197 196 195 194 193 192
633207 206 205 204 203 202 201 200
634215 214 213 212 211 210 209 208
635223 222 221 220 219 218 217 216
636231 230 229 228 227 226 225 224
637239 238 237 236 235 234 233 232
638247 246 245 244 243 242 241 240
639- - 253 252 251 250 249 248 
						

							NEAX2400 IMX Feature Programming Manual
ND-70184 (E), Issue 3
Page 645
Station Message Detail Recording (SMDR) S-10
Programming (cont’d)
System Data 1, Index 641, Bit 0. Type of the station number for the ICS text format.
0/1=Physical Station Number/Telephone Number.
System Data 1, Index 641, Bit 3. Kind of the route number for the ICS text format.
0/1=Physical Route Number/Logical Route Number.
STEP 3:SOCKET Interface (Lan Interface) Programming
System Data 1, Index 529: Assign the methods of parity check
b0: 0/1=No parity check/Odd parity
b1: 0/1=No parity check/Even parity
Index 576, b2=1 (LAN interface is used)
Index 578-581, b4: Assign the usage of the SMDR.
Index 578, b4: 0/1=SMDR A is not used/used
Index 579, b4: 0/1=SMDR B is not used/used
Index 580, b4: 0/1=SMDR C is not used/used
Index 581, b4: 0/1=SMDR D is not used/used
STEP 4:ASYDN - This data should be set “0” for ASYDL, SIS 1, Index 583, b0-2. Index 583, bit 7.
The node for saving fusion billing data:
0 = The node accommodating the calling party
1 = The node accommodating the outgoing trunk or the called station
STEP 5:AIOC - Assign the function and attribute data of the IOC ports. 
This data is not necessary when using LAN interface.
STEP 6:ARTD - CDN 10:SMDR. Enable outgoing routes to be included for SMDR registration. CDN
16:SMDR2. Determination, on a per-route basis, of what type of connection will be registered by
SMDR. Also remember to flag the LCR (S) flag route. For outgoing only routes, assign data “0”. For
incoming routes, assign data “2”. For bothway trunk routes, assign data “1” only. CDN 56:SMDR3.
Detailed billing for outgoing (tandem). CDN 69. Detailed billing for incoming (tandem). With regard
to CDN 56:SMDR3 and CDN 69:SMDR4, see below.
In the network shown above, PBX B functions as a tandem switch. In this example, parameters SMDR
3 and SMDR 4 for RT 1 of PBX B should be assigned as “1” for the following reasons:
 When Station C places a call to Station A:
 Since SMDR collects billing information on the outgoing trunk at PBX C, billing information
on the outgoing trunk of RT 1 is not required at PBX B (SMDR 3 = 1).
 When Station A places a call to Station C:
 At PBX B, SMDR collects billing information on the outgoing trunk of RT 2, and therefore
billing information on the incoming trunk of RT 1 is not required (SMDR 4 = 1).
PBX A PBX A PBX A
Station AStation C RT 1 RT 2
No SMDR SMDR
SMDR 
						

							NEAX2400 IMX Feature Programming Manual
Page 646ND-70184 (E), Issue 3
S-10 Station Message Detail Recording (SMDR)
Programming (cont’d)
STEP 7:ASFC - Assign data “1” to SFI14 of a Service Feature Class, the traffic of which is to be registered on
SMDR (Trunk Basis). Assign data “1” to SFI58 of a Service Feature Class the traffic of which is to be
registered on SMDR (STN to STN Basis).
Note:
When SMDR for station-to-station calling is not used, both stations in communication must be restricted at the SFI58.
STEP 8:ARNP - For the routes flagged for SMDR in ARTD, list the route number and the Outgoing Trunk
access code (OGC) or Outgoing Trunk Advance (OGCA) access code here. If LCR(S) is used, list the
route numbers and the LCR(S) access code. 
STEP 9:AMND - Assign the number of digits the register is to receive for every dialing code. List the Toll
Number ID Data code for the system to distinguish the Toll Dialing patterns for SMDR registration.
The dialing code listings are identical for LCR(S). Refer to the AMND descriptions for LCR-3/6-
DIGIT [L-5] and TOLL RESTRICTION-3/6-DIGIT [T-7].
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)
AT D F - Assign time difference data if the time between the nodes and the UCT (Universal
Coordinated Time) may not be identical on a FCCS network. The assigned data (time difference
margin [Plus/Minus, Hour, Minute] between each FPC and the UCT) is to be written in Network Data
Memory (NDM) of the Network Control Node (NCN).
Note:
When using ASYDL or ASYDN to program an FCCS feature, the basic programming of ASYD is required in addition
to ASYDL or ASYDN.