Outbound CDR issue

[seahawk04]

I have a customer with an Option11C Rls 3.0 There is an issue with some of the outbound CDR records. Most are coming through fine, but we have some that are coming through with incomplete records. Below is a printout of 2 "good" records vs. 2 "bad" records. Any ideas why these are being cut? Is it a timer issue in the RDB? Thanks in advance....

N 115 00 5589 T002022 003.0.00.09 04/10 16:03 00:00:18 A 19024109395055
& 0000 0000

070410
N 116 00 5589 T002022 003.0.00.09 04/10 16:03 00:01:06 A 19024109394444
& 0000 0000

%070410
S 117 00 5579 T002022 003.0.00.12 04/10 16:05 00:00:04 A 190295
& 0000 0000
%070410
S 118 00 5579 T002020 003.0.00.12 04/10 16:04 00:01:34 A 19023
& 0000 0000

 

[bigindian65]

Are you sure they are bad records? I know if I break dialtone w/ MCI & it is costed, I'm getting charged the 1st minute, whether I dialed the wrong arecode and hung up before entering other digits, or completing the call, it shows on my reports.

 

[seahawk04]

No...not 100% sure they are bad records. I was just wondering if there was a timer setting that could be extended, that perhaps these folks were taking their time when dialing or were dialing "too fast" and that the call was being completed before the full record was recorded.

 

[bigindian65]

Actually, I see the time there, first one @ 4 seconds looks reasonable, the one for a minute and 1/2 to 19023 is strange

 

[acewarlock]

Thats not a 1 1/2 min call, thats 2 seperate calls.
The S denotes START record.

They arent BAD CDR records, there just incomplete because the call didn't finish dialing the number.

The NTP's explain in detail how to read them.