Show posts
I never had issues with the older sail versions using legacy polycom phones. I just upgraded to 4.1 on debian and I have not been able to get either older IP550(ver3_3_5) or newer VVX 500(ver4_1_8) to receive the provisioning files from the http /provisioning directory. I manually upgraded both models to the recommended software using the http://voipt2.polycom.com website.
Where are the specific [MACADDRESS].cfg, [MACADDRESS]-polycom-phone1.cfg , [MACADDRESS]-polycom-locals.cfg files being placed? They are not in the /public/polycom folder and I can't see them in the sark.db sqlite3 database.
This is what /var/log/messages puts out on a provisioning attempt:
The polycom logs are long and not very descriptive, This is a sample of Minor Errors:
If I look at the Polycoms through their direct web interface they are all at default settings after booting up so the cfg files are invalid or not being accepted. Additionally each Polycom model family have different cfg formats but require identical file names so there would have to be distinctive folders under the public share to accomodate this. Looking at your sark.conf and device.php it that you are just pushing them out which means a wireshark packet trace is the only way to see what is being transmitted.
Do you have documentation posted on how the .cfg files are built?
Where are the specific [MACADDRESS].cfg, [MACADDRESS]-polycom-phone1.cfg , [MACADDRESS]-polycom-locals.cfg files being placed? They are not in the /public/polycom folder and I can't see them in the sark.db sqlite3 database.
This is what /var/log/messages puts out on a provisioning attempt:
Code Select
May 8 23:21:52 asterisk apache2: 192.168.1.55 0004f2afe689-calls.xml provisioning data not found in db. Sending 404 and giving up
May 8 23:21:52 asterisk apache2: 192.168.1.55 sending config 0004f2afe689-directory.xml
May 8 23:21:52 asterisk apache2: 192.168.1.55 0004f2afe689-calls.xml provisioning data not found in db. Sending 404 and giving up
May 8 23:21:52 asterisk apache2: 192.168.1.55 sending config 0004f2afe689-directory.xml
May 8 23:21:53 asterisk apache2: 192.168.1.55 sending config 0004f2afe689.cfg
May 8 23:21:53 asterisk apache2: 192.168.1.55 sending config 0004f2afe689-phone.cfg
May 8 23:21:53 asterisk apache2: 192.168.1.55 0004f2afe689-web.cfg provisioning data not found in db. Sending 404 and giving up
May 8 23:21:53 asterisk apache2: 192.168.1.55 000000000000-license.cfg not found in db(RowCount). Sending 404 and giving up
May 8 23:21:53 asterisk apache2: 192.168.1.55 0004f2afe689-license.cfg provisioning data not found in db. Sending 404 and giving up
May 8 23:21:53 asterisk apache2: 192.168.1.55 Ignoring PUT request - Sending 200 and giving up
May 8 23:21:55 asterisk apache2: 192.168.1.55 Ignoring PUT request - Sending 200 and giving up
The polycom logs are long and not very descriptive, This is a sample of Minor Errors:
Code Select
000036.338|clist|4|00|dbSet::startLoadLocalSet:No local copy, requesting backup from server
000036.484|clist|4|00|dbIO::processResult:copy error
000036.484|clist|4|00|dbSet::srv2mem:transfer failed
000036.593|clist|4|00|dbSet::startLoadLocalSet:No local copy, requesting backup from server
000036.593|clist|4|00|dbSet::load:cleared load error state m_sync=<0x40>
000036.629|clist|4|00|dbIO::processResult:copy error
000036.629|clist|4|00|dbSet::srv2mem:transfer failed
If I look at the Polycoms through their direct web interface they are all at default settings after booting up so the cfg files are invalid or not being accepted. Additionally each Polycom model family have different cfg formats but require identical file names so there would have to be distinctive folders under the public share to accomodate this. Looking at your sark.conf and device.php it that you are just pushing them out which means a wireshark packet trace is the only way to see what is being transmitted.
Do you have documentation posted on how the .cfg files are built?