07-26-2018 09:41 AM
Hi there,
My SPA-122 will grab a configuration file from our provisioning server if the URL provided via DHCP is HTTP, but not via HTTPS.
I've tried DHCP Option 66, 159, and 160. All work with HTTP, but none work with HTTPS.
Is there some trick to getting HTTPS provisioning working?
Thanks,
Brad
07-26-2018 12:35 PM - edited 07-26-2018 12:41 PM
option 66 is standard option "tftp server name". Name of server is allowed here only.
You should use vendor specific DHCP option 160 to push "full url" parameter to device. 1.3.1 firmware or newer is required if you wish to use https in option 160
This post contain information related to other's site thus it may contain information considered Sensitive or Confidential. |
07-26-2018 12:45 PM
I'm on firmware 1.4.1.
As I mentioned, I tried Option 160, but HTTPS still won't take.
Any other suggestions?
07-26-2018 01:26 PM
Well, what's exact meaning of "won't take" ?
It may mean anything from "option 160 is ignored" to "SSL handshake with HTTPS server has failed". And even more.
Turn on syslog&debug of Voice Application (highest level possible). Capture all packets on wire - DHCP, DNS, attempt to setup SSL and so on. It could help to narrow the cause.
This post contain information related to other's site thus it may contain information considered Sensitive or Confidential. |
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide