Frequent Advisor


the incumbent Cyta in Cyprus doesn't provision Polycom IP phones on BroadWorks, so we'll have to configure them manually.

The VVX 450s don't subscribe to the List URI, are any additional parameters needed than below?


Attached is the user's List URI setting on BW's DMS.


Polycom Employee & Community Manager


Hello @Chris-M-Cy ,


welcome to the Polycom Community.

Both the community's Must Read First and the community's FAQ reference the basic minimum information a new or follow up post should contain.

This ensures the questions having to be asked are limited and any new or follow up post contains the right amount of details to ensure any voluntary participant within the community does not spend additional time chasing basic information.

As a reminder the basic information asked for:


  • Provide the exact Software Version of your Phone
  • Provide the Phone Model
  • Provide the Call Platform (aka openSIP,Skype for Business Online, Skype for Business on Premise, Lync)
  • Additional Polycom Infrastructure (RPRM,PDMS or BToE)
  • If applicable provide a backup of the phone in question

UC Software 4.0.0 or later via the Web Interface Utilities > Phone Backup & Restore > Phone Backup > Phone Backup. Please rename into .TXT or Zip the file to attach.
Since UC Software 5.9.0 simply provide this via the Web Interface Diagnostics > Download Support Information Package

  • If possible provide a Log and either attach them or use the Code Tag.Consult the Troubleshooting Section found within the FAQ if applicable
  • If possible provide the MAC Address or Serial of the device
  • Provide details for example if the issue is a day 1 issue or only happened after an upgrade or any other relevant details
  • For questions around Support please check here


Whilst providing some of these details may not directly impact any possible answer the community can provide, it does enable Polycom to have an overview of the current software used. In addition providing all details at the same time allow us to check logs or look up a potential support partners if an issue needs to come into support. It also enables us to verify the entitlement for using features.

Please ensure you always check the FAQ's and/or utilize the community search before posting any new topics or follow up post’s.

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


If official support is required please check how to phone or open a case here

The title Poly Employee & Community Manager is a community setting and does not reflect my role. I am just a simple volunteer in the community like everybody else. All posts and words are my own & do not represent the views of Employer.


⇓⇓⇓⇓⇓⇓⇓⇓⇓⇓⇓⇓⇓⇓⇓⇓⇓⇓⇓⇓SIGNATURE ⇓⇓⇓⇓⇓⇓⇓⇓⇓⇓⇓⇓⇓⇓⇓⇓⇓⇓⇓
Notice: This community forum is not an official Poly support resource, thus responses from Poly employees, partners, and customers alike are best-effort in attempts to share learned knowledge.
Please also ensure you always check the VoIP , Video Endpoint , Microsoft Voice , PSTN or other FAQ's in the different sections
Message 2 of 5
Frequent Advisor


Danke Steffen! ;-)

Software Version: Version=

Phone model: VVX 450

Call Platform: BroadWorks R22

Best Regards


Message 3 of 5


I havew a VVX 250 test phone registered to Broadworks R22 and BLF's are working. My phone is provisioned through my own provisioning server and I have BLF's working.


Firmware: 5.9.1

Opensips: Broadworks R22


My phone has 2 lines registered and currently using line 2 for BLF's and I have the following config set for BLF's 

<attendant attendant.reg="2" attendant.uri="sip:user_BLF@domain"/>

I had to add attendant.reg="2" to get BLF to work. if you have more than 1 line registered to the phone you may need to add attendant.reg="2" and replace 2 with the line you are using for BLF's


For reference here is the config options for BLF from firmware 5.9.1

  <attendant attendant.callAction="Dial-Pickup" attendant.reg="1" attendant.restrictPickup="0" attendant.ringType="ringer1" attendant.uri="">
      <attendant.behaviors.automata attendant.behaviors.automata.pickupOnBusy="1">
        <attendant.behaviors.display.remoteCallerID attendant.behaviors.display.remoteCallerID.automata="1" attendant.behaviors.display.remoteCallerID.normal="1">
        <attendant.behaviors.display.spontaneousCallAppearances attendant.behaviors.display.spontaneousCallAppearances.automata="0" attendant.behaviors.display.spontaneousCallAppearances.normal="1">
    <attendant.callActionMenu attendant.callActionMenu.enabled="0">
    <attendant.callWaiting attendant.callWaiting.enable="0" attendant.callWaiting.ring="silent">
    <attendant.displayHoldState attendant.displayHoldState.enable="0">
    <attendant.resourceList attendant.resourceList.1.address="" attendant.resourceList.1.bargeInMode="" attendant.resourceList.1.callAddress="" attendant.resourceList.1.display.spontaneousCallAppearances="auto" attendant.resourceList.1.hold.ringer="ringer11" attendant.resourceList.1.label="" attendant.resourceList.1.proceedingIsRecipient="0" attendant.resourceList.1.rejectParkOnBusy="0" attendant.resourceList.1.requestSilentBargeIn="0" attendant.resourceList.1.ringType="default" attendant.resourceList.1.type="" attendant.resourceList.2.address="" attendant.resourceList.2.bargeInMode="" attendant.resourceList.2.callAddress="" attendant.resourceList.2.display.spontaneousCallAppearances="auto" attendant.resourceList.2.hold.ringer="ringer11" attendant.resourceList.2.label="" attendant.resourceList.2.proceedingIsRecipient="0" attendant.resourceList.2.rejectParkOnBusy="0" attendant.resourceList.2.requestSilentBargeIn="0" attendant.resourceList.2.ringType="default" attendant.resourceList.2.type="">


I checked the broadworks template file and see it only sets the tag you have already set.

<attendant attendant.uri=""/>

 The Attendant URI in your config file looks correct based on the broadworks screenshot you sent. 

One thing I notices is your override file looks like it's incomplete as there is no closing tags. if your file is complete then I would recommend creating a separate config file that has the BLF tags and uploading that from the web interface.

Message 4 of 5
Frequent Advisor


Thank you,
I will import all your BLF config parameters from the web-UI and test it again.

I also had to use my own provisioning server and upgraded all phones last week to UCS 5.9.1 but it still didn't work.

According to Broadsoft's Partner Config Guide for Polycom VVX in the CPE kit downloaded from Broadsoft Xchange only the attendant.uri parameter was required since all phones have only 1 line registered.

From the service provider's pcap we can see that the phone subscribes successfully to the list but it cannot parse the BLF info sent by BW, so maybe additional config parameters are needed in the phone's config.

Regarding the MAC-web.cfg all web-UI overridden parameters are within the overrides tag and no additional opening/closing tags or set parameters are needed compared to the MAC.cfg.
You can check any MAC-web.cfg or MAC-phone.cfg on your provisioning server.
Message 5 of 5