Hello,
I am test driving FusionPBX. I have successfully provisioned auto-provisioned an Aastra 6867i, at least as far as registering extensions on it. I am having some trouble getting the programmable keys to show up; they just don't.
Under "Accounts > Devices" and then I edit my specific phone, I added the following under the "Keys" section:
I was able to add two different extensions on the phone (Line 1 and Line 2) and have them register, so *some* of that info does pass through; I just can't seem to figure out how to get the programmable keys to show up?
Also, instead of editing the keys on each device separately, is there an easy way to add the programmable keys to a "global" template so they apply to all phones? The only way I can see to possibly do it is to do something like this:
One other question: I see the Aastra templates just have 'aastra.cfg' and '{mac}.cfg' files, but Aastra phones do look for additional files, particularly a model-specific file (e.g., '6867i.cfg'). I thought maybe just adding a '6867i.cfg' to the '686x' template directory might work, but while watching the Nginx access.log file, the phone was still getting a "404" error for that file, so that dosn't appear to be the way to do it. *Is* there a way allow the phone to find such an additional file? I suspect it would involve editing some PHP code to have it identify the model and grab the appropriate vendor file?
Thanks!
I am test driving FusionPBX. I have successfully provisioned auto-provisioned an Aastra 6867i, at least as far as registering extensions on it. I am having some trouble getting the programmable keys to show up; they just don't.
Under "Accounts > Devices" and then I edit my specific phone, I added the following under the "Keys" section:
Code:
Category,Key,Aastra,Line,Value,Label
"Programmable",1,"DND",1,(left blank),"DND"
"Programmable",2,"Speed Dial",1,"","*97"
"Programmable",3,"BLF Xfer",1,"John Smith","403"I was able to add two different extensions on the phone (Line 1 and Line 2) and have them register, so *some* of that info does pass through; I just can't seem to figure out how to get the programmable keys to show up?
Also, instead of editing the keys on each device separately, is there an easy way to add the programmable keys to a "global" template so they apply to all phones? The only way I can see to possibly do it is to do something like this:
- Make a copy of the '686x' directory in '/var/www/fusionpbx/resources/templates/provision/aastra' (naming it something unique)
- Manually add the global programmable buttons I want in the 'aastra.cfg' file (or possibly the '{mac}.cfg' file)
- Assign this new template to the appropriate devices
One other question: I see the Aastra templates just have 'aastra.cfg' and '{mac}.cfg' files, but Aastra phones do look for additional files, particularly a model-specific file (e.g., '6867i.cfg'). I thought maybe just adding a '6867i.cfg' to the '686x' template directory might work, but while watching the Nginx access.log file, the phone was still getting a "404" error for that file, so that dosn't appear to be the way to do it. *Is* there a way allow the phone to find such an additional file? I suspect it would involve editing some PHP code to have it identify the model and grab the appropriate vendor file?
Thanks!