Why does scheduling in TMS not give me the call direction choice I want?

Available Languages

Updated:April 23, 2015
Document ID:112540

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 does scheduling in TMS not give me the call direction choice I want?

A. Check the following:

For specific systems:

  1. Go to Systems > Navigator.

  2. Select the system.

  3. Select the Settings tab and scroll to the TMS Scheduling Settings pane.

  4. Ensure there is no limit on the direction of allowed call on the system.

  5. If you wish to edit settings, select Edit Settings at the top of the section and edit appropriately.

For specific system type:

  • TMS may not be able to automate outbound calling from that system type. Check the TMS Product Support document for compatibility.

  • TMS will not automate outbound calling from systems (for example T150) supporting lower bandwidth than what is set in the Conference Bandwidth. To set Conference Bandwidth, go to Booking > New Conference > Advanced Settings pane and set the IP/ISDN Bandwidth appropriately.

TMS does not allow IP Address dialing into H.323 devices which provide services, such as MCUs or Gateways (with the exception of the TANDBERG Codian MCU under certain configurations).

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