We looking at rolling out the Trio-Teams-RealConnect-Line2-unregistered-Template as a profile deployment to over 100 devices (Combination of Trio 8500 & 8800 model devices).
However as the attribute reg.2.address needs to be unique, is there anyway to input a variable rather than requiring a profile per each device?
Solved! Go to Solution.
Hello @JamiePeers
the "Importing all phones via a CSV File" section of the above FAQ shows an example. As long as the CSV file contains the minimum required details aka the mac_address as a column you can just import a single configuration parameter aka reg.2.address.
Best regards
Steffen Baier
If official support is required please check how to phone or open a case here
----------------Hello @JamiePeers ,
Welcome back to the Poly Community.
From our Voice FAQ:
Dec 06, 2017 Question: Is there an FAQ for RealPresence Resource Manager RPRM to provision Poly or Troubleshoot phones?
Resolution: Please check => here <=
Simply create a CSV file and RPRM will do the rest for you.
Please ensure to provide some feedback if this reply has helped you so other users can profit from your experience.
Best Regards
Steffen Baier
If official support is required please check how to phone or open a case here
----------------Hi Steffen,
Thanks for the prompt reply.
For clarity, in terms of the CSV file you are referring to - is this uploaded directly into the profile configuration using the Resource File option against the Reg2.Address Attribute (see attached screenshot). If this is the case what data needs to be included in the CSV?
Alternatively does this need to be a separate configuration profile per device?
Many thanks,
Jamie Peers
Hello @JamiePeers
the "Importing all phones via a CSV File" section of the above FAQ shows an example. As long as the CSV file contains the minimum required details aka the mac_address as a column you can just import a single configuration parameter aka reg.2.address.
Best regards
Steffen Baier
If official support is required please check how to phone or open a case here
----------------Thanks Steffen.
I can confirm that the advised changes were made via a CSV uploaded to the PDSM-E console and these successfully applied to the targeted devices.
Thanks for your help.