adding newer vvx phones to legacy ftp setup

[Anonymous]

Hello,

I am adding vvx300/vvx400s to our legacy ftp provisioned 301-650 phones. I have been reading all of the relevant faqs, bulletin s and guides, but I still have a couple of questions.

I understand that the 000000000000.cfg points the legacy phones to their relevant sip.cfg / phone1.cfg /sip.ld (sip_318.ld...), and that's how they get their main configs sorted in the upgrade, but each phone has a phone<macaddress>.cfg file containing the login information as such...

reg.1.displayName="109"
reg.1.address="109-******"
reg.1.label="109"
reg.1.type="private"
reg.1.lcs=""
reg.1.thirdPartyName=""
reg.1.auth.userId="109-******"
reg.1.auth.password="password"
reg.1.server.1.address="ipaddress"
reg.1.server.1.port="5060"
reg.1.server.1.transport="DNSnaptr"
reg.1.server.2.transport="DNSnaptr"
reg.1.server.1.expires=""
reg.1.server.1.expires.overlap=""
reg.1.server.1.register="1"
reg.1.server.1.retryTimeOut=""
reg.1.server.1.retryMaxCount=""
reg.1.server.1.expires.lineSeize=""
reg.1.outboundProxy.address=""
reg.1.outboundProxy.port=""
reg.1.outboundProxy.transport=""
reg.1.acd-login-logout="0"
reg.1.acd-agent-available="0"
reg.1.proxyRequire=""
reg.1.ringType="2"
reg.1.lineKeys=""
reg.1.callsPerLineKey=""

I understand that these files are old and need to be updated for the newer (vvx* phones) - but

1. for the legacy phones, do I need to enter the phone<mac-address>.cfg for each phone into the config_files section for the respective phone model in the new 000000000000.cfg?

2. if not, how do the phones know to go get their phone<mac-address> file to get the login parameters?

3. for the vvx phones, do they need a phone<mac-address>.cfg file as well? I guess so since they need their login parameters too...

4. Is there a newer master phone<mac-address>.cfg file for newer phones? the ones I'm using only have 6 reg.x.address... parameters - is this what the cfcutility will do?

Thank you, 

Kevin Farley

Natel Broadband

[Anonymous]

I think I just found a part of my answer - I need to update each phone<mac-address>.cfg file to the structure relevant to the supported version - ie.  phones to be loaded with 3.1.8 will need a phone<mac-address>.cfg file equivalent to the phone1_318.cfg structure.  Am I correct?  Will the CFC utility convert my old files?

[SteffenBaierUK]

Hello NatelBroadband,

welcome to the Polycom Community.

Downloading the VVX300 Software for example and looking at its 000000000000.cfg shows this:

<?xml version="1.0" standalone="yes"?>
<!-- Default Master SIP Configuration File-->
<!-- For information on configuring Polycom VoIP phones please refer to the -->
<!-- Configuration File Management white paper available from: -->
<!-- http://www.polycom.com/common/documents/whitepapers/configuration_file_management_on_soundpoint_ip_p... -->
<!-- $RCSfile$  $Revision: 135829 $ -->
<APPLICATION APP_FILE_PATH="sip.ld" CONFIG_FILES="" MISC_FILES="" LOG_FILE_DIRECTORY="" OVERRIDES_DIRECTORY="" CONTACTS_DIRECTORY="" LICENSE_DIRECTORY="" USER_PROFILES_DIRECTORY="" CALL_LISTS_DIRECTORY="">
   <APPLICATION_SPIP300 APP_FILE_PATH_SPIP300="sip_213.ld" CONFIG_FILES_SPIP300="phone1_213.cfg, sip_213.cfg"/>
   <APPLICATION_SPIP500 APP_FILE_PATH_SPIP500="sip_213.ld" CONFIG_FILES_SPIP500="phone1_213.cfg, sip_213.cfg"/>
   <APPLICATION_SPIP301 APP_FILE_PATH_SPIP301="sip_318.ld" CONFIG_FILES_SPIP301="phone1_318.cfg, sip_318.cfg"/>
   <APPLICATION_SPIP320 APP_FILE_PATH_SPIP320="sip_334.ld" CONFIG_FILES_SPIP320=""/>
   <APPLICATION_SPIP330 APP_FILE_PATH_SPIP330="sip_334.ld" CONFIG_FILES_SPIP330=""/>
   <APPLICATION_SPIP430 APP_FILE_PATH_SPIP430="sip_327.ld" CONFIG_FILES_SPIP430="phone1_327.cfg, sip_327.cfg"/>
   <APPLICATION_SPIP501 APP_FILE_PATH_SPIP501="sip_318.ld" CONFIG_FILES_SPIP501="phone1_318.cfg, sip_318.cfg"/>
   <APPLICATION_SPIP600 APP_FILE_PATH_SPIP600="sip_318.ld" CONFIG_FILES_SPIP600="phone1_318.cfg, sip_318.cfg"/>
   <APPLICATION_SPIP601 APP_FILE_PATH_SPIP601="sip_318.ld" CONFIG_FILES_SPIP601="phone1_318.cfg, sip_318.cfg"/>
   <APPLICATION_SPIP670 APP_FILE_PATH_SPIP670="sip_403.ld" CONFIG_FILES_SPIP670=""/>
   <APPLICATION_SSIP4000 APP_FILE_PATH_SSIP4000="sip_318.ld" CONFIG_FILES_SSIP4000="phone1_318.cfg, sip_318.cfg"/>
   <APPLICATION_SSIP7000 APP_FILE_PATH_SSIP7000="sip_403.ld" CONFIG_FILES_SSIP7000=""/>
</APPLICATION>

Above should demonstrate that all files that are specifically mentioned as phones will load their specified files.

Example SPIP501:

<APPLICATION_SPIP501 APP_FILE_PATH_SPIP501="sip_318.ld" CONFIG_FILES_SPIP501="phone1_318.cfg, sip_318.cfg"/>

So the phone would attempt to load the sip_318.ld  software, the phone1_318.cfg and the sip_318.cfg.

Since SIP 2.1.2 Polycom has introduced substitution strings that can be used when provisioning Polycom Phones via a server using either the000000000000.cfg or a individual <mac>.cfg

The community's VoIP FAQ contains this post here:

Oct 7, 2011 Question: Can I use substitutions when I provisioning my Phones?

Resolution: Please check => here <=

So above example would look like this:

<APPLICATION_SPIP501 APP_FILE_PATH_SPIP501="sip_318.ld" CONFIG_FILES_SPIP501="phone[PHONE_MAC_ADDRESS].cfg,phone1_318.cfg, sip_318.cfg"/>

Using the phone[PHONE_MAC_ADDRESS].cfg string in this case would cause each individual phone that fits into the 501 category to automatically substitute its own MAC Address and therefore load the individual configuration before attempting to load the other 2 files.

There is no need to use the cfcUtility for any other phones other than the configuration for phones planned to be running / updating to UCS 3.3.0 or newer.

I have in addition updated this FAQ post:

May 14, 2012 Question: Can I support a mix of legacy SIP and UCS Phones on the same Provisioning Server?
Resolution: Please check => here <=

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