CDR passing incorrect or multiple Records Associated with SIP Trunk Calls

[wallot]

Howdy

My CM 8.1.3 is in certain instances, calls are that associated with SIP calls, from SIP stations, 2 to 3 CDR records per call are being presented. Most are presenting the TAC on one end or the other in some of the records rather than the called station ID.

The call accounting folks are pleading ignorance which may be factual.

I've been here before but that was 5 or 6 years ago, can't recall what the fix was.

 

[AvayaTier3]

CM cdr output format choices are here:
Command: change system-parameters cdr

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

 Node Number (Local PBX ID): 2                     CDR Date Format: month/day
      Primary Output Format: unformatted   Primary Output Endpoint: CDR1
    Secondary Output Format:
           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? n
                  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

     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
Remove '+' from SIP Numbers? y

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

bsh

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

 

[wallot]

Thanks but this is a custom, we are aware of this form, just not finding where or what is causing the CM CDR to send 2 to 3 records per call from a SIP station.

 

[AvayaTier3]

post the records and include the condition code for each.

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

bsh

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

 

[wallot]

AvayaTier3

These are the 3 records for the same call.

Not my issue yet but, only the first line is being processed giving the TAC 1025 for one end of the call. My query is, why 3 (actually 5) records are being sent for one call.

This is a SIP to SIP station call.

2023-Apr-10 07:41:06.165 TXDATA: 041023 0741 0000 9 6843489 1025 1 1025 187
2023-Apr-10 07:41:06.196 TXDATA:
2023-Apr-10 07:42:33.184 TXDATA: 041023 0742 0014 9 6843489 6843489 1 1025 187
2023-Apr-10 07:42:33.205 TXDATA:
2023-Apr-10 07:42:33.224 TXDATA: 041023 0742 0014 C 6843489 6844059 1 1025 156

Thanks!

 

[wallot]

OK, got this figure out except for one call type.

Being it was only sending multiple call records for SIP phone calls, the solution was to disable 2 settings in the off-pbx-telephone configuration-set, the CDR for Origination
and CDR for calls to EC500 Destination set to n. See the attached SOLN.

https://files.engineering.com/getfi...ac-4279-95ec-a56bfd9f051d&file=PSN020086u.pdf

My last issue is that calls coming into a VDN then to a vector Auto Attendant, I get the first call shows the calling ID and the TAC as the destination, then, the second part shows the VDN extension and the destination extension. This only happens when the call is directed to an extension the is reached via a tie line to a second CM.

 

[wallot]

As it turns out, the last call records where we were getting 2 for every call, is as designed as per Avaya. No way to fix it when 2 CMs are tie'd together.