Collecting CDR from S8700 to Unix

srk2ola · Jan 4, 2013

Hi Everyone,

I used to read and get information from this forum, but this is my first post,
Im using a unix box to recollect the CDR from my Avaya S8700, (something like post 684030)

On the Avaya CM everything is configured to send this CDR to the unix box, using a customized format, another thing, is the secondary CDR

On the unix box, Im using the command:
#nc -l 64001 >> test.txt

My problem is... even when I have several percent of records in the buffer of the CM CDR, everytime I run the "nc" command I only get the hour and date of connection and the next records... when what I want to get are the records in the buffer...

What do you suggest?

Avaya CM
R015x.02.1.016.4
Running on 2 S8710 with G650's

Unix
Fedora 13

AvayaTier3 · Jan 4, 2013

Hardware platform? Definity / CM software version?

A great teacher, does not provide answers, but methods to teach others "How and where to find the answers"

bsh

39 years Bell, AT&T, Lucent, Avaya
Tier 3 for 29 years and counting
[URL unfurl="true"]http://bshtele.com[/url]

srk2ola · Jan 4, 2013

Hi, we have 2 S8800 and some G650's,

The CDR is configured in the Ip-services

Software Versions:

Code:

Operating system:  Linux 2.6.18-128.AV07PAE i686 i686
                Built:  Aug 19 04:58 2009

             Contains:  02.1.016.4
        CM Reports as:  R015x.02.1.016.4
    CM Release String:  S8800-015-02.1.016.4

UPDATES:
Update ID                       Status       Type    Update description
------------------------------- ------------ ------- ---------------------------
02.1.016.4-18250                activated    cold    patch 18250 for 02.1.016.4


Platform/Security ID            Status       Type    Update description
------------------------------- ------------ ------- ---------------------------


 CM Translation Saved:	 2013-01-03 22:00:08

 CM License Installed:	 2012-02-14 15:46:39

     CM Memory Config:	 Extra Large

IPServices:

Code:

                                   IP SERVICES
 Service     Enabled     Local        Local       Remote      Remote
  Type                   Node         Port        Node        Port
AESVCS        y      procr            8765
CDR1                 procr            0       CDR1            10001
CDR2                 procr            0       CDR2            64001

CDR Settings

Code:

display system-parameters cdr                                   Page   1 of   2
                            CDR SYSTEM PARAMETERS

 Node Number (Local PBX ID):                       CDR Date Format: month/day
      Primary Output Format: customized    Primary Output Endpoint: CDR1
    Secondary Output Format: customized  Secondary Output Endpoint: CDR2
           Use ISDN Layouts? n                   Enable CDR Storage on Disk? n
       Use Enhanced Formats? n      Condition Code 'T' For Redirected Calls? n
      Use Legacy CDR Formats? y                 Remove # From Called Number? n
Modified Circuit ID Display? n                             Intra-switch CDR? y
                  Record Outgoing Calls Only? n     Outg Trk Call Splitting? y
  Suppress CDR for Ineffective Call Attempts? y       Outg Attd Call Record? y
      Disconnect Information in Place of FRL? n      Interworking Feat-flag? n
 Force Entry of Acct Code for Calls Marked on Toll Analysis Form? n
                                    Calls to Hunt Group - Record: member-ext
Record Called Vector Directory Number Instead of Group or Member? n
Record Agent ID on Incoming? n       Record Agent ID on Outgoing? y
     Inc Trk Call Splitting? n
  Record Non-Call-Assoc TSC? n           Call Record Handling Option: warning
      Record Call-Assoc TSC? n   Digits to Record for Outgoing Calls: dialed
   Privacy - Digits to Hide: 0               CDR Account Code Length: 15

display system-parameters cdr                                   Page   2 of   2
                            CDR SYSTEM PARAMETERS

     Data Item - Length         Data Item - Length         Data Item - Length
 1: date             - 6   17: code-dial        - 4   33: in-crt-id        - 3
 2: space            - 1   18: space            - 1   34: space            - 1
 3: duration         - 4   19: tsc_flag         - 1   35: contact-uri      - 20
 4: space            - 1   20: space            - 1   36: space            - 1
 5: sec-dur          - 5   21: dialed-num       - 23  37: time             - 4
 6: space            - 1   22: space            - 1   38: line-feed        - 1
 7: calling-num      - 15  23: feat-flag        - 1   39:                  -
 8: space            - 1   24: space            - 1   40:                  -
 9: calltype         - 1   25: out-crt-id       - 3   41:                  -
10: space            - 1   26: space            - 1   42:                  -
11: acct-code        - 15  27: clg-pty-cat      - 2   43:                  -
12: space            - 1   28: space            - 1   44:                  -
13: bandwidth        - 2   29: in-trk-code      - 4   45:                  -
14: space            - 1   30: space            - 1   46:                  -
15: bcc              - 1   31: auth-code        - 13  47:                  -
16: space            - 1   32: space            - 1   48:                  -

                              Record length = 146

AvayaTier3 · Jan 4, 2013

The way you have this programmed will dump call records out of the CM memory buffer as the calls are completed. By design, they are using the port and the IP address which should be an IP endpoint with some type of collection software. You cannot pull information from the buffer. The switch decides when to dump the records.

There is an option to store the records on the s8800 server's hard disk which may work better for what you are trying to do.

A great teacher, does not provide answers, but methods to teach others "How and where to find the answers"

bsh

39 years Bell, AT&T, Lucent, Avaya
Tier 3 for 29 years and counting
[URL unfurl="true"]http://bshtele.com[/url]

srk2ola · Jan 4, 2013

Thanks,

But after enabling the CDR Storage on Disk, how I will retrieve this info?

AvayaTier3 · Jan 4, 2013

Code:

change system-parameters cdr                                    Page   1 of   1 
                            CDR SYSTEM PARAMETERS

 Node Number (Local PBX ID): 1                     CDR Date Format: month/day
      Primary Output Format: unformatted   Primary Output Endpoint: DISK    

           Use ISDN Layouts? n                   Enable CDR Storage on Disk? y

Avaya Aura Communication Manager
Feature Description and Implementation
555-245-205
Issue 7
Release 5.2
May 2009

Pg 82

CDR logins
Use a CDR login to retrieve CDR records stored on the Communication Manager
server. When creating a CDR login on the Communication Manager
Security >Administrator Accounts of the Server Administration Interface, enter
CDR_User as the login group and leave the additional groups field blank.

Pg 480

Call Detail Recording
Avaya Aura Communication Manager
Feature Description and Implementation
May 2009

A filesync, a reset system 2 (cold restart), or a reset system 4 (reboot) occurs
After one of the above events occur the following actions take place:

- The Current CDR file is closed and it becomes an archive CDR file
- The file permissions change from read/write (rw) for root and read only for
members of the CDR_User group to:
- Owner (root): Read/Write/Execute (rwx)
- Group (CDR_User): Read/Write (rw-)
- World: none (---)
- The 'C-' prefix is removed from the front of the file name
- For a main server, a new Current CDR file is created
- For an LSP or an ESS server, a new Current CDR file is created only if the LSP
or the ESS server is controlling one or more gateways or port networks.

File naming conventions for Survivable CDR
The Survivable CDR data files have the following naming conventions:
tssssss-cccc-YYMMDD-hh_mm
where:
- t is populated with an L for an LSP, an E for an ESS server, or an S for a
main server
- ssssss is populated with the least significant six digits of the System ID or
SID. The SID is a unique number in the RFA license file used to identify the
system. The SID for a server can be viewed by using one of the following
methods:
- Use the statuslicense -v BASH command.
- Use the command display system-parameters customer-options on
the SAT.
- cccc is populated with the least significant four digits of the Cluster ID
(CL ID) or Module ID (MID). To display the MID for the server:
- Use the statuslicense -v BASH command.
- YY is populated with the two digit number of the year the file was created.
- MM is populated with the two digit number of the month the file was created.
- DD is populated with the two digit day of the month the file was created.
- hh is populated with the hour of the day the file was created based on a 24
hour clock.
- mm is populated with the number of minutes after the hour when the file was
created.
The Current CDR file uses the same naming convention except the name is prefixed
with a 'C-'.
--------------------------------------------------------------------------------
Administrator Accounts -- Add Login: CDR Access Only

This page allows you to create a login that is intended to be used with the
survivable CDR feature only.

- The add was successful for login: cdrusr.

Login name: cdrusr
Password: cdrusr2013
Primary group: CDR_Usr
Linux shell: /bin/bash
Home directory: /var/home/ftp/CDR
--------------------------------------------------------------------------------
dadmin@s8500c> loginReports -lu cdrusr
Group Name CDR_User
Profile Name --
Other Groups -
Authentication -
ASG Account Lock N/A
Shadow Locked No
Pam_Tally Locked No
Shell /bin/bash
Home /var/home/ftp/CDR
PW Min Days 0
PW Max Days 99999
PW Warn Days 7
PW Last Changed Jan 04, 2013
PW Next Change Allowed Jan 04, 2013
PW Expires Never
Account Expires Never
Last Login Jan 04, 2013 -- rhost[192.168.0.200], tty[pts/1]
--------------------------------------------------------------------------------
dadmin@s8500c> su - cdrusr
Password: cdrusr2013
[cdrusr@s8500c ~]$ id
[cdrusr@s8500c ~]$ pwd
/var/home/ftp/CDR
[cdrusr@s8500c ~]$ ls -lR
.:
total 4
lrwxrwxrwx 1 root root 53 Jan 4 16:38 C-S041643-0001-130104-16_38 -> /var/home/ftp/CDR/current/C-S041643-0001-130104-16_38
drwxr-x--- 2 root CDR_User 4096 Jan 4 16:38 current

./current:
total 4
-rw-r----- 1 root CDR_User 18 Jan 4 16:38 C-S041643-0001-130104-16_38
[cdrusr@s8500c ~]$ cat C-S041643-0001-130104-16_38
01/04/13 16:38:15
--------------------------------------------------------------------------------
No call records yet. This is a lab server.

A great teacher, does not provide answers, but methods to teach others "How and where to find the answers"

bsh

39 years Bell, AT&T, Lucent, Avaya
Tier 3 for 29 years and counting
[URL unfurl="true"]http://bshtele.com[/url]

srk2ola · Jan 4, 2013

Thanks you very much for your help,,

I dont think this would resolve my issue but I will try in another way...

If someone has another point of view, I'll appreciate your help...

Thanks guys

Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

Collecting CDR from S8700 to Unix

srk2ola

Technical User

AvayaTier3

Technical User

srk2ola

Technical User

AvayaTier3

Technical User

srk2ola

Technical User

AvayaTier3

Technical User

srk2ola

Technical User

Similar threads

Part and Inventory Search

Sponsor