SMDR not always correct

[troyz]

The SMDR output is not always correct, the phone numbers get mixed up sometimes.

Example:

2008/03/07 13:54:36,00:15:37,23,5344,O,17605001414,917605001414,,0,11090,0,E5344,Bernie Pawlicki,T9021,Line 1.21,0,0

2008/03/07 14:10:36,00:00:51,3,5354,O,,17605001414,,0,11268,0,E5354,Matt Larson,T9063,Line 2.23,0,0

I know that the first line E5344 did NOT dial the number listed in the line. I know this because they dialed the number using an autodial system that records the date and number called at that time. This happens to a small percentage of records (all users) but I still need to get this resolved.

Has anyone heard of this?

 

[kwing112000]

Are you using the delta server for this? what version delta server.

Kevin Wing
ACA- Implement IP Office
Carousel Industries

 

[troyz]

Looking at raw smdr file.

Version 5.2.16

 

[kwing112000]

I think there are some issues with that version. other will know.

Kevin Wing
ACA- Implement IP Office
Carousel Industries

 

[troyz]

System Info: IP412 4.1.9

 

[troyz]

Looks like 5.2.18 has some fixes for SMDR output. I will install that.

Thanks

 

[CLWINGET]

My experience, over the last 5 years, is that the Delta Server and CDR info - is sporadically accurate and sometimes unexplainable - constant upgrades to the Delta Server seem to be the only fix. And that is sketchy at best - at times.

I am very hesitant to trust the information.

Sorry.

 

[ProviderReborn]

5.2.18 reports extension numbers as trunks.
SO in call reports I see T9701 or similar. NOT GOOD.

ACA - IP Office Implement
ACA - IP Telephony
CCENT - Cisco ICND1
CCNA - Working towards.

 

[troyz]

Can you post a few sample smdr lines from 5.2.18?

 

[troyz]

Does anyone have SMDR sample from 5.2.18? I would appreciate it if you could post a sample.

 

[dencom]

We just had a pb for a 406V2. This fixed an issue with regards to continued calls (CQ53843). Deltaserver running is 5.2.16. I was quit suprised the pb was for the core software rather than the deltaserver itself. Final fix for this is targeted for Q2 maintenance release.

As we are currently in the final stage of our new call reporter application, I expect to find more issues like the one you described. Another one we have found so far is the mix up of extensions who answered an incomming call. It happens but it is unclear when and how. One thing I know for sure now: it's more an IPO core problem rather than the deltaserver.

regards

Arnoud