Avaya (Customized Output Format ACM 4.0+). SMDR/CDR data format and connection settings
This data is being extracted with help of the "Advanced PBX Data Logger" software only. It may not applicable for other software titles.
Avaya Communication Manager 4.X
1. Change node-name ip and add a new entry that hosts our PBX Data Logger application.
2. Change ip-services add a new entry of CDR1, and fill out the rest of the values. If you go to page three, you may need to set the "Secure" or "Reliable" option to N.
3. Change system cdr and setup the link how you want it outputted.
4. Disable the switch for "Legacy" output.
5. Our software expects date in MMDDYY format if nothing else is specified explicitly.
Our software does not support Reliable Session Protocol. You need to select another protocol type in your PBX
Avaya Call Manager v4+. Customized format.
This parser is designed for the following customized format.
The parser expects date in MMDDYY format (month/day/year).
In the Avaya Communication Manager (ACM) world, a device on the PBX needs to be specified that the CDR stream towards the logger goes out on. this can be a 'CLAN' card (a dedicated Avaya proprietary circuit back for network connectivity) or, in newer versions of Avaya Communication Manager, it can be 'Processor Ethernet' (the network interface of the code CM server).
As it turns out, in ACM 5.2.1 SP15 and to a certain level also in ACM 6.0.1. SP5 (these were the only versions we tested it on), when using Processor Ethernet for the CDR stream, it is not stable. ACM 5.2.1 dropped it a log (every 30 or so minutes) while ACM 6.0.1 dropped it about once a day.
Moving the CDR stream to a CLAN card fixed it. In ACM 6.2, it seems to be running stable on Processor Ethernet. It seems Avaya made some improvements between ACM 5.2.1, ACM 6.0.1 and finally resolved all issue in ACM 6.2.
|Description||Data type||Column name|
|Call duration (s)||integer||CALL_DURATION_S|
|Access code used||string||FLAG1|
|Access code dialed||string||FLAG2|
|Incoming circuit ID||string||FLAG4|
|Outgoing circuit ID||string||FLAG5|
|Incoming trunk code||string||TRUNK|
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.