CDR in G430

[tototinho]

Anybody knows how to active CDR in the Avaya G430, The following commands are already configured:

- Ch ip-services
- Ch node-names
- Ch sys CDR

But when I set the data-module, doesn’t work … I don’t know what I set in the line “port”.

Could help me?!

 

[mojoputter]

The CDR in the G430 is only used for SLS..is that what your attempting to use it for..?

 

[tototinho]

How do I get the ticket from CDR? I’m not using the SLS mode. I just want the information form detail’s from calls. But I use Billing.

 

[AvayaTier3]

System: Standard          Software Version: R014x.00.5.742.0
------------------------------------------------------------
The example below is s8300B running CM4.0.5, with g700 media-gateway
s8300 uses "procr" is used in place of clan - network address is 192.168.0.25
call records are continuously sent to "cdr1" 192.168.0.102 port 5112
call records are continuously sent to "cdr2" 192.168.0.112 port 9000
------------------------------------------------------------
display system-parameters customer-options                      Page   5 of  11 
                                OPTIONAL FEATURES

Processor Ethernet? y
------------------------------------------------------------
list node-names                                                        Page   1 

                        NODE NAMES

Type     Name              IP Address
IP       cdr1              192.168.0.102                           
IP       cdr2              192.168.0.112                             
IP       procr             192.168.0.25
------------------------------------------------------------
display system-parameters cdr                                   Page   1 of   2 
                            CDR SYSTEM PARAMETERS

 Node Number (Local PBX ID): 1                     CDR Date Format: month/day
      Primary Output Format: unformatted   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? y
      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? y                  Inc Attd Call Record? y
  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: time             - 4   17: node-num         - 2   33:                  - 
 2: duration         - 4   18: ins              - 3   34:                  - 
 3: cond-code        - 1   19: ixc-code         - 3   35:                  - 
 4: code-dial        - 4   20: bcc              - 1   36:                  - 
 5: code-used        - 4   21: ma-uui           - 1   37:                  - 
 6: dialed-num       - 15  22: res_flag         - 1   38:                  - 
 7: calling-num      - 10  23: tsc_ct           - 4   39:                  - 
 8: acct-code        - 15  24: tsc_flag         - 1   40:                  - 
 9: auth-code        - 7   25: space            - 1   41:                  - 
10: space            - 2   26: date             - 6   42:                  - 
11: frl              - 1   27: space            - 1   43:                  - 
12: in-crt-id        - 3   28: vdn              - 5   44:                  - 
13: out-crt-id       - 3   29: return           - 1   45:                  - 
14: feat-flag        - 1   30: line-feed        - 1   46:                  - 
15: attd-console     - 2   31:                  -     47:                  - 
16: in-trk-code      - 4   32:                  -     48:                  - 

                              Record length = 111
------------------------------------------------------------
display ip-services                                             Page   1 of   4 

                                   IP SERVICES
 Service     Enabled     Local        Local       Remote      Remote 
  Type                   Node         Port        Node        Port   
CDR1                 procr            0       cdr1            5112 
CDR2                 procr            0       cdr2            9000 
display ip-services                                             Page   3 of   4 

                              SESSION LAYER TIMERS
  Service     Reliable  Packet Resp   Session Connect  SPDU  Connectivity
   Type       Protocol     Timer       Message Cntr    Cntr     Timer

 CDR1            n         60                3          3         60 
 CDR2            n         30                3          3         60 
------------------------------------------------------------
status cdr-link                                                                 
                                CDR LINK STATUS
                   Primary                      Secondary

       Link State: up                           up                             

      Date & Time: 2011/1 /20 7 :32:24          2011/1 /20 7 :32:24
  Forward Seq. No: 0                            0   
 Backward Seq. No: 0                            0   
CDR Buffer % Full:   0.00                         0.00
      Reason Code: OK                           OK

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

bsh

36 years Bell, AT&T, Lucent, Avaya
Tier 3 for 26 years and counting

http://bshtele.com

 

[tototinho]

I did all the steps, but it still didn’t working. There is a way to verify if CDR is running on the Prorc? I tried to use the telnet but without success.
FYI I didn’t have a clan, I have S8300D with MG 430.

Regards,

 

[AvayaTier3]

status cdr-link and post here


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

bsh

36 years Bell, AT&T, Lucent, Avaya
Tier 3 for 26 years and counting

http://bshtele.com

 

[tototinho]

Thanks for your help. Follow the st cdr:

status cdr-link
CDR LINK STATUS
Primary Secondary

Link State: down down
Number of Retries: 999 999
Date & Time: 0 /0 /0 0 :0 :0 0 /0 /0 0 :0 :0
Forward Seq. No: 0 0
Backward Seq. No: 0 0
CDR Buffer % Full: 13.75 4.19
Reason Code:

display ip services Page 1 of 3

IP SERVICES
Service Enabled Local Local Remote Remote
Type Node Port Node Port
CDR1 procr 0 CDR 5112
CDR2 procr 0 CDR2 9000

Thanks...

 

[AvayaTier3]

what hardware and software application do you have installed on your network that is configured to collect cdr call records?

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

bsh

36 years Bell, AT&T, Lucent, Avaya
Tier 3 for 26 years and counting

http://bshtele.com

 

[telcoguy]

Check the CDR application,looks like either the app is not listening on port 5112 and or 9000, or the server is not reachable from the gateway.Can you ping the server back and forth?

 

[tototinho]

Should the S8300 have the port 5112 or 9000 on listening status?