04-28-2012 03:16 PM - edited 03-17-2019 11:07 PM
Looking at the new TMSPE release, have a few questions:
Solved! Go to Solution.
05-01-2012 12:44 AM
Hi Frederick
Sorry I noticed that what I wrote here is wrong. It is opposite of what I said and I'm sorry for the mistake. You can use the 4.4 jabber client using the 4.3 template but the 4.3 client cannot use the 4.4 template. That's how it works.
So basically you can have 4.2 template and 4.4 template. Then you can login with 4.2, 4.3 and 4.4 but not 4.1 for example.
Sorry again for the misleading information.
/Magnus
04-28-2012 10:34 PM
Hi
Yes you need a version specific template, there is no univeral template anymore, but lets take jabber for example. You cannot use the 4.3 template for jabber version 4.4 you need the 4.4 template. However the 4.3 client can use the 4.4 template etc.
I guess what your asking must be reported as an enhancement request if you want this universal template implemented.
/Magnus
Sent from Cisco Technical Support iPhone App
04-29-2012 07:04 AM
Thanks Magnus.
There are a significant number of parameters in most deployments that are universal across all provisioned endpoints, and the ability to configure/change them once at the top-level container was efficient and convenient. So TMSPE took a step back in this regard, but not a huge concern since there is still a way to implement an effective configuration, and once set up these things tend not to change too much.
So confirming what you stated: is it safe to assume if I use the newest template for a given product, an older version of product will just ignore the fields it doesn't implement?
05-01-2012 12:44 AM
Hi Frederick
Sorry I noticed that what I wrote here is wrong. It is opposite of what I said and I'm sorry for the mistake. You can use the 4.4 jabber client using the 4.3 template but the 4.3 client cannot use the 4.4 template. That's how it works.
So basically you can have 4.2 template and 4.4 template. Then you can login with 4.2, 4.3 and 4.4 but not 4.1 for example.
Sorry again for the misleading information.
/Magnus
05-01-2012 05:08 AM
Thanks Magnus. This matches my observations and probably explains why TMSPE ships only with templates for some pretty old (i.e. movi 3.1) product versions out of the box.
05-01-2012 05:37 AM
Yes, it would be much more handy if it has a centralized template upgrade option
accessing it from a cisco server.
I would guess 99% are running anyhow only the original unmodified cisco xml templates.
So a TMS alert "hey there is a new software version and it also comes with a new template"
with a nice "do you want to download and integrate the new schema?"
An option to manually install / replace one would still be handy.
Please remember to rate helpful responses and identify
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide