Reporting > CDR > User CDR Update time

[walter steadman]

Greetings all,

    I am running TMS V13.0 with VCS 6.1 and we were seeing CDR USER CDR Records and now we aren't.  Is there a time delay as to how often they show up?  If I make a call at 8PM CST and my TMS Server is in CST.  I hang up the call at 8:10 PM CST should I be able to go into the CDR Records and immediately see the call record show up or is there a time period that it gets updated.  Do the CDR Records have anything to do with TMS Agent Replication?

New to this part of TMS so any advice would be appreciated.

Thanks

Wally

[walter steadman]

So we finally solved this issue.  What we found out was that the feeback listeners on our VCS's were not properly configured. 

when we logged in to the VCS's as root and ran the xstat command we were not seeing the feedback listeners register to a URL.  Once we added the URL reports started working.

xCommand HttpFeedback Register FeedbackSlot:3 ServerUrl:http://oururl.com/tms/public/feedback/code.aspx Expression[1]:/History/CallLog/History

Expression[2]:/History/CallLogs/Call

Expression[3]:/Status/Call[Status='Connected']

Expression[4]:/Status/H323/Gatekeeper

Expression[5]:/Status/SIP/Registration

Expression[6]:/Status/Network/Ethernet/Speed

Expression[7]:/Event/CallSuccessful

Expression[8]:/Event/Message/Prompt/Response

[Justin Ferello · Accepted solution]

Walter,

That is very interesting, your slot is totally different than mine, yet we have never had any problems with our CDRs or MOVI CDRs.

*s Feedback 3:
     Status: On
     URL: "https://10.9.8.190/tms/public/feedback/code.aspx"
     Expression: "/Event/CallDisconnected"
     Expression: "/Event/CallConnected"
     Expression: "/Event/CallFailure"
     Expression: "/Event/RegistrationAdded"
     Expression: "/Event/RegistrationChanged"
     Expression: "/Event/ResourceUsage"
     Expression: "/Event/AuthenticationFailure"
     Expression: "/Status/Warnings"
*s/end

[walter steadman]

We were making changes to our HTTP HTTPS external manager settings and since that is where it gets the feeback URL I think that is what caused the feedback to get set to null.  We didn't do a restart (in a production environment) so it didn't populate the feedback URL.  I am interested in diving into the different expressions to see what else the feedbacks will do, thanks for showing me (new to the video world) that there are many more options to potentially watch for.  Thanks

Wally

[Jens Didriksen]

I wonder if your issue was related to this:

https://supportforums.cisco.com/thread/2094494?tstart=60

last few posts in particular.

cheers jens

[walter steadman]

Jens,

  I had read that thread in my searches and it was the thread that led me to start looking at Feedbback listeners and then when I got on the call with Cisco TAC, that is where we found ourselves.  We are using HTTP and not doing enforce management settings now and all is working. 

Thanks

Wally