Why am I not getting any CDR or trap log entries for my TANDBERG MXP systems in TMS?

Available Languages

Updated:April 23, 2015
Document ID:112552

Bias-Free Language

The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.

Introduction

This article relates to Cisco TelePresence Management Suite.

Q. Why am I not getting any CDR or trap log entries for my TANDBERG MXP systems in TMS?

A. This condition means that TMS is not receiving any feedback events from the system. The endpoint will be automatically configured to send its information to TMS when it was added to TMS. If this information is missing or misconfigured, the endpoint will not be able to send events to TMS.

Check the settings on the system:

  1. Telnet or SSH into the System and enter xstatus externalmanager.

  2. The output should point to the address of your TMS server. If this address is wrong:

    1. Go to Administrative Tools > Configuration > Network > Advanced Network Settings.

    2. Check the TMS Server Address settings and correct the values as necessary.

    3. Save your changes.

  3. Go to the system in Systems > Navigator and open the Edit Settings page.

  4. Click the Enforce Management Settings button.

  5. Check the endpoint's xstatus output again and you should see the new values.

  6. Reboot the endpoint by clicking the Boot button.

  7. If after one minute you do not get a boot entry in the Trap Log for the system in TMS, feedback is being blocked by the network or web server.

Related Information

Revision History

Revision Publish Date Comments
1.0
23-Apr-2015
Initial Release

Was this Document Helpful?

FeedbackFeedback

Contact Cisco

This Document Applies to These Products