2 posts / 0 new
Last post
jkeegan123
jkeegan123's picture
Joined: 2015/09/25
Points: 0

Hello,

I'm setting up a bunch of Polycom VVX 400's and I can't get the provisioning template to place any BLF's for PARK on the phones.

If I manually add the Park buttons through the web interface of the phone, they do monitor 701, 702, 703 correctly...but only if I add them manually.

LINE KEY for SIP LOGIN provisions just fine. We are provisioning with FTP.

I looked through the config generated for the phone (mac.cfg) and it doesn't seem to have the correct entries. After adding the manual Park keys and exporting the config, I see that this is what it wants added:

attendant.resourceList.1.address="701"
attendant.resourceList.2.address="702"
attendant.resourceList.3.address="703"
attendant.resourceList.1.label="Park 1"
attendant.resourceList.2.label="Park 2"
attendant.resourceList.3.label="Park 3"
attendant.resourceList.1.type="normal"
attendant.resourceList.2.type="normal"
attendant.resourceList.3.type="normal"

How can I resolve this? I usually use Yealink phones, I've never had to drop Park monitors on a Polycom. I can't get ANY BLF to provision. Is there a different way to do this with Polycom?

jakeness
jakeness's picture
Joined: 2017/02/15
Points: 30

This should work out of the box with a Polycom VVX 400
Looks good to me.
Are you starting you buttons after your span length?
Using BLF and not park
Remember setting via web interface takes priority over config changes
Here is mine:
reg.1.lineKeys="6"

attendant.resourceList.7.address="701"
attendant.resourceList.7.label="Park 1"
attendant.resourceList.7.type="automata"

attendant.resourceList.8.address="702"
attendant.resourceList.8.label="Park 2"
attendant.resourceList.8.type="automata"

attendant.resourceList.9.address="703"
attendant.resourceList.9.label="Park 3"
attendant.resourceList.9.type="automata"

attendant.resourceList.10.address="704"
attendant.resourceList.10.label="Park 4"
attendant.resourceList.10.type="automata"