TMS does not collect CDR from VCS Control

[hashimoto.kotaro]

Hi all,

Our TMS does not collect Call Detail Record of VCS Control.

(Reporting > Call Detail Record > Gatekeeper and VCS)

It collected CDR correctly until August 2.

But it does not collect any CDR from August 3 till today even though many calls are placed.

We have not changed any configuration of the TMS and VCS.

What should I check on the TMS and VCS?

Any advise is welcomed

Best Regards,

Kotaro Hashimoto

[Magnus Ohm]

Hi

Is the VCS running X7.2? If so there is a known issue where the TMS is not able to collect CDR records from the VCS due to a defect.

BugID: CSCub58677

Also if you are not running this version of VCS but 13.1 on the TMS, there was a defect changing the feedback protocol from HTTP to HTTPS and if the TMS did not have HTTPS enabled then the feedback would fail.

It might be something else as well, do you see this on anything else than the VCS?

/Magnus

[Tomonori Taniguchi · Accepted solution]

As Magnus mention, there is known issue with X7.2 for CDR.

Symptom:

TMS will not produce CDR data of type "Gatekeeper and VCS", and the log-web-public.txt log file in TMS will contain entries similar to:

---> Tandberg.TMS.SystemAPI.OakPine.InvalidStateException: Expected to find , but instead found .

at Tandberg.TMS.SystemAPI.OakPine.XMLFeedbackReader.AssumePositionedAtTag (XmlReader reader, String tag)

at Tandberg.TMS.SystemAPI.OakPine.XMLFeedbackReader.ProcessCall(XmlReader reader)

at Tandberg.TMS.SystemAPI.OakPine.HttpFeedback.ProcessCallDisconnected(IXMLDoc txasDoc, RoutableSystem system)

--- End of inner exception stack trace ---

TMS Version 13.2.1

Background:

Because of a change in the XML feedback which the VCS sends to TMS for events related to calls connecting and disconnecting, TMS is not able to properly interpret the XML data provided by the VCS. Because of this, TMS is not able to generate CDR records based on the feedback data provided by the VCS.

Workaround:

There is currently no known workaround for this issue when running X7.2 software on the VCS. X7.1 and previous versions of VCS software are not affected by this issue.

This issue will be fix with next maintenance release, X7.2.1.

[hashimoto.kotaro]

Hi Danny, Taniguchi-san.

Thank you for your information.

Unfortunately the version of our VCS is X5.2 and TMS is 12.6.2.

Is there any suspicious cause else?

Best Regards,

Kotaro Hashimoto

[Tomonori Taniguchi]

No I don’t aware any known issue about CDR on VCS, but VCS X5.2 is quite old and highly recommend to upgrade anyway.

BTW, are you missing CDR only from VCS but still able to capture all CDR from other devices under TMS?

[Martin Koch]

Some TMS & VCS versions switched communication over to https or vice versa.

So check on the VCS if the external manager is properly up.

One workaround for that might simply be to add https to the IIS of the TMS.

Anyhow, like Tomonori said, an upgrade is highly recomended. There are some major issues resolved with the latest versions.