No Movi User CDR Reports in TMS

[Andrew Vasel]

TMS 12.6

VCS X5.1.1

Movi 4.1

We have had an open ticket with Cisco TAC for months with no real good direction except what feels like a generic guidance to upgrade TMS. Within TMS, under the Reporting -> Call Detail Record -> User CRD reports, it is my understanding that there should be a drop-down for Movi users under the device type field before running the report. My drop-down only shows all and does not include any information about Movi users when running the report with device type set to all.

Any ideas or suggestions?

[Jens Didriksen]

Yup, same here, despite having made the changes as Martin suggested.

TMS log shows this problem started after upgrading to 13.1, but that was most probably due to the http/https issue, so X7.0 is a strong contender for this one. I opened a case with TAC this afternoon.

[Anthony Chan]

Cisco TAC came back and said to blow away the existing TMS and do a fresh install of TMS 13.1.  They indicated that the upgrade path was corrupted somehow eventhough it said that it was successful. 

Martin, so what you are saying is that the CDR report should work with https and not http in communicating with the VCS?

As well as version 13.2 resolves the https issue?

[Martin Koch]

1. enable https on the tms, good idea anyhow and then you do not drop into the mentioned issue.

2. TMS13.1 (if enforce management setting is set) will force the vcs to use https as the external manager

3. TMS13.1.2 will force http if not and https if secure only and enforce management settings are set.

They also work with http and tms13.1, but then enforce management has to be disabled as well.

Anyhow you should check the external manager settings/status from time to time if CDRs are important to you.

Cisco: Sounds like an useful future feature to show a warning on the VCS web interface if the external manager failed!

Also the User CDRs are not ideal, at least I have not seen a way to show real movi2movi call-cdrs incl start and stop time instead of the cumulated value.

Anthony: I would really appreciate if you (and all others) would vote answers

[Jens Didriksen]

Just heard from Cisco TAC, they strongly recommend upgrading to 13.1.2 as this fixes the issue.

The changing of HTTP to HTTPS is part of it, even with protocol set to HTTP and external manager status showing "active" in VCS, TMS 13.1 is unable to properly understand the data it is receiving from VCS due to some API changes - and user CDRs will not be available. The Cisco engineer advised me he had proved this in their test lab, so it shall be interesting to see what happens after I upgrade TMS tomorrow morning.

[Anthony Chan]

Interesting to hear that your Cisco TAC says upgrade to 13.1.2 whereas my Cisco TAC to blow away and reinstall fresh under 13.1 and then upgrade to 13.1.2

would like to hear your results in your upgrade

[Martin Koch]

Hi Anthony,

you had 13.1 running before, so did you use a backup of the sql and openDS database?

Then I completly agree on going 13.1 and then 13.1.2.

The end result for Jens, you and me is that we all have 13.1.2 running at the end,

which I can at least say work fine for us.

btw, the upgrade from 12.6 to 13.1 and then to 13.1.2 worked ok for us.

I expect the same for Jens and you.

[Anthony Chan]

we have nightly backups of the SQL database along with the Provisioning Database

will need to migrate them over to the new TMS

Then will switch the VCS connection to the new TMS server most likely in December where it is calmer

[Jens Didriksen]

Hi Anthony,

"My" TAC was adament he got user CDRs after upgrading, however, I upgraded this morning and am now running 13.1.2 and X7.02 - and no user/VCS/GK CDRs to be found .

So, a clean 13.1 install might be the way to go - perhaps - however, that is just not an option for us, not at this stage at least.

[Anthony Chan]

Sorry to hear about the results Jens,

I was able to build a new VM to install a new TMS running 13.1 right now and as above reply to Martin will restore the database over this weekend. Next steps would be to link the new TMS to the VCS and see if that works or not before I upgrade to 13.1.2.  Or should I upgrade first before the link?

Thoughts?

Would be interesting to hear back from your TAC on what the next steps would be?

[Jens Didriksen]

Just had a WebEx session with TAC, and he identified the reason I was not getting user CDRs right away;

once you have upgraded to 13.1.2 you need to enforce management settings as the VCS' will not otherwise know about the change. I have now turned "Enforce Management Settings" back on, and I'm now getting user CDRs again.

[Anthony Chan]

awesome news Jens

btw what version of VCS are you using?

and are you using http or https?

[Jens Didriksen]

X7.02 and http

[Anthony Chan]

Just a quick update on this issue that i was having, it seems now that the Movi User CDR is working again but have lost information from Sept to Nov. 2011.  I have data starting from Dec 1 2011 and forward.  Not sure why it hust came back have not done any upgrade to TMS since Aug or VCS.   TMS currently 13.1.2 and VCS 6.1

[jarnold]

I'd been having Movi User CDR and OpenDS issues ever since upgrading from 12.6 to 13.0. Working through TAC they suggested that I upgrade to TMS 13.1.2, which immediately took care of my OpenDS issues I had been seeing, but User CDR was still an issue. After a couple of hours of going through logs and traces, TAC noticed that all of the User CDR information was being sent to the IPv6 Address on the TMS server (which isn't being used) and blowing the information into Never Land. We disabled IPv6 on the TMS server and User CDR records started working again. I'm now running TMS 13.1.2 and my VCS is running x6.0 (working on upgrading this now) and everything seems to be working fine for me. Not sure if this will help anyone or not, but it was the root of my issue.

[ahmed]

Hi all,

it's OK about User CDR, but most of customers always ask about details of CDR, because you know that MOVI CDR is different with Endpoint or MCU CDRs. in MOVI CDR has no detail call history like time start, from to who, etc.

i try to make like CDR use Syslog server, which capture log file from VCS, but it still need some programs to analysis the log, so only call log be collected. i try by use query about string "call completed" and make analysis about time start and end, but folks this is really-really make me sick, but it works.

so maybe we can make it easier if anybody have solution to how capture call history in VCS then save it as log file.

please advice

Thanks