Nec SOPHO iS3000 (RS232, FDCR Format 4) SMDR/CDR format

This page shows how to get call records out of the Nec SOPHO iS3000 (RS232, FDCR Format 4) into Advanced PBX Data Logger: the connection settings, the parser to select and the 14 fields the logger extracts for reports or a database. The settings apply to our logger; other call accounting software may expect a different configuration.

Quick facts

PBX settings

FDCR over IP features "real-time" FDCR information over a TCP/IP interface. FDCR information is also available over a V.24 (RS232) interface. Either one of the two interfaces (TCP/IP or RS232) is active. It is not possible to use FDCR on both interfaces at the same time.

FCDR over RS232

The port to which the external call logging device is connected to must be projected with equipment type 25: FDCR (ASCII format).

FCDR over IP

To activate FDCR over IP, first FDCR must be started, using OM command STRTFR. System option LOSYSOP 60 (FDCR INSTEAD OF TOLL TICKETING) must be TRUE, else FDCR over IP can not be started. When LOSYSOP 60 is changed, it has no immediate effect. Only when the FDCR is started, the changed option will have effect.

For FDCR over IP, the FDCR IP device has to be assigned, using OM command ASDEVC (equipment type 33). The FDCR IP device is assigned to the same port (SHELF, BRD, CRT) as the V.24 FDCR device.

When (new) FDCR information is present, this information is sent to the connected user. The user must acknowledge each received FDCR record.

The FDCR record is prefixed by the record number (00 .. 99). This prefixed record number is not packed; the rest of the FDCR message is packed (just like with V.24). This record number is returned with the FDCR acknowledge, so the corresponding FDCR record can be removed.

Settings from the manufacturer's documentation

Taken from NEC SOPHO iS3000 Manual 201701. Values are those stated in the documentation; confirm them against your firmware release.

Switching SMDR output on, as documented

1. RS232/V.24 port must be projected as equipment type 25 (FDCR ASCII) to output FDCR
2. FDCR over IP requires FDCR started via STRTFR and LOSYSOP 60 TRUE; FDCR IP device assigned via ASDEVC equipment type 33 on same port as the V.24 FDCR device
3. An alternative binary-format equipment type also exists (not ASCII/type 25)

Record format notes

• Manual's term is 'FDCR output format version' (0-4); page title's 'Format 4' maps to output format version 4
• Version 4 = version 3 plus Group Call performance and seconds-resolution start time (new in SIP@Net 6.2); version 3 adds Cradle to Grave (SIP@Net 5.1)
• Record type value for the standard record in v4 is hex 8
• Record data is BCD-packed (2 digits per byte); only the IP-prefix record number is unpacked
• Party A/B type codes in v4 add Agent(6) and IVR line(7) to a base set of extension/operator/PSTN-tie-line/DPNSS/paging
• Accounting record password-indication codes: 0 normal, 1 password call, 2 call back call

Configuring PBX Data Logger as a TCP client

Our software should work in the TCP client mode. It means that our software will initiate connection with the PBX and the PBX will work as a server. Add one or several PBX IP addresses here (the IP address of the Nec SOPHO iS3000). The port number should match the port that you have defined within the PBX (2599 in the example below).

1. Add a new configuration with the TCP data source (if you didn't it before).

2. Configure the TCP settings as shown below.

192.168.1.220

2599

192.168.1.220:2599

Selecting the correct parser for Nec SOPHO iS3000 (RS232, FDCR Format 4)

Nec SOPHO iS3000 (RS232, FDCR Format 4)

Nec SOPHO iS3000 (RS232, FDCR Format 4)

Data items

Reports and a database

Once records arrive, the logger writes them to a text file or to any ODBC database in real time, or hands them to the PBX Reports utility for manual, scheduled and e-mailed reports with a built-in web server. See exporting call log data to a database for the database setup.

Related Nec systems

Note: Products and companies mentioned here are used only for definition and identification purposes and can be trademarks and/or registered trademarks of the respective companies.