no, you dont want to do the 2nd option.. because a CORRECTLY setup ftp site wont let anyone but root write to the files in the base directory. Only the sub directories like CONTACTS have permissions to let the phone's ftp user login and update the logs etc.

what you can do is create an identical models.txt entry in the user_provisioning/ directory for that device and change the line that says

output_3=${mac}-directory.xml

to

output_3=CONTACTS/${mac}-directory.xml

I will see about getting Alex to make the change in the master models.txt file

this is a sorta workaround method of populating the expansion module that someone requested of me. Its not the best method for polycom because the directory.xml is a file that can be modified both by the provisioner (the pbx) and by the provisionee (the end user adding entries on their phone). You dont want to tick off someone by wiping out their stored contacts if you can help it.

ive decided to axe the whole device.. there is a new method of monitoring an extension in polycom that is more conducive to the provisioning tool. The catch is it requires asterisk 1.6.2 or higher and requires polycom sip firmware 3.2.0 or higher.

however the method supports more advanced features like bliking when ringing, slow blink when on hold, and the ability to combine the feature with directed call pickup. I think the features are worth meeting the requirements.