BC11 - Call recording from V24 to Network ?

[vince62s]

I have 2 NIU cards on my MD110 BC11

One is used for:
V24 MML local serial port
V24 MML for modem
V24 OUT call recording
Network MML for FTP access

can I assign call recording to the same network port as the MML one?

if not, how can I assign traffic recording to the other network port of the other NIU card?
what kind of protocol is used in this case?

Thanks for help.

 

[SYAR2003]

e.g ( card 2 is 2-0-60 )
Initiation will be something like this.

IOPBI:node=SYSN2,BPOS=2-0-60;
CNBOC:BPOS=2-0-60,BRDNAM=NIU,NUMIND=16;
IONPC:EQU=2-0-60-4,IP= ,GATE= , MASK= ;
IOEQI:IODEV=SYSNET2,EQU=2-0-60-4,TYPE=NETWORK,USAGE=OUT;
IONCI:IODEV=SYSNET2,USER=CIL,IP=... ,RPORT= .... ;
(where IP is remote cil-server's and rport is the servers listening port)
CLDFI:FILE=TEST1,IODEV=SYSNET2,USER=CIL-0,PRIO=...;


You should also concider "CIL on HDU" setup
and use FTP to collect the files .

SYAR

 

[vince62s]

so basically you are telling me I cannot use the same network port for both MML and tax recording OUT, am I correct?

 

[SYAR2003]

I don't recommended to use the I/O board for applications.
Leave the I/O board for maintenance operations .
Telnet-MML/FTP/V.24-MML .
(you can use it , but ... as i said)


Have application ports on dedicated NIU's .


SYAR

 

[vince62s]

you said

You should also concider "CIL on HDU" setup
and use FTP to collect the files .

how does this work?

and what network port/IP address should I use? the same as the one defined on the NIU card?

how do I login in FTP on this port (what credentials?)

 

[SYAR2003]

CIL ON HDU.

The CIL buffer on HDU is an optional feature which stores the output of the CIL data and MIL events on an HDU for retrieval and processing later on. This feature can also be used together with other CIL output devices using the Ethernet or a V.24 port on the NIU/NIU2 output device. Depending on the selected priority of each CIL output device, the CIL data and MIL events can be output using a V.24 port, the Ethernet port on the NIU/NIU2 output device or stored on the HDU. This feature can be used as a primary CIL output device or as a CIL back up device.

This feature, however, cannot be used in conjunction with the call information logging output device using the V.24 interface on the SIU output device.

One advantage of storing the CIL data on the HDU, is that the data can be retrieved later at any time, and there is no need to e.g. dedicate a printer for the CIL print out.

Configuration:
The feature can be ordered separately and can be installed without interrupting the operation of the system.

An HDU (HDU7/2) is connected to the SCSI port on the NIU/NIU2/IPU board. As the CIL-functionality allows more than one CIL output device, there can be several HDUs connected to the system for this purpose (See section about Capacity). Each HDU can be connected to a separate NIU/NIU2/IPU board. Up to five HDUs can be connected in series to the one and the same SCSI bus, each defined as a unique HDU. See figure 2-1.

The other ports on the NIU/NIU2/IPU board, the V.24 ports, and the Ethernet port on the NIU/NIU2 board, can be used at the same time as an HDU is connected for storage of CIL-data. However for reliability purposes it is recommended to have the HDU(s), intended for storage of CIL-data, connected to an NIU/NIU2/IPU board which does not have any other connections, and if applicable in different LIMs.
Except for when the retrieval of the CIL-data shall take place via Ethernet, that Ethernet connection must be on the same NIU/NIU2 board, as the HDU for CIL-data is connected to.

File structure:
An HDU is logically connected to the system by stating a file system node name to it, including one, or up to eight sub file systems. A file path can then look like /CIL1/DAILY/. If the HDU to use is the same as the one for the system back-up (often used in small systems i.e. one or two LIM systems), the file system node name must be the default pre-defined /SYSN/USR1/ACS/CIL/.

Under a certain sub file system, the files containing the CIL-data are created. The beginning of the name of these files is pre-defined by CL-command, and the end of the name consists of the current date the file is created, including the year, month and day. A complete file path can then look like /CIL1/DAILY/DAY20000518.

Each sub file system occupies one partition on the HDU. An HDU can at the same time be used by other applications using other sub file systems and their partitions.

A logical affiliation between a CIL output device and a file path to an HDU is also made, and at the same time the priority of the output is defined. The priority states whether this HDU shall be the primary storage or the back-up storage of the CIL-data.


Storing of data:
The storing of CIL-data into files on the HDU, is made on the period defined, stating when the output shall be done. The output is made either for every day, every week (every saturday), or every month. A new data file in the CIL-directory on the HDU is created when there is a change in the day, week or month.

Which HDU and sub file system the file is created on, is based on the affiliation defined between a CIL output device and a file path.

The CIL-data is first temporary, internally stored into a 10 kbytes buffer, and when the buffer is full, or at the end of the given period, the CIL-data are stored on the HDU.


Retrieval of data:
The storing of CIL-data into files on the HDU, is made on the period defined, stating when the output shall be done. The output is made either for every day, every week (every saturday), or every month. A new data file in the CIL-directory on the HDU is created when there is a change in the day, week or month.

Which HDU and sub file system the file is created on, is based on the affiliation defined between a CIL output device and a file path.

The CIL-data is first temporary, internally stored into a 10 kbytes buffer, and when the buffer is full, or at the end of the given period, the CIL-data are stored on the HDU.



Initiation:

1 Initiate an NIU/NIU2 board.

2 Key command IOBPI to initiate the NIU/NIU2 board.

3 Key command IOEQI to initiate the input/output equipment on the board.

4 Key command IOSII to initiate a HDU which is connected to the I/O bus on NIU/NIU2. For more details, see command description for I/O DATA, IO.

5 Key command FIDII to create a directory for CIL data on HDU. For more details, see command description for FILE ADMINISTRATION, FI.

6 Key command CLDFI to affiliate the CIL directory with the CIL output file. For more details, see command description for CALL INFORMATION LOGGING, CL.

7 Key command CLOHI to affiliate the CIL output file to Call Information Logging, i.e. activate the CIL output file.

8 Key command CLODI to initiate the call criteria for the CIL output file.

9 Key command CLTGI to activate the CIL function.

Assign an IP adress for the NIU board for CIL.
Use FTP against the board to collect the files .
Login credentials for FTP is Username/password as the NIUX one .


SYAR