HOW TO SET SMDR on NIU 2

[cuneyt2919]

Hi all,
I ve very little know-how about SMDR and call information...
Now i have 16 NIU cards and want to to use it for incoming calls (Who called whom, and when ??)
Can someone tell me the commands in order, for how i can set it for RS232 connection between niu and PC for NIULIM23(shown below)
And also how will it effect to sytem performance? Is it dangerous for the system, approximately 3 million calls per month?

[tt]
<IODDP;
I/O DEVICE DATA
NODE IODEV/SUBFS BPOS/EQU SIPOS TYPE/USAGE STATUS AUTH
SYSN - 001-0-70 - - IN SERVICE
SYSN SYSDISK1 001-0-70-0 3 ADTX IN SERVICE
SYSSUBFS11
TM-SF
SYSN SYSDISK2 001-0-70-0 4 ADTX IN SERVICE
SYSSUBFS21
SYSN SYSTERMINAL 001-0-70-1 - MML - 7
SYSN SYSTERMINAL1 001-0-70-2 - MML - 7
SYSN SYSTERMINAL2 001-0-70-3 - MML - 7
SYSN LIM1ETH 001-0-70-4 - NETWORK/OUT IN SERVICE
SYSN LIM1MML 001-0-70-4 - NETWORK/MML - 7
NIULIM2 - 002-0-70 - - IN SERVICE
NIULIM2 LIM2ETH 002-0-70-4 - NETWORK/OUT IN SERVICE
NIULIM2 LIM2MML 002-0-70-4 - NETWORK/MML - 7
NIULIM3 - 003-0-70 - - IN SERVICE
NIULIM3 LIM3ETH 003-0-70-4 - NETWORK/OUT IN SERVICE
NIULIM3 LIM3MML 003-0-70-4 - NETWORK/MML - 7
NIULIM4 - 004-0-60 - - IN SERVICE
NIULIM4 LIM4ETH 004-0-60-4 - NETWORK/OUT IN SERVICE
NIULIM4 LIM4MML 004-0-60-4 - NETWORK/MML - 7
NIULIM5 - 005-0-70 - - IN SERVICE
NIULIM5 LIM5ETH 005-0-70-4 - NETWORK/OUT IN SERVICE
NIULIM5 LIM5MML 005-0-70-4 - NETWORK/MML - 7
NIULIM7 - 007-0-70 - - IN SERVICE
NIULIM7 LIM7ETH 007-0-70-4 - NETWORK/OUT IN SERVICE
NIULIM7 LIM7MML 007-0-70-4 - NETWORK/MML - 7
NIULIM9 - 009-0-70 - - IN SERVICE
NIULIM9 LIM9ETH 009-0-70-4 - NETWORK/OUT IN SERVICE
NIULIM9 LIM9MML 009-0-70-4 - NETWORK/MML - 7
NIULIM11 - 011-0-70 - - IN SERVICE
NIULIM11 LIM11ETH 011-0-70-4 - NETWORK/OUT IN SERVICE
NIULIM11 LIM11MML 011-0-70-4 - NETWORK/MML - 7
NIULIM12 - 012-0-60 - - IN SERVICE
NIULIM12 LIM12ETH 012-0-60-4 - NETWORK/OUT IN SERVICE
NIULIM14 - 014-0-42 - - IN SERVICE
NIULIM14 LIM14ETH 014-0-42-4 - NETWORK/OUT IN SERVICE
NIULIM14 LIM14MML 014-0-42-4 - NETWORK/MML - 7
EVM - 014-1-50 - - IN SERVICE
EVM EVM-IPU-TEST1 014-1-50-1 - MML - 7
EVM EVM-IPU-TEST2 014-1-50-2 - MML - 7
NIULIM15 - 015-0-70 - - IN SERVICE
NIULIM15 LIM15ETH 015-0-70-4 - NETWORK/OUT IN SERVICE
NIULIM15 LIM15MML 015-0-70-4 - NETWORK/MML - 7
NIULIM17 - 017-0-70 - - IN SERVICE
NIULIM17 LIM17ETH 017-0-70-4 - NETWORK/OUT IN SERVICE
NIULIM17 LIM17MML 017-0-70-4 - NETWORK/MML - 7
NIULIM19 - 019-0-70 - - IN SERVICE
NIULIM19 LIM19ETH 019-0-70-4 - NETWORK/OUT IN SERVICE
NIULIM19 LIM19MML 019-0-70-4 - NETWORK/MML - 7
NIULIM21 - 021-0-70 - - IN SERVICE
NIULIM21 EVMTEST 021-0-70-1 - MML - 7
NIULIM21 LIM21ETH 021-0-70-4 - NETWORK/OUT IN SERVICE
NIULIM21 LIM21MML 021-0-70-4 - NETWORK/MML - 7
NIULIM22 - 022-0-42 - - IN SERVICE
NIULIM22 LIM22ETH 022-0-42-4 - NETWORK/OUT IN SERVICE
NIULIM23 - 023-0-70 - - IN SERVICE
NIULIM23 CIL 023-0-70-3 - OUT IN SERVICE
NIULIM23 LIM23ETH 023-0-70-4 - NETWORK/OUT IN SERVICE
NIULIM23 LIM23MML 023-0-70-4 - NETWORK/MML - 7
EN



<lIDAP;


LICENCE TAG ALLOWED USED
ACD-AGENT 1000 573
ANALOGUE-EXTENSION 64 63
ANCD-FEATURE 1 0
APP-LINK-INTERFACE 24 16
CAS-EXTENSION 600 576
CCM-ETH-INTERFACE 36 14
CCM-V24-INTERFACE 1 0
DIGITAL-EXTENSION 640 593
DISA-NUMBER 1 0
DUPLICATED-GS 1 0
EXTERNAL-LINE-CAS-ANA 24 24
EXTERNAL-LINE-ISDN-NET 5760 0
EXTERNAL-LINE-ISDN-USR 300 240
EXTERNAL-LINE-QSIG 1050 810
GROUP-SWITCH-LINK 108 55
LICENSE-FILE 1 0
NET-SERVICES 1 0
OM-ETH-INTERFACE 15 14
OM-V24-INTERFACE 20 5
RVA-INTERNAL 384 33
SMDR-V24-INTERFACE 10 0
TRAFFIC-MEASUREMENT 1 0
VM-V24-INTERFACE 16 0
END
[\tt]


Thanks for your answers
Regards..

 

[lancbomb]

Hi,

It's not dangerous, and dont think you should have any problems at all !

procedure as follows !

-------------------------


CALL LOGGING OVER NIU CARD

Red text - md110 initiate command.
Green text - md110 print command.
Black text - description.



1. IOEQI:EQU=1-0-60-04,IODEV=SMDR,TYPE=NETWORK,USAGE=OUT; IODDP
2. IONCI:IODEV=SMDR,USER=CIL-1,RPORT=700,IP=123.456.789.101; IODEV is the same IODEV entered in IOEQI. IP is the IP address of the Call Logging PC. RPORT is the Software port on the Call Logging PC. USER Watch out for the syntax for USER (it allows you to bend the syntax rules in IONCI, however when you re-use the USER parameter in command CLDFI it has to be the correct format). IONCP
3. CLDFI:IODEV=SMDR,FILE=CLRC,USER=CIL-1; IODEV is the same IODEV in IOEQI. FILE is any file name you want to use. USER is the USER from previous IONCI command. In this case CIL-1; CLDFP
4. CLOHI:FILE=CLRC,FORM=2,DMPSIZ=2; FILE has to be the same FILE initiated in CLDFI in this case CLRC. FORM is still set to 2. DMPSIZ is the buffer size before the MD transmits the CIL info i.e. 2/3 seem to be best. CLINP
5. CLODI:FILE=CLRC,DIAL=ALL,ORIG=ALL,LOGABN=NO; FILE is the FILE entered in CLDFI. DIAL states to which called parties calls are to be registered. (Set to ALL unless informed otherwise). ORIG is the identity of the calling parties against which calls are to be logged (usually set to all but could be using ranges. Set to all unless informed otherwise). LOGABN is set to yes if abandoned calls require logging otherwise (and more usually) set to no. CLINP
6. CLTGI; CLTGI starts the call logger. CLINP (IN SERVICE Should read YES) CLDFP (DEVICE STATE Should read ACTIVE)


The above describes initiating call Logging from an NIU card that has already been configured with IP address e.t.c.
The NIU is positioned in 1-0-60 and call logging has not previously been initiated, If the call logging is existing the values in CLODI may be varied to match the original set up.

The output was verified using Ericsson software Smdrsrvr.exe available via Phil Doherty.



“Dodgy bits”

The NIU didn’t appear to want to go into service with call logging unless the logging PC (in this case my PC with the Smdrsrvr.exe program running) was available and the relevant service running on the PC.
The CLINP reported IN SERVICE but the CLDFP reported PASSIVE when no PC was available. After various restarts this was still the case. Therefore I launched the Smdrsrvr.exe software on my PC and ended then reinitiated the call logging output. This seemed to work well and any subsequent disconnection of my PC caused alarm EC 344 and CLINP/CLDFP to show OUT OF SERVICE e.t.c. On reconnection of my PC the alarm took a couple of minutes to receipt and the output started ok.

The Ericsson software Smdrsrvr.exe seems to lock up Comm ports, which only clear on a restart of the PC.

 

[cuneyt2919]

Thanks a lot lancbomb. I Will try it

Rgrds.

 

[lancbomb]

kool
no problem
and thanks

 

[cuneyt2919]

Hi lancbomb,
we set it for V24 as we have no licence for SMDR ethernet..But thx for the procedure,it's very helpful for me...
And now i get records like this. But i can't see the durations for the calls...
Here is a part of call logging.

[tt]

09151057 0054 NI 5623 3471641 00 69837
09151058 0016 N 66763 2742889 00 66763
09151058 0007 NI 5623 4155866 00 67269
09151058 0003 NI 5625 096004028 00 69732
09151058 0017 NI 5623 3272523 00 69760
09151058 0048 NI 5625 096004001 00 69714
09151058 0016 NI 5624 3410993 00 67143
09151058 0014 NI 5621 099011008 00 69908
09151058 0019 NI 5621 5659669 00 69811
09151058 0003 0038 06516181 4264 00 092011019
09151058 0009 NI 5624 3638700 00 69844
09151058 0003 NI 5621 5397636 00 67134
09151058 0007 NI 5624 3305237 00 69899
09151058 0037 NI 5621 5701847 00 67231
09151058 0006 T 69571 2239970 00
09151057 0018 T 66180 0256219127 00
09151057 0006 NI 5626 001010005 00 69846
09151057 0001 0055 52633110 5403 00 092001010
09151057 0001 NI 5626 0252413566 00 67157
09151058 0001 0055 52633110 5403 00 092024020
09151058 0008 NI 5626 001010053 00 67151
09151058 0013 NI 5626 0252214225 00 69913
09151058 0021 NI 5626 0366212189 00 67272
09151058 0019 T 69286 0248234221

[/tt]

Can you help me ,how i can see the call duration?
Greetings...

 

[cuneyt2919]

Hi i sent it with monotext but the paper size is bigger than this area, i think..

So, i can give two values by manually editing it.

09141441 0035 NI 5624 2859160 00 69826

09141441 0012 T 5484 3856674 00 5484

 

[lancbomb]

I've not logged on in a while to check this,

But from memory, the MD sends everything out, the CIL unit sort's calculates it out.

The MD will either output or not. It won't withold informattion.

HTH

LB

 

[cuneyt2919]

Hi again,What my partner told me is, the second column is the duration..
For exp: 0019 means; 1 minute + 9x6 seconds=1 minute,54seconds

0121 means 12 minutes+1x6seconds=12 minutes,6 seconds

Regards

Note: In our system , firstly, the call comes to Huntgroup 5621,5622... 5626)of IVR ports.. If the customer, wants to talk with an agent, IVR transfers the call to the ACD group..
So in this case;for exp: think that customer ANI is 04221234567
He calls 5621 (huntgroup) And the answering position is 69803 (member of hunt group)
When ivr transfer the call to the ADN -for exp 66123-

I think the CIL data will consist of two calls per call,
such as

1st record 09141440 0009 NI 5621 04221234567 00 69803
2nd record 09141440 0015 T 66123 04221234567 00 66123

Am i right? Or the 2nd record will be like this??

2nd record 09141440 0015 T 66123 5621 00 69803

Rgrds

 

[lancbomb]

not sure,...

as I said you need to know "exactly" what is coming out of the CIL port from the MD, by hooking up a PC to it and seeing the raw data

 

[aprasha]

[tt]
In BC10....

There are two importants PARNUMs important for CIL:

PARNUM 103: 0 -> Record dialied number in CIL
1 -> Record translated LCR number in CIL

PARNUM 122: 1 -> ONE second resolution is selected
6 -> SIX seconds resolution is selected

By the other side, you can see exactly de definition of the FORM you selected with CLFOP:FORM=form_number;

Field Identifier Field Minimum Maximum
A Access Code 1 1 5
B Access Code 2 1 5
C Access Code 2/ISDN CBC 1 5
D Account Code 1 15
E Calling Number 1 20
F Authorization Code 1 6
G Dialled Number 1 20
H Single Character Condition Code 1 1
I Double Character Condition Code 2 2
J End Date 4 4
K Call Duration Time 4 5
L Operator Queue Time 1 2
M Space 1 20
N Call metering 1 4
O Queue Time Busy External Line 1 2
P End Time 4 4
Q ISDN Call by Call 1 3
R Operator System Access Code 1 2
S Transit Network Selection Code 1 3
T External Line ID 1 9
U 10 Digit Market Data 1 1 10
V 10 Digit Market Data 2 1 10
W 10 Character Data 1 10
X Ring Time Duration 1 3
Y Queue Time Duration 1 3
Z Triple Character Condition Code 3 3


There are 4 Predefined Forms:
FORM 0 -> FP15 format
FORM 1 -> MDFP15 format
FORM 2 -> ASB501 standard format
FORM 3 -> ASBU MDFP15 format
FORMs 4, 5 and 6 -> Flexibles format

And also, you can define your own FORM (only Forms 4, 5 or 6) with CLFOC :FORM=, DATA= [,APPEND=YES]; (If no Append is defined, FORM will be erased and written with the new DATA. If APPEND=YES is defined, then the DATA will be appended at the end of the actual DATA).

For example, my own FORM:
CLFOC:FORM=6,DATA=1-4J&2-1M&3-4P&4-1M&5-5K&6-1M&7-5N&8-1M&9-20E&10-1M&11-20G&12-1M&13-6T;

And the Condition Codes (Field identifiers H and I)description:

The condition code is the key element in the call record. It designates the type of call that was made.

Condition codes may be either one, two or three characters wide, and are supported as shown below. The condition codes that are two or three characters wide allow a more detailed description of the call case.

Condition code (type of call that consists of one/ two characters):

( ) Outgoing call
(A) Call handled by a PABX operator
(D) Extremely long call duration
(G) Call has been connected with alternative route selection
(H) Recall to route
(I) Incoming call or tandem call
(J) Internal call
(L) Conference call
(M) Least cost routing
(N) Dialled party not equal to answering party
(Q) Malicious Call Tracing
(R) Intrusion
(S) Dynamic Route Allocation
(T) Transferred call
(V) Data call
(W) Call terminated due to route optimization
(X) External follow me
(Y) Call established due to route optimization
(Z) DISA call
(VJ) Internal data call
(VI) Incoming data call
(VO) Outgoing data call
(DO) Long outgoing call
(DA) Long PABX operator extended call
(DI) Long incoming call
(DJ) Long internal call
(DV) Long data call
(DX) Long external follow me call
(NJ) Dialled party is not the answering party on an internal call
(NI) Incoming DID call when the answering party was not the dialled party
(CI) Abandoned non-DISA call
(CJ) Abandoned internal call
(CO) Abandoned outgoing call in a private network
(CZ) Abandoned DISA call

Condition code (type of call that consists of three characters)-> (BC11 or Above):

(NCI) Abandoned non-DISA call, dialled party is not the answering party.
(NCJ) Abandoned internal call, dialled party is not the answering party.
(NCZ) Abandoned DISA call, dialled party is not the answering party.
[/tt]