ā11-13-2012 05:51 PM - edited ā03-18-2019 12:07 AM
I'm working on migrating from TMS Agent Legacy to TMSPE, and I noticed the following within the TMS provisioning options:
Note: Video Address Pattern and Device Address Pattern must be configured for provisioning and FindMe to function properly.
I'm use to the Legacy method of only filling in the Device URI to create the SIP video address we use. Though, how do I go from that single method of configuration to the new TMSPE addresses, and what does each of the new address types do if they were separate or the same?
Thanks
Solved! Go to Solution.
ā11-13-2012 06:20 PM
Video address pattern is the FindMe address, the device address pattern is, well, just that, the address of the device; i.e. the users JabberVideo (Movi) address. The Video address pattern is only used if you are using FindMe, otherwise not.
See: https://supportforums.cisco.com/thread/2179099?tstart=120
/jens
ā11-13-2012 06:20 PM
Video address pattern is the FindMe address, the device address pattern is, well, just that, the address of the device; i.e. the users JabberVideo (Movi) address. The Video address pattern is only used if you are using FindMe, otherwise not.
See: https://supportforums.cisco.com/thread/2179099?tstart=120
/jens
ā11-13-2012 06:27 PM
Thanks Jens, that makes perfect sense. The note that they mention on the provisioning page is a bit confusing, making it sound like you need both, even if in some configurations you might not like you mention depending on if they use FindMe.
ā11-15-2012 03:14 PM
Video address will only work if FindMe is being used correct? I did notice in the phonebook source that if a video address is being used that it also appears, however it doesn't route to any specific device, that is if it is different from the device address.
ā11-15-2012 03:24 PM
That is correct. We're not using FindMe either, so I've set Video address pattern to the same as the Device address pattern.
/jens
ā11-15-2012 03:40 PM
Thanks, my opinion, PE has it's good points and again some bad ones too. Seems a bit harder to me to manage some areas of the user data and configurations, but I suppose we have to get use to it.
Jens, do you just provision Jabber Video, or other endpoints such as E20, or EX systems as well? Also, what setting do you have the provisioning phone book source set to for advanced settings. I've thought about provisioning some of our E20 units along with Jabber Video so users can be able to call one URI and connect to someone no matter which device they are behind. This is without the use of FindMe, hense registering each device with the same video/device address.
ā11-15-2012 03:55 PM
Took me a while to get my head around TMSPE as compared to legacy, but I quite like it now.
I only provision JabberVideo clients at this stage as we only have a couple of EX90 and no E20 devices.
Provisioning both with same URI should work, can't see any reason as to why it wouldn't.
Not sure what you mean by te provisioning phone book source for advanced settings; but in all of our C-series and the EX90's under Phonebook Server 1, I'm using ID "default", Type "TMS" - if that's what you're referring to?
/jens
ā11-15-2012 05:38 PM
I was refering to the provisioning phonebook source within TMS, that's all. Thanks for the info, and yeah it does take a little while to go from the legacy method to the new one.
ā11-15-2012 07:02 PM
Aha, I see
Only "Import Provisioned Devices" selected.
/jens
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