11-08-2016 07:00 AM - edited 03-13-2019 09:40 PM
Hi Folks,
I'm trying to work with the API for our SX20's (TC7.3.6), in order to manipulate the contact info as displayed on the codec home page. I can see various types available in the valuespace.xml and I can see the available command to manipulate the config as:
http://x.x.x.x/formputxml?xmldoc=
<Configuration><SystemUnit>
<ContactInfo item="1"><Type item="1" valueSpaceRef="/Valuespace/TTPAR_ContactInfoVs">SystemName</Type></ContactInfo>
</SystemUnit></Configuration>
or from SSH:
xconfiguration SystemUnit ContactInfo Type: SystemName
I'm trying to automate the process for a number of endpoints, combining the E164Alias with the SystemName to be the contactinfo (which I can use the API, CLI or custom field to update).
Like: String = "E164Alias+SystemName" (or similar).
Can anyone with more experience suggest a way to concatenate the 2 types to display? Perhaps even a way to change the realtive positions of the types?
I can't edit the valuespace.xml to add a new type. I've tried a number of operator types to concat the 2 types to no avail. With no root access I can't get access to manipulate configs to test.
Any advice would be appreciated! (Even if it's, no this can't be done)
TIA
Solved! Go to Solution.
11-08-2016 09:14 AM
It's not possible to manipulate SystemUnit ContactInfo Type, your only options are:
With that said, you have a few workarounds that you can do. Use either SystemName or DisplayName for example and manually input what you want to be displayed in those fields.
11-08-2016 09:14 AM
It's not possible to manipulate SystemUnit ContactInfo Type, your only options are:
With that said, you have a few workarounds that you can do. Use either SystemName or DisplayName for example and manually input what you want to be displayed in those fields.
11-09-2016 02:09 AM
Hi Patrick,
That's pretty much what I suspected. I was hoping there was a not-advertised method or XML schema way of doing it. I'm trying to minimise the administrative chore of updating multiple endpoints. DisplayName was always an option, but concatenating two fields into one would have been my preference.
Thanks for chipping in and putting it to bed!
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