[FAQ] What files does my phone download or upload and why?

[SteffenBaierUK]

Below information is based on a SoundPoint IP 650 running UCS 4.1.0.

Different phones depending on their current software version may vary.

The Boot process may differ and several files may be downloaded or uploaded /created/appended during the boot process.

NOTE: 123456789012 is a made-up MAC address for this example only. The phone will attempt to download/upload/create/append a file named after its MAC address!

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

Resolution: Please check => here <=

123456789012.cfg	The file must be manually created, can be a copy of 000000000000.cfg
000000000000.cfg	A standard file that comes with the SIP / UCS Software compatible with the phone
2345-12600-001.sip.ld	Phone Software, either SIP or UCS based on the Phone Part Number as split download (In this example SoundPoint IP 650)
123456789012-phone.cfg	The file will be created by the phone if changes via the Phones GUI / WEB Interface have been made only since > UCS 3.3.0 The provisioning server needs to allow to upload this file or it can impact the phones ability to store settings made via the Phone.
123456789012-web.cfg	The file will be created by the phone if changes via the Phones Web Interface have been made only since > UCS 3.3.0 The provisioning server needs to allow to upload this file or it can impact the phones ability to store settings made via the Phone.
000000000000-license.cfg	A site License for features described => here <=
123456789012-license.cfg	An individual License for features described => here <=
123456789012-directory.xml	An individual Phone directory for any numbers stored on the phone
000000000000-directory.xml	A Site Phone directory only loaded on original bootup. From UC Software 5.4.0 onwards check >here<
123456789012-app.log	The Phones Application log file
123456789012-boot.log	The Phones Booting up log file
Leaf.jpg	Background Picture for main Phone as explained >here<
LeafEM.jpg	Background Picture for extension module as explained >here<
Sailboat.jpg	Background Picture for main Phone as explained >here<
SailboatEM.jpg	Background Picture for extension module as explained >here<
Beach.jpg	Background Picture for main Phone as explained >here<
BeachEM.jpg	Background Picture for extension module as explained >here<
Palm.jpg	Background Picture for main Phone as explained >here<
PalmEM.jpg	Background Picture for extension module as explained >here<
Jellyfish.jpg	Background Picture for main Phone as explained >here<
JellyfishEM.jpg	Background Picture for extension module as explained >here<
Mountain.jpg	Background Picture for main Phone as explained >here<
MountainEM.jpg	Background Picture for extension module as explained >here<
123456789012-upload-config.cfg	Backup of Phone configuration changes made via provisioning files
123456789012-upload-phone.cfg	Backup of Phone configuration changes made via the phone GUI
123456789012-upload-web.cfg	Backup of Phone configuration changes made via the Phones Web Interface
123456789012-upload-all.cfg	Backup of Phone configuration changes made every source
123456789012-cloud.cfg	Backup of Phone configuration changes made via Cloud Provider (Since UC 6.2.0 or later)
123456789012-presetX.png	Camera Preset File X on a Poly Trio to store Presets

Note: For individual phones, the Provisioning Server should be set to allow the upload and to append the created files!!

Exceptions:

sip.cfg or sip_(Version of Sip).cfg	Only used prior to UCS 3.3.0 or with legacy phones
phone1.cfg or phone1_(Version of Sip).cfg	Only used prior to UCS 3.3.0 or with legacy phones
123456789012-calls.xml	The Calls list of the phone. Only for VVX models!
<user>-directory.xml	The Directory for a phone if using User Login Feature
<user>-calls.xml	The Calls list of a Phone if using User Login Feature. Only for VVX models!
<user>-web.cfg	Changes made via the Web Interface if using User Login Feature
<user>-phone.cfg	Changes made via the Phone GUI if using User Login Feature
sip.ld	Phone Software, either SIP or UCS based on the Phone Part Number as combined download. On a reboot of the Phone, the Software will be downloaded partly and the header compared to check for a newer version.
xxxx-xxxxx-xxx.sip.ld	Phone Software, either SIP or UCS based on the Phone Part Number as split download. On a reboot of the Phone, the Software will be downloaded partly and the header compared to check for a newer version.
3111-17823-001.dect.ld	D60 DECT phone software.
xxxx-xxxxx-xxx.bootrom.ld	Phone BootROM based on the Phone Part Number as split download. On a reboot of the Phone, the Software will be downloaded partly and the header compared to check for a newer version.
bootrom.ld	Phone BootROM based on the Phone Part Number as combined download. On a reboot of the Phone, the Software will be downloaded partly and the header compared to check for a newer version.
xxxx-xxxxx-xxx.updater.ld	Split
	Phone Updater being used to upgrade the phone to UCS 4.0.0 a or later as split download =>here<=
updater.ld	Combined
	Phone Updater being used to upgrade the phone to UCS 4.0.0 a or later as combined download =>here<=
123456789012-plcmsyslog.tar	Trio & CCX additional log files
enc.123456789012-5.7.1.13914-core.764.tar.gz	Please provide these or similar files to Poly support for further analysis.

Combined SIP Software	All individual compatible software packets for all supported phones in one large file
Split SIP Software	The individual version of compatible software for a single phone

Exceptions:

• When using WiFi with a Poly Trio or the CCX Range the MAC address requested by the phone as a file name is the main MAC address and not the WiFi MAC!

\Config Subdirectory

Since UCS 3.3.0 or newer a subdirectory called Config is also included with the downloaded software.

This directory contains various template files. They can be utilized provisioning certain parameters to phones.

The files are:

• H323.cfg
• reg-advanced.cfg
• reg-basic.cfg
• region.cfg => optional, often used for non-North American settings
  
  
• sip-basic.cfg
• sip-interop.cfg
• site.cfg
• video.cfg => if using the VVX 1500, 500 and 600 for video calls
  
  
• video-integration.cfg => For deployments in which the SoundStation IP 7000 is deployed as an audio and control endpoint connected to a Poly HDX device or GroupSeries, you only need to configure a limited number of parameters
  
  
• device.cfg
• features.cfg
• applications.cfg => If implementing applications using the browser and XML Control/Status API

Above are not automatically downloaded and need to be specified within the CONFIG_FILES="" section of a 000000000000.cfg or <mac>.cfg

Product Name	Model Name	Part Number
SoundStructure VoIP Interface	SSTRVOIP	3111-33215-001
VVX D60 Wireless Handset	VVX D60	3111-17823-001
VVX 101	VVX101	3111-40250-001
VVX 150	VVX150	3111-48810-001
VVX 201	VVX201	3111-40450-001
VVX 250	VVX250	3111-48820-001
VVX 250 New Hardware	VVX250	3111-48820-021
VVX 300	VVX300	3111-46135-002
VVX 301	VVX301	3111-48300-001
VVX 310	VVX310	3111-46161-001
VVX 311	VVX311	3111-48350-001
VVX 350	VVX350	3111-48830-001
VVX 350 New Hardware	VVX350	3111-48830-021
VVX 400	VVX400	3111-46157-002
VVX 401	VVX401	3111-48400-001
VVX 410	VVX410	3111-46162-001
VVX 411	VVX411	3111-48450-001
VVX 450	VVX450	3111-48840-001
VVX 450 New Hardware	VVX450	3111-48840-021
VVX 500	VVX500	3111-44500-001
VVX 501	VVX501	3111-48500-001
VVX 600	VVX600	3111-44600-001
VVX 601	VVX601	3111-48600-001
VVX 1500	VVX1500	2345-17960-001
SoundPoint IP 300	SPIP300	2345-11300-001
SoundPoint IP 301	SPIP301	2345-11300-010
SoundPoint IP 320	SPIP320	2345-12200-002
		2345-12200-005
SoundPoint IP 321	SPIP321	2345-12360-001
SoundPoint IP 330	SPIP330	2345-12200-001
		2345-12200-004
SoundPoint IP 331	SPIP331	2345-12365-001
SoundPoint IP 335	SPIP335	2345-12375-001
SoundPoint IP 430	SPIP430	2345-11402-001
SoundPoint IP 450	SPIP450	2345-12450-001
SoundPoint IP 500	SPIP500	2345-11500-001
		2345-11500-010
		2345-11500-020
SoundPoint IP 501	SPIP501	2345-11500-030
		2345-11500-040
SoundPoint IP 550	SPIP550	2345-12500-001
SoundPoint IP 560	SPIP560	2345-12560-001
SoundPoint IP 600	SPIP600	2345-11600-001
SoundPoint IP 601	SPIP601	2345-11605-001
SoundPoint IP 650	SPIP650	2345-12600-001
SoundPoint IP 670	SPIP670	2345-12670-001
SoundStation IP 4000	SSIP4000	2201-06642-001
SoundStation IP 5000	SSIP5000	3111-30900-001
SoundStation IP 6000	SSIP6000	3111-15600-001
SoundStation IP 7000	SSIP7000	3111-40000-001
SoundStation Duo	SSDuo	3111-19000-001
Trio 8800	Trio8800	3111-65290-001
Visual+	TrioVisualPlus	3111-66420-001
Trio 8500	Trio8500	3111-66700-001
Trio 8300	Trio8300	3111-66800-001
Trio C60	TrioC60	3111-86240-001
VVX D230	VVXD230	2201-49230-001
CCX 400	CCX400	3111-49700-001
CCX 500	CCX500	3111-49710-001
CCX 600	CCX600	3111-49770-001
CCX 700	CCX700	3111-49740-001

NOTE: The RealPresence Trio and the VVX Phones automatically supplies the Visual+ / DECT Base Station with its software

[SteffenBaierUK]

Since UC Software 4.0.0 or later a backup can be created via the Web Interface Utilities > Phone Backup & Restore > Phone Backup > Phone Backup

The backup is stored as a <mac>_PhoneModel_Date_Time.pbu format. Example 0004f2fcb831_Trio8800_18-04-2018_14-25.pbu

The backup contains the running configuration of a phone with separate sections showing the provisioning source i.e. Phone itself, Web Interface or Configuration files from a provisioning Server or in case of Skype for Business the Call Server.

In addition a user can also use the Web Interface to create individual Export files

• All Configuration (except Device Settings) Export_all.cfg
  All configuration sources apart from device configuration i.e. IP Settings, CDP, LLDP, etc.
  
  
• Config Files => Export_config_files.cfg
  All configuration provisioned via a provisioning Server shown as <CONFIG_FILES in a backup PBU file
  
  
• Local => Export_phone_local.cfg
  All configuration changes made on the phone locally via the Phone UI shown as <PHONE_LOCAL in a backup PBU file
  
  
• Web => Export_web.cfg
  All configuration changes made via the Web Interface of the phone shown as <WEB in a backup PBU file
  
  
• SIP => Export_call_server.cfg
  Changes pushed inbound from a Call Server like Skype for Business shown as explained => here <= and as  <CALL_SERVER in a backup PBU file
  
  
• Device Settings => Export_device_settings.cfg
  All device configuration i.e. IP Settings, CDP, LLDP, Passwords, etc. shown as  <DEVICE_SETTINGS in a backup PBU file
  
  
• <DEVICE_SETTINGS_CHANGED shows the changes made to the above standard values
  
  
• <FACTORY_CONFIG shows the difference to the factory config
  
  
• <CLOUD shows the changes made via cloud configuration aka Lens or PDMS-E

The actual hierarchy of provisioning priority a Poly phone is in this order:

Utilising the Web Interface to determine the Source:

Configuring a parameter via the web

Configuring a parameter via a configuration file via provisioning

Utilising the Web Interface to find the relevant configuration parameters:

The above shows the reg.1.protocol.SIP parameter.

The above shows the "special" Device Parameter as shown => here <=