Avaya IP Office SMDR setup and CSV formats
This page covers the Avaya Avaya IP Office 500 (CSV) and Avaya IP Office Phone (CSV) variants in Advanced PBX Data Logger. Each section gives the connection settings, the parser to select and the fields the logger extracts for reports or a database; where the setup steps are the same for every variant they are given once. The settings apply to our logger; other call accounting software may expect a different configuration.
Quick facts
| Item | Avaya IP Office SMDR setup and CSV formats |
|---|---|
| Variants on this page | Avaya IP Office 500 (CSV), Avaya IP Office Phone (CSV) |
| Interface | LAN. The PBX accepts a connection on TCP port 180; the logger connects to the PBX IP address. |
| Port | 180 |
| Parsers | Avaya IP Office 500 (CSV), Avaya IP Office Phone (CSV) |
| Fields extracted | 31 to 49 |
| Other Avaya systems | Avaya Communication Manager, Definity and G3 CDR formats, Avaya Merlin 1030, 3070 and Magix SMDR formats |
Variants on this page
- Avaya IP Office 500 (CSV) · LAN, port 180, 49 fields
- Avaya IP Office Phone (CSV) · LAN, port 180, 31 fields
Settings from the manufacturer's documentation
Taken from Avaya Delta Server SMDR Fields, avaya Delta Server user manual, avaya ip office smdr enu, avaya rddt. Values are those stated in the documentation; confirm them against your firmware release.
| Setting | Documented value |
|---|---|
| fields provided only by direct IP Office SMDR, not by the older Delta Server SMDR | External Targeting Cause, External Targeter Id, External Targeted Number |
| External Targeting Cause codes | e.g. HG=Hunt Group, U=User, LINE=Line, AA=Auto Attendant, ICR=Incoming Call Route, RAS=Remote Access Service; reason codes fb/fu/fnr/fdnd for forward-on-busy/unconditional/no-response/DND, plus CfP/Cfd conference and XfP/Xfd transfer, MT mobile twinning, TW teleworker |
Record format notes
- Account is the last account code attached to the call, and IP Office account codes may contain alphanumeric characters (not digits only).
- AuthValid/AuthCode fields cover authorization codes: AuthValid is 1 for a valid code or 0 for invalid, and AuthCode is the code used or 'n/a' if none was used.
- Cost-per-unit values used for Advice of Charge (AoC) are stored as 1/10,000th of a currency unit, e.g. a call cost of 1.07 per unit is entered as 10700 on the line.
Avaya IP Office 500 (CSV)
Parser: Avaya IP Office 500 (CSV)
Connection: LAN. The PBX accepts a connection on TCP port 180; the logger connects to the PBX IP address. Port 180.
Fields extracted: 49
Configuring Avaya IP Office
Replacing Avaya Delta Server
Recently Avaya have stripped off Delta Sever application which used to serve as SMDR. Our PBX Data Logger allows to replace this application and is very user friendly.
Data items: Avaya IP Office 500 (CSV)
| Description | Data type | Column name |
|---|---|---|
| Call time | datetime | CALL_TIME |
| Call data | datetime | CALL_DATE |
| Call time only | datetime | CALL_TIME_ONLY |
| Call duration | datetime | CALL_DURATION |
| Call duration (s) | integer | CALL_DURATION_S |
| Ring duration (s) | integer | RING_S |
| Ring duration | datetime | RING |
| Call type | string | CALL_TYPE |
| Direction | string | DIRECTION |
| Is internal | string | FLAG1 |
| Caller phone | string | CALLER_PHONE |
| DNIS | string | DNIS |
| Source | string | FLAG4 |
| Destination | string | FLAG5 |
| Extension | string | EXT |
| Dialed phone | string | DIALED_PHONE |
| Account | string | ACC |
| Call ID | integer | CALL_ID |
| Call ID | string | FLAG7 |
| Continuation | string | FLAG6 |
| Party1 device | string | PARTY1_DEVICE |
| Party1 name | string | PARTY1_NAME |
| Party2 device | string | PARTY2_DEVICE |
| Trunk | string | TRUNK |
| Party2 name | string | PARTY2_NAME |
| Line | string | LINE |
| CO | string | CO |
| Caller name | string | FLAG2 |
| Called name | string | FLAG3 |
| Hold time | integer | HOLD_TIME |
| Park time | integer | PARK_TIME |
| Auth valid | integer | AUTH_VALID |
| Auth code | string | AUTH |
| User charged | string | USER_CHARGED |
| Call charge | float | COST |
| Call charge | string | CURRENCY |
| Amount at last user change | float | AMOUNT_LAST_USER_CHANGE |
| Call units | string | CALL_UNITS |
| Units at last user change | string | UNITS_LAST_USER_CHANGE |
| Cost per unit | float | COST_PER_UNIT |
| Mark up | string | MARK_UP |
| External targeting cause | string | EXT_TARGET_CAUSE |
| External targeter ID | string | EXT_TARGET_ID |
| External targeter number | string | EXT_TARGET_NUM |
| Server IP address of the caller extension | string | CALLER_SERVER_IP |
| Unique call id for the caller extension | string | CALLER_CALL_ID |
| Server IP address of the called extension | string | CALLED_SERVER_IP |
| Unique call id for the called extension | string | CALLED_CALL_ID |
| Call time (UTC) | datetime | CALL_TIME_UTC |
Sample record
As delivered by the system; phone numbers, names and public addresses are masked.
2009/02/02 13:37:29,00:00:22,6,913xxxxxxxxx,I,2020,343xxxx,,0,101xxxx,0,T9005,Line 5.6,V9544,VM Channel 44,0,0,,,,,,,,,,,,,, 2009/02/02 13:37:41,00:00:54,0,914xxxxxxxxx,I,2000,343xxxx,,0,101xxxx,1,T9005,Line 5.7,V9512,VM Channel 12,0,0,,,,,,,,,,,,,, 2009/02/02 13:38:10,00:00:22,6,913xxxxxxxxx,I,2020,342xxxx,,0,101xxxx,0,T9005,Line 5.1,V9545,VM Channel 45,0,0,,,,,,,,,,,,,,
Avaya IP Office Phone (CSV)
Parser: Avaya IP Office Phone (CSV)
Connection: LAN. The PBX accepts a connection on TCP port 180; the logger connects to the PBX IP address. Port 180.
Fields extracted: 31
Configuring Avaya IP Office
Replacing Avaya Delta Server
Recently Avaya have stripped off Delta Sever application which used to serve as SMDR. Our PBX Data Logger allows to replace this application and is very user friendly.
Data items: Avaya IP Office Phone (CSV)
| Description | Data type | Column name |
|---|---|---|
| Call time | datetime | CALL_TIME |
| Call duration | datetime | CALL_DURATION |
| Call duration (s) | integer | CALL_DURATION_S |
| Ring duration | integer | RING |
| Direction | string | CALL_TYPE |
| Direction | string | DIRECTION |
| Is internal | string | FLAG1 |
| Caller phone | string | CALLER_PHONE |
| Extension | string | DNIS |
| Extension | string | EXT |
| Called phone | string | CALLED_PHONE |
| Dialed phone | string | DIALED_PHONE |
| Account | string | ACC |
| Call ID | integer | CALL_ID |
| Continuation | string | FLAG2 |
| Party1Device | string | PARTY1_DEVICE |
| Party1Name | string | PARTY1_NAME |
| Party1Device | string | PARTY2_DEVICE |
| Party1Name | string | PARTY2_NAME |
| Hold time | integer | HOLD_TIME |
| Park time | integer | PARK_TIME |
| Auth valid | string | FLAG3 |
| Auth code | string | AUTH |
| User charged | string | USER_CHARGED |
| Call charge | float | CALL_CHARGE |
| Currency | string | CURRENCY |
| Amount at Last User Change | float | LAST_CHARGE |
| Call units | string | CALL_UNITS |
| Units at Last User Change | string | LAST_UNITS |
| Cost per Unit | float | COST_UNIT |
| Mark up | string | MARK_UP |
Sample record
As delivered by the system; phone numbers, names and public addresses are masked.
2014/07/30 11:44:01,00:00:02,3,,I,400,67767,,0,100xxxx,0,E212,Name ,T9002,Line 2.1,0,0,,,,,,,,,,,,, 2014/07/30 11:43:53,00:00:05,1,202,O,20067767,20067767,12,0,100xxxx,0,E202,BigTom,T9006,Line 6.0,0,0,,,,,,,,,,,U,BigTom, 2014/07/30 11:44:51,00:00:02,1,20067767,I,400,67767,,0,100xxxx,0,E212,Name ,T9002,Line 2.2,0,0,,,,,,,,,,,,,
Connecting the logger
All variants on this page use the same connection settings; the steps below apply to each of them.
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 Avaya IP Office). The port number should match the port that you have defined within the PBX (180 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
180
192.168.1.220:180
Selecting the correct parser for Avaya IP Office 500 (CSV)

Avaya IP Office 500 (CSV)
Avaya IP Office 500 (CSV)
Avaya programming software
Avaya IP Office is programmed with IP Office Manager, which comes from Avaya or your dealer, not from AGG Software. SMDR output is switched on there; PBX Data Logger receives the records.
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 Avaya systems
Avaya IP Office 406 (CSV)Avaya G3 V9
Avaya MERLIN 1030
Avaya Communication Manager, Definity and G3 CDR formats
Avaya Merlin 1030, 3070 and Magix SMDR formats
Avaya MERLIN 3070
All supported PBX 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.
Related topics: Advanced PBX Data Logger
hereCall logging Call accounting SMDR to SQL SMDR Listener Cables and signals
