Plantronics + Polycom. Now together as Poly Logo

Organizing the config directory on the Lync Provisioning Server using 000000000000.cfg

SOLVED
Advisor

Organizing the config directory on the Lync Provisioning Server using 000000000000.cfg

Good morning,

 

Our environment is Skype for Business 2015 servers and Polycom VVX 300 and 400 phones running UCS 5.4.1.  We are testing out Polycom UCS 5.4.4 and I was hoping to take this time to make a more organized file/folder structure.  When I extracted the 5.4.4 split software it created the usual directory with 000000000000.cfg, multiple ld files, and a Config and languages folder.  I then created CoreDumps, Logs, Profiles, and CompanyConfig folders.  On my 000000000000.cfg file, I specify the following parameters:

 

CONFIG_FILES="CompanyConfig\compdevice.cfg (contains some customized parameters based on our needs)

LOG_FILE_DIRECTORY="Logs\"

USER_PROFILES_DIRECTORY="Profiles\"

CALL_LISTS_DIRECTORY="http://0.0.0.0" (Thank you again Steffen for this one!)

COREFILE_DIRECTORY="CoreDumps\" (this puts all <device>.tar.qz core dump files in one spot)

 

I'm curious to know if these types of config files can also be forced to write to a different custom directory:

 

<device>-phone.cfg

<device>-web.cfg

<device>-app.log

<device>-boot.log

<device>-directory.xml

 

I doubt the cfg files could move since they are more specific versions of 000000000000.cfg that gets referenced in the root directory but I'd love to move the log files out of there.  Right now every so often I'll log onto the server and manually move the app.log and boot.log files to the Logs directory.

Message 1 of 3
2 REPLIES 2
Polycom Employee & Community Manager

Re: Organizing the config directory on the Lync Provisioning Server using 000000000000.cfg

Hello jplarsonqg,

welcome back to the Polycom Community.

The community's VoIP FAQ contains this post here:

 

Oct 7, 2011 Question: What is the relevance of the 000000000000.cfg or <mac>.cfg?

Resolution: Please check => here <=


The above or the Admin Guide should explain all the structures you require.


Please ensure to provide some feedback if this reply has helped you so other users can profit from your experience.

Best Regards

Steffen Baier

Polycom Global Services




<======== Signature / Disclaimer ========>
Please be aware:For questions about the type of support to expect please check here

Please also ensure you always check the VoIP , Video Endpoint , Skype for Business , PSTN or RPM FAQ's

Please remember, if you see a post that helped you , and it answers your question, please mark it as an "Accept as Solution".

The title Polycom Employee & Community Manager is an automatic setting within the community and any forum reply or post is based upon my personal experience and does not reflect the opinion or view of my employer.
Poly employee participation within this community is not mandatory and any post or FAQ article provided by myself is done either during my working hours or outside working hours, in my private time, and maybe answered on weekends, bank holidays or personal holidays.
Message 2 of 3
Highlighted
Advisor

Re: Organizing the config directory on the Lync Provisioning Server using 000000000000.cfg


@jplarsonqg wrote:
I'm curious to know if these types of config files can also be forced to write to a different custom directory:

 

<device>-phone.cfg

<device>-web.cfg

<device>-app.log

<device>-boot.log

<device>-directory.xml

 

I doubt the cfg files could move since they are more specific versions of 000000000000.cfg that gets referenced in the root directory but I'd love to move the log files out of there.  Right now every so often I'll log onto the server and manually move the app.log and boot.log files to the Logs directory.


Hello,

 

You can use the following parameters for the files above:

 

OVERRIDES_DIRECTORY="PhoneConfigurations" -> for <device>-phone.cfg and <device>-web.cfg
CONTACTS_DIRECTORY="Directories" -> for <device>-directory.xml
LOG_FILE_DIRECTORY="Logs" -> for <device>-boot.log and <device>-app.log

 

From my experience, even when you set these parameters in your master configuration file, some phones might still try to upload log files (especially the <device>-boot.log ones) to the root of the provisioning server. To prevent this, just restrict the "write" permission on the root folder (only allow phones to "read" the root folder), this will allow you to have a "clean" root folder. Here are the rights that I typically use for each subfolders:

 

 

VVX Provisioning folder permissions

 

Best regards,

Mickael BREST
Orange Business Services
Message 3 of 3