<VAL:NUMERIC_ID> is null in email templates

[cehr_itsupport]

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.

Like many other people have posted, we need to be able to add this 4-digit Numeric ID to the DDI prefix for dial-in callers and I'd like to use the same Numeric ID value in the Jabber Guest URL.

Any help greatly appreciated!

Thanks

Lee

[Nick Halbert-Lillyman]

I've had the same issue, we (sort of) solved it using a different variable.

It was a little while ago now but I think it was VIDEO_ADDRESS.

[cehr_itsupport]

Thanks for the replies.  The VIDEO_ADDRESS value is already in there and is returning the full sip URI assigned by TMS in Connection Settings tab.

The TMS email template includes the phrase {TELEPRESENCE_VIDEO_ADDRESS}: and then value <VAL:VIDEO_ADDRESS>

This results in the email reading "join using your mobile device: 8180@{our domain}

When you hover over the 8180@{our domain} in the email you see the full sip URI (i.e sip:8180@{our domain}

What I need to be able to do is reference just the 8180 part of that string as that is the bit which matches the last 4 digits of the DDI used by the dial-in participants.

I've attached the configured conference aliases in Conductor, if that helps.

This has got me a bit flummoxed... there has to be a solution!

[Patrick Sparkman]

Because Conductor is SIP, the address will contain a domain, there is no way that I'm aware of to remove it from the address that appears in the conference invite email.  One workaround you could do is add some text in the email invite that instructs your users to dial into the conference using just DID that appears before the domain.

[Nick Halbert-Lillyman]

There's a way to make the Conductor scheduled conference alias be numeric only without requiring the domain suffix, using Regex between Conductor and TMS.

I'm sorry it was quite a while ago so I don't remember the exact regex, but it was something along the lines of:

For a Conference range of 701X, TMS has Regex of 701% and Conductor has it as 701.*

This way, TMS thinks the conference is Numeric, but when the endpoint actually makes the call, the domain portion is automatically added but it still matches on Conductor.

[Patrick Sparkman]

I went through the steps within TMS to configure Conductor and create a conference per Nick's suggestion and it appears to work, I would have thought since Conductor is only capable of SIP that TMS would have thrown some kind of warning or something because no domain is present, but it didn't.  The only downside to this configuration is if someone receives the conference invite from TMS and needs the full SIP URI, as the email will then only contain the alias portion without the domain.

[cehr_itsupport]

Excellent, thanks everyone.  We'll give that a go and report back!

Cheers
Lee

[Nick Halbert-Lillyman]

To get around the external invite problem for external participants that Patrick points out, we put something along the lines of the following in the email template:

"To join from inside the organization, dial <VIDEO_ADDRESS>.  To join from outside the organization, dial <VIDEO_ADDRESS>@domain.com"

[cehr_itsupport]

Thanks for the replies everyone.  Finally managed to get around to this again, but still don't have a fully working solution.

Tried changing the regex's in TMS and that did shorten the VIDEO_ADDRESS url to e.g. 8180 without the domain suffix but we still have the issue that when you use this variable in the email template it is automatically prefixed with "sip:".  This means I cannot incorporate the variable into the DDI dial string which is what I need to be able to do.  If I did, then the dial string would be something like 01xx8xxsip:8180

Also, to note, the VIDEO_ADDRESS variable only seems to be valid in certain parts of the template, namely the SECTION:VIDEO_ADDRESS which has a repeating sub section.

We're now on the latest TMS 15.3.

It's doing my head in now! Any final thoughts much appreciated!

Lee

[Patrick Sparkman]

Conductor doesn't support the legacy email variable NUMERIC_ID, see bug CSCun23958. 

As mentioned by Nick, you can use the email variable VIDEO_ADDRESS, which is supported with Conductor and was introduced in TMS 14.5. Suggest you try and update your email templates to use the current supported variables instead, refer to the "Email Template" section in TMS 15.2.1 Admin Guide starting on pg 208. 

If you need to add a prefix to the video address, you can add it within the email template yourself.