Guest

Preview Tool

Cisco Bug: CSCun23958 - TMS Legacy Email Variable NUMERIC_ID is not valid when using Conductor

Last Modified

Jun 08, 2020

Products (1)

  • Cisco TelePresence Management Server

Known Affected Releases

14.3.1

Description (partial)

Symptom:
Legacy Email variable NUMER_ID is not valid when using Conductor with TMS for scheduling

Conditions:
Edit the Booking Invite Email template and use the NUMERIC_ID variable - <VAL:NUMERIC_ID>.

i.e. <td align="left" colspan="2" class="smallLabel" style="font-family: Arial; font-size: 13px; line-height: 16px; color: #666; font-weight: bold;">{WEB_CONFERENCE_LOCAL_CALL_IN_NUMBERS}<BR />Conference ID: <VAL:NUMERIC_ID>#</td>

Schedule a meeting in TMS that uses Conductor.
When you receive the Confirmation Email there will be no value for <VAL:NUMERIC_ID>.

Related Community Discussions

&lt;VAL:NUMERIC_ID&gt; is null in email templates
Hi, I've seen a few posts about this issue and hoping there's a solution for TMS 15.2.1 when used with Conductor. Basically the custom email templates in TMS are not pulling back the NUMERIC_ID value.  This value is matched to the inbound DDI on CUCM which is pushed to Conductor using route patterns etc.  TMS is allocating the Numeric ID properly (range = 8180 thru 8189) and we can see it in the Conference Settings tab in TMS (as part of the video address) but it just will not show in the email template. ...
Latest activity: Aug 25, 2016
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.