READ THESE NOTICES BEFORE ACCEPTING THE DOWNLOAD OF POLYCOM® UC SOFTWARE 4.0.x:

Anonymous · ‎05-10-2012

Salvete! This is my first post here. I found my way here from Asterisk.org by way of Steffen Baier - thanks Steffen!

I have a Polycom IP 7000 Sounstation here that I am trying to bring online. It is hung up on a scren with "Updating sip_401b.ld, Please Wait." - and it never finishes.

Now, I am learning how all this works, and have browsed various documentation (there is so much), but I need some help. I had the bootrom upgrader for 4.3.0 in the polycom directory when it booted, and I saw that it uploaded that. Maybe it is my sip_401b.cfg file that is bad? Here are the contents:

<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<!-- Generated sip-basic.cfg Configuration File -->
<!-- For Polycom Soundstation IP5000 and SoundPoint IP 650 -->
<polycomConfig xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="/polycom/config-401b/polycomConfig.xsd">
  <voIpProt>
    <voIpProt.server voIpProt.server.1.address="xxx.xxx.x.xx" voIpProt.server.1.port="xxxx" />
    <voIpProt.SIP voIpProt.SIP.enable="1" />
  </voIpProt>
  <call call.transferOnConferenceEnd="1">
    <call.autoAnswer call.autoAnswer.H323="0" call.autoAnswer.micMute="1" call.autoAnswer.ringClass="ringAutoAnswer" call.autoAnswer.SIP="0" call.autoAnswer.videoMute="0"></call.autoAnswer>
    <call.autoOffHook call.autoOffHook.1.contact="" call.autoOffHook.1.enabled="0" call.autoOffHook.1.protocol="" call.autoOffHook.2.contact="" call.autoOffHook.2.enabled="0" call.autoOffHook.2.protocol=""></call.autoOffHook>
    <call.donotdisturb call.donotdisturb.perReg="0"></call.donotdisturb>
    <call.missedCallTracking call.missedCallTracking.1.enabled="1" call.missedCallTracking.2.enabled="1"></call.missedCallTracking>
    <call.serverMissedCall call.serverMissedCall.1.enabled="0" call.serverMissedCall.2.enabled="0"></call.serverMissedCall>
  </call>
  <device>
    <device.auth device.auth.localUserPassword="">
      <device.auth.localUserPassword device.auth.localUserPassword.set="0"></device.auth.localUserPassword>
    </device.auth>
    <device.em device.em.power="">
      <device.em.power device.em.power.set="0"></device.em.power>
    </device.em>
  </device>
  <lineKey lineKey.1.category="Unassigned" lineKey.1.index="0" lineKey.2.category="Unassigned" lineKey.2.index="0">
    <lineKey.reassignment lineKey.reassignment.enabled="0"></lineKey.reassignment>
  </lineKey>
  <reg reg.1.acd-agent-available="0" reg.1.acd-login-logout="0" reg.1.auth.domain="" reg.1.auth.optimizedInFailover="0" reg.1.auth.useLoginCredentials="0" reg.1.bargeInEnabled="0" reg.1.callsPerLineKey="24" reg.1.csta="0" reg.1.displayName="" reg.1.fwd.busy.contact="" reg.1.fwd.busy.status="0" reg.1.fwd.noanswer.contact="" reg.1.fwd.noanswer.ringCount="0" reg.1.fwd.noanswer.status="0" reg.1.lcs="0" reg.1.lineKeys="1" reg.1.musicOnHold.uri="" reg.1.outboundProxy.failOver.failBack.timeout="3600" reg.1.outboundProxy.failOver.failRegistrationOn="1" reg.1.outboundProxy.failOver.onlySignalWithRegistered="1" reg.1.outboundProxy.failOver.reRegisterOn="0" reg.1.outboundProxy.port="0" reg.1.outboundProxy.transport="DNSnaptr" reg.1.protocol="" reg.1.ringType="default" reg.1.serverFeatureControl.activateCodeSequence.cf.always="" reg.1.serverFeatureControl.activateCodeSequence.cf.busy="" reg.1.serverFeatureControl.activateCodeSequence.cf.noanswer="" reg.1.serverFeatureControl.activateCodeSequence.dnd="" reg.1.serverFeatureControl.cf="0" reg.1.serverFeatureControl.deActivateCodeSequence.cf.always="" reg.1.serverFeatureControl.deActivateCodeSequence.cf.busy="" reg.1.serverFeatureControl.deActivateCodeSequence.cf.noanswer="" reg.1.serverFeatureControl.deActivateCodeSequence.dnd="" reg.1.serverFeatureControl.dnd="0" reg.1.serverFeatureControl.signalingMethod="subscribeAsFeatureEvent" reg.1.serverFeatureControl.subscribeToUri="" reg.1.telephony="1" reg.1.thirdPartyName="" reg.1.type="private" reg.1.useCompleteUriForRetrieve="1" reg.1.server.1.expires="3600" reg.1.server.1.expires.lineSeize="30" reg.1.server.1.expires.overlap="60" reg.1.server.1.lcs="0" reg.1.server.1.retryMaxCount="3" reg.1.server.1.retryTimeOut="0" reg.1.server.1.specialInterop="standard" reg.1.server.2.expires="3600" reg.1.server.2.expires.lineSeize="30" reg.1.server.2.expires.overlap="60" reg.1.server.2.lcs="0" reg.1.server.2.retryMaxCount="3" reg.1.server.2.retryTimeOut="0" reg.1.server.2.specialInterop="standard" reg.2.acd-agent-available="0" reg.2.acd-login-logout="0" reg.2.auth.domain="" reg.2.auth.optimizedInFailover="0" reg.2.auth.useLoginCredentials="0" reg.2.bargeInEnabled="0" reg.2.callsPerLineKey="24" reg.2.csta="0" reg.2.displayName="" reg.2.fwd.busy.contact="" reg.2.fwd.busy.status="0" reg.2.fwd.noanswer.contact="" reg.2.fwd.noanswer.ringCount="0" reg.2.fwd.noanswer.status="0" reg.2.lcs="0" reg.2.lineKeys="1" reg.2.musicOnHold.uri="" reg.2.outboundProxy.failOver.failBack.timeout="3600" reg.2.outboundProxy.failOver.failRegistrationOn="1" reg.2.outboundProxy.failOver.onlySignalWithRegistered="1" reg.2.outboundProxy.failOver.reRegisterOn="0" reg.2.outboundProxy.port="0" reg.2.outboundProxy.transport="DNSnaptr" reg.2.protocol="" reg.2.ringType="default" reg.2.serverFeatureControl.activateCodeSequence.cf.always="" reg.2.serverFeatureControl.activateCodeSequence.cf.busy="" reg.2.serverFeatureControl.activateCodeSequence.cf.noanswer="" reg.2.serverFeatureControl.activateCodeSequence.dnd="" reg.2.serverFeatureControl.cf="0" reg.2.serverFeatureControl.deActivateCodeSequence.cf.always="" reg.2.serverFeatureControl.deActivateCodeSequence.cf.busy="" reg.2.serverFeatureControl.deActivateCodeSequence.cf.noanswer="" reg.2.serverFeatureControl.deActivateCodeSequence.dnd="" reg.2.serverFeatureControl.dnd="0" reg.2.serverFeatureControl.signalingMethod="subscribeAsFeatureEvent" reg.2.serverFeatureControl.subscribeToUri="" reg.2.telephony="1" reg.2.thirdPartyName="" reg.2.type="private" reg.2.useCompleteUriForRetrieve="1" reg.2.server.1.expires="3600" reg.2.server.1.expires.lineSeize="30" reg.2.server.1.expires.overlap="60" reg.2.server.1.lcs="0" reg.2.server.1.retryMaxCount="3" reg.2.server.1.retryTimeOut="0" reg.2.server.1.specialInterop="standard" reg.2.server.2.expires="3600" reg.2.server.2.expires.lineSeize="30" reg.2.server.2.expires.overlap="60" reg.2.server.2.lcs="0" reg.2.server.2.retryMaxCount="3" reg.2.server.2.retryTimeOut="0" reg.2.server.2.specialInterop="standard"></reg>
  <se se.destination="chassis">
    <se.rt>
      <se.rt.modification se.rt.modification.enabled="1"></se.rt.modification>
    </se.rt>
  </se>
  <up up.25mm="1" up.25mmRealTime="1" up.accessibilityFeatures="0" up.analogHeadsetOption="0" up.audioMode="0" up.callTypeOrderVoice="0" up.cfgWarningsEnabled="1" up.displayOperMode="0" up.handsfreeMode="1" up.headsetMode="0" up.hideDateTimeWhenNotSet="0" up.idleStateView="0" up.localClockEnabled="1" up.manualProtocolRouting="1" up.mwiVisible="0" up.onHookDialingEnabled="1" up.pstnSetup="0" up.simplifiedSipCallInfo="0" up.useDirectoryNames="1" up.warningLevel="0" up.welcomeSoundEnabled="1" up.welcomeSoundOnWarmBootEnabled="0">
    <up.2P5mmJack up.2P5mmJack.mode="0"></up.2P5mmJack>
    <up.audioSetup up.audioSetup.auxInput="2" up.audioSetup.auxOutput="2"></up.audioSetup>
    <up.backlight up.backlight.idleIntensity="1" up.backlight.idleIntensity.SL8440="0" up.backlight.idleIntensity.SL8450="0" up.backlight.idleIntensity.SL8452="0" up.backlight.onIntensity="3" up.backlight.timeout="40" up.backlight.timeout.SL8440="10" up.backlight.timeout.SL8450="10" up.backlight.timeout.SL8452="10"></up.backlight>
    <up.headset up.headset.phoneVolumeControl="auto"></up.headset>
    <up.hearingAidCompatibility up.hearingAidCompatibility.enabled="0"></up.hearingAidCompatibility>
    <up.idleBrowser up.idleBrowser.enabled="0"></up.idleBrowser>
    <up.manualProtocolRouting up.manualProtocolRouting.softKeys="1"></up.manualProtocolRouting>
    <up.offHookAction up.offHookAction.none="0"></up.offHookAction>
    <up.pictureFrame up.pictureFrame.folder="" up.pictureFrame.timePerImage="5"></up.pictureFrame>
    <up.screenSaver up.screenSaver.enabled="0" up.screenSaver.waitTime="15"></up.screenSaver>
    <up.toneControl up.toneControl.bass="0" up.toneControl.treble="0"></up.toneControl>
  </up>
  <voIpProt>
    <voIpProt.SIP>
      <voIpProt.SIP.assuredService>
        <voIpProt.SIP.assuredService.namespace>
          <voIpProt.SIP.assuredService.namespace.label>
            <voIpProt.SIP.assuredService.namespace.label.custom voIpProt.SIP.assuredService.namespace.label.custom.1="" voIpProt.SIP.assuredService.namespace.label.custom.2=""></voIpProt.SIP.assuredService.namespace.label.custom>
            <voIpProt.SIP.assuredService.namespace.label.drsn voIpProt.SIP.assuredService.namespace.label.drsn.1="" voIpProt.SIP.assuredService.namespace.label.drsn.2=""></voIpProt.SIP.assuredService.namespace.label.drsn>
            <voIpProt.SIP.assuredService.namespace.label.dsn voIpProt.SIP.assuredService.namespace.label.dsn.1="" voIpProt.SIP.assuredService.namespace.label.dsn.2=""></voIpProt.SIP.assuredService.namespace.label.dsn>
            <voIpProt.SIP.assuredService.namespace.label.UCRdrsn voIpProt.SIP.assuredService.namespace.label.UCRdrsn.1="" voIpProt.SIP.assuredService.namespace.label.UCRdrsn.2=""></voIpProt.SIP.assuredService.namespace.label.UCRdrsn>
            <voIpProt.SIP.assuredService.namespace.label.UCRdsn voIpProt.SIP.assuredService.namespace.label.UCRdsn.1="" voIpProt.SIP.assuredService.namespace.label.UCRdsn.2=""></voIpProt.SIP.assuredService.namespace.label.UCRdsn>
          </voIpProt.SIP.assuredService.namespace.label>
        </voIpProt.SIP.assuredService.namespace>
      </voIpProt.SIP.assuredService>
    </voIpProt.SIP>
  </voIpProt>
</polycomConfig>

What can I do? This new configuration is confusing.

Also, I still have all my phones using <macaddress>.cfg files. This is because I have a mix of soundpoints 430, 601, 650 (which I haven't installed yet), an ip5000 and an ip7000. So they all have separate settings, hence the <macaddress>.cfg configurations. Please help!

Anonymous · ‎05-23-2012

Mr. Baier,

This post is the closest you have come to explaining things clearly. You have given some useful, full examples here, and some easy-to-follow, direct explanations of things, and have not simply directed me to various FAQ pages (most of which I *have* read, already).

Let me say that I have spent nearly two weeks trying to figure things out using the online documentation. The Administrator's Guide mostly contains lists of features and changes - only a small portion of it is actually about how to configure your polycom ftp directory.

What is missing the most, in my opinion, are complete examples.

I have related that the documentation is difficult - and I'll tell you why I think that. Firstly, they are not designed like tutorials - where they try to teach somebody how to do something. Actually, they are FAQ - Facts, basically - a list of notes. For someone who comes to site for answers, they don't find an easy entry. For example, take the "substitution strings". Most people who are going to do anything with configuration files will know at least a tidbit of programming. Why not just say they are "variables" or "tokens" - or at least explain just what a "substitution string" is? And then, how do you use one? I had to figure out on my own that I had to use the literal phrase [PHONE_MAC_ADDRESS] to represent the macaddress of the actual telephone. Reading through the file, it did say I had to use the square brackets - which made me wonder if that meant to put [<macaddress>]. After awhile it dawned on me what was happening - my point is, that the docs are more like someone's personal notes to themself.

Another thing that I couldn't understand (and I have read everything!) is PHONE_PART_NUMBER. From the substitutions explanation, there is no way to know what that means, or what, exactly is swapped for that token? I still am not sure exactly what is swapped for [PHONE_MODEL]. You know what? That phrase is to be found nowhere at all in the 4.0.1 Administrator's Guide. Where would I find a list of each token, and a description and example of what is substituted for them? The substitutions page gives a list, but doesn't say if there are any more, and doesn't describe them. Here is an example of the kind of explanation that would have helped me understand what the substitutions were and how they work. This is just an example of what I mean by easier documentation:

Token	example value	description
[PHONE_MODEL]	SoundPointIP430	The phone's brand name
[PHONE_PART_NUMBER]	2345-11402-001	polycom model identification number (corresponds to sip.ld)
[MACADDRESS]	0004f21234ab	The phone's actual mac address
[PHONE_MAC_ADDRESS]	0004f21234ab	same as above

For the token to work, it must appear exactly as it is written above - in all caps and surrounded with the square brackets.  When the polycom phone reads the configuration file, anywhere it finds that token, it will replace it with value that it reads from the actual phone.  You can add any text you want to before or after the token - only the token will be replaced.  These tokens can be used in the 000000000000.cfg.  Consider this example below.  When the phones look for their sip.ld files, they will look for an .ld file that is named the same as their phone's part number:  [PHONE_PART_NUMBER].sip.ld  - thus, the IP430 will look for this file:  2345-11402-001.sip.id

------------------------------Example 000000000000.cfg------------------------------------------------------------------------
<?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: 126421 $ -->
<APPLICATION APP_FILE_PATH="[PHONE_PART_NUMBER].sip.ld" CONFIG_FILES="[PHONE_MAC_ADDRESS]-extension.cfg" MISC_FILES="" LOG_FILE_DIRECTORY="" OVERRIDES_DIRECTORY="" CONTACTS_DIRECTORY="" LICENSE_DIRECTORY="" USER_PROFILES_DIRECTORY="" CALL_LISTS_DIRECTORY="">   
 <APPLICATION_SPIP430 APP_FILE_PATH_SPIP430="[PHONE_PART_NUMBER].sip.ld" CONFIG_FILES_SPIP430="sip_326.cfg, [PHONE_MAC_ADDRESS]-extension.cfg"/>
 <APPLICATION_SPIP600 APP_FILE_PATH_SPIP600="[PHONE_PART_NUMBER].sip.ld" CONFIG_FILES_SPIP600="sip_318.cfg, [PHONE_MAC_ADDRESS]-extension.cfg"/>
 <APPLICATION_SPIP601 APP_FILE_PATH_SPIP601="[PHONE_PART_NUMBER].sip.ld" CONFIG_FILES_SPIP601="sip_318.cfg, [PHONE_MAC_ADDRESS]-extension.cfg"/>
</APPLICATION>

Mr. Baier, it is obvious to me that you want to help folks (after all, you did make every attempt to help me!), and it is also obvious that you know how all of this works - and at a most expert level, too. It would help alot if you would try to understand how to explain things to the person listening. Some folks need to understand it one way, some another. The same way is not easy for everyone. That is why people go to forums - to ask questions so people can help them the way they need help. I know you have become frustrated with me because it seems like I don't listen - but on the contrary, I find it difficult to get you to explain something that you take for granted.

Anyway, I hope you take me the right way here. I am going to mark this thread solved.

Thank you for all of your help; I hope you haven't written me off for the future!

-BGM

View solution in original post

SteffenBaierUK · ‎05-14-2012

Hello BGM,

I have just added a new FAQ section that discussed the mix of legacy Phones and new Phones running different configurations and Versions of SIP / UCS Software.

You can find this => here <=

It is of utter most importance to check the phones log files as they will contain the reason for the phone being unable to load a software.

You mention a sip_401b.cfg file. I can only assume that you or your SIP provider/platform have named the file like this.

If you are trying to run a SSIP 7000 on a UCS 4.x.x Software you no longer use the BootROM, you will have to run the Upgrader and then the Updater instead.

The latest Version can be found => here <= and is described in detail in the Updater Release Notes.

Only if the Phone has downloaded the Upgrader and Updater you are then able to upgrade the Phone to UCS 4.0.2 Rev B (latest current Version)

Best Regards

Steffen Baier

------------------------------------------------
Notice: I am an HP Poly employee but all replies within the community are done as a volunteer outside of my day role. This community forum is not an official HP Poly support resource, thus responses from HP Poly employees, partners, and customers alike are best-effort in attempts to share learned knowledge.
If you need immediate and/or official assistance for former Poly\Plantronics\Polycom please open a service ticket through your support channels
For HP products please check HP Support.

Please also ensure you always check the General VoIP , Video Endpoint , UC Platform (Microsoft) , PSTN

Anonymous · ‎05-14-2012

Thanks for answering, Mr. Baier.

Yes, I named the bootroms like that so that I can point to them in each phone's .cfg file. Thus, I use a different .ld and a matchingly named sip.cfg file for each type of phone. All of my phones work this way.

However, with the ip7000,it wouldn't take the sip_401b.cfg (the ip5000 would, however), so I did get it to load the 3.3.2 configuration - both sip_332.ld and sip_332.cfg. The phone is operational. With regards to the upgrading of the bootrom, I saw the phone upgrade to 4.3, and says so now in its platform setting.

I do understand that I am going about this the wrong way. I do realize that not all the bootroms are compatible with older versions, which is the reason why I've gotten this setup that I have. Problem is that I inherited the system from someone else and have to figure everything out myself. I find so much of the polycom documentation to be long and tedious and difficult. What I need is a few sample configurations so I can see and compare.

Since you cannot rename the BootROM release files like the SIP release files the relevant <PHONE_PART_NUMBER>-bootrom.ld files will need to be placed on the provisioning server for each phone model.

This seems to be what I have done. I have a bootrom.ld file for each model of phone. Then, in my <macaddress>.cfg file for each phone, I point to that .ld file.

Here is my 000000000000.cfg file, which is actually never used because each phone has a <macaddress>.cfg file, instead.

<?xml version="1.0" encoding="utf-8" 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: 000000000000.cfg,v $  $Revision: 1.21.20.3 $ -->

<APPLICATION APP_FILE_PATH="sip.ld" CONFIG_FILES="phone1.cfg, sip.cfg" MISC_FILES="" LOG_FILE_DIRECTORY="" OVERRIDES_DIRECTORY="" CONTACTS_DIRECTORY="" LICENSE_DIRECTORY="">
  <APPLICATION_SPIP430 APP_FILE_PATH_SPIP430="sip_326.ld" CONFIG_FILES_SPIP430="phone1_326.cfg, sip_326.cfg" />
  <APPLICATION_SPIP601 APP_FILE_PATH_SPIP601="sip_317.ld" CONFIG_FILES_SPIP601="phone1_317.cfg, sip_317.cfg" />
   <APPLICATION_SSIP4000 APP_FILE_PATH_SSIP4000="sip_401b.ld" CONFIG_FILES_SSIP4000="phone1_316.cfg, sip_401b.cfg"/>
  <APPLICATION_SSIP5000 APP_FILE_PATH_SSIP5000="sip_401b.ld" CONFIG_FILES_SSIP5000="sip-401b.cfg" />
  <APPLICATION_SSIP7000 APP_FILE_PATH_SSIP7000="sip_401b.ld" CONFIG_FILES_SSIP7000="sip-401b.cfg" />
</APPLICATION>

However, I still don't see how to set the msg settings (for example) for a particular phone. I see how to make that setting in the phone_1.cfg - but that would affect every phone that is that model - it is a global setting, not an individual setting.

Where would I make changes for individual phone settings if there is no <mac>.cfg?

SteffenBaierUK · ‎05-14-2012

Hello BGM,

I had provided you with a Link explaining these details.

In addition when downloading the new UCS Software a prompt appears:

READ THESE NOTICES BEFORE ACCEPTING THE DOWNLOAD OF POLYCOM® UC SOFTWARE 4.0.x:

1) Before you can successfully install UC Software 4.0.x onto phones running Polycom® UCS released prior to version 4.0.0, you must perform a required upgrade procedure using the Polycom® Upgrader 4.0.0 Utility.

Before you download and install Polycom® UC Software version 4.0.x or higher, Polycom strongly recommends that you review the changes to the upgrade procedures detailed in the Polycom® UC Software 4.0.0 Administrators’ Guide or newer and Engineering Advisory 64731 Polycom® UC Software 4.0.0: Upgrade and Downgrade Methods.

Above clearly states that a special process is required when installing the UCS Software.

Your SSIP7000 according to your statement is Running a BootROM 4.3.0. This BootROM will be unable to load the UCS 4.0.x Software.

You need to use the Upgrader and Updater as this contains the latest Supported Version and this is explained in the Release Notes => here <=

Once the Phone is running the latest UCS 4.0.x (4.0.2 Rev B is the current latest) you can easily implement this or other phones using the substitution method to load individual files.

Best Regards

Steffen Baier

Polycom Global Services

------------------------------------------------
Notice: I am an HP Poly employee but all replies within the community are done as a volunteer outside of my day role. This community forum is not an official HP Poly support resource, thus responses from HP Poly employees, partners, and customers alike are best-effort in attempts to share learned knowledge.
If you need immediate and/or official assistance for former Poly\Plantronics\Polycom please open a service ticket through your support channels
For HP products please check HP Support.

Please also ensure you always check the General VoIP , Video Endpoint , UC Platform (Microsoft) , PSTN

Anonymous · ‎05-22-2012

Mr. Baier,

Sorry to take so long to respond - I guess the email alert got lost somewhere...

I still don't understand. There are sooo many files and soooo much to read, and every name is branded. It makes my poor, hard head ache; there is hardly any tutorials on the whole matter, hardly any screenshots, and no simple, easy-to-follow directions.

I am looking for the type of directions like this:

Download such-and-such files.

Extract such-and-such file to your ftp directory.

Also extract this other file to the same directory.

Backup up such-and-such files.

Edit this file like this in order to configure the bootroms for these kinds of phones.

Now, to configure the individual settings for each phone, add this line to this file.

Once I have done this, I will be able to repeat the steps for my other phones.

Yes, I DID read that notice that you posted again for me. And had even downloaded the utility - the CFCUtility. However, the ReadMe.txt file that comes with the package says it is for the conversion of configuration files. My IP7000 is brand new - I don't have any configuration files to convert.

Also, I still don't understand how to configure the individual phone settings without using a mac-address.cfg. I understand using the 0000000.cfg as a sort of "router" to direct each model of phone towards its proper bootrom, and towards its proper default config. Now, in the FAQ, I do read this:

The substitution strings [PHONE_MODEL], [PHONE_PART_NUMBER] , [MACADDRESS], and [PHONE_MAC_ADDRESS] can be used.

But I don't see any example of how to use a [MACADDRESS] in that file. How can I set the settings for an individual phone?

Thanks for all your help, Mr. Baier, but I have not, in all the documentation to which I have been directed, found what I need to configure my system. What I need is a tutorial, not a list of features, enhancements and specifications.

SteffenBaierUK · ‎05-22-2012

Hello,

usually you should call your Polycom Reseller or call Polycom Support and get charged the PPI fee.

There are so many topics regarding this within this community or around the web covering this over and over.

Download:

UCS Software 4.0.2 Rev B and unzip it into a Folder

Download the Updater and unzip it into the same Folder

Download the Upgrader and unzip it into the same Folder

Create a FTP User and point it to that directory

Setup your phone as described in the post's I highlighted for you to point to that FTP User

Boot your phone and let it upgrade and install the UCS Software

Configure your SIP Details as described => here <=

If you are still struggling call your Polycom Reseller or call Polycom Support and get charged the PPI fee.

Best Regards

Steffen Baier

------------------------------------------------
Notice: I am an HP Poly employee but all replies within the community are done as a volunteer outside of my day role. This community forum is not an official HP Poly support resource, thus responses from HP Poly employees, partners, and customers alike are best-effort in attempts to share learned knowledge.
If you need immediate and/or official assistance for former Poly\Plantronics\Polycom please open a service ticket through your support channels
For HP products please check HP Support.

Please also ensure you always check the General VoIP , Video Endpoint , UC Platform (Microsoft) , PSTN

Anonymous · ‎05-22-2012

Okay, I've almost got it, I think, thanks to your patient assistance, Mr. Baier. Please correct me if I am wrong. (I think I've downloaded every manual there is to find!)

From the various packages, I have extracted the bootroms and the proper upgraders. Since my ip430's and ip601's are too old for the uc software, they get their own ld files named with their last versions (as per the manuals). They also get their own phone1.cfg and sip.cfg named with their own versions, too.

I have used these packages:

UC_Software_4_0_2B_release_sig_split.zip - for the ip650, 5000 and 7000

spip_ssip_3_1_8_legacy_release_sig_split.zip - for the ip601

spip_ssip_vvx_3_2_6_release_sig_split.zip - for the ip430

The newer phones, the ip650, ip5000 and ip7000 will use the new bootrom, hence the present upgraders, and the new .ld files. I didn't see in the manuals that I needed to rename the .ld files for phones using uc software. Here are my directory contents:

sip.ver (it contains this text: "4.0.2.11307")

bootrom.ld

2345-12600-001.bootrom.ld
2345-12600-001.sip.ld
3111-30900-001.bootrom.ld
3111-30900-001.sip.ld
3111-40000-001.bootrom.ld
3111-40000-001.sip.ld

sip_318.ld
sip_326.ld

000000000000.cfg
phone1_318.cfg
phone1_326.cfg
sip_318.cfg
sip_326.cfg

000000000000-directory~.xml

Config (directory)
SoundPointIPLocalization(directory)

languages (directory)

And the contents of 000000000000.cfg:

<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_SPIP430 APP_FILE_PATH_SPIP430="sip_326.ld" CONFIG_FILES_SPIP430="phone1_326.cfg, sip_326.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>

Now, for the settings for each individual phone, am I right to create a <macaddress>.cfg file and make the contents like this?:

<PHONE_CONFIG>
	<OVERRIDES 
                reg.3.ringType="12" reg.2.ringType="6" reg.1.ringType="11" reg.1.displayname="5555" reg.1.label="Me"
                msg.mwi.1.subscribe="5555"
        />
</PHONE_CONFIG>

That means that <macaddress>.cfg doesn't need this line anymore, right, since that info is in 000000000000.cfg?:
<APPLICATION APP_FILE_PATH="sip_317.ld" CONFIG_FILES="0004f20588dd---2536.cfg, sip_317.cfg" MISC_FILES="" LOG_FILE_DIRECTORY="logs" OVERRIDES_DIRECTORY="" CONTACTS_DIRECTORY=""/>

Okay, if I am doing well so far, then I've only a few other things to clear up. I am sure a post like this will help others, too.

Do I create a <macaddress>.cfg file for my uc software phones too?
Do I put an entry in 000000000000.cfg for the 3111-40000-001.sip.ld that the ip7000 uses?
How do the uc devices get a config?
Does the ip7000 need a sip.cfg?
Is it okay not to have a file called sip.cfg in the ftp folder?
Is the "Config" folder only to hold the samples, or do the uc devices use this directory (I don't see any config references to the directory)?

Thanks again!

SteffenBaierUK · ‎05-23-2012

Now, for the settings for each individual phone, am I right to create a <macaddress>.cfg file and make the contents like this?:
<PHONE_CONFIG>
	<OVERRIDES 
                reg.3.ringType="12" reg.2.ringType="6" reg.1.ringType="11" reg.1.displayname="5555" reg.1.label="Me"
                msg.mwi.1.subscribe="5555"
        />
</PHONE_CONFIG>

That means that <macaddress>.cfg doesn't need this line anymore, right, since that info is in 000000000000.cfg?:
<APPLICATION APP_FILE_PATH="sip_317.ld" CONFIG_FILES="0004f20588dd---2536.cfg, sip_317.cfg" MISC_FILES="" LOG_FILE_DIRECTORY="logs" OVERRIDES_DIRECTORY="" CONTACTS_DIRECTORY=""/>
Okay, if I am doing well so far, then I've only a few other things to clear up. I am sure a post like this will help others, too.

Do I create a <macaddress>.cfg file for my uc software phones too?

Do I put an entry in 000000000000.cfg for the 3111-40000-001.sip.ld that the ip7000 uses?

How do the uc devices get a config?

Does the ip7000 need a sip.cfg?

Is it okay not to have a file called sip.cfg in the ftp folder?

Is the "Config" folder only to hold the samples, or do the uc devices use this directory (I don't see any config references to the directory)?

Thanks again!

Above <mac>.cfg is wrong.

A <mac>.cfg or 000000000000.cfg always only points to a filename or Location\filename combination. It does not contain parameters. Please check my updated FAQ Entry for 000000000000.cfg => here <=

To your question 1:

Every Phone will need a 000000000000.cfg or <mac>.cfg independant of the SIP / UCS Version

To your question 2:

The phones automatically download the correct sip.ld if this guide is followed => here <=

To your question 3:

Like every other device. They load their 000000000000.cfg or <mac>.cfg from a provisioning server

To your question 4:

Check this post => here <= explaing the relevance of the sip.cfg and phone1.cfg. If you are running anything after UCS 3.3.x a sip.cfg is not needed.

As long as your legacy phones are aware via the 000000000000.cfg or <mac>.cfg what their sip.cfg and phone1.cfg are called they will load it.

To your question 5:

See question 4

To your question 6:

Again the phones will only load the files or location\filename specified in the CONFIG_FILES="". The \config Files Subdirectory contains templates for people being used to the sip.cfg and phone1.cfg.

If you are still struggling call your Polycom Reseller or call Polycom Support and get charged the PPI fee.

Best Regards

Steffen Baier

------------------------------------------------
Notice: I am an HP Poly employee but all replies within the community are done as a volunteer outside of my day role. This community forum is not an official HP Poly support resource, thus responses from HP Poly employees, partners, and customers alike are best-effort in attempts to share learned knowledge.
If you need immediate and/or official assistance for former Poly\Plantronics\Polycom please open a service ticket through your support channels
For HP products please check HP Support.

Please also ensure you always check the General VoIP , Video Endpoint , UC Platform (Microsoft) , PSTN

Anonymous · ‎05-23-2012

Thanks again - I think we are getting closed to being done with it.

Now, you just said,

"Every Phone will need a 000000000000.cfg or <mac>.cfg independant of the SIP / UCS Version"

but in the Admin Guide 4.0.1, it says

"6 Remove the <MACaddress>.cfg files on your provisioning server if the files correspond to legacy phones."

So, if I am running a mix, do I need a <macaddress>.cfg file for each phone or not, if I want to use a centralized configuration?

If I use <macadddress>.cfg, then don't I have to specify an applicatin setting therein? If so, doesn't that negate the use of the 000000000000.cfg configuration tell the phones which application to use?

Okay, now, you also said:

"Like every other device. They load their 000000000000.cfg or <mac>.cfg from a provisioning server"

That means the devices load one OR the OTHER. I understand THAT - but it seems you are telling me to use both. This is still not clear.

What I want to do is to use the 000000000000.cfg instead of a <mac>.cfg to tell all of my phones which .ld files and which sip.cfg files to use, that way, I don't have to name the sip.ld and sip.cfg files in every phone's <mac>.cfg.

So, if I define the sip.ld and sip.cfg in the 0000.cfg, then that means I don't need to specify an application inside the <mac>.cfg?

Also, it seems that I need a <mac>.cfg for every uc phone, no matter what, right? After all, there is no entry for them in the 0000.cfg.

If I use a <mac>.cfg file with this in it:

"<APPLICATION APP_FILE_PATH="sip_318.ld" CONFIG_FILES="5555.cfg, sip_318.cfg" MISC_FILES="" LOG_FILE_DIRECTORY="logs" OVERRIDES_DIRECTORY="" CONTACTS_DIRECTORY=""/>"

then what good would it do to have any entry for sip_318 in the 0000.cfg? I don't get that.

SteffenBaierUK · ‎05-23-2012

This is my last attempt to answer your questions.

Source:

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

Resolution: Please check => here <=

the Phone on booting from the Provisioning Server will always look for it's own <mac>.cfg file and load this if it can be found.

A <mac>.cfg can be created by opening the original 000000000000.cfg and storing it with the MAC Address of a Phone.

NOTE: The <mac>.cfg is just a place holder in this explanation for the Phones real unique MAC Address.

In the absence of a individual <mac>.cfg the Phone will load the 000000000000.cfg.

Above clearly explains what the Phone does. It checks for a <mac>.cfg and if this is not there it loads a 000000000000.cfg

If you are running a mix of legacy phones you will only need the 000000000000.cfg that comes with for example the UCS 4.0.2 Rev B download.

This has the separate sections for current phones:

and as an example (there are more in there) for a SPIP301

..

<APPLICATION_SPIP301 APP_FILE_PATH_SPIP301="sip_318.ld" CONFIG_FILES_SPIP301="phone1_318.cfg, sip_318.cfg"/>

..

Above again clearly shows what the Phones will load if there is no individual <mac>.cfg.

The "new" phones will load the sip.ld but no configuration (as we have nothing in CONFIG_FILES="")

The SPIP301 will load the sip_318.ld and phone1_318.cfg and sip_318.cfg (as we have it specified in CONFIG_FILES_SPIP301="phone1_318.cfg, sip_318.cfg"/>)

I cannot make myself more clear and all this information is documented and has been successfully used for years by uncountable users.

You can then utilize the substitution method and provide individual files within the 0000000000000.cfg via :

...

!! New Phone running UCS !!====>>><APPLICATION APP_FILE_PATH="sip.ld" CONFIG_FILES="[PHONE_MAC_ADDRESS]-extension.cfg,site.cfg" MISC_FILES="" LOG_FILE_DIRECTORY="" OVERRIDES_DIRECTORY="" CONTACTS_DIRECTORY="" LICENSE_DIRECTORY="" USER_PROFILES_DIRECTORY="" CALL_LISTS_DIRECTORY="">

...

!! Old Phone running SIP !!====>>><APPLICATION_SPIP301 APP_FILE_PATH_SPIP301="sip_318.ld" CONFIG_FILES_SPIP301="[PHONE_MAC_ADDRESS]-extension.cfg,site.cfg,phone1_318.cfg, sip_318.cfg"/>

...

Above will need you to create 3 files.

File 1 for a made up mac of 123456789012 called 123456789012-extension.cfg

File 2 for a made up mac of 123456789013 called 123456789013-extension.cfg

File 3 that will contain a configuration for your site with the Sip Server details and other settings that apply to multiple phones.

All phones will load their SIP / UCS Software and matching BootROM/Updater

Your New Phone will then load File1 and File 3

Your SPIP301 will then load File 2, File 3, phone1_318 and sip_318

Any additional Phone will only need individual [PHONE_MAC_ADDRESS]-extension.cfg

NOTE: !! This is my last reply and any further free support needs to come from any other Polycom Community member that is willing to go into more detail as I have already done !!

ADDED EXTRA INFORMATION TO HIGHLIGHT THE DIFFERENCE BETWEEN OLD & NEW

Best Regards

Steffen Baier

------------------------------------------------
Notice: I am an HP Poly employee but all replies within the community are done as a volunteer outside of my day role. This community forum is not an official HP Poly support resource, thus responses from HP Poly employees, partners, and customers alike are best-effort in attempts to share learned knowledge.
If you need immediate and/or official assistance for former Poly\Plantronics\Polycom please open a service ticket through your support channels
For HP products please check HP Support.

Please also ensure you always check the General VoIP , Video Endpoint , UC Platform (Microsoft) , PSTN

IP7000 Stuck on Loading sip_401b.ld

Create an account on the HP Community to personalize your profile and ask a question

READ THESE NOTICES BEFORE ACCEPTING THE DOWNLOAD OF POLYCOM® UC SOFTWARE 4.0.x: