Guest

Preview Tool

Cisco Bug: CSCun68407 - TMS sees TCS as adhoc call when TCS is in gateway mode and using B2BUA C

Last Modified

Nov 27, 2020

Products (1)

  • Cisco TelePresence Management Server

Known Affected Releases

14.3.2 14.4RC2 14.5 14.6

Description (partial) 

Symptom:
When a SIP trunked bridge or Conductor dials out to a TCS in gateway mode via TMS, the bridge or Conductor appends its VCS trunk address to the suffix part of the alias, as a result the VCS and TMS sees the destination address as alias@VCS-IP. The end result is TMS sees the resulted connected call as an ad-hoc call and presumes the TCS it dialed out to as being not connected when it actually is connected.

Conditions:
TMS scheduling a call with Conductor or a SIP trunked bridge and a TCS in gateway mode. Note that all clustered TCSs are in gateway mode.

Related Community Discussions

Double Dialing
UPDATE 03/02/2017 01:49 PM Central: Time between dialing is 60 seconds not the 1 second I posted. Patrick Sparkman very eloquently corrected me in his post. We have an issue were Conductor will call a Participant twice in the same conference. The first call gets connected and shows up as Ad-Hoc in TMS. Depending on how the receiving codec is setup the second call either never connects or it connects a second time. All our endpoints are setup to not except a second call when in a call so it doesn't ...
Latest activity: Mar 13, 2018
Bug details contain sensitive information and therefore require a Cisco.com account to be viewed.

Bug Details Include

  • Full Description (including symptoms, conditions and workarounds)
  • Status
  • Severity
  • Known Fixed Releases
  • Related Community Discussions
  • Number of Related Support Cases
Bug information is viewable for customers and partners who have a service contract. Registered users can view up to 200 bugs per month without a service contract.