mskenderian Posted June 7 Report Share Posted June 7 i follow the normal process, factory default, reboots, go into web gui, setting -> provisioning server http: tenant domain name, restart the phone, and it says provisional failed. This all started when i upgraded my dev PBX to 69.0.4, i could not make button changes, so i tried to factory reset it and here i am. Quote Link to comment Share on other sites More sharing options...
mskenderian Posted June 7 Author Report Share Posted June 7 how can I troubleshoot this? Quote Link to comment Share on other sites More sharing options...
mskenderian Posted June 7 Author Report Share Posted June 7 Quote [9] 11:54:47.504 Accept connection 145 from ipAddressⓘ [9] 11:54:47.519 Request from ipAddress:52412 for /64167f41374e.cfgⓘ GET /64167f41374e.cfg HTTP/1.1 Host: tenantDomainName Accept: */* User-Agent: FileTransport PolycomVVX-VVX_301-UA/6.4.3.5156 Type/Application [7] 11:54:47.519 Provisioning without domain contextⓘ [9] 11:54:47.521 Failed to match 64167f41374e.cfgⓘ [5] 11:54:47.522 Loading file 64167f41374e.cfg from UA "FileTransport PolycomVVX-VVX_301-UA/6.4.3.5156 Type/Application" from the tftp folderⓘ [9] 11:54:47.522 REST: Return 404 Not Foundⓘ HTTP/1.1 404 Not Found Content-Type: text/html Cache-Control: no-cache Cache-Control: no-store Content-Length: 173 <html><head> <title>Error</title> </head><body> <h1>File was not found</h1> <b></b> <p>Please ask your system administrator to check the log file.</p> </body></html> [6] 11:54:47.564 Delete HTTP connection 145 from ipAddress:52412ⓘ [9] 11:54:47.596 Accept connection 146 from ipAddressⓘ [9] 11:54:47.608 Request from ipAddress:22244 for /000000000000.cfgⓘ GET /000000000000.cfg HTTP/1.1 Host: tenantDomainName Accept: */* User-Agent: FileTransport PolycomVVX-VVX_301-UA/6.4.3.5156 Type/Application [7] 11:54:47.609 Provisioning without domain contextⓘ [9] 11:54:47.610 Failed to match 000000000000.cfgⓘ [5] 11:54:47.610 Loading file 000000000000.cfg from UA "FileTransport PolycomVVX-VVX_301-UA/6.4.3.5156 Type/Application" from the tftp folderⓘ [9] 11:54:47.611 REST: Return 404 Not Foundⓘ HTTP/1.1 404 Not Found Content-Type: text/html Cache-Control: no-cache Cache-Control: no-store Content-Length: 173 <html><head> <title>Error</title> </head><body> <h1>File was not found</h1> <b></b> <p>Please ask your system administrator to check the log file.</p> </body></html> [6] 11:54:47.650 Delete HTTP connection 146 from ipAddress:22244ⓘ [9] 11:54:47.692 Accept connection 147 from ipAddressⓘ [9] 11:54:47.699 Request from ipAddress:38558 for /64167f41374e-directory.xmlⓘ GET /64167f41374e-directory.xml HTTP/1.1 Host: tenantDomainName Accept: */* User-Agent: FileTransport PolycomVVX-VVX_301-UA/6.4.3.5156 Type/Application [7] 11:54:47.699 Provisioning without domain contextⓘ [9] 11:54:47.700 Failed to match 64167f41374e-directory.xmlⓘ [5] 11:54:47.700 Loading file 64167f41374e-directory.xml from UA "FileTransport PolycomVVX-VVX_301-UA/6.4.3.5156 Type/Application" from the tftp folderⓘ [9] 11:54:47.700 REST: Return 404 Not Foundⓘ HTTP/1.1 404 Not Found Content-Type: text/html Cache-Control: no-cache Cache-Control: no-store Content-Length: 173 <html><head> <title>Error</title> </head><body> <h1>File was not found</h1> <b></b> <p>Please ask your system administrator to check the log file.</p> </body></html> [6] 11:54:47.737 Delete HTTP connection 147 from ipAddress:38558ⓘ [9] 11:54:47.796 Accept connection 148 from ipAddressⓘ [9] 11:54:47.808 Request from ipAddress:49820 for /000000000000-directory.xmlⓘ GET /000000000000-directory.xml HTTP/1.1 Host: tenantDomainName Accept: */* User-Agent: FileTransport PolycomVVX-VVX_301-UA/6.4.3.5156 Type/Application [7] 11:54:47.808 Provisioning without domain contextⓘ [9] 11:54:47.809 Failed to match 000000000000-directory.xmlⓘ [5] 11:54:47.809 Loading file 000000000000-directory.xml from UA "FileTransport PolycomVVX-VVX_301-UA/6.4.3.5156 Type/Application" from the tftp folderⓘ [9] 11:54:47.809 REST: Return 404 Not Foundⓘ HTTP/1.1 404 Not Found Content-Type: text/html Cache-Control: no-cache Cache-Control: no-store Content-Length: 173 <html><head> <title>Error</title> </head><body> <h1>File was not found</h1> <b></b> <p>Please ask your system administrator to check the log file.</p> </body></html> [6] 11:54:47.849 Delete HTTP connection 148 from ipAddress:49820ⓘ Quote Link to comment Share on other sites More sharing options...
Vodia PBX Posted June 8 Report Share Posted June 8 It should match the following pattern (from pop_polycom.xml): <file name="polycom_master.xml" encoding="xml"> <pattern mac="0">############.cfg</pattern> <user-agent>FileTransport Polycom</user-agent> <user-agent>FileTransport PolyEdge</user-agent> <prefix>true</prefix> <vendor>Polycom</vendor> <protocol>tftp,http,https</protocol> </file> How is the whole HTTP request from the phone looking? Has anything changed for Poly(com), maybe its HP now? Did you open for provisioning (pairing)? Anything in the log for provisioning that might prove additional clue? Quote Link to comment Share on other sites More sharing options...
mskenderian Posted June 8 Author Report Share Posted June 8 Nothing has changed. I just upgraded pbx 68.0.30 To 69.0.4 phone firmware is the same. It’s clearly the PBX server. It says Mac ID not found in domain context. Quote Link to comment Share on other sites More sharing options...
Vodia PBX Posted June 8 Report Share Posted June 8 4 hours ago, mskenderian said: It’s clearly the PBX server. It says Mac ID not found in domain context. Hmm. But the MAC is in the device inventory? What is the exact log message about the domain context? Quote Link to comment Share on other sites More sharing options...
mskenderian Posted June 8 Author Report Share Posted June 8 See logs above. unless your asking for something else Quote Link to comment Share on other sites More sharing options...
Vodia PBX Posted June 8 Report Share Posted June 8 35 minutes ago, mskenderian said: See logs above. Oops should have expanded it... It looks like the support for the new PolyEdge devices displaced the support for the older Polycom devices. We'll fix that in the next build. If you like, remove the User-Agent lines for the Edge devices in the pnp_polycom and then they should work again. Quote Link to comment Share on other sites More sharing options...
Vodia PBX Posted June 8 Report Share Posted June 8 35 minutes ago, mskenderian said: See logs above. Oops should have expanded it... It looks like the support for the new PolyEdge devices displaced the support for the older Polycom devices. We'll fix that in the next build. If you like, remove the User-Agent lines for the Edge devices in the pnp_polycom and then they should work again. Quote Link to comment Share on other sites More sharing options...
mskenderian Posted June 8 Author Report Share Posted June 8 its fine. its a dev machine. i will wait. can we port poly edge and new fanvil like w6116w to v68? it might be a while until i move production to v69, but need basic things like phone template to work out of the box in v68 Quote Link to comment Share on other sites More sharing options...
Vodia PBX Posted June 9 Report Share Posted June 9 23 hours ago, mskenderian said: its fine. its a dev machine. i will wait. If you like, try 68.0.5 (daily build). 23 hours ago, mskenderian said: can we port poly edge and new fanvil like w6116w to v68? it might be a while until i move production to v69, but need basic things like phone template to work out of the box in v68 Poly Edge B will be a challenge because it's a completely different phone. The Poly Edge E series is a lot easier—it's practically just a renamed user-agent. Quote Link to comment Share on other sites More sharing options...
mskenderian Posted June 9 Author Report Share Posted June 9 51 minutes ago, Vodia PBX said: If you like, try 68.0.5 (daily build). Poly Edge B will be a challenge because it's a completely different phone. The Poly Edge E series is a lot easier—it's practically just a renamed user-agent. Thats fine, lets do Poly Edge E and Fanvil W6116W on v68 Poly Edge B, just looks cheap. horrible screen. B10 and B20, doesnt even have gigabit ports. B10 doesnt even support POE. Quote Link to comment Share on other sites More sharing options...
mskenderian Posted June 9 Author Report Share Posted June 9 1 hour ago, Vodia PBX said: If you like, try 68.0.5 (daily build). it works. The button type Cell Phone, doesn't show on the phone and the template edit button under Device Management doesnt do anything. Quote Link to comment Share on other sites More sharing options...
Vodia PBX Posted June 10 Report Share Posted June 10 13 hours ago, mskenderian said: The button type Cell Phone, doesn't show on the phone and the template edit button under Device Management doesnt do anything. The template icon is just an indicator. But maybe it makes sense to make that a link to the actual profile. Quote Link to comment Share on other sites More sharing options...
mskenderian Posted June 10 Author Report Share Posted June 10 5 hours ago, Vodia PBX said: The button type Cell Phone, doesn't show on the phone how about this? why doesnt it provision to the phone. Quote Link to comment Share on other sites More sharing options...
Vodia PBX Posted June 10 Report Share Posted June 10 Seems like a glitch for the Polycom phones that has not been found in the past ten years or so. We'll fix it in the next release. Until then you can just use the star code. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.